yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] bradical711:
Okay so now I'm super worried but let's back up a bit.....

Windows PC

Platform tools latest 33.0.1 installed & tested

Franco Kernel Manager

I flashed your "Kirisakura_Oriole-2.4.0_A12_stable.zip"

Magisk renamed & Hidden

Zygisk - Enabled

Denylist - disabled

Magisk modules installed as follows:

Ainur Narsil

Audo Modification Library

AK3 oriole Kirasakura 2.3.0

JamesDSP

MagiskHidePropsConfig

Substratum

Systemless hosts

Zygisk Universal SafetnynetFix

I was doing my usual OTA updates on my computer for my pixel's today with no issue until I hit my Pixel 6 just now. Usually when I did my previous Pixel 6 updates I had a stable and consistent process and is as follows.

I would disable all my modules listed above, uninstalling the substratum overlays as well as restoring stock boot.img, dtbo.img, vendor_boot.img & vendor_dlkm.img BEFORE attempting each update. I would then patch the next month's boot image (in this case the May boot.img) ahead of time so I could then be rerooted on the following boot up after the update.

Well.. I forgot to patch this months boot image so I booted up without root after the process just fine. I was on May's OTA and April Google Play System Update. After patching May's image and rebooting I had root and I enabled all my modules again (EXCEPT ak3) with no issue thus far.

The problem arose when I flashed your Kirasakura kernel 2.4.0 for oriole. My phone got stuck in a bootloop immediately. Now I didn't notice anything odd in the flashing logs before because I clicked "flash & reboot" and wasn't reading the log when I encountered the first bootloop. My Pixel 6 wouldn't make it past the 'google' logo at that point...

I did save it a first time by reflashing the Pixel 6 May OTA again. Now I rebooted just fine after that but I wanted your kernel because I've used it before and thought it was an odd fluke for sure. Never had it before and thought I downloaded the wrong zip.... But I hadn't...

So I reflash again but this time I notice the oddest thing at the end of the flashing screen before I reboot. A FATAL TYPO.....

/dev/block/vendor_dlkm_ak3

I didn't catch a picture the second time but I'm pretty sure that caused both boot loops in my case. However the second boot loop is much WORSE. I'll post a picture of the stage I'm at now....

I tried the same process that fixed it the first time which was reflashing the May OTA but it didn't work and couldn't verify the package. Idk how/why/where to fix this now. This is beyond my realm of knowledge and as of now I just wanna know how to fix my phone because I can't turn it off/reboot it. Check screenshot below...
[Google Pixel 6 Pro] capntrips:
What version of Magisk are you using? Do you have verity disabled? Some (all?) people using Magisk 24303 or later with verity enabled have this issue.

This is expected for AK3 version 20220430 or later. It is a temporary partition used for resizing the logical vendor_dlkm partition on a running system. See here for details.

I have no idea why flashing the full OTA isn't working in recovery, but I've had the most luck with the Android Flash Tool. If I ever have the full OTA or flash-all script fail, the flash tool still manages to work.

You can also try flashing boot, dtbo, vendor_boot, and vendor_dlkm from the full factory image. See "How do I return back to stock?" in the FAQ in post #2.
[Google Pixel 6 Pro] bradical711:
Thank you for updated information & help, much appreciated. I am using stable magisk 24.3, I never disabled verity before when I first rooted and now that would make sense. But I've never had to disable verity before on stable magisk for the Pixel 6 prior to now, why would I have to do that now with the may update.? From all I've read, verity requires yet another wipe so if I could avoid it, I will. I just recovered my pixel 6 again WITHOUT wiping..
[Google Pixel 6 Pro] capntrips:
Just to clarify, you don't have to disable verity with 24.3 stable. It's the combination of the latest canary builds and having verity enabled that is causing bootloops. I'm on the May update and 24.3 with verity enabled, myself.

As for why it didn't work for you, I'll have to defer to others.
[Google Pixel 6 Pro] bradical711:
So my situation was just an anomaly then because I tried flashing kirisakura a 3rd time and it worked!! I don't know why it didn't work the first 2 times but reflashing the may factory image without the "-w" and rerooting worked. What a bizarre situation to have happen twice but work a third.
[Google Pixel 6 Pro] 93ae8074:
A bit different though, 4.1.0 detects Zygisk, 4.0.1 detected Magisk. Oh, well, the hunting game...

Update:

Latest version of Shamiko fixes it.
[Google Pixel 6 Pro] Nightf0x_007:
Pixel 6 here my screen freezes and touch become unresponsive sometimes after closing apps from recents and going back to homescreen and when messneger bubbles i finish using it and close the bubble, does anybody knows what might be the cause of the issue and sometimes bottom half of the screen becomes unresponsive while upper bottom works
[Google Pixel 6 Pro] rhetorician:
Happened to me too but I don't believe it's related to the kernel. I believe in my case, it was lxposed related.
[Google Pixel 6 Pro] Paz9:
Make sure your finger isn't touching the side of the screen even swiping only time I notice I can't return home is when one of my fingers holding the phone is pressing on the screen
[Google Pixel 6 Pro] majorfigjam:
And the latest Shamiko v0.5.0-110 module is here: https://github.com/LSPosed/LSPosed.github.io/releases
[Google Pixel 6 Pro] awarman:
I am still experiencing this issue. Keep in mind it's only with screen record. I don't see any slowdown issues elsewhere but I would think that I shouldn't have an issue there. Here is a video of it.

This is not happening on my wife's P6 with stock ROM+kernel and no root.

I've even factory reset and checked for any bad apps that may be causing the issue but can't find any. I am running lsposed with face unlock but this issue occurred before that.

I could flash the kernel back to stock and check but I guess I don't really want to.

Does no one else see this from a screen record?

0 new items by Andy Carter

photos.app.goo.gl
[Google Pixel 6 Pro] Freak07:
something is keeping the phone awake. maybe an app stuck in background, maybe a service silently crashing.

better battery stats might be able to give you an idea (there´s a workaround to get it working "enough" on A12 in this forum or the thread of better battery stats app) or other apps that were previously mentioned here.

The kernel itself does not keep the phone awake or cause any drain. If an app/service requests a wakelock or resources and asks the kernel it´s usually granted otherwise wifi, bluetooth, mobile data etc would not work. Simplest example is no notifications if phone can´t wake up. :)

Sometimes a simple reboot fixes those things.

Thanks for sharing those. The kernel log (dmesg) you shared doesn´t show anything regarding screen recording, but I also didn´t expect it to.

I believe it´s a userspace issue, so sharing a logcat would be helpful if you encounter it again no matter if it´s caused by the kernel or not I can take a look at the logcat if you share it as I can´t reproduce the issue on my end.

But I have another question, is your fingerprint scanner working? Do you have it set up at all?

There are some very strange lines in your log and I believe the fingerprint hal can´t be started, but the phone is constantly trying to (sometimes several times a second). That in itself could potentially lead to a lot of issues as it constantly polls.
[Google Pixel 6 Pro] ㄹㅇhh:
Hello developer, can evolution ROM use this kernel?
[Google Pixel 6 Pro] Freak07:
Hey,

I personally don´t run a custom ROM at the moment, but according to this post I´m assuming it should work just fine:

https://xdaforums.com/t/kernel-03-0...pixel-6-pro-aka-raviole.4358435/post-86874933
[Google Pixel 6 Pro] awarman:
Of course it is not lagging this morning when I attempt to replicate it. Not that I'm complaining. I will send you the lcat the next time it does(I assume today).

As for the fingerprint, it died when I replaced my screen and I'm using face unlock. Not sure if it's a hardware problem with the scanner or something else with the OS. I don't need it with the face unlock though. Do you know of a way for me to disable it and the service? I see it in the lcat too. I'll take an adb command even.

I will note that this started before the screen change and fingerprint issue.
[Google Pixel 6 Pro] darkcbc123:
Guys, does this Kernel help with overheating?
[Google Pixel 6 Pro] Freak07:
It might help, but it must not help. It all depends on your own unique usage, ambient temps and other factors. There were a few changes introduced that could affect this, but they must not.

It might have helped this user:

https://xdaforums.com/t/kernel-03-0...pixel-6-pro-aka-raviole.4358435/post-86837487

While it might not make a difference for others.
[Google Pixel 6 Pro] Reechings:
I've never had problems flashing Kiri on custom roms, I just flash the one that matches up (April/may etc)
[Google Pixel 6 Pro] Admiral2145:
dtbo dtbo.img

vendor_boot vendor_boot.img

How often do we have to update or flash these files... I'm asking because after I root May then I use fkm to flash this kernel or another one I get bootloops until I flash the stock kernel then root via magisk.... This is the 1st time I've ever ran into this issue... April March and Feb was flawless with fkm and 24.3 stable.
[Google Pixel 6 Pro] awarman:
@Freak07 Here you go. Do you know how to disable the fingerprint polling?

It's lagging when doing a screen record currently.
[Google Pixel 6 Pro] rolarocka:
This kennel is awesome 👍😍

Got a question, I'm on 2.40 and need to update to 2.40 with the fix. How do I do that? Dirty flash with FKM? Magisk retains?

Ty
[Google Pixel 6 Pro] Lughnasadh:
Yeah, just flash the newer version in FKM. You'll retain root.
[Google Pixel 6 Pro] Sasaiber:
Please tell me which is better: kiri or radioactive kernel?..

It's just that both have heating of the phone (34 degrees Celsius) May patch
[Google Pixel 6 Pro] roirraW "edor" ehT:
This kind of thing is subjective - personal to each individual user - and also isn't a welcome discussion almost anywhere but particularly in one kernel's thread. Flash one, try it, see what you think for a month. Flash the other, try it for a month, and see what you think.
[Google Pixel 6 Pro] Sasaiber:
Н Good. Thanks for the answer. Just curious about people's opinions
[Google Pixel 6 Pro] Paz9:
Should this be official 2.4 now?
[Google Pixel 6 Pro] Sasaiber:
Phone temperature 38 degrees Celsius when using telegram :( The set of applications is minimal) Wi-fi and lte - the temperature is the same (((Probably it's still in the May update._.

I'm sorry, I'm just afraid that something is wrong with the phone. I thought that others also have problems with overheating.
[Google Pixel 6 Pro] DespairFactor:
I have found the May update to be a huge step backwards from April, I have the QPR3 beta running on my device now and it is far more stable. More acceptable battery and temperatures.
[Google Pixel 6 Pro] Sasaiber:
Thanks for the answer! I'll probably upgrade to it!

Or better on Android 13? I just want normal battery and device temperature :(

Tell me please)
[Google Pixel 6 Pro] DespairFactor:
I would say QPR3 is a better option
[Google Pixel 6 Pro] Sasaiber:
Thanks to!
[Google Pixel 6 Pro] russian392:
2 weeks on the kernel running stock 12.1. Things I have noticed:

1) Battery life is maybe 10% better on average, mostly during standby and heavy usage. There are a few medium use days that do worse, but over all its a bit better. My battery life was already pretty good even on stock.

2) Yes the thermals are better. But I noticed that there is absolutely nothing you can do against 5G or LTE overheating. Using data pretty much guarantees higher temps, but on wifi it heats up less, but my device didn't have much issues.

3) Overall everything is as stable if not more stable than stock, if you have bugs, this may or may not help. Things like the swipe up freeze bug still happens occasionally, as app related bugs won't be fixed by a kernel.
[Google Pixel 6 Pro] Freak07:
Not the case for me. Battery and temps are the same as before on my end.

There has been nothing that's not stable in May for me too.

Depends on your ambient temperature if that's normal or not.

I'd check if something is pinning the CPU in background, could be an app getting stuck or a service.

Could be something else that was introduced in May update and only affects some users and not others.

Check the post here that links how to do this:

https://xdaforums.com/t/kernel-03-0...pixel-6-pro-aka-raviole.4358435/post-86772729

In this case it turned out to be Facebook.

https://xdaforums.com/t/kernel-03-0...pixel-6-pro-aka-raviole.4358435/post-86772819

Nope, if mobile network has a weak signal it takes more battery (which also causes more heat due to higher power draw), you're entirely correct. (y) most of this is due to baseband and not kernel, so the kernel doesn't have much impact on that, just like other userspace/framework related issues.
[Google Pixel 6 Pro] arvylas:
Hi freak, is it possible to make a version like this? Not a demand or anything of course, only if you have the time and will.
[Google Pixel 6 Pro] Freak07:
sorry, I completely forgot about that.

I´ll send you a PM once I have a build with it completely removed. Alternatively you can set /sys/kernel/mm/lru_gen/enabled to "N" (for example in EXKM, tools, user settings simply add the node) to disable it at runtime. (please note that this setting might be overwritten each time you boot, so wait a while after the phone booted successfully to change this setting)

If you´re still running the kernel I´d appreciate if you could report back with it disabled that way. If not I´ll try to get a build out for you. :)
[Google Pixel 6 Pro] Admiral2145:
I'm new and can't seem to find where I was or the article/guide that shows how to do this part of vendor and enable /disable this part... I have to manually download the whole factory image instead of doing the Ota to update via computer.... If that matters/i see it overwrites vendor with this process.
[Google Pixel 6 Pro] awarman:
We'll try this again. It didn't let me edit my message and add it for some reason.

I am getting lag right now when recording but it's not awful. Performed a couple reboots when I was trying to disable the fingerprint service and since it only jitters or lags after a number of hours.

Do you have any idea how I would disable it? I definitely want to rule that out as a factor and so far I've come up short. I read that I could unmount the driver but I'm not sure what driver it is.
[Google Pixel 6 Pro] arvylas:
Didn't know it was that easy. I'll flash back 2.4.0 and report back using the flag.

Edit: which value should I set? 0x0000?

Btw I was using radioactive kernel for the past week and didn't face the same issue. Do you know if it has the MGLRU patch as well?
[Google Pixel 6 Pro] Freak07:
yeah, either that or just simply "N" or "0" :)

Wanted to do a separate build as disabling via runtime is not exactly the same as reverting all the needed code for MGLRU.

Yes radioactive has MGLRU included as well according to the source. So it might not be that after all, but well hard to say.

You should soon receive a PM with something to test on your end. :)

I tried constantly over the day yesterday and I still can´t reproduce lag during screenrecording similar to the one you shared.

Might need to put the log in a zip, like you did with the dmesg previously. XDA is somtimes a bit finicky.

Unfortunately I don´t know how to stop the phone trying to poll there with a simple adb command.

I think rmmod´ing the driver won´t work as it´s not allowed to unload the driver during runtime. the command would be similar to this:

rmmod /vendor/lib/modules/5.10.116-Kirisakura_Raviole_2.5.1-992957-geed62cb785cd/kernel/drivers/input/fingerprint/goodixfp.ko

where you replace the kernel version, with the version of the kernel you´re currently on.

Maybe it works for you as you´re fp scanner is already broken, but I don´t think so.
[Google Pixel 6 Pro] awarman:
Tried it and it looks to still be polling even with a successful command. As for the lag I rebooted and it ran overnight but it's not lagging at all which leads me to believe it's something I am running through the day? Not sure.

I have tried the google fingerprint calibration too but it always ends up telling me I have a newer version thus I've had no success.

I realize this is unrelated to kernel but would you know of a way to stop or disable the ServiceManager from trying to start the FP reader? Maybe a magisk mod? Understood if you don't want to discuss this on your kernel thread.

Thanks for the help! We'll see if 2.5.1 changes anything.
[Google Pixel 6 Pro] Freak07:
if my suggestion above did not work for unloading the fingerprint module/driver and thereby stopping the polling I don´t have any other ideas sorry.

maybe a rom developer knows how to prevent that single part from starting, but I don´t have any other ideas. I´m also not sure if magisk can help as the file vendor/etc/init/fingerprint-goodix.rc gets parsed before magisk can change any files during bootup.
[Google Pixel 6 Pro] Sonoo:
Hi, I am trying to flash this kernel (2.4.0) on stock Pixel 6 pro rooted with magisk and updated to the latest canary (24312) and May update. Every time I flash it via EXKM or FKM it flashes normally but after reboot, it gets up to the google logo but then hard crashes and starts looping. I managed to go to the bootloader and was able to restore it to the stock kernel. What am I doing wrong here? I can't figure it out! Any suggestions.
[Google Pixel 6 Pro] bleez99:
Use Magisk stable 24300
[Google Pixel 6 Pro] Sonoo:
I don't think it is recommended for the May update. Will try
[Google Pixel 6 Pro] bleez99:
Not to be rude but yeah, it is recommended, and I'm on May as well with stable.
[Google Pixel 6 Pro] Sonoo:
Sorry, but I was referring to the above guideline. Returning to stable now. :)
[Google Pixel 6 Pro] V0latyle:
This is only for the stock kernel. A few things have changed with the Pixel 6 boot image that have required Magisk fixes. If a kernel developer is using the stock kernel as a base and incorporates the same changes, then yes one would want to use the latest Canary. However, many developers either use an old base, or build their kernel from scratch using the original kernel source; in those cases one could probably use almost any version of Magisk since 24000.
[Google Pixel 6 Pro] Sonoo:
Installed fine with stock magisk
[Google Pixel 6 Pro] Sonoo:
Didn't know that. Thank you.
[Google Pixel 6 Pro] V0latyle:
It's important to pay attention to the commits and update notes :)
[Google Pixel 6 Pro] Ghisy:
Some would even say that you need to "commit" to this hobby in order to root safely. 🙃

I'll see myself out now...
[Google Pixel 6 Pro] V0latyle:
Well, some people are rooted in tradition....
[Google Pixel 6 Pro] Gytole:
Am not developer but yesh 😉
[Google Pixel 6 Pro] acidspider:
Finally found the courage to reflash this kernel after a corrupt error forced me to wipe my device last time due to the issues with magisk canary,all good now though and glad to be back, p6pro feels so much snappier
[Google Pixel 6 Pro] mrViZhy:
Hello,

"- supports direct usb access for hi-res playback over USB-C DACs"

1. Does it possible to unlock HDMI Alt mode?

2. As i understand - miracast support depends on ROM (not kernel)?

As i know this features are locked by Google to push users to use Chromecast.

UPD: HDMI Alt mode and miracast support will be a strong reason to root my Pixel 6.
[Google Pixel 6 Pro] swieder711:
My employer recently made us switch to Microsoft authenticated apps on our mobile devices. After hiding Magisk stable 24300 and denying all the Microsoft apps, I was able to run programs like Outlook and Team without root being detected. I had the initial 2.4 kernel running too.

Today, those app started to detect root and would not run. I dont know what changed to cause root to get detected.

I upgraded to Magisk Canary 24313 and can hide root from those apps again. Unfortunately, I when I tried to flash original Kiri 2.4, the Google logo just appeared and then went out.

Are there any workarounds to get this kernel running with Magisk Canary 24313? Is there a test version of the kernel that might work with Magisk Canary?

thanks,
[Google Pixel 6 Pro] Freak07:
Try magisk stable with the kernel zip attached to this post:

https://xdaforums.com/t/kernel-03-0...pixel-6-pro-aka-raviole.4358435/post-86860531

If you disabled verity/verification vbmeta flags you will have no trouble using magisk canary. If your vbmeta flags are enabled canary will not work as far as I'm aware.
[Google Pixel 6 Pro] swieder711:
If I use Magisk stable then root gets detected by the Microsoft apps.

I have Magisk Canary currently installed and have it hid and deny list is enabled. I need to research how to determine the state of the verity/verification vbmeta flags.

Are you saying that if these flags are disable then I can use Kiri 2.4 with Magisk canary?
[Google Pixel 6 Pro] Freak07:
If you didn't disable the flags while updating each month, they are enabled.

Disabling them requires a full wipe.

Yes, canary with this kernel works fine if the flags are disabled.

Magisk changed the way verity is handled during the canaries and that's why things will change. It has nothing to do with the kernel itself.
[Google Pixel 6 Pro] swieder711:
Thanks for the clarification. I am running Magisk Canary and can hide root from my corporate overlords. I didnt use an vbmeta flag options when I flashed the Magisk Canary via fastboot.

I am going to hold off on doing a full wipe. I did a flash-nowipe earlier today to bring my phone back to life after it got borked.

Sad to now be running a stock kernel!
[Google Pixel 6 Pro] capntrips:
The issue is Magisk no longer strips the avb key from fstab entries, so if you don't have verity disabled, when the system tries to mount vendor_dlkm, it looks for the hashtree described in vbmeta, but it doesn't exist, and even if it did, it would no longer match the the descriptor.

I posted a workaround on the issue in the Magisk repo, but it currently isn't trivial to apply. Unless there's some way to modify the fstab entries from within the kernel, it seems we'll be forced to either disable verity or patch vendor_dlkm (though I suppose it could be shipped with the hashtree already appended) and vbmeta.

The upside is patching the hashtree descriptor in vbmeta does not require you to wipe your data.
[Google Pixel 6 Pro] Freak07:
You don't disable the vbmeta flags when flashing a boot.img, but when updating your phone via the factory images for example. Or just issue the command via fastboot for the current firmware you're on.

If you plan to disable the flags in the future, you have to repeat the command to disable them each time you flash a firmware package (full OTA zip or factory image) that contains a vbmeta image before you boot into the phone with the updated firmware.

I kept my flags disabled (which allows me to basically flash any source compiled image to my phone without tripping verity and relying on magisk for this in any way) since the beginning (magisk did not support this in the first few days of the pixel) and that's why I have no problem now.
[Google Pixel 6 Pro] swieder711:
Can I use your modified vendor_dlkm and vbmeta images for the May update to flash them to my Pixel 6 Pro?

If I understand thing correctly, this would like me Flash Kiri 2.4 without wiping my phone.
[Google Pixel 6 Pro] Freak07:
Edit: mis-read due to already being half asleep. :D
[Google Pixel 6 Pro] capntrips:
I'm on Pixel 6 (oriole, not Pro), so mine will be different from yours. I'll try to package up my workaround in the next few days to make it a bit easier to apply, assuming I can generate the hashtree on-device.