I knew it!For anyone wondering why the TWRP recovery is overwritten by Lineage's recovery here's how to avoid that:
During the first boot of Lineage make sure to leave unchecked this option:
View attachment 5499593
If you check it Lineage will overwrite TWRP with its own recovery at every boot.
If you checked this option at boot, follow this video (obviously you have to reflash TWRP after disabling this option):
Yeah, I Really feel you hahaI knew it!
I had a small hunch that, that option was causing those issues.
Though ngl, Custom Lineage OS ROMs don't get updates in the OS, so it would be a bit odd to allow it to update the recovery with the OS anyways..
Apparently I don't pay attention enough, and yet will still end up at the same conclusion for the wrong reasons. xD
Just missing the right blobs. LolSo I can officially say that the v5stable version is not bugged
I had a problem with audio for some reason and it took a reboot to fix. Maybe its because of how i installed it but idk.So I can officially say that the v5stable version is not bugged
Well if you still have this problem send a logcat when you experience itI had a problem with audio for some reason and it took a reboot to fix. Maybe its because of how i installed it but idk.
Unfortunately I think there isn't a way to enable it since this Android variant is Go and not full.Is there any way to make "display over other apps" service available?
okey then, thanks for the informationUnfortunately I think there isn't a way to enable it since this Android variant is Go and not full.
YepLet me guess, disabling navbar? Also, any tips for better performance? I want to switch from slim 7 for better UI.
Any news on LOS 19?
will there be any ltedx builds?Yep
The performance is what it is, you can't achieve much more unfortunately with Android 11 on a grand prime : (
Regarding Android 12, at the moment I'm still putting the final touches on the (probably last?) v6 18.1 release. I'll update you all if I can do something interesting.
Oh right! Thanks for reminding me, I almost forgot about this variant. It looks like it is similar to the gprimeltexx variant so it should be okay to build for it.
Then you need to find out why. It can be a kernel issue, or maybe it can be on the lineageos side. Experiment with the config filesdoesn't let me, i can use adb while in recovery and on my other phones but it wont let me logcat during boot
i would test it but my grand prime's touch diedlos - Google Drive
drive.google.commaybe it will work for yall, my phone is a piece of crap.
- gprimeltexx (SM-G530FZ) (since V1beta)
- fortuna3g (SM-G530H) [XXU] (since V3stable)
- fortunave3g (SM-G530H) [XCU] (since V3stable)
- fortunalteub (SM-G530M) (since V3stable)
- gprimelte (gprimelte, gprimeltecan, gprimeltetmo, gprimeltemtr, gprimeltevl) (since V4stable)
- fortuna3gdtv (since V4stable)
- gprimeltetfnvzw (S920L) (since V5stable)
- gprimelteusc (SM-G530R4) (since V5stable)
- fortunaltedx (SM-G530F) (since V6stable)
Build date/Release version you downloaded/installed (the name of the .zip file):
Device variant you are using:
Gapps version (if using):
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: