Related
The X10 has an issue with the Bootloader being protected by Marlin DRM.
There is no obvious reason and no clear benefit to end users or the general public. Most likely a precautionary measure to ensure SE applications work as intended and to assist with purchases of games, music, updates to Android firmware (often mistakenly called ROM's) and features Sony Ericsson have not explained in any level of detail or even stated that it exists as part of their obligations and your rights to know as the consumer.
According to the W3C.
What are some potential invasions of privacy?
1. User authentication - current PKI protocols limit the degree of anonymity -- we need to know who are you so we can sue you if you infringe
2. Usage tracking for fraud prevention
OK. Now you have just purchased a Sony Ericsson Android phone and all your social network contacts from any social media site can be merged with your phone book, backed up into Google's Gmail and shared beyond any one or all of these service's. The man controlling 'everything' that happens on your device is SE.
The phone at core capability is able to run Ubuntu / Debian Linux, Windows, iPhone and emulate everything you might wish to or choose to. Thanks to this 'feature' in the form of the Marlin DRM and Seacert broadband bootstrap implementation being present on these phones... it isn't going to happen.
With the Xperia models, the entire operating system is virtualized on boot and impossible to modify the behavior of the boot loader, due to a very high grade encryption system, provided by Inter Trust.
Unlike HTC, Motorolla, Samsung (who own a stake in the Marlin DRM but choose not to use it for snooping or destroying the main purpose of Android phones) for that matter most other Android phone manufacturers, allow the boot loader to be modified without too much effort and load a custom bootloader for multiple firmwares.
e.g; Gingerbread 2.3.2 is the default o/s shipped with Sony Ericsson apps, you want to keep this but also load Honeycomb, or Gingerbread 2.3.3, a modified vanilla o/s without things like timescape and unnecessary apps that do nothing for saving battery life.. it's your phone and you should be able to have this choice, in fact the reason Android is open source, is stop one company from forming any kind of monopoly.
So what should DRM so for us?
Are there general requirements from the concept of free flow of information?
* avoid unnecessary use restrictions, respect fair use
* universal service --- equal and fair access right
* support variety of licensing options
* make it easy for users to act lawfully
* seamless operation, interoperability of DRMS
* Support Information Search(engines)
* make licensing easy to reduce transaction costs
* secure operating environment: integrity and availability of content
* avoid bottlenecks and monopolies when standardizing (production and distribution)
Conclusion:
* copyright laws give free hand to those who develop DRMS
* Only few compulsory requirements from Law, but Guidelines can be derived from Law
* when hesitating, think in terms of free flow of information
Now back on over in Android world at Google HQ...
On 24 September 2009, Google issued a cease and desist letter to the modder Cyanogen, citing issues with the re-distribution of Google's closed-source applications within custom firmware.
Even though most of Android OS is open source, phones come packaged with closed-source Google applications for functionality such as the application store and GPS navigation.
Google asserted these applications can only be provided through approved distribution channels by licensed distributors. Cyanogen complied with Google's wishes and is continuing to distribute this mod without the proprietary software.
He has provided a method to back up licensed Google applications during the mod's install process and restore them when it is complete.
The exact same principle can be done with SE closed source apps and SE do provide the source code for their firmwares as part of the open source license. Anyone withing to check this out can simply head over to http://developer.sonyericsson.com/wportal/devworld/technology/android/ and start developing straight away. The source code, test keys and everything you need is either there or linked from there back to the places you need to be.
Semcboot security algorithms are not required and serve no benefit. The day that SE stop's supporting updates for this device, the same as they did with the Xperia X10 at 2.1 Eclair, your phone will be useless and stuck with older versions of Android.
If this is acceptable and your not bother by having no bootloader mod's, a hack to be able to change firmware that may someday soon be blocked and privacy issues built in as a matter of due course that you were not even correctly informed of, except for via a specialist forum (your looking at it), then good luck with your Arc, Neo or Play.. and I suspect that there is the real rationale here - Play.
Marlin DRM exists in the PlayStation 3 for the market and guide as it does in the PSP and also will in the Xperia Play. SE became rather unhappy when the master cryptographic key to the PS3 was discovered and distributed on mass over the internet (I have a t-shirt with the codes printed...) as it bypassed their protection ad allowed among other things, pirated games to play and unauthorized content to loaded, custom operating systems etc..
Sony Ericsson watched carefully at HTC and thought about how best to implement all of their technology in an extremely secure manor and this is the result. It may actually benefit end users, so far Sony have yet to state their side of the story and will be looking forward to seeing posts on anything relevant in this thread, for anyone interested in the subject and for anyone thinking of buying an Arc.
Wish I had of known this information before I purchased my x10 but is it such a perfect world?
Isn't the X10 hackable?
This forum here has tons of custom roms for the X10
http://forum.xda-developers.com/forumdisplay.php?f=617
Sorry for the stupid question. I'm new to SE and considering an Xperia arc.
yoyohere2 said:
Isn't the X10 hackable?
This forum here has tons of custom roms for the X10
http://forum.xda-developers.com/forumdisplay.php?f=617
Sorry for the stupid question. I'm new to SE and considering an Xperia arc.
Click to expand...
Click to collapse
No it is not. We cannot get a newer Linux kernel with new feature hooks that support functions like tether and hotspot and speed or security improvements. All the roms just overlay newer Android on top of the older kernel.
Other phones have been fully hacked and can get a newer kernel to support the newer Android without any mismatched functions. The devs here have to work hard retrofitting Android.
Sent from my X10a using XDA App
well the X2 wasnt hacked yet
This thread shows how to root a X10.
http://forum.xda-developers.com/showthread.php?t=711907
So the xperia arc and xperia x10 can be rooted?
Geohot recently announced that he bought a Xperia x10 and will be first in cue for the Xperia play. Keeping his success in mind I've got a good feeling about it.
http://www.youtube.com/watch?v=dXxw71oxjxs
Quite a few of us xda lurkers are itching to get root on our devices, but the DRM-debacle of the Sony phones has made many, including myself, hold off with unlocking the bootloader. Instead, we've put our hopes to new exploits that would allow root while keeping the bootloader locked, thus making it possible to keep all DRM functions in place, and also to restore the phone to factory conditions with the bootloader intact.
However, as Chainfire explains in the post below, the chances of any such exploit surfacing are slim. He says it's more important than ever to buy phones with unlocked bootloaders if we want to keep root.
Sadly, I'm afraid he's right and that the official bootloader unlock is the only way we'll be able to get root in the foreseeable future.
What do you guys think? Worth it or not?
Check out Chainfire's post on G+:
https://plus.google.com/113517319477420052449/posts/VxjfYJnZAXP
Fruktsallad said:
Quite a few of us xda lurkers are itching to get root on our devices, but the DRM-debacle of the Sony phones has made many, including myself, hold off with unlocking the bootloader. Instead, we've put our hopes to new exploits that would allow root while keeping the bootloader locked, thus making it possible to keep all DRM functions in place, and also to restore the phone to factory conditions with the bootloader intact.
However, as Chainfire explains in the post below, the chances of any such exploit surfacing are slim. He says it's more important than ever to buy phones with unlocked bootloaders if we want to keep root.
Sadly, I'm afraid he's right and that the official bootloader unlock is the only way we'll be able to get root in the foreseeable future.
What do you guys think? Worth it or not?
Check out Chainfire's post on G+:
https://plus.google.com/113517319477420052449/posts/VxjfYJnZAXP
Click to expand...
Click to collapse
Well it's @Chainfire talking, who are we to doubt him? I'm only waiting for a way to backup my TA-Partition (DRM keys), I wouldn't mind losing some features. Even tho I must agree that losing some camera quality is really annoying, but Android is pretty open source so I have no doubts that people will find something to reverse the algorithm loss or create their own.
And also when the occasion occurs that I need to send my device out for repair, that they don't refuse it due to an unlocked BL
I'm sure that's true in the long run, just not sure if it's true now.
It's economics. The security bugs are going to get fewer and further between, but they will arguably never be eradicated. You should expect it to take longer and longer to find new exploits, but I wouldn't bet a wooden nickel that there are no exploits left.
More likely, we will reach a point where the cost of finding an exploit is so great that they're no longer worth looking for to a critical mass of hackers.
On the bright side, the implementations get better all the time, and I see very little about my z3c that I would like to change if only I had root.
And I do think Sony should find a way to make the early rooters whole again. I feel terrible that so many people's $500 phones have been seriously degraded by a completely reversible software change.
Dsteppa said:
Well it's @Chainfire talking, who are we to doubt him? I'm only waiting for a way to backup my TA-Partition (DRM keys), I wouldn't mind losing some features. Even tho I must agree that losing some camera quality is really annoying, but Android is pretty open source so I have no doubts that people will find something to reverse the algorithm loss or create their own.
And also when the occasion occurs that I need to send my device out for repair, that they don't refuse it due to an unlocked BL
Click to expand...
Click to collapse
True, but as I'm sure you're aware, backing up the TA-partition requires said exploit to be found in order to get root. So I think it'll be a looong wait. [emoji20]
He still thinks root will be achievable in the early editions of Android L so I think it's safe to say root will arrive for this device under a locked bootloader, it will just take a bit longer than it has in the past to find an exploit.
Sent from my D5803 using XDA Free mobile app
This is really disheartening. It's kinda ironic that Sony, who in recent times has been raised in its support of the developer community of its phones, and even won XDA's OEM of the Year, has such a downer in its phones.
I know this doesn't work for everyone but I'm hopeful that the new AOSP L camera API will mean that AOSP custom roms have some native low light enhancement processing. Maybe...
Chances improve with new software so I t could happen with android L too.
pricey2009 said:
He still thinks root will be achievable in the early editions of Android L so I think it's safe to say root will arrive for this device under a locked bootloader, it will just take a bit longer than it has in the past to find an exploit.
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
Yup, but we're still looking at about five months wait considering Sony won't ship L until Q1 2015. Even then, there's no guarantee an exploit will be found.
Maybe I'm overly pessimistic about this. I do, however, have high hopes for the new camera API's regarding camera quality and post processing.
Personally, every day without root is a little painful, so I'll never last all those months. As soon as there are custom kernels available and a ROM like CM or PA, my locked bootloader goes bye-bye.
Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.
zxz0O0 said:
Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.
Click to expand...
Click to collapse
Let's hope Sony make or have made some little security mistakes.. To quote his post:
" Of course, this is all dependent on OEMs implementing everything exactly right. If a certain OEM doesn't protect one of their services correctly, then we can leverage that to launch the daemon without kernel modifications. While I'm fairly certain this will be the case for a bunch of devices and firmwares, especially the earlier L firmwares, this is not something you should expect or base decisions on."
Here's hoping they have missed something.
Sent from my GT-I9300 using XDA Free mobile app
pricey2009 said:
Let's hope Sony make or have made some little security mistakes.. To quote his post:
" Of course, this is all dependent on OEMs implementing everything exactly right. If a certain OEM doesn't protect one of their services correctly, then we can leverage that to launch the daemon without kernel modifications. While I'm fairly certain this will be the case for a bunch of devices and firmwares, especially the earlier L firmwares, this is not something you should expect or base decisions on."
Here's hoping they have missed something.
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Let's wait until January for the first android L release then :crying:
I've rooted two weeks ago and still enjoying the phone
zxz0O0 said:
Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.
Click to expand...
Click to collapse
This.
The post was mainly aimed at Android L...
Google hired one of our very own (Towelroot) and iPhone's pioneering hacker so it's going to get tougher. I hope they hired him only for NSA purposes.
That move by sony is just stupid. if they wanted to protect their code, why not store it into the camera firmware (referring to the camera algorithms)?
Why do they have to kill Miracast?
Obviously that is the other side of the medal. investments on security = far less exploits available. we are gonna wait a while, but as a developer I really really miss Xposed. Each time I look at my G2 a little tear drops.
No way I'm gonna root loosing DRM keys. The camera is already weak (to be honest I would be used a word beginning in shi but let's be polite) so I'm not in any way gonna make it worse.
zxz0O0 said:
Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.
Click to expand...
Click to collapse
Yes he does:
"As stated above, it seems for now that modifications to the kernel package are required to have root, we cannot attain it with only modifications to the system partition.
Combine that with a locked bootloader (and optionally dm-verity) and a device becomes nigh unrootable - exactly as intended by the security guys.
Exploit-based roots are already harder to do thanks to SELinux, and now because of the kernel requirements for persistent root, these exploits will need to be run at every boot. Exploits that make the system unstable (as many do) are thus out as well."
Then he goes on to say:
"Of course, this is all dependent on OEMs implementing everything exactly right. If a certain OEM doesn't protect one of their services correctly, then we can leverage that to launch the daemon without kernel modifications. While I'm fairly certain this will be the case for a bunch of devices and firmwares, especially the earlier L firmwares, this is not something you should expect or base decisions on. It is now thus more important than ever to buy unlocked devices if you want root.
It might also mean that every firmware update will require re-rooting, and OTA survival mode will be broken. For many (but far from all) devices we can probably automate patching the kernel package right in the SuperSU installer ZIP. We can try to keep it relatively easy, but updating stock firmwares while maintaining root is probably not going to work as easy and fast as it did until now."
zxz0O0 said:
Chainfire is talking about the su daemon and problems running it (on Android L). He does not say anything about a root exploit. It seems you misunderstood his post.
Click to expand...
Click to collapse
How can anything be a root exploit if it doesn't result in a functional su? I read Chainfire's post as Google making it impossible to elevate privileges from within Android, necessitating kernel level exploits which in turn will require unlocked bootloaders to install.
Once we get to where the bootloader has to be unlocked it's really not a root exploit anymore, is it?
michyprima said:
Why do they have to kill Miracast?
Click to expand...
Click to collapse
Because they don't want to support Miracast without HDCP. Remember that Sony is also a content provider. While that may be as annoying for a normal user as the degradation in camera quality, their approach actually still is developer friendly. Request a code - get full control over the device, at the cost of losing some functionality (software functionality). It's as simple as that. CM and other roms work perfectly fine on Xperia devices, and if you want to implement an equivalent camera algorithm, you're free to do so.
Iruwen said:
Because they don't want to support Miracast without HDCP. Remember that Sony is also a content provider. While that may be as annoying for a normal user as the degradation in camera quality, their approach actually still is developer friendly. Request a code - get full control over the device, at the cost of losing some functionality (software functionality). It's as simple as that. CM and other roms work perfectly fine on Xperia devices, and if you want to implement an equivalent camera algorithm, you're free to do so.
Click to expand...
Click to collapse
Can only agree to that. If you buy a Sony phone to act like a Sony phone (most people do!) then one should leave it as it has been delivered by Sony. If you can't agree to how it is, Sony gives you the option to unlock the BL and do whatever you want to do with the HW, but don't expect it to work/act as before. Personally, I have no issues with that at all.
On a different note, Linux/Android is comprised of x million lines of code. There're bugs in this code, there're bugs in the compiler, bugs in Java, bugs even in the Hardware etc. etc. There's no reason to believe (or fear) that Linux/Android would ever be perfect or non-vulnerable. Root will come, it's only a matter of effort and time...
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.
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.
This post over at the recovery/kernel dev thread seems to suggest that locked bootloader root and recovery might actually be impossible to achieve on the Z3+, so I've started to consider unlocking, having previously been adamant about not doing it. Losing the DRM keys is what prevents me, though.
Does anyone have a full list of lost features that go with the keys? I'm aware of some camera stuff, the Bravia engine, and noise cancellation.
Also, some users have reported at least partial restoration of DRM functions (not keys!) on previous Z devices, is that/will that be possible on the 3+?
+1 . I am in the same boat as op!
Sent from my Xperia Z3+
What features are lost? Anyone?
For me its not worth it
Some potential problems are as follows:
Bravia engine stuff and all that
Camera software is degraded especially low-light(can't confirm if this was changed with the z3+)
Sound EQ thingies and NC stops working
Drm Keys
Updates and stuff are not accepted anymore(OTA, PCC)
not worth it. additional to hasona's post :
-Xperia Lounge feature (eg: free movie)
- Screen mirroring
etc.
Currently i can live without root.
Adguard, Helium, will do the necessary needs atm.
And Sony is "committed to the openness of Android" or somesuch. I didn't know purposeful limiting counts as being committed.
monx® said:
not worth it. additional to hasona's post :
-Xperia Lounge feature (eg: free movie)
- Screen mirroring
etc.
Currently i can live without root.
Adguard, Helium, will do the necessary needs atm.
Click to expand...
Click to collapse
Currently I can live without root too, only thing I'm missing being not rooted is that I can't edit mixerpath to make my headphones louder,but still can live without that (but it would be cool to have it )
Sent from my E6553 using XDA Free mobile app
[NUMINIT] said:
This post over at the recovery/kernel dev thread seems to suggest that locked bootloader root and recovery might actually be impossible to achieve on the Z3+, so I've started to consider unlocking, having previously been adamant about not doing it. Losing the DRM keys is what prevents me, though.
Click to expand...
Click to collapse
Everything is impossible? says who? this will take time at least 9-10 months or 1 year to achieve root. Awesome devs at XDA always come with new exploits. :d
Don't unlock till then.
chesterr said:
Everything is impossible? says who? this will take time at least 9-10 months or 1 year to achieve root. Awesome devs at XDA always come with new exploits. :d
Don't unlock till then.
Click to expand...
Click to collapse
Once the z5 is out and they find a away for that, the z4 is sure to follow, with the same method.
Sent from my Xperia Z3+/Z4.
I have no issue with loosing that functionality to gain root..
If blocked updates are an issue, you can just flash newest ftf to get back to unrooted.. but right now, there is no way to get DRM back.
Personally I bought this phone for the express purpose of rooting it so I just assumed I'd loose the DRM keys from day 1.
[NUMINIT] said:
And Sony is "committed to the openness of Android" or somesuch. I didn't know purposeful limiting counts as being committed.
Click to expand...
Click to collapse
I think you've gotten Sony's intentions wrong mate. At least there's the option of unlocking the bootloader, albeit by loosing some phone functions. Most other companies they'd lock the bootloader away forever if unlocking meant compromising on proprietary software, or unlock their bootloader and not develop any customised functions as they'd be compromised if the bootloader got unlocked. At least Sony have a way for us to unlock the bootloader and also keep their IP safe. It's a compromise, and one that I'm happy to take.
Sony are one of the few companies that release their source code for their phones to the public. As far as I'm aware, the only other manufacturers only do so when they make a Nexus device and Google force them.
serrin85 said:
Personally I bought this phone for the express purpose of rooting it so I just assumed I'd loose the DRM keys from day 1.
I think you've gotten Sony's intentions wrong mate. At least there's the option of unlocking the bootloader, albeit by loosing some phone functions. Most other companies they'd lock the bootloader away forever if unlocking meant compromising on proprietary software, or unlock their bootloader and not develop any customised functions as they'd be compromised if the bootloader got unlocked. At least Sony have a way for us to unlock the bootloader and also keep their IP safe. It's a compromise, and one that I'm happy to take.
Sony are one of the few companies that release their source code for their phones to the public. As far as I'm aware, the only other manufacturers only do so when they make a Nexus device and Google force them.
Click to expand...
Click to collapse
You're right, I worded that more harshly than necessary. I was just so pissed that I bought an expensive phone I can't fully own without losing functions I paid for.
I do think it's silly to protect their software like this, though. Who would risk a massive lawsuit by stealing the IP that gets blocked with unlocking the BL?
Anyway, since you've unlocked, have you personally noticed much difference in everyday use?
Not worth.
My Z3+ wen crazy after some updates from Google (I think just after time when Google changed their logo). I was getting ~40-60 alerts "Google Services can't start" just after reboot. And they were jumping from time to time all the time. My phone was unable to reach google services so it was impossible to retrieve any updates, impossible to install or remove anything. This means impossible backup SMS/Call logs too (I didn't have any apps installed). Yeah I had Sony Xperia Transfer app, but this app will not let you transfer data to any other phone except SONY. Thank you SONY.
Decided perform factory reset. BUT, factory reset button from menu didn't worked. It simply did nothing. Was thinking bring phone to service, but then I need remove my mail accounts (I'm keeping job data there and I probably would be fired and get some 5-number-USD fine if I'd disclosure that info). Removing accounts didn't worked too.
Tried perform factory reset via adb, but no success. Decided boot into boot loader as in my good old nexus 4 and perform factory reset from there. Found some link on web that SONY gives you unlock code gently and you can do that yourself. What could be better, I thought?! Yeah, I've rebooted my phone, reset it and was happy again.
But after few days I've noticed that when I try zoom with my camera just a little, it simply freezes or performs 1 frame / 3-5 seconds. If I try record something - similar **** is happening. Quality is terrible too comparing what I had before. And then I found out about DRM...
So now I have one of top expensive phones with one of worst cameras.
[NUMINIT] said:
You're right, I worded that more harshly than necessary. I was just so pissed that I bought an expensive phone I can't fully own without losing functions I paid for.
I do think it's silly to protect their software like this, though. Who would risk a massive lawsuit by stealing the IP that gets blocked with unlocking the BL?
Anyway, since you've unlocked, have you personally noticed much difference in everyday use?
Click to expand...
Click to collapse
Well people port google apps all the time. Granted, no one's been sued yet, but there is a real likelihood that people are going to try it.
I don't think Sony are that worried about joe blow modder, but one of two things:
1) As part of their contract with the third party who they've leased the license from requires them to secure it (which may mean locking the bootloader)
2) Samsung or some other manufacturer would steal their code.
I'm just speculating, but Sony aren't making life difficult for everybody (and themselves) just for ****s and giggles.
I haven't noticed much difference, but then i didn't spend much time with it unlocked. I doubt loosing the drm keys will make the camera laggy.
serrin85 said:
Well people port google apps all the time. Granted, no one's been sued yet, but there is a real likelihood that people are going to try it.
I don't think Sony are that worried about joe blow modder, but one of two things:
1) As part of their contract with the third party who they've leased the license from requires them to secure it (which may mean locking the bootloader)
2) Samsung or some other manufacturer would steal their code.
I'm just speculating, but Sony aren't making life difficult for everybody (and themselves) just for ****s and giggles.
I haven't noticed much difference, but then i didn't spend much time with it unlocked. I doubt loosing the drm keys will make the camera laggy.
Click to expand...
Click to collapse
Would it not be possible to just use a different camera app or will that be the same?
serrin85 said:
Well people port google apps all the time. Granted, no one's been sued yet, but there is a real likelihood that people are going to try it.
I don't think Sony are that worried about joe blow modder, but one of two things:
1) As part of their contract with the third party who they've leased the license from requires them to secure it (which may mean locking the bootloader)
2) Samsung or some other manufacturer would steal their code.
I'm just speculating, but Sony aren't making life difficult for everybody (and themselves) just for ****s and giggles.
I haven't noticed much difference, but then i didn't spend much time with it unlocked. I doubt loosing the drm keys will make the camera laggy.
Click to expand...
Click to collapse
The camera is laggy as hell as per 5.0.2 anyway, so that's not an issue. I'm more worried about low-light shots. Unlocking absolutely ruined then on my Yuga.
Plus there are things such as the Bravia engine and noise cancellation which I really like
Is anyone willing to test this one on his UB?
http://forum.xda-developers.com/cro...deodex-xperia-z5-themes-home-widgets-t3207016
cjm1979 said:
Would it not be possible to just use a different camera app or will that be the same?
Click to expand...
Click to collapse
You can use a different camera app, but the Sony magic mojo (noise filter etc) is only found in the stock app. That is to say unlocking the bootloader nerfs the stock camera app, the camera hardware itself is untouched.
serrin85 said:
You can use a different camera app, but the Sony magic mojo (noise filter etc) is only found in the stock app. That is to say unlocking the bootloader nerfs the stock camera app, the camera hardware itself is untouched.
Click to expand...
Click to collapse
So if we had a camera app that does equivalent post-processing Sony's apps we would not lose any picture quality? Does this also mean that any 3rd party app that accesses the camera does not take advantage of any DRM-licensed functionality, and they will work exactly the same way after unlocking the BL?
steveeJ said:
So if we had a camera app that does equivalent post-processing Sony's apps we would not lose any picture quality? Does this also mean that any 3rd party app that accesses the camera does not take advantage of any DRM-licensed functionality, and they will work exactly the same way after unlocking the BL?
Click to expand...
Click to collapse
So I use 'A Better Camera' for taking pictures, as the stock app overheates the device incredibly fast. But if the stock sony camera app is working it's much faster than a third party app. But this is is only my own opinion, don't know, if that's always the case and if this depends somehow on the DRM key stuff. (Locked BL, using the 28.0.A.7.24 FW)