View Single Post
Posts: 202 | Thanked: 385 times | Joined on Jul 2018
#53
Originally Posted by rinigus View Post
Note that XZ2c is not working yet. We started on adjusting builds for it, as we did earlier for XZ3. See progress at https://github.com/sailfishos-sony-tama/main/issues/38

As for camera, it is not going to be ever as good as on stock. At least I don't expect it. Development of the camera functionality for AOSP is around kernel 4.14 which is linked to android 10. To get an idea of what's going on, see https://forum.xda-developers.com/xpe...0-0r1-t3975009

In context of SFOS, 4.14 camera development is not possible to carry over to Linux 4.9 that we use now. I hope to be able to just bump kernel version with new blobs for 4.14. If it fails, we will have to make new port on the basis of AOSP10. Realistically, if it goes that way, its probably autumn 2020.

There are few IFs in these scenarios, as you could see. So, I want people to know what they are getting into. We have risks, but we can try to work around them the best way we can.

You could check out at XDA and ask there whether you will get back camera functionality if you flash AOSP and then return back to stock using stock flasher. As far as I know, if you unlock, you will loose DRM keys. But whether they are needed for camera - I am not sure on newer Xperias. Also, you will loose stock OTA updates, if I understood it correctly.
I had XZ2C when Pie was released, and unlocked, and camera was fine - as good as stock as far as I could tell. As of Pie, Sony changed it so losing DRM wouldn't break camera, https://www.google.com/url?q=https:/...mR-XRZOFL24CrT (in previous Xperias like Z1C, Z3C, it would cause camera to be worse, since you would lose Sony-specific camera features and functions, but with XZ2C and others, it would actually break it, on Oreo). So if it's just a matter of what you lose with unlocking, it should be fine, but if there's other issues related to kernel or port-specific things, maybe not.

-- Sent from my Palm Pre using Forums
 

The Following User Says Thank You to levone1 For This Useful Post: