yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Oswald Boelcke:
Moderator Announcement

As requested by the OP @Freak07 I've cleaned his thread from off-topic posts but also posts in reply to them. I'm convinced the affected members will know and notice.

This is a development thread regarding a very specific kernel but not a Q&A or general discussion thread about e.g. advantages or disadvantages of custem kernel versus stock kernel. In this thread please limit your posts and sharing of experiences and knowledge to the use of exactly this specific kernel including bugs. In this context, please refer to post no. 2 how to report bugs properly.

I've now subscribed to this thread. And I'd appreciate if everybody reads this PSA as a friendly warning that any further report by @Freak07 about off-topic posts in his thread might lead to more severe consequences to the author's account pending on the specific evaluation. In minor cases it might only read to a reply ban for the respective owner - temporarily of permanently - i.e. the affected member will always be able to access this thread and to read it but be unable to post or to reply here during the reply ban time. I'm convinced the indicated measures are in the interest of all of our members. Thanks very much for listening to me, for your understanding and your future cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Google Pixel 6 Pro] xflowy:
cant find the new kernel to download in the linked folder :l
[Google Pixel 6 Pro] TotallyAnxious:
It's attached above your post....
[Google Pixel 6 Pro] xflowy:
above my post? im probably blind then.. couldnt find it in the normal download folder. saw it attached to the release post then. dont understand why its that way tbh
[Google Pixel 6 Pro] capntrips:
From the release post:
[Google Pixel 6 Pro] Ghisy:
@Freak07, slightly OT but will you be getting the 7 Pro? And/or developing your wonderful kernel for it?
[Google Pixel 6 Pro] xflowy:
wondering this too. kinda making my decision to buy or not buy it depending on his decision..
[Google Pixel 6 Pro] GAKP:
Will it work at some point with pixel 6a? My phone is so hot that I can't use it :(
[Google Pixel 6 Pro] evanxyj:
;)wander will it work on october feature drop 2 build?
[Google Pixel 6 Pro] bobbarker2:
Anyone having trouble with haptic feedback? I've always felt it was a little bit light on this phone but now I'm having problems where it doesn't vibrate at all to the touch or any other action that would trigger it. Phone calls vibrate.

Been through the system settings and app settings to make sure nothing got messed up when updated to October.
[Google Pixel 6 Pro] Freak07:
Vibration is working fine here. Doesn't sound like a kernel issue. If it was the phone wouldn't vibrate at all and it would be completely broken most likely.

As to what's the exact cause for your vibration issue is, no idea. I guess you tried a reboot already?

You're on a13 stable, not qpr beta?

Regarding vibration strength: There's a setting in CleanSlate config app to increase the intensity called vibration power override.
[Google Pixel 6 Pro] bobbarker2:
Yeah tried reboot, all the usual stuff. It's weird, if I adjust it in system settings it will work for a few seconds and then go away again. Phone vibrates when I get a call, so not a hardware defect. Maybe just a system bug, I went from August to Oct. without flashing September but that has seems unlikely. 🤷

I didn't see if it was the same on stock kernel though, I guess that's the real test.

Thank you for all the time and effort you put in to this! I've always loved your kernels.
[Google Pixel 6 Pro] Poesini:
I'm on latest RiceDroid as of today and when I try to flash the 4.2.0 kernel (with EXKM and/or Kernel Flasher), when I reboot, I get no root... Do you guys know why is this happening?

I'm on Magisk 25204
[Google Pixel 6 Pro] w_tapper:
maybe flash magisk again
[Google Pixel 6 Pro] Poesini:
Can't flash Magisk because I lost root... I have to reflash back to stock/magisk-patched
[Google Pixel 6 Pro] w_tapper:
oh nvm im stupid
[Google Pixel 6 Pro] miqcea3:
i would like to install this on derpfest 13, but i also lose root if i do so and cannot flash magisk in recovery.

maybe the problem is the preinstalled radioactive in derp.

i flashed it with exkm, with this i lost root and did get stock recovery (instead derp) where i could not sideload magisk

someone knows how to do it? =)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Since DerpFest isn't stock Pixel firmware, it wouldn't surprise me if this kernel just won't work with it correctly.
[Google Pixel 6 Pro] Freak07:
Can you share a log of the flash?

Kernel flasher app allows to take a log after the flash. FKM does too iirc.
[Google Pixel 6 Pro] miqcea3:
This one? Thank you for lookimg into it :)
[Google Pixel 6 Pro] Poesini:
Will try to next time because 7.0 was pushed yesterday and as of right now, I can't even flash Magisk on stock boot.img nor of course install 4.2.0
[Google Pixel 6 Pro] miqcea3:
I flashed rom again and the sideloaded magisk without problem. Guess works for you aswell.
[Google Pixel 6 Pro] Poesini:
RiceDroid 7.0? Which Magisk version are you on?

I renamed the Canary APK to .zip and sideloaded it and it bootloops
[Google Pixel 6 Pro] miqcea3:
No derpfest 13, but should be the same. I use magisk 25.2, you can sideload the apk and don't have to rename. Guess we should stop now with OT.
[Google Pixel 6 Pro] Poesini:
I fixed it, thanks to @miqcea3 (I flashed 25.2 and then upated to 25204)... But now I still can't keep root after flashing...

Attached is the log
[Google Pixel 6 Pro] slickrasta:
Stuck in bootloop for a third time in recent months after flashing kernel via KernelFlasher.
[Google Pixel 6 Pro] capntrips:
I don't know enough about custom roms to even be able to speculate. A dmesg and logcat (and ramoops, if present) from the initial boot might be helpful. Also the untouched and patched boot images.

AK3 does have a ramdisk_compression property, so it might be worth testing with gzip or lz4, rather than auto. I have no idea if lz4 ramdisk compression in AK3 is the same thing as the lz4_lg ramdisk format from the logs. It's also interesting that the kernel and ramdisk formats are different for the custom rom but the same for the stock one.

I would think if the compression was the issue, the device would completely fail to boot, unless the device is rolling back to the previous slot or magiskboot is completely failing to apply the patch. In the latter case I would expect to see some errors in the logs. It might be worth verifying that AK3 is repacking the image with the right kernel and ramdisk.

It might also be worth trying with Magisk 25.2 stable and 25205 canary, in case there were any related regressions or fixes.
[Google Pixel 6 Pro] Freak07:
yes, I´m not familiar with the custom roms either. I made sure to test 25205 and flashing a kernel.zip preserves root just fine on my end on stock rom.

I can´t test myself on custom roms, as I don´t have the time to wipe and setup my device freshly.

So @Poesini and @miqcea3 or anyone else on custom roms: If the maintainer of your custom rom is open to it, maybe ask for help if you don´t know how to obtain the things @capntrips asked you for. Some don´t like to support 3rd party mods, so there´s that too.

I´m not sure if it´s possible to obtain a dmesg without root, but maybe iirc correctly taking a full bugreport might include it. Don´t know if custom roms include this possibility or not.
[Google Pixel 6 Pro] Poesini:
@capntrips (didn't know if I could tag you, but here it is) and @Freak07

Here are the attached files (couldn't get dmesg or ramoops)

If it can't be done, I will ask on the Rice thread @alvin14

EDIT: Using Magisk 25205 Canary
[Google Pixel 6 Pro] capntrips:
Both dmesg and ramoops are in the bugreport zip, but I'm not seeing any of the issues I know how to pick out. Was this on the first boot after flashing the kernel?

Also, any chance you can grab the patched boot image? Since you're already using Kernel Flasher, the simplest way would be to make a backup after flashing the kernel but before rebooting. You can grab the image from the backup folder in /sdcard/KernelFlasher.

I know just enough about what Magisk does at boot to realize how little I know, so it might be worth submitting a bug report to Magisk including the bugreport zip. Edit: or maybe post it in the support thread here.
[Google Pixel 6 Pro] Sergey_Maslo:
Hello. Does this core have support for maximum brightness mode?

Also wanted to ask, is there support for fast charging throughout the process?
[Google Pixel 6 Pro] Sergey_Maslo:
And in general, it saves charge much better than the stock core from A13?
[Google Pixel 6 Pro] Freak07:
High brightness mode gets triggered automatically in sunlight or bright lightning conditions.

Alternatively you can trigger high brightness mode manually via a sysfs command or apps such as EXKM or others which names I don´t recall.

Charging behaves the same as on stock. No changes to charging as it can potentially damage devices.

Read the first post to get an idea of the features this kernel offers.

If you´re purely after battery life and expect "magic" improvements by flashing, that probably will not be the case.

There´s a battery saver mode accessible via CleanSlate config app after flashing, that restricts max cpu to 3 pre-defined levels. That will save battery for sure.
[Google Pixel 6 Pro] xflowy:
since high brightness mode is supported (right?), can someone tell me how many nits the 6 pro reaches with it? :)
[Google Pixel 6 Pro] Poesini:
All right

Attached is backed up boot.img (and I don't know if its worth something, but also ramoops, dmesg and logcat)

EDIT: I tried Magisking the backed up boot.img (and flashing it) before rebooting and still no luck
[Google Pixel 6 Pro] capntrips:
The dmesg was taken too long after book to contain anything interesting. I unpacked the image and extracted the ramdisk and confirmed the kernel matches the Kiri 4.2.0 and /init matches Magisk 25205, so I wouldn't think the issue has anything to do with the format or compression.

I checked the RiceDroid thread, and there were several comments that custom kernels aren't working with custom roms. One user in that thread reported a similar issue, in that they were able to install the kernel but lost root.

I skimmed through the issue tracker and support thread, and I didn't see this reported anywhere. Since this appears to be a bit more widespread than a single rom or kernel, I would suggest posting it here. Be sure to follow the template, or it will be closed automatically.
[Google Pixel 6 Pro] majorfigjam:
I have used a Zooaux combined usb-c power and 3mm audio adapter for many months, with a wired earphone to listen to audio played by Musicolet, on a rooted Pixel 6 Pro. I’ve always used this kernel, until now.

Everything is fine with the October stock kernel using the adapter, but if I install the 4.2.0 kernel, then the sound cuts out when the device display times out, and the Musicolet app freezes. I’ve tried various battery options without success. I've also been able to use bluetooth earplugs in a different context without the app freezing when the display times out, so it's not a Musicolet issue.

I assume this is a kernel wakelock block affecting the power adapter, but how do I find out which wakelock(s), and more importantly, can I override the blocking, so that I can get back to using this kernel?
[Google Pixel 6 Pro] cultofluna:
@Freak07 are you going to upgrade and maybe start developing for the 7pro?
[Google Pixel 6 Pro] starm0113:
Hello!! My phone is a pixel 6 pro android13 T1B2.20220916.004.

This kerrnel can use?
[Google Pixel 6 Pro] JULIUS_PONOZKA:
Hi. Is there any way to implement DC dimming to mitigate the low brightness PWM?
[Google Pixel 6 Pro] Misterxtc:
Kind of a dumb question but is root necessary to run this kernel?

Edit: I should have stopped there... without root I would not be able to flash this.
[Google Pixel 6 Pro] Poesini:
Hey @Freak07 , any chance on supporting Paranoid?
[Google Pixel 6 Pro] w_tapper:
paranoid android is pretty mid and I don't think it's out for pixel 6/pro

IGNORE THIS IM STUPID
[Google Pixel 6 Pro] phaino00:
Actually, PA was released last night in beta, for both Oriole and Raven. New posts created last night under development in respective forums.
[Google Pixel 6 Pro] w_tapper:
oh nice then, can't wait for lineageos to release too
[Google Pixel 6 Pro] scloutkst:
Thank you for your hard work @Freak07

You made the 6 pro much better and usable for me with your kernels. Sadly I am moving on to the 7 pro and won't be able to use your kernel anymore. Nothing could fix the connectivity issues I had on my 6 pro, so I had to upgrade. Have used your kernels on many devices in the last few years, and they always rock.

Thanks again for the amazing work you put in.
[Google Pixel 6 Pro] Freak07:
I can´t reproduce this behaviour on my end with and usb c to 3.5mm adapter. I don´t have a split adapter like yours though.

There are no wakelocks blocked.

Maybe it´s an update to the app that screwed it over?

If not I need a kernel log and a logcat, while the issue happens. If you can get me the exact time (hours, minutes, seconds )the issue happens it will be easier for me to search through the logs.

The FAQ explains how to take those logs.

Please search the thread. Only Android 13 Stable, not A13 QPR beta is supported.

have you tried setting higher manual brightness and use extra dim tile via quicksettings?

:)

It´s not really up to me to "support" custom roms. If you refer to the issue that makes users lose root on custom roms when flashing a kernel.zip I don´t know what´s up there. Probably best to follow the advice here.

Thank you very much for the kind words. :)

:)
[Google Pixel 6 Pro] scloutkst:
Hallelujah, praise all that is good. Looks like you're using a 7 pro. We can hopefully expect good things in the future. 😁
[Google Pixel 6 Pro] Utini:
Off topic level 3000 but: Do you feel a upgrade in battery or anything else with the P7P over the P6P? So far I am not convinced to upgrade. Congrats on your P7P!
[Google Pixel 6 Pro] w_tapper:
now that you have the 7 Pro, will there still be updates for kirisakura for the 6 pro?
[Google Pixel 6 Pro] Ghisy:
@Freak07, woot woot! 👍
[Google Pixel 6 Pro] slickrasta:
How do I update the Pixel software without causing bootloop when I use this kernel? Do I have to uninstall the kernel first? I've bootlooped three times on the last 3 updates so I want to hear how everyone else is doing this without issue?
[Google Pixel 6 Pro] jericho246:
Personally I use Pixel Flasher https://xdaforums.com/t/pixelflasher-for-google-pixel-6-pro-support-thread.4419561/

When there's a new monthly update, I simply update my phone with the Pixel Flasher tool. Then, if a new version of the kernel is available, I flash it with EX Kernel Manager. No need to uninstall anything.

Not sure why you get bootloops though. Can you share the exact steps you take when updating?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I don't remember ever having a bootloop when I used the modified (without -w) flash-all.bat with each month's factory image zip. I first boot with the stock unrooted kernel, then I live-boot the rooted stock kernel and direct install it. Lastly, I use Kernel Flasher to flash this updated kernel, and reboot once more.
[Google Pixel 6 Pro] Nightf0x_007:
I faced the same issue, using type c to 3.5mm adapter, my p6 started to lag and youtube forceclosed and audio stops when i turn off the screen (playing youtube videos on background), and the phone reboots but after some trials of uninstalling & reinstalling youtube it started to work, idk if its from the kernel or what, also since october my device ram usage is high and apps wont stay for long at the background and will refresh again when i reopen them from recent apps, and sometimes phone suddenly reboots (happened to me today pressed on chrome on a link which directs u to a website and i have the app of the site installed on my phone when phone switched from chrome to the app the phone rebooted)

Edit: the lag and audio issue isnt there when i use my bluetooth tws (oppo enco x2)
[Google Pixel 6 Pro] manueltimz:
Yes, he always updates his kernels for older devices
[Google Pixel 6 Pro] manueltimz:
T

The reason you get a bootloop is because you don't disable your magisk modules before updating OTA
[Google Pixel 6 Pro] Lughnasadh:
I take it you're trying to update via OTA through the "Install to Inactive Slot" method in Magisk? If so, you need to have stock (unmodified) partitions to pass pre-OTA block verifications, so yes, you need to flash the stock images that the kernel modifies beforehand. However, this method hasn't been working for the Pixel 6 series with much success lately.

If you are trying to update via the "normal" OTA method, the above still applies.

You could just flash the factory image, use Pixel Flasher or Android Flash Tool and re-install the kernel afterwards.

Would be helpful to know exactly how you are updating. Magisk mods can also cause bootloops.
[Google Pixel 6 Pro] AlDollaz:
I don't disable my Magisk modules either. No issues updating.

(Edit: I don't update via OTA either. Doh, sorry for not reading.)
[Google Pixel 6 Pro] jimbob343343:
It's it working with the latest beta? Want to ask before I risk trying on my daily. Lost root and this on the first beta
[Google Pixel 6 Pro] digger16309:
It's odd how many times this question is asked and answered. It is also in the OP. The kernel is for stable only, not beta-supported.
[Google Pixel 6 Pro] jimbob343343:
Thank you. And I'm sorry, I read though a few pages and didn't see it so I thought I would ask.
[Google Pixel 6 Pro] pakin1:
Hello I'm trying to flash this kernel with my Pixel 6.

I don't see an option in Kernel Flasher to flash zip.

Can someone point me in the right direction? Thanks in advance.
[Google Pixel 6 Pro] roirraW "edor" ehT:
"Flash AK3 Zip"

:D
[Google Pixel 6 Pro] pakin1:
That's what I tried. I'm getting bootloop after flashing this. That's why I though it's a wrong button :D . I'm on the latest stable Android 13 with Magisk flashed.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Is the Kernel Flasher app up to date? XDA thread for the Kernel Flasher app is here.
[Google Pixel 6 Pro] pakin1:
Yes, I'm on the latest version. I also checked sha256 sum after moving file from my pc to phone.

EDIT:

As for now I dirty re-flashed my pixel twice. It's booting with your kernel now. I'm not sure why this happened. I didn't changed anything. Just the dirty flash. Anyway it's working now, not sure what caused the problem. Thanks for your time.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I've had something just like this on my Pixel 6 Pro before - I think maybe last January or March. I think in that case I used the

Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own) to dirty flash, as dirty flashing with the factory image zip wasn't helping.
[Google Pixel 6 Pro] darkness4every1:
Been using the latest release of this Kernel (oct update) with battery saver level 3 and Battery saver touch limit enabled in CleanSlate but I'm only getting 3-4h SOT on a relatively new Pixel 6 Pro.
[Google Pixel 6 Pro] Freak07:
Doesn't sound right to me. Though I guess it depends on usage.

I'd check via batter battery stats if something is keeping the phone awake or via terminal with top command if an app or service is hogging resources.

search the thread, both have been explained. :)

better battery stats is available on XDA.
[Google Pixel 6 Pro] darkness4every1:
Thank you, I'll be looking into it tonight.

Before the Kernel my SOT was 6-8h but I reckon it might be something killing my battery in the background.
[Google Pixel 6 Pro] pakin1:
Could be an updated app that cause problems.

I sometimes check CPU usage with HTOP in Termux.

Example:

Few days ago I noticed that Revolut app was constantly using about 20-30% of my CPU. I downgraded this app to previous version and it's all good now.
[Google Pixel 6 Pro] darkness4every1:
Also using Revolut but seems fine.

system_server (goes up to 40-50%)

sys ui, logd, surfaceflinger, nexuslauncher, imputmethod.latin (20-30%)

com.zhiliaoapp.musically (10%~) I'm not sure why TikTok runs in the background so much when I don't even use the app...
[Google Pixel 6 Pro] w_tapper:
data collection
[Google Pixel 6 Pro] DRatJr:
Just checked the 4.2.0 folder in the Generic android device folder on AFH and there was no download. Am I missing something? Sorry lol.
[Google Pixel 6 Pro] Freak07:
Check the release post of 4.2.0. it's linked in the OP ;)

AFH was lately a bit wonky and didn't allow me to upload correctly, so it's attached there.
[Google Pixel 6 Pro] Freak07:
Something is not right on your end.

If I let it idle without touching barely anything crosses 10% CPU usage during short spikes.

If that's only very short spikes I guess it can be fine.

Usually it looks like this for me:

The kernel only grants the resources it's told to use for those tasks. If you can find out, what exactly is causing this behaviour.

They're smarter than that 😁 taking that much CPU share is too obvious.
[Google Pixel 6 Pro] DRatJr:
Oh okay awesome. Sorry about that lol. I remember (and read again just now) the problem of the 'device is corrupt' bug. I see the warning is still there. Is the bug still there? I remember hitting it last time and being able to fix it, just wanted to double check. Thank you again!
[Google Pixel 6 Pro] Freak07:
I can't give you a definitive answer, but I think the bug can still happen.

I never encountered it on my p6pro since I run with avb flags for verity/verification disabled since I got the device basically.

But I recently fiddled around with avb on my P7 pro and I can reproduce this error there by "confusing" avb while trying to "trick" avb.

So my guess is yes, it can still happen.
[Google Pixel 6 Pro] w_tapper:
then what might they be doing
[Google Pixel 6 Pro] Freak07:
no idea. :)

but system server at 50%, while not touching the phone isn´t supposed to happen either.

In this case I´d start to very closely examine logcat, check for anomalies with battery historian and try to find out what´s causing an issue that way. Or start fresh in case something is messed up badly.

But that´s also where this gets off-topic :)
[Google Pixel 6 Pro] BarackMitzvah:
Anyone try 4.2.0 on Nov update yet? 🙂
[Google Pixel 6 Pro] Houssem9506:
Stuck at 120 all them time is it related to the kernel ?

So far the kernel is awesome great work hope you will port the faceunlock feature from pixel 7 pro

(I don't have force peak refresh enabled)
[Google Pixel 6 Pro] djo_5296:
there's usually a new Kirisakura version when Pixel monthly update arrives so im waiting for that before I update to Nov
[Google Pixel 6 Pro] AlDollaz:
This is the way.