[ROM][OFFICIAL][enchilada][12] LineageOS 19

Search This thread

lm089

Senior Member
It used to be that changing gapps meant wiping system
that's what I had in mind too. But then, how do I wipe system in the first place? TWRP 3.6.1 and 3.6.2 only offer to wipe Cache, Data, Internal Memory, USB, or Vendor. But no "wipe system". In addition to that I can "format data" which I think is like a factory reset (which I never was able to run, always resulted in runtime errors, but that's a different story)
From my older devices (Sony Xperia) I know that TWRP has this "wipe system" option.

On the other hand I don't remember ever having seen a "wipe system" option in LOS recovery when I was running it during first installation. So question is: how would I wipe system in the first place? Is that possibly a fastboot or adb job?
 

Chris Kerry

Senior Member
Nov 23, 2010
71
19
Greetings All.
I just wiped Cache and Data (leaving the Internal Memory and Vendor as was). Then, went through the usual:

1. LOS recovery >> latest LOS 19.1 ROM; reboot into LOS rec. >> latest MGapps; reboot into LOS rec. [again to ensure that both A/B were fully LOS installed and Gapped because I always have issues with the TWRP stage 1st System reboot] >> latest LOS 19.1 ROM; reboot into LOS rec. >> latest MGapps
2. Reboot into Bootloader >> TWRP.img
3. Reboot into TWRP.img >> flashed TWRP.zip from adb (to be sure A/B fully TWRP-applied) >> Reboot into System [I always need to force an active partition switch if not reboot attempts never boot system but return to TWRP]
4. Usual initial setup of phone and main Google account
5. No force closes so far. Internal memory is populated as before (since it wasn't wiped)
6. Reboot to TWRP >> make boot backup into USB-attached storage (since TWRP refused to write into LOS19.1 Int.Memory]
7. Reboot to System >> Install Magisk 25.1 APK (previously in the internal memory) >> Use Magisk to patch the boot image (renamed to boot.img) >> copied the patched IMG to PC
8. Rebooted to Bootloader >> fastboot the patched IMG >> reboot to System
9. Install swift backup APK >> restore apps, messages and call logs

Everything worked well, this time, also the text-to-speech options (whether Google or Ivona's).
Am I going to have to be going through all these steps to apply future LOS 19.1 updates? That would be quite inhibiting if so. Well, let's see how the future ROM idiosyncrasies pan out.
 
Last edited:
  • Like
Reactions: lm089

lm089

Senior Member
Am I going to have to be going through all these steps to apply future LOS 19.1 updates?
Shouldn't be necessary, just use the built-in updater.
What I do after applying an update and before reboot:
1. run Magisk module "Twrp_a_b_retention script" if you want to stick to using twrp
2. from magisk manager app install magisk to unused slot

Some say Magisk is sticky now between updates, but that extra steps is easy enough
 
Last edited:
  • Like
Reactions: Spaceoid
that's the point: there's no system partition to select in (my) TWRP 3.6.2-11 for OP6 under Advanced Wipe, just the options I mentioned above o_O (if there was a screenshot feature in TWRP I'd post it)
I don´t have it on me, but I don´t remember this phone being dual slotted with a slot_a / slot_b replacing system.
Could you have requested that system be read-only when you first set up TWRP ?
 

lm089

Senior Member

Chris Kerry

Senior Member
Nov 23, 2010
71
19
Shouldn't be necessary, just use the built-in updater.
What I do after applying an update and before reboot:
1. run Magisk module "Twrp_a_b_retention script" if you want to stick to using twrp
2. from magisk manager app install magisk to unused slot

Some say Magisk is sticky now between updates, but that extra steps is easy enough
👍 Many thanks!
I have seen this in the past (for other android 10 and 11 ROMs) but did not know that it would work for this LOS19.1 (Android 12.1) which needs such a finicky installation procedure.
 

lm089

Senior Member
Just a question out of pure curiosity - no complaint: why is it that LOS 19 is taking so long (at least 1 hour on my device) for an OTA update? I downloaded the package at 9:30 this morning then started the update right away. At 11:30 the updater finished. Even if I keep my phone awake all the time I have to be prepared for an hour or so (the updater apparently is taking a break as soon as the phone is in standby mode). Could that have to do with the way I setup the phone, or with apps I installed? None of the other updaters (LOS on different phones, or OOS on this one here) ever took longer than 10 or 15 minutes.
 
Last edited:

jiyermin

Member
Aug 10, 2016
17
1
is there any guide to roll back to OXYGENOS? have LOS19 atm, but noticed there are some features in oOS i really miss..
 

olifee

Senior Member
Sep 12, 2011
228
145
OnePlus 6
Just a question out of pure curiosity - no complaint: why is it that LOS 19 is taking so long (at least 1 hour on my device) for an OTA update? [...] Could that have to do with the way I setup the phone, or with apps I installed?
I also wondered about that and had a look via `logcat`. What happens is that after the actual update installation, `dex2oat` is triggered for the most commonly used apps (seems to be about 50 % of the apps). I'm not sure whether this is a new feature with Android 12, but this usually takes up to one hour for me, too, since I have many apps installed.

In short, this means the most commonly used apps are optimized for the phone before the reboot to the new system. The same process usually happens when the phone is idle (and connected to the charger) for over two hours, e.g. when charging overnight.

I think this happening right during OTAs is something new, though, but it likely improves the "post-OTA-experience" a bit since apps will start faster before the first "overnight charge", i.e. "things will settle" faster ;-).

The time for updates to run through can be improved (at cost of more battery usage) by going into the updater, pressing the three dots in the top right corner, and then in settings selectiong to give priority to the update process. This shortens down the process by 20-30 % for me.
 
  • Like
Reactions: lm089

lm089

Senior Member
The time for updates to run through can be improved (at cost of more battery usage) by going into the updater, pressing the three dots in the top right corner, and then in settings selectiong to give priority to the update process. This shortens down the process by 20-30 % for me.
Thanks, I sure will try that next time (if I remember... ;))
 
  • Like
Reactions: olifee

Spaceoid

Senior Member
Mar 29, 2013
345
118
Dortmund
A second comment on the recently new behaviour of the stock gallery app. It's a minor 'issue' though.
I like to change my background images frequently. Up till two weeks ago, I could do so by just opening an image in the stock gallery app, entering the top right menu and selecting "Set as..." and "Nova background image" (I use Nova launcher).
For two weeks now the menu option has completely vanished. I have to enter the LOS settings, go down to the Design, Wallpaper menu, click "Change wallpaper", and then I have to search for the image file in the file browser. If I select the system gallery for image selection instead, my background image is shifted to the complete right, no matter which part of the image I select as a wallpaper.

I assume this is due to a new gallery app version? I wonder though why the gallery devs (I assume the AOSP devs) would remove the option to set a wallpaper. Anybody here experiencing similar behaviour or knowing a better workaround? 🤔
 

jfreak27

Senior Member
Apr 2, 2013
105
8
Nagpur
Installed LOS 19.1 from OOS11 couple of days back. ROM feels great. Very smooth. No ANR, no random restarts, no freeezes.

Going to install Magisk now.
Can I just sideload magisk.zip via recovery?
Magisk GitHub says it's not recommended anymore?
 

Nihal @A-JAX

Senior Member
Oct 18, 2013
291
224
Bangalore
Apart from buggy VoLTE which only works once in a while, there are no major issues in this official ROM.

Anyone relying only on VoLTE for calls and SMS, stay away from this ROM for now! Else need to keep rebooting the phone to get VoLTE working. Airplane mode and fix connectivity option under internet settings doesn't help.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I've also experienced the notification sound crackling issue, but only on first install.

    The first time I installed (maybe 3-4 builds ago), the OTP, trust, and setup notifications during/after the setup process were all very crackly. I tried calling the phone and sending it messages too, all the notifications crackled. Then I tried a media audio stream (YouTube video in the browser), and it sounded fine. Immediately after that, the notifications started sounding fine too.

    The next day I did another clean flash, and I had the same crackling notifications during the setup process. This time, I didn't try anything else, just started a Swift Backup restore and left my phone for half an hour. When I came back, the notification sounds were perfectly fine. 🤷‍♂️

    Edit: Forgot to mention, I have no problems with notifications now, and I leave my phone on ring mode for most of the day.
    2
    Okay, I managed to restore the backup. I'll post my exact steps for reference, perhaps it'll help someone. Perhaps even future me, when I get into this mess again.

    TL;DR: Keep system installation zip for each backup you wish to be able to restore.

    So, I had two backups, newer based on LOS from 28.06 and older based on LOS 15.06. I had an install zip with LOS version from 15.06, but I didn't have one from 28.06 and it was already gone from LOS download site.

    1. First, I copied everything from internal storage onto my computer. This procedure will wipe data and sdcard so copy your twrp backups and other data to avoid losing it.
    2. Rebooted to fastboot (power+volume up)
    3. Flashed LOS recovery: fastboot flash boot ./lineage-19.1-20220615-recovery-enchilada.img
    4. Booted to recovery (from fastboot)
    5. Used factory reset option (this will wipe your data including internal memory, backup your data)
    6. Flashed the same version of LOS as was in the older backup adb sideload adb sideload ./lineage-19.1-20220615-nightly-enchilada-signed.zip (used install update option)
    7. Rebooted recovery (switches active slot)
    8. Flashed gapps adb sideload ./MindTheGapps-12.1.0-arm64-20220605_112439.zip
    9. Flashed again the same version of LOS as was in the older backup adb sideload adb sideload ./lineage-19.1-20220615-nightly-enchilada-signed.zip (now in the second slot)
    10. Rebooted recovery (switches active slot)
    11. Flashed gapps again adb sideload ./MindTheGapps-12.1.0-arm64-20220605_112439.zip
    12. Went through initial setup in the OS - didn't set any pin
    13. Rebooted to fastboot adb reboot bootloader
    14. Booted TWRP fastboot boot twrp-3.6.2_11-0-enchilada.img
    15. It didn't decrypt data partition
    16. Flashed TWRP: advanced -> flash current TWRP
    17. Rebooted recovery - it decrypted data now
    18. Sideloaded magisk (because I had it in my backup, not sure if that's needed) adb sideload Magisk-v25.0.apk
    19. Downloaded the older backup (with LOS from 15.06) onto the phone adb push ../2022-07-03--19-28-17_lineage_enchilada-userdebug_12_SQ3A22060500/ /sdcard/TWRP
    20. Restoring data alone didn't work (system didn't finish booting)
    21. Restoring boot, system, data worked
    22. Rebooted twice for proper working system
    Now I had a working system with a month old backup, but I wanted to restore the newer backup for which I didn't have the system install zip. I'm sure it worked by an accident but I'll post my steps. They were taken right after I confirmed that a month old backup is restored and is booting properly.
    1. First I switched to the other slot in TWRP.
    2. Made a backup of the key store so that TWRP will be able to decrypt data: adb pull /data/system/recoverablekeystore.db .
    3. Restored only data from the newer backup
    4. Restoring data overwrote the keystore so I backed this one up as well: adb pull /data/system/recoverablekeystore.db ./recoverablekeystore.db.from_backup
    5. Pushed original keystore (AFAICT this enables TWRP to decrypt the data): adb push ./recoverablekeystore.db /data/system/recoverablekeystore.db
    6. Rebooted to system, however it didn't finish booting
    7. Rebooted to recovery (it decrypted the data)
    8. Restored keystore from backup: adb push ./recoverablekeystore.db.from_backup /data/system/recoverablekeystore.db (effectively this is the same as restoring data from backup again at this point)
    9. Restored system and boot from newer backup
    10. Rebooted to system and it booted properly.
    Now, I'm certain that some of these steps are not needed, however I have a working system now and I can't spend any more time to narrow it down. It weird that it worked, since I tried similar steps while first flashing newest LOS (27.07) and when I restored system+boot I got into recovery bootloop.

    For now, it seems that the only working way to restore backup is to first have system installation zip. Perhaps some shenanigans with keystore could work, but I couldn't work that out.

    Thanks to @lm089 and @tabletalker7 for their instructions.
    2
    That got me thinking:
    Just tried to use the alert slider every other hour, and voila: No more issues until now.
    Although it's not a perfect solution, it works fine for me.

    Thanks a lot!
    So this evening I let my phone sit in loud mode for around 4 hours and did not notice any sound issue. Might be the time span was too small, or it is somewhat not a general problem...

    Edit: The same evening, I received a SMS without receiving a notification! I just saw it right now after opening the SMS app. First time it happens. As I read further above, this might be a kinda known issue. Still never happened to me before, and I communicate lots via SMS.
    Still, might also be I swiped the notification away by accident. :D

    Edit2: I found this regarding the SMS 'issue', which is quite interesting:
    https://www.reddit.com/r/LineageOS/comments/n5dttk Seems to be a long-known bug with the stock SMS app of LOS. Two different fixes are offered, too, either via ADB command or by switching to a different, third-party messaging app.
    1
    i am on latest oos what instructions do i need to follow to upgrade to 19.1 safely without errors ?
    This is the guide for you:

    If you follow it closely, no errors or problems should arise.
    1
    Any chance to have Wireguard kernel implementation?
  • 37
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    6
    Just did a dirty flash from LOS 18.1 and everything works fine.

    I had to reinstall some Google apps (YouTube, Gmail, Keep, GCam, Photos), as they stopped working after the upgrade (maybe because I accidentally clicked No on the Signature verification failed screen while flashing Gapps and didn't notice, then the OS didn't boot. whoops. So I went back into the recovery and flashed Gapps again. Sure enough, the install went through. So be careful and make sure to click the correct button, lol)

    Everything else seems to work perfectly!

    Thanks again LuK for your work!

    In case anyone with Gapps and Magisk wants to try a dirty flash from 18.1, here are the steps I did:
    (you're on your own if things break! better to do a clean flash! magisk isn't officially supported!)

    1. Restored images in Magisk
    2. Removed PIN and fingerprints
    (Not sure if these first two steps are needed, but did them just in case)
    3. adb reboot sideload
    4. adb sideload lineage-19.1-20220426-nightly-enchilada-signed.zip
    5. Advanced->Reboot to Recovery
    6. Apply Update->Apply from ADB
    7. adb sideload MindTheGapps-12.1.0-arm64-20220416_174313.zip
    8. adb sideload Magisk-v24.3.apk
    9. Back->Reboot system now
    5
    I'm using a single SIM and I see the same thing often. I guess it depends on the amount of icons you have in the status bar. I observed this since the first build
    Change the smallest width to 411 in developer options.
    Before OOS 11 it was set to 411 by default but that changed with OOS11.
    4
    I'm on the May 17th enchilada nightly, and came directly from 18.1. I'd like to use ANT+, but no worky :confused:. Is this a known issue? Are there plans to fix it?

    ANT+ also didn't work when I went from 17.1 to 18.1, but I fixed it by upgrading the firmware. I tried that again on 19, but it didn't fix it this time.

    Here is what the ANT Tester app shows on LOS 19:

    View attachment 5619435
    4
    Question: Will there ever be more stable versions than the "nightlies"? I'm unsure where to put them in terms of quality and stability- should they be considered as "alpha" versions? Or are they even more reliable than "betas"?

    Thanks in advance.
    imo the first 2 nightlies were perfectly stable. No crashes, fc, excessive battery drain, whatever. (y)