Related
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
Background:
Tablet Z is an amazing device. I have had a number of different Android devices with comparable specs but nothing has come close to this one in overall performance, durability, build, and stability. The question that I did not find an answer for and made me write this info piece is: what is the best stock ROM for this tablet that can offer the best overall stability and power consumption. Note that a lot of what follows are matters of opinion and personal preferences and you should probably tweak based on your specific needs. So first some basics.
Basics:
There is an empirical finding that the best performance is achieved from the ROMs that are available about six months to a year after the release of any given device and here is the justification. The device is initially shipped with the Android version available at the time of the release. This initial version is invariably buggy because the fast design cycles of these things do not allow a comprehensive test drive by the vendor. So the consumers report the bugs, they get patched, and about 6 months later everything is wrapped into the next version of Android and pushed as an update. This second ROM release is much more stable than the first one but still lacking a few things here and there, which brings us to the next major ROM that will fix most everything.
By this time we are 6 months to a year into the life of the product and the market is now seeing other devices with higher processing power and better specs. The Android releases at any given point in time are tweaked towards the expected performance of the devices that are available at that time. So the next update for your now-more-than-a-year-old device will have nicer features but it is geared towards other devices that are faster and better than yours. So now you upgrade to the third release and you will find that while all the initial bugs are gone the device is laggy and the battery goes down faster than it used to. Most devices don't have a straightforward procedure to downgrade to an older version (at least for the common user) and therefore you will just write this off as your device being too old and slow and then you will be likely convinced by a Sony salesperson to buy the next generation tablet and that is the end of that.
The key is to identify that sweet spot where the OS is stable and fast and tweak the performance there and NOT upgrade anymore. Let me say something about software upgrade while I have your attention. I have sadly found that a lot of people upgrade their phone/tablet OS without really knowing why they do it. Sometimes it almost looks like a fashion trend that since my neighbor is running his/her phone on Kitkat I must upgrade from Jellybean too. This often results in a slowdown of your system and sometimes even makes it impossible to do cool stuff such as rooting your device, because new updates close loopholes and vulnerabilities.
Xperia Tablet Z Stock Roms:
Before we get into that, let's mention the non-stock Roms such as AOSP and CM and their derivatives. There may be a compelling argument for certain cases where for example the vendor either heavily loads the device with bloatware that is difficult to remove or a custom Rom is needed to improve power or increase the performance by overclocking and whatnot. This is very true of some Samsung models with great hardware that are actually degenerated to slow devices with over-bloating and a little help from possessive phone operators like AT&T. However, this is not particularly true for Sony, or at least not yet. The Sony bloat is minimal and easy to remove and what Sony packs with the OS, such as multi-window, remote control, and Bravia engine, are in fact quite useful especially if you are using the device in a Sony ecosystem like with a big screen TV. Besides, Sony is very open-source friendly so there are not a whole lot of locked down features that you may need a custom ROM to get around. So I will limit this discussion to Sony's official Rom releases.
XTZ was initially shipped with 10.1.C.0.344 Android 4.1.2 in the US. Within a few months they upgraded it and if you like most people bought your tablet in the summer of 2013 it probably came with 10.1.C.0.370. This was to fix a touch sensitivity problem and improve WiFi. No update however is complete without limiting the ability of the user to root the device so Sony patched a vulnerability that allows the method of rooting you find inside the menus of Flashtool. Soon another vulnerability was discovered and a piece of code was written by Doomslord which would remain the only safe way to root XTZ until Towelroot was born. The update also removed the ability to choose the number of active cores, which was not the end of the world of course.
This release arguably has the best user interface which located the important touch keys on the bottom left and right sides of the screen, which is easy to operate when you grab the tablet with two hands. However, it had a few performance issues. For example, adding a weather widget would introduce a visible lag when swiping the home screen. It didn;t take long before users started nagging on different forums about how they are not running the latest Android version and how Sony should release it ASAP,... and Sony did.
Android 4.2.2 (10.3.1.C.0.136) removed the nice tablet UI. Soft button keys were now at the bottom center of the display with nothing on the left and right sides, which makes it awkward to grab the tablet with two hands and operate these keys at the same time. The notification area that was previously on the bottom right hand side would now be relocated to the top banner which resulted in a loss of screen real estate, and this pissed off a lot of users including yours truly. In all fairness it was not Sony's fault because this was a decision made by Google to unify tablet and phone interfaces beyond 4.2.2. Sony did their best to give something back (Quick Settings option in top notification bar) and mitigate the lost screen area (Semi-transparent bar in lockscreen). Then there were added features like multi-user support, ability to change the length of “preview time” after shooting a snap from camera, widgets on both homescreen and lockscreen,Video Unlimited movie app integration, updated media apps, my Xperia app to track the tablet in case it is lost, and official support 64 GB SD card.
The initial 4.3 release (10.4.B.0.577) changed the UI to a white theme that looks a lot like Xperia Z1 and Z Ultra: new improved smart camera app and new Xperia wallpapers (like Xperia Z1). A cool feature was added that allows the downloading of themes which change the navigation bar and status bar colors, and the soft keys icons as well. New keyboard app was added with one-hand keyboard settings. Also, a Windows Tethering option made it possible to pair the tablet with Windows 8.1. All welcome options which made most of us get over the grudge caused by the removal of the Tablet UI. Screen was calibrated for a brighter display and restricted profiles settings added more control of the multi-user feature.
The best feature which went unnoticed by many was the new version of Battery STAMINA Mode. Not that the older one needed any serious make-over but this one offered even a longer battery life. By now, almost all the lag observed in earlier versions were gone. For example, the weather widget would no longer self-update until the swiping was complete and this provided a significant smoothness in home display transitions. Finally, the 4.3 update 10.4.1.B.0.109 reduced the display flickering, improved battery life, shortened shutdown times, and fixed a problem which made it possible to use Bluetooth without losing WiFi.
Sometime in May of 2014 Sony released the long-awaited 4.4.2 Kitkat update (10.5.A.0.230) and this was when things started to go south. Sure, there where enhancements in camera app, ability to add emojis to messages, screenshots via the power menu, updates to Email, Calendar, and other apps, and good looking live wallpapers. But nothing could hide the fact that the tablet was now visibly slower and the battery would drain much faster. Sony admitted that the battery drain is a real problem and traced it to a buggy version of the Google services, which the user could uninstall or disable but that didn't make the update any faster.
The fact is, Xperia Tablet Z has a snapdragon S4 running at 1.5GHz, which from an antutu score perspective sets it at around the 20-21k mark. For comparison consider the Tablet Z2 with a 2.3GHz Snapdragon 801 with an antutu score in the 35000 range and that is really the type of system that the Sony Kitkat update should run on. That's why the tablet becomes so sluggish after the kitkat upgrade. The transitions are visibly slow and even if you disable live wallpapers and other things the settings menus will remain slow. In fact the antutu score after this upgrade drops sharply to around 18000.
Sony eventually released Kitkat 4.4.4 with 10.5.1.A.0.283 in late summer of 2014 and updated that a month or two later with a limited release of 10.5.1.A.0.292 in Nordic countries. These update are more fluid than 4.4.2 with much less lag in different programs. All Kitkat releases have been plagued by a sever battery drain due to a malfunctioning of Google Play services, which is resolved if you update this app to 5.2.08 after the firmware installation. 4.4.4 is still slower in Antutu scores compared to 4.3.
And the winner is...
4.4.4, followed by 4.3.
With the latest Kitkat update (4.4.4) I found that after patching the Google services and minimal debloating the tablet will last 78 days (more than two and half months) in standby. That is pretty impressive. See the screenshots (under Attached Thumbnails). So if you decide to go with 4.4.4, to get the most out of your battery:
1- Upgrade Google Play services to 5.2.08.
2- Go to settings:
Wifi -> Advanced -> Keep Wi-Fi on during sleep -> Never
Wifi -> Advanced -> Scanning always available -> off
Wifi -> Advanced -> Wifi optimization -> on
Power management -> Stamina Mode on and queue background data
3- Disable Google+ and Hangouts (and play store, if you don't use it). I suggest turning off both "Remotely locate" and "allow remote lock" options under Android device manager in Google settings.
4- Uninstall (via Titanium backup) or remove from /system/app and priv-app SonyEntrance.apk and UpdateCenter.apk. If your tablet is wifi only do the same for SemcTelephonyProvider.apk, Stk.apk, phone-usage.apk, and SemcPhone.apk.
The 4.3 update 10.4.1.B.0.109 provides a good battery life too. In standby it can last about 55 days without a recharge (see 1.jpg and 2.jpg). In camparision, the 4.4.2 release lasts about 40-45 days under similar testing conditions. To install 4.3 you can either use this long procedure: http://forum.xda-developers.com/showthread.php?t=2772943 which gives you a pre-rooted 4.3, with the added benefit of a nice recovery image, or flash a stock ftf and root it with towelroot. Either way you need to learn and use flashtool because this update is no longer available through Sony's update channels. If you decide to go with 4.4.4, to get the most out of your battery:
1- Root and disable non essential programs either using Titanium backup or other methods that require a knowledge of the terminal emulator. On an SGP311 For 4.3 what you typically disable is the following (the list is different for the LTE version!):
B2bCustInstaller, com.sonyericsson.startupflagservice, Crackle, Facebook, FBiX Post Viewer, Gmail (and use the stock Email client if you have want to check your gmail), Google Play Books/Games/Magazines/Movies/Music, Google+ and Hangout, Let's start PSM, McAfee Security, Mobile Data, Mobile Network, Configuration, Netflix, POBox Touch (unless you use Japanese keyboard), Reader, Sim Lock, Sim Toolkit, Social Engine, Socialife, Twitter, Video Unlimited, Wisepilot (which doesn't work anyway!), Xperia AppShare, Xperia Calendar Sync, Xperia Friends' music, Xperia Music Likes, Xperia Social Engine Photos/Sharing (all of them), Xperia Chinese keyboard, Xperia with Facebook and Twitter.
2- Then go to settings:
Wifi -> Advanced -> Keep Wi-Fi on during sleep -> Never
Power management -> Stamina Mode on.
I tried programs like Juice Defender but it seemed that in the presence of Sony's Stamina mode none of that is necessary.
One last detail. As you can see in the picture mobile data is still burning 3% although I froze/disabled it in Titanium. The reason is that while freezing an app prevents it from starting at boot-up, the binary is still in the storage and other apps can still invoke it. If you want that portion to go down to zero you will need to uninstall the app in Titanium (or delete/rename the app to disable it, which requires knowledge of the terminal emulator.)
Update: Sony released 5.0.2 with 10.6.A.0.454 in late spring of 2015 and 5.1.1 in September. The standby battery life is nowhere near the latest 4.4.4 or 4.3.
So that is it folks. Give it a try and see it for yourself. At the end of the day, regardless of the firmware, this is an awesome tablet which will still be around after all of its peers are gone and forgotten.
Thanks for your reply. In general i agree with you that the most stable and responsive (fluid) was 10.4.1.B.0.109 on SGP311/312 and 10.4.1.B.0.101 on SGP321. However you can perform fresh install of 10.5.A.0.230 KitKat, make some performance-wise adjustments/remove-freeze bloatware and you will have practically the same performance. As i did it, i can't distinguish between 4.4 and 4.3 in performance at least visually, however it shows a little bit less score in Antutu, 21500 for JB, 20800 for my adjusted KK, but it doesn't really matter.
This is a great post. Thank you. I noticed the performance since installing KitKat has been sluggish too. I haven't tried optimizing it much, haven't had time, but I'm going to try that before downgrading to 4.3. The animations and transitions are so sluggish its annoying. Makes me want a new tablet to be honest heheh.
Great post! Although I'm still loving 4.4. I really missed immersive mode since I've had Nexus phones.. Anyway after fixing the settings app the other 'glitches' in kitkat weren't noticeable. Battery life's awesome since most of the not needed things are disabled/uninstalled.
I get 3-4 days with moderate to heavy use with about 9-10 hours of screen on time. It's really an indoor tablet for me so the brightness can be as low as minimum with no impact on visibility.
I bought my tablet without thinking 6 months ago but I honestly have 0 regrets. It's a truly amazing multimedia device.
Too bad Cyanogenmod 11 is in a poor state with still buggy nightlies and no proper milestone releases...
And I agree Kitkat feels a bit sluggish on the tablet, especially when you compare it to a Snapdragon 801 phone.
Dzhedaj said:
Too bad Cyanogenmod 11 is in a poor state with still buggy nightlies and no proper milestone releases...
And I agree Kitkat feels a bit sluggish on the tablet, especially when you compare it to a Snapdragon 801 phone.
Click to expand...
Click to collapse
Snapdragon itself it a way way more faster chip. Also Sony don't really bother with OS optimizations for old devices.
As per my opinion since i updated .233 update via flashtool that Lag and sluggishness is gone perfectly
http://forum.xda-developers.com/xperia-tablet-z/general/ftf-4-4-10-5-0-233-sgp321-3at-t2789187
Alongwith a little mod with beats audio improves the internal speakers upto 100dbi more who feels tab internal speaker volume is low.
Update to .233 and enjoy the tab to its full capacity
Sent from my GT-N7100 using Tapatalk 2
Thanks for the write-up.
I'm a noob that's researched this to death, and this adds some clarity to whats becoming more murky as I read.
Will probably try to optimize 4.4.2 1st before attempting your link (I'm hoping a couple of other posters on this thread can point me in the right direction - question forthcoming but could you clarify 'or flash a stock ftf and root it with towelroot'? Sorry for the noob question, but 'root after flash' and 'what specific stock ftf' has me lost. Thanks
---------- Post added at 08:12 PM ---------- Previous post was at 08:09 PM ----------
Rootk1t said:
Thanks for your reply. In general i agree with you that the most stable and responsive (fluid) was 10.4.1.B.0.109 on SGP311/312 and 10.4.1.B.0.101 on SGP321. However you can perform fresh install of 10.5.A.0.230 KitKat, make some performance-wise adjustments/remove-freeze bloatware and you will have practically the same performance. As i did it, i can't distinguish between 4.4 and 4.3 in performance at least visually, however it shows a little bit less score in Antutu, 21500 for JB, 20800 for my adjusted KK, but it doesn't really matter.
Click to expand...
Click to collapse
Do you have a link to the method by which you optimize?
Thanks
gmore1 said:
Thanks for the write-up.
I'm a noob that's researched this to death, and this adds some clarity to whats becoming more murky as I read.
Will probably try to optimize 4.4.2 1st before attempting your link (I'm hoping a couple of other posters on this thread can point me in the right direction - question forthcoming but could you clarify 'or flash a stock ftf and root it with towelroot'? Sorry for the noob question, but 'root after flash' and 'what specific stock ftf' has me lost. Thanks
---------- Post added at 08:12 PM ---------- Previous post was at 08:09 PM ----------
Do you have a link to the method by which you optimize?
Thanks
Click to expand...
Click to collapse
i installed 4.4.4 which is already optimized by sony. Antutu benchmark +2000 scores comparing to 4.4.2:victory:
Rootk1t said:
i installed 4.4.4 which is already optimized by sony. Antutu benchmark +2000 scores comparing to 4.4.2:victory:
Click to expand...
Click to collapse
You've given me even more homework, but I greatly appreciate the response
I currently have a stock (unlocked/unrooted) Tab Z and if I understood the 4.4.4 posts I've read, the best method to keep root(towelroot for 4.4.2+older) and files is install via OTA which requires an unlocked bootloader, which requires a code from Sony so.... a brief summary of steps to keep my unit as 'open/versatile' as possible here would be....
1:Get code from Sony
2:Unlock bootloader
3:Install Flashtool and root via towelroot (the order here is not important?)
4:Back up files
5:Install 4.4.4 via OTA
Done?
And then I'm left to be able to move back and/or install older firmware?
If this is a PITA to answer, I understand - appreciate any help
gmore1 said:
You've given me even more homework, but I greatly appreciate the response
I currently have a stock (unlocked/unrooted) Tab Z and if I understood the 4.4.4 posts I've read, the best method to keep root(towelroot for 4.4.2+older) and files is install via OTA which requires an unlocked bootloader, which requires a code from Sony so.... a brief summary of steps to keep my unit as 'open/versatile' as possible here would be....
1:Get code from Sony
2:Unlock bootloader
3:Install Flashtool and root via towelroot (the order here is not important?)
4:Back up files
5:Install 4.4.4 via OTA
Done?
And then I'm left to be able to move back and/or install older firmware?
If this is a PITA to answer, I understand - appreciate any help
Click to expand...
Click to collapse
Be AWARE !
Before unlocking bootloader BE SURE TO BACK UP YOUR TA PARTITION OR YOU WILL LOOSE DRM LICENCE KEYS FOREVER !!!
Google "Sony DRM TA backup" to find more information.
gmore1 said:
You've given me even more homework, but I greatly appreciate the response
I currently have a stock (unlocked/unrooted) Tab Z and if I understood the 4.4.4 posts I've read, the best method to keep root(towelroot for 4.4.2+older) and files is install via OTA which requires an unlocked bootloader, which requires a code from Sony so.... a brief summary of steps to keep my unit as 'open/versatile' as possible here would be....
1:Get code from Sony
2:Unlock bootloader
3:Install Flashtool and root via towelroot (the order here is not important?)
4:Back up files
5:Install 4.4.4 via OTA
Done?
And then I'm left to be able to move back and/or install older firmware?
If this is a PITA to answer, I understand - appreciate any help
Click to expand...
Click to collapse
no! no need to unlock bootloader to root device and get OTA.
Rootk1t said:
no! no need to unlock bootloader to root device and get OTA.
Click to expand...
Click to collapse
GretaLewd said:
Be AWARE !
Before unlocking bootloader BE SURE TO BACK UP YOUR TA PARTITION OR YOU WILL LOOSE DRM LICENCE KEYS FOREVER !!!
Google "Sony DRM TA backup" to find more information.
Click to expand...
Click to collapse
OK.
I won't be 'developing' anytime soon, so no need to unlock. I just thought in order to access anything newer than 4.4.2 OTA from Sony would require it.
Thank you both and sorry again for the ?'s, but this has been WAY more involved than the days of rooting my Photon
Will continue my research on OTA 4.4.4.
---------- Post added at 12:33 PM ---------- Previous post was at 11:42 AM ----------
OK,
No 4.4.4 for SGP312 yet so I guess just be patient and make sure I'm rooted and backed up?
Any link for optimizing in the meantime still appreciated - many searches and I can't find anything.
gmore1 said:
No 4.4.4 for SGP312 yet so I guess just be patient and make sure I'm rooted and backed up?
Any link for optimizing in the meantime still appreciated - many searches and I can't find anything.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe...oot-4-4-4-kitkat-sgp311-10-5-1-0-283-t2875885
http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377
Rootk1t said:
http://forum.xda-developers.com/xpe...oot-4-4-4-kitkat-sgp311-10-5-1-0-283-t2875885
http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377
Click to expand...
Click to collapse
OK
I was aware of 4.4.4 via FT and PC, but based on a post I had read in another thread, thought only OTA would allow one to maintain root after 4.4.2...
I should have read further into that thread.
This should do it -Thanks again Rootk1t
Can I just clarify... in the first post, it says "On an SGP311 what you typically enable is the following..." Do I take it that should say disable, not enable?
I also noticed that I don't have B2bCustInstaller, but I do have B2bCertInstaller and B2bCustomSetupWizard. Are either of those two, the same as you mentioned?
This latest update (10.5.1.A.0.283) has introduced some annoyances with video playback, so I am trying to get rid of useless apps etc... in the hope that one of them clears things up.
LeeC22 said:
Can I just clarify... in the first post, it says "On an SGP311 what you typically enable is the following..." Do I take it that should say disable, not enable?
I also noticed that I don't have B2bCustInstaller, but I do have B2bCertInstaller and B2bCustomSetupWizard. Are either of those two, the same as you mentioned?
This latest update (10.5.1.A.0.283) has introduced some annoyances with video playback, so I am trying to get rid of useless apps etc... in the hope that one of them clears things up.
Click to expand...
Click to collapse
1- Thanks for pointing out the typo. I fixed it in the text.
2- You don't see B2bCustInstaller because Sony disables it by default, but it is still in your system. Leave the other two apps be. They will be dormant.
3- What annoyances are you referring to? I may be able to help if you are more specific.
najoor said:
1- Thanks for pointing out the typo. I fixed it in the text.
2- You don't see B2bCustInstaller because Sony disables it by default, but it is still in your system. Leave the other two apps be. They will be dormant.
3- What annoyances are you referring to? I may be able to help if you are more specific.
Click to expand...
Click to collapse
My tablet is primarily a video playback device for the music videos I collect. Before this update, video playback was smooth, after this update, it's just not quite right. What makes me think it's the update, is that I use MX Player Pro, and the video playback isn't smooth in that either. The Sony Movies app is all over the place with playback. One update it's fine, next update it's bad, then it might be okay again, but this update it's just not quite right. It was during a bad period that I decided to get MX Player Pro, which seemed much better... but now it's suffering the same problem.
To most people, it would probably look fine, but as a graphic artist, I find I'm very susceptible to the slightest irregularity in playback. As it affected two players, I presumed that it was a background service or something that was affecting resources enough to affect video decoding.
I would also just like to say thanks for providing that list. My tablet used to take just over an hour to recharge 10% of the battery life back. In just over 6 hours last night, it recharged 80%. So that's a major plus point in my book, so thank you for your efforts. :good:
LeeC22 said:
My tablet is primarily a video playback device for the music videos I collect. Before this update, video playback was smooth, after this update, it's just not quite right. What makes me think it's the update, is that I use MX Player Pro, and the video playback isn't smooth in that either. The Sony Movies app is all over the place with playback. One update it's fine, next update it's bad, then it might be okay again, but this update it's just not quite right. It was during a bad period that I decided to get MX Player Pro, which seemed much better... but now it's suffering the same problem.
To most people, it would probably look fine, but as a graphic artist, I find I'm very susceptible to the slightest irregularity in playback. As it affected two players, I presumed that it was a background service or something that was affecting resources enough to affect video decoding.
I would also just like to say thanks for providing that list. My tablet used to take just over an hour to recharge 10% of the battery life back. In just over 6 hours last night, it recharged 80%. So that's a major plus point in my book, so thank you for your efforts. :good:
Click to expand...
Click to collapse
I'm not sure you can fix this by just disabling background processes. Sony's Kitkat release is slower at its core than 4.3 and that can be seen and quantified in an Antutu benchmark. Give it your best shot but your best bet is to downgrade to 4.3.
najoor said:
I'm not sure you can fix this by just disabling background processes. Sony's Kitkat release is slower at its core than 4.3 and that can be seen and quantified in an Antutu benchmark. Give it your best shot but your best bet is to downgrade to 4.3.
Click to expand...
Click to collapse
You're right, I disabled loads of stuff last night, and the problem frustratingly remains.
I'd ideally downgrade to 4.2, because I think 4.3 is where Sony removed the screenshot option (before cunningly adding it back in 4.4 as a "new feature"), isn't it? I use that a lot, because my eyes aren't that good, and when you hit a website that blocks pinch-zooming, or you get an app that has text that is too small, like Google Earth, I frequently need to capture the screen and zoom in.
Of course, the problem with this solution is that downgrading to a specific rom version, for a specific version of the tablet, in a specific territory, is not that simple. I'll have to spend some time collecting the required files and instructions, then wait for a good day (mentally), to give it a go.
Woke up this morning to my Galaxy Camera 2 claiming it was downloading a new software update (~130mb). Of course, there's no mention anywhere in the update process for what is included in this update, but I can definitely tell you that it's not Kitkat (sadly). Unfortunately, I didn't check version numbers prior to accepting the update (sorry), but here's the version numbers after the update:
Build Number:
JSS15J.GC200XXUCNK4
Kernel version:
3.0.31-2807772
[email protected] #1
Sat Nov 29 15:55:43 KST 2014
That's the same Build Number we've had since like April 2014, but the kernel definitely seems to have been updated. Maybe they finally fixed the loss of Google account settings issue??? I appreciate updates, but I really wish they would inform the customer better on what these updates fixed.
Ironically, for the first time in a long time, my Camera 2 had lost its Google Account settings when I turned it on this morning....haha.
Oh, I reside in Florida, USA. Not sure who else in the world is receiving the update, but according to SamMobile.com the Camera 2 update was hitting other locations around the globe starting 12/18/2014, but there's no mention of it hitting the USA at all.
Need to know if it's root able.
cantenna said:
Need to know if it's root able.
Click to expand...
Click to collapse
As long as this fixes the problem of losing the Google account, I have no reason to root the camera. Plus, I still have this weird hope that Samsung will actually release a Kitkat update for it (haha), and with there basically being ZERO development for this device on XDA, I don't want to be stuck not able to update.
Well, it's been almost a week since this update and it's also been a week of heavy Camera 2 use with the holidays. I haven't lost Google settings even once.
Thus far my camera hasn't lost my Google accounts, and by now it surely would have happened
Sent from my Nexus 9 using Tapatalk
internetpilot said:
As long as this fixes the problem of losing the Google account, I have no reason to root the camera. Plus, I still have this weird hope that Samsung will actually release a Kitkat update for it (haha), and with there basically being ZERO development for this device on XDA, I don't want to be stuck not able to update.
Click to expand...
Click to collapse
Eh...
I didn't waste my time getting the Galaxy Camera 2, just got the One.
I understand your stress though.
Someone needs a swift kick in the butt so we can get development going for both devices.
Sent from my LG-P920 using XDA Free mobile app
hmm am glad to see an uphdate still, though im really really hoping for lollipop which should allow RAW access for the camera.
mark2410 said:
hmm am glad to see an uphdate still, though im really really hoping for lollipop which should allow RAW access for the camera.
Click to expand...
Click to collapse
Assuming you do get it, could we transfer it over to the Galaxy Camera One, Wi-Fi Edition?
I don't like to be the rude one. But at this point, someone has to help root the Wi-Fi Only version, and come up with a Custom Recovery.
Not only this, but we need to see Devs, but we've got people sitting and pointing fingers instead.
I wanna see a ROM putting us all on a better version, or something more come to all the cameras.
Sent from my LG-P920 using XDA Free mobile app
hmm, really wouldnt have thought so, its probably possible given the hardware similarities but i think that given the camera 1 and 2 have been such unpopular devices they havent warranted their own listings here i wouldnt hold me breath. the key to getting a ROM for a device is someone who is techy enough to do wanting to use one. i for one might like the camera but i would have absolutely no clue how to make a rom for it.
hmm surely there must be a dev out there who likes photos.
mark2410 said:
hmm, really wouldnt have thought so, its probably possible given the hardware similarities but i think that given the camera 1 and 2 have been such unpopular devices they havent warranted their own listings here i wouldnt hold me breath. the key to getting a ROM for a device is someone who is techy enough to do wanting to use one. i for one might like the camera but i would have absolutely no clue how to make a rom for it.
hmm surely there must be a dev out there who likes photos.
Click to expand...
Click to collapse
The Camera 2 has gotten support, but not what it needs.
And honestly, Developing ROMs isn't too difficult, I just don't have the time for it.
Sent from my EK-GC110 using XDA Free mobile app
The reason why you would want to root the camera is because you can instal Link2sd and Foldermount, with these two apps you can install theoretically 128G of apps
cantenna said:
The reason why you would want to root the camera is because you can instal Link2sd and Foldermount, with these two apps you can install theoretically 128G of apps
Click to expand...
Click to collapse
Why would anyone want to put 128GB of apps on a camera? I mean, a tablet or phone, okay...but a camera? I just don't really see the practical purpose for that. The biggest storage hog on my tablet/phone is music and movies, and neither of those require the device to be rooted to store them on the external SD card.
Again, with the way Samsung is really clamping down on not allowing OTA's to be delivered to even just rooted devices, and with the basically non-existent development support for this device, I won't be rooting it until I'm 100% certain that there's no OTA update coming for it, and even then I would only root it if someone put out a reliable custom Kitkat or Lollipop ROM for it. Honestly, if Samsung won't update it, then I'm really not holding my breath that some 3rd-party dev ever will.
Ouya-XD said:
The Camera 2 has gotten support, but not what it needs.
And honestly, Developing ROMs isn't too difficult, I just don't have the time for it.
Click to expand...
Click to collapse
It would be a heckuva lot easier to port a Camera 2 ROM over to the Camera 1 (rather than develop a ROM from scratch for either camera model), but even that hasn't been done. I don't think there's ever going to be any original development on these devices (like a CM11 or CM12). Developing ROMs isn't terribly difficult, but it's not easy either, especially not on a device that is so driver dependent like these cameras are. Just about every Android device I've owned (phone or tablet) has problems with the camera not working in some way (if not completely) on any original development project. What good is a camera with the latest Android OS if it causes the camera function not to work or even not work reliably?
I think we need to face it, folks -- these cameras are pretty much as-is. At best we're highly dependent on whatever Samsung gives us.
Nope, I disagree. Rooting this camera is a damn good idea for so many reasons. Most tablet or phone dont have a miro HDMI, My camera, I can install apps without deleting and its not just a camera, its an android device by Samsung that comes with a micro hdmi and with a Bluetooth mouse and keyboard, well if you have ever thought about buying an android TV box, this is a better replacement, it performs much better than majority on the market.
And yes I agree that stock ROMs with stock drivers perform better but asop base ROM do perform much better in terms of speed in gaming and applications. What about a multi ROM solution to allow you multi-boot i.e. boot stock from internal nand and asop lollipop from from external SD, now that would be a sweet setup!
hmmm i get your point but for me, the camera is a camera. ive got a tablet for tablety things, a phone for phoney things so what i want is camera focused and to have dropbox autoupload everything nicely.
thats the anly reasen im so fussed that i want it to get lollipop as it should then get RAW capabilities. while i realise it may not happen i will vote with my wallet. this is my first real samsung device (galaxy nexus doesnt count) and while i love oled screens and removable batteries if samsung abandon the camera, well i will abandon them. its really that simple, if they wont support devices going forward then i wont buy any other android devices from them.
if only google put out a Nexus Camera.
NK4 and rooting
I just finished the upgrade to NK4. I was trying to keep root through survival mode in Superuser Pro, but I ended up having to reroot. The upgrade via kies took about a hour. I attempted to re-establish root via Superuser but was unable to do so. I ODIN'ed the CF-autoroot onto the camera and reinstalled Superuser. I now have a NK4 rooted camera.
Since the discussion seems to have shifted to the rational for rooting, here's my take. First, it should be noted that root <> custom recovery. We do not have custom recovery for the GalCam2, so installing alternative ROM's, if available is not an option. So, why root? For me, it's Xposed modules; specifically pie controls(mmmm, pie). I've had several digital cameras over the years. In fact, when I bought this camera, I had a year old samsung camera. Why this camera? It's android, so I can to many things that would be not be possible on other cameras in this price range, like say using different camera apps.
So, if you're rooted on NC2, fear not. The water's OK over here on NK4.
cantenna said:
Nope, I disagree. Rooting this camera is a damn good idea for so many reasons. Most tablet or phone dont have a miro HDMI, My camera, I can install apps without deleting and its not just a camera, its an android device by Samsung that comes with a micro hdmi and with a Bluetooth mouse and keyboard, well if you have ever thought about buying an android TV box, this is a better replacement, it performs much better than majority on the market.
Click to expand...
Click to collapse
Well, of course you can disagree, but I still think you're stretching your camera well beyond practical purpose. Cameras are quirky enough on their own (especially ones with Android OS) -- it's probably not a good idea to use it so much for non-photography purposes because when you wear it out from overuse with all these extraneous functions you're not just going to be out an Android TV device -- you're going to be out a $400 camera. Android TV boxes can be had for as cheap as US$25 and are practically disposable at that price.
Incidentally, I have a HDMI dongle (that uses a standard, readily available fullsize HDMI plug/cable) that I use on my Galaxy Note 2 phone and/or my Galaxy Note 10.1 2014 tablet all the time (typically when on vacation watching movies on the hotel TV). Not to mention $30 Chromecast can be used wirelessly. All of this without overusing my $400 camera, so that the next time I want to use my camera it won't have a low battery, scratched up screen, or otherwise screwed up or acting quirky from rooting it.
cantenna said:
And yes I agree that stock ROMs with stock drivers perform better but asop base ROM do perform much better in terms of speed in gaming and applications. What about a multi ROM solution to allow you multi-boot i.e. boot stock from internal nand and asop lollipop from from external SD, now that would be a sweet setup!
Click to expand...
Click to collapse
Again, it's all about what's your priority purpose for this device. I bought this device to use as a internet connected camera -- I didn't buy it for playing games or running non-photography related apps. I don't want to have choose which OS I'm booting to....I just want to turn the camera on, take some pics, and be able to immediately upload them somewhere. As long as that's working, then in my world there's really no need to actively look for alternative solutions that are just going to potentially mess that simple process up.
Again, there's a reason why I'm here on XDA -- I've rooted (and usually ROMed) every other Android device I've owned. I'm even currently running CM11 on my Galaxy Note 2 at the expense of losing some of the S-pen features because it runs so much faster that it's like I got a completely new phone. But I just don't see any reason for rooting (or especially ROMing) the Camera 2.
10amla said:
Since the discussion seems to have shifted to the rational for rooting, here's my take. First, it should be noted that root <> custom recovery. We do not have custom recovery for the GalCam2, so installing alternative ROM's, if available is not an option. So, why root? For me, it's Xposed modules; specifically pie controls(mmmm, pie). I've had several digital cameras over the years. In fact, when I bought this camera, I had a year old samsung camera. Why this camera? It's android, so I can to many things that would be not be possible on other cameras in this price range, like say using different camera apps.
Click to expand...
Click to collapse
That's actually very good to know for future reference that NK4 is rootable. That's likely the last update we'll see for this camera knowing Samsung.
I actually don't always use a custom recovery on my Samsung devices. Since most root methods, ROMs, and even the recoveries themselves are flashed via Odin, there's really not a pressing need for a custom recovery. I've even encountered a lot of quirkiness with most custom recoveries (Philz, CWM, TWRP) when it comes to Nandroid backups (especially reliable restores), so I never rely on them and instead just reflash the ROM, allow Google to restore system data, and then restore personal apps/data with TitaniumBackup. Plus, even if you're rooted, as long as you have the stock recovery you can USUALLY take any OTA updates. I emphasize USUALLY because my Note 10.1 2014 Ed tablet is rooted but running stock recovery and the latest bug-fix update will not flash because they claim my tablet has been modified.
I guess I've never felt the need for pie controls because I haven't used the stock launcher on any Android device I've ever owned. The Camera 2 camera app interface is already pretty sweet with the on-screen dial menus. Like I said above, I'm not just globally adverse to rooting (far from it), but I just have yet to find any reason to root this camera, especially now that the latest update seems to have corrected the stupid vanishing Google Account settings issue.
Now, if someone ever comes up with a fully functioning Lollipop ROM for this camera, you'll quickly see me singing a different tune, but until then....
internetpilot said:
Well, of course you can disagree, but I still think you're stretching your camera well beyond practical purpose. Cameras are quirky enough on their own (especially ones with Android OS) -- it's probably not a good idea to use it so much for non-photography purposes because when you wear it out from overuse with all these extraneous functions you're not just going to be out an Android TV device -- you're going to be out a $400 camera. Android TV boxes can be had for as cheap as US$25 and are practically disposable at that price.
Incidentally, I have a HDMI dongle (that uses a standard, readily available fullsize HDMI plug/cable) that I use on my Galaxy Note 2 phone and/or my Galaxy Note 10.1 2014 tablet all the time (typically when on vacation watching movies on the hotel TV). Not to mention $30 Chromecast can be used wirelessly. All of this without overusing my $400 camera, so that the next time I want to use my camera it won't have a low battery, scratched up screen, or otherwise screwed up or acting quirky from rooting it.
Again, it's all about what's your priority purpose for this device. I bought this device to use as a internet connected camera -- I didn't buy it for playing games or running non-photography related apps. I don't want to have choose which OS I'm booting to....I just want to turn the camera on, take some pics, and be able to immediately upload them somewhere. As long as that's working, then in my world there's really no need to actively look for alternative solutions that are just going to potentially mess that simple process up.
Again, there's a reason why I'm here on XDA -- I've rooted (and usually ROMed) every other Android device I've owned. I'm even currently running CM11 on my Galaxy Note 2 at the expense of losing some of the S-pen features because it runs so much faster that it's like I got a completely new phone. But I just don't see any reason for rooting (or especially ROMing) the Camera 2.
That's actually very good to know for future reference that NK4 is rootable. That's likely the last update we'll see for this camera knowing Samsung.
I actually don't always use a custom recovery on my Samsung devices. Since most root methods, ROMs, and even the recoveries themselves are flashed via Odin, there's really not a pressing need for a custom recovery. I've even encountered a lot of quirkiness with most custom recoveries (Philz, CWM, TWRP) when it comes to Nandroid backups (especially reliable restores), so I never rely on them and instead just reflash the ROM, allow Google to restore system data, and then restore personal apps/data with TitaniumBackup. Plus, even if you're rooted, as long as you have the stock recovery you can USUALLY take any OTA updates. I emphasize USUALLY because my Note 10.1 2014 Ed tablet is rooted but running stock recovery and the latest bug-fix update will not flash because they claim my tablet has been modified.
I guess I've never felt the need for pie controls because I haven't used the stock launcher on any Android device I've ever owned. The Camera 2 camera app interface is already pretty sweet with the on-screen dial menus. Like I said above, I'm not just globally adverse to rooting (far from it), but I just have yet to find any reason to root this camera, especially now that the latest update seems to have corrected the stupid vanishing Google Account settings issue.
Now, if someone ever comes up with a fully functioning Lollipop ROM for this camera, you'll quickly see me singing a different tune, but until then....
Click to expand...
Click to collapse
Stretching beyond practice purpose is what makes android, android. Samsung makes good hardware, this camera will never fail from overuse and $25.00 android boxes perform like $25.00 android boxes.
I also do not use the stock launcher on any of my Samsung devices. I use lightning launcher on the camera(as well as my notes). The reason I like pie controls is that you gain extra screen space when you're using the launcher(no nav bar). So far, that's my only use of root, that could change in time; but not having custom recovery makes me very cautious in installing addition items.
cantenna said:
Stretching beyond practice purpose is what makes android, android. Samsung makes good hardware, this camera will never fail from overuse and $25.00 android boxes perform like $25.00 android boxes.
Click to expand...
Click to collapse
If you think a multi element autofocus mechanical extending zoom lens and an electronic shutter are never going to fail, then you better start preparing yourself for disappointment in about 2 years. LOL.
My three $25 AndroidTV boxes have been working great for years, running Netflix and Amazon Prime video since day one that I bought them. They're also running Kitkat even though they started out on Gingerbread.
10amla said:
I also do not use the stock launcher on any of my Samsung devices. I use lightning launcher on the camera(as well as my notes). The reason I like pie controls is that you gain extra screen space when you're using the launcher(no nav bar). So far, that's my only use of root, that could change in time; but not having custom recovery makes me very cautious in installing addition items.
Click to expand...
Click to collapse
I'm pretty sure that all of my Samsung devices have been rooted and ROMed using Odin. My first Android device was a HTC EVO 4G, which solely used custom recoveries (unless you just like going back to the dark years of ADB), so the first couple of times I asked devs for a flashable zip, I was all but excommunicated from the XDA forum for such blasphemy. Everyone here seems to do just about everything via Odin, so I don't really sweat not having a custom recovery. Most things that can go wrong (bootloops, soft-bricks, etc.) when mucking around flashing devices are solved via Odin anyway.
Hi all,
I made this post to enhance your experience with the Z3C. Indeed I thought since a few days that I was going to throw away my phone because of multitasking. This issue is not clear at all and not all people seemed to be touched by this. However I am, definitely.
This is my experience on lollipop: I can’t have 5 apps running at the same time, even if they’re very light. For example if I’m listening to music and using chrome, everytime I switch to another app, it needs to start again. It gets really annoying when I’m using some apps at the same time and I lose lots of time.
My first idea was to switch to another phone (even if I love the Z3C for other qualities like battery life or how compact it is) but this issue seems to touch every phone except HTC’s but I’m not happy with their battery life. My last choice was the iPhone 6 to get a nice user experience.
Then I thought a little and I remembered that in fact my experience was much much better on KitKat.
So I decided to try again kitkat and OMG!!! I couldn’t get back to L, seriously. If you have the same issues as I have, it’s definitely a solution.
So of course you’ll lose some interesting stuff from Lollipop and the interface doesn’t look as nice as on L but it is definitely worth it.
Indeed on Kitkat the battery is at least equal, maybe better.
But all the difference is about performances: you can’t even compare it. When I switched from KK to L I didn’t realize and I got accommodate to it but actually in this way we can feel the difference without any hesitation.
Now I can use at least 8 apps at the same time, everything is snappier and quicker. Really it changes my smartphone life.
So if you’re ready to leave L, join me with KK and you won’t regret. You’ll get a new phone (even it’s kinda absurd) and you’ll never want to change it for another. That’s the phone I have liked.
Thx for the comparison
I haven't tried Lollipop because there is nothing wrong with KitKat (+ROOT!) and there is nothing about Lollipop that I really need, it's mostly just eye-candy imho. Oh yes there is one small thing: The sparkly unlock animation in KK is the worst, haven't found a way to get rid of it yet... (except using a 3rd party lockscreen - which is something I'm not willing to do because I love my lockscreen widgets, any suggestions?)
If you miss the Lollipop stuff here's some suggestions:
-NiLS(app): Gives you customizable lockscreen notifications like Lollipop with any lockscreen
-Nova Launcher(app): Just got a huge Lollipop update, the average person won't know the difference to lollipop when looking at the launcher
-Install Lollipop theme to change nav-bar icons (or use xposed or any other method)
-Sony is pretty amazing with app updates, so all the independent apps like Music are Material Design anyway
Cheers
Well. The problem with multitasking happens on all Xperia Z3 phones with Sony´s Lollipop (Yes, I confirmed it after test with 5 different Xperia Z3 phones from friends and family).
After I get frustrated with this problem, I also think in change the phone for an iPhone, but lol, iPhone have similar problems with browsers that can´t keep various tabs opened and ends refreshing all tabs, and other similar multitasking problems because of limited ram. I maybe change my Z3 for an Samsung Galaxy S6 Edge in a month (Or when the Galaxy S6 gets Android 5.1 update) because the camera of the Z3 is very bad in quality for me, but until then, I found a "fix" for the multitasking problem:
I finally "fixed" it. ¿How?: Simple, I just installed Cyanogenmod 12.1 in my phone, and it is just... just, very beatiful in multitasking. I can have a loooot of apps opened and get back to one app after a day and they are still opened, it´s is what I ever expected from a phone like Xperia Z3, is amazing. It is because Cyanogenmod is always updated and have all the latest fixes and their own fixes also. I heard that they have fixed more than 51 memory leaks (included the critical ones) in his 12.1 version. Also I get in love with Cyanogenmod extra features.
Yes, I lose all DRM protected features from camera and also PS4 Remote, but meh, camera sucks anyway in stock firmware, and is only a little worse in Cyanogenmod. Just to be careful I backed up my TA partition before unlock my bootloader and go into cyanogenmod.
Hope this helps to all guys that have lollipop, and need a true multitasking on his Xperia Z3 or Z3 Compact.
Aside from multitasking Lollipop seems still very beta on xperia to me. Mind u I own the Smartphone for only 3 days, but the amount of times it made me go nuts, not even my evo 3d managed over 3 years. Phone ran really hot and sort of slugish on lp, but waht reall drove me crazy was Bluetooth Audio... It made my whole phone crash after starting to crackle on my soundwaver (bluetooth speaker).... It wouldnt even play over pc... Back to kitkst and all is fine and dandy. I can actually feel i run a newer handset than before (evo 3D). Ill probably switch to CM some timecdown the road, when lp is fully working.
The stock lollipop build is beta version at best. The debloated lollipop build found here on XDA is beyond acceptable, almost good. The stock kitkat build, though, still has the upper hand. I reverted back today to an old backup and there's no match between the debloated lollipop and the stock kitkat. Stock kitkat wins hands down.
For some balance ive no such issues with lollipop albeit i agree there isnt much of an incentive to upgrade from kitkat. I dont use chrome though. Chrome uses a scary lot of memory. (i use firefox)
Cm12 uses less memory than stock sony roms so that leaves more to chrome, which explains that i guess.
My only complaint is few UI elements that are not very material, you know.
I don´t use Chrome too, I use Cm Browser that dont use a lot of Ram too...
The problem is not how much Ram uses the system, the problem is that Stock Sony in 5.0.2 have a Bad Memory Management and still have Memory Leaks (Except the crititcal ones that are already fixed in Sony Stock Lollipop Firm).
In CM 12.1 a loot of those memory leaks are already fixed, so that also explains why Cyanogenmod works a lot better with multitasking and can keep a lot of apps without close.
clouds5 said:
Thx for the comparison
I haven't tried Lollipop because there is nothing wrong with KitKat (+ROOT!) and there is nothing about Lollipop that I really need, it's mostly just eye-candy imho. Oh yes there is one small thing: The sparkly unlock animation in KK is the worst, haven't found a way to get rid of it yet... (except using a 3rd party lockscreen - which is something I'm not willing to do because I love my lockscreen widgets, any suggestions?)
If you miss the Lollipop stuff here's some suggestions:
-NiLS(app): Gives you customizable lockscreen notifications like Lollipop with any lockscreen
-Nova Launcher(app): Just got a huge Lollipop update, the average person won't know the difference to lollipop when looking at the launcher
-Install Lollipop theme to change nav-bar icons (or use xposed or any other method)
-Sony is pretty amazing with app updates, so all the independent apps like Music are Material Design anyway
Cheers
Click to expand...
Click to collapse
Thanks for the apps. I'm happy not to be the only one to have made this step!
iFlasher said:
Well. The problem with multitasking happens on all Xperia Z3 phones with Sony´s Lollipop (Yes, I confirmed it after test with 5 different Xperia Z3 phones from friends and family).
After I get frustrated with this problem, I also think in change the phone for an iPhone, but lol, iPhone have similar problems with browsers that can´t keep various tabs opened and ends refreshing all tabs, and other similar multitasking problems because of limited ram. I maybe change my Z3 for an Samsung Galaxy S6 Edge in a month (Or when the Galaxy S6 gets Android 5.1 update) because the camera of the Z3 is very bad in quality for me, but until then, I found a "fix" for the multitasking problem:
I finally "fixed" it. ¿How?: Simple, I just installed Cyanogenmod 12.1 in my phone, and it is just... just, very beatiful in multitasking. I can have a loooot of apps opened and get back to one app after a day and they are still opened, it´s is what I ever expected from a phone like Xperia Z3, is amazing. It is because Cyanogenmod is always updated and have all the latest fixes and their own fixes also. I heard that they have fixed more than 51 memory leaks (included the critical ones) in his 12.1 version. Also I get in love with Cyanogenmod extra features.
Yes, I lose all DRM protected features from camera and also PS4 Remote, but meh, camera sucks anyway in stock firmware, and is only a little worse in Cyanogenmod. Just to be careful I backed up my TA partition before unlock my bootloader and go into cyanogenmod.
Hope this helps to all guys that have lollipop, and need a true multitasking on his Xperia Z3 or Z3 Compact.
Click to expand...
Click to collapse
CM12.1 alternative is good to know then. If I miss L too much, I guess I'll give a try to CM.
clouds5 said:
Thx for the comparison
I haven't tried Lollipop because there is nothing wrong with KitKat (+ROOT!) and there is nothing about Lollipop that I really need, it's mostly just eye-candy imho. Oh yes there is one small thing: The sparkly unlock animation in KK is the worst, haven't found a way to get rid of it yet... (except using a 3rd party lockscreen - which is something I'm not willing to do because I love my lockscreen widgets, any suggestions?)
Cheers
Click to expand...
Click to collapse
Xposed Installer + Xperia Xposed should make you happy.
I see lollipop better than kitkat, phone run faster and smoother. Good update
Son Lam said:
I see lollipop better than kitkat, phone run faster and smoother. Good update
Click to expand...
Click to collapse
Yes, is smoother, but we are talking about the multitasking that is not so good as it have to be...
KitKat has much more battery time than lollipop.
What do yolu think
draligus said:
KitKat has much more battery time than lollipop.
What do yolu think
Click to expand...
Click to collapse
I think that it's a wrong statement. The same power usage curves and same percentage at the end of the day for me.
However, you might be using apps that don't behave well on LP.
Jack_R1 said:
I think that it's a wrong statement. The same power usage curves and same percentage at the end of the day for me.
However, you might be using apps that don't behave well on LP.
Click to expand...
Click to collapse
that was my observation.
KK were amazing for my needs (good battery, smooth).
Lollipop looks just the same.
I always disable animations and whatnot, so I'm kind of an odd user.
to me LLP is good except the quick toggle and sound profile
i need to swipe twice for quick toggle and to swipe twice to close the quick toggle.
using volume button for sound profile annoys me as when i wanna silent my phone while plating music can't be done
multitasking so far is good for me
battery life is the same and in fact idle time is better in LLP
most of the apps improve smoothness in LLP except a few
mimicicu said:
Xposed Installer + Xperia Xposed should make you happy.
Click to expand...
Click to collapse
Could you elaborate on that
I have tried to like Lollipop, but the annoyances i really have, is the swipe down quick menu, prefer the kitkat one, and i really dislike, the user icon on the Lockscreen status bar, At the moment, i have reverted back to kitkat, but would love to give lollipop more time, but after a day, i alway's revert back.
clouds5 said:
Could you elaborate on that
Click to expand...
Click to collapse
You wanted to get rid of the "sparkly unlock animation" of your Z3 Compact, right?
Do you want the classic Android locker instead?
The original Xperia unlock:
http://i.imgur.com/umsERNx.png
Install Xperia Xposed then this:
http://i.imgur.com/VQOD6ay.png
(reboot)
You activate this:
http://i.imgur.com/92fLyDf.png
And you get this:
http://i.imgur.com/ZOOTdTn.png
Hello everyone. I've been using the stock firmware since i bought the phone but currently thinking to try cynogenmod.
What i want to ask is, does it worth to install CM as Sony's stock rom is pretty good both performance/battery consumption and UI wise, compared to many other phone like samsung which i never quite liked.
Will it improve the battery life which is sony has already done a good job on stock firmware and what other benefits will i get?
Thanks in advance.
Brick3 said:
Hello everyone. I've been using the stock firmware since i bought the phone but currently thinking to try cynogenmod.
What i want to ask is, does it worth to install CM as Sony's stock rom is pretty good both performance/battery consumption and UI wise, compared to many other phone like samsung which i never quite liked.
Will it improve the battery life which is sony has already done a good job on stock firmware and what other benefits will i get?
Thanks in advance.
Click to expand...
Click to collapse
Try to use stock based rom if u don't want to loose drm keys. As cm requires an ub phone.
Brick3 said:
Hello everyone. I've been using the stock firmware since i bought the phone but currently thinking to try cynogenmod.
What i want to ask is, does it worth to install CM as Sony's stock rom is pretty good both performance/battery consumption and UI wise, compared to many other phone like samsung which i never quite liked.
Will it improve the battery life which is sony has already done a good job on stock firmware and what other benefits will i get?
Thanks in advance.
Click to expand...
Click to collapse
CM based roms have terrible camera performance. U will lost ur drm keys. Its contains ur camera clarity, bravia engine and so.. So better stick with stock Sony. But performance wise CM is best..
Brick3 said:
Hello everyone. I've been using the stock firmware since i bought the phone but currently thinking to try cynogenmod.
What i want to ask is, does it worth to install CM as Sony's stock rom is pretty good both performance/battery consumption and UI wise, compared to many other phone like samsung which i never quite liked.
Will it improve the battery life which is sony has already done a good job on stock firmware and what other benefits will i get?
Thanks in advance.
Click to expand...
Click to collapse
In Sony world, it is mostly personal preference. If it was a Samsung phone I would no doubt say "go for it and never look back". For a Sony, it is just you have more than one option.
What you get with Sony's stock over a pure(ish) Android;
-Options to have ClearAudio+ and XReality technologies which helps to improve music and image quality respectively from Sony.
- Stamina Mod. Without turning up and down bars into orange
- Picture correcting software which is heavily integrated into original camera software and protected by famous DRM keys. It helps smoothing the noise on the photos, coming mostly from lack of enough light. Especially night shots really benefit from it (difference not so visible on day light).
- FM Radio and some software of Sony like Playstation center and internal backup and restore software, also an Antivirus if anyone is interested in.
Bad side of Sony's software over Pure Android:
- the theme you apply directly effects the top bar. I love red and red-like colors but I don't wanna use my whatsapp with a cherry red line on top. I was hoping that would change in 5.1.1 but no luck.
- standby drain is high if no Stamina is on. Something between 5-10% over night. That's absurd considering the usage drain is fairly good.
- all those beautiful camera options only limited to 8mp option. 12mp is just pure photo (still combined with Sony's correction software if DRMs are active)
- when I try to fast scroll, sometimes the launcher jumps two pages at a time but that happens only going to the right, not happening when going to the left
- I don't know if it's only my phone but most of the time turning on the WiFi is not enough for it to auto connect to a remembered network. I have to open the network list and click on it to connect.
So, what CM or other pure Android-based ROMs offer:
- visual consistentcy among all the apps and menus. Once use stock Android you understand how odd the later added apps look in modified versions. For example Google photos and Google calendar has very familiar look and feel and behaviours. So once you get used to them you can immediately and efficiently start using Google Messages too. However that is not the case with Sony's Album or Walkman app no matter they have their functional advantages.
- super fast, super light, super light on the battery.
- sound and camera may need some fine tuning to reach to Sony level but it is possible as this device have is well known by developers and shares a very generous, open code. For example OpenCam app is perfect for doing anything you want to do with your camera, and it also comes without Mp limitations.
- there are some neat additions to original Android like theme engine or assigning volume keys to change the song or reordering the tiles on the top bar.
- per app ops to limit untrusted apps' intentions.
- more options through Xposed as it is created from a widely shared code.
The cons:
- since most of the works are based on nightlies, sometimes things can be broken for a couple of days or something working might stop working after an update. So you must decide between a tester and a careful everyday user who comes one or two days after the testers on the update schedule.
- you should find you DRM keys a safe place before unlocking your bootloader (I keep mine on Google drive) as they will be gone in order to be able to install a non-Sony ROM.
- camera quality may degrade if you are fan of super auto mod especially (personally, not).
- Xreality will not be there as it is a Sony extension. However I personally think this beautiful screen does not need any tuning to show the beauty of anything.
- no FM radio or pre installed anti virus software.
Sent from my D6503 using XDA Free mobile app
_delice_doluca_ said:
In Sony world, it is mostly personal preference. If it was a Samsung phone I would no doubt say "go for it and never look back". For a Sony, it is just you have more than one option.
What you get with Sony's stock over a pure(ish) Android;
-Options to have ClearAudio+ and XReality technologies which helps to improve music and image quality respectively from Sony.
- Stamina Mod. Without turning up and down bars into orange
- Picture correcting software which is heavily integrated into original camera software and protected by famous DRM keys. It helps smoothing the noise on the photos, coming mostly from lack of enough light. Especially night shots really benefit from it (difference not so visible on day light).
- FM Radio and some software of Sony like Playstation center and internal backup and restore software, also an Antivirus if anyone is interested in.
Bad side of Sony's software over Pure Android:
- the theme you apply directly effects the top bar. I love red and red-like colors but I don't wanna use my whatsapp with a cherry red line on top. I was hoping that would change in 5.1.1 but no luck.
- standby drain is high if no Stamina is on. Something between 5-10% over night. That's absurd considering the usage drain is fairly good.
- all those beautiful camera options only limited to 8mp option. 12mp is just pure photo (still combined with Sony's correction software if DRMs are active)
- when I try to fast scroll, sometimes the launcher jumps two pages at a time but that happens only going to the right, not happening when going to the left
- I don't know if it's only my phone but most of the time turning on the WiFi is not enough for it to auto connect to a remembered network. I have to open the network list and click on it to connect.
So, what CM or other pure Android-based ROMs offer:
- visual consistentcy among all the apps and menus. Once use stock Android you understand how odd the later added apps look in modified versions. For example Google photos and Google calendar has very familiar look and feel and behaviours. So once you get used to them you can immediately and efficiently start using Google Messages too. However that is not the case with Sony's Album or Walkman app no matter they have their functional advantages.
- super fast, super light, super light on the battery.
- sound and camera may need some fine tuning to reach to Sony level but it is possible as this device have is well known by developers and shares a very generous, open code. For example OpenCam app is perfect for doing anything you want to do with your camera, and it also comes without Mp limitations.
- there are some neat additions to original Android like theme engine or assigning volume keys to change the song or reordering the tiles on the top bar.
- per app ops to limit untrusted apps' intentions.
- more options through Xposed as it is created from a widely shared code.
The cons:
- since most of the works are based on nightlies, sometimes things can be broken for a couple of days or something working might stop working after an update. So you must decide between a tester and a careful everyday user who comes one or two days after the testers on the update schedule.
- you should find you DRM keys a safe place before unlocking your bootloader (I keep mine on Google drive) as they will be gone in order to be able to install a non-Sony ROM.
- camera quality may degrade if you are fan of super auto mod especially (personally, not).
- Xreality will not be there as it is a Sony extension. However I personally think this beautiful screen does not need any tuning to show the beauty of anything.
- no FM radio or pre installed anti virus software.
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks delice_doluca. That was just the answer I was looking for.
A few things I want to say:
-You've said that the camera is limited to 8 mp but I didn't get what you meant. I can go up to 20.7 mp.
-Cm and other rom's light weight, fast performance is due to the lack of unnecessary bloatware but I dont see how its one of their strengt as you can remove those bloatwares on stock ROM too with root access.
-There's a security software inside Cm as you said but the only difference is that its built in. On stock ROM you just download it manually and besides i'm pretty sure the security programs you're going to download from by kaspersky, avira etc will be a lot better than the cm one. Again I don't think its an advantage either. Im tryong find some good reasons to justify installing cm but I just can't find besides some minor ones as many features that is considered strength of cm you can also do it on stock ROM and im wondering why do some people prefer using cm?
Brick3 said:
Thanks delice_doluca. That was just the answer I was looking for.
A few things I want to say:
-You've said that the camera is limited to 8 mp but I didn't get what you meant. I can go up to 20.7 mp.
-Cm and other rom's light weight, fast performance is due to the lack of unnecessary bloatware but I dont see how its one of their strengt as you can remove those bloatwares on stock ROM too with root access.
-There's a security software inside Cm as you said but the only difference is that its built in. On stock ROM you just download it manually and besides i'm pretty sure the security programs you're going to download from by kaspersky, avira etc will be a lot better than the cm one. Again I don't think its an advantage either. Im tryong find some good reasons to justify installing cm but I just can't find besides some minor ones as many features that is considered strength of cm you can also do it on stock ROM and im wondering why do some people prefer using cm?
Click to expand...
Click to collapse
- Camera is limited to 8mp if you want to apply scenes or choose another mode like HDR. When 20.7mp chosen, all you can do is to take the photo without any ambient or method oriented tuning. (no big deal actually, I shot at 20.7 Mp and tune it in my computer layer. However I wished there was HDR on 20.7 mp)
- do not think bloat ware only as additional apps. There are also background services, running under the OS, or other methods of the OS handling the user's or automated requests. I am not an Android developing master but I can give an example from Linux world. Last month Linux Mint released a new version and they announced their desktop environment (Cinnamon) was now using %40 less CPU even thought it had introduced more effects and options to the user. The trick was to calculate desktop's actions more efficiently and in a more harmonic way so the processes would not fight with each other. So they have knocked the CPU's door at more empty times and less frequently.
Stock Android is tailored by one team, with the same goals at their heads. Sony has another team who is also dressing it and tailoring some parts again. The Sony team is supposed to know what the first team intended and how good they are so they can make the modification exactly like they desired. However now the hybrid OS is designed by two different teams with (maybe entirety) different goals in minds. Don't get me wrong, Sony is the closest and most friendly team to the original Android project and to Google but still it is a complex effort and simplicity is everyone's friend in complex jobs.
- About the security software. Stock Sony ROM is the one which comes with security software (McAfee I guess). CM is open as a nature and you can limit user apps one by one (which is possible where root access exist, regardless of the ROM). My thinking is, all the Antivirus software is unnecessary in Android world. The one and only protection is common sense (simply don't install or clock everything )
What I have been writing should not make you want to install CM BTW CM or other stock Android - like ROMs exist mostly for the people who are saying "I wish that was the next Nexus device, like Xperia Nexus". Basically, for an Xperia device, wanting to install stock Android is just about personal joy or habits coming from another stock Android device (mostly a Nexus).
Don't look for bigger reasons as you probably will not find. All you need to have in your mind is liking stock Android more than Sony's Android and some free time to build your own device experience.
Ps: stock Android term is used for Google's own Android which is not touched by any other company (Sony, Samsung, HTC etc.)
Sent from my D6503 using XDA Free mobile app
_delice_doluca_ said:
- Camera is limited to 8mp if you want to apply scenes or choose another mode like HDR. When 20.7mp chosen, all you can do is to take the photo without any ambient or method oriented tuning. (no big deal actually, I shot at 20.7 Mp and tune it in my computer layer. However I wished there was HDR on 20.7 mp)
- do not think bloat ware only as additional apps. There are also background services, running under the OS, or other methods of the OS handling the user's or automated requests. I am not an Android developing master but I can give an example from Linux world. Last month Linux Mint released a new version and they announced their desktop environment (Cinnamon) was now using %40 less CPU even thought it had introduced more effects and options to the user. The trick was to calculate desktop's actions more efficiently and in a more harmonic way so the processes would not fight with each other. So they have knocked the CPU's door at more empty times and less frequently.
Stock Android is tailored by one team, with the same goals at their heads. Sony has another team who is also dressing it and tailoring some parts again. The Sony team is supposed to know what the first team intended and how good they are so they can make the modification exactly like they desired. However now the hybrid OS is designed by two different teams with (maybe entirety) different goals in minds. Don't get me wrong, Sony is the closest and most friendly team to the original Android project and to Google but still it is a complex effort and simplicity is everyone's friend in complex jobs.
- About the security software. Stock Sony ROM is the one which comes with security software (McAfee I guess). CM is open as a nature and you can limit user apps one by one (which is possible where root access exist, regardless of the ROM). My thinking is, all the Antivirus software is unnecessary in Android world. The one and only protection is common sense (simply don't install or clock everything )
What I have been writing should not make you want to install CM BTW CM or other stock Android - like ROMs exist mostly for the people who are saying "I wish that was the next Nexus device, like Xperia Nexus". Basically, for an Xperia device, wanting to install stock Android is just about personal joy or habits coming from another stock Android device (mostly a Nexus).
Don't look for bigger reasons as you probably will not find. All you need to have in your mind is liking stock Android more than Sony's Android and some free time to build your own device experience.
Ps: stock Android term is used for Google's own Android which is not touched by any other company (Sony, Samsung, HTC etc.)
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
I guess i'll continue to use stock ROM as i'm happy with it.
Thank you so much for this detailed answer.
why is the multi tasking so bad on cm11?
Do you get camera 2 api on cyanogens rom? If be prepared to swap if they did for manual focus
cm has media skip buttons function., that alone makes me prefer it more
I was contemplating the same as the OP. After reading the replies here I've decided to look at other options for installing a custom ROM without unlocking the bootloader.
You guys have provided some really good info in this thread, I wish others could be as informative.
Thanks
Cm is good for my nexus5, but seems it is not so good for my z2
Hey Folks,
I just ordered a XZ Premium yesterday, which will come till this Weekend. First Thing to do is updating and unlocking the Bootloader, before checking out how actual SONY Stock Firmware looks like nowadys (My last SONY was a Z3). After that comes the next important Step. Contributing to the XZ Premium Forums.
I'm not sure what will be better or makes more Sense. The Options are:
-A new AOSP based Project for Xperia Devices
-A new Stock ROM Project (Snappatch Xperia Stock Exclusive)
-A new Patch for a own AOSP based Project (Combing the first two Options somehow)
If You want to know what the Patch is, just check out My Signature where You will find the Link to My actual Thread. I'm just really happy to get a XZ Premium (Since i don't like the XZ2 and prefer the XZP Design over the XZ1 Design), and can't wait to work with it and share the Results with You! Let Me know what You think which is mostly needed or what would make the biggest difference (Upgrade) to Your Device...
BR
Miustone said:
Hey Folks,
I just ordered a XZ Premium yesterday, which will come till this Weekend. First Thing to do is updating and unlocking the Bootloader, before checking out how actual SONY Stock Firmware looks like nowadys (My last SONY was a Z3). After that comes the next important Step. Contributing to the XZ Premium Forums.
I'm not sure what will be better or makes more Sense. The Options are:
-A new AOSP based Project for Xperia Devices
-A new Stock ROM Project (Snappatch Xperia Stock Exclusive)
-A new Patch for a own AOSP based Project (Combing the first two Options somehow)
If You want to know what the Patch is, just check out My Signature where You will find the Link to My actual Thread. I'm just really happy to get a XZ Premium (Since i don't like the XZ2 and prefer the XZP Design over the XZ1 Design), and can't wait to work with it and share the Results with You! Let Me know what You think which is mostly needed or what would make the biggest difference (Upgrade) to Your Device...
BR
Click to expand...
Click to collapse
I gotta say im very happy to hear that!
well most of the community here just want google camera working properly without losing drm keys and to have a native 4k screen option or 1080p/120hz hdr and all that stuff
so as i understood unlocking bootloader loses drm keys so flashing aosp roms with google camera doesnt make the camera better due to loss of drm (as noise reduction is lost along with the drm)
if its just possible a way to keep drm while having aosp that way we would have a God level of a camera, coming with 4k/1080p-120hz options that would do it! this phone would be the best for long time
but i guess its impossible to combine those features together which hurts me a lot knowing what potential this device has but cannot be used to the fullest...
any way thank you for joining in i love how developers here are very helpful and doing a great job
so to show my love to them im willing to donate cash to whoever makes a rom with all these features up and running, and there are other people too who are willing to do the same
so good luck dev <3 much love
madshark2009 said:
I gotta say im very happy to hear that!
well most of the community here just want google camera working properly without losing drm keys and to have a native 4k screen option or 1080p/120hz hdr and all that stuff
so as i understood unlocking bootloader loses drm keys so flashing aosp roms with google camera doesnt make the camera better due to loss of drm (as noise reduction is lost along with the drm)
if its just possible a way to keep drm while having aosp that way we would have a God level of a camera, coming with 4k/1080p-120hz options that would do it! this phone would be the best for long time
but i guess its impossible to combine those features together which hurts me a lot knowing what potential this device has but cannot be used to the fullest...
any way thank you for joining in i love how developers here are very helpful and doing a great job
so to show my love to them im willing to donate cash to whoever makes a rom with all these features up and running, and there are other people too who are willing to do the same
so good luck dev <3 much love
Click to expand...
Click to collapse
Thanks for the nice and quick response! As a ex Xperia Usera am i aware of the benefits and cons of unlocking the Bootloader. I remeber well how the Camera stopped working on the Z1 after unlocking the Bootloader and the lack the of Camera2 API. And it looks like it isn't much better these Days.
A thing i really miss here is the choice to have a locked Bootloader with at least Root to save the DRMs and to be able to use modified Stock. With My Patch would this End in endless Options and Ways of Optimizing/Customizing the Firmware without loosing any Features. But this is something i don't count on anymore (Android is a Fort Knox since Marshmallow/Nougat)...
How does it actually looks like on AOSP? The Camera works and has legacy Camera2 API Support? Lost Features are the Super Slow Motion Recording and Noise Reduction? The added 120Hz Mode and 4K / HDR Features seem to be there...!?
Well, i'm still not sure what to do. I see a lack of Stock ROMs on the Xperia Forums (I worked on this last Night but was unable to extract the sin Files), but i see also how AOSP has enhanced on Xperia Devices. We don't have treble Support on the XZ Premium but the XZ1 is already able to use Unified AOSP Builds and almost everything is working well thanks to the great Devs and of course SONY. And i'm sure AOSP will ever be a important alternative to Stock (Smaller, faster, fresher)...
So which Way should i go? I'm planning for Years to create a AOSP based close to Google Firmware like OS, but Stock is just looking great too on Xperias. And the DRM Fix is allowing to use all the Features on Stock for now!?
Hmm... Sorry for the many Questions! :angel:
first welcome..great to see devs have an interest in this device. I'm sure you will love it. only thing i would wish for is to have google camera work on it. as for custom roms ,not well versed in that scene,, its my first ever android device to still getting to grips with it.
kibet85 said:
first welcome..great to see devs have an interest in this device. I'm sure you will love it. only thing i would wish for is to have google camera work on it. as for custom roms ,not well versed in that scene,, its my first ever android device to still getting to grips with it.
Click to expand...
Click to collapse
Thanks
Couldn't live without a unlocked Android anymore. Android User since around 8 Years here (Made some Holidays on iOS and Windows). And i'm glad to be back on Xperia. Hope You enjoy it as much as i do and will with the XZP But to understand that right, what's the actual Point with the Google Camera? I managed to gain some extra functionalities in the Past, but how does it actually looks like after installing the Stock Google Camera (Or even the Modded Ones)?
Is it full functional? Are the Pixel (2) Configs working? Differences between Stock and AOSP? Would love to take a look on the Camera Part overall. I want to shoot great Results with My new Baby so it's also important for Me...
Miustone said:
Thanks for the nice and quick response! As a ex Xperia Usera am i aware of the benefits and cons of unlocking the Bootloader. I remeber well how the Camera stopped working on the Z1 after unlocking the Bootloader and the lack the of Camera2 API. And it looks like it isn't much better these Days.
A thing i really miss here is the choice to have a locked Bootloader with at least Root to save the DRMs and to be able to use modified Stock. With My Patch would this End in endless Options and Ways of Optimizing/Customizing the Firmware without loosing any Features. But this is something i don't count on anymore (Android is a Fort Knox since Marshmallow/Nougat)...
How does it actually looks like on AOSP? The Camera works and has legacy Camera2 API Support? Lost Features are the Super Slow Motion Recording and Noise Reduction? The added 120Hz Mode and 4K / HDR Features seem to be there...!?
Well, i'm still not sure what to do. I see a lack of Stock ROMs on the Xperia Forums (I worked on this last Night but was unable to extract the sin Files), but i see also how AOSP has enhanced on Xperia Devices. We don't have treble Support on the XZ Premium but the XZ1 is already able to use Unified AOSP Builds and almost everything is working well thanks to the great Devs and of course SONY. And i'm sure AOSP will ever be a important alternative to Stock (Smaller, faster, fresher)...
So which Way should i go? I'm planning for Years to create a AOSP based close to Google Firmware like OS, but Stock is just looking great too on Xperias. And the DRM Fix is allowing to use all the Features on Stock for now!?
Hmm... Sorry for the many Questions! :angel:
Click to expand...
Click to collapse
thats the thing, what I understood is aosp doesnt have legace camera2 API support, no super slow mo, no noise reduction (as drm is lost).
as for screen options 4k HDR or 1080p 120hz seem to show in options but people and devs say its not actually working, as after they choose an option and restart they claim to nothing changing.
these are the main reasons why people here hesitate unlocking the bootloader, as there is no camera2 API support on aosp so you get google camera but lose noise reduction and so many other camera features.
and there is no additional features that aosp give, neither of 4k nor 120hz work, so there is really no point of unlocking, if any thing its not just useless but also worsens...
and while still having drm, google camera has no support for max resolution (only 8mp) and does not have HDR+ option
so here to sum up:
2 thing that will make this community love you so much
1) fully working google camera while still having drm (or drm patch for that matter if its impossible to backup drm)
2) screen options of [email protected] or [email protected]
if you can do that in aosp build thats the best
if you can do it in stock based build, also great
but as I saw your snappatch rom it looks very nice but yet again, unless it has those 2 things, unlocking bootloader and going through this much trouble is useless in my opinion
so good luck bro I really appreciate your collaboration
Miustone said:
Thanks
Couldn't live without a unlocked Android anymore. Android User since around 8 Years here (Made some Holidays on iOS and Windows). And i'm glad to be back on Xperia. Hope You enjoy it as much as i do and will with the XZP But to understand that right, what's the actual Point with the Google Camera? I managed to gain some extra functionalities in the Past, but how does it actually looks like after installing the Stock Google Camera (Or even the Modded Ones)?
Is it full functional? Are the Pixel (2) Configs working? Differences between Stock and AOSP? Would love to take a look on the Camera Part overall. I want to shoot great Results with My new Baby so it's also important for Me...
Click to expand...
Click to collapse
the thing about google camera is in the HDR+ algorithm. its an incredibly easy way to produce some stunning photos. for HDR+ to work,, it needs the full camera2api and support of RAW images. currently, Sony use some kind of legacy camera2api and doesn't support RAW, So most ports are limited to 8mp and HDR+ doesn't work.
madshark2009 said:
thats the thing, what I understood is aosp doesnt have legace camera2 API support, no super slow mo, no noise reduction (as drm is lost).
as for screen options 4k HDR or 1080p 120hz seem to show in options but people and devs say its not actually working, as after they choose an option and restart they claim to nothing changing.
these are the main reasons why people here hesitate unlocking the bootloader, as there is no camera2 API support on aosp so you get google camera but lose noise reduction and so many other camera features.
and there is no additional features that aosp give, neither of 4k nor 120hz work, so there is really no point of unlocking, if any thing its not just useless but also worsens...
and while still having drm, google camera has no support for max resolution (only 8mp) and does not have HDR+ option
so here to sum up:
2 thing that will make this community love you so much
1) fully working google camera while still having drm (or drm patch for that matter if its impossible to backup drm)
2) screen options of [email protected] or [email protected]
if you can do that in aosp build thats the best
if you can do it in stock based build, also great
but as I saw your snappatch rom it looks very nice but yet again, unless it has those 2 things, unlocking bootloader and going through this much trouble is useless in my opinion
so good luck bro I really appreciate your collaboration
Click to expand...
Click to collapse
kibet85 said:
the thing about google camera is in the HDR+ algorithm. its an incredibly easy way to produce some stunning photos. for HDR+ to work,, it needs the full camera2api and support of RAW images. currently, Sony use some kind of legacy camera2api and doesn't support RAW, So most ports are limited to 8mp and HDR+ doesn't work.
Click to expand...
Click to collapse
SONY really HAS to include Camera HAL3 in the Future... Looks like the XZ2 will have the same Issues, but i wonder how hard it can be to change the Software of the own produced Hardware!? The Xperia Cameras would be outstanding against Others running AOSP, but even with all the Developer Support are they missing this Important Point...
I really hope i can gain some nice Results on Stock, otherwise would i like to try out Porting the SONY Camera App(s) to AOSP (With working Noise Reduction) which would even without HAL3 Support end in better Results as without HAL3 on AOSP/Google Camera Apps. Could be something for Xperia Cross Device Development, but i don't know yet if this is even possible without Porting the half of the Xperia Stock Systems to AOSP...
Can't wait to get My Hands on the XZP... Checking the Shipping State all 10 Minutes
https://nolp.dhl.de/nextt-online-public/set_identcodes.do?lang=de&idc=JJD1405123613478
Bit worried about the coming Camera Quality but i'm looking forward to get the best out of our Devices! Treble would also be something nice to have... Has anyone checked the Partition Table of the XZ Premium to see if there is a chance for a Vendor Partition!?
I think if you create a stock based rom with ported xz2 features and native 4k, you are doing the best and it most be easier and more stable than a aosp.
Blackghosthm said:
I think if you create a stock based rom with ported xz2 features and native 4k, you are doing the best and it most be easier and more stable than a aosp.
Click to expand...
Click to collapse
Yeha, i was thinking about to deliver Stock again (Since SONY Stock is also really good except of the End of Support with Updates at any Point). But that means pretty Device Specific Work (Lot of Work). I could ease the Things on Stock up if i would deliver real Stock (Barely Debloated) flashable ZIPs for Xperia Devices besides doing the Snappatch for Xperia (Debloating, Adding, Root, Features, Google App Replacements, Mods and such).
I see there is also actually no alternative to this "Turbo ROM" i've taken a look on. And to be honestly, i don't see Me using this ROM. So a Stock Flashable with some Extra Features and deep going Optimizations from the Patch could be something great in My Eyes. I could also extend the Support with that up to other Xperia Devices like the XZ1 and XZ2 (If the need is there).
Let's see what i'm able to do after getting My new Baby. I'm full of Hopes that i rock this Device for all of us here :fingers-crossed:
madshark2009 said:
due to loss of drm (as noise reduction is lost
Click to expand...
Click to collapse
I used to run an old build of AOSP to test out the 120 hz feature (though it's bugged. Sony devs are aware of this and I filed an issue in their github). The noise reduction was albeit the same. AFAIK the pictures you take will just show a green picture if you don't have the drm keys (at least the fix). But the noise reduction is still quite the same. However, I did not test that completely, just from memory.
As for topic, I'd rather go stock. The google camera isn't really something I'm after, but that's just me. I'm slowly teaching myself how to port stuff from other phones, specifically the new XZ2. I'd rather have stock + your patch + xz2 goodies, maybe?
iArvee said:
I used to run an old build of AOSP to test out the 120 hz feature (though it's bugged. Sony devs are aware of this and I filed an issue in their github). The noise reduction was albeit the same. AFAIK the pictures you take will just show a green picture if you don't have the drm keys (at least the fix). But the noise reduction is still quite the same. However, I did not test that completely, just from memory.
As for topic, I'd rather go stock. The google camera isn't really something I'm after, but that's just me. I'm slowly teaching myself how to port stuff from other phones, specifically the new XZ2. I'd rather have stock + your patch + xz2 goodies, maybe?
Click to expand...
Click to collapse
Yah in stock based the fix works good
But in aosp that doesnt work
iArvee said:
I used to run an old build of AOSP to test out the 120 hz feature (though it's bugged. Sony devs are aware of this and I filed an issue in their github). The noise reduction was albeit the same. AFAIK the pictures you take will just show a green picture if you don't have the drm keys (at least the fix). But the noise reduction is still quite the same. However, I did not test that completely, just from memory.
As for topic, I'd rather go stock. The google camera isn't really something I'm after, but that's just me. I'm slowly teaching myself how to port stuff from other phones, specifically the new XZ2. I'd rather have stock + your patch + xz2 goodies, maybe?
Click to expand...
Click to collapse
Getting XZ2 Features on the XZ Premium sounds Good to Me. Smart would be to integrate the Ported Content into the Patch so People can add it or just keep it Original with a untouched Stock Firmware (System+Boot). But i wonder...
madshark2009 said:
Yah in stock based the fix works good
But in aosp that doesnt work
Click to expand...
Click to collapse
Does it mean that the Camera does not work without this DRM Fix (Which isn't TWRP flashable (Without a PC))?
And AOSP has a working Camera out of the Box but without Camera2 API and with Noisy Pictures!? Just want to make sure i got it right before flaming about the lack of a mobile DRM Fix (Which could be included in ROMs, or simple be a Flashable ZIP for on the go)
Something i don't want is the need for a PC after flashing anything. I test so often My changes with Clean Flashs over the Day that it would kill Me to use Windows with this DRM Fix over and over again >.<
When you wana fix drm keys on stock or stock based rom you need twrp+flashable kernel (you can find it in afs)+flashable magisk+drm fix flashable file thats all so quickly without pc.
Im do it all the time in all oreo firmware.
Blackghosthm said:
When you wana fix drm keys on stock or stock based rom you need twrp+flashable kernel (you can find it in afs)+flashable magisk+drm fix flashable file thats all so quickly without pc.
Im do it all the time in all oreo firmware.
Click to expand...
Click to collapse
So there no need for the XperiFix Tool all the Time? Can You give Me any Links to it? I don't see the need to include it into the ROMs itself, but i would really like to take a look on what it does (Especially since Magisk in involved somehow). Maybe is there a way to get the Noise Reduction on a AOSP Port of the SONY Camera App. Can't say anything about this yet...
Kernel link:https://androidfilehost.com/?fid=673791459329069491
Drm fix link:https://mega.nz/#!LRoFkSDA!bOsnRRE1gRpAZ0su-bZMfUjvMB7aRkLEc3V63bOuKnM
You dont need xperifix but if you flash stock rom with flashtool you need to flash twrp in fastboot and if you want twrp you can download it from here:https://dl.twrp.me/maple/twrp-3.2.1-0-maple.img.html
Blackghosthm said:
Kernel link:https://androidfilehost.com/?fid=673791459329069491
Drm fix link:https://mega.nz/#!LRoFkSDA!bOsnRRE1gRpAZ0su-bZMfUjvMB7aRkLEc3V63bOuKnM
You dont need xperifix but if you flash stock rom with flashtool you need to flash twrp in fastboot and if you want twrp you can download it from here:https://dl.twrp.me/maple/twrp-3.2.1-0-maple.img.html
Click to expand...
Click to collapse
Thanks for sharing this with Me! Since this includes a Kernel am i wondering what's changed on the boot.img to get the Fix working. And it's dated on 2017 and still working on newer Firmwares?
I just extracted the latest G8414 .145 Firmware. Would be cool if i could Patch the kernel for the fix so that we can run the latest Kernel with it...
Yes it works,this is canbe good.
Miustone said:
So there no need for the XperiFix Tool all the Time? Can You give Me any Links to it? I don't see the need to include it into the ROMs itself, but i would really like to take a look on what it does (Especially since Magisk in involved somehow). Maybe is there a way to get the Noise Reduction on a AOSP Port of the SONY Camera App. Can't say anything about this yet...
Click to expand...
Click to collapse
Yes and no. On an old version of the hack, you can just flash the drmfix. However, on the new xperifix software, it seems to also change a few file attributes. Not really sure about that though.
Androplus' kernel (kernel.andro.plus) is always updated to the latest version. You can flash that and do the old method of the drmfix (flashing) instead of the xperifix. I've tried that before but it seems to not work. I probably missed a step anyways.
iArvee said:
Yes and no. On an old version of the hack, you can just flash the drmfix. However, on the new xperifix software, it seems to also change a few file attributes. Not really sure about that though.
Androplus' kernel (kernel.andro.plus) is always updated to the latest version. You can flash that and do the old method of the drmfix (flashing) instead of the xperifix. I've tried that before but it seems to not work. I probably missed a step anyways.
Click to expand...
Click to collapse
Im tried androplus kernel and it doesn't fix drm keys.