yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Daenjel:
Sorry if I wasn't detailed enough, this is what happened to me, phone got in a bootloop on the "Google" logo, never going to the G loading screen and going back to that splash screen saying that my system was corrupted, had to do everything I said to make it boot properly again
[Google Pixel 6 Pro] ttle54:
I flashed the May factory image on my phone this morning and wiped everything. Kirisakura may patch is working as well. I'm just not a fan of reflashing the phone from scratch every time
[Google Pixel 6 Pro] jcp2:
Why are you wiping the phone each time you flash factory zip? You do know that you can flash the factory zip without wiping? Just use the Android Flash Tool website and upgrade each month (unchecking all the wipe/ lock bootloader/ flash partition boxes)
[Google Pixel 6 Pro] cabagekiller:
I'm unsure if it's the kernel or what. But whenever my pixel gets to power saving mode at 20% it becomes entirely unresponsive and boots to a blue/green G. Only way to restore normal use is by charging it. Has anyone else ran into this issue?
[Google Pixel 6 Pro] Jon8RFC:
Oh no! You don't have to wipe each time. You can "dirty flash" on top of your current installation.

All you do is download the factory image (use the "link" URL, rather than the "flash" URL), unzip, edit flash-all.bat and

remove/delete the

-w

flag

. Save the file.

Then run flash-all.bat with your phone in bootloader mode, connected to your computer. It'll reboot numerous times. Let it do its thing until the batch file says it's finished.

Here's the standard way to "dirty flash"

the factory image, go to the "Update and Root Factory Image" spoiler.

Custom Kernel...

If you patch the kirisakura kernel boot.img ahead of time, you can edit your flash-all.bat to flash all of the kirisakura kernel files (copy & paste them into the same folder as your newly edited flash-all.bat), as long as you've pre-installed the latest kirisakura powerhaul magisk module,

before

you run the edited flash-all.bat.

This will install the update via factory image, not wipe the phone, then install the various files necessary (at this time as of Kirisakura 2.4.0) for the kernel and power up the phone normally. No manual intervention is necessary after you double-click your edited flash-all.bat. It'll boot up, be rooted, and have the custom kernel.

Maybe @V0latyle could add the below in, with less hand-holding/verbose instructions.

I found their seamless rooted boot.img install instructions really convenient.

I'll leave my hand-holding/verbose version below, but they'll likely do something cleaner.

SIDE NOTE IF THIS EVER GETS LINKED TO IN THE FUTURE:

Other kernels (and future Kirisakura kernel) may or may not require additional--or fewer--files.

Other kernels (and future Kirisakura kernel) may or may not require a pre-installed magisk module(s).

Other kernels (and future Kirisakura kernel) may require an important, additional step.

As of 2022-05-04:

Spoiler content hidden.

Spoiler content hidden.
[Google Pixel 6 Pro] V0latyle:
Who dares summon me from my thousand year slumber? I demand a feast of souls!
[Google Pixel 6 Pro] tiddy_tangler:
Are all of these issues confirmed fixed?? And how does the update process work when theres a revision? I havent messed with kernels since TWRP was a flash away.
[Google Pixel 6 Pro] Freak07:
None of that is present on 1.0.5.

Follow the instructions in the first post and you'll be fine.
[Google Pixel 6 Pro] Joelbrentbell:
Anyone having that weird bug where the phone just goes down to 60hz I have to do a full reboot to get it back to 120hz? It's not the kernels fault because it would happen to me all the time on stock kernel as well
[Google Pixel 6 Pro] TotallyAnxious:
Try enabling Force Peak Refresh rate. But sounds like a bug you should report to Google if occurs on stock.

Factory reset is always an option too. You'll be able to do it while running the kernel and you'll keep root. The magisk app will be gone and replaced by a stub that offers to download magisk app and then says you need to reboot for magisk to be fully installed. I've already done this when fingerprint scanner broke and was rooted with this kernel (not saying kernel caused it).
[Google Pixel 6 Pro] Joelbrentbell:
Thx but I tried that, still stuck at 60hz. I've tried stock kernel and Kirisakura kernel seems like a software issue
[Google Pixel 6 Pro] TotallyAnxious:
Even more reason to report to Google then.
[Google Pixel 6 Pro] boxemall:
1. what's the difference compared to stock kernel (other than battery life as some folks have already pointed out)?

2. will installing this kernel prevent the device from passing safetynet?

3. i saw a post here on xda (was an asus device) that had a krisakura kernel with battery-idle mode (pass-through charging), is this planned for this kerel as well?

by no means is this a feature request just trying to understand so questions posted in order of importance.

regards
[Google Pixel 6 Pro] Freak07:
1. for now there are only minimal changes to stock kernel, but that will change in the near future :) You´ll find a short features list in the OP.

as for battery life, that might vary from user to user.

2. No your device will stop to pass safety net once you unlock it. There´s a module called universal safety net fix from kdrag0n, which could help you pass safetynet. But there are other threads for that.

3. No it´s not planned. It´s the OP7 kernel and all I did there was to cherry-pick a commit from OnePlus beta branch to the stable branch. This device uses a completely different driver and I´m not playing with the charging drivers myself, other than commits tested by the OEM like in the case on OP7.
[Google Pixel 6 Pro] boxemall:
yeah in this case that makes sense, no one wants a burning "pocket warmer" lol

tx for taking ur time to answer!
[Google Pixel 6 Pro] Jiggs82:
Hey has anyone flash kernel v.1.0.5 over the .037 update that was uploaded today by Google?

Thanks in advance
[Google Pixel 6 Pro] ne0ns4l4m4nder:
No but I'll try now
[Google Pixel 6 Pro] Izy:
missed the chance of calling is Ravenole
[Google Pixel 6 Pro] Jiggs82:
Ok thx. I would think it would work but then again this new update has new .imgs etc?
[Google Pixel 6 Pro] Joelbrentbell:
Could not get mine to update
[Google Pixel 6 Pro] ne0ns4l4m4nder:
Working fine.
[Google Pixel 6 Pro] vandyman:
Ravioli 😎
[Google Pixel 6 Pro] Jiggs82:
Did u flash all the images from the op and patched the boot to keep root ? and everything working fine?
[Google Pixel 6 Pro] roirraW "edor" ehT:
You generally can't take OTA updates actually over the air when you're rooted. And if you happen to be able to, it can cause issues forcing you to wipe your phone. Better to update manually using either the full image zip or OTA zip.
[Google Pixel 6 Pro] ne0ns4l4m4nder:
Yep. I also modified the flashall.bat file in the factory image and replaced the -w with --disable-verity --disable-verification then booted restarted and flashed the images and patched boot
[Google Pixel 6 Pro] cmh714:
Youve been getting lazy since roirraW edor ehT has you covered! ;^)
[Google Pixel 6 Pro] arvylas:
@Freak07 can you check those? I had several slowdowns but not entirely sure I got them.
[Google Pixel 6 Pro] arvylas:
I upload it again because for some reason logcat doesn't want to be uploaded here. Also I have logs for today again after slowdowns.

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] Freak07:
I just took a look. You´re running out of memory and the userspace lmkd starts killing stuff as a last resort. It´s the same on both logs.

I see you´re running oriole so "only" 8GB of RAM. That´s one of the reason why I wouldn´t recommend anyone to buy the pixel 6 regular, as 8GB RAM is the bare minimum for Pixels really. Pixel 4 struggles badly with 6GB and Pixel 5 also struggles with 8GB, although Pixel 5 needs way less as there´s less cameras and less other fancy stuff that needs RAM.

Did you flash any mods that change kernel settings? scripts, magisk modules, tuner apps, other apps? Did you change any kernel settings via EXKM or FKM that are somehow related to Memory?

Did you disable ZRAM?

Do you use any other magisk modules? xposed?

do you restrict any permissions for play services or similar google stuff?

I see play services throwing errors similar to these for 40seconds several times a second before the OOM situation happens:

Spoiler content hidden.
[Google Pixel 6 Pro] arvylas:
I had the servicely app but only what it had by default so I uninstalled it. Other than that nothing of the sorts. Nothing changed in exkm or fk. I attached a SS from magisk. The thing is that at the time of the slowdowns I think only 3-4 apps were active.
[Google Pixel 6 Pro] jericho246:
@Freak07 Hello there it's me again with the incredibly annoying bank app that refuses to work on Kirisakura kernel :(

After testing I am pretty sure it is the kernel that causes the app not to work. For what reason, though - I don't have the slightest idea.

Here's what I tried:

Stock ROM, (May update) + root + stock kernel =✅ app works, no problems. Only Magisk denylist is required.

Stock ROM (May update) + root + Bluspark or Radioactive kernel = ✅ same as above.

Stock ROM (May update) + root + Kirisakura kernel = ❌ something breaks and the app won't work.

I would appreciate some assistance if possible. I'm pulling my hair out here lol.

Also popular workarounds with magisk modules like Shamiko, or Island/Shelter apps (cloning to work profile) have no effect.
[Google Pixel 6 Pro] Sasaiber:
I did it according to the instructions - I flashed it through EXKM. The Google logo just appeared and went out
[Google Pixel 6 Pro] roirraW "edor" ehT:
@Hand76, you could try a custom kernel like this one to improve battery performance.
[Google Pixel 6 Pro] capntrips:
Since the issue was closed on the Magisk repo, I figured I would try to continue the conversation here.

Edit: I tried making a new vbmeta with updated signatures using avbtool to match the modified partitions, but that didn't boot either. I won't say I did it right, but verify_image at least reported success.

Edit 2: It turns out you have to add a hashtree footer to vendor_dlkm and flash it and the updated vbmeta.
[Google Pixel 6 Pro] 93ae8074:
Basically Momo is detecting Magisk with Kirisakura kernel since 2.1 in April. Using stock kernel Magisk is not detected by Momo.

I can confirm none of these work on Kirisakura to avoid detection of Magisk.

No idea what's going on. Just would like to let you know you are not alone on this one. ;-)
[Google Pixel 6 Pro] Dorisnov:
I've been reading the post since I want to flash this kernel and I just have a couple of question:

What is this ProxyHandler bug and it's still mandatory to reboot the phone in airplane mode.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I only knew what I've read here about that bug, and I haven't really retained it since I've never had the issue, and I don't reboot in airplane mode and everything's fine for me.
[Google Pixel 6 Pro] Freak07:
What's the name of the banking app?

Can I try to reproduce the issue without opening an account, so does the app detect root before you log in?
[Google Pixel 6 Pro] Paz9:
My banking app didn't work until I followed the steps in the other thread 1. Hide magisk app 2. Install safety net fix 3. Configure deny list/enable zygote
[Google Pixel 6 Pro] bLack_Q:
For me it was the same thing.

Had it with Gpay and with "S-PushTAN" aswell
[Google Pixel 6 Pro] Freak07:
no problems on my end using GPay running the kernel.

Make sure to use universal safetynet fix, use denylist and wipe data for GPay. No experience with the other app.

yes, that´s what I already replied previously. it makes no sense for apps to target a specific kernel.

Maybe a kernel change present in my kernel triggers an issue with a specific app, which causes the workarounds to break.

But I need logs to even have a chance of figuring out what goes wrong or being able to reproduce it myself.
[Google Pixel 6 Pro] arvylas:
Forgot to mention that this behavior started with the 2.1.0 kernel. Before that wasn't an issue. Also it doesn't seem to happen with stock kernel.
[Google Pixel 6 Pro] Freak07:
Could be MGLRU then. Though if you´re the only one with the issue it might be something else.

I wonder where those Google Play services errors in the logs before the OOM situation happens though.

The userspace lowmemorykiller handles most of the management on pixels. I wonder if MGLRU somehow interferes with that and you´re usage triggers a very specific bug. Or an app triggers a very specific bug, that leads to the situation.

You can try to gather more logs, but at the moment I´m unsure what´s happening.

If I find time I´ll compile a build without MGLRU for you and sent it via PM.
[Google Pixel 6 Pro] arvylas:
I uninstalled servicely so I'll sent you logs again to see if that was the culprit of the gms errors.
[Google Pixel 6 Pro] Freak07:
(y)
[Google Pixel 6 Pro] Freak07:
A12L QPR Beta Kernel

For those on the A12L QPR Beta 3 here are zips to try. They are only supposed to be flashed on Android 12 QPR Beta!

They should work fine on QPR Beta 3 as source was pushed already, merged and I have confirmation it´s working fine on Beta 3.

That kernel has feature parity with the 2.4.0. So for a detailed changelog please refer to the release post of 2.4.0.

I don´t know what´s the current situation with magisk and flashing kernels on QPR Beta, but it´s probably best to use magisk stable if you don´t want to face issues. (although I have confirmation magisk canary 24307 works fine with verity/verification disabled, don´t know about vbmeta enabled)

I´m not myself on QPR Beta so please leave feedback, but remember:

These zips are provided as is I don´t have time to flash between stable and QPR

Feel free to report issues with proper bug reports (containing logs, steps to reproduce according to the guide linked in the FAQ), but they might remain unresolved if it´s not easy to fix without running A12L Beta on my own end.

I wish everybody a great weekend!

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07
[Google Pixel 6 Pro] Nightf0x_007:
I have delayed notifications here, notifications stops coming until i change between using wifi or data, mainly this was caused by gms doze magisk module but i dont have it anymore does anybody knows what might be the cause ?
[Google Pixel 6 Pro] jericho246:
The app is Crédit Mutuel

And yes, you just gotta get to the actual log-in screen after accepting the conditions and cookies. At the log-in screen there will be a red warning that root has been detected.

Thanks!
[Google Pixel 6 Pro] Jon8RFC:
@Sasaiber

That sounds like you're using magisk version 24303+

You'll need to get on magisk 24300:

Release Magisk v24.3 · topjohnwu/Magisk

For those coming from v24.1, check the full changelog for changes introduced in v24.2. [General] Stop using getrandom syscall [Zygisk] Update API to v3, adding new fields to AppSpecializeArgs [App...

github.com

I've had terrifying problems with hidden magisk app and version updates or un/installations in the past, so my method is:

Unhide

magisk app; use the "restore" function in magisk settings

Go into android's app settings and select magisk

Force stop, and uninstall from there (not from magisk app's "uninstall" button inside the app)

Install your desired magisk app version

RE-hide magisk app now

Then you can use exkm to flash with magisk 24300 and you should be good to go.
[Google Pixel 6 Pro] KillerVamp009:
After testing the latest radio from QPR Beta 3 have not seen this bug. no rebooting in Airplane Mode for the last few days since release.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I can only say that this custom kernel wouldn't be the cause of that. You might want to create a question thread about the issue.
[Google Pixel 6 Pro] Sasaiber:
Thank you very much! Installed =) Tell me, do I need to configure something else after installing the kernel?
[Google Pixel 6 Pro] Jon8RFC:
Happy to help! =)

You don't need to configure anything else. When you use EXKM to flash, it installs the magisk module you need for the kernel. You're all finished!
[Google Pixel 6 Pro] Sasaiber:
Well! Thank you) I hope this will solve the problem with overheating and improve battery time))
[Google Pixel 6 Pro] arvylas:
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

This is a few mins ago. Again with slowdowns but can you check for gms please?
[Google Pixel 6 Pro] Paz9:
Try uninstalling updates to gms.

I remember having this issue on my OP phone when dozing Google services
[Google Pixel 6 Pro] Freak07:
Managed to reproduce the issue. It´s a magisk issue that surfaces probably since 2.0.1 where direct USB access was added and was not kernel related.

To get direct USB access working a firmware file in vendor/firmware is replaced during bootup when my kernel is flashed, which is required for the kernel changes to actually work.

The denylist trick to hide modifications stumbles upon that dir and fails due to a selinux error as denylist is not allowed to access that dir.

As a workaround I fixed that selinux denial and root is no longer being detected by the app. :)

05-08 08:45:40.268 778 778 D Zygote : Forked child process 18269
05-08 08:45:40.269 3697 5245 I AssistantForeground: Get launcher package: com.google.android.apps.nexuslauncher
05-08 08:45:40.269 1579 1769 I ActivityManager: Start proc 18269:com.cm_prod.bad/u0a313 for pre-top-activity {com.cm_prod.bad/com.e_i.bad.controls.activities.StartActivity}
05-08 08:45:40.271 18269 18269 I Magisk : zygisk64: [com.cm_prod.bad] is on the denylist
05-08 08:45:40.274 18269 18269 D Magisk : denylist: Unmounted (/system/bin/magiskpolicy)
05-08 08:45:40.274 18269 18269 D Magisk : denylist: Unmounted (/system/bin/magisk)
05-08 08:45:40.274 18269 18269 D Magisk : denylist: Unmounted (/system/bin/app_process64)
05-08 08:45:40.274 18269 18269 D Magisk : denylist: Unmounted (/system/bin/app_process32)
05-08 08:45:40.275 18269 18269 D Magisk : denylist: Unmounted (/system/bin)
05-08 08:45:40.275 18269 18269 D Magisk : denylist: Unmounted (/product/overlay)
05-08 08:45:40.272 18269 18269 W main : type=1400 audit(0.0:1514): avc: denied { search } for name="firmware" dev="dm-4" ino=722 scontext=u:r:zygote:s0 tcontext=u:object_r:vendor_fw_file:s0 tclass=dir permissive=0
05-08 08:45:40.276 18269 18269 D Magisk : denylist: Unmounted (/dev/G8MMn)
05-08 08:45:40.277 18269 18269 D Magisk : denylist: Unmounted (/system/etc/hosts)
05-08 08:45:40.277 18269 18269 D Magisk : denylist: Unmounted (/system/app/Stk)
05-08 08:45:40.277 18269 18269 D Magisk : denylist: Unmounted (/vendor/etc/powerhint.json)

After flashing the updated zip what I did was hide the magisk app in magisk manager, enable deny list and added the app to the list. Wipe data of the banking app, reboot (not sure if needed but rebooting is always good in these cases) and root was no longer detected by the app.

Attached are zips which include the fix the selinux denial for you to confirm.

This might also fix root detection by other banking apps that are not detecting root on stock kernel, but were broken after flashing the few last releases of this kernel.
[Google Pixel 6 Pro] jericho246:
Wow, fantastic work! I flashed the zip, and can confirm the app no longer detects root. Really good stuff, thank you.
[Google Pixel 6 Pro] shizonic:
Can confirm: My banking app works now too! No root is detected. Great work, thank you!
[Google Pixel 6 Pro] Nightf0x_007:
No im not dozing gms, the modulen already caused me problems before, i figured out what was the problem, google app cleared its data and started to get notifications again
[Google Pixel 6 Pro] spr33:
I'm not sure if anyone else has reported this but I've got a bootloop after attempted to install this latest kernel for QPR beta.

I flashed the beta update, installed Magisk (stable 2.4) and flashed the kernel in FKM which resulted in a bootloop. It gets to the Google logo then restarts

My bad - I forgot to flash the patched boot image and instead I just booted it.. got a feeling that's what caused it!

Confirmed: working fine :)
[Google Pixel 6 Pro] scott.hart.bti:
Anyone else notice heat issues on the latest version? I am on 12.1 may update. Didn't have issues prior to updating. Doesn't happen often, but something like watching a YouTube video for 15 minutes the phone will be excessively warm (it's not burning hot or anything too extreme, but def not normal). Only difference as far as app side is I've installed the magisk aosp mods. Since then I've uninstalled the mod and switched kernels for now and haven't noticed the issue since. So assuming it's gotta be one of the two causing the heat?
[Google Pixel 6 Pro] Freak07:
No heat issues on my end. :)

Higher ambient temps might play a role. But most likely something was happening in background that just ramped up the CPU.

Next time maybe check top command via rooted shell directly on the phone, maybe it'll show something. :)
[Google Pixel 6 Pro] scott.hart.bti:
Thanks for confirming.
[Google Pixel 6 Pro] Gytole:
I have noticed myself that the Pixel 6 Pro just likes to get hot when it wants. I was outside with the screen at FULL brightness, Florida heat and phone was fine. I come in for a glass of water. Set the phone down, play with our bunny for about 10 minutes and grab my phone and it was stupid hot...not even being used! It has a mind of it's own sometimes. Also. Does anyone's get to the point where it literally shuts down? Mine has literally down this 10 times.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I have not had any shutdowns at all in the past 6+ months.
[Google Pixel 6 Pro] 93ae8074:
Fantastic! I can confirm that Momo 4.0.1 doesn't detect Magisk anymore. :) Great job, @Freak07!
[Google Pixel 6 Pro] majorfigjam:
Unfortunately, Momo 4.1.0 now does.
[Google Pixel 6 Pro] rhetorician:
Is it normal to have battery drain upon first installation? I'm on 2.3 with April update and Magisk 24300. I'm noticing substantial battery drain with the screen off-- it's just sitting on my desk.
[Google Pixel 6 Pro] jericho246:
I guess it depends how high the idle battery drain is. I would highly recommend downloading the Battery Guru app from the Play Store. It provides many stats and info about battery life, and it even has "Doze optimization" settings which help reduce idle battery drain, similarly to how another popular app, "Nap Time" works.

Perhaps you have some rogue app that prevents your device from sleeping?

Personally, my screen off/idle drain is around 0.9%-1.6% when on Wifi or mobile data. For the night I always turn off Wifi and data and so the idle battery drain is around 0.5%.

The stats are mostly the same as the stats from my previous phone (S21U) so I guess it's working as intended.

Note: currently, I am on Evolution X 6.3.1 with Kirisakura kernel.
[Google Pixel 6 Pro] rhetorician:
Ok--i'll give that a shot and investigate it more closely. I should have specified that I am experiencing battery drain relative to the stock kernel. I'm on the stock, T-Mobile ROM.
[Google Pixel 6 Pro] bradical711:
Hey your kernel bootloops my pixel 6 oriole may update. will have more details in a bit