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

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.

April fools day but no joke: Updates are out!
Enjoy and stay safe!

Looks I did got april fooled -.-

So yes, there is a bug with the creation of the zip files. I found that the build process creates hard links. So when I build the MicroG version after the vanilla version it kind of "overwrites" the vanilla zip.

I noticed that when testing the 19.1 version although I couldn't explain it. But I fixed that before uploading.

When testing the 17.1/18.1 versions I had already copied them to the test phone before they got "overwritten", so I didn't notice it there.

Anyway I uploaded the correct 17.1 file now from own phone but need to rebuild the 18.1 file as I already overwrote it locally. I'll upload that in the next few minutes/hours.

@decsimon I assume the crash happens because there are now 2 playstores: The Gapps and MicroG one which may cause the FC. Simply flash the fixed version of the ROM which should resolve this.

I deeply apologize for the mistake!
I took measures to avoid this happening in the future and strongly recommend again to NOT install a ROM with a mismatched or skipped digest check, i.e. especially make sure to download the md5sum file too and make sure the "Skip digest check" checkbox in TWRP is NOT enabled.

jurkoman said:

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.

jurkoman said:

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)

foresto said:

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

petefoth said:

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.

petefoth said:

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)

petefoth said:

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