yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
I adjusted the FAQ to better reflect this behavior now and hopefully prevent confusion about this, but I think it still can get confusing for inexperienced users.

The easiest solution is to dirty flash firmware as that includes vbmeta.img anyway. If a user disabled the verity/verification flags, they need to pass those flags during the dirty flash of the firmware package to keep them disabled.

If anyone reading this thread has a suggestion on how to improve the FAQ I´m always happy to hear it.
[Google Pixel 6 Pro] reddvilzz:
I've managed to fix it by using Android Flash Tool, before I thought my device is not detected by the Android Flash Tool because I haven't add the device.

Thank you for the help!
[Google Pixel 6 Pro] Freak07:
Flash tool to the rescue :cool:

Great to hear it's fixed, thanks for reporting back.
[Google Pixel 6 Pro] Sigray:
Is this kernel still for A12 only?
[Google Pixel 6 Pro] Freak07:
Read the thread title and check the OP. :) You'll find download links.

That will clear it up for you.
[Google Pixel 6 Pro] Lughnasadh:
Not really a suggestion on how to improve the FAQ, but it seems if people really want to avoid the corruption error/message (which happens in a variety of situations, not just related to flashing kernels), then keeping verity/verification disabled may be the best way to go about it. Not sure if I've seen anyone (including myself) get the corruption message when they have these disabled, but I could be mistaken.

Disabling verity alone (which does not require a wipe) may also do the trick.
[Google Pixel 6 Pro] scloutkst:
To be clear I'm not complaining at all. Just leaving an informative post. For those wondering if the kernel will work properly on the latest beta.

Latest kernel will install and boot on latest 13 beta qpr. However performance is not good. Also breaks whatever changes have been made in the new modem firmware. As my phone will no longer connect properly to my cell spot and fallback to LTE. That being said the new modem firmware very good in the beta.
[Google Pixel 6 Pro] bleez99:
How much improvement is there in the modem firmware? I really don't have much to complain about given some of the horror stories I've heard. I know it can be better, for example I'm on T-Mobile and in a really good spot I get 5G UC which is unbelievably fast. At home I just see it toggle back and forth from UC to regular. Wish the sensitivity was a bit better. It's in my neighborhood and if I drive a few blocks away it's great for a distance then I drop my music stream here and there. Sketchy but I can always make calls. It is a phone after all. Sorry for the off topic just curious.
[Google Pixel 6 Pro] Utini:
Flashed newest A13 update and newest Kernel but I got some "errors" in the logs.

Hope this is all fine? Device booted up correctly.

Log from Android update:

Kernel flash log is attached as screenshot (couldn't copy the output?).
[Google Pixel 6 Pro] ArmashOnXDA:
Dam
[Google Pixel 6 Pro] Freak07:
looks fine :)

If you want give kernel-flasher from capntrips, that makes it easy for you to save the log file after a flash.
[Google Pixel 6 Pro] Utini:
Thanks again, will probably flash today/tomorrow.

Regarding Cleanslate Features:

I used those features with your kernel on the P4XL but I am not sure that there is anything for the P6P I would benefit from? Is there anything you use personally?

E.g. HBM is probably not needed on the P6P, no discoloration on battery saver as well, etc etc :)

Thanks!
[Google Pixel 6 Pro] Freak07:
I use sweep to sleep all the time :)

The battery saver feature from cleanslate is also very useful for me, when I use navigation or sports tracking apps to just have a powersave mode that purely restricts cpufreqs when I want it, without any other stuff like background app usage, gps, location or similar restricted. (as that is what the standard powersaver in the firmware does)
[Google Pixel 6 Pro] Utini:
Ye the powersaver feature is the only thing I could imagine being helpful for me.

Why not have the powersaver firmware in your kernel setup for it? :)
[Google Pixel 6 Pro] Freak07:
I don't understand what you mean.

The CleanSlate batterysaver is part of the kernel now. You can activate it simply via the CleanSlate config app. There's no need to setup anything.

The batterysaver that's already included in the ROM doesn't have anything to do with the kernel really. Its functions can't be altered via kernel as it's handled in the framework.
[Google Pixel 6 Pro] Utini:
I meant / suggested: Why not configure the kernel out-of-the-box with the battersaver configuration? So that one doesn't need the CleanSlate config app anymore to configure and activate it?
[Google Pixel 6 Pro] Freak07:
I don't want to restrict max cpufreqs when I use my device outside of navigation/sports tracking sessions.

I enable the powersaver when I need it and then disable it.

The kernel can't know which app you're running or what you do each moment with your device. So it's not automated.
[Google Pixel 6 Pro] Utini:
Ohhhh okay! Thanks for the clarification.
[Google Pixel 6 Pro] Nekromantik:
Yeah main ones I was talking about were the 2 WLAN wakelocks.
[Google Pixel 6 Pro] Jhoopes517:
Probably vbmeta not being disabled. I don't know why I didn't think of that.

Thank you! Will try later.

Also, is root required? I didn't want root so had no plans to patch.
[Google Pixel 6 Pro] xflowy:
If I wanna be safe and flash vendor_boot.img, how and when in the kernel update process would I do this? Whats the command again? Thank you!
[Google Pixel 6 Pro] Burt Squirtz:
Fastboot flash vendor_boot vendor_boot.img
[Google Pixel 6 Pro] xflowy:
thanks. and when do i do this in the update process?
[Google Pixel 6 Pro] Freak07:
yeah those are already removed.

I´ll include the wakelock blocking driver in the next release. Maybe it helps somebody. Though I always fear it can be abused too easily, which will result in random breakage.

It should only be used in scenarios, like at work where you´re device has a never-ending wakelock due to a certain wifi router/firmware combination and the IT admin says screw you. It should never be used to get better idle battery life.

not strictly. the powerhal module requires magisk to be present, but as this point it´s optional.

cleanslate features can be controlled without root, that´s the point of them.

But since the rest is basically flash and forget about it, you´re fine without root.

it doesn´t really matter at this point :)

probably best to just boot to fastboot if you want to restore, then flash the three imgs there, (boot, dtbo and stock vendor_boot) then to fastbootd (since fastbootd kinda sits in vendor_boot, so you´re sure to have restored stock there earlier) and flash vendor_dlkm in fastbootd.
[Google Pixel 6 Pro] john-aurelio:
If I am not mistaken, I think the memory is less optimized because I will have the games and it restarts again.
[Google Pixel 6 Pro] flyl0:
Thank you for the hard work, really appreciated
[Google Pixel 6 Pro] john-aurelio:
To you for great work with the kernel my battery is more than 50% better
[Google Pixel 6 Pro] ansh1996:
Hi there. I just tried the kernel on the latest stock OTA (.037). The device boots okay however i am facing an issue with the screen refresh rate. A few minutes after booting the refresh rate gets stuck at 60hz. It does not come back unless after reboot but only for a few minutes. Has anyone else experienced the same issue? It definitely was not there for me before flashing the kernel.

I am rooted with just riru and LSposed and safetynet fix modules installed.
[Google Pixel 6 Pro] Freak07:
I had exactly the same bug happening on the day I received the device a few hours after setting my phone up. I was full stock at that time. Reboot, 120hz after two or three minutes it dropped to 60hz and would never go to 120hz.

The only thing that helped was to wipe the device unfortunately. I concluded it was due to google backup restoring something it shouldn´t from my previous device, as I didn´t use the restore option when setting up again and the bug hasn´t happened since.

There´s another bug that was described in that forum too, where refresh rate gets stuck at 60fps randomly on stock kernel as well. But on that occassion a reboot helps. I ran into that issue a few times as well. 3 or 4 times. I think 2 times on stock firmware, before I built the first build here.

I´m sorry it happened, but it´s not a kernel issue.

If you want you can send dmesg and logcat, but I didn´t find anything in the logs when I checked mine either.
[Google Pixel 6 Pro] ansh1996:
See next post
[Google Pixel 6 Pro] ansh1996:
I can confirm i have the same problem now after reverting back to stock kernel as well. I will try flashing stock boot img to see maybe not being rooted helps or not. If that doesn't work i might just have to wipe. :(

The weird thing is that i did not have this problem up until I flashed the kernel. Maybe thats something worth looking into..
[Google Pixel 6 Pro] Ghisy:
Hey @Freak07, someone mentioned in the QPR beta thread that the new radio doesnt't work well on stable 13 with your kernel. Have you tried? I thought the kernel had nothing to do with the radio itself?
[Google Pixel 6 Pro] Freak07:
can you point me to the post? :)

No I haven´t tried. Creating frankenstein firmware configurations is not something I´d recommend. I know some people seem to have troubles with mobile network and flashing radio from more recent firmwares supposedly helps or helped them, but the firmware that´s running on the device should always match.

Generally the kernel should match the rest firmware on the device as those interfaces need to match and need to be compatible. This time the kernel compiled for stable a13 seems to be able to boot the beta, but just because it´s booting doesn´t mean it´s made for the beta.

For example this change: https://android.googlesource.com/ke...oc/+/a3b7f6fd2c93261c171a7a70015bcfc4661be8b0

This needs an updated aoc.bin firmware, as well as several other files on /vendor. If those are not present, this feature will cause problems like crashes or simply just don´t work (probably the better case).

Same goes for the radio, there´s firmware on the device that should match the radio that comes with the firmware. Those are not just interchangeable, even if there are improvements for some in certain configurations there might be regressions they don´t notice or just don´t affect their usecase.

That makes it unpredictable what might or might not be happening if frankenstein configurations are used. Especially with just saying it doesn´t work well. :)
[Google Pixel 6 Pro] Ghisy:
Thanks for the explanation!

Hmm, I can't seem to find this particular post... Will post a link if I do, sorry! But I know it mentioned Kiri kernel with the newest radio from QPR beta 1.
[Google Pixel 6 Pro] roirraW "edor" ehT:
You mean the one in this thread on the last page?

Can we please keep completely off-topic posts out of this custom kernel thread? Not trying to drum up traffic in my own thread - there's enough, but my own Android 13 QPR1 Beta 1 thread is a more appropriate place for talking about things unrelated to this custom kernel.

If needed, you can always click the Quote button at the bottom left of someone's post in this thread, then go to my thread and in a new post, click "Insert Quotes", so you can quote the user, therefore tagging them (or just use @username instead of quoting).

https://xdaforums.com/t/android-13-...n-ota-zip-or-full-firmware-image-zip.4380119/
[Google Pixel 6 Pro] Ghisy:
Nope, it was about the combination of the newest radio from the QPR beta and Kiri kernel on 13 stable.
[Google Pixel 6 Pro] sensui123:
So I'd like to think I have a decent understanding with custom roms, recovery, adb/fastboot processes etc. But something is baffling to me and I'm not sure why things eventually worked out.

I was having seriously bad battery drain with Android 13 that I started to notice at the last build of 12 so I decided on a fresh wiped install (not using any backup, manually adding back apps one by one after wipe). Things were better but still not great so I tried this kernel (my first custom kernel on this phone....6pro/Raven) and it made a decent difference so I expected to use this kernel moving forward.

This September update came and because I have a custom kernel, I knew my usual way of updating wouldn't be sufficient with the bootloader files changed (I usually use the OTA via sideload in recovery and then patch the boot.img using magisk to flash in the bootloader after the initial restart). So I proceeded to use the full flash-all script on the full image removing the -w flag to make sure I reflash all the kernel files back to stock first before reflashing Kiri. After I did this, I got the corrupt device message and then proceeds to bootloop with the Google logo. I tried to use the online Android tool but it couldn't detect my device in the bootloader.... Probably a driver thing.... So I tried the whole flashing a past boot.img thing to let it attempt boot and then the current boot.img thing. It seemed to temporarily work as I got rid of the corrupt message but I still was in a bootloop. The weird thing is reflashed the full image using the flash-all script again and I got the corrupt device screen back..... Then I thought maybe it's a slot issue of some kind so just in case I reflashed again using flash-all and now all is good with root and kiri after repatching and flashing Kiri again.

So I want to ask, was this some sort of fluke or is the way I'm updating with this kernel installed isn't right in some way? Also can anyone explain why the bootloop/corrupt message went away with me seemingly doing the same thing? Doesn't seem to make much sense to me. Thanks.
[Google Pixel 6 Pro] Freak07:
As long as you flash the full OTA zip via sideload in recovery and not an incremental one you shouldn´t have problems updating "your usual" way while having the kernel flashed, as the full OTA zip just flashes everything.

You can´t use the OTA option on the device or flash incremental OTA zips as long as any partitions are altered (being rooted changes boot.img, having the kernel installed changes even more partitions).

So I see no problem using your usual method of updating going forward.

If you just run the flash-all script slots shouldn´t get switched. Using sideload in recovery for full OTA zip your slots will get switched.

I think it´s a bug around verity on googles end, that just happens unfortunately. Nothing you´ve done wrong from what I can tell, but something you did triggered it to resolve itself. Since that issue started to show up it didn´t make much sense to me. It happened to users without having a custom kernel flashed as well.

Same as suggested in this post: I have kept verity/verification flags disabled since I got the device as I need to flash a lot of images and don´t want to rely on avb patching. I haven´t seen that issue once on my end.

Of course if going that route and disabling both flags it will initially wipe the device, following that you need to disable the flags every month you install a full firmware, which contains a vbmeta.img.
[Google Pixel 6 Pro] sensui123:
Thanks for the thorough response. I didn't know sideloading the OTA via recovery also replaces all the parts the custom kernel encompasses. I will try that on the next round vs the flash-all method to see where it lands me. Keep up the great work on the kernel and appreciate you confirming there isn't any special prep updating month to month with a custom kernel.
[Google Pixel 6 Pro] hanschke:
QP1 ist available. Good Idea to use your kernel?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Read this same page of posts, or at least Control-F (Find), and search for QPR.

FYI, QPR1 is in Beta, it's not Final until December.
[Google Pixel 6 Pro] hanschke:
I have read it. Dont you think I dont search before I ask?
[Google Pixel 6 Pro] scloutkst:
If you had managed to read what I posted, and what the developer posted as a reply to someone else. No it is not a good idea to use this kernel in the beta. It's not built with the beta in mind. It is not compatible. It boots but performance is bad and things are broken with the radio/modem.
[Google Pixel 6 Pro] Az Biker:
@Freak07

Just flashed the latest A13 via EXKM and it was seamless, as usual!

THANK YOU VERY MUCH for your had work, and for supporting users here.

Mad respect for all you do.
[Google Pixel 6 Pro] Freak07:
Kernel is compiled for stable. Please read back a few posts.

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

https://xdaforums.com/t/kernel-06-0...pixel-6-pro-aka-raviole.4358435/post-87411589
[Google Pixel 6 Pro] Freak07:
Thank you for the kind words. It's really appreciated!
[Google Pixel 6 Pro] Poesini:
Hey @Freak07 , I am currently testing MVK and it really helps a lot with the undervolting that he did on his kernel to mitigate the heat problems (at least on my phone) and while I cannot prove that there is better battery on the kernel, for sure having less heat on the battery will help longevity

I don't know if you could implement this on this kernel? Or maybe it is prone to errors/crashes/reboots? So far I have not experienced any
[Google Pixel 6 Pro] Freak07:
Yeah as you suggested it's not something I'm interested in. Undervolting causes unexpected and random instability. It's also dependant on the binning, but i don't want to introduce that kind of instability. No undervolting on this kernel. :)
[Google Pixel 6 Pro] 隆巴拿拿:
Hi!I'm a user of this kernel since ver.3.0.

This kernel wroks good on my smartphone but I'm concerned about the stability after updating to A13

Tips from a Chinese forum(translate by google)：

(Android 13 Pixel6/6Pro)Don't flash third-party kernels. At present, many users have been recruited. The symptom is that the kernel stability problem causes intermittent cycle reboot. At this time, it may not be repaired by re-flashing the official system, because some content of the error report activates the system protection mechanism, which is different from system damage. It is used by Google as an anti-cracking method (some technology companies will try to analyze Google's algorithm, which may not be accessible to you, but many of the black bricks I have come into contact with involve to the staff in this area).

No offence,I just want to know if this issue is solved in the kernel.
[Google Pixel 6 Pro] Freak07:
The anti rollback protection is unrelated to the kernel, but can happen due to any mods flashed that cause the device to be not able to boot properly.

There's an anti rollback protection in android 13, as your translated snippet points out.

If the anti rollback protection is triggered and you have A13 on your current slot while having A12 on the other slot and the phone tries booting in your other slot with A12 you end up bricked.

The phone can try to boot a different slot for a variety of reasons. If you're in a bootloop due to flashing a magisk module, an incompatible kernel or modifiyng anything else that breaks the phone to boot it might attempt to switch into the other slot after several failed attempts to boot.

If you update your phone to A13 on both slots this issue won't happen. So make sure you're running A13 (not the betas before the official release) on both slots.

You can find more information about the anti rollback protection reading the pinned thread here:

https://xdaforums.com/t/warning-read-this-before-you-upgrade-to-android-13-stable.4482091/
[Google Pixel 6 Pro] boxemall:
Got a silly question. I just installed Kirisakura_Oriole-3.0.17_A12_stable yesterday (I'm still on protonAOSP which is still on A12) and have no root. Magisk App is installed but says magisk is not installed. Was magisk removed or did i mess it up somehow? Now I'm off not wanting to reflash the whole rom. Is there anything I can do? Kernel is installed just fine and threw no errors. Everything works except some apps like PayPal are crapping out on me...
[Google Pixel 6 Pro] roirraW "edor" ehT:
Previous to installing Kirisakura_Oriole-3.0.17_A12_stable, were you using the stock ProtonAOSP kernel?

Did you have the ProtonAOSP kernel rooted with Magisk before installing Kirisakura_Oriole-3.0.17_A12_stable?

What did you install Kirisakura_Oriole-3.0.17_A12_stable with?

I normally only install Kirisakura over top of the stock kernel that I've already rooted, but you might be able to get a copy of the ProtonAOSP kernel moved over to your phone's internal storage, root that boot.img with the Magisk app, copy it back over to your computer and then:

adb reboot bootloader
fastboot boot Magisk'dBoot.img

Then once your phone has booted into that rooted ProtonAOSP kernel, run the Magisk app and choose Direct Install, which should root the Kirisakura kernel. I don't ever do it this way so your mileage may vary, but I know that Kirisakura is designed to detect whether the kernel you already have installed is rooted or not, and will apply root to the Kirisakura kernel when you install it, as appropriate.

I don't have any experience with ProtonAOSP either.

Good luck!

Edit: This kernel would have nothing to do with how well PayPal works. It's working fine on my Pixel 6 Pro running stock rooted.
[Google Pixel 6 Pro] Freak07:
There's no way to flash the zip without root as we have no working TWRP as far as i know :)

Flashing the zip detects magisk and keeps it preserved like @roirraW "edor" ehT said.

Sounds to me like the magisk app might be messed up. Have you tried clearing cache and data for the magisk app followed by a reboot? Or uninstalling/ reinstalling just the magisk app followed by a reboot helps maybe.

If that's not working flash the images to get back to stock (in your case extract those from the firmware of the custom ROM) as described in the FAQ. If you want root, flash the magisk patched boot.img of the custom ROM you're on.
[Google Pixel 6 Pro] shag_on_e:
4.1.6 is running great for me so far at max frequencies. I don't have any battery info as I just use this phone for gaming and tinkering, but I can damn sure say it's fast. Everything feels extremely responsive and I've had no weird issues. Though I'm worried I need to flash 13 to the other slot before something for happen!
[Google Pixel 6 Pro] boxemall:
Guys you were both right. i have to admit i shat myself. somehow i did forget to root the kernel before flashing kiri. guess i shouldn't do things on a hurry. it's all good now but i had to reflash proton then redo all steps. my bad sry to have bothered you!

one more question: saw a post about A13 introducing some kind of hardware count making it hard to switch back. my question is if A12 is still being worked on and will there be updates to kiri or is it only A13 from now on?

regards
[Google Pixel 6 Pro] Freak07:
No need to apologize, thanks for reporting back here!

Only the A13 kernel will be updated from now on, the A12 kernel is "finished". There´s also a simple reason for this, even if there would be no anti rollback protection, I can´t work on two versions simultanously, as I don´t have the time or motivation to switch between the different android versions for testing.

I hope you understand where I´m coming from here.
[Google Pixel 6 Pro] boxemall:
All good. i can totally understand your point. i just have to rethink what to do now. maybe i'll have to go back to stock kernel. not sure yet.

tx!
[Google Pixel 6 Pro] Freak07:
No problem :) it's your choice what to do.

If looking at the latest A12 kernel release here from a Linux-stable upstream, kernel-common upstream, f2fs etc perspective, you have to keep in mind the last A12 release here is still ahead by a lot of the stock A13 kernel at the moment. While the latest A12 kernel is also based on the A13 kernel base minus a few incompatible changes that require firmware, which A12 doesn't have. :)