• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM] LineageOS 17.1/18.1 UNOFFICIAL - (Update: 2021-09-18)

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


  • Total voters
    88
Search This thread

Flamefire

Senior Member
Jul 26, 2013
118
179
Sony Xperia XZ1 Compact
I don't think he needs to wipe system if he's only updating from:
18.1 2021-07-20
to
18.1 2021-08-11
Unless I totally missed something. Simply flashing the zip should be enough? Someone correct me if I'm wrong.
Correct. Wiping system will remove gapps. Just flashing the new zip without wipe will keep it.
So yes just install the new zip from recovery works fine for updating
 
  • Like
Reactions: jmbattle

7alvoo

Senior Member
Jul 18, 2019
120
27
Beyond smoldering upgrade solutions ...

It has been a long-standing mistake for me that the caller hears an echo during a phone call if I turn down my speaker volume it is partially solved, but it is completely eliminated only by speakerphone. Unfortunately I can't find the call noise filtering / noise cancellation off option in the call app.
Have you noticed this? Obviously another type but the same problem was detected in S7 as well:
- Audio: Reworked incall audio handling in mixer paths to disable 2nd mic that was picking up noise
 
Last edited:

toejam119

Senior Member
I dirty flashed lineage-17.1-20210811-UNOFFICIAL-lilac.zip over 17.1-20210720 (via TWRP) and when booted to OS was met with "Google Play Services has stopped" error in 1-2 sec repeat. I'm pretty sure I only wiped Dalvik cache and Cache before flashing.

My fix to this was I downloaded latest Open GAPPS (which was open_gapps-arm64-10.0-pico-20210813.zip), rebooted to TWRP recovery, wiped Dalvik cache and Cache, queued lineage-17.1-20210811-UNOFFICIAL-lilac.zip and open_gapps-arm64-10.0-pico-20210813.zip and flashed them, booted to OS and all worked fine, except Magisk was gone, had to flash Magisk-v23.0.zip. Now all seems fine.
 
Last edited:
  • Like
Reactions: andacro

FFW

Senior Member
May 24, 2020
50
34
@Flamefire: now I kept looking at the old thread for almost a month until I finally found out there is a new one - and in the meantime you released not only one but two updates! You are too fast for me o_O

I'll be off to update my phone now - and my bookmark as well ;)
 

jmbattle

Member
Jul 3, 2015
14
2
I dirty flashed lineage-17.1-20210811-UNOFFICIAL-lilac.zip over 17.1-20210720 (via TWRP) and when booted to OS was met with "Google Play Services has stopped" error in 1-2 sec repeat. I'm pretty sure I only wiped Dalvik cache and Cache before flashing.
I also updated from 7/20 to 8/11 builds, albeit using the 18.1 version.
I didn't wipe anything (just enter TWRP, select latest zip, flash, reset), and did not experience any issues with GApps.

I do not use Magisk.
 

GT9000er

New member
Aug 21, 2017
2
0
Hi there, and thanks a lot for this rom.

I had only one issue so far. When trying to enable IMS services, my wlan and sim card would stop working. No connection possible. After disabling and rebooting the problem was gone, but IMS is still disabled of course. I did expect the sim card to cause trouble, but not the wlan module to give up.

What can I do to get IMS working?
 

petefoth

Senior Member
@Flamefire I've been using your device and kernel trees, with my own vendor blobs* to build unofficial and custom /e/ OS ROMs for a while now, and everything has been working fine - thanks.

In my most recent builds, based on your 17.1 branch, I get a problem when trying to play audio through some connected BT devices. The audio does not get routed to the connected BT device, but plays through the phone loudspeaker. The 'Settings | Sounds' page shows that the audio is being played though the BT device even though it is not. This applies to both phone calls and music streaming. Also, it only applies to *some* devices - others seem to work fine.

Your 17.1 ROM works fine, and I suspect the problems are in the depths of vendor/sony/lilac. I wonder whether you have any idea where I should start looking? Do I need to extract the latest vendor blobs from your 17.1 ROM?

* My vendor blobs were extracted from Modpunk's LOS 17.1 v1.6. in December 2020
 

tassee

Member
Nov 6, 2018
15
5
First of all I would like to agree with the previous speakers - thank you for keeping the OS alive!

@Flamefire I've been using your device and kernel trees, with my own vendor blobs* to build unofficial and custom /e/ OS ROMs for a while now, and everything has been working fine - thanks.

In my most recent builds, based on your 17.1 branch, I get a problem when trying to play audio through some connected BT devices. The audio does not get routed to the connected BT device, but plays through the phone loudspeaker. The 'Settings | Sounds' page shows that the audio is being played though the BT device even though it is not. This applies to both phone calls and music streaming. Also, it only applies to *some* devices - others seem to work fine.

Your 17.1 ROM works fine, and I suspect the problems are in the depths of vendor/sony/lilac. I wonder whether you have any idea where I should start looking? Do I need to extract the latest vendor blobs from your 17.1 ROM?

* My vendor blobs were extracted from Modpunk's LOS 17.1 v1.6. in December 2020
I notice something similar - yet for some devices it works (e.g. for a bluetooth box) and for other devices it doesnt (or at least only sometimes with some bluetooth crashes).
I checked the log and found the following:

Code:
08-21 11:14:53.890 10069 10117 I bt_stack: [INFO:device.cc(1363)] f8:30:02:88:03:e6 : HandlePlayPosUpdate
08-21 11:14:53.890 10069 10095 D AvrcpTargetJni: getCurrentPlayStatus
08-21 11:14:53.890 10069 10095 D AvrcpNativeInterface: getPlayStatus
08-21 11:14:53.891 10069 10117 I bt_stack: [INFO:device.cc(520)] f8:30:02:88:03:e6 : PlaybackPosNotificationResponse: Queue next play position update
08-21 11:14:53.903 10069 10095 D AvrcpTargetJni: getCurrentPlayStatus
08-21 11:14:53.903 10069 10095 D AvrcpNativeInterface: getPlayStatus
08-21 11:14:53.904 10069 10117 I bt_stack: [INFO:device.cc(520)] f8:30:02:88:03:e6 : PlaybackPosNotificationResponse: Queue next play position update
08-21 11:14:53.989 10069 10124 D BluetoothAtPhonebook: handleCpbsCommand - atString = ="RC"
08-21 11:14:53.989 10069 10124 D BluetoothAtPhonebook: handleCpbsCommand - set command
08-21 11:14:53.994  2505  2524 E DatabaseUtils: Writing exception to parcel
08-21 11:14:53.994  2505  2524 E DatabaseUtils: java.lang.IllegalArgumentException: Invalid token LIMIT
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.database.sqlite.SQLiteQueryBuilder.enforceStrictGrammarOrderBy(SQLiteQueryBuilder.java:846)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.database.sqlite.SQLiteQueryBuilder.lambda$RN4X37kr4P69Zco8q57M-c-6Pcc(Unknown Source:0)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.database.sqlite.-$$Lambda$SQLiteQueryBuilder$RN4X37kr4P69Zco8q57M-c-6Pcc.accept(Unknown Source:4)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.database.sqlite.SQLiteTokenizer.tokenize(SQLiteTokenizer.java:108)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.database.sqlite.SQLiteQueryBuilder.enforceStrictGrammar(SQLiteQueryBuilder.java:808)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:569)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:514)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at com.android.providers.contacts.CallLogProvider.queryInternal(CallLogProvider.java:362)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at com.android.providers.contacts.CallLogProvider.query(CallLogProvider.java:291)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.content.ContentProvider.query(ContentProvider.java:1214)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.content.ContentProvider.query(ContentProvider.java:1307)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.content.ContentProvider$Transport.query(ContentProvider.java:267)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:104)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.os.Binder.execTransactInternal(Binder.java:1021)
08-21 11:14:53.994  2505  2524 E DatabaseUtils:     at android.os.Binder.execTransact(Binder.java:994)
08-21 11:14:53.995 10069 10124 E AndroidRuntime: FATAL EXCEPTION: HeadsetService.StateMachines
08-21 11:14:53.995 10069 10124 E AndroidRuntime: Process: com.android.bluetooth, PID: 10069
08-21 11:14:53.995 10069 10124 E AndroidRuntime: java.lang.IllegalArgumentException: Invalid token LIMIT
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:170)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:140)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at android.content.ContentProviderProxy.query(ContentProviderNative.java:423)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at android.content.ContentResolver.query(ContentResolver.java:944)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at android.content.ContentResolver.query(ContentResolver.java:880)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at android.content.ContentResolver.query(ContentResolver.java:836)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.bluetooth.hfp.AtPhonebook.queryPhonebook(AtPhonebook.java:423)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.bluetooth.hfp.AtPhonebook.getPhonebookResult(AtPhonebook.java:392)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.bluetooth.hfp.AtPhonebook.handleCpbsCommand(AtPhonebook.java:247)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.bluetooth.hfp.HeadsetStateMachine.processAtCpbs(HeadsetStateMachine.java:1745)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.bluetooth.hfp.HeadsetStateMachine.processUnknownAt(HeadsetStateMachine.java:1888)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.bluetooth.hfp.HeadsetStateMachine.access$3200(HeadsetStateMachine.java:74)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.bluetooth.hfp.HeadsetStateMachine$ConnectedBase.processMessage(HeadsetStateMachine.java:957)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.bluetooth.hfp.HeadsetStateMachine$Connected.processMessage(HeadsetStateMachine.java:1083)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:992)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:809)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:107)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at android.os.Looper.loop(Looper.java:214)
08-21 11:14:53.995 10069 10124 E AndroidRuntime:     at android.os.HandlerThread.run(HandlerThread.java:67)
08-21 11:14:53.997  1389 10225 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
08-21 11:14:54.000  1389  1421 I ActivityManager: Showing crash dialog for package com.android.bluetooth u0
08-21 11:14:54.171   791 10114 I [email protected]_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
08-21 11:14:54.173   791 10114 I [email protected]_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
08-21 11:14:54.173   791 10114 I [email protected]_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
08-21 11:14:54.406 10069 10095 I bt_stack: [INFO:btif_config.cc(756)] hash_file: Disabled for multi-user
08-21 11:14:54.406 10069 10095 I bt_stack: [INFO:btif_config.cc(798)] write_checksum_file: Disabled for multi-user, since config changed removing checksums.
08-21 11:14:54.455 10069 10095 D AvrcpTargetJni: getCurrentPlayStatus
08-21 11:14:54.456 10069 10095 D AvrcpNativeInterface: getPlayStatus
08-21 11:14:54.667   790   888 D audio_hw_primary: out_standby: enter: stream (0xe600d000) usecase(0: deep-buffer-playback)
08-21 11:14:54.853   790   888 D audio_hw_primary: disable_audio_route: reset and update mixer path: deep-buffer-playback
08-21 11:14:54.854   790   888 E soundtrigger: audio_extn_sound_trigger_update_stream_status: invalid input device 0x0, for event 2
08-21 11:14:54.854   790   888 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_info->id 0 of type 0 for Event 2, with Raise=1
08-21 11:14:54.854   790   888 D sound_trigger_platform: platform_stdev_check_and_update_concurrency: concurrency active 0, tx 0, rx 0, concurrency session_allowed 1
08-21 11:14:54.854   790   888 D hardware_info: hw_info_append_hw_type : device_name = speaker
08-21 11:14:54.854   790   888 D audio_hw_primary: disable_snd_device: snd_device(2: speaker)
08-21 11:14:54.862   790   888 D hardware_info: hw_info_append_hw_type : device_name = vi-feedback
08-21 11:14:54.862   790   888 D audio_hw_primary: disable_snd_device: snd_device(182: vi-feedback)
08-21 11:14:54.862   790   888 D msm8974_platform: platform_split_snd_device: snd_device(182) num devices(0) new_snd_devices(1684960623)
08-21 11:14:54.862   790   888 I soundtrigger: audio_extn_sound_trigger_update_device_status: device 0xb6 of type 1 for Event 0, with Raise=0
08-21 11:14:54.862   790   888 D audio_hw_primary: disable_audio_route: reset and update mixer path: spkr-vi-record
08-21 11:14:54.862   790   888 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_info->id 48 of type 1 for Event 2, with Raise=0
08-21 11:14:54.867   790   888 I soundtrigger: audio_extn_sound_trigger_update_device_status: device 0x2 of type 0 for Event 0, with Raise=0
08-21 11:14:54.867   790   888 D audio_hw_extn: audio_extn_get_anc_enabled: anc_enabled:0
08-21 11:14:54.867   790   888 D audio_hw_extn: audio_extn_get_anc_enabled: anc_enabled:0
08-21 11:14:54.867   790   888 D audio_hw_primary: out_standby: exit
08-21 11:14:54.904 10069 10117 I bt_stack: [INFO:device.cc(1363)] f8:30:02:88:03:e6 : HandlePlayPosUpdate
08-21 11:14:54.904 10069 10095 D AvrcpTargetJni: getCurrentPlayStatus
08-21 11:14:54.904 10069 10095 D AvrcpNativeInterface: getPlayStatus

Hope this is helpful in finding the problem.
 
  • Like
Reactions: petefoth

drissie

Member
Jul 4, 2019
9
4
Firstly, thank you @Flamefire for keeping this ROM alive - much appreciated!

I am a complete noob I need a bit of help before I can use it though. I am still running modpunk's 16.0 (I know 🙈) and I'm wondering if I can dirty flash your 17.1 over it? The TWRP version is the same, so can I simply download your zip, boot into recovery and install it? And wipe cache and Dalvik? Or were there more steps I needed to do? Thanks in advance!
 

petefoth

Senior Member
I've now done a clean build using earlier working device & kernel trees (mine, not FF's) and my stored vendor blobs, and BT audio is now working fine. So it looks like the problem was a mismatch between device tree and vendor blobs.

My next step is to extract vendor blobs from FF's ROM and use them to build with their kernel & device trees.
 

jmbattle

Member
Jul 3, 2015
14
2
Currently working on an attempt for a major performance improvement and Bugfix on the 17.1 issue (under the hood, found some potential security issues)
"Major performance improvement" sounds great!

This would be for both 17.1 and 18.1, yes?

By the way, would it be worthwhile donating a device to allow you to develop and test both 17.1 and 18.1 simultaneously?
 

Sprnza

Member
Mar 15, 2018
9
1
Tried dirty upgrade to the latest release with TWRP 3.2.1 and got boot loop. Fixed after upgrade TWRP to the latest 3.3.1. So I think 3.3.1 is required and not recommended as stated in the first post.
 
  • Like
Reactions: toejam119

Flamefire

Senior Member
Jul 26, 2013
118
179
Sony Xperia XZ1 Compact
"Major performance improvement" sounds great!

This would be for both 17.1 and 18.1, yes?

By the way, would it be worthwhile donating a device to allow you to develop and test both 17.1 and 18.1 simultaneously?
No only 17.1. Basically building with the same compiler as 18.1 which has better optimizations (3 versions difference) and found a few bugs through that...

This is a kind offer but no. I don't really have time to do much dev on this. When building the 17.1 I use it myself and see that works. Then I provide this here for others to benefit too. The 18.1 is just a bonus as changes to 17.1 usually work on 18.1. But as mentioned I don't have time for dev or testing on something I don't use myself anyway :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Excellent! I'd be happy to test both Casting and Safetynet for the October version of 18.1 for you. Sounds like I may be re-flashing August anyway if I can't get this worked out, so its not like I'm risking much :p Shouldn't be a problem to dirty-flash a version with an earlier build date, right? I wouldn't think TWRP would care.


    (Feel free to send me an email or DM with your beta version of October 18.1, if you don't want to release the untested verion publically yet @Flamefire and I'll test Safetynet immediately)
    I uploaded the new versions. If you could give the 18.1 a try and check if safetynet passes it would be great. If it does not send me the output of `adb shell getprop` and I'll rebuild with a fix as required.
    See https://androidfilehost.com/user/?w=settings-dev-files&flid=327069 for the download
    2
    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
    I don't have a chromecast to test and no idea where to start looking for the issue... Is there anything in the logcat that may hint at the issue? Maybe compare the output for the working and broken version to see if that turns up anything.

    In any case I just built the October update for 17.1 which caused some trouble with getting CTS/Safetynet to pass. Trying the same on the 18.1 build now and will upload that later. Would need someone to test the 18.1 version anyway to check if safetynet passes there as well. And maybe the chromecast issue is also resolved there already. Could be something from Lineage upstream which they may have fixed there.
    1
    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!
    1
    @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.
    1
    Hi all, just a quick info from me and a question: As I already wrote I'm still using LOS 17.1/Android 10 as it allows using the Sony camera which Android 11 does not and the benefits of Android 11 compared to 10 are not worth the switch for me.
    However with the recent release of Android 12 switching to that becomes worth it due to various improvements over those 2 versions.
    However porting a new LOS to a that device isn't easy and requires quite some testing (and I can't even promise I'll succeed)
    So in order to keep supporting multiple LOS/Android versions I'd need a spare device for testing.

    Hence I'm asking if anyone would be able to donate an XZ1C to me for that. Maybe someone knows someone who has an unused phone, maybe with cracked screen but otherwise working or one which isn't used anymore. Again: I can't promise anything in exchange and I know the XZ1C is still such a good phone that prices aren't exactly low. So this is really meant as an outreach to the community in case anyone has somehow access to an unused phone which I can use for testing and see what I can do with that.
    Of course you can tell me which LOS version you use yourself and I'll try and take a bit of extra effort to support that as long as I can.

    Thank you all for your support and the nice words here which motivate me to put in that extra effort to provide you with a ROM that works on more than only my device and even one I don't even use myself!

    Sadly I only have the XZ1C I use. The above is duly noted though, if I get hold of another one somehow, or decide to replace mine before you stop developing the rom.

    Shipping to your country according to your profile is cheap and simple too, not as prohibitive as shipping overseas last time I did something similar :)
  • 28
    LineageOS 17.1/18.1 for Sony Xperia XZ1 Compact

    logo.png


    RELEASE

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

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

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

    DOWNLOAD

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

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

    INSTALLATION

    Put the zip file of the ROM on you sdcard or internal store and boot into recovery.
    I suggest to use modpunks TWRP recovery. Again: Don't forget the md5sum file!
    TWRP 3.3.1-0 by modpunk for LineageOS 17.1
    TWPR 3.5.0-0 by derf elot for LineageOS 18.1
    Or use the latest TWRP from https://twrp.me/sony/sonyxperiaxz1compact.html.

    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.

    KNOWN ISSUES
    • UnifiedNlp doesn't work with LineageOS 18.1 yet
    • Spell checking doesn't switch if you change keyboards
    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 any chance to actually test it myself.
    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
    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

    ROM OS Version: Android 10/11
    ROM Kernel: Linux 4.x
    Based On: LineageOS

    Version Information
    Status:
    Stable
    Stable Release Date: 2021-07-20
    11
    CHANGELOG

    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
    6
    Updated with the July security patches.
    Note: AndroidFileHost was quite quirky today, so use the md5sum files to verify the integrity of the files
    6
    "Major performance improvement" sounds great!

    This would be for both 17.1 and 18.1, yes?

    By the way, would it be worthwhile donating a device to allow you to develop and test both 17.1 and 18.1 simultaneously?
    No only 17.1. Basically building with the same compiler as 18.1 which has better optimizations (3 versions difference) and found a few bugs through that...

    This is a kind offer but no. I don't really have time to do much dev on this. When building the 17.1 I use it myself and see that works. Then I provide this here for others to benefit too. The 18.1 is just a bonus as changes to 17.1 usually work on 18.1. But as mentioned I don't have time for dev or testing on something I don't use myself anyway :)
    6
    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 ?
    I'm using an XZ1C with 17.1 myself and am keeping that updated as much as possible. This includes security patches and kernel patches and updates. I also included some stuff I need for myself (e.g. the SafetyNet fix w/o Magisk to use GooglePay) But I'm not really doing any development, e.g. adding new features beyond that.
    What I do for 17.1 I also add to 18.1 but I have no way to test that myself as I only have that one device, hence the disclaimer at the top. Adding stuff or fixing bugs in 18.1 is hence to dangerous for you guys, as I won't know if that bricks your phones. So I really only add what I tested in 17.1 and assume to be fine in 18.1

    TLDR: 99.9% security patches only. The ROM is already stable enough thanks to the original authors.