yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
If I had to guess I'd say yes but the only way to be sure is to try it. I do know the stock kernel from January works with December (don't ask how I know). Just have a known working kernel as a backup.

Just remember if you're fastbooting Kirisakura you have to flash its dtbo as well. Note that the dtbo for all the versions since 1.3.0 is the same (at least so far). And if you want to flash a non-kirisakura kernel you'll need to flash the stock dtbo (at least for stock and elemental-x).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] serpent android:
Hi all.seems a great kernel. A dev by tbe name of mikekotee666 has made kirisakura op7 for lg v20. Does it work.is it save to flash?im on alpha omega rom oreo on lg v20h910...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
If there’s a kernel for this device, going by the name “kirisakura” it is not developed by me.

Can you link me to the thread or to the github of this project?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] serpent android:
https://androidfilehost.com/?w=profile&uid=1395089523397942885
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Ah okay it’s just a download link.

It seems this is just my latest kernel for the OP7 Pro re-uploaded (which I don’t really like or see any point in).

Even the md5-sum matches with my zip. So yeah no idea why it’s uploaded there for the lgv20 , but it will not work on this device.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
i've had two instances where my Pixel 3 XL showed a black screen. The power button would turn the screen on/off. I could swipe to unlock, but the screen was black accept for the back button. I have to hold the power button for 10 seconds and get it to reboot. The next time this happens I will try to capture the log files after the phone reboots.

This seems to occur after a long period of not using the phone, like this morning after undocking from the Pixel stand.

Anyone else seeing behavior like this?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Post removed.

Sorry, was just stating that it did work on December since I had asked.

Just put that up there in case people run the stock flashall bat or sh. And were still in fastboot, wanted Kiri and root.

[MENTION=3428502]Freak07[/MENTION] , did not mean to be the cause of anything.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Does fastboot flashing your Kiri img also give the custom dtbo?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
I am just assuming it would since I did flash the 1.4.1 Kiri zip and while retaining magisk with it just made a backup with exkm. My logic - since the zip has the kernel / dtbo combined why would the patched .img not have it.

Please, allow for someone to chime in that is 100% sure on the answer.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
It does NOT have the dtbo image. Which is why I specifically stated that you need to flash dtbo. (See my previous response)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zaacc:
please add support to this! https://twitter.com/franciscof_1990/status/1215673739435704320
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
[MENTION=3428502]Freak07[/MENTION] didn't you implement flashing dtbo in your kernel as of 1.3?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
This leads to nothing good. [MENTION=4217078]dirtyreturn[/MENTION] I’ll politely ask you to remove the link to your uploaded boot.img.

The kernel is intended to be used on the latest available firmware which is January. If you personally want to use it with December firmware it’s fine if you do so. Just don’t report any issues. if anybody wants that boot.img they can gladly sent you a PM. I’d appreciate if you could edit your post.

This just ends with a firmware that consists partly January/partly December.

Why would your boot.img have the dtbo.img included?

they’re two separate imgs in the factory image as well.

I think the dtbo.img is flashed via my anykernel Zip since one of the first versions of this kernel was published.

The kernel is intended to be flashed with exkm/fkm via the anykernel zip. and I’d appreciate it, if there are no shared boot.imgs in this thread. If anybody ends up with weird issues and uploads logs, I might spend an hour essentially wasting my time trying to find the cause.

Also this leads to the boot.img being patched with different versions of magisk, that another user is on, which can also lead to issues.

Not trying to put down any of your work, but this is just not the right way, if you don’t exactly know what you’re doing.

And it seems there’s some more research needed :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
[MENTION=3428502]Freak07[/MENTION] - could be something you could implement. https://twitter.com/franciscof_1990/status/1215673739435704320?s=19
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] iamjimmy:
Anyone have any experiences of this kernel vs EX Kernel? Which has the better battery life?

Also does the Kirisakura kernal allow swipe up to wake like the EX Kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] newkydawg:
I haven't tried the EX Kernel so I can't tell you about the battery life but I can say the Kiri Kernel has Swipe up, down, left, or right to Wake.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It´s fine don´t worry about it. Like I said, I appreciate that you tried to help and provided something for the community.

Didn´t want to make you bad or anything. It´s just that it´s not a good and failsafe way.

Anybody that flashed this boot.img on January Firmware lost a part of January Firmware.

If you´re interested in why this isn´t a good idea. Maybe take a look at this article about A/B devices:

https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

The boot.img contains more than just the kernel. Basically boot.img != kernel.

To simplify it a bit: By flashing my kernel on december, and providing that backed up boot.img, people ended up with a ramdisk from December (which contains the stock recovery on A/B devices), a specific version of magisk that you patched the kernel with (which might conflicts with the previous version of magisk that was installed prior to flashing this boot.img), but a kernel from January. Depending on the setup they ran with, they ended up with whatever dtbo.img was installed on their device.

The Anykernel.zip allows to replace only the necessary kernel files on the fly (kernel parts of the boot.img as well as the dtbo.img) . That way you will only end up, with the parts needed.

Do you see why just providing the boot.img causes issues?

the dtbo.img is a bit of a different aspect of the pixels. It allows the kernel tree to be unified. Since I modify code, when building my kernel, that ends up in the dtbo.img, my anykernel zip will replace the dtbo.img as well.

That´s why you need to flash both, boot.img and dtbo.img extracted from the factory image that matches the firmware you´re currently on to restore the stock kernel. Flashing just the boot.img is not enough.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
[MENTION=3428502]Freak07[/MENTION] .

DARN IT!

Oh, man. Hopefully noone on xda flashed it.:confused: , I'm not the most competent with Android.

If you have the time, with the flashall, how do you update while maintaining root?

I get that removing -w keeps data intact and one time I think I even tried removing the boot.img from the ROM pack off of Google. It just errored out when I tried flashing.

Any way you could give any pointers? It'd be very appreciated.

YES, I see that what I provided was not what I thought I provided.

Lesson learned I believe.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
If you want to maintain root while using flash-all here's what you can do:

1) extract boot image from factory image download and patch it via Magisk Manager.

2) modify flash-all.bat/sh as follows:

:: replace -w with --skip-reboot

:: At the end of the script add the following:

(sleep 5 is for sh

for bat use

ping -n 5 127.0.0.1 >nul)

[/code]sleep 5

flash --slot all flash boot <your patched boot image>

sleep 5

fastboot reboot[/code]

After you reboot you'll still have Magisk. Just flash Kirisakura on top of it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ojiz1:
Google P3 xl

Newbie here, so dont judge right away. I rooted my pixel and downloaded Franco kernel manager and flashed the newest Kiri kernel. Well apparently gaming performance does not have any impact if i use performance mod in FKM. Just wondering can this FKM change this kernels thermal throttling values? I dont care if my pixel get toasted for it, just wanted stutter free gaming performance. Any tips how to improve gaming performance via this kernel and FKM?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] iamjimmy:
Thank you very much. I will try the Kiri kernel instead of EX.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
There's probably a few more things you should do before you go messing with stuff like that. I could be wrong here, but that seems like one of those things that unless you know very precisely what you're doing, things can go bad fast.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Ojiz:
Alright, I know the risks.. I just tried gaming with friends Oneplus 5 and i immediately noticed that it gets hotter than my Pixel 3 XL, and it was stutter free, so it didnt throtle like crazy like this googles flagship. I can run fps benchmark test and it throttles after one test which takes 2 minutes. Very light degrees (phone back maybe 30 celsius) so that why i asked.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kakabobo:
fingerprint scanner issue with this kernel? most of the time fail authentication. maybe just 50 percent success rate?

revert to stock and issue seen to fix.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] drdrewdown:
never experience that with Kiri, seems unlikely
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] luckana:
It's funny because i also have that, are you blocking any wakelocks ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lagarde:
I hate doing the "it works for me" but I'm blocking a bunch of wakelocks and not having fingerprint scan issues at all. If it is a wakelock issue, it might be a specific wakelock being blocked or app frozen/removed. If it looks like a wakelock issue you're having, I'd be happy to compare lists of what I block vs yours and see if there's something that might be causing it on your end.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Only problem I have with the fingerprint scanner is that when my finger sweats up it doesn't register:silly:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
I've been experiencing this lately, especially with Spotify and Bluetooth streaming.. UI stutters alot , or even opening Google messages takes a few seconds to respond.

I just flashed and go , no user specified settings
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] iAMv7:
My phone charges slowly compared to the stock kernel. I have the Pixel fast charger. Is it some tuning done by the kernel or could I be wrong? It also never charges to 100%, it stays at 98%. any help would be appreciated, and if needed I can provide logs. Using on the normal Pixel 3 :D
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] luckana:
I have had this bug ever since. I think it's a software issue try unplugging and plugging the cable back in, usually does the trick and will show up to 100% charged. Btw mine stops at 98 as well when it happens
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
For the record , i've experienced a variety of hiccups on the UI even with stock kernel etc. just don't understand why , or even how it's getting worse.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gacky1601:
possible to add rapid wireless charge?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
For me when I tap and on-screen button, such as to stop music from playing there's usually a 4 second delay between when I tap it and when it disappears off screen.

Recent kernel, January patch
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KurioHonoo:
Has anyone switched from LZ4 to LZO-RLE for ZRAM and if so have you noticed any improvements or deteriorations?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
I use EXKM to set lzo-rle algorithm and 175 swappiness at boot. I haven't noticed a huge difference - LZ4 is good and fast, but I believe lzo-rle is (slightly) better for Android use, at least theoretically. It certainly hasn't resulted in any noticable problems.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KurioHonoo:
How exactly does a swappiness value above 100 even work?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
I set swappiness to 175 because Freak07 and jcmm11 both do, and those guys seem to know what they are doing :)

Freak discussed briefly what the setting does in his release notes here:

https://xdaforums.com/pixel-3-xl/de...ra-1-0-0-pixel-3-xl-aka-t3864563/post80269185
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KurioHonoo:
Thank you! Is there anyway to easily find all of the big release note posts like that one?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KurioHonoo:
So I changed to lro-rle and 175 for swappiness and even made sure everything was set to apply on boot and they keep getting set to Disabled zram and gets set back to lz4, swap stays at 175 though and all of the apply on boot buttons are still set
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nullness:
I believe zram is enabled by default, so you shouldn't have to touch the toggles to turn it off or on. I tried using lro-rle but I realized it was booting with lz4 then when settings were applied it had to do process of cleaning then recreating the zram to use lro-rle which is a slow process so I just decided to leave lz4 as I personally didn't see any difference with it enabled anyways.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KurioHonoo:
Cleaning and recreating is what I did and it doesn't stick.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
i am going to flash 1.4.1 with Feb 2020 update. I will report back.

Got it working but on first reboot after screen turn off. I turn it back on but lost touch sensors, have to hard reboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Xeust:
I'm using Pixel 3 with February update with 1.4.1 kiri. Works fine. No touch issues.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nomisunrider:
Same here. No problems on February update.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
the update is already compiled. I want to give it a good test run until tomorrow, to make sure everything is stable.

If everything is alright I´ll release the update tomorrow morning :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Samuel Holland:
CrossHatch_#1

Hi, I just wanted to share that using "Sysctl GUI" found on XDA Labs seemed to work nicely for setting "swapiness" on boot. Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KurioHonoo:
As in you can use Sysctl GUI in place of EXM or KM if you'd rather not use them or use Sysctl GUI even if you use either of those two to make sure swappiness is being set on boot?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] crixley:
This kernel is really battery friendly! Great work ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] luckana:
In my experience, after some testing with lz4,lzo-rle and zstd, subjectively zstd performes the best, keeping the overall zram usage fairly stable and not aggressive even (swappiness at 175)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Thanks for the update Freak !

Enjoy your coffee !
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Expliciate:
Edit: 1.5.0 working great so far. HBM seems to only work with EXKM and not FKM, not sure what the difference is.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xuser_:
[MENTION=3428502]Freak07[/MENTION],

Any chances this kernel may not require root in future ?

and works for pixel 3 device?

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] crixley:
How could flashing a kernel not require root?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
Flashing a kernel only requires an unlocked bootloader,. You don't need root unless you're using ex or Franco kernel manager.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] crixley:
Ah I assumed since twrp does not work on Android 10 that this was not possible. Is it just done via fastboot flash?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KurioHonoo:
The first thing that comes to mind is if someone was uploading a stock Pixel 3/XL boot.img that was pre-flashed with the Kirisakura kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I set it to 1 in user settings. I appreciate the help, thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Best kernel on the block. Kudos to [MENTION=3428502]Freak07[/MENTION] I have been following you for a long time now. This is the standard everyone should adhere too. Smoochie! Kiss, kiss.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I tried flash in exkm got the unpack ramdisk failed error. Reboot to twrp and try to flash there same error. How should I fix this? Is there a boot.img zip file?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
You can flash the boot.img directly in TWRP. That'll clean it up then flash TWRP, kernel and magisk.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
thank you for the tips, all is good now. but I wish it will work inside EXKM so don't really need all this extra steps.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
I just extracted the boot image from the November update. It's in the zip. Copy it to your device and in TWRP you can Flash an image take a look
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
It generally will work. But sometimes it doesn't. That's why I keep the monthly stock boot.img on my device. I just had the same issue you did and was fixed with just a few short steps.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
I've never had it fail in EXKM, and I've flashed thru the app probably close to 100 times on this phone. I wonder if there is some mod that causes this problem?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
No mods, other than TWRP/kernel/magisk. It works fine most of the time. About once every 4 flashes or so, I get the error. Only a fresh start corrects it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
I never flash TWRP, always fastboot it (except Essential, which doesn't allow it). Trying to have custom kernel, root and custom recovery all modifying the same partition has been the cause of most user problems since a/b partition devices started. TWRP works perfectly in fastboot mode, and I never have issues with a/b, Magisk or kernels.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Really strange... I´m a bit baffled.

[MENTION=4684315]flar2[/MENTION] I also flashed all my kernel builds (not yet 100 but nearly 70) consecutively either in TWRP (have it permanently flashed to ramdisk of boot.img via .zip installer) or EXKM. Root was always preserved and I never faced the error. I´m using a canary magisk, although not the latest.

again thanks for chiming in :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
[MENTION=3428502]Freak07[/MENTION]

possible to mount all partitions with noatime and nobarriers in kernel?

should give a nice bump in UI Performance
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
I don't have TWRP or any Magisk modules and it's still failing with EXKM.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
Substratum? BusyBox?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
No I won’t include this by default into the kernel.

Anyone that wants to risk a partition getting corrupted in case of an unexpected shutdown can do that via a script herself/himself.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _LLJY:
You can do that in fstab.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
Nothing at all. Do we need BusyBox?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
System is mounted before fstab is read so any changes to system in fstab makes 0 difference to actual mounts iirc change came in oreo
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kingkong0821:
Don't know if it's kernel related

But I found that the now playing history is not working

And the only changes to the device I can think of is flashing kernel
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Still working here
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wangdaning:
Yes, you will need a boot.img of the Kirisakura which would only be available if someone else posts it. This is released only as a zip, so you need root to flash it. Once choice is to root, flash the kernel in EXKM, then after it is installed uninstall magisk. Never tried that personally though.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fratletimac:
Hi, how flash this kernel for adb?, Thanks:good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] redsmith:
Kernel must be flashed via fastboot, or via a kernel manager if you are already rooted.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fratletimac:
Adb sideload "KERNEL".Zip?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wangdaning:
You cannot sideload this kernel. OP only includes .zip files, they must be flashed on a rooted phone with kernel manager.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fratletimac:
Ok, thanks, :good:, i try
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] muttonhead411:
March feature drop is out!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
Let me guess, you wanted to tell the OP to hurry the ...up? :D:cool:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nomisunrider:
I'm running the March patch with Kirasakuro_Q 1.5.0

I had the phone freeze up while playing a calendar alert tone. I had to hold the power button to reboot it hard. Will the ramoops files provide anything useful?

Thank you
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
i am on Tmobile so no update yet for me
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] melgar:
I'm as well on t-mobile(germany) and now on march firmware without any issues. Everything's fine so far...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I’ll try to update the kernel tomorrow.

I’m very busy right now and struggling to find time.

A little bit more patience and it’ll be there :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Everything seems to be working well as of now.

If it stays that way I try to get the release out this evening! :)

Thanks for everybodys patience!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] enweazudaniel:
Stable enough ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
how are you patching the boot.img in magisk now, it's not working for me, i am on build 277.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
You can't be in Canary. It crashes when trying to patch.

Need to uninstall Magisk Manager and install the stable Manager
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TraderJack:
Just wanted to check that you were aware of all the issues people are having passing ctsProfile checks now over the past couple of days.

I have no idea if this is something that can be fixed on your end, or if you need to find out more data from the (Magisk) community first (no one yet seems to have any idea apart from it is most likely being detected from unlocked bootloader).

Just wanted to make sure you are aware as there hopefully will be a solution found that you might need to integrate.