yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Jon8RFC:
@Freak07 Wanted to share this if you're curious to know...

Pixel 6 Pro (Google Store GoogleFi edition)

April 2022 factory image

Magisk 24306

Using the flashable 2.1.0 zip through exkm led to the "corrupt" pre-bootloader-warning splash screen, it would not bootloop, but got stuck on the "Google" screen, not even getting to the "G" animated loading screen.

Reverting to stock + magisk patched boot.img resulted in an error screen like this which, fortunately, was resolved after one "try again" reboot. This solution resolved the "corrupt" splash screen issue.

Manually installing did not give the "corrupt" splash screen and would bootloop. I did this with and without the module.

I did, a very long time ago, do the verity disable flags. I've been dirty flashing every monthly factory image without disabling verity, since Magisk was patched to not require it. I also dirty flashed the "bad" December factory image before it was pulled.

EDIT:

Reverting to magisk 24300 then...

1) Flashing a magisk 24300 stock boot.img, rebooting into android for grins, then rebooting again and manually flashing kirisakura with a magisk 24300 patched boot.img with the module resulted in success. (I was curious if it would work without the module, and that resulted in a perpetual "G" animated loading screen)

2) Reverting to all-stock + magisk 24300 boot.img, removing the kirisakura module, rebooting, flashing your flashable zip via exkm resulted in success.

Obviously, there's still something up with 24306.
[Google Pixel 6 Pro] Lughnasadh:
Yeah, you want 2.1.0. if on the April build.
[Google Pixel 6 Pro] TotallyAnxious:
Delete
[Google Pixel 6 Pro] jayjay1234:
Thanks Folks, up and running!(y)
[Google Pixel 6 Pro] Freak07:
the only thing you need to be for this is rooted. which kernel you run doesn´t matter. stock works, all other custom kernels work. :)

But don´t worry if you´re occupied elsewhere,. I got plenty of data and the last few logs no new binnings popped up, so I think I should have enough.

That said if anyone wants to contribute their dmesg I´m still open. :)

Thanks for the kind words. Enjoy your new toy :)

There´s nothing in the kernel that changes this behaviour.

Nice to hear you got it working.

Unfortunately Google created a total mess of versioning this time.

At first we had A12. Then we had A12 and A12Beta, beta was called A12L or 12.1.0.

With the last feature drop in march A12 became 12.1.0 or A12L, however you want to call it. Google decided to let the Android-Version displayed in settings still be just "A12" when you´re running 12.1.0 as it´s also called on the factory images page. (https://developers.google.com/android/images#raven)

A12L Beta is now Android 12 QPR3 Beta or June Feature drop Beta.

I definitely understand why 12.1.0 and A12L beta as it´s in my OP gets confusing to somebody new to this.

Thanks for the detailed report. I don´t exactly know at this point if magisk is to blame or there´s just a bug on pixel 6 devices triggering that corrupt splash screen issue.

As to 1): the module contains a part of the updated firmware. Without that part the phone won´t be able to boot.
[Google Pixel 6 Pro] HyaenidaeNET:
Hi @Freak07. Just want to ask, do you have any plans to support a13 beta? And did you see a sultan's work about RT in android kernel?

My dmesg. Stock, a13, magisk, p6pro
[Google Pixel 6 Pro] crixxuscenturion:
Hello this is my dmesg logs. Thanks for doing this for us

Easyupload.io - Upload Files and Share Them Easily

Uplaod files easily and share them with your friends and colleagues. File upload solution for everyone. Upload big files and get a link to share effortlesly.

easyupload.io
[Google Pixel 6 Pro] Lughnasadh:
A slight bit off topic, but the kernel version in A13B1 is 5.10.103, so they finally have the dirty pipe fix in a release, for those interested.
[Google Pixel 6 Pro] Paz9:
Anyone notice app preferences being reset? (Picture in picture, usage access, restricted apps, all go back to default after a few restarts)
[Google Pixel 6 Pro] Freak07:
no I don´t have plans to support a13 beta at the moment.

Nice to see. Checked a13 beta source yesterday and brought in a few improvements to the A12 kernel so we all can benefit in the next release.

A12L QPR3 Beta 2 also has dirty pipe fix :)

That has nothing to do with the kernel. You might want to create a new thread in regards to that problem to avoid confusion and cluttering. :)
[Google Pixel 6 Pro] dijia1124:
But it does feel different on raven. Once got moto edge x30, it had the similar issue under 144hz refresh rate, but no issue under 120hz. And it had got fixed after the following OTA update.
[Google Pixel 6 Pro] spr33:
I don't see this behaviour on mine.
[Google Pixel 6 Pro] Jon8RFC:
Attached.
[Google Pixel 6 Pro] Paz9:
Am I able to flash this over radioactive? Kernel?
[Google Pixel 6 Pro] phaino00:
It may work, but it is best practice to return to stock image prior to flashing another kernel. Reason is due to the vbmeta, dklm, etc partition sizing. @Freak07 has a thorough explanation posted a month or so ago.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Edit: I was too slow. :D To be safe, you should restore ALL the partitions that the radioactive kernel flashed to stock - not only boot.img. Then flash this kernel.
[Google Pixel 6 Pro] Fauxnetiks:
Just flashed 2.3.0, so far so good, feels a little snappier to me. Also it seems to have reset a lot of permissions which is a strange behavior.
[Google Pixel 6 Pro] Freak07:
Kernel is not related to permissions or similar. That's handled by the framework.

It seems to happen for others on stock kernel and other kernels as well.

https://xdaforums.com/t/app-preferences-being-reset.4438307/

If that's new "behaviour" or a new bug it might be introduced by some of the playservices, google computational services updates the past few days.

According to the thread it's seemingly triggered by simply rebooting, which you'll inevitably have to do to flash a kernel. sounds to me like something breaks there unfortunately.
[Google Pixel 6 Pro] Fauxnetiks:
Ah I hadn't seen this yet, sure sounds like what happened, thanks for the info!
[Google Pixel 6 Pro] Utini:
Flashed fine over 2.1.0 :)
[Google Pixel 6 Pro] Paz9:
Newupdate seems to be much better
[Google Pixel 6 Pro] Gytole:
Yeah it is. I noticed instantly that I was getting better battery life. Not going to lie I never tried this kernel before? But it's actually kinda nice? My phone isn't getting hot...the battery is lasting longer...I would day this is good stuff. And there's no lag in my keyboard input.
[Google Pixel 6 Pro] Karim.younus:
Just flashed 2.3, running great so far. Thanks for your work on these devices, expect a small donation in the coming week good sir
[Google Pixel 6 Pro] Jon8RFC:
@Freak07 just wanted to let you know about this anykernel3 source update, for your future releases, if you didn't already know:

Question: module highlighted in red? · Issue #138 · Fox2Code/FoxMagiskModuleManager

What does this mean, and what should I inform the module's creator of, if anything? https://imgur.com/a/m8SHaSZ Here's the exact zip file which, among other things, contains the module: https://and...

github.com
[Google Pixel 6 Pro] Utini:
While I cannot comment on battery life (yet) it feels like the phone is much smoother now.

Maybe the reboot (and an SD Maid run) have made it smoother. No idea if that does anything to performance.

But I did that together with flashing the new update.
[Google Pixel 6 Pro] cabagekiller:
I want to add the latest kernel has helped my battery life a ton. And I wanted to thank you for your work. !
[Google Pixel 6 Pro] Jon8RFC:
I guess everyone else already tried going into recovery and trying to get /proc/last_kmsg (doesn't exist) and /sys/fs/pstore (doesn't exist), or similar. I just googled and came across those...although last_kmsg was from 2012 and may not be applicable.

Anyway, I read that "you should patch your boot.img on your own phone" to play it extra safe. This has me wonder if maybe there is something barely different about the boot.img files from one phone to the next. Is there a chance, at all?

If so...

Freak07, would you mind sending me your working Kirisakura_Raven-2.1.0_A12_stable 24306 manually patched boot.img for raven/pixel6pro, if that's your phone? If it's a worthwhile trial, I'd like to see (just for grins), what happens if we trade. I never patched 2.3.0 with 24306, so I don't have that one handy, but I could still try your 2.3.0 anyway.

If feel like there must be a way to narrow down the cause, whether it's magisk or the phone, because of whatever changed between 24302 and 24303 being able to point at something in particular.

EDIT:

Actually, I do see /sys/fs/pstore/console-ramoops-0 with su while I'm booted into android. But apparently I don't know the right way to access that from recovery.

adb shell was my missing step. So /sys/fs/pstore/ does exist, but it's empty. No console-ramoops-0 either. Does this kernel support config_pstore?
[Google Pixel 6 Pro] viper8u2:
I agree, my phone has been off the charger for almost 24 hours screen on time says 6h 27m and I am 53% battery left. Wow I just sent you a small donation to your Paypal to show my appreciation. Thank you
[Google Pixel 6 Pro] roirraW "edor" ehT:
There is definitely no difference in the boot.img on different devices before patching with Magisk. There is definitely a difference in the boot.img when patched with Magisk on different devices.
[Google Pixel 6 Pro] Jon8RFC:
Just to clarify that we're on the same page...

It's not merely a difference in the hash of the file because maybe magisk salts something innocuous but unique into each patched boot.img, like the wifi mac address and the first and last 2 digits of the IMEI or something?

So if I buy two Pixel 6 Pro phones, set them up identically, then patch boot.img, they will be fundamentally different and the boot.img files will function differently? If so, I'm even more interested to try a "working" 24306 boot.img
[Google Pixel 6 Pro] capntrips:
For what it's worth, if I patch the same boot image with the same version of Magisk on both a Pixel 6 and a Pixel 5a, the binaries are identical. I'm sure there are some configuration differences between some devices that would prevent that from being the case, so I wouldn't expect that to be true for all devices.
[Google Pixel 6 Pro] Freak07:
Correct, you should always patch the boot.img yourself on your own device. Besides the advice to do that as patching on different devices might not create the exact same binary (has happened in the past, but don´t ask my why), the uninstall magisk option will not work properly if not patched on your own device. That´s the most important reason.

Kernel has pstore support. You can check how to get a ramoops via the linked post in the FAQ.

As far as I´m aware you can´t access pstore from stock recovery. we´d need a custom recovery for that.

You already learned how to access it from the running system, once booted up again after a crash occured.

Attached is the pixel 6 pro/raven boot.img uploaded to androidfilehost for 2.3.0 patched via magisk 24306.

Flashed powerhint module via magisk manager, then flashed the 4 images according to the instructions via fastboot/fastbootd and booted up no problems.

Glad it´s working out for you!

Thank you very much for the donation! It´s greatly appreciated :)
[Google Pixel 6 Pro] Jon8RFC:
Thanks! Unfortunately, it didn't work.

I removed my PIN hoping maybe if the pstore contents were encrypted-hidden in recovery (whatever that weirdness is that it does) that it'd be accessible, but it wasn't. I remember TWRP being unique in asking for the PIN to be able to access data from the phone.

As best I can infer, the pstore folder is overwritten on boot. I compared the files after a boot, then rebooted, and none of the old data was retained upon reboot. I also let it bootloop on the 5.10.113 kernel for ten times, then I flashed back to the 5.10.109 kernel, grabbed the console-ramoops-0 file and it only contained 5.10.109 references.

There were some older files I grabbed, but after seeing that data is overwritten on reboot, I struggle to believe that the data is relevant, which is why I tried with a different version kernel to more easily check. I've attached files I grabbed after clicking through a bootloop 10 times, then letting it idle through a bootloop 10 times, consecutively, then flashing a working boot.img. Based on the file size being half of that of a reboot from a successful boot (which overwrote all of the old data), I don't know if those "reboot info" messages were just from my flashing reboots in my batch file, or what.

Thanks again for entertaining this mess, Freak07. I really wish there was a quick way to figure this out...or that TWRP existed so I could actually pull the files in confidence.
[Google Pixel 6 Pro] Freak07:
Like I said you can´t access pstore in stock recovery.

On each reboot sys/fs/pstore will be overwritten from the past running session. If you boot from fastboot to fastbootd to flash vendor_dlkm, the files will be overwritten as that´s a reboot.

Might need to use a few tricks to get a ramoops then.

I don´t fully understand what you´re trying to do or get logs for. From your previous post I assume you´re trying to figure out why patching with magisk 24300 works and boots but patching with magisk 24306 doesn´t work on your end?

If your device is bootlooping and not crashing like you describe, you can simply try to get a dmesg via adb shell with su access granted. If you get to adb shell there´s no need for a pstore.

adb shell

su

dmesg -w

check what´s happening or save the log.

So how you can get pstore for your situation if it´s crashing and not bootlooping and you never get to adb shell:

Install latest powerhint module via magisk manager.

Flash 2.3.0 boot.img patched via magisk 24300, the other images according to instructions and make sure everything works.

Now flash 2.3.0 boot.img patched via magisk 24306 and let the phone crash.

You might need to get the timing right if you press any buttons to get to bootloader. If you press too long you trigger a reboot which will overwrite previous pstore.

Once in bootloader, flash back working 24300 magisk patched 2.3.0 image. boot up and check if you have a ramoops of the crash. That way you avoid rebooting to fastbootd.

The 4 images you´re flashing always have to match from the same compilation. you can´t mix and match there.
[Google Pixel 6 Pro] Jon8RFC:
Thanks. What it's doing is crashing then, and it cyclically reboots itself.

I was doing that before, but I expected something to stand out to me more obviously than some of these things which look like normal unlocked bootloader or custom kernel kind of things. I hope that the AVB error is exactly what it is, and then it's a piece of cake fix for magisk to correct. Is that it, a bug in magisk? Do I just post a bug report and send them dtbo.img, vendor_boot.img, vendor_dlkm.img, and both 24300 and 24306 boot.img files? Nope, that looks normal for unlocked bootloader/custom kernel stuff. And I have no idea what the other errors could remotely mean, so I hope you have some insight.

successful boot with Kirisakura 2.1.0 patched via magisk 24300 and powerhint_p6_v11.zip

restarted via interface

held volume down button only after power off, bootloader came up

fastboot flash boot kirisakura_2.1.0_magisk_patched-24306_pixel6_apr22.img

clicked power button once to issue "START" from bootloader

phone rebooted

allowed to crash

when screen was blank, held volume down button, bootloader came up

fastboot flash boot kirisakura_2.1.0_magisk_patched-24300_pixel6_apr22.img

clicked power button once to issue "START" from bootloader

phone rebooted

copied sys/fs/pstore/console-ramoops-0 file
[Google Pixel 6 Pro] Freak07:
Yes that looks like you catched it.

I´d open an issue on magisk github. Explain that boot.img patched via magisk 24300 works, while 24306 breaks booting.

Upload all images (boot, dtbo, vendor_boot and vendor_dlkm), the unpatched ones and both patched images.

Describe the setup of your phone, verity enabled, remove all other modifications etc except the powerhint module to make sure the issue is not from something else.

Include the ramoops file and maybe someone might know why that is happening.
[Google Pixel 6 Pro] f8lxninja:
Successfully flashed 2.3.0 on ProtonAOSP 12.3.1 test 1 for patrons, will see if I encounter any problems.
[Google Pixel 6 Pro] XSLdesire:
hello, can't we disable the magisk module that comes with this kernel? I did that then got stuck at boot logo
[Google Pixel 6 Pro] Freak07:
No you can't disable it. It's crucial as it contains a part of the updated firmware from the qpr beta, which some kernel changes rely on.

I'll put a warning in the instructions in the OP.
[Google Pixel 6 Pro] XSLdesire:
ok, i see. thanks for the reply😘
[Google Pixel 6 Pro] McNaccken:
Hi there, just wanted to say big thanks to Freak07 and this awesome kernel! Flashed the latest one without a single problem and so far so good. Will report back in a few days how it goes, especially about the battery usage. Really curious about that. Thanks again!
[Google Pixel 6 Pro] awarman:
Does anyone notice degraded performance after your phone has been up and running for over 24 hours? I have no idea if it's the Kernel or not. I mostly notice that after a reboot I can record my screen with no fps drops then a day later when I attempt to use it, I notice the fps drops and lag. Is it kernel related or does it happen on stock? Is it just me?
[Google Pixel 6 Pro] Admiral2145:
It was like that for me on the kernel before this one... I haven't tried this newer version yet to see if it was fixed or not... Most people said it was nothing wrong when I brought it up here.
[Google Pixel 6 Pro] Freak07:
Hey :)

thanks for the report. I´ll try to reproduce that issue and do some tracing next week to check if I can find anything .:)

I haven´t noticed any slowdowns on my end, but I can try that specific scenario. What are you trying to record exactly?

There can be many reasons why the phone could slow down the longer its uptime is.

App/services stuck in background, thermals, other background work running at the same time, some android maintenance stuff going on at exactly the wrong time, RAM being filled slowly, it can even be a specific app causing this slowly over time, it could be down to adblocking (host file being silently updated in background) but there could be a kernel issue that manifest only for specific scenarios too.
[Google Pixel 6 Pro] awarman:
I noticed it at first when I was trying to screen capture an Instagram gif. Then seeing that it was so laggy and slow, I closed Instagram and just transitioned through my launcher/home screen to find that the lag persisted. When you released the latest update and I rebooted, I noticed that it was nice and smooth again just recording my launcher transitions. I figured it was something you had fixed in the Kernel then the next day I tried it again which is when I noticed the lag... But not quite as bad as the first time. I rebooted and tried again, noticing that it once again was smooth and high fps. I did uninstall some apps that I'm not using just in case but I don't know that it has helped yet.

I do have Adguard installed. But considering that it occurred and then subsided after a reboot I wouldn't think it was that. Still working fine right now, just checking it.
[Google Pixel 6 Pro] TotallyAnxious:
Adguard doesn't cause this issue. I use it and face no problems with degrading performance.
[Google Pixel 6 Pro] KillerVamp009:
I just noticed after being booted for a day or so that my CPU max is locked to 1197.
[Google Pixel 6 Pro] awarman:
I'll have to check mine the next time it does it. Right now it's still going strong.
[Google Pixel 6 Pro] NikoZBK:
I'm also noticing a degradation in performance after 1d 2 hr of standby
[Google Pixel 6 Pro] Paz9:
I've noticed this, I'll go back to stock and test it out to see if the same happens
[Google Pixel 6 Pro] Lughnasadh:
For what it's worth, I've noticed absolutely no performance degradation on this kernel, even without rebooting for a couple/few days.
[Google Pixel 6 Pro] McNaccken:
Same here, still working great for me.
[Google Pixel 6 Pro] Freak07:
Interesting. So just that I understand it correctly: you started the screen-recording, the phone started to lag and after the screen-recording was stopped the lagging persisted on launcher while no screen recording was happening?

The recording itself was laggy too?

No probably not adguard, just wanted to give a possible list of reasons.

As sad as it sounds android is more or less known for exhibiting this kind of random slowdown behaviour for some and not for others. Just google around and you´ll find plenty of cases.

Next time it happens can you please get a dmesg and a logcat, while the issue happens as described in the FAQ?

That probably means your phone is either thermally throttled or something else changes the freq from userspace/firmware.

The kernel itself doesn´t change the max-freq. Thermal hal, powerhal, powersaver all those can change the max-freq depending on the device state.

Thanks for the report. While I appreciate the effort this will rule out nothing and won´t help me in any way unfortunately. A reboot usually clears out most issues that could cause this, no matter the origin.

Without logs it won´t be clear if it´s the same issue in case you encounter the same symptom on stock or if it´s an issue on my kernel if you don´t encounter the issue on stock.

As long as I can´t reproduce the issue on my end and do some tracing to get a proper look into this it´s just random guesswork what exactly is happening.

Try to take a dmesg and a logcat when the issue happens as described in the FAQ. If you want to make it easy for me give me an exact timestamp so I waste less time going through the logs.

Maybe that way it will be possible to tell what actually happens.

Thanks for the reports, same on my end.
[Google Pixel 6 Pro] Jon8RFC:
An odd thing happened to me, twice. Youtube, would not play via app or browser. So maybe things center around the gpu in some manner. I don't think my phone "slowed down", but it seemed fine when I switched apps between the browser and youtube app, and seemed fine when I did a simple check for internet connectivity via browser. Maybe it was very sluggish with video rendering and that's why it appeared to not work. A reboot fixed that issue, both times, but I only ever experienced it those two times.

I'd like to know if any of you all having the slowdown issues also cannot use the latest magisk. Maybe that's a start to some commonality.
[Google Pixel 6 Pro] Freak07:
That has almost certainly nothing to do with the kernel either. Next time it happens, get a dmesg and logcat after app and browser fail to start a video.

I´m using latest canary, no slowdowns, no youtube playback issue/video starting issues.
[Google Pixel 6 Pro] Paz9:
I'm suspecting some other update Google pushed out causing the issues recently experienced. My app preferences are no longer resetting, it's about the same time I realised the laggy/stutter.

Previously app preferences and battery restrictions were being reset between restarts now it seems fixed.

Ill try and get lcats and dmesgs when it happens next.
[Google Pixel 6 Pro] Freak07:
thanks for the input. :)

could very well be something like that. app preferences have nothing to do with the kernel like I said earlier, but great to hear it seemingly doesn´t happen on your end.

chances are high slowdowns as reported and experienced here by a few are not caused by the kernel. usually kernel issues manifest pretty quickly and everyone is affected, not only a few.

lets see if the logs show anything.
[Google Pixel 6 Pro] awarman:
It was only occuring when recording. When I stopped recording it was smooth again. I'm seeing a little bit of the same right now but it's no excessive.