[ROM][NIGHTLIES][7.1] LineageOS 14.1 for Xperia ZL

[Daedroza]

#include <std_disclaimer.h>
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

About LineageOS

LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.

All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

Official LineageOS website : http://lineageos.org
​

Downloads Links

LineageOS 14.x (Unlocked Bootloader) :
Nightlies : https://download.lineageos.org/odin

Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.

Informations and references :
About LineageOS updates : ChangeLog available on http://www.cmxlog.com/14.1/odin/
About LineageOS device side : See my GitHub trees linked below
​

Flashing and updating

LineageOS clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot

LineageOS update / upgrade :
- (Information) Don't wipe anything unless you want to
- (CM / UNOFFICIAL) Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot

LineageOS addonsu for root access :
- (Information) Read the Root section of the Q&A thread
- (Download) Download the addonsu for arm : LineageOS Downloads / Extras
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot
​

About the builds

Device tree : https://github.com/fusion3-common/android_device_sony_Odin/commits/cm-14.1
Kernel sources : https://github.com/fusion3-common/android_kernel_sony_apq8064/commits/cm-14.1
Vendor blobs : https://github.com/fusion3-common/proprietary_vendor_sony/commits/cm-14.1
​

Issues and reports

- Report issues only if you are using the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
​

About LineageOS Legal : http://lineageos.org/legal/

The LineageOS team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!
[/INDENT]



LineageOS available for Odin also thanks to :

- The LineageOS Team
- The CyanogenMod Team
- Everyone involved in working and testing​

XDA:DevDB Information
[ROM][NIGHTLIES][7.1] LineageOS 14.1 for Xperia ZL, ROM for the Sony Xperia ZL

Contributors
Daedroza, AdrianDC, Chippa_a, Olivier, Namelos, CyberwalkmaN, sigprof
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x

Version Information
Status: Testing

Created 2017-07-17
Last Updated 2017-11-10

 

[Daedroza]

Reserved

FEATURES AND ISSUES

- Boot : Ok
- GApps : OpenGApps Micro Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Fully enforced

 

[esgwpl]

Thanks and good luck on getting this official.

 

[[email protected]]

Thanks for your hard work,it works fine

 

[Astra7525]

Successfully upgraded from Chippa_a's unofficial Lineage 170413 build without wipe. Thanks.

 

[saddambea]

after bootind in recovery (twrp), wiped cache and data, flashed the zip lineage-14.1-20170716-UNOFFICIAL-odin.zip and open_gapps-arm-7.1-mini-20170722.zip and rebooted. After that, only black screen and no boot into system, only fastboot or flash mode...

previously using a stock rom in 5.1.1 with root and recovery.

any help?

ps: after that, tried to flash the boot.img in fast boot mode, get this error:

>fastboot flash boot c:\boot.img
sending 'boot' (14972 KB)...
OKAY [ 0.293s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.297s

PS 2: tried flashing a ftf via flashtool, but get some errors too...
23/036/2017 18:36:01 - INFO - Opening device for R/W
23/036/2017 18:36:03 - INFO - Reading device information
23/036/2017 18:36:12 - INFO - Unable to read from phone after having opened it.
23/036/2017 18:36:12 - INFO - trying to continue anyway
23/036/2017 18:36:12 - INFO - Phone ready for flashmode operations.
23/036/2017 18:36:12 - INFO - Opening TA partition 2
23/036/2017 18:36:12 - INFO - Start Flashing
23/036/2017 18:36:12 - INFO - No loader in the bundle. Searching for one
23/036/2017 18:36:16 - INFO - Processing loader.sin
23/036/2017 18:36:16 - INFO - Checking header
23/036/2017 18:36:16 - ERROR - Processing of loader.sin finished with errors.
23/036/2017 18:36:16 - INFO - Ending flash session
23/036/2017 18:36:16 - ERROR - Error in processHeader : 22 : O dispositivo não reconhece o comando.
23/036/2017 18:36:16 - ERROR - Error flashing. Aborted
23/036/2017 18:36:16 - INFO - Device disconnected

 

[NamenIos]

@saddambea looks like you bootloader is not unlocked. Is that possible? If you back up you TA partition with twrp and recover from those backups you will relock your bootloader.

 

[saddambea]

@saddambea looks like you bootloader is not unlocked. Is that possible? If you back up you TA partition with twrp and recover from those backups you will relock your bootloader.

yes, i think it´s possible, my bl may be locked. couldn´t unlock via fastboot after that
and now, i can´t even boot to recovery. tried to flash recovery.img through fastboot with no success...

 

[NamenIos]

yes, i think it´s possible, my bl may be locked. couldn´t unlock via fastboot after that...

What error did you get? Maybe you have to go back to stock via flashtool for this.

... and now, i can´t even boot to recovery.

This should be normal if you used Dual Recovery on the stock rom before. Dualrecovery is on the /system partition, that you wiped while flashing.

... tried to flash recovery.img through fastboot with no success...

This can't work as we don't have have a recovery partition. Our recovery is either in the boot.img or the system partition. LineageOS uses the boot.img and optionally then boots the recovery in the FOTA Kernel partition if you press vol up.

 

[Daedroza]

Uploading a new build as we speak. The changelog since 2016 is (I'm just being vague here, I don't remember all the issues, but I do have all the logs with me, if someone is interested):
1. Fix ancient F2FS bug (Specific to Fusion3)
2. Fix https://forum.xda-developers.com/showpost.php?p=69849473&postcount=1243
3. Fix https://forum.xda-developers.com/showpost.php?p=68245138&postcount=1130
4. Fix for input_evdev specific to us
5. Fix for SWAP
6. Fix for C5502 Double Tap to Wake Screen Freeze.
7. Many other improvements like ZRAM / Process Reclaim / Perf / mmc / Anon Reclaim etc
8. Changes from Chippa_a for XML audio configuration is also picked, I don't know maybe you will see a improvement @gorillanobka?

I haven't gone much into detail, but please send logs (dmesg / last_kmsg / logcat) wherever possible if you face something. At the moment, I only have C5502 (Fusion3 Dogo) with me. Yuga / Odin has hardware specific to them (other than chipset), so I won't be able to reproduce them on my device if you get some event changes / sensors changes.

I've also included a minor hack for auto-brightness. Let me know how you feel about it.
Please give it a go? Thanks

 

[gorillanobka]

Thank you Daedroza!
You're a scholar and a gentleman. Gimme a week or so ( I am caught up with assignments and exams ) and i will have a look at it...
I'm pretty sure it will be a super stable build as always...
I am already running a Chippa's build with some changes to the XML audio if i am not wrong, and i could already hear some improvements.
The notifications remained very low though... I think the EU specific limitation for the audio needs to be commented / removed in order to see serious improvements .

Kind regards
Gorilla no Baka

Uploading a new build as we speak. The changelog since 2016 is (I'm just being vague here, I don't remember all the issues, but I do have all the logs with me, if someone is interested):
1. Fix ancient F2FS bug (Specific to Fusion3)
2. Fix https://forum.xda-developers.com/showpost.php?p=69849473&postcount=1243
3. Fix https://forum.xda-developers.com/showpost.php?p=68245138&postcount=1130
4. Fix for input_evdev specific to us
5. Fix for SWAP
6. Fix for C5502 Double Tap to Wake Screen Freeze.
7. Many other improvements like ZRAM / Process Reclaim / Perf / mmc / Anon Reclaim etc
8. Changes from Chippa_a for XML audio configuration is also picked, I don't know maybe you will see a improvement @gorillanobka?

I haven't gone much into detail, but please send logs (dmesg / last_kmsg / logcat) wherever possible if you face something. At the moment, I only have C5502 (Fusion3 Dogo) with me. Yuga / Odin has hardware specific to them (other than chipset), so I won't be able to reproduce them on my device if you get some event changes / sensors changes.

I've also included a minor hack for auto-brightness. Let me know how you feel about it.
Please give it a go? Thanks

 

[Linwood.Ferguson]

Thank you for continuing with this phone. I plan to download this new build momentarily and try, but I have two long running issues and wonder if you might comment.

One is that this seems to come from the C6503 which has a different set of cellular bands, and I think that means my C6506 cannot access them. Is that correct? I seem to have poorer coverage in some areas than with the stock Sony software (which is now ancient of course). I have no done a deep dive to see, other than to see cynogenmod now lineage seems to be specific to the less-bands phone modem?

The more specific question is this: after some days or weeks, the phone's display gets laggy on scrolls; two specific places I use a lot are the CNN app and the News360 app. I found a fresh install cleared it up nicely, then over time it gets worse. I experimented (takes a long time as it is reproducible only over a long time) and found it is the Dalvik cache. If I clear that and reboot -- smooth as silk. A couple weeks later, have to do it again. Any thoughts as to what is happening? It's easily fixable now that I know a full install is not needed, but it just seems strange. Anyone else seeing it? Try wiping just Dalvik, see if it helps.

 

[Daedroza]

Thank you for continuing with this phone. I plan to download this new build momentarily and try, but I have two long running issues and wonder if you might comment.

One is that this seems to come from the C6503 which has a different set of cellular bands, and I think that means my C6506 cannot access them. Is that correct? I seem to have poorer coverage in some areas than with the stock Sony software (which is now ancient of course). I have no done a deep dive to see, other than to see cynogenmod now lineage seems to be specific to the less-bands phone modem?

The more specific question is this: after some days or weeks, the phone's display gets laggy on scrolls; two specific places I use a lot are the CNN app and the News360 app. I found a fresh install cleared it up nicely, then over time it gets worse. I experimented (takes a long time as it is reproducible only over a long time) and found it is the Dalvik cache. If I clear that and reboot -- smooth as silk. A couple weeks later, have to do it again. Any thoughts as to what is happening? It's easily fixable now that I know a full install is not needed, but it just seems strange. Anyone else seeing it? Try wiping just Dalvik, see if it helps.

- No idea about phone coverage. I had preferred if you could do a diff with signal measuring app or something of sort? That would give you a base stock result and one from Lineage.

- The phone's display gets slow / laggy / unresponsive systemwide or it just the apps? Maybe both the apps consume a lot of space on internal and cache. Hence you need to clear them.

 

[Linwood.Ferguson]

On the original firmware there was a dialer code to show usable bands; it does not work on LineageOS. I have tried without success to find a way to tell which bands are supported in the current OS. With some playstore apps I can see the current band but not all usable bands.

The original C6506 (odin rimy) documentation listed the bands available, and compared to the C6503 (odin gina). There are a number of differences. The C6506 supports LTE I, IV and XVII that the C6503 does not; the C6503 supports LTE III, VII, VIII and XX that the C6506 does not. My understanding (but I am not certain) is that this is a hardware limitation of the device, which of course corresponds to the stock firmware. It could also be that the radios are the same, but the restriction on bands was purely in software tied to the model.

My reading of old postings on the cynogenmod software was it was based on the C6503, and so my question is what is the result. It seems POSSIBLE that it only then supports the bands they had in common: LTE I and V, which leaves a lot missing. Or it is also POSSIBLE that it supports all the C6503 bands which (again, my loose understanding) were not ideal for US/AT&T use, which is what the C6506 was fo.

Basically I know only enough to wonder if the LineageOS is limiting the bands the phone can use? And how I might tell for sure? And/or if you have all the source, can you tell, or is this buried in the blobs that are opaque?

As to the laggy: I think it is the whole system, but it is hard to say as I'm generally using some app. They do begin to start up slower as well as operate slower, but it is most noticeable on things that scroll. Frankly I would likely not notice other slowness if the scrolling did not hesitate. A list of stories in the CNN app, for example, if you touch and start scrolling hesitates nearly a second before it moves. Clear dalvik and there's no hesitation. It is also worth noting I use very little on the phone - mail, CNN, News360, weatherbug, calendar, and the phone are just about it. All visible resources (that I know how to look at) show lots of free space. Now that I know how to quickly fix it not a big deal.

 

[JLBouras]

Does the IR blaster work with this build? Does it work with other apps like Anymote?

 

[NamenIos]

According to Sonys whitepaper the C6506 should support LTE Band I, Band II, Band IV, Band V and Band XVII (1, 2, 4, 5 and 17). The supported bands are stored in partitions not touched by LineageOS (see here). You have to check which bands your provider uses in your region and then use an app to check if you get connected to which band, I don't think there is an alternative. The old dialer code won't work, as it is sony specific. I too haven't found an app that shows available LTE networks regardless of your contract and possibly this is not even possible on standard Android APIs.

Performance (in scrolling and in general) doesn't seem worse than on stock for me (in fact it feels better). I use F2FS, but I doubt it changes anything on your performance problems. Once we get all this in the official repos and get a weekly build status, there will probably be some experimental stuff that will be tried out and surfaces here. For now the focus is more on getting the officially supported status.

edit:

Does the IR blaster work with this build? Does it work with other apps like Anymote?

Only with one app (the one that worked on CM13), root access and selinux disabled, we have to add file permissions, ownership and selinux rules. This is not yet tested enough though. edit: Just tested with selinux disabled, works well with preconfigured remotes, slightly flaky when learning imo.

 

[Linwood.Ferguson]

According to Sonys whitepaper the C6506 should support LTE Band I, Band II, Band IV, Band V and Band XVII (1, 2, 4, 5 and 17). The supported bands are stored in partitions not touched by LineageOS ....
The old dialer code won't work, as it is sony specific. I too haven't found an app that shows available LTE networks regardless of your contract and possibly this is not even possible on standard Android APIs.

That's the list of the supported bands, but I know I read years ago that the (not sure if this is the right word?) modem used by Cynogenmod for this phone started as the 6503. Does the software incorporated within LineageOS support all bands listed in the partition mentioned?

I tried to find the old discussion I remember without success. Closest I got was this which brings it up (look for "bands"), but people are saying "mine works". The issue of course is if some bands work but not others the phone may "work" but not have the same coverage where you have less bands or more congestion.

I was hoping there was a way to actually query the phone for which have actual hardware+software support, but it sounds like there no longer exists that ability with the loss of that service menu.

Performance (in scrolling and in general) doesn't seem worse than on stock for me (in fact it feels better). I use F2FS, but I doubt it changes anything on your performance problems. Once we get all this in the official repos and get a weekly build status, there will probably be some experimental stuff that will be tried out and surfaces here. For now the focus is more on getting the officially supported status.

Frankly it may have been the same there. I'm wondering if, being news related apps I use most, if they are leaking/cluttering up the cache in some way more than normal use (Dalvik is for the VM, right? Do apps cache data there or just the VM cache app code there?). Regardless, I have an easy workaround, it takes just a few minutes to clear and get back fully up.

I absolutely agree getting fully supported is great. I hope to get a Pixel2 when they come out, and leave this as a backup phone, so would love to get a few more years utility out of it. It's been a really great phone, I still rarely see any with the low percentage of wasted space on the front as this.

 

[CyberWalkMaN]

That's the list of the supported bands, but I know I read years ago that the (not sure if this is the right word?) modem used by Cynogenmod for this phone started as the 6503.

Modem partitions are not affected in case of installation of LineageOS/CyanogenMod. This ROM is universal for all models (C6502/6503/6506).

The supported bands are stored in partitions not touched by LineageOS

 

[Daedroza]

New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)

Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you

 

[AloXado320]

New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)

Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you

And just a day later, August Security Patches was released...