[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2023-02-25)

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


  • Total voters
    199
Search This thread

Flamefire

Senior Member
Jul 26, 2013
241
627
Sony Xperia XZ1 Compact
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.
 
Last edited:

Flamefire

Senior Member
Jul 26, 2013
241
627
Sony Xperia XZ1 Compact
CHANGELOG


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
  • Attempt to fix Android Auto connection (untested)
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
 
Last edited:

landsome

Senior Member
May 4, 2015
545
139
Thank you so much!! Can anyone report to me if flashing the new 18.1 directly over the previous version of 18.1 works?

I would test myself, but right now I cant afford to need to totally reset my phone if it doesn't work.
All I can say dirty flashing works well over the latest/previous 17.1 by Flamefire, which in turn works well over the latest modpunk (1.7). So it's worth a try.

More generally, although these ROMs are hardly as well tested as HavocOS, there are satisfied reports over on the original LOS17.1/18.1 thread.
 
  • Like
Reactions: MilesBHuff

rez78

Senior Member
Nov 16, 2017
165
36
Thank you so much!! Can anyone report to me if flashing the new 18.1 directly over the previous version of 18.1 works?

I would test myself, but right now I cant afford to need to totally reset my phone if it doesn't work.
Dirty flash from 17.1 to 18.1 and all work fine!
 

landsome

Senior Member
May 4, 2015
545
139
Updated with the July security patches.
Note: AndroidFileHost was quite quirky today, so use the md5sum files to verify the integrity of the files
Thanks. Tried it for a couple of hours - dirty flashed over the 0702 version - and it works just as well so far.

I had one brief moment of panic: upon first boot the phone was stuck right on hitting the desktop for some 10 seconds (did not happen on the many previous dirty flashes); but then everything proceeded well.

Again, great work.
 

7alvoo

Senior Member
Jul 18, 2019
163
52
@Flamefire Regarding the information to TWRP: There is an official TWRP version (maintained by @modpunk & @derf elot ): https://twrp.me/sony/sonyxperiaxz1compact.html :)
Maybe you can update the information in your header.
Your suggestion would be valuable if you share your experience:
- encrypted partition mount and decryption compatibility with LineageOS 17.1/18.1
- partition backup / restore - single / batch - with / without password protection
- other version differential bug report
 
Last edited:

xenonism

Senior Member
Dec 20, 2010
172
52
Sony Xperia XZ1 Compact
Ok, I was bored and I made a mess, I could use some help. :(

I was on the latest and last 17.1 by modpunk. I updated TWRP to the latest official one. I tried to flash the latest 18.1 by Flamefire (I had to disable zip signature verification. I know :censored:). Upon reboot it spends about a minute on the LOS animated logo then reboots to TWRP. I then downgraded TWRP to the latest by modpunk and flashed his latest 18.1 from January. This bootloops to recovery without ever reaching the LOS logo.

I know this is my fault. This said, what's my best chance (if any) not to have to wipe everything? I read in a post above that downgrading from 18.1 to 17.1 won't work, otherwise that would be my next idea.

Thanks in advance to anyone replying! :)

EDIT: Silly me. I had just forgotten to flash 11.0 gApps. All is well with the dirtiest flash ever. :p
 
Last edited:

baboon23

Senior Member
Apr 9, 2020
149
38
OUTSTANDING!
Thanks for bringing life to this amazing work, you are the best!
Much appreciated.
 

mstrnemo

Senior Member
Feb 1, 2021
158
20
@Flamefire

Im confused so u continue with updating the security patches every month correct ?
Im confused about the 18.1 u also only update it with securitypatches or also other stuf like making stable and fixing problems orwhatnot ?

Thank you for keeping our trusty xz1 compact alive a little longer.
 

7alvoo

Senior Member
Jul 18, 2019
163
52
It was not possible to boot LOS 17.1 with TWRP version from first post. (fresh flash, etc... ) However when using latest official twrp https://twrp.me/sony/sonyxperiaxz1compact.html everything works well.
Does it respond to volume up button presses and in special system restart recovery mode? Prompts for a pin/pattern during login and successfully mount and decrypt the partition? So far no one else has reported using it and so far we knew 17.1 / 18.1 requires a different version. Your experience will help us a lot please share as much experience as possible about the new twrp.
 
Last edited:

megaice

Senior Member
Does it respond to volume up button presses and in special system restart recovery mode? Prompts for a pin/pattern during login and successfully mount and decrypt the partition? So far no one else has reported using it and so far we knew 17.1 / 18.1 requires a different version. Your experience will help us a lot please share as much experience as possible about the new twrp.
i forgot to mention - i'm using lineage-17.1-20210702-UNOFFICIAL-lilac.zip build (not the latest ..20210720..)
TWRP version 3.5.2_9.0
Magisk 20.4 -> 23
Entering recovery works well, pwr+vol down, vol up after pwr, or when set in Developer submenu - advanced reboot. I have active pin and fingerprint. When entering recovery, twrp asks for password for user 0, using my pin works and twrp decrypts FBE. i can mount and read user data by File Manager in twrp.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    As you may have noticed March updates are late. Besides that the LOS patches are only released last week there are no updates to LOS 17.1 in the "official" LOS repos which means the bug fixes to the (security and other) issues from March in Android 11+ (LOS 18+) are missing in LOS 17. It seems that Google didn't even backport the Android 11 fixes to Android 10 which might be the reason why there are no updates to the LOS 17 branches, which were there until last month.

    So over the past days I did that myself: backporting all security fixes done for March in LOS 18 to LOS 17 besides also debugging and fixing a bug introduced in the latest kernel backport (through CIP) used in all branches, which was quite some work in itself.
    This also made me postpone my work on some potential performance improvements for LOS 17 which I started working on to (likely) next month.

    This looks good so far. When I'm done testing etc. I'll build and release all (6!) versions of LOS as usual in the next few days hopefully before the weekend.

    However it seems that Android 10 may now have really reached its end of life with Google stopping to provide even security updates for it which makes the amount of work required to provide the updates unbearable. So if no one else in the LOS community provides backports of the patches then this might be the last update to LOS 17.1 and hence the last version with a working (stock) Sony camera app on our device.
    2
    Hello, now in latest update of LOS 17.1 for lilac 02/25 (clean install) I am experiencing random UI reboots and one bug:
    If i turn off device and turn on (no reboot), system sounds arent working, freeze and FC when i want to set an alarm in clock app or play music, no flashlight, camera cannot start and maybe something else which i havent noticed.
    [...]
    I dont know if someone has similar problems, but this is strange.
    I'm using that ROM (17.1) myself on my daily device and haven't encountered any issues at all. So looks like something with your device, not the ROM itself.
    Now battery lasted 3 days +20% with 5hrs SOT, very nice ! No gapps.
    2 more bugs:
    Camera taking blank photos if default storage is set to sd card.
    Front camera gives white screen, freezes, FC and then i cant open camera when is flashlight turned on.

    Maybe it is related only to Sony camera app, i havent tested other camera apps.
    I assume you are (still) using 17.1 as you mention the Sony camera app. I'm a bit confused: Above you said that the camera cannot start.

    I just tried to reproduce the other issues: Camera works fine for me, I've always had the default set to SD and front camera does also work. I can imagine issues with camera and the flashlight feature as the former may want to access the light which may be already in use in that situation but it also does work fine for me.
    In fact the camera is one of the things I test on a spare device for a new ROM before even installing that on my own phone as a working camera is a good hint that a big part of the system works.

    So I can only imagine that there is still something left on your device interfering with the current ROM. If you don't mind loosing your data reflash the Stock firmware with newflasher, TWRP and then this ROM making sure to wipe /data, /cache and dalvik in the process. Or if you don't want to flash stock wipe /system, /cache & dalvik and format /data, then reinstall the ROM (without rebooting TWRP) which might help.
    At the very least try wiping /cache & dalvik (keep your data)

    This update seems to have broken extract-files.sh, preventing a clean build from source. Reported on github as issue 13.
    Answered there (a link to the issue in your post would be helpful as I don't get a notification on GH, but found it anyway): In short: It does work (I always do clean builds, by now 6 times), check your extracted system image :)
    2
    First, my TWRP backups were all done from within TWRP with the phone running in Recovery, not using `adb backup --twrp` so I don't know if they two methods are functionally equivalent.
    Thanks for the reply! I actually think they use slightly different storage formats, so next time backing up to the SD card may be worth a try.

    Are you able to get back to your original setup (i.e. your custom ROM, with your backup restored?
    Maybe I'm misunderstanding the question, but my problem is exactly that I can't boot the restored backup unless I format the restored data partition... at which point it wouldn't be my original setup anymore. (The backup I created covers all partitions, and adb does not support partial restores)

    My '"if all else fails" backup' is to backup using Android Backup and Restore Tools project. You need rooted debugging enabled, and access to a Linux machine (real or virtual). I have used these scripts to backup my apps and data and then to
    1. Restore to the same device, running the same or different custom ROM
    2. Restore / migrate to a completely new / different device
    Not everything gets retored - any apps whose account data is handled by Accuont Manager (e.g DAVx5, NextCloud) will lose the account settings, as will K-9 Mail (though you can export your settings before the backup, and re-import them after the restore). See this post in the /e/OS community forums for more information on my experiences with this.
    Yeah I've read about this project after the failed backup as well. Looks like another good line of redundancy in addition to SeedVault and partition backups.

    For now I've come to accept that the original data partition is just lost forever despite my best attempt at creating a proper backup. I was kinda hoping there'd be some takeaway lesson here like "If you format Data once, restoring old backups won't work anymore [for some reason]" to explain what went wrong. But it looks like my best bet is trying to back up to SD card rather than through adb in the future and cross fingers that'll work better 😬
    2
    I did a clean flash of 19.1 2023-02-25 MicroG from stock and I can't seem to find the settings for MicroG and don't see it listed in the system apps.
    When I check in /system/product/priv-app I see the folder for GmsCore and the fake store, but there is no apk in it.
    Is there additional setup needed in order to get MicroG working?
    Looks like something went wrong on my side and the apps were missing from the (source) where they were supposed to be. Not sure why.
    Anyway I took measures to avoid this in the future.
    I also uploaded a fixed build (same name, md5 c66cd526c6c92fd9eaa61e42153d3b8e) to AFH, so just download and flash that. You likely don't even need to wipe your data if you don't want to.
    2
    But I am on 19-20220918 - which version does fix this (or is it something completely different I'm experiencing?)...
    There isn't a real fix yet, this happens after reboot or some time without network (e.g. Tunnel or basement)
    You can try updating to latest version and enable the reflash-modem option in XperiaParts and see if that helps.
    Didn't help for me on 17.1 but 19.1 has stuff that is not possible on 17.1 which may help.
  • 54
    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


    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
    • Attempt to fix Android Auto connection (untested)
    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!
    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...