New Xperia Project - Sony Xperia XZ Premium Guides, News, & Discussion

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.

Related

Sonys Bootloader Unlock Page Updated With Warning About Camera Performance

"Certain pre-loaded content on your device may also be inaccessible due to the removal of DRM security keys. For high-end devices running recent software versions, for instance Xperia Z3, the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected. The secure user data partition may also become inaccessible, and you will not be able to get any more official software upgrades if you unlock the boot loader."
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
So there you go folks officially confirmed again to anybody in doubt.:good:
It would be nice to have an exploit so we can root, without losing those DRM keys.
NRG1975 said:
It would be nice to have an exploit so we can root, without losing those DRM keys.
Click to expand...
Click to collapse
Fingers crossed. This is such an awesome phone and even knowing this in advance, I would still buy the Z3 Compact over everything else because there's nothing on the market that comes close, IMO.
Bounty is available to unlock and keep functions
I'm sure this will help the cause: http://forum.xda-developers.com/z3-compact/general/bounty-root-unlocking-bootloader-method-t2940539
Oh well... I'll just wait one year or two before unlocking it, until then I'll try to survive with the intrusive apps
question: If I flash a custom rom, I will lose camera functionality anyways, right? What if I use a different camera-app? Does the Sony app produce the best pictures?
Hope you guys can help me out here
No, camera will still work. It's just the low lighting algorithm that's lost, which is meant to give better quality pictures in low light. I've rooted and personally don't see any difference in picture quality if flash is used.
Just to add... Since I've rooted i have deleted some built in Sony crap which freed up space and ram, to me... My phone feels faster and I'm sure battery is even better. Ive also installed viper4android which has greatly improved the sound on the phone. Definitely not regretting rooting but that's just my opinion.
Cheers
thanks for your reply. It is good to hear that there are people out there that have root and are happy with it. Personally, I will root as soon as I get the phone (which should be around monday).
I'm aware that the camera still works. I was just wondering if different camera apps produce different quality pictures (with and without root). In that case I wouldnt care about loosing DRM keys because I will probably install CyanogenMod anyway.
Is there any AOSP 5.0.X build signed by Sony? Which you can flash without unlocking the bootloader or something like that..
(I don't like modded roms, just the basic aosp builds).
I am asking this because I read here that aosp is available for this phone:
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/latest-updates/
And I want to buy the next Z compact because I want a 720p small phone instead of a 1080p lesser big one.
But only if AOSP Android is available. (Since I've been using a Nexus for a few years)
Sent from my Nexus 5
thesebastian said:
Is there any AOSP 5.0.X build signed by Sony? Which you can flash without unlocking the bootloader or something like that..
(I don't like modded roms, just the basic aosp builds).
I am asking this because I read here that aosp is available for this phone:
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/latest-updates/
And I want to buy the next Z compact because I want a 720p small phone instead of a 1080p lesser big one.
But only if AOSP Android is available. (Since I've been using a Nexus for a few years)
Sent from my Nexus 5
Click to expand...
Click to collapse
Shortt answer is no there is not an AOSP build signed ny Sony.
Youll need to unlock, if you really want stock. Sony's optimisations are useless on Aosp ROMs so if that's all you want to run then losing DRM keys is not a big issue unless you wanted to return to a Sony ROM.

### Cynogenmod vs Stock Rom? ###

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

AOSP Camera Bounty, Z3 and Z3 Compact

Hi XDA community,
I am currently running the latest AOSP on our phone, and it is very nice. The only part really missing now is the camera. I know anyone who is familiar with AOSP on our device will know the story.
What I am wondering now is if people would be interested in raising a bounty to get an implementation put together?
I for one would be happy to put up some cash if it meant that we got a fully functioning Android for another year. The hardware in the phone is plenty enough for everything I use it for.
Developers would any of you be interested in claiming a bounty by fixing up our camera drivers to work with the 3.10 AOSP kernel?
Flashable Zips of AOSP Nougat Z3c:https://www.androidfilehost.com/user/?w=settings-dev-files&flid=73595
Promised Donations:
@mcgi5sr2 $50
@smorgar $10
@istux $15
@okij $15
@Rumbi $10
 @danilobertelli $15
 @nailyk $20
 @Tilarou $20
 @Me Gusta $10
Total: $165
I will need to work out exactly what we are going to specify as a working camera. Please comment with thoughts.
requests so far:
No fish eye
picture and video recording
Auto Focus
This is a neat idea. But I don't even know if it's possible to achieve this.
Im in! 10$ from me!
---------- Post added at 08:38 AM ---------- Previous post was at 08:18 AM ----------
mcgi5sr2 said:
Hi XDA community,
I am currently running the latest AOSP on our phone, and it is very nice.
Click to expand...
Click to collapse
Is it stable enough to use as a daily driver? Other bugs/kinks than the broken camera? Im really tempted to test it but i cant download it through the mirror they use. Get some popup regarding adblock that i cant get rid of, even tho i use IE with no adblock at all...
Put me up for $15 :good:
I'll give my money ONLY IF the camera will be fisheye-bug free. (no flame please, this is just my offer)
I'm in with 15 $ too.
And I share the opinion of @istux that the camera should be fisheye-bug free.
@mcgi5sr2: Could you cross-post this in the Z3 forums too, since they are in the same situation and also might participate in the bounty? Cheers.
I would be in with 10 Bucks, too. Afaik the camera is already working with picture and video, only this fisheye bug makes it more or less useless. So with the fisheye bug fixed, everything should be fine?!
Rumbi said:
I would be in with 10 Bucks, too. Afaik the camera is already working with picture and video, only this fisheye bug makes it more or less useless. So with the fisheye bug fixed, everything should be fine?!
Click to expand...
Click to collapse
On the 1.3.3 kernel the cameras are split, and video isn't working. Work is still ongoing on it, but I'm hoping a financial incentive will help
I'm in with 15 $ too if all camera issues can be fixed.
danilobertelli said:
I'm in with 15 $ too if all camera issues can be fixed.
Click to expand...
Click to collapse
cool camera is improving a lot, next set of blobs should have it all sorted including auto focus. Would be cool if we could find a good dev and get him interested in sorting out the fish eye issue
Glad to see your thread as I wanna do the same.
Do you know a dev thread had been opened for this problem?
How do you plan to split the bounty between the devs who will fix the issue?
I buy my device for the camera. Without camera it is useless for me. Depending of the month on the claim I can be in between 20 and 50$.
The fisheye bug isn't there in the new camera. It's there only in the older blobs.
oSandmaNo said:
The fisheye bug isn't there in the new camera. It's there only in the older blobs.
Click to expand...
Click to collapse
I assume the same progress has been done for both Z3/C, right?
If so, what are the downsides of the new 7.1 builds?
doriandiaconu said:
I assume the same progress has been done for both Z3/C, right?
If so, what are the downsides of the new 7.1 builds?
Click to expand...
Click to collapse
I don't see anyone compiling 7.0/1 for z3/C except for Nailyk, but AFAIK he does cm14 and not AOSP. But whatever is fixed in z1 and z2 will work for z3 as well. As long as someone builds one for us
oSandmaNo said:
I don't see anyone compiling 7.0/1 for z3/C except for Nailyk, but AFAIK he does cm14 and not AOSP. But whatever is fixed in z1 and z2 will work for z3 as well. As long as someone builds one for us
Click to expand...
Click to collapse
They are not on xda but fxpblog roms should be up-to-date with sonyxperiadev work.
And you are right, I only build CyanogenMod.
If I get it right you said fisheye is not present anymore. Can you link me to the rom zip and sources as I can give a try please? Or maybe you are talking about incoming blobs?
nailyk said:
They are not on xda but fxpblog roms should be up-to-date with sonyxperiadev work.
And you are right, I only build CyanogenMod.
If I get it right you said fisheye is not present anymore. Can you link me to the rom zip and sources as I can give a try please? Or maybe you are talking about incoming blobs?
Click to expand...
Click to collapse
I'm not a developer but from what I've been reading (I'm a lurker ) for the past year is that the fish eye bug is introduced due to using the jellybean blobs from Z1 and then using a wrapper around it. The new camera does not use that, so there is no fish eye bug. Please correct me if I'm wrong, I haven't flashed any AOSP ROM on my device, but I read a lot. I've also seen the pictures taken by the z2 users and I can't see the fisheye in them. The incoming blobs should fix the focus problems, but the fish eye was never a problem ever since they got it working.
oSandmaNo said:
I'm not a developer but from what I've been reading (I'm a lurker ) for the past year is that the fish eye bug is introduced due to using the jellybean blobs from Z1 and then using a wrapper around it. The new camera does not use that, so there is no fish eye bug. Please correct me if I'm wrong, I haven't flashed any AOSP ROM on my device, but I read a lot. I've also seen the pictures taken by the z2 users and I can't see the fisheye in them. The incoming blobs should fix the focus problems, but the fish eye was never a problem ever since they got it working.
Click to expand...
Click to collapse
Sorry but the fisheye problem doesn't came from blobs only. We discuss a little about it here (and next posts). Our z3(c) had a wide angle camera in a small component. The only way to get this is with a specific lens on the imx220. (imx220c iirc). So honami blobs on z3 get the camera working (almost) perfectly except the proprietary implementation of sony lens correction is absent, that is why we have this fisheye bug. And afaik only z3(c) had this imx220 version.
So if new blobs doesn't provide this proprietary correction or release it still under drm protection, fisheyebug will still be present.
The fisheye is something that needs to be corrected with aftermarket picture processing. As of V5 blobs, the camera on shinano is working, but autofocus is not properly calibrated. That will be done in the future V6 blobs.
If someone wants a 7.1 Build for aries with a working (read non-crashing cam, but broken AutoFocus), I upload some of my Carbon Builds from time to time here:
https://dl.myself5.de/aries/CarbonROM/
Btw, the fix for the camera on 1.3.3 that made full pictures possible was done by @erikas, maybe you want to consider him in your bounty decision. Everything else will be done using vendor blobs or picture post processing.
Sent from my D6603 using Tapatalk
the new camera fix noises in night pictures ?
images night z1 and z2 is is incredibly good this can also work on z3 / C / tablet ? I know that has many problems focus and others but it's a big step to aosp in xperias
I would gladly put 20€ if the camera support the following:
Z3 dual (D6633/D6683), noise reduction, all feature of original sony camera app including video with audio and 4K (except proprietary function like Sony noise reduction and other DRM related fonctions).
tiliarou said:
I would gladly put 20€ if the camera support the following:
Z3 dual (D6633/D6683), noise reduction, all feature of original sony camera app including video with audio and 4K (except proprietary function like Sony noise reduction and other DRM related fonctions).
Click to expand...
Click to collapse
That is never gonna happen

Why are we working on Oreo???

Why are we working on android Oreo? Should we try to perfect Nougat first. I see this so much with other devices, instead of having a few perfect roms you have a ton of half baked ones.
I'm running this device on Oreo and it works perfectly well for my needs. Its not my day to day tablet, but as a backup tablet, its there when I need it and does what I need it to. Why wouldn't they work on Oreo? There's no such thing as a perfect rom and nobody is ever going to make one due to limitations in hardware and open source drivers etc....
Personally, I'm happy that they have brought the latest incarnation of Android to this device and look forward to watching it improve with each new release.
lmulli said:
I'm running this device on Oreo and it works perfectly well for my needs. Its not my day to day tablet, but as a backup tablet, its there when I need it and does what I need it to. Why wouldn't they work on Oreo? There's no such thing as a perfect rom and nobody is ever going to make one due to limitations in hardware and open source drivers etc....
Personally, I'm happy that they have brought the latest incarnation of Android to this device and look forward to watching it improve with each new release.
Click to expand...
Click to collapse
>No such thing as a perfect rom
what are you talking about? Nougat on my RAZR M (just as old as the Nexus 10) runs flawlessly, and everything functions, so yes, there is such a thing as a perfect rom (or at least one with minimal bugs)
Most all roms have all functions on my ancient OG Nexus 7 (albeit a bit slow)
>Running oreo
HW video playback doesn't work, so no youtube app or netflix
Camera is still broken (some people need it for conference calls and hangouts chats)
--flash is broken too (you usually don't need it, but for those few situations you do, this is quite annoying)
Bluetooth wifi bug persists (turning on bluetooth and connecting a device makes wifi slow down and then disconnect)
My point is that we shouldn't just ditch/give up on fixing old bugs just to pursue a newer version of android. I'd rather run stable and fast Nougat than a half baked Oreo or Nougat build any day.
I know development is hard (my build set up errors out like no other) but that is just the reason we need to fix these things before wasting our time on something that will be harder to fix.
Galaxyninja66 said:
>No such thing as a perfect rom
what are you talking about? Nougat on my RAZR M (just as old as the Nexus 10) runs flawlessly, and everything functions, so yes, there is such a thing as a perfect rom (or at least one with minimal bugs)
Most all roms have all functions on my ancient OG Nexus 7 (albeit a bit slow)
>Running oreo
HW video playback doesn't work, so no youtube app or netflix
Camera is still broken (some people need it for conference calls and hangouts chats)
--flash is broken too (you usually don't need it, but for those few situations you do, this is quite annoying)
Bluetooth wifi bug persists (turning on bluetooth and connecting a device makes wifi slow down and then disconnect)
My point is that we shouldn't just ditch/give up on fixing old bugs just to pursue a newer version of android. I'd rather run stable and fast Nougat than a half baked Oreo or Nougat build any day.
I know development is hard (my build set up errors out like no other) but that is just the reason we need to fix these things before wasting our time on something that will be harder to fix.
Click to expand...
Click to collapse
If you know how to fix the issues on Nougat, nobody will stop you.
The Devs. which are still supporting the N10 said that they are not specialists for the open issues like camera, so they can't fix it. We should be happy that they try to make the best rom which they are capable and motivated for Nougat/Oreo etc.
tim-scrap said:
If you know how to fix the issues on Nougat, nobody will stop you.
The Devs. which are still supporting the N10 said that they are not specialists for the open issues like camera, so they can't fix it. We should be happy that they try to make the best rom which they are capable and motivated for Nougat/Oreo etc.
Click to expand...
Click to collapse
>making the best rom which they are capable
they aren't though, that's my point. They are slowly moving on to building oreo instead of trying to fix nougat which would both be easier and more beneficial to the community.
>If you know how to fix the issues on Nougat, nobody will stop you
I obviously don't (not that I'm not trying to), and part of my point is that the people who are the most competent (not competent, just the most competent, if you know what I mean) would get on the camera fix choo choo train, we could probably have a fix sooner rather than never.
Galaxyninja66 said:
>making the best rom which they are capable
they aren't though, that's my point. They are slowly moving on to building oreo instead of trying to fix nougat which would both be easier and more beneficial to the community.
>If you know how to fix the issues on Nougat, nobody will stop you
I obviously don't (not that I'm not trying to), and part of my point is that the people who are the most competent (not competent, just the most competent, if you know what I mean) would get on the camera fix choo choo train, we could probably have a fix sooner rather than never.
Click to expand...
Click to collapse
Got your point. Nevertheless if the developers are not willing or capable doesn't matter. It's their decision and they owe us nothing. If you read the different threads each dev. said why he didn't fix e.g. camera.
tim-scrap said:
Got your point. Nevertheless if the developers are not willing or capable doesn't matter. It's their decision and they owe us nothing. If you read the different threads each dev. said why he didn't fix e.g. camera.
Click to expand...
Click to collapse
link me, I have been looking for explanations on the camera for ages now. I didn't know if it was a problem with the Exynos framework for the camera or Nougat/Oreo themselves.
Galaxyninja66 said:
link me, I have been looking for explanations on the camera for ages now. I didn't know if it was a problem with the Exynos framework for the camera or Nougat/Oreo themselves.
Click to expand...
Click to collapse
Sorry my friend I will not read all posts of the last roms and why scanno, followmsi and the others are not fixing the open topics like camera, etc. That's your job. And if it is still not clear for you, you can ask the last active dev. (followmsi). he just pointed out today why he will not do so. Just read the posts around N10.
Galaxyninja66 said:
link me, I have been looking for explanations on the camera for ages now. I didn't know if it was a problem with the Exynos framework for the camera or Nougat/Oreo themselves.
Click to expand...
Click to collapse
Marshmallow is the last version of Android where everything works right on the Nexus 10. I don't have links but from everything I have seen/read, the devs can't do anything about the camera after Marshmallow. Google isn't giving the devs anything to work with anymore so stuff has to be ported or fixed by the devs alone. And I do beleive it has something to do with the hardware. But as it stands, Nougat is pretty flawless except for the camera. And Oreo is getting worked on to fix the HW Video Playback and other bugs which I'm sure they'll get fixed eventually. But most of the issues lie with the hardware. There's nothing much any dev can do about certain bugs. At this point, it's either live with the bugs or move on from the Nexus 10.
jsgraphicart said:
Marshmallow is the last version of Android where everything works right on the Nexus 10. I don't have links but from everything I have seen/read, the devs can't do anything about the camera after Marshmallow. Google isn't giving the devs anything to work with anymore so stuff has to be ported or fixed by the devs alone. And I do beleive it has something to do with the hardware. But as it stands, Nougat is pretty flawless except for the camera. And Oreo is getting worked on to fix the HW Video Playback and other bugs which I'm sure they'll get fixed eventually. But most of the issues lie with the hardware. There's nothing much any dev can do about certain bugs. At this point, it's either live with the bugs or move on from the Nexus 10.
Click to expand...
Click to collapse
I'll probably live with the bugs for a bit, I don't use the camera much, but when I do, its REALLY convenient. Marshmallow works great, and worst case I sell my N10 and grab a Nexus 9
Galaxyninja66 said:
I'll probably live with the bugs for a bit, I don't use the camera much, but when I do, its REALLY convenient. Marshmallow works great, and worst case I sell my N10 and grab a Nexus 9
Click to expand...
Click to collapse
Yeah, don't get a nexus 9. Oreo has the same problems (no h/w video decoding, no camera) on N9. I've pretty much given up on Android tablets (I own 4, Touchpad, N10, N9 and Amazon Fire w/ LineageOS), it looks like google has too.
funkybrunk said:
Yeah, don't get a nexus 9. Oreo has the same problems (no h/w video decoding, no camera) on N9. I've pretty much given up on Android tablets (I own 4, Touchpad, N10, N9 and Amazon Fire w/ LineageOS), it looks like google has too.
Click to expand...
Click to collapse
I can't, I love android tablets. They are a blast to use, and I use them much more often than my phone. To each their own, but frankly Google can suck it if they think people will stop using tablets.
The point is thet when android 8 wil works on nexus 10 all newer androids will work to thanks to project treble.
source.android.com/devices/architecture/treble
sagu55 said:
The point is thet when android 8 wil works on nexus 10 all newer androids will work to thanks to project treble.
source.android.com/devices/architecture/treble
Click to expand...
Click to collapse
iirc project treble was only for devices shipping with oreo out of the box, and was only a requirement, i.e. you must have a compatible AOSP factory image that is compatible with other treble devices (which doesn't count the N10 as it shipped with 4.2). I'll give that link a read but I as far as I currently know it doesn't support the N10
@Galaxyninja66 to fix the camera you need to port the old api1 camera to nougat/Oreo.
The api2 camera code was removed entirely from Android, that's why the camera stopped working.
The reason nobody is working on this is because it takes a lot of time to do that and none of the active devs even use the camera
tetsuo55 said:
@Galaxyninja66 to fix the camera you need to port the old api1 camera to nougat/Oreo.
The api2 camera code was removed entirely from Android, that's why the camera stopped working.
The reason nobody is working on this is because it takes a lot of time to do that and none of the active devs even use the camera
Click to expand...
Click to collapse
I also noticed while poking around in the camera HAL that a TON of values were just missing entirely. I would love a working camera but frankly it doesn't seem worth the work if it means either A: porting a deprecated API or B: rebuilding an entirely new one
*sigh* and the layer of dust on top of the Nexus 10 gets a little thicker.
Everyone else is doable tho
considering what an excellent tablet the Nexus was in its brief heyday, this is all very depressing! I really hate how valuable devices can be turned into landfill so gratuitously...

Solved Xperia AOSP Problems - Better as Stock

Hey Folks, while working on My next Snappatch Version was i able to fix the biggest Problems on the XZ Premium which should also affect other Xperias. Here are the main Points:
-Camera Noise (Solved)
-Display Quality (Solved)
-Audio Output Quality (Solved)
-Microphone Handling (Solved)
In conlcusion:
I added and enabled some Camera Services and Functions to enhance the Quality and to allow full Google Camera Mod Support.
I added and enabled Display Services and Functions to deliver a more Natural Output besides HDR Support and Adaptive Backlight capabilities.
I added and enabled Audio Services, Functions and Libraries from Qualcomm and SONY Oreo Firmwares to enhance the Output Quality over all Sources like Videos, Music and the main System.
Last but not least better Microphone Handling. Adapted and ehanced from many Android Devices and Qualcomm Documentations to deliver better Recognition and Input Quality over both Mics on top and bottom of the Device.
Nothing against switching from Stock to AOSP anymore. The benefits of Snappatched AOSP over Stock are huge. Latest SDK, full Substratum Support, better Audio and Visual Quality (In and Output), better Performance (Shadowgun Ledgends on Ultra - 60FPS, No heat, no glitches), more freedom of UI Layouts, better App Support, faster Storage Speeds, newer Kernel, Smoother UI, Adaptive Icon Support, Pixel Features and so on. The Snappatch for the XZP is coming soon and i Hope i can raise the Interest on AOSP on Xperias with this!
Forget Stock! This is the next Level! Love My XZP now...
Stay tuned and try it by Yourself!
I hope that you are right. But i want to try it very bad want i want a good working aosp! I CANT WAIT!!!
I'm on 8142 dual SIM I'm willing to try too
:cyclops: Ufff!!! sounds amazing !!! can't wait to test it
G8142 here also. Can't wait to try this out
I think I will unlock my bootloader ?
Can't wait for some reviews
I would really like to get some advanced Feedback and compares between Stock and AOSP. RAW alone should be worth the Bootloader unlock and going away from Stock. SONY does a really great Job on the Sources for our AOSP Bases and everything runs really well compared to other Devices like from LG. One Thing that really bothers Me is the buggy TWRP on our XZP. CPU Temp isn't showing right, MTP fails 90% of the Time and AROMA has a Displaying Bug. Since the Snappatch is coming with My own crafted AROMA Installer will we face a invisible Utility, but i will make a Video showing how to easily flash the Patch anyways on our Devices (Side by Side with working AROMA on the Axon 7).
Hope @Myself5 can solve the TWRP Issues one Day, and that more Users will pay attention to him and his Work on our Forums! Thanks a lot Mate for contributing that much to our Devices, and Sorry for People like this "FartyParty" Guy! Much respect for You, i know how it feels to be on XDA sometimes...
Miustone said:
Hey Folks, while working on My next Snappatch Version was i able to fix the biggest Problems on the XZ Premium which should also affect other Xperias. Here are the main Points:
-Camera Noise (Solved)
-Display Quality (Solved)
-Audio Output Quality (Solved)
-Microphone Handling (Solved)
In conlcusion:
I added and enabled some Camera Services and Functions to enhance the Quality and to allow full Google Camera Mod Support.
I added and enabled Display Services and Functions to deliver a more Natural Output besides HDR Support and Adaptive Backlight capabilities.
I added and enabled Audio Services, Functions and Libraries from Qualcomm and SONY Oreo Firmwares to enhance the Output Quality over all Sources like Videos, Music and the main System.
Last but not least better Microphone Handling. Adapted and ehanced from many Android Devices and Qualcomm Documentations to deliver better Recognition and Input Quality over both Mics on top and bottom of the Device.
Nothing against switching from Stock to AOSP anymore. The benefits of Snappatched AOSP over Stock are huge. Latest SDK, full Substratum Support, better Audio and Visual Quality (In and Output), better Performance (Shadowgun Ledgends on Ultra - 60FPS, No heat, no glitches), more freedom of UI Layouts, better App Support, faster Storage Speeds, newer Kernel, Smoother UI, Adaptive Icon Support, Pixel Features and so on. The Snappatch for the XZP is coming soon and i Hope i can raise the Interest on AOSP on Xperias with this!
Forget Stock! This is the next Level! Love My XZP now...
Stay tuned and try it by Yourself!
Click to expand...
Click to collapse
dude send your paypal account, dinner on me <3
cant wait to see this baby up and running
Yes I agree we all should donate for all the hard work and time invested yes send me your PayPal address
Miustone said:
I would really like to get some advanced Feedback and compares between Stock and AOSP. RAW alone should be worth the Bootloader unlock and going away from Stock. SONY does a really great Job on the Sources for our AOSP Bases and everything runs really well compared to other Devices like from LG. One Thing that really bothers Me is the buggy TWRP on our XZP. CPU Temp isn't showing right, MTP fails 90% of the Time and AROMA has a Displaying Bug. Since the Snappatch is coming with My own crafted AROMA Installer will we face a invisible Utility, but i will make a Video showing how to easily flash the Patch anyways on our Devices (Side by Side with working AROMA on the Axon 7).
Hope @Myself5 can solve the TWRP Issues one Day, and that more Users will pay attention to him and his Work on our Forums! Thanks a lot Mate for contributing that much to our Devices, and Sorry for People like this "FartyParty" Guy! Much respect for You, i know how it feels to be on XDA sometimes...
Click to expand...
Click to collapse
Man this is wonderful a i cant wait for your patch,but twrp,i remember you created a patch called light patch and aroma installer on that worjs with our device,[email protected] he created carbon rom and twrp for G8141 so carbon works for us but twrp not.
madshark2009 said:
dude send your paypal account, dinner on me <3
cant wait to see this baby up and running
Click to expand...
Click to collapse
grodri19721 said:
Yes I agree we all should donate for all the hard work and time invested yes send me your PayPal address
Click to expand...
Click to collapse
That makes Me very glad and proud, Thanks Guys! Sadly can i not use PayPal, but i would really appreciate if People would Donate to My Mother. She had a Hard Time and is now caring My Grandma which is diseased. I think she would be very thankful and happy about some Donations based on My Work here. I will talk to her and if it's ok do i share her Paypal Address on My Thread or Signatur somehow. Think that would be a nice Idea if You're also ok with that!
Blackghosthm said:
Man this is wonderful a i cant wait for your patch,but twrp,i remember you created a patch called light patch and aroma installer on that worjs with our device,[email protected] he created carbon rom and twrp for G8141 so carbon works for us but twrp not.
Click to expand...
Click to collapse
Strange. I Googled a lot about this and this was always a Issues with some TWRP Recoveries. Most of the Time did it helped to use older TWRP Images but the last one gives just a Black Screen after booting into it. I will test a Copy of My old Light Patch again and take a look on whats different! Thanks for the Hint!
Miustone said:
That makes Me very glad and proud, Thanks Guys! Sadly can i not use PayPal, but i would really appreciate if People would Donate to My Mother. She had a Hard Time and is now caring My Grandma which is diseased. I think she would be very thankful and happy about some Donations based on My Work here. I will talk to her and if it's ok do i share her Paypal Address on My Thread or Signatur somehow. Think that would be a nice Idea if You're also ok with that!
Strange. I Googled a lot about this and this was always a Issues with some TWRP Recoveries. Most of the Time did it helped to use older TWRP Images but the last one gives just a Black Screen after booting into it. I will test a Copy of My old Light Patch again and take a look on whats different! Thanks for the Hint!
Click to expand...
Click to collapse
If it possible release your patch for less than 5 hours because my internet time is going to end.please.
How was RAW support achieved?
From what I've seen, this wasn't possible before because there were no drivers that enabled that with the used camera chip.
And there's still one thing missing; SloMo support. Is there a chance this can be added as well?
Blackghosthm said:
If it possible release your patch for less than 5 hours because my internet time is going to end.please.
Click to expand...
Click to collapse
I had trouble with the Camera Configs (Camera not starting anymore), but solved it and added more of them. Last remaining Problem are Issues with Google Service Audio (Music and Video not playing due to failing Audio Configs). Think i need more Time to solve this, but the release is close...
4rz0 said:
How was RAW support achieved?
From what I've seen, this wasn't possible before because there were no drivers that enabled that with the used camera chip.
And there's still one thing missing; SloMo support. Is there a chance this can be added as well?
Click to expand...
Click to collapse
It's all there on AOSP. Camera2 API is supported but not configured right (There are X Lines for the Cameras), i've seen the same on the Z1 and Z3 (https://forum.xda-developers.com/cr...ussion-development-custom-rom-t3479108/page11) some Years back, and i was sure it's all depending on this right now. Other Xperias may have the same Camera Problems since AOSP is coming with just the barely minimum of Build Properties and Configs. That's also the Case on the most other Devices and AOSP based ROM and one of the Reasons for doing My Patch. Some missing Things are causing Issues (Like Microphone Problems), and others do just bring a lack of Features (Like with the Camera and Display, Audio, etc.).
It's pretty Time intense to test all this Entries and Values but it's really worth the Time. And if i would do a OS would i start with that Things before changing the Kernel and adding ROM Features, but i can only talk for Me. Not sure how much Time ROM Devs put into building of AOSP for the own Devices, but i work for sure at least 40 Hours on One Major Release of My Patch (Including copying, flashing, testing and editing).
AROMA was also really Time Intense but i removed the Installer over Night and edited the Updater Script to flash the recommended Options without it. Here is a little List of what gets flashed:
-Original Oreo Pixel Bootanimation
-Original Oreo Pixel Ringtones, Alarms, Notifications
-HTC U 11 UI Sounds, Ringtones, Alarms, Notifications
-Prop Patch (Including many changes and Configs)
-Snappatch Core System (Including the mainly needed Content)
-Snappatch Audio System (Based on XZ Premium Oreo Stock)
-Snappatch Emojis (EmojiOne replacement Font)
-Magisk Stable V16
-Busybox with many Applets, SElinux & Magisk Support
-GApps (Barely minimum Set)
And that's it for now. It includes all of the Features of the Patch, less optional but i can ensure a great Experience with this Setup! Like said am i now about to fix the last Bugs which are Audio Config related and after that will come the Thread with the new Release. Hope You will like it Folks!
BR
Stupid xda -__-
Keep up the good work brother
I'm done for now! Release is in the next 24 Hours...
Changelog can be found here: https://docs.google.com/document/d/1ak5DsenMjuSyypPBAjQact6MhtsE2MRFlvCHLTn9uHA/edit?usp=sharing
I removed the Audio System for now due to Issues with Xperias AOSP ROMs but i'll work on it again after releasing the actual Patch. Sounds already a lot better even without the replacement Libs and Configs! Stay tuned...
Sony 8142 dual SIM ?? Please
grodri19721 said:
Sony 8142 dual SIM ?? Please
Click to expand...
Click to collapse
Yes
can't wait to have a try.
bro you've contributed a lot to our device
Thank you so much!

Categories

Resources