yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] znbaboy:
that is referring to device integrity which can be spoofed with root and magisk modules. I am talking about basic integrity which all devices (regardless of root and bootloader status) should pass (if i understand correctly)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] khusika:
That's included, basic integrity = SafetyNet.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] znbaboy:
...no. safetynet is deprecated. basic integrity and device integrity are two different things.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] khusika:
Sir, I understand that as I stated above, Play's basic integrity tests are almost like Safetynet tests (although they cover a lot more). I'm just responding to your statement above, and as I mentioned above that LineageOS will not pay attention to Play Integrity checks even if it's basic checks.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Samppaz:
I was too the same problem.

Then i download playintegrityfix and install it with magisk and both device integrity and basic integrity pass and safetynet too.

GitHub - chiteroman/PlayIntegrityFix: Fix Play Integrity (and SafetyNet) verdicts.

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
I have sometimes problem with dt2w,it's really random.Is anyone experienced this.I noticed that from the first build,so i clean flashed yesterday build and the problem still exists.That hapened a few minutes ago,so it's a first wake up from last night.thanks
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Mine has seemed to work pretty consistently, but I did have one random instance where it didn't want to work right away. Haven't had any further issues, though.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
On stock rom it's working perfectly fine,today i have taped on the screen multiple times and nothing happened.funy thing is that screen woke up itself after couple of seconds.Nevermind because i'm on Oxygen at the moment,but i'll be back for sure.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] arnecc:
Thanks for your effort, almost everything seems great so far. Only during calls the earpiece seems a bit too quiet and definitely quieter than before to me. Not when using speaker or some external headphones, only the integrated earpiece.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] znbaboy:
No. You likely were already passing basic integrity, but not device integrity. "Play integrity fix" only fixes device integrity

I found the reason (90% sure) why basic integrity isn't working in LOS21. It's because key attestation (TEE) is broken on 21 (at least on my OP7Pro) which prevents it from getting basic integrity.

You can check yours using this GitHub project: https://github.com/vvb2060/KeyAttestation/releases
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] G23 Mr Gimp:
First of all, thanks @LuK1337 for keeping the OnePlus 7 Pro maintained, it's greatly appreciated.

I was wondering if anyone else was having issues with screen rotation ocassionally glitching and taking a moment to redraw?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
Maybe a stupid question,do we need to have OOS 12 on both slots prior to flash Lineage.What do you suggest guys and thanks.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
This is a problem that i was talking about,on Lineage 20 i didn't noticed that.Sorry for the video quality.i just waited a moment to capture this.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] colaigor:
I will be switching from pe to los soon. Is it worth getting this version over los20? I dont need any of the features of android 14, i need stability.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
I actually did have this happen once yesterday. It's very rare in my case, but it might be worth grabbing a logcat if it happens again.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Yes, this one is just as stable. Also, 20 won't be getting updates anymore, so 21 is the better way to go.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
Oh man,you save my day because i'm not the only one.It's really weird because it happens randomly.Tried now multiple times and it's working like a swiss clock.I'll try to grab a logcat although i've never done that.thank you once again
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] kool018:
How has 21 been compared to 20 for those who upgraded? Seems like the most common issue is DT2W, but it's hard to gage how wide-spread that actually is.

I figured I'd let it bake a few weeks since I value the current stability of 20, but it's been over month and 21 is tempting me now!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Upgrading to 21 actually fixed some minor issues for me. Namely, Nova Launcher seems to work better on 21 than it did on 20.

I still have very rare occasions where DT2W doesn't work on the first try, but it works 99.9% of the time. Also, I can't get Google's "At a Glance" widget to open relevant apps, like the Calendar, but I'm not sure if that's just more of a Google problem than an OS problem.

Otherwise, stability is every bit as good as 20. I'd say go for it!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] scubajeff:
Is the notification led supported in this build?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] LuK1337:
The notification led that this phone doesn't even have?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] G23 Mr Gimp:
Just a quick one to see if anyone else is having the issue I mentioned on the 8th with rotation lagging (both auto rotate and manual) as it's becoming a little annoying now and would love to resolve it if it is indeed a problem specific to me, but don't want to go to the effort of reflashing and restoring data if it is a known issue.

I hope you're all having a great weekend!

Andy
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
I haven't noticed anything like that. Is it only with certain apps, or does it happen with any app?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] G23 Mr Gimp:
Thanks for the reply, it's much appreciated.

It happens when just using the phone in general, but seems worse when using YouTube or Discord. If you're not experiencing it I might bite the bullet and do a clean install as I'm currently running after upgrading from LOS 20.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
That seems odd (and annoying.) Yeah I mostly only rotate my phone for video, including YouTube, and it never does anything like what you describe. I just tried it in Discord and it worked without any issues there, too. No idea what might cause that. Hopefully a clean install does the trick if you go that route.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] G23 Mr Gimp:
Can confirm a clean install seems to have sorted it. It's now quicker than Usain Bolt with the ****s!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Abuu darda:
Just installed yesterday. Issues that I found till now.

Charging is super SLOW. Just measured it. and it's only 300 mA.

Fingerprint logo bit out of place and slow.

There was some screen stuttering or frame drop I guess. Fix: toggling off Display > Smooth display did the trick.

Whenever any app uses location, It was showing in the status bar. Fix: turning off Status bar location indicator from developer settings. fixed it.

Putting the clock in the center of the status bar makes an empty space at the left side. Notification icons start after the empty space.

Camera is terrible
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] EvilAVP9000:
I have a problem with recent apps button. It's not working.

Pixel Launcher always crashing and unusable.

Clean install after full wipe, latest MindTheGapps
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] almahix:
I've had that problem too. I use Apex as my launcher and I figured it was a bug in that. Perhaps not.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] almahix:
Anyone seen any new builds lately? The latest appears to be March 18.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
Builds are temporary on hold
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] MJPollard:
More specifically, Android 14 QPR2 broke a bunch of things, so the LOS team put everything on hold while they put the pieces back together. The individual maintainers then had to verify that the changes worked before recertifying the devices. There's a commit in the Gerrit waiting to be merged that reinstates (most of) the builds, so it shouldn't be much longer now.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Something's definitely not right. I'm unable to reproduce any of these issues (except location indicator in the status bar, but that's a feature, not a bug.) If you came from a different ROM, I wonder if there's some data that wasn't properly wiped that might be causing issues. Either that, or a problematic mod. Hard to know for sure, though.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] almahix:
Thank you for the explanation. It is appreciated
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] kool018:
Thank you! I just came to ask the same thing.

To clarify, is the March 18th build based on QPR2, or was that just the last build before the devs all got pulled away?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] kool018:
I had the clock issue on 20. The workaround I used was ticking the "don't show clock" option on Nova Launcher. If the gap is there, going to the homescreen fixes it until I lock my screen again.

It looks like the newest version of Nova removed that option, but I can still see it in settings search and still have it enabled. I might put a Nova bug report in for that... I'm on beta. Not sure if the new version has made it's way to GA
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] MJPollard:
That last thing. The QPR2 updates (part of the March 2024 ASB patches) started being applied on March 20th, so I'm almost certain that's when the automatic builds were put on hold (or somewhere around that time). The open Gerrit commit for the hudson package got another couple of updates today, so things are definitely moving along.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Pickrenhine:
Hi all,

before switching from stock, I would like to know what to expect.

Most importantly: how is the camera quality compared to stock? Good (excellent) quality with all 3 cameras is very important to me, as well as the effects (portrait) and other modes (panorama, night). Are these as good as the original?

Other than this, are there any quirks or bugs, or lacking quality compared to stock? Thanks in advance!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Steve Geemaggio:
My experience has generally been good. The ROM runs smoothly if installed as per instruction. There are minor glitches here and there with Android 14 being relatively new to this device, but things get fixed pretty quick and nothing has affected day to day usage. The default camera in my opinion isn't as good as stock sadly. I am currently using OpenCamera with Camera2 API enabled in settings which is close to, if not, stock Camera quality I believe. Hope that helps.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Pickrenhine:
Thanks for the answer! I've been using OpenCamera before, many years ago, on a different device with Cyanogenmod and I remember it wasn't as good as stock, but better than the default CM camera. I hope these things have been developed since then.

It would be nice to see some comparison pictures but I don't expect anyone had made some.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
**edit**

I was still on Magisk 26.4. Updating to v27.0 seems to have fixed it. Also, the issues I was having with Magisk 27 in the past are no longer a problem on the newest LineageOS build.

Builds are back. I updated this morning, and so far so good, except I can't get Zygisk to work in Magisk. I might try a full uninstall/reinstall of Magisk later, but just FYI for anyone who needs it to pass device integrity, etc.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
Updated to latest version,running like a swiss clock.Double to wake is working fine as of now.i will test further.thanks is a small word for developers.cheers
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] zyguo:
Anyone tried

lineage-21.0-20240415-nightly-guacamole-signed.zip

or newer?

Is it QPR2?

Safe to update?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Yes, yes, and yes. 🙂
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] zyguo:
Seams have to reinstall gapps and magisk after 20240415. That's what I'm doing now.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] znbaboy:
i had this as well, LSPosed was the issue. having it enabled causes Zygisk to not enable.

I tried doing a clean install of Magisk and all my modules and everything enabled fine, but LSPosed's UI/app would not launch (although shows it running in notifications).

I tried the most starred fork (https://github.com/pumPCin/LSPosed), but it has the same issue.

This was on my Pixel 7 Pro after updating to the latest April 16 LOS build.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] zyguo:
This LSPosed fork bring me back to normal after qpr2 update. Zygisk enabled.

GitHub - mywalkb/LSPosed_mod: My changes to LSPosed

My changes to LSPosed. Contribute to mywalkb/LSPosed_mod development by creating an account on GitHub.

github.com
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] znbaboy:
worked perfectly. thank you
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Nmh85:
Hi all,

I updated to the latest Lineage version and have Magisk 27002 running. I had the issue mentioned above where Zygisk was not running and needed the LSPosed mod installed. Everything is shown to be running now but I have found the apps that are enabled in Hide My Applist no longer open, they just get stuck on their loading screen. If I disable the HMA policy for that app, they open. Has anyone else got the same issue? Thank you
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] droidman1992:
Top notch work @LuK1337 as usual, the latest build based on QPR2 is running perfectly with one exception, charging control appears broken again and charges to 100% regardless of the limit set. This is a new clean install from scratch (OnePlus MSM tool back to factory and complete reflash) and charging control was working properly on the 20240318 build before QPR2, so I'm not sure what the problem is and would appreciate if you could look into it. I also have the bug reported on the Lineage OS bug tracker.

EDIT: I can reproduce the issue on two guacamole phones running the same build of Lineage OS 21 as my sister also has this issue with charging to 100%, therefore, you should have no problem reproducing the issue.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] zyguo:
I use Acc for charging control. It's not that simple vs the built-in one but once it's stable, the correct options configed, it can control charging level too.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] kool018:
I upgraded from LineageOS 20 to the March build, then less than 24 hours later the April 15th build came out and I upgraded to that.

I've had a very stable experience, but one big issue for me. It seems my Galaxy Watch 5 will not stay paired anymore. At first I followed a set of instructions online to re-pair without factory resetting and that worked, but the next morning, it was missing from my Bluetooth connections again.

Any ideas?

Also, I have the same charge control issues droidman
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Winter7191:
I have exactly the same problem with my Galaxy watch 4, going from LOS 21 202402xx (don't know the exact version right now, but I can look it up later) to 20240415.

I tried this already:

Resetting the watch, removing the watch from the saved bluetooth devices list, removed all Galaxy apps+plugins from my phone, reinstalled everything and set it up as a new watch. Then it works, but only for a few hours. After 8-10 hours, I can't connect to the watch via Bluetooth anymore, only with WiFi remote connection (which causes extreme battery drain on the watch).

In the Bluetooth device list on the phone, the watch always bounces between "saved devices" and "other devices".

The charge control doesn't work either, it charges past the limit to 100%.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
I had that issue with Magisk 27000 on the pre-QPR2 builds (any LineageOS build before April) so I ended up downgrading Magisk to 26.4. With the newest LineageOS builds, Magisk 26.4 wouldn't let me enable Zygisk, so I upgraded to 27.0 (27000) and it's working perfectly for me. None of my apps hang on the loading screen, and Zygisk works.

(Note: I'm on the stable channel in Magisk, and I don't use LSPosed.)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Nmh85:
Hi, do your banking apps work without using HMA? I have found that I need Magisk and HMA for them to work, they somehow detect Magisk when not hidden by HMA.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Mine do, yes. The only Magisk module that I'm using is Play Integrity Fix, and I have my banking apps added to the DenyList in Magisk. Also, the Magisk app itself is hidden.

I'm also in the U.S., so I'm not sure if that makes a difference. It could just be that my specific US-based banking apps work just fine without any additional modding, hence why I've never bothered with LSPosed.

Hopefully you can get yours working. Sounds like the issue might be with LSPosed or HMA, and maybe the developers just need to update them to work with the QPR2 changes.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aeonixx:
I absolutely can't manage to root Lineage 21 on my OP7Pro. I'm befuddled. I've tried everything I could think of with Magisk.

My OnePlus 7 Pro is currently running the latest Lineage 21 Nightly build (April 29th). The Magisk app is installed and does not have its root functionality. The OS is great, no complaints. I'm using this phone until the wheels fall off, and Lineage has been driving it for quite a while now. Well, the charge limiter broke in april, but I'm trying to work around it by rooting and using a battery charge limiter app.

What I've tried to root with Magisk:

Sideload: Reboot to recovery, "apply update", "apply from ADB", adb sideload the magisk.zip/.apk (extension shouldn't matter but I tried both). No root on reboot.

Downloaded boot.img from official Lineage download page for OP7Pro, patched it in Magisk app on the phone, rebooted to bootloader (old fastboot), run "fastboot flash boot magisk_patched-27000_Ec3ZN.img". This said it was sending it to "boot_a". Also tried "fastboot flash boot_a magisk_patched-27000_Ec3ZN.img" immediately also flashing it to boot_b. Didn't give me root.

Tried booting from magisk patched boot.img for temporary root so that I couldn't perma-root from inside the Magisk app. Didn't work. Command used: "fastboot boot magisk_patched-27000_Ec3ZN.img" (in bootloader, so not fastbootd, fastbootd doesn't actually support booting from an image)

Tried flashing boot in fastbootD, which I think is a Lineage 21 thing: "fastboot flash boot magisk_patched-27000_Ec3ZN.img" -- didn't work either.

Tried booting a TWRP image in bootloader ("fastboot boot twrp.img") to flash from there. It just goes to a different "fastboot" splash image, and still shows up in fastboot devices. TWRP no worky work.

When doing the sideload now, it says that a "Magisk patched boot image" is detected. But I'm not getting root functionality, and Magisk app says not installed.

I took the liberty of flashing the non-patched boot image, then sideloaded the magisk apk-zip, it recognized the boot image as stock and patched it.

But I still don't get root functionality.

I'm absolutely lost. Am I missing something? Is Lineage 21 (or at least the version out for OnePlus 7 Pro) incompatible with Magisk at the moment? Am I stupid? (Probably! But I've definitely learned a lot about the different approaches to rooting today, so perhaps I'm a little less stupid than before.)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Definitely scratching my head on this one. ADB sideload should be all you'd need to do. Root is working just fine for me, with Magisk 27.0.

Do you have the "Uninstall Magisk" button in the Magisk app? I'd probably start there, let it do a complete uninstall, then try ADB Sideload with the Magisk.zip again. No idea if that'll help, but could be worth a shot?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] yubisoft:
Confirming that I have the same exact issue.

I was about to post this on the LineageOS/MicroG thread but I see that the issue is actually on this side.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] droidman1992:
Yes, this has been an ongoing issue since the beginning of 21. I reported the bug about two months back, maybe they will get to it before Android 15 comes out. It's a quality of life feature that is really useful and greatly missed.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] yubisoft:
After doing research it seems like the consensus is root + AccA (get it on F-Droid) which is not ideal. Partly because of root, partly because I've seen that thing increase battery drain. To anyone searching for solutions, this seems to be the workaround. Maybe my Android 15 it'll be fixed again, then we can enjoy a native battery charge limiter. Not sure why this is the one thing that keeps breaking, but it is what it is, and luckily that old app still works fine.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
After reading all of these reports about charging control being broken, I thought I'd try it out and see what happens (I haven't been using it.) Weirdly, it works perfectly fine for me. I set the limit to 80%, left it plugged in, and it never charged beyond 80%. So, why is mine working when there are so many reports of it being broken?

Best I can guess is that I keep my mods at a bare minimum. The only Magisk module that I use is Play Integrity Fix. That's it. Nothing else.

For those who are having issues, are you running any modules that could somehow be interfering with charging control? I'm kind of wondering if it's not actually a problem with LineageOS itself, but some other outside factor that can affect things at a system level.

Or, maybe there's some other reason that mine works that I'm unaware of.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] yubisoft:
The most exotic thing I have added to my phone is MicroG, no Google. That's pretty much it.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] droidman1992:
Thanks for your input, however, I'm also in the same situation as you with only Magisk and playintegrityfix by osm0sis, nothing else and it's broken for me, therefore, it must be something in Lineage 21.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Huh, well that all disproves that theory. Well I'm stumped, then. Guess I'm just lucky?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] soundsticks:
I have a problem with dual sim there is no setting for second sim
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] ctag:
How do you have your phone set up? A comment on this thread claims you need eSIM functioning for dual SIM to work.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] ctag:
I've seen some discussion online about LOS 21 supporting MicroG now. Does anyone have experience installing it with this ROM? Some threads claim it needs to be loaded as a system app, but this guide makes it seem like just installing the apps will work..
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] yubisoft:
As of May 25th LOS-MicroG release, charge limiting works again. 👏

Edit (May 27): Aaaaaaand it worked only that one time. Still broken.