yashsingh1/xdaforums huggingface dataset:
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] TAGTRAUM:
Coming from stock, v70-74-75 7T Pro Mclaren, so far so good, just one thing about kernel - maybe i'm crazy and it's not connected, but on full stock sound on same type-c adapter with same earphones and audio player was a bit clearer and/or deeper

Regarding the flash process and battery life/smoothness - absolutely brilliant and step up from stock, thanks for your work :cyclops:
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Don't notice much difference in BT.

I build from OP source with no changes regarding sound.

Sent from my blu_spark'd OnePlus
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] abalam:
My WiFi works. No problem with flashing and so on, running it on 10.0.7. I also noticed that we don't have to install a magisk behind the kernel flash. This is a must have.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] L2_n19h7m4r3:
Is it possible to add the USB HID patch to the kernel?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Don't know what you're talking about.

Sent from my blu_spark'd OnePlus
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] L2_n19h7m4r3:
More info here: https://patchwork.kernel.org/patch/10299667/

Patch would allow Rucky to work. https://github.com/mayankmetha/Rucky
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
I think I know what you're referring to, KB HID emulation on android.

That is just a polling patch. Other stuff needs to be patched around kernel for what you're talking about, add hacky ramdisk files, etc.

It's a no go for me, already messed with it on the past and it didn't go well. But I can add that polling patch, no prob.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] L2_n19h7m4r3:
That would be wonderful. Also loving this kernel, many thanks!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] pxrave:
What's the recommendation app to install the kernel?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] beaverhead:
i use ekm.

Verstuurd vanaf mijn OnePlus 7T Pro met Tapatalk
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
FKM has nice support :)

Sent from my blu_spark'd OnePlus
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] pxrave:
That's for your fast replay. I will use the app. Franco have done very good things too.

I hope twrp support for Android 10 is done soon. Because seems very complicated to hack the new devices os. I love you decided to support our op7 series. Thank you for invest your time in this project.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] DanDroidOS:
[MENTION=3873953]eng.stk[/MENTION] just wanted to let you know this works perfectly with the 7T Pro McLaren 5G, it doesn't break 5G. Thanks for your efforts:) :good:
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ricky886:
Will add UV on next version?

Thanks
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
blu_spark r77 release (A10 unified)

All right crew!

New build is up :highfive:

This kernel is unified, good to go on OP7/T/Pro (I only can test on Pro).

Custom ROM variant will only support ROMs that follow CAF/AOSP wifi module usage (I tested on OMNI). So if you use a custom ROM with builtin driver (like LOS), you're out of luck.

You can now use FKM download kernel feature, just import the links bellow in the app :highfive:

blu_spark_r77 release

FKM download configs: oos | custom

Keep in mind: I will give no active support for custom ROMs (including OOS based ones).

I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).

Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.

Also don't go spam and bug reporting on ROM threads if using this.

No mirrors please

If you like my work, donations are always welcome.

Don't forget to hit thanks and rate the thread nicely, it's free :)
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Fesag:
I flashed blu_spark_r77-custom_op7x_264c9254c.zip on a 7t.

Double tap screen activation does not work. Can I fix it?

blu_spark_r77-oos_op7x_0a127b34b.zip

Double tap work good.

What is the difference.

Why not add to the header?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Eddiemc:
It's in the op you just quoted, one is custom (for aosp) and the other one is for oos (Oxygen)

What ROM are you running?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Fesag:
Oxygen

blu_spark_r77-oos_op7x_0a127b34b.zip

Double tap work good.

Thanks! Wireguard work in kernel mode!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] lil_kujo:
Just installed through EXKM and its working great. Will report back after u use it for a couple of days. Thanks for the great work! OP7t hd1900 global rom 10.0.7 Hd65AA
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] lil_kujo:
So after playing a bit with the kernel and going through some settings i did notice that when you enable Klapse brightness dependent mode you wait for the screen to change colors it will make the fingerprint scanner stop recognizing your fingers, i tried it several times on and off and as soon as i turned it off my scanner would work again, i guess is because of the screen dimming.

everything else so far has been a charm!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Well an optic FPR sensor needs light ot work, if you mess too much with values it can misbehave.

Sent from my blu_spark'd OnePlus
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] lil_kujo:
Thanks mate so I found the sweet spot for it in the dimming option if the dimming is from 0-14% th fp won't work if you raise the dimming option to 15%-above it works just fine. Thanks for your work mate.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] heiskanenej:
My finger print scanner doesn't work with klapse if I don't change all RGB values to almost 256. I don't use dimming option, it's set to max. Same problem with all kernels I have tried. And I have 7T.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Doesn't seem all that bad considering. I personally think screen is already too dim in some situations, even with stock vlaues

Like I said, there's some technical limitations, that stuff was never designed with optical sensors in mind, but capacitive ones.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Eddiemc:
You mentioned adding minimum brightness setting to your app last month to support the minimum brightness option in this kernel, but I've not seen an update to the app. Did you release it?

I still can't figure out how to increase minimum brightness.. Am I missing something else here?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] NoSauce:
Confirmed that it works on OmniROM. Doubletap and Fingerprint works great! I'm not using Klaspe (which is off by default).

Thank you!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] franciscofranco:
You're right. I was caught up with life/wife is almost due with the baby so this month I was pretty slow. But good news is today 5.1 is going to be released and I already added this feature.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Congrats on the little one mate :)

Sent from my blu_spark'd OnePlus
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Eddiemc:
No worries mate, just making sure I'd not mistaken something here.

Congrats on upcoming fatherhood. If this is your first, welcome to a life altering roller coaster ?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] franciscofranco:
Don't want to hijack this thread but eng.stk asked me to add this backlight_min support consistently so here it is, it's been released in the latest app update: https://twitter.com/franciscof_1990/status/1227658176037892099?s=20
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Wineklek:
Can this going to fix my Qualcomm Crashdump Mode? The qcdm has a message or kernel stack overflow nmi_panic. I have a 7t which is always rebooting and booting in QUALCOMM CRASHDUMP MODE. Can you help me please?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Nope.

Sent from my blu_spark'd OnePlus
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Wineklek:
Do you know how to fix this issue? :( The seller refuses to replace the device and I try msmdltool already.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Mohammed779:
Go to bootloader and flash OOS.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] zioloiso:
You have problem with phone after instal custom Kernel?

Wysłane z mojego OnePlus 7T przy użyciu Tapatalka
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Wineklek:
Flashing Rom in bootloader needs my phone to be unlocked right? Also, does flashing in bootloader is also the same with flashing in fastboot?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Wineklek:
No sir, I am running a stock on everything.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Mohammed779:
You should be unlocked as far as I know. Which you can in bootloader? Then you can relock afterwards (ok maybe you shouldn't, I have no knowledge of this, but since osm0sis is saying so, it's better to listen to him).

Just enter bootloader or fastbootd then extract ROM file from here https://xdaforums.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213

Then just open flash-all.bat
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] osm0sis:
With no fully functional TWRP nobody should be playing around with relocking their bootloader yet.. :eek:
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] calvin0512:
I found that's the issue about the bluspark twrp. I got the same problem and solved it. I reflashed the official twrp and magisk and kernel. Everything come back, no data were wiped.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Lossyx:
Well, there is no bluspark or regular TWRP that actually works for 7T/Pro so that's not it.

But yeah, [MENTION=953821]winkle[/MENTION]k I guess it wouldn't hurt to try if you've already tried other options
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
blu_spark r80 release (A10 unified)

All right crew!

New build is up :highfive:

This kernel is unified, good to go on OP7/T/Pro (I only can test on Pro).

Custom ROM variant will only support ROMs that follow CAF/AOSP wifi module usage (I tested on OMNI). So if you use a custom ROM with builtin driver (like LOS), you're out of luck.

You can now use FKM download kernel feature, just import the links bellow in the app :highfive:

blu_spark_r80 release

FKM download configs: oos | custom

Keep in mind: I will give no active support for custom ROMs (including OOS based ones).

I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).

Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.

Also don't go spam and bug reporting on ROM threads if using this.

No mirrors please

If you like my work, donations are always welcome.

Don't forget to hit thanks and rate the thread nicely, it's free :)
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] michelemascia7:
Thank you :) I have a problem with the "download" and "flash" options in fkm app. Both of these two options doesn't works :/ the download process stops without downloading the zip. Anyone have the same issue?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Nope, just downloaded and flashed fine here.

Maybe some temp download issue on your end?

Sent from my blu_spark'd Oneplus
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] lil_kujo:
Downloaded and installed on update OOS 10.0.8 Oneplus 7t 19000. thanks!
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Eddiemc:
Nope, works fine here.

Check you magisk installasjon (root checker)

Try: removing and re-adding fkm in magisk

Still an issue?

Try: clear all data for fkm

Then (re)add the "link" so you can download/update blu_spark

Then try again.

If it still errors out, reinstall fkm

If it still errors, contact Franco.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Mohammed779:
Hey, well perhaps I shouldn't ask here, but since you've tested OMNI,

I'm having trouble with WiFi being lower signal compared to OOS, and well much lower speeds of course at same distance. Can this be kernel related? Perhaps any idea if it's fixable? 7T.

Thank you,
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] NoSauce:
I'm on OmniROM and I get full bars and max speed, same as my laptop. I'm sitting 5 feet from my router. I'm on r80 but also had no problems on r77.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Mohammed779:
At about 1meter, speed is fine. But once it becomes longer, or a wall is there, OOS WiFi performance becomes marginally better than on OMNI (like 150mbps vs 20mbps). I couldn't figure out anything about it sadly.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Didn't notice much difference to be honest, works +/- the same for me.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] pxrave:
No new kernel sources? ?

BTW Thx
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Hmm it's on github like always, what you mean?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] pxrave:
Sry didn't check github. Only your changelog. I mean new 7t firmware so maybe new kernel sources to be compatible to latest firmware ?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
You mean OP updates, sure.

There's no updates so far, nope.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] NoSauce:
I think I might be misunderstanding you because 150mbps vs 20 mbps seems like a big material difference. If it's 500mbps vs 300mbps it probably doesn't matter for most intents and purposes. But 20mbps seems low even for browsing the web.

I did some rough testing using SpeedTest. I could NOT compare OmniROM vs OOS ROM. However, I did make a backup of the stock kernel that OmniROM comes with and compared it to the blu_spark's kernel (r80). I also compared it to my laptop and my Pixel 1 (which has a lot of issues) running Revolution Remix ROM with Elemental X kernel.

TLDR: I saw no difference between Stock Kernel and blu_spark Kernel on my OP7T running OmniROM

Clearly, there are a ton of confounding variables. The one thing worth pointing out is that I have yet to put in a SIM chip in my OP7T. i.e. I haven't transferred over my number and connected to Verizon yet. With my Pixel, I turned off mobile data.

"Max up" is 450 to 500+ mbps. "Max down" = 17.5 mbps. When I got reception I got max up for all devices.

6 ft from X10 Router unobstructed:

OP7T (either kernel) and laptop: Max

Pixel: 250 down / max up

12 ft from Router through 1 wall

OP7T and laptop: Max

Pixel: 250 down / max up

35 ft from Router through TV and wooden door

laptop: Max

OP7T: 360 down / max up

Pixel: 250 down / max up

100 ft+ from Router through 2 walls

laptop: 150 down / max up

OP7T: ~50 down / max up

Pixel: no signal, 0 / 0

There seemed to be less variance between the trials with the laptop and it was consistently maxing higher ~530+ down.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Eddiemc:
My guess is that it would be due to caf/aosp WiFi drivers used on Omni Vs proprietary ones in Oos..

If so, to fix it would require a lot of hacking since they aren't interchangeable. Meaning; modification of the aosp drivers in kernel and making ROM changes to gain compatibility.. I guess you'd be looking at someone who does custom ROM+custom kernel combination releases based on aosp.

But I'm no developer so this is simply guessing?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Mohammed779:
Thank you for the thorough testing. I decided to get on OMNI again and test, and issue sadly still there for me. There's 2 meters + a wall separating me from the router. But I get 150mbps on OOS and 30mbps on OMNI. Exact same position same everything. even on really good wifis I tried, would get 300+ Mbps on OOS but not even 70mbps on OMNI (nor aosip for the record). Idk what to try anymore sadly.

It seems to be my body that does the blocking and reduces speed significantly on OMNI, or simply blocking top of the phone. However it has not been an issue on OOS.

yeah did some more testing, try blocking top of the phone with your hand, you'd see a significant decrease in speed, however on OOS, there is almost no drop in speed, which doesnt explain me much why is that happening.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Kernel driver is the same for both variants on my builds.

OOS has many tricks for lot's of stuff, while custom ROMS normally stick to CAF/AOSP.

There's inherent stuff that comes with config choices and so on, it can show more in some particular setups/use cases than others..

This is more of a ROM discussion than kernel, let's move on guys.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] jamesgryffindor99:
I was testing this kernel for a bit on my 7T Pro 5G McLaren, and after a day or so the phone gets really laggy then freezes up while in sleep mode. Happens with other kernels that I've tried too. Wonder if the 5G modem has something to do with this.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
Whatever you got there most likely is nowhere kernel related.

IIRC other people already tested in the early beginnings and it runs fine on that device.

Don't forget to match OOS to kernel codebase.

I don't how far behind/different that device is on OTAs.

Sent from my blu_spark'd OnePlus
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] osm0sis:
AnyKernel3 FlashAfterUpdate addon.d-v2 Support

Awesome news for custom ROM users! Now that the latest build is up-to-date with the AnyKernel3 git HEAD, it automatically has support for my new FlashAfterUpdate addon.d-v2 script, so you can easily keep a custom kernel installed through an A/B ROM OTA! :victory::highfive:

My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!

Setup is simple!

1) Download my latest 999-flashafterupdate.sh from the attachments of the scripts post in my Odds & Ends thread (read the blurb there/follow the links for more info).

2) Put the script at /system/addon.d/999-flashafterupdate.sh and give it rwxr-xr-x (755) permissions.

3) Create the /sdcard/FlashAfterUpdate directory and put the latest kernel zip there.

When you get an A/B OTA update the custom kernel zip should now be automatically flashed again at the end, over the boot partition of the updated slot, as part of the update process. Magisk root is required, and the latest Canary build is recommended.

You can also keep TWRP installed on A/B devices where recovery is inside the boot.img (boot-as-recovery)! See my 98-twrp_ab.sh addon.d-v2 script at the above link. With all of these in place, then TWRP, Magisk, and AK3 (via FlashAfterUpdate) all get retained through an OTA! :cowboy:

The script gets logged in logcat during booted OTAs, just like my TWRP A/B addon.d-v2 and Magisk addon.d-v2 scripts, so keep an eye there if you're curious, AND the next TWRP will also have support for addon.d-v2 thanks to the amazing work of [MENTION=7104332]k4y0z[/MENTION], so keep an eye out for that.

P.S. If there are any other mod zips out there that would benefit from FlashAfterUpdate addon-d.v2 support (i.e. they wouldn't be better handled by their own addon.d-v2 script), then contact the mod developer and point them to this post so they can follow my instructions for adding support.

Lastly, also feel free to pester any and all kernel devs who aren't up-to-date with their AK3 zips yet, and please link them to this post, so that we can make things easier for everyone on custom ROMs and custom kernels. :D
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] photolarry:
Does this work on McLaren? This device OOS is only up to December patch level. Rooting it causes OTA to break I'm told as well
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] TAGTRAUM:
I have McLaren (not 5G) and it works like a charm! But with OTA situation, yes, root "breaks" OTA notification, but not problem for me personally, i check the news frequently and know when new version is out, downloading full version (2.7GB+) and installing throught local update in updater and have actual version of OOS + custom Kernel + root + magisk etc :cyclops:
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] DanDroidOS:
I can confirm it works with T-Mobile McLaren 5G perfectly.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ums1405:
This is. Noob question.

How to install this kernel.? My EXKM does not see downloaded zip file to flash.

Is there something I'm missing?

Scratch that..... Bought FKM, works well.

Thanks
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] ums1405:
Thank you for a superb kernel.

Device is fast and smooth.

Thank you sir
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Dogedog:
do I need to disable ram boost?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
blu_spark r82 release (A10 unified)

All right crew!

New build is up :highfive:

This kernel is unified, good to go on OP7/T/Pro (I only can test on Pro).

Custom ROM variant will only support ROMs that follow CAF/AOSP wifi module usage (I tested on OMNI). So if you use a custom ROM with builtin driver (like LOS), you're out of luck.

You can now use FKM download kernel feature, just import the links bellow in the app :highfive:

blu_spark_r82 release

FKM download configs: oos | custom

Keep in mind: I will give no active support for custom ROMs (including OOS based ones).

I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).

Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.

Also don't go spam and bug reporting on ROM threads if using this.

No mirrors please

If you like my work, donations are always welcome.

Don't forget to hit thanks and rate the thread nicely, it's free :)
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] scott.hart.bti:
Ignore
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] osm0sis:
Weird, fingerprints are still working fine on my 7T.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] Galaxea:
Fingerprint also fine on my 7T. Has been on every version.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] heiskanenej:
Did you flash the correct version of kernel? Or are you using kcal or klapse?
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] scott.hart.bti:
Thanks for confirming.... I just figured it out. It is working fine... Until I enable the "night shift" display feature in the Franco kernel module. I enable that, it doesn't recognize the Fingerprint. I disable it, Fingerprint works fine. Weird.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] jotha.dx:
Working fine in my OP7t pro global

Thanks
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] eng.stk:
It is known. Some kcal and similar stuff interfere with the FPR, because it is optical and light sensitive.

Sent from my blu_spark'd OnePlus
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] lendawg:
Just rooted my phone and contemplating pulling the trigger on this kernel. Maybe a stupid question but does the op brain service still drain battery once a custom kernel is flashed? Do I need to flash the magisk module to stop it? Thanks in advance.
[OnePlus 7, 7 Pro, 7T, 7T Pro Cross Device Kernel D] lil_kujo:
I doesn't happen on this Kernel so you should be fine, honestly this is by far for me the best kernel in terms of idle drain which is around 0.4% per hour =3% over a lapse of 8 hours and screen time at least with my usage around 1 hour per 9% , performance is top notch. I been trying many other kernels and they all give a similar time for SOT but when I comes to idle drain and more consistency this kernel is king.