[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2024-03-30)

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

  • Yes - I need it

    Votes: 59 24.3%

  • No - It takes space. (Can install F-Droid or OpenGapps manually if required)

    Votes: 116 47.7%

  • No - I want microG apps instead (NOT OpenGapps)

    Votes: 38 15.6%

  • Don't care - Do what others want

    Votes: 30 12.3%
  • Total voters
    243
Search This thread
By:
Advanced…
Flamefire

Flamefire

Senior Member
Jul 26, 2013
295
876
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...
 
  • Like
Reactions: sieghartRM, Danko Jones, landsome and 2 others
R

rez78

Senior Member
Nov 16, 2017
204
49
Flamefire said:
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
Click to expand...
Click to collapse
Great! Please give me istructions to make a donation for your work! :-D
 
Flamefire

Flamefire

Senior Member
Jul 26, 2013
295
876
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:
  • Like
Reactions: sieghartRM, Danko Jones, jfora and 8 others
E

ezdi

Senior Member
Dec 14, 2010
94
43
ezdi said:
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.
Click to expand...
Click to collapse

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

Flamefire

Senior Member
Jul 26, 2013
295
876
Sony Xperia XZ1 Compact
ezdi said:
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.
Click to expand...
Click to collapse
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
J

jmbattle

Member
Jul 3, 2015
21
5
Flamefire said:
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...
Click to expand...
Click to collapse
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.
 
J

jmbattle

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

Flamefire

Senior Member
Jul 26, 2013
295
876
Sony Xperia XZ1 Compact
jmbattle said:
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?
Click to expand...
Click to collapse
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.
jmbattle said:
By the way, what do "Fix/enhance wifi display" and "fix some power hints" mean in the November changelog?
Click to expand...
Click to collapse
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.
 
  • Like
Reactions: sieghartRM and jmbattle
landsome

landsome

Senior Member
May 4, 2015
610
159
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

Flamefire

Senior Member
Jul 26, 2013
295
876
Sony Xperia XZ1 Compact
landsome said:
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).
Click to expand...
Click to collapse
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.
 
  • Like
Reactions: sieghartRM and landsome
You must log in or register to reply here.

Similar threads

M
[ROM] LineageOS 18.1 UNOFFICIAL - 2.0 (Update: 2021-01-20)
Replies
2K
Views
246K
alesimattia
alesimattia
M
[ROM] LineageOS 16.0 UNOFFICIAL - 1.2 [2020-02-11]
Replies
1K
Views
167K
N
neurer
M
[ROM] LineageOS 15.1 UNOFFICIAL - BETA8 (2018-10-22)
Replies
840
Views
160K
spacedrone808
spacedrone808
N
[ROM] [Final] LineageOS 20.0 UNOFFICIAL - 1.2 [2023-12-28]
Replies
650
Views
76K
P
Pfrinz
N
[ROM] [Final] LineageOS 19.1 UNOFFICIAL - 1.6 [2022-09-18]
Replies
332
Views
47K
P
petefoth

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 8
    Flamefire
    Flamefire
    Happy Easter!

    I uploaded the 17 & 18 versions of the new ROM to GDrive. Google wallet seems to work. The 19 and MicroG versions still need some testing, will upload after Easter.

    @snoopy29 not sure what you mean exactly. Can you Clearly describe the issue? But likely not fixed as I have spent a lot of time on IMS, kernel issues and the Play Integrity stuff especially if the time issue only happen on reboot it is annoying but not crucial. I haven't seen it on 17-non-MicroG (using network time which might hide it)
    View
    8
    Flamefire
    Flamefire
    Currently uploading the remaining builds (19.1 & MicroG versions) after some more testing and fixes. Play Integrity now passes on all builds and Wallet should hence work again. You can also use the PIF JSON file to change the fingerprints in case it gets blocked, as if PlayIntegrityFork was installed. Place it at /data/adb/pif.json to use. Only Build fields are supported though (i.e. not the properties)
    See the example file or better /vendor/etc/pif.json on the phone for the format and current usages.

    The time issues on 17.1 persist and are hard to fix if at all so I stopped searching for a fix after some time as it works on 18 & 19 and on 17 the auto-set from network is "good enough". Or just don't reboot ;-)
    View
    3
    A
    antoniu200
    LegendOcta said:
    Also, does VoLTE work stable as in stock rom?
    Click to expand...
    Click to collapse

    VoLTE and VoWiFi should work better than in stock ROM, universal support has been added, so the only limitation is the carrier possibly blocking the phone.

    zpunout said:
    I took these steps to enable VoLTE as shown in an earlier post
    Click to expand...
    Click to collapse

    For the March 2024 update, those steps are not necessary anymore. IMS features start automatically, when IMS is enabled in XperiaParts.
    View
    2
    7
    7alvoo
    compactifier said:
    Hi,
    I tried out 17 and 18 and everything works fine.
    Any suggestions?
    Click to expand...
    Click to collapse

    Choose one.
    View
    1
    A
    antoniu200
    decsimon said:
    In version 17, I have always had the problem of the proximity sensor which during a call, in certain situations, when I move my face away, causes the screen to remain black and therefore makes it inaccessible to use the phone for example on speakerphone, during a call, to navigate or simply press keys on the numeric keyboard. This doesn't happen with other versions of lineageos. As a compensatory solution, we would need a function that forces the screen to stay on during the call, even with your face close...
    Click to expand...
    Click to collapse
    Has your phone ever been disassembled? Do you feel the top of the screen being a bit above the phone's case?

    If you do, that's likely the reason. I have never experienced this, but will keep an eye out for this behavior.
    As a momentary fix, you can press the power button and that will wake up the screen.
    View
  • 58
    Flamefire
    Flamefire
    LineageOS 17/18/19 for Sony Xperia XZ1 Compact

    logo.png


    RELEASE

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

    It is based on the great work of modpunk and derf elot from https://xdaforums.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/ with recent security updates, some backported from newer versions.

    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+)

    DOWNLOAD
    You can download the latest release here. (Backup download when AFH isn't uploading)
    HINT: Download both the ZIP and md5sum file so TWRP can check the consistency of the upload/download.
    Make sure you download the right version, vanilla LineageOS is named lineage-*UNOFFICIAL-lilac.zip while the MicroG version is named lineage-*-MICROG--lilac.zip

    REQUIRED FIRMWARE: 47.2.A.11.228

    IMPORTANT:     I only use the 17.1 releases myself. The 18.1/19.1 are build from mostly the same sources and roughly tested, i.e. boots, WiFi works and SN passes/MicroG self check shows OK.

    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". You don't need to 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 / derf elot
    Or use the latest TWRP for 17.1/18.1 or TWRP for 19.1.
    3.7.0 Seems to work well with latest updates (decryption working) but LineageOS 19.1 (Android 12) requires the ones with "_12" suffix, e.g. 3.6.2_12.

    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.

    Upgrades between versions​

    Dirty-flashing (e.g. from 17.1 to 18.1) works well but you have to also flash a GApps version matching the Android version or the device will bootloop.
    For the upgrade to 19.1 you may need to fully remove OpenGapps by wiping /system and install e.g. MindTheGapps.

    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 too and build the Lineage 18/19 ROMs without much testing.
    Contributions to the sources are welcome and likely get integrated into the next release.

    Contributors
    modpunk, derf elot, Rooted_Ansh, Flamefire, linckandrea
    Source Code: Device tree: https://github.com/Flamefire/android_device_sony_lilac
    Kernel: https://github.com/Flamefire/android_kernel_sony_msm8998

    If you want to buy me a coffee/beer, I'll appreciate it but it is not necessary.


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

    ROM OS Version: Android 10/11/12
    ROM Kernel: Linux 4.4.x
    Based On: LineageOS
    GApps: None included, except for the MICROG builds. Recommended is OpenGApps for 17/18 and MindTheGapps for 19.
    View
    27
    Flamefire
    Flamefire
    CHANGELOG


    2024-03-30
    • Kernel updates (CIP tag -st50)
    • Reduce performance issues
    • Play Integrity workaround (based on osm0sis work)
    • Attempt to enable IMS by default for all providers (mostly from @antoniu200 )
    2024-02-18
    • Feburary security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st49)
    2024-01-20
    • January security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st48 & LOS common kernel merge)
    2023-12-24
    • December security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st47 & additional security fixes)
    • Fix for critical Bluetooth vulnerability (CVE-2023-45866)
    2023-11-11
    • November security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st46 & additional security fixes)
    • Updates to the kernel scheduler backported from LOS 20 common kernel
    • Fix for CVE-2023-5217
    2023-10-15
    • October security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st45 & additional security fixes)
    • Fix for CVE-2023-4863 (actively exploited!)
    2023-09-16
    • September security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st44)
    2023-08-25
    • August security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st43)
    • Increased headset volume
    • Add Sony camera app to 18 & 19 (files copied from xperiance)
    2023-07-26
    • July security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st42)
    2023-06-16
    • June security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st41)
    • Fix noise when calling with a headset
    • Configurable fingerprint sensor when screen is off (Settings->Lockscreen)
    2023-05-19
    • Fix Play Integrity checks --> Google Wallet works
    • Minor improvements that were missed earlier
    • May security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st40)
    2023-04-30
    • April security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st39)
    2023-03-31
    • March security patches (backports from 18.1 to 17.1)
    • Kernel updates (CIP tag -st38)
    • Fix possible camera issues on 18.1
    2023-02-25
    • February security patches
    • Kernel updates (e.g. CIP tag -st37, also add some missing patches to 19.1 kernel)
    • Use newer compiler (Clang 12.0.7) for kernel, possibly improving performance/battery life
    • Add "Re-apply Modem" setting to XperiaParts to help with connection/modem-crash issues
    • Clear some space on /system & /vendor partitions by removing files no longer needed
    • Fix Android Auto connection
    2023-01-20
    • January security patches
    • Kernel updates
    • MicroG builds added (build date 31st Jan, but same sources)
    2022-12-27
    • December security patches
    • AGPS fix (using Google servers)
    • Kernel updates (e.g. Wireguard v1.0.20220627, improved security against stack attacks)
    2022-11-15
    • November security patches
    • WLAN driver update
    • Huge APN update
    2022-10-13
    • October security patches
    • Kernel update
    • APN for DIGI HU
    • Option to switch temporarily to 2G on boot
    2022-09-29
    • September security patches
    • Kernel update
    • APN update
    2022-08-12
    • August security patches
    • Kernel update (CIP st20)
    2022-07-25/28
    • July security patches
    • Kernel update
    2022-06-30
    • June security patches
    • Kernel update
    • Backport fix for CVE-2021-39686
    • Workaround fixing bootloop with recent OpenGapps (20220503 tested)
    2022-05-16
    • May security patches
    • Fix mic volume issue with wired headsets
    • Known issue: OpenGapps after 15/2 result in bootloop
    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
    View
    20
    Flamefire
    Flamefire
    I'm happy to announce the June update. Took a lot more work as I backported quite a bit to our kernel to fix CVE-2021-39686 although I'm not sure we were ever really affected by that. Anyway the backport fixes that hole and a few potential others making the device a bit safer!
    View
    18
    Flamefire
    Flamefire
    April updates are out, enjoy! Again I had to backport every security patch from 18.1 to 17.1 so it really seems to be dying...
    I might switch to building LOS 20 though as derfelot doesn't seem to be providing updates anymore. And especially the battery charge/protection service that might be coming there looks promising...

    sieghartRM said:
    Could you provide LineageOS recovery for this device?
    Click to expand...
    Click to collapse

    Sorry no. I'd need to research how to create that recovery and maintaining 3/6 different ROM versions is already enough work especially with the hugely increased time/effort to keep LOS 17, so I can't afford to do even more.
    View
    15
    Flamefire
    Flamefire
    @MarkMRL Update 20220516 is out which should also fix the headset issue. Reproduced, found and fixed it as far as I can tell.
    View

New posts