[ROM][FINAL][9.0] LineageOS 16.0 for Xperia Z

[Flounderist]

Yeah and that's great, but why not add Treble support?

The device latest official firmware is a 5.1 one. Treble support start from devices shipped with 8.0. It is impossible to get treble on such old device, and basically useless.

P.s. for the other ones asking if ROM is functional: everything is running fine except:
- auto brightness is quite buggy yet (screen never dims below a certain value). Is much worth keeping it disabled atm.
- for Magisk users: stick on 18.1 version. Latest builds are breaking twrp recovery access.

My two cents: after these bugs are fixed, ROM could be easily moved to an official lineage support.

 

[EliasAlucard]

The device latest official firmware is a 5.1 one. Treble support start from devices shipped with 8.0. It is impossible to get treble on such old device, and basically useless.

So you're saying the firmware isn't updated when what flash LineageOS 16 on an Xperia Z?

P.s. for the other ones asking if ROM is functional: everything is running fine except:
- auto brightness is quite buggy yet (screen never dims below a certain value). Is much worth keeping it disabled atm.
- for Magisk users: stick on 18.1 version. Latest builds are breaking twrp recovery access.

My two cents: after these bugs are fixed, ROM could be easily moved to an official lineage support.

Alright. Auto brightness isn't a big deal to me personally. But does it run smooth? I flashed LineageOS 14.1 on my Xperia Z, and while everything works okay, it's a bit slow. It shouldn't be slow, right? I mean I'm not expecting my Xperia Z running LineageOS to be as smooth and fast as my Xperia 1, but still, I expected a much fast faster experience.

 

[Flounderist]

So you're saying the firmware isn't updated when what flash LineageOS 16 on an Xperia Z?

Do you know, at least, how Treble works?

About performance: it is a 2012 device with a 2012 CPU. For me, I can't find any difference in performance since CM13 times.

If you want to get it a little snappier, change data and cache to f2fs and keep it with less apk running as possible.

 

[EliasAlucard]

Do you know, at least, how Treble works?

Not at the deeper level, no. But you still didn't answer my question So when we flash LineageOS 16 on an Xperia Z, are you saying the firmware on it is still Lollipop?

About performance: it is a 2012 device with a 2012 CPU. For me, I can't find any difference in performance since CM13 times.

If you want to get it a little snappier, change data and cache to f2fs and keep it with less apk running as possible.

It was released in 2013, but yeah I get it, can't expect blazing fast speeds with it.

 

[MartinX3]

Not at the deeper level, no. But you still didn't answer my question So when we flash LineageOS 16 on an Xperia Z, are you saying the firmware on it is still Lollipop?

Yes, unless the source code of the closed source hardware drivers magical appears or a professional reverse engineers these under hard work and tries to mainline this device into the official Linux kernel.

This and introducing treble support is very hard, much time consuming work.

---------- Post added at 05:34 PM ---------- Previous post was at 05:32 PM ----------

P.s. for the other ones asking if ROM is functional: everything is running fine except:
- auto brightness is quite buggy yet (screen never dims below a certain value). Is much worth keeping it disabled atm.
- for Magisk users: stick on 18.1 version. Latest builds are breaking twrp recovery access.

You mean these bugs came into the new version or just unchanged compared to the previous version?
(I maintain this device for my dad and he is far away at the moment)

 

[Flounderist]

Not at the deeper level, no. But you still didn't answer my question So when we flash LineageOS 16 on an Xperia Z, are you saying the firmware on it is still Lollipop

A ROM is usually made of a boot and a system img, plus the stuff that are needed for flashing them. So modem, bootloader, and so on are still the same you had on latest official firmware.

Treble, roughly, moves the vendor folder from system to a detached partition. Doing so, you can boot a generic system image (gsi) on top of the original firmware.

---------- Post added at 09:56 PM ---------- Previous post was at 09:50 PM ----------

You mean these bugs came into the new version or just unchanged compared to the previous version?

The previous version had no sensor working at all (proximity, rotation, brightness), so comparing with the previous build, it is a big game changer.
The brightness remain stuck above 70% even on darkness, unless you turn it down manually.
The Magisk issue isn't strictly ROM related.

 

[MartinX3]

Does anyone know how I can boot the recovery?
I'm still on the april build.
I tried to reboot into recovery and "fastboot boot twrp.img" with the may 3.3.1 twrp (CM14.1).
It just jumps into LineageOS.

 

[Flounderist]

Does anyone know how I can boot the recovery?

Are you using latest Magisk by any chance?
Builds after 18.1 broke twrp access.

Otherwise, reboot and when you get vibration+pink led, press volume up. The led would change to yellow and you should boot in twrp.

 

[MartinX3]

Are you using latest Magisk by any chance?
Builds after 18.1 broke twrp access.

Otherwise, reboot and when you get vibration+pink led, press volume up. The led would change to yellow and you should boot in twrp.

Thanks for your fast reply!

I'm on 18.1 at the moment.

oh. nothing worked, except pressing VolUP at the right moment.
Thank you!

 

[ISPG]

Are you using latest Magisk by any chance?
Builds after 18.1 broke twrp access.

Otherwise, reboot and when you get vibration+pink led, press volume up. The led would change to yellow and you should boot in twrp.

Hi Flo ... some time without contact you
I am following this thread about Android 9 and reading your always helpful tips. After my troubles with A8.1 and Magisk 19, I recovered full funcionality
on my Xperia Z, and I continue updating with the Nightlies ROM for 8.1. Any problem in this case, and of course, maintaining Magisk always in 18.1.
I see that basically only brightness is the pending bug. Sensors are corrected and Magisk is not a problem of Android.
But nonetheless I would like to know if this version 9 is higher than Nightly 8.1. Is it worth to upgrade it?
I am aware that with 9, the updatings won't be frecuent as Nightlies with monthly patch for security, for example.
If you think that yes, it is worth it, I have seen that the size of ROM 9 is 420 Mb, more than typical 360 Mb in Nightlies.
Is it normal?
Is Android 9 heavier than Android 8.1?
Does this ROM include Magisk 18 as Nightlies does?
And finally, the updating/upgrading from 8.1 to 9 is as usual as in Nightlies? Without any wipe data if you don't want?
I continue with TWRP 3.3.1.0 with any problems to updating Nightlies, I guess that it will work as well for this updating.

Thanks and regards,

 

[Zerikwan]

@ISPG

Here's some quick answers from my point of view.

Q: how about updates frequency?
A: this is still on beta stage. As soon as we get official, the update frequency will be the same as nightlies.

Q: the size is big, is it normal?
A: I'm not a developer, but higher android version might comes with higher size of the ROM

Q: is 9 heavier than 8.1?
A: a little bit, maybe..

Q: Is this ROM include Magisk?
A: you mean by default? No. You must flash it after flashing ROM.
If what you mean is Magisk 18 compatible, I don't know, because I use addon SU.

Q: how about upgrading from 8.1 to 9?
A: Maybe you can, after the ROM goes official. I prefer clean flash btw.

Q: Is it worth to upgrade?
A: Absolutely. At least for me. But I'll wait for official status.

 

[MartinX3]

Sadly with the new release
The screen is sometimes dead (no touch)

The phone reboots now instead of shutdown

If that are not known bugs, I'll try to get logs.

 

[Zerikwan]

Sadly with the new release
The screen is sometimes dead (no touch)

The phone reboots now instead of shutdown

If that are not known bugs, I'll try to get logs.

Mine too.
I have to lock and unlock the screen again with power button.

I got both of the bugs since first release.

 

[Flounderist]

@ISPG

I 100% agree with @Zerikwan.
Oreo and Pie builds have overall the same performance.
Feel free to go for it with a clean flash.

 

[CyberWalkMaN]

New build uploaded (lineage-16.0-20190824-UNOFFICIAL-yuga.zip), major changes since May:

• All sensors works now (Thanks to @Chippa_a)
• Manual network selection fixed
• Telegram calls fixed (Need to confirm)
• FM Radio fixed
• Small gps improvement
• Performance improvement
• Updated kernel (fixed bug with rebooting instead of shutting down and some other bugs), also we now use binder and lmk from AOSP 3.18 kernel
• SELinux denials resolved at 90%
• Magisk issue fixed
• Android 9.0.0_r46 (August security patches)

Addonsu is already included, you can enable root access in the developer settings

 

[MartinX3]

New build uploaded (lineage-16.0-20190824-UNOFFICIAL-yuga.zip), major changes since May:

• All sensors works now (Thanks to @Chippa_a)
• Manual network selection fixed
• Telegram calls fixed (Need to confirm)
• FM Radio fixed
• Small gps improvement
• Performance improvement
• Updated kernel (fixed bug with rebooting instead of shutting down and some other bugs), also we now use binder and lmk from AOSP 3.18 kernel
• SELinux denials resolved at 90%
• Magisk issue fixed
• Android 9.0.0_r46 (August security patches)

Addonsu is already included, you can enable root access in the developer settings

Thank you very muuuuch

 

[ISPG]

@Zerikwan; @Flounderist thank you very much to both for your help and comments.
Surely I´ll try this new build.

 

[MartinX3]

Mine too.
I have to lock and unlock the screen again with power button.

I got both of the bugs since first release.

You said you have to lock and unlock again
It sadly doesn't help here
The exact area of the navigation bar at the bottom has no touch
I would consider a hardware defect
But the dead area fits exactly the navbar area.
Maybe coincidence.
Rotating the screen by 180° doesn't move the dead area.
It stays the same.
Using the extended desktop to hide the navbar area doesn't help, too

So either it is a bug or the screen is starting to die (I hope not)

 

[EliasAlucard]

Any estimation when this will hit stable?

 

[MartinX3]

Sadly the camera is unstable and sometimes needs a restart to become functional again.