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

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


  • Total voters
    243
Search This thread

ygofoust

New member
Oct 10, 2021
2
2
Thanks very much for your help! To me there is an annoying issue with Gboard or swiftkey keyboard that there is a keyboard selection bar, when enabling gestures.

How do you remove the bar? It is really a waste of space for a small screen.

Thanks!
 
  • Like
Reactions: PhobiaSoft

ygofoust

New member
Oct 10, 2021
2
2
@7alvoo thanks for the link. I tried to understand it with google translate. They seemed to solve the issue with the navigation bar? However I couldn't find the setting after check nearly every possible setting.
 
  • Like
Reactions: mstrnemo

berti42

Member
May 8, 2016
12
1
I flashed the September Version of 18.1 and it seems, that everything is working well. I wiped my old 17.1 system plus data, cache and DALVIK with the latest TWRP, so i did a clean install. I also installed gApps pico then for minimizing Google at my device. At the beginning the wifi connection was cut often. But now i couln't notice that. For mobile data i had to change the APN configuration for my german provider "Drillisch". Later i will check GPS and battery drain.
 

mstrnemo

Senior Member
Feb 1, 2021
195
31
Pictures under the + mark
/i don't think it's a very wise decision to use these apps mainly for password writing/
Very interested in this but i could not find that screen either
@7alvoo thanks for the link. I tried to understand it with google translate. They seemed to solve the issue with the navigation bar? However I couldn't find the setting after check nearly every possible setting.

I second this Any help would be appreciated
 

trax7

Senior Member
May 15, 2012
944
345

For people who want to use F2FS:​

0. (Optional) Backup your data and apps and install latest TWRP 3.5.2 from the TWRP official site.
1. Reboot to TWRP > Go to Wipe > Advanced Wipe > Select Data > Repair or Change FIle System > Click F2FS

* CHANGING FILE SYSTEMS WILL WIPE ALL YOUR DATA *

2. Reboot to recovery again
3. Mount /vendor (should be handled automatically, only if you get mount error when flashing)
4. Flash zip file in attachments after flashing the ROM. It should support encryption too.
5. Enjoy! :)

Note: There is no point to make F2FS for /cache! In fact, it gets reduced performance in real world use.

** Here is why you might want to switch to F2FS.
*** If someone is interested in kernel building, there are kernel patches that can be applied for better operation and performance.
 

Attachments

  • FSTAB-EXT4_F2FS-encryptable_footer-LILAC.zip
    124 KB · Views: 7
Last edited:

berti42

Member
May 8, 2016
12
1
Now, i tested GPS with the app "Here we go" and everything is working fine. On the first try it didn't work because i didn't switch on the location-switch in settings:) I want to grant access to location service to only some selected apps and so i limited it in the location settings. Battery drain also seems to be as good as LOS 17.1
 
Last edited:
  • Like
Reactions: 7alvoo

petefoth

Senior Member
Dec 12, 2015
550
425
Whaley Bridge
Sony Xperia Z3 Compact
But you wiped system which gets rid of the OS if I understood it correctly. After wiping system you need to again install stock rom + then install lineageos on top of that. Someone correct me if I'm wrong.
In my experience, it is not necessary to install stock ROM before moving from LineageOS 17 to 18. The latest Stock ROM was Android 9 / Pie. Why would you need to go back an Android version (from LOS 17 / Android 10 / Q to Android 9 / Pie) when moving to LOS 18 Android 11 / R?

I have swapped between 17 and 18 with no problems
 
  • Like
Reactions: PhobiaSoft

toejam119

Senior Member
In my experience, it is not necessary to install stock ROM before moving from LineageOS 17 to 18. The latest Stock ROM was Android 9 / Pie. Why would you need to go back an Android version (from LOS 17 / Android 10 / Q to Android 9 / Pie) when moving to LOS 18 Android 11 / R?

I have swapped between 17 and 18 with no problems
When I installed 18.1 from 17.1 I didn't install stock rom in between, I just flashed 18.1 on top of 17.1, but I didn't wipe system in between, he wiped system which would remove his operating system completely, thus he's back to 0, thus now requiring some of the stock files again if he wants to install any LineageOS version. At least this was the order of installation with modpunk's version.

I quickly googled and found the following:
"Wiping system in TWRP erases your entire Android OS. Your device will no longer have an operating system. It will not wipe all of your user apps and data, as those are stored on the /userdata (Data) partition."
 

petefoth

Senior Member
Dec 12, 2015
550
425
Whaley Bridge
Sony Xperia Z3 Compact
When I installed 18.1 from 17.1 I didn't install stock rom in between, I just flashed 18.1 on top of 17.1, but I didn't wipe system in between, he wiped system which would remove his operating system completely, thus he's back to 0, thus now requiring some of the stock files again if he wants to install any LineageOS version. At least this was the order of installation with modpunk's version.

I quickly googled and found the following:
"Wiping system in TWRP erases your entire Android OS. Your device will no longer have an operating system. It will not wipe all of your user apps and data, as those are stored on the /userdata (Data) partition."
With official Lineage OS it is not necessary to install stock when installing 18.0 after wiping system.
I have just done the following on an Xperia Z3 (because I don't have my XZ1 Compact available for such experiments) but I am sure the same is true for this device.
  1. TWRP Wipe my existing system (an Android 10 / Q based /e/ OS ROM)
  2. TWRP Install `lineage-17.1-20210708-nightly-z3-signed.zip`
  3. Reboot system and complete first time setup wizard
  4. Power off
  5. Reboot to TWRP
  6. TWRP Wipe | Advanced | System
  7. TWRP Install `lineage-18.1-20210805-nightly-z3-signed.zip`
  8. TWRP Wipe Cache / Dalvik
  9. Reboot system and complete first time setup wizard
So, I do not believe it is necessary to install Stock ROM when installing 18.0 after wiping system.

But I'm always pleased to be proved wrong, so I'm willing to learn from your experience if following this sequence does not work for you.
 
Last edited:

mugenXperia

New member
Oct 14, 2021
4
1
Hi,

thanks for the rom. I really like to upgrade my XCompact to a more recent version. However, as it is a japanese model, I would like to try to make some changes in the kernel (NFC). I follow the instruction given from the source you gave in the post, but did not succeed. Would it be possible for your to share your build tools or which other magic sauce you may have.

Thanks
 

petefoth

Senior Member
Dec 12, 2015
550
425
Whaley Bridge
Sony Xperia Z3 Compact
Why this step? You wiped away LineageOS 17.1 you just installed.
Yes, because we were discussing whether or not it is necessary to flash a Stock ROM before flashing LOS 18.1. You suggested it would be necessary because @berti42 had wiped his system.

he wiped system which would remove his operating system completely, thus he's back to 0, thus now requiring some of the stock files again if he wants to install any LineageOS version.

I do not believe that to be the case, so I followed this process to check whether or not it was true. What I found out is that there is no need to flash a stock ROM when moving from 17.1 to 181 whether or not you have wiped the system. If I had not wiped the system, the experiment would not have proved anything.

In normal circumstances, I would never wipe the system when installing, because I believe that the old system is wiped as part of the install, so wiping would be a waste of time, effort and processing cycles. This thread is starting to become the same, so I will stop :)
 

PhobiaSoft

Senior Member
Aug 6, 2015
103
44
www.youtube.com
After updating to the September 18th version of 18.1 I've found that Chromecast no longer works on this device. The Cast device search works correctly but hangs upon actually trying to connect. Tried with an original release Chromecast and a Chromecast Ultra, and they both exhibit the same issue. It was working on the August 11th version of 18.1.

Can anyone reproduce this issue? Is Casting working for you on the September 18th version of 17.1 @Flamefire ? In any other situation, I would just downgrade, but my retinas are very grateful that the Sony logo is dimmed on the phone's startup now and I don't know if I can go back lol


EDIT: Reflashing the September 18th version of 18.1 fixed the issue, so it was likely a TWRP error of some kind that caused my problem, and not anything wrong with this version of the ROM. All is well now :)
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    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)
    8
    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 ;-)
    2
    Also, does VoLTE work stable as in stock rom?

    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.

    I took these steps to enable VoLTE as shown in an earlier post

    For the March 2024 update, those steps are not necessary anymore. IMS features start automatically, when IMS is enabled in XperiaParts.
    2
    Hi,
    I tried out 17 and 18 and everything works fine.
    Any suggestions?

    Choose one.
    1
    Which version is this? LOS 17,18 or 19? MicroG or not? Will check but if it works fine with the setting disabled it isn't critical at least
    Antoniu said I'm using 18, but I'm actually using LOS 19 (20240121), without MicroG.
  • 58
    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.
    27
    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
    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!
    18
    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...

    Could you provide LineageOS recovery for this device?

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