Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
mariotme said:
Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
Click to expand...
Click to collapse
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Entropy512 said:
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Click to expand...
Click to collapse
I totally understand Entropy512! Thanks for your input buddy. Appreciate all your efforts man. Keep it up :good:
Entropy512 said:
I wanted a Z2. I really, really wanted one.
Click to expand...
Click to collapse
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
May I Taste said:
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
Click to expand...
Click to collapse
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Entropy512 said:
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Click to expand...
Click to collapse
Thanks for your kind answer and I can understand you. It seems however that the Z4 will now last for one year as flagship. Anyway I'll make sure to stay tuned if by chance you work on OmniROM for it.
Have a wonderful year, you and your whole family!
There some unofficial builds for the Sony Sirius floating around...
http://infectedbuilds.net/downloads/sirius/omni_lp/
From my very brief play with it, there's no Cam or NFC but everything else seems pretty useable.
A number of Omni team members are working with the Sony AOSP guys. Short-term it means a lot of things are broken that aren't in CM since Sony AOSP is reworking a bunch of stuff onto a newer unified kernel that will support a large variety of devices. Long-term it'll allow us to support more Sony devices with less effort.
I think one of the guys working this has a sirius... I forget who.
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
mikeysteele said:
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
Click to expand...
Click to collapse
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Entropy512 said:
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Click to expand...
Click to collapse
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
mikeysteele said:
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
Click to expand...
Click to collapse
Yeah. They used a kernel backcompat hack, and are using old 4.3 rhine blobs because those are the last ones that were completely 100% DRM-free.
DRM issues have caused all sorts of problems with rhine/shinano cameras ever since 4.4 - Workarounds for many of these have been found, but not all. But the kernel backcompat hacks would still be needed (potentially multiple hacks for each device supported by the Sony AOSP kernel) and that gets nasty.
So the current plan is to have a unified set of sensor drivers in the kernel, with blobs provided as part of the Sony AOSP project. However I think this is going to be easier said than done - it's not just Sony lawyers, but Qualcomm lawyers. It really sucks that the entirety of Qualcomm's mm-camera subsystem is proprietary and there's no way for an opensource developer to write modules for it, which prevents any of the community side of the Sony AOSP project from working on some things. Otherwise it would probably be not too difficult to replace Sony's noise reduction algorithm (likely with a better one... Sony's NR algorithm got slammed for being too aggressive and killing sharpness over in a dpreview review... All that DRM protection for something some people actually prefer to have gone.)
Edit: And yes, Sony's stock firmwares are amazing. My Z3 holds the record for longest I've ever owned a device without even bothering to root it.
Another thing, my phone is the China Mobile version (L50t) and OmniRom runs perfectly on it, I just have to change the radio and wlan firmware. I can supply the required files and be a tester if you wanted to add official support for this varient.
Related
sosad dat it only includes 2011 lineup
http://developer.sonyericsson.com/wp/2011/11/17/camera-libraries-available-for-sony-ericsson-phones/
Camera libraries available for Sony Ericsson phones
As promised when we announced our support of independent developers, we have now made the camera library binaries for a number of Sony Ericsson phones available under a special end user license agreement (EULA). You can use these camera libraries to handle the camera hardware in our 2011 Xperia™ phones except Xperia™ PLAY, which has a different camera module.
Download and find out more after the jump.
As we stated a while back, we recognise custom ROMs as an important part of the Android™ ecosystem. When we decided to support the FreeXperia group working on the custom ROMs for Sony Ericsson phones, we quickly found out they had problems with our cameras. This is because the camera technology used by Sony Ericsson is a very advanced – we actually consider it to be the best in the market. However it is a closed implementation, so we can’t share the source code for it.
However, after some discussions with the FreeXperia team, we agreed to allow the FreeXperia team to use our libraries (which can be seen as drivers) for the cameras. But these libraries could not be used as they were, since they had dependencies to other modules in the phone that could not be included in the custom ROM project. To solve this, we rebuilt the libraries and provided them with a special EULA.
These newly rebuilt camera libraries are now modified with less dependencies to other libraries. We have recompiled the libraries without code changes but with different build flags. You can use these camera libraries under a special EULA-license. There are several important conditions you need to comply with, for example:
The Software can be copied and distributed under the condition that the original copyright notice and disclaimer of warranty will stay intact and the Licensee will not charge money or fees for the Software, whether as a stand-alone product, or as part of a compilation or anthology.
Several more conditions apply – please read the full EULA and make sure you are complying before using the camera libraries in any software. Download the camera libraries and find the full EULA text in the zip. Here you can also find a short instruction on how to start using these libraries. For more information on how use libraries like these, please see the FreeXperia project related thread on the XDA forum. We don’t have any possibilities in providing further support on this.
At last but not least, we want to say thanks to all of you in the community supporting this work, we really appreciate it. Even though we might not be able to support every single request we get, we are doing our best to support the community going forward.
Karl-Johan Dahlström
Head of Developer Relations
Sony Ericsson
More information
Download the camera libraries for the 2011 Xperia phones.
Find out how Sony Ericsson is supporting independent developers.
Learn how to build a Linux kernel.
Visit our unlock boot loader web service.
sounds good. anyone who understand this may improve the photo quality.
i can't wait to
anakinlam95 said:
sosad dat it only includes 2011 lineup
http://developer.sonyericsson.com/wp/2011/11/17/camera-libraries-available-for-sony-ericsson-phones/
Camera libraries available for Sony Ericsson phones
As promised when we announced our support of independent developers, we have now made the camera library binaries for a number of Sony Ericsson phones available under a special end user license agreement (EULA). You can use these camera libraries to handle the camera hardware in our 2011 Xperia™ phones except Xperia™ PLAY, which has a different camera module.
Download and find out more after the jump.
As we stated a while back, we recognise custom ROMs as an important part of the Android™ ecosystem. When we decided to support the FreeXperia group working on the custom ROMs for Sony Ericsson phones, we quickly found out they had problems with our cameras. This is because the camera technology used by Sony Ericsson is a very advanced – we actually consider it to be the best in the market. However it is a closed implementation, so we can’t share the source code for it.
However, after some discussions with the FreeXperia team, we agreed to allow the FreeXperia team to use our libraries (which can be seen as drivers) for the cameras. But these libraries could not be used as they were, since they had dependencies to other modules in the phone that could not be included in the custom ROM project. To solve this, we rebuilt the libraries and provided them with a special EULA.
These newly rebuilt camera libraries are now modified with less dependencies to other libraries. We have recompiled the libraries without code changes but with different build flags. You can use these camera libraries under a special EULA-license. There are several important conditions you need to comply with, for example:
The Software can be copied and distributed under the condition that the original copyright notice and disclaimer of warranty will stay intact and the Licensee will not charge money or fees for the Software, whether as a stand-alone product, or as part of a compilation or anthology.
Several more conditions apply – please read the full EULA and make sure you are complying before using the camera libraries in any software. Download the camera libraries and find the full EULA text in the zip. Here you can also find a short instruction on how to start using these libraries. For more information on how use libraries like these, please see the FreeXperia project related thread on the XDA forum. We don’t have any possibilities in providing further support on this.
At last but not least, we want to say thanks to all of you in the community supporting this work, we really appreciate it. Even though we might not be able to support every single request we get, we are doing our best to support the community going forward.
Karl-Johan Dahlström
Head of Developer Relations
Sony Ericsson
More information
Download the camera libraries for the 2011 Xperia phones.
Find out how Sony Ericsson is supporting independent developers.
Learn how to build a Linux kernel.
Visit our unlock boot loader web service.
Click to expand...
Click to collapse
2011 line of [email protected]#$% [email protected]#%$ phones...
MASSIVE FACE PALM.
What i find so funny.. is how the x10 gets nothing.
They must have buried the source code disks for the x10 in the SUN.
Because it's nearly impossible to find anything on any 2010 device.
x10 wont go anywhere....even x10 as old phone also they not share the drivers libraries. thats mean our development for x10 wont go so far. They just gave another reason why we should not buy x10 at these days and why we should start looking for new phone.
Problem....
Hi all..i copied the 3 files for my arc and into the correct folder as instructed..
then i rebooted..
now the phone is on 'sony ericsson' screen..reboot n rebooted..
erm..
anyway to remove the 3 files again?
hinata76 said:
Hi all..i copied the 3 files for my arc and into the correct folder as instructed..
then i rebooted..
now the phone is on 'sony ericsson' screen..reboot n rebooted..
erm..
anyway to remove the 3 files again?
Click to expand...
Click to collapse
Are you trying to use arc camera lib files on x10? Only way to repair is recovery restore if it is working or flashtool a ftf rom or seus...
Sent from my X10i using xda premium
hinata76 said:
Hi all..i copied the 3 files for my arc and into the correct folder as instructed..
then i rebooted..
now the phone is on 'sony ericsson' screen..reboot n rebooted..
erm..
anyway to remove the 3 files again?
Click to expand...
Click to collapse
If u copied the files given by SE in ur arc so u are doing it wrong
that files are for development purposes
Repair ur phone using pc companion
The Gingerbread Man said:
Are you trying to use arc camera lib files on x10? Only way to repair is recovery restore if it is working or flashtool a ftf rom or seus...
Sent from my X10i using xda premium
Click to expand...
Click to collapse
no im using on arc..then the whole phone just died..
just reflashed now okay!
almost got my fingers burnt..lol.
Don't know if anyone or the devs notice this:
Dec 8, 2011
Sony Ericsson Xperia™ X10 add-on for the Android SDK
The Sony Ericsson Xperia™ X10 add-on for the Android SDK includes the complete Android system with additions customizing it for the X10 : Sony Ericsson splash screen; X10 colour backgrounds; A "skin" of the X10 which is a simple graphic of the front of the phone; A hardware.ini file to set the operating parameters for screen, camera, audio and so on. Link:http://developer.sonyericsson.com/wportal/devworld/downloads/download/dw-102216-xperia-x10sdkadd-onr1?cc=gb&lc=en
Can this help with the camera development?
Can anyone make normal flash for x10?
Sent from my xperia "z10i"
Many rom projects like Cyanogen mod, Paranoid droid rom and many others were released only for renowned company phones like Galaxy Series, Nexus series etc etc, where as millions & billions of MTK soc phones that contribute alot to the daily millions of Android activations are left out. Many MTK phones developers started request threads for cyanogen mod and other rom communities to build/release a rom for MTK phones but those request were neglected till date.
Now with the start of new rom project "Omni", MTK phone devs are hoping that this rom will also be compiled & released for MTK phones. We want Omni pioneers to release this rom for millions & billions of MTK phones.
We are willing to help you guys making Omni rom project better & grow.
Regards
Wouldn't have it been easier to read some posts in the forum?
This will happen. When you're able to watch the presentation video (which will be up in the next few days) you'll notice that @XpLoDWilD shows Omni running on the Oppo R819, a quad-core MTK device.
jerdog said:
This will happen. When you're able to watch the presentation video (which will be up in the next few days) you'll notice that @XpLoDWilD shows Omni running on the Oppo R819, a quad-core MTK device.
Click to expand...
Click to collapse
There are a lot of things in the way. Also, any MTK devices that ship without kernel sources (there are a lot of them) are still out of luck.
The R819 is a game changer here - Oppo really wants it to receive community firmware support and has been EXTREMELY cooperative with us in terms of getting us documentation.
Entropy512 said:
The R819 is a game changer here - Oppo really wants it to receive community firmware support and has been EXTREMELY cooperative with us in terms of getting us documentation.
Click to expand...
Click to collapse
So they are giving you access to the MTK framework sources? Or do you have to reimplement the dual sim support (I have never seen any open source ROM with dual sim support)? I'd really love to help a bit, having some MTK6577 phones lying around here.
I too have two MTK phones .....they are a powerful if it got development projects like this ...it will be the no.1 vendor in chip set marketing and ...I support for OMNI PROJECT
Sent from my Fly IQ451 using XDA Premium 4 mobile app
C-o-M said:
So they are giving you access to the MTK framework sources? Or do you have to reimplement the dual sim support (I have never seen any open source ROM with dual sim support)? I'd really love to help a bit, having some MTK6577 phones lying around here.
Click to expand...
Click to collapse
I'm not sure about the state of dsim support. We do have access to quite a bit, however some items even the OEM we're working with doesn't have access to source for, and it's also a nasty licensing minefield.
There's much better potential than there has been previously, however there are still some nasty technical and legal challenges. For example, MTK's 4.2 firmware appears to be using all sorts of hwcomposer backcompat hacks to use what is effectively a 4.0 (ICS) HWC.
Entropy512 said:
I'm not sure about the state of dsim support. We do have access to quite a bit, however some items even the OEM we're working with doesn't have access to source for, and it's also a nasty licensing minefield.
There's much better potential than there has been previously, however there are still some nasty technical and legal challenges. For example, MTK's 4.2 firmware appears to be using all sorts of hwcomposer backcompat hacks to use what is effectively a 4.0 (ICS) HWC.
Click to expand...
Click to collapse
With this I assume device will not receive 4.4 barely 4.3 but can I ask how is to work with OEM?
Sent from my Xperia U using xda app-developers app
XperianPro said:
With this I assume device will not receive 4.4 barely 4.3 but can I ask how is to work with OEM?
Sent from my Xperia U using xda app-developers app
Click to expand...
Click to collapse
Nobody can predict what happens in the future.
In terms of working with OEMs, not sure what your question is, but one thing we do bring to the table with Omni is considerable experience in working with OEMs. And that should be rather beneficial for everyone
Will you be allowed to release all sources needed to build the ROM?
There are sources for various MTK devices (MT6577/MT6575) that can be used already. I assume it would be no problem for the omni team to integrate them into their builds.
darkguy2008 said:
There are sources for various MTK devices (MT6577/MT6575) that can be used already. I assume it would be no problem for the omni team to integrate them into their builds.
Click to expand...
Click to collapse
We have more recent ones that are being used to bring up MTK devices.
At the BBQ, Xplod demonstrated an Oppo r819 running Omni, which is an MT6589
pulser_g2 said:
We have more recent ones that are being used to bring up MTK devices.
At the BBQ, Xplod demonstrated an Oppo r819 running Omni, which is an MT6589
Click to expand...
Click to collapse
So with this you mean that those sources work for MT6577 devices?
I wish you guys the best of luck, but conserning MTK and their closed sources policy, i really don't believe those sources (and im talking about the framework /RIL) will be Open Source.
If we are lucky enought we may get some working builds for some of the phones (if an brand gives you support), but concerning the MTK licenses, well its an MINE FIELD.
An good example is the on-going Cyanogen project by FAEA for the F2S (MT6589), they got the green light from MTK, BUT the project will remain Closed Source, so no one will get those sources...
B.Regards
superdragonpt said:
An good example is the on-going Cyanogen project by FAEA for the F2S (MT6589), they got the green light from MTK, BUT the project will remain Closed Source, so no one will get those sources...
Click to expand...
Click to collapse
AFAIK, you are wrong:
chasepoes said:
Well I know of one dev. who is develloping CM port voor MTK658x devices (usinf Faea mobile). For now he has to operate under a NDA agreement, but once finished his source will be come available.
Click to expand...
Click to collapse
darkguy2008 said:
So with this you mean that those sources work for MT6577 devices?
Click to expand...
Click to collapse
Unknown. And as I've said, it's a licensing nightmare.
It may be that certain components will have to be developed in a "some people have the source but can only release blobs" - I would prefer to avoid this if at all possible. The issue is if any of those "files with nasty license" are in things that can't be cleanly separated, it will present a MAJOR issue.
Entropy512 said:
Unknown. And as I've said, it's a licensing nightmare.
It may be that certain components will have to be developed in a "some people have the source but can only release blobs" - I would prefer to avoid this if at all possible. The issue is if any of those "files with nasty license" are in things that can't be cleanly separated, it will present a MAJOR issue.
Click to expand...
Click to collapse
Well I assume something like the HTC Magic or the Defy can be done. They don't have the sources for the hardware GPU but they managed to enable hardware compositing after some work somehow. I don't think that MTK will oppose to the project using the libs and such instead of having full access to the code, usually that feels less restrictive for both the company and the devs, imho.
I may be talking rubbish though, I'd just like the MT6577 devices to get some lovin', because we've been fighting for quite some time against ZTE for them to release the kernel sources so we can develop ROMs for the V970M and more =/
darkguy2008 said:
Well I assume something like the HTC Magic or the Defy can be done. They don't have the sources for the hardware GPU but they managed to enable hardware compositing after some work somehow. I don't think that MTK will oppose to the project using the libs and such instead of having full access to the code, usually that feels less restrictive for both the company and the devs, imho.
I may be talking rubbish though, I'd just like the MT6577 devices to get some lovin', because we've been fighting for quite some time against ZTE for them to release the kernel sources so we can develop ROMs for the V970M and more =/
Click to expand...
Click to collapse
ZTE,I dont know much about this company but its worse than Sony I think...
Why not release kernel sources,what are developers doing at their company...
XperianPro said:
ZTE,I dont know much about this company but its worse than Sony I think...
Why not release kernel sources,what are developers doing at their company...
Click to expand...
Click to collapse
Pretty much most Chinese companies are like this. Oppo is VERY non-typical of a Chinese company, which is why they have a FAR better chance of global success than any other Chinese mobile OEM right now.
Entropy512 said:
Pretty much most Chinese companies are like this. Oppo is VERY non-typical of a Chinese company, which is why they have a FAR better chance of global success than any other Chinese mobile OEM right now.
Click to expand...
Click to collapse
How very true. I have high hopes for this project as my current device is an OPPO R819. I chose OPPO because exactly they try to be open with the developers, having the experience of Motorola and their locked bootloaders the past years while the Motorola DEFY was my main device. It took a long time for the DEFY to get its first custom kernel and it only happened thanks to some very persistent people. It shouldn't be like this, so as long I have a choice I'll opt for unlocked (and cheap...) devices.
Sent from my Nexus 7 using xda app-developers app
THey guys i just created this petition for sony to add Camera2 API , in a Sony forum , Sony Xperia Staff stated that they will add this feature if there is a huge demand on it .
" we will consider this for the future if there is a popular demand "
http://talk.sonymobile.com/t5/Software-Updates/Camera2-API/td-p/974742
So i just created this petition to show the great demand of users , please share it all over xda
https://www.change.org/p/sony-mobil...pport-to-xperia-smartphones?just_created=true
Thank you!
res.
I'm pretty sure a petition already exists
@muzab a
I looked everywhere i couldn't find one , now just share this one so we can reach thousands
Thank You
http://email.change.org/mpss/c/hQA/...YsbFj-2Fnr1tIwpy-2BPjoUzKExudIx-2BxnqUA-3D-3D
---------- Post added at 11:28 AM ---------- Previous post was at 11:28 AM ----------
Delete yr one and use this
This is something else , my petiotion is for Camera2 API , check the sony website they said they will support it if they find huge demand.
that petition has nothing to do with that
Guys please share it , just copy the link and post on other threads, we need to reach thousands so sony can see it and see the demand
Are you really that naive? Support for the device ended after ICS 4.0.4 and you really expect them to add support to Camera2 API (which by the way is an Lollipop feature)?
@RollingRoman uhh noobs again , this forum is for all sony devices and you can see it in any sony device forum , but for sure we only mean devices that are still in support
RollingRoman said:
Are you really that naive? Support for the device ended after ICS 4.0.4 and you really expect them to add support to Camera2 API (which by the way is an Lollipop feature)?
Click to expand...
Click to collapse
Man..please, forgot about ended support 4.0.4, it's xperia 2011 series..... For that, hope that CM12 would release lollipop update with Camera2 API..
Now we're talking about the Z series (maybe T2 Ultra and C3 too) which got official lollipop update and yes, Camera2 API is a part of lollipop feature. We're hoping sony to release an update featured with Camera2 API and this is cross-sony device section.. So it means all "SONY" related thing is here.. sorry, no hard feeling no harshing.. PEACE NO WAR brother..
@daniLaLaLaLaLa Thank you
Ref
M7ammad said:
Ref
Click to expand...
Click to collapse
Signed. I hope we succeed.I also wrote to Sony. Here is their answer:
Dear Mr. Tochev,
Thank you for contacting Sony Xperia Support.
With regards to your inquiry, we would like to inform you that Android™ 5.0 supports the new camera features via android.hardware.camera2, and Google™ defines three modes for the new camera features:
1.Legacy mode (no support RAW capture)
2.Limited mode (optional capability for RAW capture)
3.Full mode (optional capability for RAW capture)
Currently, Xperia™ supports Legacy mode in our Lollipop update which incorporate features and functionality in addition to our already renowned camera experience.
As always, we monitoring our customer expectations and regarding supporting taking pictures in RAW format, we will consider this for the future if there is a popular demand.
They write the exxact same thing everytime.We have to push them harder to succeed.
@BlAckXpeRia
Let's show them the demand
Actually i think its nothing more than scripted customer care reply...It will take a lot of work for them to incorporate camera 2 api in our devices and i don't think they will bother..maybe incorporate it in future devices or something.
ref
M7ammad said:
@BlAckXpeRia
Let's show them the demand
Click to expand...
Click to collapse
I think we did it! Look at the Z3+. It supports all manual functions exept RAW.
BlAckXpeRia said:
I think we did it! Look at the Z3+. It supports all manual functions exept RAW.
Click to expand...
Click to collapse
''We did it'' one may say only when Sony pushes this API on all LP devices. Untill then, and i think they will keep it that way because they need to seel the new phone somehow, we should keep raising our voice, as it is not fair to have a damn good hardware that is ''ruined'' by lousy software. They need to enhance it ASAP in my opinion, or else Sony is risking a bad reputation going even worse...
bubimir13 said:
''We did it'' one may say only when Sony pushes this API on all LP devices. Untill then, and i think they will keep it that way because they need to seel the new phone somehow, we should keep raising our voice, as it is not fair to have a damn good hardware that is ''ruined'' by lousy software. They need to enhance it ASAP in my opinion, or else Sony is risking a bad reputation going even worse...
Click to expand...
Click to collapse
I think it will come atleast for Z2 and Z3. They are really similar. But no matter what Sony does, I am stuck with them. I just can't get away from that beautiful design and software. All other manufactures have things I hate(LG-plastic, Samsung-software, nexus line and motorola- awful camera). My only problem with Sony is the new API. And they don't forget their devices-even the 2012 xperia z has lollipop and may get M.
Its not guaranteed to come to z3 or even z2, z1 and grampa z we can now easily forget since z has an expired 18 months period and z1 is close to expiration... Further on, LG G$ as it stands has way more superior camera then z3, Samsung is also investing hugely in marketing, and only thing Sony needs to do basically to survive is to a) improve software department, not so much the overall UI but software in camera for instance, it lags behind Samsung, Apple and LG as things stand, but they mosty use Sony's hardware, more limited one, so there is no objection for not handling software part more effectivley. and B) to improve customer relations, as we all know Sony is always lagging with announcments for new software features, heck they event dont know if the M2 or T3 are in plans for LP upgrade (which is lousy)!!!!
Onwards, remember the explanation provided for question wheter Sony will publish and software update for camera2 API or not, Sony gave as a bunch of c**p and basically told us ''oh, go f**k yourself with that'' masked in ''if there will be public demand we will then see...''
Of corse there is public demand, why wouldn't there be on since people always appreciate good featured updates. Look at Samsung, they are doing everything they can to fix camera things, publishing updates more oftenlly then Sony Social networks CM published something on either Social network used by Sony.
I guess we are done for security updates. It has been right at 2 years. Sad thing is, this is still a great little phone. I am not in the mood to root and tinker with issues. I wished there was a stable ROM out there to use. I wished that LineageOS would pick this little jewel up. Oh, well. It has been a good 2 years of a small, but very informative community of X Compact users.
I am still searching for a small phone replacement since Sony does not make small phones anymore. Post here if you have any recommendations.
Cheers!
del
I feel you. I think I've said it before on this forum, but I really don't get why there isn't a lineageos build for this phone. Lots of sony xperia phones have official lineageos builds and there even is an unofficial build for this device (so it's not exactly impossible to build).
That being said, I generally prefer omnirom and luckily they are supporting this device. I've been on omnirom 8.1 for ages and haven't encountered a bug yet, so imho it can definitely be considered stable. Right now I'm using a self-built omnirom 9.0 (security patch level 5 november 2018) as a daily driver and for a pre-official build it is already pretty stable. Sony's 'Pie' software binaries (which thankfully they still provide) are still in beta, so coupled with the omnirom team efforts the stability will only increase.
Bottom line for smartphone manufacturers: Just provide what is needed for the open source community to flourish, it'll cost you next to nothing and will pay you back in goodwill many times over.
Next upcoming problem is the lack of support for the Project Treble in Xperia X series devices which at least may cause significant delay in releasing ROMs based the newer Android versions or in the worst case might result in stopping their development as the successor - XZ1 series - supports it. I hope developers will follow the Z5 series path as there already is LineageOS for these. And hopefully some Xiaomi devices path as there are devices which now have unofficial support of the Project Treble.
BTW, we should also thank to the Google for an unwise cycle of releasing new Android version every year which accelerates fragmentation significantly as its main reason seems to be to persuade people to buy newer devices with latest version of Andoid OS on board.
harryharryharry said:
Lots of sony xperia phones have official lineageos builds and there even is an unofficial build for this device (so it's not exactly impossible to build).
Click to expand...
Click to collapse
I suppose more recent Sony smartphones have been sold in significantly lower quantities than older ones (I read many times about Sony's smartphones poor sales numbers) and it might be the reason of a smaller community gathered around those newer devices.
Software security updates stopped?
If Sony stops providing software updates after 2y, it means those of us with a Sony Xperia X Compact (F5321) are unable to add Work e-mail accounts as the Microsoft Intune app requires an Android software update dated May 2019.
This silly policy by Sony is preventing me from adding my work O365 account to the device and means I am very unlikely to buy another Sony mobile phone ever again as its usable life is 2 years max. I am actually quite raging because I like the phone -this is beyond stupid from Sony.
RTV_1974 said:
If Sony stops providing software updates after 2y, it means those of us with a Sony Xperia X Compact (F5321) are unable to add Work e-mail accounts as the Microsoft Intune app requires an Android software update dated May 2019.
This silly policy by Sony is preventing me from adding my work O365 account to the device and means I am very unlikely to buy another Sony mobile phone ever again as its usable life is 2 years max. I am actually quite raging because I like the phone -this is beyond stupid from Sony.
Click to expand...
Click to collapse
use browser.
intune sucks anyway.
RTV_1974 said:
If Sony stops providing software updates after 2y, it means those of us with a Sony Xperia X Compact (F5321) are unable to add Work e-mail accounts as the Microsoft Intune app requires an Android software update dated May 2019.
This silly policy by Sony is preventing me from adding my work O365 account to the device and means I am very unlikely to buy another Sony mobile phone ever again as its usable life is 2 years max. I am actually quite raging because I like the phone -this is beyond stupid from Sony.
Click to expand...
Click to collapse
This device has pretty lackluster support even in the dev community as well. All it's really got going for it atm but fortunately we have Lineage 17.1 and Project Treble. I recommend flashing a new rom if you don't want to switch phones.
Hello developers of XDA!
I'm Rox, a Razer Vanguard and i'm here to let you know that the Audio Source is now available for the Razer Phone 2! You can now find the complete source code on the Razer Developers website here
I'm glad you all now have access to the full open source material and we can finally see some movement on the custom development we all know from Android
I would also like to take this opportunity to ask the developers of XDA for some feedback. Is there anything stopping people in particular supporting the device in the community with custom ROM's and Kernels? And is there anything that Razer could do to help?
This is by no means any assurance but I will gather all your feedback and pass it on.
The community is the most important thing to a product and I will continue to raise the communities voice as much as possible.
Thank you so much for the time!
Rox - Razer Vanguard.
Roxas598 said:
Hello developers of XDA!
I'm Rox, a Razer Vanguard and i'm here to let you know that the Audio Source is now available for the Razer Phone 2! You can now find the complete source code on the Razer Developers website here
I'm glad you all now have access to the full open source material and we can finally see some movement on the custom development we all know from Android
I would also like to take this opportunity to ask the developers of XDA for some feedback. Is there anything stopping people in particular supporting the device in the community with custom ROM's and Kernels? And is there anything that Razer could do to help?
This is by no means any assurance but I will gather all your feedback and pass it on.
The community is the most important thing to a product and I will continue to raise the communities voice as much as possible.
Thank you so much for the time!
Rox - Razer Vanguard.
Click to expand...
Click to collapse
Thanks for the info, I'm waiting for my phone to arrive. I hope to start playing with the ROM very soon.
What's a Razer Vanguard?
It's like their tech support reps, except they're a little more involved. Already dealt with one on their site, and he was very helpful and responsive. Most replies were within just a couple hours. Seems like these guys actually use the hardware they support, and don't treat the users like idiots. Nice to see this, especially since they just laid off most of their phone division. Hopefully this is a sign of better things to come. This phone is a beast.
jonchance_84 said:
It's like their tech support reps, except they're a little more involved. Already dealt with one on their site, and he was very helpful and responsive. Most replies were within just a couple hours. Seems like these guys actually use the hardware they support, and don't treat the users like idiots. Nice to see this, especially since they just laid off most of their phone division. Hopefully this is a sign of better things to come. This phone is a beast.
Click to expand...
Click to collapse
That is essentially it! Thank you for the kind words, I'll be sure to pass it on to the team. We definitely do use the hardware we help with and for me personally the Razer Phone is my specialty but we all have experience with most Razer products.
I think there are two main things I would like to see:
1. Earlier factory images and the release of ota updates. It would be nice for those who have yet to get pie, for example.
2. Though I realize it's unlikely, the release of the device tree would really be a big boost to rom and kennel development
I second earlier factory image and source releases.
On another note. The sources we have currently had a lot of header/build issues. As other Devs have pointed out(elsewhere) this was probably due to the sources being built out of the device tree but they still seemed weird as I've never seen that before and can't make out how a device tree would have changed that. Would it be too much to ask that some time be taken to scrub the sources better and maybe even have some basic build scripts or instructions? I realize this is contrary to my first point but it's the next best thing to a device tree.
It would be nice to get full android 9 images the same as android 8.1
I still do not understand - why there is no support for aptx, aptx hd, ldac?!!!
And you can't even install it like on most other phones, maby razer developers know how fix it?
Also, due to a strange signature system, most gsi roms do not work.
How about Razer Phone 1?
Now I'm not a gamer, just got a used RP1 from a moderator on the Swedroid forum quite by accident, as it were.
I really quite like it, the Sharp IGZO screen especially, same as on my Xiaomi Mi Mix1, which was the main reason I got it.
I have had zero problems with it so far.
ROM for Andorid 9
GoomerHD said:
It would be nice to get full android 9 images the same as android 8.1
I still do not understand - why there is no support for aptx, aptx hd, ldac?!!!
And you can't even install it like on most other phones, maby razer developers know how fix it?
Also, due to a strange signature system, most gsi roms do not work.
Click to expand...
Click to collapse
+1 having the full image will save us a lot of time and will expedite the creation of mod ROM.
CurtisMJ said:
I second earlier factory image and source releases.
On another note. The sources we have currently had a lot of header/build issues. As other Devs have pointed out(elsewhere) this was probably due to the sources being built out of the device tree but they still seemed weird as I've never seen that before and can't make out how a device tree would have changed that. Would it be too much to ask that some time be taken to scrub the sources better and maybe even have some basic build scripts or instructions? I realize this is contrary to my first point but it's the next best thing to a device tree.
Click to expand...
Click to collapse
I was informed this is how all new MSM kernels are - they don't build properly out of the AOSP tree (it looks like Android's build system supplies some additional flags to the kernel make system to make it use some prebuilts and AOSP headers over the kernel-provided ones). I don't think this is unique to Razer, since it's a Qualcomm thing.
I've got build instructions for the kernel in my thread too if you need them.
Of course, I could be relaying incorrect information but this does seem like it's typical of Google/Qualcomm to be changing Open Source projects to fit their internal needs...
Rox598 said:
Rox - Razer Vanguard.
Click to expand...
Click to collapse
Can you guys get in contact with CurtisMJ on this forum and see about implementing his amazing Chroma logo alternative app, integrating features of it with the current Chroma logo app, or otherwise allowing us non-root users to systemize it?
https://forum.xda-developers.com/razer-phone-2/themes/beta-logo-oss-implementation-lighting-t3893981
It has a lot of features I want from the Chroma app, but I'm weary of rooting, especially now that Android 9 Pie has come out and no factory images for 9 Pie are on the Razer dev site. If you even wanted to put it in the next update and give users the option of which Chroma app they wanted to use, I'm sure CurtisMJ would think that was pretty neat, though you'd have to ask him. I mean, I'd personally pay to use it if it meant I didn't have to root. Maybe integrate it with the stock Chroma app, and charge $5 to upgrade to CurtisMJ's features, and then split the cash with him. Idk.
AbsoluteContingency said:
Maybe integrate it with the stock Chroma app,.
Click to expand...
Click to collapse
I wonder lol.
Interestingly I did see some code in the Chroma app which can grant use of the service to unprivileged apps. I think it was used to whitelist some other Razer component. Just opening up that functionality to users so they can "grant" Chroma access to apps of their choosing might be enough. Otherwise, if I could get a signed stub in the next OTA that'd be cool (and ridiculously unlikely, just to be clear)
Great comments everyone keep them coming!
GoomerHD said:
It would be nice to get full android 9 images the same as android 8.1
I still do not understand - why there is no support for aptx, aptx hd, ldac?!!!
And you can't even install it like on most other phones, maby razer developers know how fix it?
Also, due to a strange signature system, most gsi roms do not work.
Click to expand...
Click to collapse
Yeah, coming from my Samsung S8+, LDAC is the thing I'm missing the most.
I would just like to say thanks to Razer for listening to their customers and trying to be helpful, so: Thank you! :good: :victory:
I'm not a developer, but whatever these other guys need to get TWRP working, I'm all for
Pete450 said:
I would just like to say thanks to Razer for listening to their customers and trying to be helpful, so: Thank you! :good: :victory:
I'm not a developer, but whatever these other guys need to get TWRP working, I'm all for
Click to expand...
Click to collapse
That's my goal atm to get the developers points of view and requests I'm proud of the community helping each other out so this is my next focus.
So far my feedback list has faster Factory images, and source code, device tree, more Audio Codec (APT-X AND LDAC) and a couple of other things I can't get into.
If anyone else thinks of anything lmk and I'll add it to my list to send on. I hope the right person sees it but again there is zero assurances that any of it will happen but this is where the voices matter.
Thanks again everyone!
Might be a little off topic, but since this is a gaming phone, why can't I pair my old ps3 controller? I even tried an old usb Xbox 360 controller, which a usb host test app successfully found the device. I would have hoped this would have been built in, being a gaming phone and all. I'm on pie and rooted, even when trying multiple previous methods of trying to get something the work, all the phone wants to do is charge the connected device.
jonchance_84 said:
Might be a little off topic, but since this is a gaming phone, why can't I pair my old ps3 controller? I even tried an old usb Xbox 360 controller, which a usb host test app successfully found the device. I would have hoped this would have been built in, being a gaming phone and all. I'm on pie and rooted, even when trying multiple previous methods of trying to get something the work, all the phone wants to do is charge the connected device.
Click to expand...
Click to collapse
Unfortunately the PS3 controller doesn't connect and act like a good Bluetooth or USB device. There is an app called sixaxis controller on the play store that allows you to connect a PS3 controller via Bluetooth, but it needs root and I don't believe it works anymore. There's also an app for wired PS3. It's not a Razer issue, it's a controller issue.
CalebQ42 said:
Unfortunately the PS3 controller doesn't connect and act like a good Bluetooth or USB device. There is an app called sixaxis controller on the play store that allows you to connect a PS3 controller via Bluetooth, but it needs root and I don't believe it works anymore. There's also an app for wired PS3. It's not a Razer issue, it's a controller issue.
Click to expand...
Click to collapse
Right, I tested it all. That app gets to the part where it tries to pull the Mac of the phone's Bluetooth adapter and simply can't. I'm leaning more towards the an Oreo/Pie issue. Seems to be driver related.