yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
Seems fine to me. Maybe a bit of background stuff going on plus mild thermal throttling. But overall that looks just fine. Nothing to worry about there.

To be frank it was probably just "luck" or however you want to call it this morning. There´s nothing I did to get that score. The phone was pretty cool when I started the bench, I was in a cold room and probably nothing happening in background.

When I check my past geekbench scores, where I know I started with a cool device to rule thermal throttling out multicore scores are "roughly" around 2700-2900. So the screenshot I shared from a random run this morning was on the higher end of my results.

Geekbench has a noticable variance of scores on all of my phones, but at least it´s not one of those benchmarks that just max out the phone.

I wouldn´t put too much importance on benchmarks (the popular benchmark apps) in general, that´s why I rarely post or talk about them in my threads. :) They´re useful tools, but score chasing is nothing for me.

Quite frankly score chasing is what brought us to the current situation that most flagship SOCs can't maintain their max perf for only even a few minutes, if even a minute without throttling in some form. But that's another story :)
[Google Pixel 6 Pro] highdro:
Couldn't agree more. I'm on the latest beta running your kernel and it's so smooth. Great job man. I couldn't care less about geekbench scores but I installed it just to see if I could get a 2900 and I didn't get it. Extremely dissapointed 🤣
[Google Pixel 6 Pro] arvylas:
So I flashed back to 2.1.0 to capture logs and now everything is buttery smooth and fast. That's really weird, I don't even re downloaded the file. The only thing I did differently is that the previous time I flashed 2.1 over stock and now I flashed it over 2.0.1.
[Google Pixel 6 Pro] Freak07:
Thanks for reporting back.

It was probably the reboot that cleared out whatever the problem was. Or highly unlikely a bad flash, or the magisk module did not get created properly or was deleted for some reason.

It doesn´t really matter if you start from stock april firmware or april with 2.0.1 flashed, when flashing the 2.1.0 zip. The end result is the same.

The zip will replace the zImage inside the boot.img and flash 3 images to your device alongside with creating the magisk helper module.

Thanks for the report and taking the time! Glad it´s working fine now.
[Google Pixel 6 Pro] arvylas:
I had done several reboots before going back to 2.0.1 so I doubt that was the issue.
[Google Pixel 6 Pro] Israafil:
So i had an magisk issue, so flashed stock boot files with flash-all.bat, afterwards all worked fine, rooted phone and later installed the kernel and immediately after flashing the kernel the camera performance suffered greatly. Whenever i switch to a another mode or switch to front camera there is a significant lag like 5 to 10 sec, this was not the case with stock boot all was fluent, just after flashing the kernel the camera lag issue appeared.
[Google Pixel 6 Pro] DRatJr:
Just to confirm, if I'm on Magisk v24306 I should not flash this kernel, right? And I'm assuming next version would support this magisk version?
[Google Pixel 6 Pro] Freak07:
Alright, then it was probably something else. Without logs it´s just a guessing game in the end.

From experience of others and reading the forums here magisk seems to be more spotty on the P6 series than other devices, although I didn´t have any issues myself so far.

Could also be that something else went wrong, which was cleared out by flashing back stock.

Can´t reproduce the issue on my ned. Switching through all modes in GCAM is fluid without any hiccups here.

Took about 150 pictures and a bunch of videos on Sunday, so I´m sure I would have noticed issues on my end.

Without logs and being not able to reproduce issues myself there´s nothing I can do to identify any potential issues, kernel related or not kernel related doesn´t matter.

Make sure to not run any other magisk mods, xposed or other modifications, then try to reproduce the issue and get me a dmesg and logcat while the issue is happening, so I can check if I spot something there.

A guide for how to take proper bug reports and capture logs can be found in the FAQ. :)

You can also try to restore stock images to get back to stock kernel as detailed in the FAQ and then start fresh flashing the kernel. Maybe it helps.

The kernel itself has nothing to do with this. It´s rather something with magisk.

If you´re on stable april 12.1.0 firmware 24306 should work fine for flashing this kernel. However there were issues introduced and also fixed during the few last magisk canaries. That´s why I put the warning to use stable magisk if one wants to be sure there´s no issue.

I´m running magisk 24306 myself without problems at the moment.

Here´s another one that runs 24306 just fine on April Stable:

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

QPR beta is another case and as far as I´m aware without using the QPR A12L beta firmware myself (so based on the experience from others and what I read on the forums), magisk stable is the only way to flash a kernel there.

To avoid all those issues, I just put the warning to use magisk stable to avoid any potential issues. :)
[Google Pixel 6 Pro] DRatJr:
Okay so I was looking and my build number is SQ1D.220205.004, so that's the February update. So you're saying I should be fine flashing this kernel then? (sorry it may be that I'm noob and not understanding what you were saying, just want to make sure)

And if I were to update to the April update, I should switch my Magisk to stable and not canary to (probably) use this kernel without issues, is that right?
[Google Pixel 6 Pro] Freak07:
Good thing you mentioned that you´re running older firmware. :) The latest release 2.1.0 is for April firmware.

Generally you should always try to run a firmware and the kernel that was compiled for this firmware. Sometimes you´re lucky and you can mix and match, but sometimes you´ll end up with bootloops or other issues.

Check the OP for the most recent kernel that was made for February firmware, which should be 1.8.4. Since your constellation is nothing I have testedm, I´d recommend using magisk stable, but canary might work fine.

If that´s your first time flashing a kernel read the instructions in the OP, check the FAQ a bit below and make sure that you have everything available to get back to stock in case you do not like the kernel or run into issues. It´s good to have time to tinker available too, so don´t flash anything to the phone a few minutes before you have to leave for work and need a working phone.
[Google Pixel 6 Pro] DRatJr:
I'm actually going to update to the April firmware now. So based on your experience, patch april image with the magisk I have, flash that, then flash the kernel?
[Google Pixel 6 Pro] Freak07:
yes that should do the trick. update to april, make sure you´re properly rooted and then follow the instructions in the first post for flashing.
[Google Pixel 6 Pro] DRatJr:
Okay so I updated to April using this guide: https://xdaforums.com/t/method-to-u...thout-wiping-data-and-retaining-root.4356065/

Then made sure I was rooted with Magisk, then flashed with EX Kernel Manager, and now it says my device is corrupt. Lol. any idea why?
[Google Pixel 6 Pro] Freak07:
It seems to be a problem some users are getting unfortunately when flashing something to the phone. It happens on regular firmware updates or OTAs to. Google dropped a patch note about it in the march update, but I assume they still haven´t fixed it completely. (patch note can be found here if you scroll down or search for it)

there´s a workaround described in the FAQ for this issue as well. it involves flashing a boot.img for an older firmware and then flashing the matching one, which will clear the message. ( don´t forget to flash the other stock images as well as described in the FAQ, if you want to boot with stock boot.img as well to flash the kernel again)

Never saw the issue myself, but the workaround will do the trick for you to get rid of the message.
[Google Pixel 6 Pro] DRatJr:
Obv not trying to rush you or anything just moreso curious, is this planned to be fixed with the next version? Or is the reason still not known and it'll take time to figure it out? Again not rushing lol, just genuinely curious if the reason this happens for some is known. Thanks for the help, tho. I just got rid of the corrupt message I got last night and I had to wipe device etc. But I'll be retrying flash today (after I get to work lol).

Last question regarding FAQ process for corrupted message:

If I try flashing the kernel again and get the corrupt message, I can flash March boot.img and let it fail to boot, then just flash the magisk modified April boot.img. After doing this though, will I still have the kernel installed?

Thanks!

Edit: Wait, if I just use Magisk 24.2 to patch my April boot image I can avoid all of this, right?
[Google Pixel 6 Pro] roirraW "edor" ehT:
The problem is Google's, and isn't specific to having a custom kernel at all - folks have gotten the corruption error under all sorts of circumstances. One or two of Google's updates have specifically mentioned fixing problems that cause this corruption screen, but they didn't specify if they thought they fixed all causes of that problem, or only some - obviously, they definitely didn't fix all causes.

Note that the corruption screen is an inconvenience but does not necessarily mean that your phone isn't useable. I used mine for about three weeks with that corruption screen any time I rebooted. For me, flashing the next full firmware update that came out fixed it, and then I was once again able to flash the custom kernel without any issue and no corruption.

Edit: At the time, I wasn't aware that flashing an old kernel (and/or related partitions) might fix the issue.
[Google Pixel 6 Pro] Lughnasadh:
Magisk 24.3 is the latest Stable. You should probably use that (if you are already on the April build). But no, that won't necessarily fix getting the corrupt message.
[Google Pixel 6 Pro] DRatJr:
Oh okay. I wasn't sure if it was unique to this kernel and magisk version or not. I had the corrupted message after flashing but it actually wouldn't boot last night. And then I finally flashed all stock and wiped device and still had the message (even when using flashing tool from google) but it was booting and working. Had to downgrade to march then upgrade to april again to get rid of it. I guess I could've just done the boot.img and not have wiped it based on the FAQ post lol.
[Google Pixel 6 Pro] DRatJr:
Gotcha. Well I will give it another try and hopefully this time I don't get the message, but if so I'll try the workaround in the FAQ and report back. Just my last question though, if I have to do the workaround of flashing older boot, failed boot, then flash newer boot, will the kernel still be installed? Sorry I just don't know specifically if kernel is flashed when flashing a boot.img lol. sorry
[Google Pixel 6 Pro] Lughnasadh:
No, because you are flashing the stock boot image, thus replacing this kernel's boot image. And as Freak07 stated earlier, don't forget to flash the other 3 stock images when returning to stock (which of course will also replace this kernel's images with the stock images).

FYI, this kernel contains 4 images that are modified: boot.img, dtbo.img, vendor_boot.img & vendor_dlkm.img. With this phone It's not like the old days where only the boot image (and maybe dtbo) were the only things being modified by custom kernels.
[Google Pixel 6 Pro] DRatJr:
I was specifically referring to the FAQ section where if you get the message, flash an older boot, then try to boot and let it fail, then flash newer boot.img.

And if I'm understanding you correctly, if I do get the message but everything works and my phone boots, I can just ignore the message and use the kernel. But if I want to get rid of it, gotta go back to stock kernel.
[Google Pixel 6 Pro] Lughnasadh:
But as I stated above and Freak07 mentioned earlier, it also says in the FAQ:

"Essentially flashing a boot.img from an older firmware, letting it attempt to boot but fail, and then restore boot.img from the matching firmware clears the message.

If you´re doing this while having the kernel installed don´t forget to flash back to stock completely, which is also described in the FAQ." (emphasis added)

As far as I know, if you get the corrupt message but everything is working as it should, you should be able to ignore it. I haven't seen anyone who has just let the corrupt message be report having any negative side effects.

But if you want to get rid of the message, follow the instructions in the FAQ.
[Google Pixel 6 Pro] stalls:
I know I might catch a bunch of crap for this 😜. Is there a way to turn up the thermal limits? I'm not quite sure if it's the battery or the CPUs temp that eventually puts it into a limp mode.
[Google Pixel 6 Pro] DRatJr:
I'm sorry. I missed that part in the FAQ. But thank you for answering my question. I'm backing up again now, and will attempt the flash again here in a bit. Thank you!
[Google Pixel 6 Pro] Israafil:
The issue could be magisk related not entire sure with no root stock images all is fluid, but after magisk root camera perfomance suffers greatly. Iam using magisk stable, gonna install beta or cannary and test again
[Google Pixel 6 Pro] capntrips:
After a lengthy startup with the G logo and progress indicator (~1 minute), the lock screen appears, but my touchscreen doesn't function at all. The hardware keys seem to work fine, and I'm able to adb into it. I tried searching the thread, but I didn't see a solution. Neither cycling the screen nor rebooting helped.

I'm on stock SP2A.220405.004 using Magisk 24306 (though I also tried 24.3 stable) and version 2.1.0 of the kernel. I think I saw a version for the beta with a different touch driver, but I assume that wouldn't be applicable here. Update: I tried the QPR version (sat at G logo for 5 minutes before giving up) and 2.0.1 (same behavior as 2.1.0) with no luck.

I tried installing it with EXKM, FKM, and running AK3 directly.

I also tried installing the driver manually, though the behavior was slightly different (it bootlooped before ever getting to the G logo). I can provide ramoops for that, if the the solution for the AK3 methods doesn't work there, as well.

The following logs are from a clean install with flash-all with wiped data. The only thing I did prior to kernel install is enable developer tools, install Magisk, and enable Zygisk (though I also tried without).

dmesg.log

logcat.log

Note: I have the exact same issue with the blu_spark kernel.
[Google Pixel 6 Pro] Ghisy:
Hey @Freak07, which CleanSlate app do I need to install to tinker with the colors (KCAL)? Is it the config or service apk?

Thanks!
[Google Pixel 6 Pro] roirraW "edor" ehT:
Neither app has anything related to KCAL. You'd have to use another user's app to mess with it, as the kernel merely enables the ability for KCAL apps to work with it.

Edit: @Freak07's posts in this thread which mentions KCAL, one of which it appears you had responded to long ago. :D

One of the posts in those search results mentions this kernel doesn't have KCAL support, unless it was added at some point after that, but if so I don't see any mention of it.
[Google Pixel 6 Pro] Freak07:
Since you flashed 2.1.0 from the release post linked in the OP for stable A12L that's on androidfilehost, i assume you either forgot to flash the powerhint module when flashing the images manually or something else is wrong regarding that.

I don't have oriole to test.

The symptoms you're facing happen when aoc.bin doesnt match the kernel one or something else is wrong there.

Edit:

I saw the logs on GitHub now.

[ 11.826932] init: Control message: Could not find 'vendor.google.whitechapel.audio.audioext@2.0::IAudioExt/default' for ctl.interface_start from pid: 447 (/system/bin/hwservicemanager)

That's the problem which seems to be from the AOC driver, that delays boot. I'd assume some thing are broken with that kind of issues in the logs.

The only thing that comes to my mind is the magisk module is either not created correctly when flashing the ak3 zip or something else is wrong there.

I'm not familiar with bluspark kernel changes, but if the same happens there the problem might be somewhere else, as i think the kernel is in the p6 oriole forums and tested for oriole? Though i have no idea where.

Another oriole user confirmed the kernel working a few pages back. I don't have a oriole to test myself.

There's no KCAL support in this kernel.

@roirraW "edor" ehT already found my previous responses and ninja'ed me. :D
[Google Pixel 6 Pro] Ghisy:
Sorry, I meant color control features (comparable to KCAL, hence my mistake). You told me to use the CleanSlate app but there's 2 of them: a config and a service one. I wanted to know which one I should install to calibrate the display to my liking.
[Google Pixel 6 Pro] Freak07:
Not sure when or where I told you this, but there's no way to calibrate the screen via any kernel app on the pixel 6 devices.

Check the posts that are linked in @roirraW "edor" ehT 's previous reply.

CF lumen works for that without the need for any kernel modifications or similar for example.
[Google Pixel 6 Pro] Ghisy:
Ah I see! Maybe I was mistaken then. I'll check out CF lumen. Thanks!
[Google Pixel 6 Pro] Freak07:
Depends if somebody finds a way to flash vendor_dlkm when the device is running as it's part of super and not like the other imgs.

But there's work being done on it in the background.

Yeah, it's pretty fast once you get used to it. :)

Not as fast as flashing a zip, but I wouldn't recommend anybody to flash anything on an A/B device without a pc nearby. :)
[Google Pixel 6 Pro] ne0ns4l4m4nder:
I use my device for work. I won't flash anything unless I'm flashing from PC. Sometimes it's hard, when you post a new update and I'm out working 😂😂 I need them sweet sweet updates baby
[Google Pixel 6 Pro] vibrantliker:
I just flashed the kernel on my P6 with no issue, I'm getting this response on the P6 pro doing everything the same.

Pretty sure r31.0.3 is the latest?
[Google Pixel 6 Pro] vibrantliker:
Just tried on another computer also. If someone can help out would be appreciated.

Stuck at "Waiting for devices" after entering fastboot flash vendor_dlkm vendor_dlkm.img in fastbootd
[Google Pixel 6 Pro] Golf c:
I believe you might need up to date Google drivers. I had to update to get it too work on windows 11.
[Google Pixel 6 Pro] ne0ns4l4m4nder:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3

15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...

xdaforums.com

15 second adb always works for me!
[Google Pixel 6 Pro] MArtyChubbs:
Yes
[Google Pixel 6 Pro] MArtyChubbs:
Did you use the same cable?
[Google Pixel 6 Pro] vibrantliker:
everything the same, flashed the kernel on the P6, then went to repeat on the P6 pro and it's getting stuck there for some reason
[Google Pixel 6 Pro] vibrantliker:
I just noticed this on my 6 pro:

shouldn't it say Raven?
[Google Pixel 6 Pro] Flawn:
It should. But may be just a bug.
[Google Pixel 6 Pro] vibrantliker:
just wondering if that's the cause of my problem...
[Google Pixel 6 Pro] RogerF81:
This is my very first battery cycle with my Pixel 6 Pro on Kirisakura. And it's already much better than anything else I ever got on my 4 XL. That's why I'm impressed and satisfied 😁
[Google Pixel 6 Pro] vibrantliker:
Update: figured it out, I may have flashed the wrong vendor_boot.img

and reflashed this for Raven and it fixed it.

fastboot flash vendor_boot vendor_boot.img
[Google Pixel 6 Pro] Texan1:
I'd succesfully installed the kernel but had to do a factory reset...when set up again I noticed Kirisakura kernel was still there rather than stock...

Does it (fully) survive a factory reset or should I go through the full kernel installation again?
[Google Pixel 6 Pro] Freak07:
if you "factory reset" from settings or stock recovery the kernel should stay in place as the partitions won´t be flashed with stock. It seems the device is still able to boot up, so you confirmed that too.

if you "factory reset" by flashing the factory image with -w flag intact or not, the kernel will be gone, as flashing a factory images will restore boot, dtbo and vendor_dlkm to stock.
[Google Pixel 6 Pro] Texan1:
Thanks, yes I did a factory reset from within settings.

So just to confirm, no need to flash vendor dlkm, dtbo and boot again, kernel will be fully working as is?
[Google Pixel 6 Pro] Freak07:
Yes it should work. If you want to be absolutely sure flash them again :)

In case you were rooted I don't know exactly how magisk handles this, but I think it should prompt you to go to setup again after opening the magisk stub app.
[Google Pixel 6 Pro] State.of.mind:
In the future, do you think that we will be able to flash the kernel via a kernel manager?
[Google Pixel 6 Pro] Freak07:
Probably yes :) work is being done in the background.
[Google Pixel 6 Pro] capntrips:
It turns out I had an extra vendor_dlkm partition (in addition to vendor_dlkm_a or vendor_dlkm_b) in both super partition slots, and AK3 defaulted to that one, rather than the slotted one, to flash. I did a fastboot wipe-super then flash-all, and everything started working.

I had the powerhint module installed, but I'll assume the extra logical partition was the issue here, as well, though unlike AK3, fastboot was flashing to the slotted partition. I'll try to run a test, at some point, to verify.
[Google Pixel 6 Pro] jericho246:
Hi,

I am currently on early access ProtonAOSP - v12.3.1. The build is SP2A.220405.004.

Do you think the attached zip is safe to try in my case? Thanks.
[Google Pixel 6 Pro] boxemall:
i don't think he'll be able to tell. in any case manually download the rom and dig out the needed files if **** hits the fan so you can MANUALLY flash back. best way ofc is make a backup b4 trying anything stupid lol :-) fly safe!
[Google Pixel 6 Pro] jericho246:
Thanks for the advice.

A small update: I went ahead and flashed the 2.1.0 zip (from this post) on ProtonAOSP 12.3.1. So far so good - no "corrupted" message at boot, no touch problems. Everything seems to work well except for my banking app which strangely detects root despite safetynet passing. Weird, but probably not kernel related.
[Google Pixel 6 Pro] Jerreth:
I have this issue after every os update event though safetynet passes it still fails for banking apps and for google pay, i have to disable all magisk hide and zygisk and all that and then go through the process again, and strange enough this most recent update i had done all this like i had before and it failed they all still saw the root, and then an hour later or so it just worked again no real answer for that but hey it happens like that some times.
[Google Pixel 6 Pro] DRatJr:
Okay new minor issue lol. About 3/4 of the time when I hit my power button to wake up my phone, my home screen wallpaper will show, not my lockscreen wallpaper, and nothing else on the screen. I can't swipe up, no fingerprint shows so I can unlock it or anything. I have to hit the button to sleep again, then hit it again to wake it, and it goes to lock screen. Any ideas?