[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2023-01-21)

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


  • Total voters
    193
Search This thread

Rataplan626

Senior Member
Feb 7, 2006
387
100
One thing i have found on latest build LOS 17.1 8/12/22 - incomming telephone calls - at first i hear my ringtone and i dont see who are calling me and after some seconds, answering screen becomes
Ah, I thought it was something bugging on my particular phone. But I suffer the same. Also when using the 3CX voip app for work by the way. Super annoying!
 

Flamefire

Senior Member
Jul 26, 2013
233
593
Sony Xperia XZ1 Compact
Currently testing the September builds. AFH seems to reject uploads right now, so might take another day or 2. Also checking the 19.1 sources from derfelot and integrating some of the changes into the new build, e.g. new APN settings.

BTW: Is there anyone who would prefer the 18.1 version over the 19.1 version? Thinking about porting my changes to 19.1 and not building 18.1 anymore, so 17.1 for those who want the Sony camera app and 19.1 for those who want a fresh system. Not sure if there is any advantage of the 18.1 version over 19.1
 

victor126

Senior Member
Sep 30, 2017
56
15
Currently testing the September builds. AFH seems to reject uploads right now, so might take another day or 2. Also checking the 19.1 sources from derfelot and integrating some of the changes into the new build, e.g. new APN settings.

BTW: Is there anyone who would prefer the 18.1 version over the 19.1 version? Thinking about porting my changes to 19.1 and not building 18.1 anymore, so 17.1 for those who want the Sony camera app and 19.1 for those who want a fresh system. Not sure if there is any advantage of the 18.1 version over 19.1
i tried 19.1 a couple times and always went back to 17.1
 

gladykov

Senior Member
Jul 12, 2010
75
14
Currently testing the September builds. AFH seems to reject uploads right now, so might take another day or 2. Also checking the 19.1 sources from derfelot and integrating some of the changes into the new build, e.g. new APN settings.

BTW: Is there anyone who would prefer the 18.1 version over the 19.1 version? Thinking about porting my changes to 19.1 and not building 18.1 anymore, so 17.1 for those who want the Sony camera app and 19.1 for those who want a fresh system. Not sure if there is any advantage of the 18.1 version over 19.1
I was always on 18.1 , but then switched to 19.1 and not going back - faster, drains less battery and nicer for the eye. So since derfelot stopped building 19.1 I think this is a great idea.
 

Flamefire

Senior Member
Jul 26, 2013
233
593
Sony Xperia XZ1 Compact
I'll try to backport some of the performance/battery changes from 19.1 to 17.1/18.1 and hope that helps but pretty busy with not much free time and maintaining 2 ROM versions is already a lot of work and the 19.1 changes are quite big. I just started looking through them although I got the kernel BPF stuff done locally now which is a major part.
That wouldn't be possible without the work of derfelot (I'm mostly cherry-picking his commits to my fork to make sure the security fixes I already have done and checked don't get lost), so many thanks for his hard work!

BTW: September builds are now finally uploaded
 

mxbndr

Senior Member
Sep 29, 2010
52
5
Thanks for working on this! Saved my phone from the voLTE nightmare carriers are enforcing right now. Love having Android 11, too! And adding a vote for staying on 18.1; Android 12+ is such a worse UI/UX for my taste.

A few things that are still buggy: the phone always boots into the Light theme. Dark Mode settings will not persist. I currently have Tasker set to change this on boot, but it's hit or miss.

Also, Wi-Fi calling did not work on @modpunk 's last build, but voLTE did. On the 09/22 build in this thread, Wi-Fi calling works well, but voLTE does not. I then changed the IMS toggle in the Xperia parts setting area, and it took a minute to find LTE but when it did voLTE worked!

Any idea how to make Dark Mode permanent? Is there a file somewhere I can patch?
 

mxbndr

Senior Member
Sep 29, 2010
52
5
Another possible issue: this version seems to have a harder time picking up an LTE signal (or any signal at all) until I manually switch to 2G and then to LTE. Is there a modem config or something I should try? It get's LTE fine once it finds it, but often it needs help.
 

gladykov

Senior Member
Jul 12, 2010
75
14
Another possible issue: this version seems to have a harder time picking up an LTE signal (or any signal at all) until I manually switch to 2G and then to LTE. Is there a modem config or something I should try? It get's LTE fine once it finds it, but often it needs help.
Use network switcher service
Screenshot_20221003-160918_XperiaParts.png
 

mxbndr

Senior Member
Sep 29, 2010
52
5
Thanks, I did have that activated. It didn't seem to change anything. I wonder if it's because it is seeking 3G networks that have been turned off, rather than 2G ("GSM").
 

zpunout

Senior Member
Aug 26, 2015
324
77
Samsung Galaxy S5
Moto G5 Plus
I'm using 17.1 (because of the stock camera and I think also the faster storage access framework). I noticed VoLTE isn't provisioned as shown in the *#*#4636#*#* Phone Info settings. To get VoLTE working, do I need to reinstall stock firmware to get it enabled before reinstalling LOS again? My carrier says they are VoLTE in their FAQ.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    January updates out. Security updates only, MicroG versios will follow in about a week when I'm back from vacation. Stay safe!
    5
    I uploaded MicroG builds for all 3 versions, they are named e.g. lineage-19.1-20230131-MICROG instead of lineage-19.1-20230131-UNOFFICIAL but are contained in the same folder.

    As they are not compatible with each other (not sure if you can dirty-flash one over the other, at least you need to wipe system) you have to be careful to choose the correct one!
    5
    The 2G setting is gone since 19.1 i believe on derfelot's build as well.
    As for the fingerprint it's been like this on flamefires builds for a while, dunno why, some of his changes broke that functionality because on derf's builds it's working fine.
    I can double-check why the 2G setting is gone but it looks like it was removed upstream. I see if I can patch it back.
    As for the fingerprint: This is not "broken" but working as intended: A lot of people here complained that touching the on/off button immediately unlocks the phone. Hence I decided to follow suit with upstream LOS to disable this if the fingerprint is integrated into the powerbutton and cherry-picked a change used in similar LOS devices: https://github.com/Flamefire/androi...mmit/924352c24a95959941fe5a471741528dc2d87026
    Unfortunately there isn't a user-setting to change this although I was thinking about adding one. I think that the current setting being the default makes sense also from a security perspective as unlocking the phone also enables NFC payments so doing that by accident can be a real problem.

    Anyway: I'm currently very packed with work as I'm backporting security patches to the kernel, incorporating new changes from 19.1 to 17/18.1, updating blobs to hopefully resolve the connection loss issue (has anyone observed those on 19.1?) and just got the MicroG build working on 18.1 so at least that will be there once I'm done
    3
    - 2G is not selectable anymore as preferred network type in Settings (I sometimes need that when I'm in the mountains)
    I found this: "Android 12 users need to go to Settings > Network & Internet > SIMs > Allow 2G"

    However I just quickly checked on the spare phone and I do still have that setting on latest 19.1, although it is more hidden than on 17.1 (which I'm using personally)

    Also switching to 2G is what I do when I have network issues (and done by the switcher service on startup). But I've seen a changeset that might help better here. Will be included in the February builds if that works.

    EDIT: wiped system, reflashed zip and OpenGapps, wiped Dalvik (or rather ART) and cache... and it fixed itself. That's bit odd.

    Wiping dalvik and cache is what I always do. Here I guess there was something on /system which shouldn't be there. Glad you could fix that! The SafetyNet fix is one of the things I do test for every update so I'd be surprised if it doesn't work.
    1
    But I have just installed a few things and was thinking on moving to the MICROG build, so: any suggestion on how to proceed?

    Based on what's said on the first post I guess the way to go is wiping everything from TWRP and flashing the mod, does it make sense? I'm unclear if I need to use a specific TWRP version and if so, which one.
    You can try to only wipe system and install the MICROG build. But I guess the data stuff from the other GApps won't be compatible so you may need to wipe data too (factory reset).
    In any case wiping cache&dalvik is a good idea.
    If all fails just flash the stock ROM and then the MICROG build. Of course you (also) loose your data but that should always work.
    I'm using LOS 17,1 latest version just flashed, and my need is to have Android Auto working (Peugeot e-208)
    ...
    Do you have any suggestion? Anyone with similar issue and who have managed to solve?
    derfelot has found something which may fix this. I'll likely add this to the February builds if I get to that. I can't test that though as I don't have an Android Auto device/car.
    Anyway when I include that stuff I'll mention it in the changelog, so keep an eye there
  • 53
    LineageOS 17/18/19 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+)

    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.
    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 test the 17.1 releases myself. The 18.1/19.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 / 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 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/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.
    22
    CHANGELOG


    2022-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
    20
    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!
    15
    @MarkMRL Update 20220516 is out which should also fix the headset issue. Reproduced, found and fixed it as far as I can tell.
    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...