[ROM] LineageOS 17.1/18.1 UNOFFICIAL - (Update: 2022-05-05)

Shall F-Droid be included in the ROM(s)?


  • Total voters
    158
Search This thread

Flamefire

Senior Member
Jul 26, 2013
208
434
Sony Xperia XZ1 Compact
Just a quick update: November build is working! Currently just working on some patches like updated APNs and the usual safetynet fix before I push it out. And I want to make sure it works flashing over the October build.
It will have the fix for IMS for the 17.1 build.
So won't be long. Sorry for the delay, currently a bit more busy due to health issues...
 

rez78

Senior Member
Nov 16, 2017
134
27
Just a quick update: November build is working! Currently just working on some patches like updated APNs and the usual safetynet fix before I push it out. And I want to make sure it works flashing over the October build.
It will have the fix for IMS for the 17.1 build.
So won't be long. Sorry for the delay, currently a bit more busy due to health issues
Great! Please give me istructions to make a donation for your work! :-D
 

Flamefire

Senior Member
Jul 26, 2013
208
434
Sony Xperia XZ1 Compact
Currently uploading the new builds. Gonna take a bit...
The 18.1 version seemingly works, passes SafetyNet etc. but as usual, I don't really test that version although I can now say that it flashes clean over the previous release and boots fine. Thanks to the test phone by @landsome
I tested the 17.1 version the same way: Flash over previous release, boot and SafetyNet is working. However I'll flash that on my own phone tomorrow and test it a bit more "in production". Hence you'll find that in the "Testing Only" folder on AFH until I verified it a bit more. No time left for that today but if you want to give it a try feel free.
As mentioned I fixed the IMS bug on 17.1 and on my phone (October build with only that patch applied) VoLTE and VoWIFI work fine.

As for GPS: The XZ1C has known hardware issues with the GPS antenna. The ROM if flashed correctly works ok although I noticed that GPS is shaky too. Some users reported that squeezing the left edges often helps...

I'll tackle the HD audio stuff later. That needs some more work to do it properly.

Donations: See the initial post and my profile (About section). Always welcome and keeps me motivated to put in a bit of extra effort :) Please note that I often integrate changes from others, like modpunk/derfelot, linckandrea etc. On Github you can usually see that as "authored by X, committed by Flamefire" as I try to keep the author unchanged. So others deserve credit (and donations) too.
 
Last edited:

ezdi

Senior Member
Dec 14, 2010
94
42
I feel it was one of the Ting Data profiles. It looks like it could cause a problem, but I don't see IMS on it like I thought it did.

I thought it was 310/260, but now that I look, I'm not seeing anything in the diff that would explain why it isn't getting loaded any more.

So something in my report is wrong. Sorry, I will investigate more and take notes. Or I wonder if I somehow carried over something from Sony or there's something in that zip I installed that did more than just update the file.

I had remembered correctly. Ting Data was the one I couldn't delete, but I guess it could be a hidden APN as well. The garbage APNs don't even show up after flashing that APN update.
I re-installed stock Pie, verified VoLTE worked, then reset and flashed the v17 Oct build I used before. It forced me to reboot to switch modems to the non-ims, after switching back to ims, VoLTE still didn't work until that APN update.

Saw the new Nov build. With it, VoWiFi can be enabled and works as soon as the ims modem is enabled. VoLTE still didn't work without the APN update. Still having the issue where it needs to be forced to 3G every time it loses signal.

Worth noting that, once I do have an LTE connection, incoming and outgoing calls work and it successfully hands off a VoWiFI call to VoLTE.
 
Last edited:

Flamefire

Senior Member
Jul 26, 2013
208
434
Sony Xperia XZ1 Compact
I had remembered correctly. Ting Data was the one I couldn't delete, but I guess it could be a hidden APN as well. The garbage APNs don't even show up after flashing that APN update.
I re-installed stock Pie, verified VoLTE worked, then reset and flashed the v17 Oct build I used before. It forced me to reboot to switch modems to the non-ims, after switching back to ims, VoLTE still didn't work until that APN update.

Saw the new Nov build. With it, VoWiFi can be enabled and works as soon as the ims modem is enabled. VoLTE still didn't work without the APN update. Still having the issue where it needs to be forced to 3G every time it loses signal.

Worth noting that, once I do have an LTE connection, incoming and outgoing calls work and it successfully hands off a VoWiFI call to VoLTE.
Which APN update do you exactly mean? Basically all APNs from that Google APN list you mentioned are included in the ROM. I don't understand what you mean exactly by APNs you can't delete or are "hidden". But to be honest I don't really understand that APN stuff anyway...

E.g. for your mentioned 310/260 MCC/MNC there are many APN configs: https://github.com/Flamefire/androi...da/config/telephony/apns-conf.xml#L1457-L1489
The "Ting Data" one you mentioned is there twice for some reason which I think is a bug. Maybe you have to delete it twice? Will fix that anyway for the next build.
The APN config list is there, maybe you can help me fix it or provide some information on what is "correct". E.g. the Ting Data stuff looks correct: https://help.ting.com/hc/en-us/articles/205428698-APN-setup-guide So I'm inclined to keep it.

I've noticed the issue about sometimes not being able to get a signal again, and even WiFi seems to be affected by that at times. Not sure how to exactly reproduce this and where that problem could be. Might be deep in Android.
 
Last edited:
  • Like
Reactions: sieghartRM

jmbattle

Member
Jul 3, 2015
18
3
Just a quick update: November build is working! Currently just working on some patches like updated APNs and the usual safetynet fix before I push it out. And I want to make sure it works flashing over the October build.
It will have the fix for IMS for the 17.1 build.
So won't be long. Sorry for the delay, currently a bit more busy due to health issues...
Thanks for updating us on your progress. Are you able to share why the previous builds were unsuccessful, and the steps you had to take to get it working correctly?

I'm very grateful for your continued work on this brilliant little device - keep up the good work!

Cheers,
James
x

ps. Sorry to read about your health issues. I hope you can stay strong, but please don't push yourself too much, or worry about delays. We are just happy that someone is continuing to update LOS for our favourite phone.
 

jmbattle

Member
Jul 3, 2015
18
3
By the way, what do "Fix/enhance wifi display" and "fix some power hints" mean in the November changelog?
 

Flamefire

Senior Member
Jul 26, 2013
208
434
Sony Xperia XZ1 Compact
Thanks for updating us on your progress. Are you able to share why the previous builds were unsuccessful, and the steps you had to take to get it working correctly?
Basically a failed cherry-pick of the WFD changes from 18.1 to 17.1 branch. It simply does not apply there and leads to bootloops for reasons I didn't further investigate. As derfelot confirmed that those are not required for 17.1 I stopped there.
The other issue was caused by my patches for SafetyNet which lead to a mismatch of the security dates leading to the system unable to decrypt data which made it stop booting.
By the way, what do "Fix/enhance wifi display" and "fix some power hints" mean in the November changelog?
On 18.1 there were issues with WFD on yoshino-phones which derfelot fixed. Also the EAS sheduler relies on "power hints" to know how much power for which information is required. Some of those were decimal instead of hexadecimal, i.e. to high maybe leading to slightly higher battery consumption.
 

landsome

Senior Member
May 4, 2015
481
119
I have just discovered that the newest version of modded Gcam Go (by Darkness, available on celsoazevedo) works pretty well with LOS17.1 and - judging by my XZ2c - probably with 18.1 as well. So if I decide to make the jump to 18.1 on XZ1c, are there still clear benefits?

I remember battery was palpably better on 18 (and that's important to me), but what about the rest of the benefits? Conversely, any things I will miss (except for the stock camera).
 
Last edited:

Flamefire

Senior Member
Jul 26, 2013
208
434
Sony Xperia XZ1 Compact
I remember battery was palpably better on 18 (and that's important to me), but what about the rest of the benefits? Conversely, any things I will miss (except for the stock camera).
Only reason I stick to 17.1 is the stock cam. Besides that newer android should be better in any case and from mod site specific to my releases both are as far as possible the same.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    I noticed that the gpu driver which the rom comes with it is fairly old- version 332(or somewhere around these numbers) from 2018. Is there any reason why it comes with that exact version? I manually updated it to 472 and it seems to work normally(also tried 490 but screen recording was broken on it).
    TBH: Not really sure which driver you refer to. Where did you get the version from and how exactly did you update it?

    I mostly rely on the LineageOS stuff and previous work by modpunk (list of proprietary blobs...) and just keep an eye on the ASBs to make sure at least the open-source patches are included. Hard enough already ;)
    4
    @MaRtYy01 As for the driver: Yes it seems we have one with OpenGL [email protected] from 2018. I found some v9a binary blobs directly from Sony (for their open-source efforts) with [email protected] from Sept. 2019. Not sure if a newer driver is worth risking issues. I mean: What could be gained by that? But I may try that for the May builds if I got time.
    I finally got around to do the April updates and am uploading them now. So not changing that ;-)
    3
    That my friend is exactly want I want to hear
    Oh sorry, missread your question. Yes, the data partition itself is encrypted and decrypting it is not yet possible on TWRP.

    Apparently, someone made stock sony cam for Los18/19.1. https://gitlab.com/xperiance
    Check his other mods too!
    2
    Can anyone confirm if @derf elot 's LineageOS 19.1 passes or fails SafetyNet? I don't need root, but a lot of LineageOS variants break it regardless and I'm afraid to try on my primary device 🙈
  • 48
    LineageOS 17.1/18.1 for Sony Xperia XZ1 Compact

    logo.png


    RELEASE

    This is an alternative ROM for the Sony Xperia XZ1 Compact.

    Creating this to honor the great work of modpunk and derf elot from https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/ which seems to be discontinued. Posting an own thread to keep the latest versions visible, I'm NOT claiming authorship over the ROM.
    I basically just build the ROM using the latest changes from upstream LineageOS/Google and kernel updates (usually incorporated by derf elot ) See my post.

    FEATURES
    • Signed with dev keys
    • EAS kernel
    • Passes SafetyNet out of the box (thanks Rooted_Ansh, Havoc-OS Team and kdrag0n)
    • Seedvault (Video)
    • IMS support (thanks to Rooted_Ansh and also Shujath)
    • 17.1 has stock Sony camera (not possible on 18.1)

    DOWNLOAD

    You can download the latest release here.
    HINT: Download both the ZIP and md5sum file so TWRP can check the consistency of the upload/download.
    REQUIRED FIRMWARE: 47.2.A.11.228

    IMPORTANT:
    I only test the 17.1 releases myself. The 18.1 are build from mostly the same sources and hopefully work. I only test them roughly.
    Backup download

    INSTALLATION

    IMPORTANT:
    Magisk seems to cause issues (bootloops) on update, so remove it first and reinstall if required. Note that Magisk is usually not required unless you want root.
    1. Put the zip file of the ROM on your SD card or internal store and boot into recovery.
    2. When coming from stock ROM, do a full wipe (i.e. factory reset) via "Wipe". Do not wipe system! When flashing the stock ROM you can select to not keep user data which is equivalent to this step.
    3. Go to "Install", select the zip file and add optionally the gapps zip. Then flash it.
    4. After updates you may now wipe cache&dalvik (option after install)
    I suggest to use modpunks TWRP recovery. Again: Don't forget the md5sum file!
    TWRP 3.3.1-0 by modpunk for LineageOS 17.1
    TWPR 3.5.0-0 by derf elot for LineageOS 18.1
    Or use the latest TWRP from https://twrp.me/sony/sonyxperiaxz1compact.html.

    For ease of use I suggest to flash this recovery (only required once):
    1. Boot in Fastboot mode: Hold "Volume Up" while connecting the USB cable to phone and PC
    2. Flash TWRP by running this on the PC: fastboot flash recovery twrp-3.3.1-0-lilac-android10-1.img
      (adjust the filename if necessary)
    3. From now you can boot TWRP by turning on the phone with "Volume Down" + Power
    I heavily recommend to make a full backup before any installation so you can go back in case of issues. Flashing an older ROM usually helps to recover bootloops etc.

    SUPPORT

    There is NONE. If you have any issues or question ask in the thread so maybe someone else knows the answer.
    I'm just providing the ROM (Lineage 17.1 variant) I use myself for others to try to and just build the Lineage 18.1 ROM without much testing.
    If you prefer to use a more well-tested Android 11 ROM, I suggest to look at Havoc-OS.
    Contributions to the sources are welcome and likely get integrated into the next release.

    Contributors
    modpunk, derf elot, Rooted_Ansh, Flamefire, linckandrea
    Source Code: https://github.com/Flamefire/android_device_sony_lilac, Original: https://github.com/whatawurst/

    If you want to buy me a coffee/beer, I'll appreciate it but it is not necessary.
    Also please consider donating to the original authors too or to local charities as requested by @modpunk

    Special thanks to landsome for donating a test phone for bug hunting and development.

    ROM OS Version: Android 10/11
    ROM Kernel: Linux 4.4.x
    Based On: LineageOS
    18
    CHANGELOG


    2022-05-03

    • April security patches
    • Kernel update (CIP st5-tag)
    • Removed LineageOS updater (unused application here)
    • Added Sony identification packages (Compatibility for some Sony apps from other sources)
    2022-03-20
    • March security patches
    • Updated some carrier configs (mostly Indian&Chinese) for IMS (VoLTE...)
    • Better support for flip covers
    • Allow disabling battery optimizations for the SMS app
    2022-02-20
    • February security patches
    • Kernel 4.4.302 (final LTS kernel)
    • Re-enable VoLTE toggle switch (there were reports of modem crashes when VoLTE is disabled, can't reproduce this, hence added the setting back)
    2022-01-23
    • January security patches
    • Kernel 4.4.299
    • Wireguard v1.0.20211208
    • Enhanced display brightness range
    • Experimental Ultra-Dim mode
    2021-12-19
    • December security patches
    • Kernel 4.4.295
    • QCom driver updates
    • Fix some permission issues
    • Reset phone ID to XZ1C
    2021-11-29
    • November security patches
    • Kernel 4.4.291
    • Fix IMS on 17.1
    • Fix/enhance Wifi-Display
    • Fix some power hints
    • Update APNs
    2021-10-19
    • October security patches
    • Kernel 4.4.288
    2021-09-18
    • September security patches
    • Include some more security patches from AOSP
    • Clang 11 for LOS 17.1 version (same as 18.1, improved optimizations)
    • Misc bugfixes backported from Android 11 to Android 10
    • Kernel 4.4.283
    2021-08-11
    • August security patches
    • Fix bug with switch 3G->4G in XperiaParts not working on slow boot
    • Include some more security patches from AOSP
    • Kernel 4.4.279
    2021-07-20
    • July security patches
    • Kernel 4.4.275
    2021-07-03
    • June security patches
    • Update to Linux Kernel 4.4.272
    • Updated APNs
    14
    I updated the ROM with the January security patches. I also included the "Ultra Dim" QuickSettings tile to reduce the screen brightness (overall). But that is experimental. I'm thinking about including that in the range of the brightness, i.e. make the lowest brightness levels less. Problem is that there are only 255 values possible so I have to define a switch-over point somehow and distribute those 255 values over effectively 2 distinct ranges. Let's see...

    I also added Google Drive downloads temporarily as a backup if AFH fails again...
    12
    Updates are out!
    Gabeldorsche seemingly works on my test phone, so maybe some upstream change already fixed it.

    Anyway, wish you all an (early) Merry Christmas and Happy New Year!
    11
    Currently uploading the new builds. Gonna take a bit...
    The 18.1 version seemingly works, passes SafetyNet etc. but as usual, I don't really test that version although I can now say that it flashes clean over the previous release and boots fine. Thanks to the test phone by @landsome
    I tested the 17.1 version the same way: Flash over previous release, boot and SafetyNet is working. However I'll flash that on my own phone tomorrow and test it a bit more "in production". Hence you'll find that in the "Testing Only" folder on AFH until I verified it a bit more. No time left for that today but if you want to give it a try feel free.
    As mentioned I fixed the IMS bug on 17.1 and on my phone (October build with only that patch applied) VoLTE and VoWIFI work fine.

    As for GPS: The XZ1C has known hardware issues with the GPS antenna. The ROM if flashed correctly works ok although I noticed that GPS is shaky too. Some users reported that squeezing the left edges often helps...

    I'll tackle the HD audio stuff later. That needs some more work to do it properly.

    Donations: See the initial post and my profile (About section). Always welcome and keeps me motivated to put in a bit of extra effort :) Please note that I often integrate changes from others, like modpunk/derfelot, linckandrea etc. On Github you can usually see that as "authored by X, committed by Flamefire" as I try to keep the author unchanged. So others deserve credit (and donations) too.