yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
No that's not really correct. 1.3.0 instructions are just for 1.3.0 and below. I guess I'll remove them from the OP now, as nobody will be on November any longer.

To flash 1.5.0 there are the instructions for using the kernel.zip via exkm/fkm or manual install.

You can have verity flags enabled or disabled, it won't matter if flashing the 1.5.0 zips, as long as you initially rooted via magisk 23016 or higher, as the kernel.zip has magiskboot 23016 integrated to flash and repack the kernel.

Same goes for manual install. As long as you patch the provided boot.img via magsik 23016 or higher, you can have the vbmeta flags enabled or disabled.

Here's another explanation:

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

The biggest risk is unlocking the bootloader and rooting the device. Pay attention to what you install or run on your phone, then you will be fine.

But you can just leave the vbmeta flags enabled as long as you use magisk 23016 or later to root.
[Google Pixel 6 Pro] Gordietm:
Do we still need to flash the additional Powerhint magisk module with the kernel?
[Google Pixel 6 Pro] DanielF50:
No, not unless you're flashing manually - it's included in the flashable zip (1.4.0 and above).
[Google Pixel 6 Pro] Zach Alt:
Ok last question for me I think. If I flash this do will I have to remove it to flash to the next pixel update?
[Google Pixel 6 Pro] :
No just sideload it and you are good to go.
[Google Pixel 6 Pro] Lughnasadh:
Updating via fastboot flashing (e.g. flash-all.bat) the next update will remove the kernel. You actually don't want to keep the kernel when updating. For example, the 1.4 version was made for December. If you flashed it on the November build it wouldn't boot (and vice-versa I believe). So you could run into problems when updating if the kernel you are on is not compatible with the new firmware. It's always best to wait until the developer updates the kernel for that specific firmware.
[Google Pixel 6 Pro] Zach Alt:
Ok, that is good then, so when I update to the newest Pixel update this won't cause an issue, I will just have to reflash the kernel if I want to/when it's updated.
[Google Pixel 6 Pro] Lughnasadh:
Correct, if using fastboot to update.
[Google Pixel 6 Pro] Starzboy77:
So I haven't flashed a kernel yet on ny Pixel 6 pro. I'm rooted, on January patch and have disabled verity/verification as I have a launch unit. I have both FKM and EXKM. Been running stock kernel but my screen keeps freezing requiring a screen off and on so thinking of trying a kernel. Am I good to go to just flash the kernel in either EXKM or FKM or do I need to do something different? If I want to go back to stock, should I just make a backup of the kernel and reflash or is there a different method? Also, what is the proper way to update when a new OTA comes out if I'm on a custom kernel? Finally, would I need to disable Magisk modules before flashing the kernel? Thanks in advance.
[Google Pixel 6 Pro] lattosimbaste:
I flashed the latest with EXKM, no issues. I did back up the stock kernel first but I haven't tested restoring same. The OP instructions differ so I'll defer. I flash the full build without wiping rather than side load OTAs and re-root afterwards, I do disable all Magisk modules and flash kernel last but I'm just a creature of habit.
[Google Pixel 6 Pro] Burt Squirtz:
Be careful bro. Restoring stock might soft brick the device. Has happened to me more often than not with other kernels.
[Google Pixel 6 Pro] lattosimbaste:
Yeah, not something I mean to test anytime soon. The OP instructions should be used or just a full factory image reflash. There's been a few hoops to jump through for sure.
[Google Pixel 6 Pro] Texan1:
Just checking... is this what everyone's Android version etc now looks like after updating to Jan build and Kirisakura kernel?
[Google Pixel 6 Pro] foobar66:
Kernel working great on Jan build. Thanks !
[Google Pixel 6 Pro] Reechings:
Yep looks same as mine.
[Google Pixel 6 Pro] :
Because the boot.img is restored only.

And this kernel has some more images, that's why.
[Google Pixel 6 Pro] Reechings:
Is there any difference between the kernels available for Pixel 6 Pro as far as USB OTG file format support? Just tried my USB flash drive that I've used on my other phones no problem and of course the Pixel wants to format it. I'm guessing it's because it's exFAT? Any way to add support? Thanks
[Google Pixel 6 Pro] Lycidias:
So, today I flashed my first kernel on raven 😊

It's running great so far.

Any chance that we could get display calibration control?

And do the cleanslate apps interfere with other config apps like FKM?
[Google Pixel 6 Pro] Freak07:
Regarding the first question check:

https://xdaforums.com/t/kernel-15-0...pro-aka-raviole.4358435/page-23#post-86118161

And also this post:

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

Regarding the second question:

No, Cleanslate apps won't conflict with anything. :)
[Google Pixel 6 Pro] Lycidias:
Okay thanks, maybe I'll try this app :)

Something I noticed while using the flashlight call notification:

I'll don't get a missed call notification. So if I don't answer the call, I can't see that someone has called me until I open the google dialer app.

Edit: I don't even get missed call notification after reloading defaults and uninstalling cleanslate apps
[Google Pixel 6 Pro] Freak07:
It must be something else. The kernel and the apps have nothing to do with that, as @tbalden also confirmed to me just now.

I called myself a few times and I get a missed call notification each time.
[Google Pixel 6 Pro] tbalden:
Yeah, the Android framework doesn't give that kind of liberty for an app like the companion. Not sure why that happens tho. Any changes on your phone for notifications for the phone app/dnd mode filters recently?
[Google Pixel 6 Pro] Lycidias:
Missed calls not showing on Pixel 4a 5G - Google Pixel Community

I double checked the settings from the first post but all seems to be ok.

Then I tried:

Settings - system - advanced - reset options - reset app preferences.

This seems to be the fix. Seems to work now, thank you two 😊

Edit: it doesn't work everytime, I sometimes still get no missed call notification... Seems to be a Pixel Bug...
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're too kind! Happy to help.

While it would be great if support for ExFAT could be added, I finally bought exFAT/NTFS for USB by Paragon Software, which successfully makes it so I can use my ExFAT formatted MicroSD card through a USB-C adapter, using my file manager of choice, X-plore File Manager.

I use the flashlight call notification and I still got the missed call notification. As @Nimueh said, maybe this other dialer app below will be the answer for you until the Google Phone app starts working for you completely.

But I know we should continue the conversation about this, if needed, in your original question thread.
[Google Pixel 6 Pro] xflowy:
@Freak07 thanks for the great kernel!

after coming from despair kernel, i love the added smoothness. however despair kernel feels a bit more snappy and less "heavy". is there sth that can be done in that department? :)
[Google Pixel 6 Pro] Vio281:
does anyone have an idea what the powerhint module does?
[Google Pixel 6 Pro] Lughnasadh:
It's stated in the OP.
[Google Pixel 6 Pro] Vio281:
is that AK3 module?
[Google Pixel 6 Pro] danw_oz:
Awesome, thank you so much for the latest build, worked great flashing from EXKM . Was a rocky start with update versions confusion, just my dumb luck when I tried to root this phone for the first time :) , am now running this Kernel for the first time on my Pixel 6 Pro, so far it seems a lot more snappy
[Google Pixel 6 Pro] nummer:
mind a few questions? ive been looking at this kernel but the lack of a feature list is turning me off.

- how easy were you able to switch between kiri and despair?

- just how about any differences between kernels you've used in general <_>
[Google Pixel 6 Pro] scloutkst:
Guess you have trouble reading.
[Google Pixel 6 Pro] Lughnasadh:
Given the contents of the post they were responding to, pretty sure that person was talking about a lack of a feature list for the Despair kernel, not Kirisakura. But that person can correct me if I'm wrong.
[Google Pixel 6 Pro] scloutkst:
You could very well be correct. Seems my post was out of line.
[Google Pixel 6 Pro] scloutkst:
Apologies for my harsh reply previously. I didn't contribute anything.
[Google Pixel 6 Pro] danw_oz:
Don't know I re-read that post above and it still seems that he is saying this kernel has less feature set, oh well.

"mind a few questions? ive been looking at this kernel but the lack of a feature list is turning me off."

Anyways to answer your question it shouldn't be that hard to switch Kernels so long as you follow the guides exactly, should be easy enough to just dirty flash stock rom (flash-all without -w switch), then ROOT, then flash Kernel to swtich between them.

I have used other kernels in the past, then once this one came out for Pixel XL, I tried this kernel along with others, then the Pixel 3XL it had support for High brightness Mode, and fixed a heap of issues with that phone. So I went with this one and haven't looked back, no point or need to IMO
[Google Pixel 6 Pro] Freak07:
As far as I'm aware no.

Some phones with sdcard slots use a proprietary driver from tuxera for exfat. On those devices a open source exfat driver can be used to get exfat formatted cards going again.

Last time I tried to add the driver on pixels, i concluded the system just lacks support for exfat sdcards.

So the post suggesting you an external app might be your best option. :)

You're welcome. :cowboy:

Maybe something was running in the background, I'd give it a bit more time. :)

Also keep out an eye for future updates as there might be more improvements to the scheduler. But I'm always hesitant to translate changes like this to "real world" improvements. Just because a microbenchmark performs better in the range of fractions of a second or even milliseconds/microseconds.

For myself I concluded over the years, feelings can be deceiving. :)

The FAQ found in the second post contains instructions to restore stock kernel/conditions after flashing the kernel here.

The features of this kernel are pretty much detailed in the first post. The OP is more detailed and provides more links for further research than pretty much any other kernel pm XDA i know of. If you want more details check out GitHub, use Google if something is unclear or ask here after doing some research. :)

The features of despair kernel are no subject of this thread, but you can take a look at GitHub as it's advised on the despair thread.
[Google Pixel 6 Pro] Reechings:
Yeah I think I remember flash kernel trying to make exFAT work a few times and I think it ended up having to be supported by ROM.
[Google Pixel 6 Pro] xflowy:
hey man! thanks for the reply! i can confirm that there is nothing running in the background causing this. i just tested with despair again.. and its somehow snappier. any ideas what this could be?
[Google Pixel 6 Pro] Freak07:
no, everything is fine on my end.
[Google Pixel 6 Pro] Texan1:
[deleted!]
[Google Pixel 6 Pro] Freak07:
I´d appreciate if we could keep anything "drama", non XDA-related and other topics that are not at all related to the topic of this thread, out of here.

I´m not really interested in comparing my kernel versus "other kernels". I´m also not really interested in reading comparisons no matter the outcome of the comparison.

I´m doing all of this during my free time, because I enjoy doing it and share what I´m personally running with everyone here on XDA.

There needs to be no "rating" of those hours I spent working on my projects as they´re completely free of charge.

I assume the same is true for others that work on similar projects too.

If you appreciate the work, drop a thanks, write a few friendly lines, maybe consider a small donation, participate in the thread, report bugs in a proper manner if you encounter any, be friendly and helpful or contribute to the project here as all the source code is up on github.

Everyones usage differs, everyone has unique usage patterns. So just try what´s available and choose what suits you best and be glad there are options for this device.
[Google Pixel 6 Pro] xflowy:
I didnt say it wasnt fine. I just said, it could be snappier :) Did u try/compare the despair kernel?
[Google Pixel 6 Pro] rav101:
Please see Freak07's message directly above yours and you will have your answer to your question...
[Google Pixel 6 Pro] Nekromantik:
@xflowy Yes lets stop comparison on kernel devs thread.

if you want to compare feel free to create thread on general forum.
[Google Pixel 6 Pro] Lycidias:
Did a clean install of the January build and directly installed your kernel again.

Thanks, i really appreciate your work. 👍

Also I like the way of communication with your users.

Great kernel, smooth as hell and definitely better than stock. 😊

Gonna buy you a beer mate 🍻
[Google Pixel 6 Pro] izzyzz:
Is there a way to further limit the core frequency when the screen is off using the module?
[Google Pixel 6 Pro] Freak07:
Or even better: Don´t create a thread to compare ROMs/Kernels or other projects at all.

I don´t understand why there´s the urge to constantly compare projects as if there was some kind of competition. Use what suits you best and be happy it´s available.

That's what I'd prefer.

If one is not satisfied about what's available they might even start to get into starting a simple first project themselves.

The XDA I know from back in the days when I was just a user, when I was not contributing anything in form of a development project because I simply lacked any knowledge and was instead just a mostly lurking and learning user, had a few unspoken rules that included to not do exactly this. (create "comparison" threads)

Happy to hear. :) Thanks for the kind words and the beer.

Yes it could be reduced further, but the lower it gets the more likely it gets to territory once entered where issues like stuttering during music playback etc could occur.
[Google Pixel 6 Pro] Gordietm:
I tried flashing the kernel with EXKM and when rebooting, I get stuck when Google shows up. It doesn't make it to the G. Had to flash the factory image without wiping to get it to boot up. Also now, when I reboot a message comes up that the device is corrupted and to press enter to continue. It then boots up fine and rooted. Would a factory reset help?
[Google Pixel 6 Pro] bouchigo:
If you want to get rid of the "corrupted" message, then yes (I just re-installed the factory image with a wipe since I hadn't set up the phone yet after retruning from protonAOSP, and I had already wiped and backed up my phone). The same thing happened to me when I tried installing the kernel a few days ago when it was first released.

I haven't tried flashing it again through EXKM as I haven't really had time in case the same thing happens again.
[Google Pixel 6 Pro] Fields47:
Hey, thanks for the update. I just flashed 1.4.0 however I seem to have an issue with Bluetooth audio, I cant for the life of me to get audio to work on my car over bluetooth.

Could this be related to the Kernel or should I be looking at other possibilities?
[Google Pixel 6 Pro] izzyzz:
Oh i was asking because i dont play music and if it can be reduced lower to only need support for notifications
[Google Pixel 6 Pro] Freak07:
It could be related. Did you flash 1.4.0 on January or is that a typo?

1.4.0 was for December, 1.5.0 is for January.

I have a few Bluetooth devices (although no car that has Bluetooth) and all of those devices work fine on my end. Tried also pairing new devices.

You can try to reboot, make sure you're running the correct kernel for the correct firmware build and if that doesn't work try to restore stock kernel and see if that changes anything.

If it's related to anything I changed, i might need logs to do anything.

edit: I just googled bluetooth issues on cars with the pixel 6, there seem to be a lot of complaints too.

I can't decrease it for everyone as that won't work.

If you're interested how to change it yourself pm me, I'll write you a short explanation.
[Google Pixel 6 Pro] omvir:
Thank you for your kernel.

I no longer need to install the p6 powerhint module along with the kernel zip (1.5.0) as it now comes bundled already with the flashable zip. Correct?
[Google Pixel 6 Pro] Freak07:
Correct (y)
[Google Pixel 6 Pro] danw_oz:
On Jan build with latest canary build of Magisk, flashed powerhint in Magisk first, then flashed 1.5.0 with EXKM no problem.
[Google Pixel 6 Pro] rav101:
Just a heads up that you don't need to flash the powerhint module anymore as it comes bundled in the Zip and will automatically be installed when flashing in EXKM. The name is different now (it's called "AK3 Helper Module".

Remove the old powerhint module if you still have it installed.
[Google Pixel 6 Pro] bouchigo:
I just flashed the 1.5.0 zip again and everything went fine.

I don't know what caused it to boot loop the last time I flashed it.
[Google Pixel 6 Pro] danw_oz:
Ok thanks for the heads up, was being super careful this time, and had read it was a requirement. Will remove it and flash kernel again
[Google Pixel 6 Pro] a63548:
@Freak07 Can't thank you enough for such an amazing kernel! Originally bought a OnePlus 7 Pro as I was so intrigued by your kernel, and am so excited that you are developing for the Pixel 6 Pro. Greatly appreciate all of the detail and information you put into all of your posts and changelogs :) Thank you for everything you do!
[Google Pixel 6 Pro] Freak07:
Thanks for the report. Maybe there´s a flag in the ak3 kernel.zip I´m missing.

I flashed numerous test builds and didn´t run into any issue so far. It´s always tedious to debug or tackle issues one doesn´t run into. I´ll take a look for the next release if that flags potentially might solve this issue.

Where did you read that it was a requirement?

I adjusted the flashing guide in the first post for flashing the kernel.zip, but it would be nice to know if I missed a reference somewhere.

Glad to hear :) Enjoy the ride!
[Google Pixel 6 Pro] Nekromantik:
Yes I agree.
[Google Pixel 6 Pro] Nightf0x_007:
Updated my pixel 6 to january update and flashed kirisaukra 1.5.0 via fkm my device bootlooped and now getting when rebooting a warning my device is corrupted before the bootloader unlocked warning
[Google Pixel 6 Pro] Gordietm:
Same thing happened to me.
[Google Pixel 6 Pro] Freak07:
So it seems it´s not related to the app you both used for flashing. @Gordietm used exkm, while @Nightf0x_007 used fkm.

Since it seems the majority of people have no issues flashing the kernel.zip, me included, there must be something that triggers an issue.

Are you 100% sure that you came from a clean stock firmware rooted with 23016 magisk canary, where you extracted the january boot.img yourself from the firmware you previously flashed, patched it yourself with magisk canary 23016 and flashed it successfully via fastboot?

Did you flash any other kernel before? Was there anything strange when updating? Did you update to January firmware with vbmeta verity flags disabled or left them enabled?

a few posts above another user, seemed to have a similar problem, which wasn´t reproducible and fixed on a second attempt:

https://xdaforums.com/t/kernel-15-0...pixel-6-pro-aka-raviole.4358435/post-86274977
[Google Pixel 6 Pro] Gordietm:
I wasn't previously rooted and since it's not necessary anymore disable vbmeta, I just flashed the kernel zip.
[Google Pixel 6 Pro] Freak07:
how did you flash the kernel.zip if you weren´t rooted?
[Google Pixel 6 Pro] Gordietm:
I meant to say, it was the first time rooting. I previously patched the boot image, fastboot booted the patched boot image and then did a direct install with magisk before flashing the kernel zip
[Google Pixel 6 Pro] Nightf0x_007:
I was rooted on dec. Update with kernel v.1.40, i remember before going from nov. To dec. I disabled both dm verity & verification (i flashed dec. Update via android flash tool website), thats it all, i feel something went wrong in my device

This is how i updated to dec.

-Executed flash-all flashed bootloader & radio but didnt want to update the device

- fastboot update the image

- fastboot boot magisk patched image

- opened magisk and directly installed magisk
[Google Pixel 6 Pro] Nightf0x_007:
Is there a way to check dm verity and dm verification status?
[Google Pixel 6 Pro] Freak07:
Alright. If you want to try again send me a pm, I'll send you an updated anykernel.zip so we can check if that changes anything for you.

I guess you could try flashing the factory image with -w flag removed and see if that changes anything on the new zip.

did you try "fastboot getvar all" in bootloader?
[Google Pixel 6 Pro] Nightf0x_007:
Yes i was flashing the update with -w removed but it wont reboot to fastbootd to continue the update, so i extracted the update image and did fastboot update image.zip and updsted this way, Will try the getvar and report back
[Google Pixel 6 Pro] Nightf0x_007:
About the corrupted device warning is it normal? Since jan. Update or did i made something wrong which made it appear
[Google Pixel 6 Pro] Gordietm:
It's not normal.
[Google Pixel 6 Pro] Gordietm:
@Freak07 I flashed the new zip you sent me and the same thing happened. It reboots to "Google" and just stays there. I had the flash the factory image again to get it to reboot and reinstall magisk. I'm going to try uninstalling root and use the Google flash tool to try and get rid of the corrupt message. Then go through setup process and reroot
[Google Pixel 6 Pro] Freak07:
It might need a complete wipe as I don´t think the new zip will fix whatever is wrong currently. There might be a chance it might not make the bug appear though, if the underlying issue is not present on a clean installation.

I don´t know what went wrong in the first place or why. I´m sorry some of your are facing this issue, but it seems to happen in the other kernel threads as well.

If that new zip doesn´t help, I´m afraid I can´t offer any more help. I updated to January via the factory image, rooted and everything went smoothly.

I flashed the kernel.zip probably well over a few hundred times and never faced any issue.
[Google Pixel 6 Pro] Gordietm:
It must have something to do with the corrupt files I have. Is the anyway to find out what's corrupted and fix it without having to completely wipe my phone? My phone works fine except for this message I get whenever I reboot and I can't seem to be able to use a custom kernel.
[Google Pixel 6 Pro] Freak07:
I guess there are no corrupt files. It's probably related to verity and something is screwed up there, which throws up this corrupt warning.

But I don't know why you're seeing it or what's wrong that you're seeing it or what's caused it.

It might be a random issue that's caused by something we haven't yet identified. Maybe patching via magisk has something to do with it, maybe outdated platform tools, maybe some special order of things, maybe your device switched slots (don't know if you remember which slot you initially started from) . I really don't know.
[Google Pixel 6 Pro] bouchigo:
It could very well be related to verity. When I first returned from protonAOSP to stock January update I did not disable verity (just wiped and updated to January) and that's when I had the issue.

When I wiped and installed the January update for the second time I disabled verity and everything went fine last evening when I finally got around to flashing 1.5.0.