Development [ROM][OFFICIAL][lemonadep][13] LineageOS 20

Search This thread

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,309
34,658
Halifax
GT-i9250
Google Nexus 4
LOS ships firmware for this device so it's possible it changes enough between regions and causes the issues people are having. It's the only theory I have for why some have lots of problems (keystore messed up for tons of apps with FC's everywhere, which I had previously until reflashing), some have some problems (gplay/firefox weirdness), and some appear to have no problems.

My personal build is using latest t-mo blobs/radio, but I can't remember if I went directly from tmo firmware to LOS, at some point I'll MSM and go direct to see if it makes it problem free.
Right, but arguably if Lineage's included firmware/vendor is going to match anything (and therefore presumably cause fewer problems) it'll be the Global device/ROM variant, which I do have, and which definitely is having some GApps problems, at least with the dirty upgrade from 19.1+MindTheGapps12.1 to 20+MindTheGapps13.
 

joecool1029

Senior Member
Jan 17, 2011
198
45
Right, but arguably if Lineage's included firmware/vendor is going to match anything (and therefore presumably cause fewer problems) it'll be the Global device/ROM variant, which I do have, and which definitely is having some GApps problems, at least with the dirty upgrade from 19.1+MindTheGapps12.1 to 20+MindTheGapps13.
It is based on C.66 blobs currently from Global. If that helps...
 
  • Like
Reactions: osm0sis

VelosterM14

Senior Member
And our devices are Global (LE2125)...

I brought that first one I MSM'd back all the way back to 1/10/23 LOS 20 using the upgrade path I'd outlined previously (MSM -> 11.2.10.10 -> LOS 18.1 -> 19.1 -> 20.0 ) with a full data wipe from recovery immediately prior to each LineageOS install (18.1) or upgrade (19.1, 20), and manual config of cert store and app install/config of preferred email client. I ran into one problem while setting up user certs in the cert store, cleared all credentials and rebooted, then got them (our CA cert, my mail client cert, and adaway self-signed cert) added back.

Within a few hours of that yesterday I had my first SSL "cert required" error message in FairEmail where it was not able to read the configured client cert from the store to present it to the server.

So I am at a loss here, no idea what else to do or try. "I guess the f***in' thing is broken" (My Cousin Vinny) comes to mind.

If someone who has seen these kinds of problems with the "fragility" of the user certs/cert store in Android 13/LOS20, as I and others have described in this topic, has a specific path from MSM to LOS20 that they followed which got them there with stable user cert behavior, please share the exact path you followed (which firmware upgrades applied etc. too) and I will follow that and see if I can reproduce as well.

-----
EDIT: I see that what looks to be the latest full A12 OTA for LE15AA / LE2125 available on the XDA OP9Pro OTA repository topic is LE2125_11_C.65. (C66 seems to be there for EU)
So would another possible valid upgrade path be:
MSM -> 11.2.10.10 OTA manual .zip in updater -> 11_C.65 OTA manual .zip in updater -> Lineage OS 20 *install* ?
or maybe even just:
MSM -> 11_C.65 -> Lineage OS 20 install?

And if so, what are chances that my phones are any different with wiped data along the way when I land in LOS20 if I did that instead of 11.2.2.2 -> 11.2.10.10 -> LOS18.1 install -> 19.1 upgrade -> 20 upgrade?

-----

If there IS a difference somehow based on how we got to 20 it would be good to figure out what/why.


In case it matters I am magisk rooted as well, using the method most recommend/follow - boot from adb bootloader with patched boot image , install magisk 25206 apk, direct install method in magisk to patch the stock LOS boot image (and get a restorable unrooted image), reboot, reboot into adb sideload and sideload the magisk apk again as .zip (symlink with .zip extension to the apk comes in handy...) to get the addon.d mod. (Rooting not done until after all updates/upgrades completed...)

Thanks
 
Last edited:

Eric_Lev

Senior Member
Jan 27, 2019
1,426
2,613
Angers
sourceforge.net
Yikes. Guess I'll have to bite the bullet and give that a try as well. Likely I'll just format data though, MSM shouldn't be necessary unless downgrading the bootloader.
FYI, same Google Play issue on lemonade (OP9).


 
  • Like
Reactions: osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,309
34,658
Halifax
GT-i9250
Google Nexus 4
FYI, same Google Play issue on lemonade (OP9).


I tried a format and factory reset yesterday and things look a little better, with more appropriate default permissions for Carrier Services and such, but all the problems remain.

Still Google apps are all behaving weirdly, like my Calendar widget will go blank, Keep will freeze, Messages will get stuck "doing operations in the background" when sending/receiving RCS, the Google account profile pics in all these apps will become grey indicating something wrong under the hood, and then there's the broken video playback in Photos, Chrome, etc.

All these issues need a Force close of the specific app at least to work around them temporarily.

Not sure what to do other than downgrade to 19.1 at this point. I guess I could try GApps from someone other than MindTheGapps to see if that makes a difference, or a different 13 ROM with the same GApps (crDroid maybe?), but I'm not very excited about either option.
 
Last edited:

Eric_Lev

Senior Member
Jan 27, 2019
1,426
2,613
Angers
sourceforge.net
I tried a format and factory reset yesterday and things look a little better, with more appropriate default permissions for Carrier Services and such, but all the problems remain.

Still Google apps are all behaving weirdly, like my Calendar widget will go blank, Keep will freeze, Messages will get stuck "doing operations in the background" when sending/receiving RCS, the Google account profile pics in all these apps will become grey indicating something wrong under the hood, and then there's the broken video playback in Photos, Chrome, etc.

All these issues need a Force close at least to work around them temporarily.

Not sure what to do other than downgrade to 19.1 at this point. I guess I could try GApps from someone other than MindTheGapps to see if that makes a difference, or a different 13 ROM with the same GApps (PA Topaz maybe?), but I'm not very excited about either option.
FYI :

 
Last edited:
  • Sad
Reactions: osm0sis

imbasador

Member
Nov 10, 2022
16
0
And will you add flip camera for selfie?
Screenshot_20230125-222024_Settings Suggestions.png
 

Eric_Lev

Senior Member
Jan 27, 2019
1,426
2,613
Angers
sourceforge.net
I tried a format and factory reset yesterday and things look a little better, with more appropriate default permissions for Carrier Services and such, but all the problems remain.

Still Google apps are all behaving weirdly, like my Calendar widget will go blank, Keep will freeze, Messages will get stuck "doing operations in the background" when sending/receiving RCS, the Google account profile pics in all these apps will become grey indicating something wrong under the hood, and then there's the broken video playback in Photos, Chrome, etc.

All these issues need a Force close at least to work around them temporarily.

Not sure what to do other than downgrade to 19.1 at this point. I guess I could try GApps from someone other than MindTheGapps to see if that makes a difference, or a different 13 ROM with the same GApps (crDroid maybe?), but I'm not very excited about either option.
FYI, logcat about the Google Play issue on lemonade :

 
  • Like
Reactions: eng.stk and osm0sis

VelosterM14

Senior Member
I tried a format and factory reset yesterday and things look a little better, with more appropriate default permissions for Carrier Services and such, but all the problems remain.

Still Google apps are all behaving weirdly, like my Calendar widget will go blank, Keep will freeze, Messages will get stuck "doing operations in the background" when sending/receiving RCS, the Google account profile pics in all these apps will become grey indicating something wrong under the hood, and then there's the broken video playback in Photos, Chrome, etc.

All these issues need a Force close of the specific app at least to work around them temporarily.

Not sure what to do other than downgrade to 19.1 at this point. I guess I could try GApps from someone other than MindTheGapps to see if that makes a difference, or a different 13 ROM with the same GApps (crDroid maybe?), but I'm not very excited about either option.

Sorry to hear that, it sounds like the situation is even more precarious for those using Google services on LOS20.

But I seem to have demonstrated that it's not just people with Google services having trouble.

My LE2125 running 12/27/22 19.1 has been rock solid since setting it up last week, not a single hiccup.

I am glad 19.1 is good because on 18.1 5/24/22 we had to disable 5G (choose LTE mode) or our phones would always crashdump eventually in same function, most often when out in the car (and presumably switching towers). T-Mobile service. It wasn't always like that, it was fine for the first 2-3 months and then one day that just started happening. T-Mobile probably messed up something with all the 5G upgrades (and presumably software upgrades) they're slapping up around here in DFW metro lately. I have the crashdump message somewhere but anywho, I eventually figured out setting to LTE mode completely avoided this crash for us.

LOS 20 has been pretty good for us, and I like it better, except for the annoying cert store problems. If anybody has any ideas on capturing debugging info for it I'm willing to help get it.
 

philip390

Senior Member
Dec 14, 2009
59
1
Stockholm
Anyone got a workaround for the "camera in use" problem?

Did anyone else notice severely degraded audio quality over LDAC when upgrading from 19 to 20? My music suddenly started stuttering, speeding up/slowing down when I am out walking with my headphones on. I have tried disabling/enabling A2DP and fiddled around with absolute volume etc.
 

eng.stk

Senior Member
Mar 29, 2011
7,222
61,210
OnePlus 5T
OnePlus 6
FYI, same Google Play issue on lemonade (OP9).



I tried a format and factory reset yesterday and things look a little better, with more appropriate default permissions for Carrier Services and such, but all the problems remain.

Still Google apps are all behaving weirdly, like my Calendar widget will go blank, Keep will freeze, Messages will get stuck "doing operations in the background" when sending/receiving RCS, the Google account profile pics in all these apps will become grey indicating something wrong under the hood, and then there's the broken video playback in Photos, Chrome, etc.

All these issues need a Force close of the specific app at least to work around them temporarily.

Not sure what to do other than downgrade to 19.1 at this point. I guess I could try GApps from someone other than MindTheGapps to see if that makes a difference, or a different 13 ROM with the same GApps (crDroid maybe?), but I'm not very excited about either option.

Yeah, I can replicate some of that, happens specially when the device stays idle more time it seems.
A reboot fixes it normally, but a few hours later is back.
 
  • Like
Reactions: osm0sis

Eric_Lev

Senior Member
Jan 27, 2019
1,426
2,613
Angers
sourceforge.net
  • Like
Reactions: osm0sis

Zhono

Senior Member
Dec 6, 2012
158
44
Had the same issue with everything constantly breaking, and needing to force stop google play services every couple of hours, after I dirty flashed from 19.1 to 20. Was tired of it, and finally had a day off to deal with it, so I backed up up all of my stuff with Swift Backup, wiped data, setup the rom again, restored all of my backups(took like 4 hours), and everything seemed fine. Forgot I hadn't turned on Zygisk in Magisk, so I went and did that, and rebooted when asked. Now I can't boot in. I get to the lockscreen, and when I try to unlock, it just says "Phone is starting". Forever. Waited 30 minutes, nothing. Rebooted, same thing. Waited some more. Rebooted again. All the same. Can't believe I'm considering going back to the garbage stock rom at this point.
 
Had the same issue with everything constantly breaking, and needing to force stop google play services every couple of hours, after I dirty flashed from 19.1 to 20. Was tired of it, and finally had a day off to deal with it, so I backed up up all of my stuff with Swift Backup, wiped data, setup the rom again, restored all of my backups(took like 4 hours), and everything seemed fine. Forgot I hadn't turned on Zygisk in Magisk, so I went and did that, and rebooted when asked. Now I can't boot in. I get to the lockscreen, and when I try to unlock, it just says "Phone is starting". Forever. Waited 30 minutes, nothing. Rebooted, same thing. Waited some more. Rebooted again. All the same. Can't believe I'm considering going back to the garbage stock rom at this point.
No idea what you did. Magisk with zygisk enabled is working fine for me.
 
  • Like
Reactions: osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,309
34,658
Halifax
GT-i9250
Google Nexus 4
I experimented the last couple of days running without USNF, Shamiko or Zygisk enabled to see if it would make any difference, but still getting video hangs and RCS messages getting stuck until I Force close the app or Play Services. Next I'll try different GApps just to be certain of that variable.
 
Last edited:
  • Like
Reactions: Eric_Lev

Zhono

Senior Member
Dec 6, 2012
158
44
Gave in and completely reverted to stock. Went through the whole process of updating to latest stock OTA, unlocking bootloader, flashed fresh LOS 20, recommended gapps, magisk, you get the idea. Setup all my apps and accounts again, watch, headphones, blah blah blah. Finally go to sleep, wake up a few hours later, and just like I thought, same problems as before, need to force stop Google play services to fix a bunch of stuff. All for nothing, right back where I started. Maybe I'll try using tasker or something to automatically kill and restart Google Play services every hour. Or dirty flash back to 19.1, or a different ROM, before I give up and go back to stock.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    Some news regarding this longstanding problem and the fix described below:

    New suggestion from LuK1337 in the issue thread here
    Code:
    adb shell settings put global cached_apps_freezer disabled
    or I guess the equivalent setting in developer options. Remember to reboot after changing it.
    I'm trying it myself now, will update in a day or two with results...

    Edit: 12h in... I'm 99% sure this has solved the issue. Have not experienced Firefox crash message, Firefox input failure, media playback failure or games failing to load, all of which happened pretty reliably previously.

    According to the LOS Gerrit, this change has been merged into android_kernel_oneplus_sm8350. Also, the changes to move the OP9Pro to the OOS 13 firmware and binaries (in the kernel, android_device_oneplus_lemonadep, and android_device_oneplus_sm8350-common) are in the process of being incorporated (some have already been merged, others are still in code review). That should mean that when OP9Pro releases resume, it'll be with the requirement to finally update the necessary firmware to LE2125_11.F.20. And the peasants... rejoiced. 😁
    5
    hey @LuK1337
    I think that after the merging with firmware a13 it has been broken again that the device wakes up only from off with the alarm.
    I'm with limonade, but in the first versions I installed (19.1 if I remember correctly) I had the same problems and in a short time you solved it.
    When you have some time if you take a look at it I would appreciate it, thanks!
    5
    Okay, for those of you who'd like to switch back to LineageOS 19.1 until these problems are resolved (or just want to stay on 19.1 for whatever reason), I built an unofficial release right after the February ASB patches were merged. Links are provided below for the zip, sha256, and recovery image files (you'll probably have to flash the recovery image first since the LOS 20 recovery would consider it a downgrade and refuse to flash the zip; either that, or use TWRP). This is pure, unfiltered LineageOS, with absolutely no changes made by me. You should probably turn off system updates after installing so that you aren't pestered to upgrade to LOS 20, which would defeat the whole purpose. 😁

    This will be the only build I make available until the next ASB patches are available in March, or if there's a fix for any serious issues that are merged into the 19.1 tree in the interim, as the LOS team usually doesn't do anything other than minor fixes to previous releases (their major work is concentrated on the current release). Also note that I'm not providing any support, I'm just making 19.1 available to those who want it. 😉

    ROM: lineage-19.1-20230218-UNOFFICIAL-lemonadep.zip
    Checksum: lineage-19.1-20230218-UNOFFICIAL-lemonadep.zip.sha256sum
    Recovery: lineage-19.1-recovery-lemonadep.img

    Let me know if the links aren't working (they're on MediaFire for now, which I haven't used in a dog's age) and I'll try to fix them.
    4
    According to the recent commits and the update to the firmware guide, when upgrading from a "old" install of LOS 20, should the update be done manually to apply the firmware update or can it be done via the LOS updater (and potentially restart) without bricking?
    OTA, unless you want to potentially hurt yourself for no reason to whatsoever.
    4
    I just would like to do clean flash this time around but I never came up with a good solution to backups&restore apps that would be fast and painless. Any tips there? What's the current go to?

    Swift Backup. Backs up and restores apps flawlessly (Titanium Backup, the community's previous "go to," hasn't been updated in ages, and doesn't handle modern app configurations like split APKs properly). It also backs up text messages, call logs, and WiFi settings, scheduled backups, cloud storage, everything the average user needs. Spend the few dollars and go with the paid version, it's well worth the investment.
  • 12
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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 :
    GPL compliance :
    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:
    8
    Some news regarding this longstanding problem and the fix described below:

    New suggestion from LuK1337 in the issue thread here
    Code:
    adb shell settings put global cached_apps_freezer disabled
    or I guess the equivalent setting in developer options. Remember to reboot after changing it.
    I'm trying it myself now, will update in a day or two with results...

    Edit: 12h in... I'm 99% sure this has solved the issue. Have not experienced Firefox crash message, Firefox input failure, media playback failure or games failing to load, all of which happened pretty reliably previously.

    According to the LOS Gerrit, this change has been merged into android_kernel_oneplus_sm8350. Also, the changes to move the OP9Pro to the OOS 13 firmware and binaries (in the kernel, android_device_oneplus_lemonadep, and android_device_oneplus_sm8350-common) are in the process of being incorporated (some have already been merged, others are still in code review). That should mean that when OP9Pro releases resume, it'll be with the requirement to finally update the necessary firmware to LE2125_11.F.20. And the peasants... rejoiced. 😁
    8
    Thank you for your work so far, and will there be any support plans in the future😉
    Depends on the outcome of this comment - https://gitlab.com/LineageOS/issues/android/-/issues/5384#note_1284136018
    5
    Thanks, yep been reading up on MSM tool. I used to be a big fan of TWRP when we were running with LG V20 and earlier days but seems like there are still various problems and gotchas with it for OP9Pro. Magisk doesn't play nice, or it does if you hold your mouth this way while you flash, etc.

    So we've stuck with Lineage recovery on this device. I do have good memories of TWRP though and hope it fully gets there someday for OnePlus 9Pro.

    Thanks for responses - appreciate it!
    Just for future reference, Android 12-13 TWRP is pretty much feature complete for OP9x: https://forum.xda-developers.com/t/...twrp-with-a12-a13-encryption-support.4523857/

    Will be made official soon. @der_akinator has done an amazing job, and in a remarkably short amount of time!
    5
    Okay, for those of you who'd like to switch back to LineageOS 19.1 until these problems are resolved (or just want to stay on 19.1 for whatever reason), I built an unofficial release right after the February ASB patches were merged. Links are provided below for the zip, sha256, and recovery image files (you'll probably have to flash the recovery image first since the LOS 20 recovery would consider it a downgrade and refuse to flash the zip; either that, or use TWRP). This is pure, unfiltered LineageOS, with absolutely no changes made by me. You should probably turn off system updates after installing so that you aren't pestered to upgrade to LOS 20, which would defeat the whole purpose. 😁

    This will be the only build I make available until the next ASB patches are available in March, or if there's a fix for any serious issues that are merged into the 19.1 tree in the interim, as the LOS team usually doesn't do anything other than minor fixes to previous releases (their major work is concentrated on the current release). Also note that I'm not providing any support, I'm just making 19.1 available to those who want it. 😉

    ROM: lineage-19.1-20230218-UNOFFICIAL-lemonadep.zip
    Checksum: lineage-19.1-20230218-UNOFFICIAL-lemonadep.zip.sha256sum
    Recovery: lineage-19.1-recovery-lemonadep.img

    Let me know if the links aren't working (they're on MediaFire for now, which I haven't used in a dog's age) and I'll try to fix them.