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

Search This thread

diemadedrei

Senior Member
Mar 13, 2012
680
253
OnePlus 6
Google Pixel 6 Pro
I'm on the latest build and camera works fine for me. Can you get logs that have something that maybe Luk can look? Without being able to reproduce it, I don't think there is anything that people can help here. Do logcat from computer and make things crash by opening the apps.
Here's a log. I opened gcam multiple times and the stock camera app once at the end. From what I see, there seems to be a permissions error and/or a problem with vrcore (wtf). Does anyone have a better understanding of this?
 

lm089

Senior Member
Thanks for the suggestion, unfortunately that was not it. The switch was enabled. I also tried disabling and enabling again, but to no avail. The camera apps still shouldn't crash though if this would have been the case but instead display an error.
I assume you already tried to delete Cache and data from the apps?
I'm still at last week's build (20220510), no problems so far (using stock and GCam apps)
 

lm089

Senior Member
Yep, tried that. From the logs, it seems the system can't find the physical cameras though. I have no idea why
Really don't have the slightest clue, esp. since I remember you recently wrote something about camera useage (or was that someone else? ;)). Just another idea: could you try to uninstall the extra camera app(s) leaving just the stock one, then reboot? Maybe even dirty flash LOS? Idea is that maybe one of the other apps is interfering...
 

diemadedrei

Senior Member
Mar 13, 2012
680
253
OnePlus 6
Google Pixel 6 Pro
Really don't have the slightest clue, esp. since I remember you recently wrote something about camera useage (or was that someone else? ;)). Just another idea: could you try to uninstall the extra camera app(s) leaving just the stock one, then reboot? Maybe even dirty flash LOS? Idea is that maybe one of the other apps is interfering...
Tried that, same behavior 😕
 

Mike69pt

Senior Member
Dec 11, 2009
61
1
hey guys, I just installed lineage os coming from stock rom and now any google services says im offline.
any ideas?
 

esbeeb

Member
Jan 25, 2022
7
2
Huawei Nexus 6P
I just did an upgrade from latest Lineage 18.1 -> to latest 19.1, following the stock instructions. After downloading the enchilada .zip file, and the MindTheGapps 12.1.0 .zip for arm64, I verified the checksums, and they were perfect.

When I actually did the install, I got a warning message that was a bit troubling, which was that the checksum failed for the MindTheGapps file (as stated by the phone, in its Recovery mode) when I went to sideload it at the appropriate time, as per the upgrade instructions. I went ahead and installed it anyway, knowing the checksum was OK as verified earlier after download. The adb command itself reported no checksum error over on the laptop, from where the "adb sideload" command was launched.

Despite this warning, I went ahead anyway, and everything seems to have successfully installed (again, no complaint was seen from "adb sideload" on the laptop), and my enchilada seems successfully upgraded to Lineage 19.1.

Note: My security string (which is the important thing to me, which I'm most interested in when it comes to all such updates/upgrades) got bumped to "May 5, 2022", as seen in the phone's Settings -> About Phone -> Android Version -> Android security update
 

madman

Senior Member
Apr 21, 2011
1,652
466
Planet Earth
OnePlus 5
OnePlus 6
hey guys, I just installed lineage os coming from stock rom and now any google services says im offline.
any ideas?
What gapps you used? Did you boot to OS before installing Gapps? I'm guessing you came from latest stock rom so that you have all the expected firmware?

I just did an upgrade from latest Lineage 18.1 -> to latest 19.1, following the stock instructions. After downloading the enchilada .zip file, and the MindTheGapps 12.1.0 .zip for arm64, I verified the checksums, and they were perfect.

When I actually did the install, I got a warning message that was a bit troubling, which was that the checksum failed for the MindTheGapps file (as stated by the phone, in its Recovery mode) when I went to sideload it at the appropriate time, as per the upgrade instructions. I went ahead and installed it anyway, knowing the checksum was OK as verified earlier after download. The adb command itself reported no checksum error over on the laptop, from where the "adb sideload" command was launched.

Despite this warning, I went ahead anyway, and everything seems to have successfully installed (again, no complaint was seen from "adb sideload" on the laptop), and my enchilada seems successfully upgraded to Lineage 19.1.

Note: My security string (which is the important thing to me, which I'm most interested in when it comes to all such updates/upgrades) got bumped to "May 5, 2022", as seen in the phone's Settings -> About Phone -> Android Version -> Android security update
I think you are mistaking signature verification with checksum verification. MTG packages are most likely not signed by LOS team (or maybe they are? I don't remember exactly). If you downloaded them from the official links and verified the checksum, you don't need to worry about things here.
 

ddffnn

New member
Jun 17, 2013
2
0
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:

Screenshot_20220521-102046_ANT Tester.png
 

LuK1337

Recognized Developer
Jan 18, 2013
8,640
17,330
Samsung Galaxy S III I9300
Moto G 2014
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
 

Mike69pt

Senior Member
Dec 11, 2009
61
1
What gapps you used? Did you boot to OS before installing Gapps? I'm guessing you came from latest stock rom so that you have all the expected firmware?
yes i was on the latest stock and figured it out that it was all a permissions issue. now its solved.

on another note, how can i install magisk? my banking app does not work! :(
I've installed everything using lineage recovery sideload. and does it format everything now?
 
Last edited:

Spaceoid

Senior Member
Mar 29, 2013
349
121
Dortmund
yes i was on the latest stock and figured it out that it was all a permissions issue. now its solved.

on another note, how can i install magisk? my banking app does not work! :(
I've installed everything using lineage recovery sideload. and does it format everything now?
Installing Magisk won't wipe anything. The official instructions are here:
 

Mike69pt

Senior Member
Dec 11, 2009
61
1
apologies for so many questions...

I have installed magisk and enabled zygisk and module universal safetynet but still my banking app does not work
tested with a tool to check safetynet status and it passes
 

gamertag128

Senior Member
Nov 15, 2021
50
33
First lockscreen after restarting my phone (lastest build 20220517) is kinda buggy. Can't screenshot it, because screenshots aren't allowed then. Can somebody confirm the issue, or is it just something on my device?
 

vikash1994b

Senior Member
Dec 7, 2012
1,016
611
27
New Delhi
Xiaomi Mi 3
Xiaomi Mi A1
First lockscreen after restarting my phone (lastest build 20220517) is kinda buggy. Can't screenshot it, because screenshots aren't allowed then. Can somebody confirm the issue, or is it just something on my device?
+1
Can you confirm if you're able to export the update from software updater ,for me it just force closes the app.
 
  • Like
Reactions: gamertag128

diemadedrei

Senior Member
Mar 13, 2012
680
253
OnePlus 6
Google Pixel 6 Pro
I still have that camera problem where every camera app is instantly crashing. I tried mindthegapps now, which didn't help. I'm wondering if anyone can tell me, if there is any file or folder I could delete or anything I could flash (like full OOS) that could solve this, short of having to wipe everything. So basically, is there any part of the system that manages cameras that does not get overwritten by LOS? Because I did reflash LOS already.
Edit: OK, reflshed oos in both slots to no avail. Now not even the flashlight works anymore, which it did previously. Guess I'll have to wipe then 😕
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    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
    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
    Clean flashed from OOS 11.2.2 following instructions from lineage wiki. No custom kernel or mods.

    Fingerprint stops working occasionally and goes back to normal after a reboot.

    Anybody else have this issue ?
    Dirty flashed previously from 18 to 19, applied last update from 26/07, fw 11.1.2.2, fingerprint working normally.
    1
    Today I again received two SMS for which I did not reveive any notification. I just saw them upon opening my (stock) SMS app. So my workaround posted above seems not to work completely. Maybe I'll try a different SMS app.

    Edit: I did some further research. Apparently the workaround I posted a little further above IS in fact working, it just has to be re-applied after every LOS update. So, for now it seems to be up to the user to either whitelist the stock SMS app from doze after every update via ADB, or to switch the standard SMS app completely.
    Edit2: It seems that whitelisting the stock SMS app in fact DOES survive updates. My SMS app STIILL got shut down by doze mode, though. Which probably leaves switching to a non-stock SMS app the only solution for reliable SMS reception at the moment.
  • 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)