[12.1][OFFICIAL] LineageOS 19 for Oneplus 5 & 5T

[zagzag99]

Not experiencing any issues with Magisk installation on latest ROM.
Did you try to wipe system, cache, dalvik and flash rom+gapps+Magisk manually?

 

[indiandragon]

Not experiencing any issues with Magisk installation on latest ROM.
Did you try to wipe system, cache, dalvik and flash rom+gapps+Magisk manually?

Thanks for confirming.

I had no issues since I upgraded LineageOS from 18.1, Magisk install by patching boot.img worked fine too. I repeated the same without issues for next few updates of 19.1.

Only since the latest update of LineageOS 19.1, Magisk doesn't seem to get installed; Logs show no error during installation.

 

[LuisCarlosHK]

Thanks for confirming.

I had no issues since I upgraded LineageOS from 18.1, Magisk install by patching boot.img worked fine too. I repeated the same without issues for next few updates of 19.1.

Only since the latest update of LineageOS 19.1, Magisk doesn't seem to get installed; Logs show no error during installation.

During installation, it would said magisk was not installed. Just flash magisk again or flash lygisk to replace magisk

 

[indiandragon]

During installation, it would said magisk was not installed. Just flash magisk again or flash lygisk to replace magisk

My bad, Installation worked fine this time. Thank you all.

 

[Eric_Lev]

FYI:

Changelog 27 - Thriving Thirteen, Amazing Aperture, Careful Commonization

X_X

www.lineageos.org

 

[morphinapg]

I've been having a lot of random freezes. It seems to happen no matter what app I'm running, and happens up to several times per day. The whole phone will just lock up for several seconds, and after it resumes, it acts like it thought the app itself was crashing and gives you the option to force close the app, but since it happens on every app, it doesn't seem to be related to any app. So I was wondering if this was an OS thing, or possibly a MindtheGapps thing. I have been having this issue ever since I installed LOS18, and I was hoping upgrading to 19 would solve it, but the same issues are happening. I was able to grab a logcat shortly after it happened, and this appears to be the relevant section, since it shows how it was assuming the facebook app was not responding:

Spoiler

07-08 16:45:13.075  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604736
07-08 16:45:13.077  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684926
07-08 16:45:13.078  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
07-08 16:45:13.078  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
07-08 16:45:13.078  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684638
07-08 16:45:13.079  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604922
07-08 16:45:13.080  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604736
07-08 16:45:13.082  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684926
07-08 16:45:13.082  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
07-08 16:45:13.083  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
07-08 16:45:13.083  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684638
07-08 16:45:13.083  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604922
07-08 16:45:13.114     0     0 W [20220708_16:45:13.114251]@7 healthd: battery l=95 v=4040 t=32.9 h=2 st=3 c=644000 fc=2878000 cc=0 chg=
07-08 16:45:13.172  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604736
07-08 16:45:13.174  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684926
07-08 16:45:13.175  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
07-08 16:45:13.178  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
07-08 16:45:13.180  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684638
07-08 16:45:13.182  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604922
07-08 16:45:14.411     0     0 E [20220708_16:45:14.410288]@4 synaptics,s3320: all finger up
07-08 16:45:18.905  1486  2212 I WindowManager: ANR in Window{58f11e7 u0 com.facebook.katana/com.facebook.katana.activity.FbMainTabActivity}. Reason:58f11e7 com.facebook.katana/com.facebook.katana.activity.FbMainTabActivity (server) is not responding. Waited 5001ms for MotionEvent(deviceId=2, eventTime=245003958749000, source=0x00001002, displayId=0, action=MOVE, actionButton=0x00000000, flags=0x00000000, metaState=0x00000000, buttonState=0x00000000, classification=NONE, edgeFlags=0x00000000, xPrecision=1.0, yPrecision=1.0, xCursorPosition=nan, yCursorPosition=nan, pointers=[0: (800.0, 1242.0)]), policyFlags=0x62000000
07-08 16:45:18.943  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042980; UID 10107; state: DISABLED
07-08 16:45:18.944  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 181136395; UID 10107; state: DISABLED
07-08 16:45:18.944  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042936; UID 10107; state: DISABLED
07-08 16:45:18.944  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 184838306; UID 10107; state: DISABLED
07-08 16:45:18.945  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 185004937; UID 10107; state: DISABLED
07-08 16:45:18.945  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042980; UID 10199; state: DISABLED
07-08 16:45:18.945  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 181136395; UID 10199; state: DISABLED
07-08 16:45:18.946  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042936; UID 10199; state: DISABLED
07-08 16:45:18.946  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 184838306; UID 10199; state: DISABLED
07-08 16:45:18.946  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 185004937; UID 10199; state: DISABLED
07-08 16:45:18.953  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042980; UID 10193; state: DISABLED
07-08 16:45:18.953  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 181136395; UID 10193; state: DISABLED
07-08 16:45:18.953  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042936; UID 10193; state: DISABLED
07-08 16:45:18.953  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 184838306; UID 10193; state: DISABLED
07-08 16:45:18.954  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 185004937; UID 10193; state: DISABLED
07-08 16:45:21.902  1486  4518 W ActivityManager: Missing app error report, app = com.facebook.katana crashing = false notResponding = true
07-08 16:45:21.905  1486 21220 I ActivityManager: dumpStackTraces pids={2747=true, 2899=true, 3340=true, 3366=true, 3637=true, 3639=true, 4039=true, 4076=true, 4989=true, 9573=true, 10461=true, 10486=true, 10582=true, 10686=true, 10852=true, 11293=true, 11524=true, 12229=true, 12264=true, 12279=true, 13724=true, 13863=true, 13986=true, 14098=true, 14752=true, 15057=true, 16365=true, 16595=true, 16600=true, 17252=true, 18902=true, 19018=true, 19160=true, 19222=true, 19462=true, 20948=true, 21038=true, 21077=true, 23830=true, 24484=true, 25610=true, 26989=true, 30766=true, 32624=true} nativepids=[582, 609, 615, 766, 767, 853, 894, 933, 937, 938, 940, 979, 1034, 4989]

Is this an issue anybody else is having? I tried searching the thread but didn't see anything. Is it possible that there's something wrong with my phone itself?

Another, possibly related, possibly unrelated issue will happen sometimes, the home button / fingerprint scanner will become completely unresponsive for a few seconds, but everything else about the phone works perfectly normal.

Here's the full logcat in case additional context is needed:

logcat.txt

drive.google.com

My LOS19 was a dirty flash, but I had to do a full wipe when I installed 18.1, due to an issue with encryption being lost, and still had the issue there.

I just wanted to make an update now that I have finally done a wipe and a clean flash just a few days ago using the newest build, and my phone has been working pretty flawlessly since then.

I tend not to do updates very often, so I actually hadn't updated since this original post. I don't know whether it's just a newer version of LOS that solved it, or the clean flash, but I'm happy with the result, especially since I was having similar (but less severe) issues in LOS18 as well.

The only things I've noticed is that the thumbprint reader still sometimes doesn't work if the screen has been off for a while, but if I turn the screen on first, it works just fine, so no big deal, just an added button press to get in. And I also have notifications for seedvault failing, even though I never set it up, and even switched it to google for backup. Would be nice to be able to disable that if I don't want it, or at least disable the notifications. Otherwise my experience has been perfect.

FYI:

Changelog 27 - Thriving Thirteen, Amazing Aperture, Careful Commonization

X_X

www.lineageos.org

Of course now that I finally update LOS20 is coming soon lol. No big deal though I usually wait a while before upgrading to a new version anyway.

 

[LuisCarlosHK]

I flashed LOS20 with MindTheGapps-13.0.0-arm64-20221025_100653.zip but google play is not working.
Anyone know how to solve?

 

[js-xda]

I flashed LOS20 with MindTheGapps-13.0.0-arm64-20221025_100653.zip but google play is not working.
Anyone know how to solve?

Wrong thread - try in the new LOS 20 thread.

 

[morphinapg]

I just wanted to make an update now that I have finally done a wipe and a clean flash just a few days ago using the newest build, and my phone has been working pretty flawlessly since then.

Well... spoke too soon. I am once again having the freezes that I used to. Anybody have any idea what could be causing this? The phone was working flawlessly for the first couple days after the clean flash, and then slowly has started to freeze up again randomly. Doesn't seem to matter what app I'm using. I feel like this may have happened last time too, where there was no issue for the first couple days and then it started up again, and got worse over time.

 

[krazed0451]

Updated to LOS19.1 26 December build and was working fine until this week when it now mostly won't recognise the fingerprint hardware. I can occasionally restore functionality via reboot but it's not a reliable fix. Given the next update is side loading LOS20, I was hoping there may be a know fix... Otherwise I'll proceed with the upgrade when I have time available.

 

[hioannand]

你好，额我也不知道对谁说，但我想求助:我想自己做一个rom，但是我不知道怎么提取内核驱动，安卓的内核驱动是像电脑windows那样的吗？还有怎么打包新的rom？

 

[hioannand]

我自己的手机是一加5t,需要root吗？是中国版的，目前使用H2OS 10.0.3