yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
Please read the release post and as it's mentioned in the release post also the instructions in the OP.

That will do as well (y) most importantly it's below 24303!
[Google Pixel 6 Pro] nafi2000:
Thanks. It's working well after installing new magisk and I ddnt reflash anything.
[Google Pixel 6 Pro] ttle54:
I flashed the 2.00 kernel this morning on my March updated Pixel. Everything is working fine so far, no complaints. Thank you for the hard work and dedication.
[Google Pixel 6 Pro] swieder711:
I have been calling this 24.301. I guess the correct name is 24301.
[Google Pixel 6 Pro] dubt17:
I'm still on magisk 24301 so I flashed 2.0 via FKM and am noticing MASSIVE improvements in standby drain over 1.89L on Proton 12.3.

Still smooth as butter 🤙
[Google Pixel 6 Pro] irule311:
Thank you! Somehow I missed this. Yes, I am indeed trying to load this against the stock kernel as a separate module. I've tried changing it here as well as simply adding it to the stock kernel sources, but haven't been able to create a working module out of it. I'm always getting an unknown symbol error in dmesg when I got to run insmod ("xt_register_targets"/unregister) which doesn't appear to be due to module verification. I just made a new thread about this particular question and would really appreciate it if you had any insights regarding how to get this working.
[Google Pixel 6 Pro] dr_rick13:
hi everyone, I apologize if that has already been asked -- I looked but couldnt find much.

I am currently on Radioactive kernel, if I want to flash this one here, do I HAVE to go back to stock first? or can I flash over it in EXKM?

Thanks all.
[Google Pixel 6 Pro] Alxoom33:
Are you making a kernel compatible with A13 DP2?
[Google Pixel 6 Pro] Freak07:
Probably works fine, if you want to avoid any issues follow the instructions to restore stock kernel in the FAQ. (one of the first posts on this thread.

No, I don't have the time for that unfortunately.
[Google Pixel 6 Pro] Alxoom33:
Thanks for your response!
[Google Pixel 6 Pro] acidspider:
Is anyone running on 24304?
[Google Pixel 6 Pro] jcp2:
Not I. Stable 24300. As The saying goes "if it ain't broke, don't fix it!" ;)
[Google Pixel 6 Pro] acidspider:
My device got corrupt boot thingy before I updated to march build and all sorts went pear shaped and wasn't booting so was doing all sorts to sort it without wiping data, and I'm so I'm all updated now but lost count how many bootloop-safemodes I've had to do, still kernel to go
[Google Pixel 6 Pro] NYCHitman1:
To be fair.. the saying is "if it ain't broken, don't fix it!"
[Google Pixel 6 Pro] a63548:
Sorry for the off topic, but I sure miss DU :cry: I remember following your build page for OnePlus 5 test builds. :)
[Google Pixel 6 Pro] neekless:
@Freak07 hi what's the process to update abi when building a kernel?
[Google Pixel 6 Pro] Freak07:
I do on stable 12.1.0 march update. But there still seem to be some issues with certain magisk modules and maybe other potential unidentified issues. If you don´t want any issues just stay on stable, which I guess should work fine. :)

Android Kernel ABI Monitoring | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] Nekromantik:
off topic but I miss Dirty Unicrons! haha was the best custom ROM from the old days.
[Google Pixel 6 Pro] danii3dot:
I am.
[Google Pixel 6 Pro] acidspider:
I tried flashing in exkm but got corrupt again.
[Google Pixel 6 Pro] danii3dot:
I am on the stock kernel for now waiting for an update.
[Google Pixel 6 Pro] swieder711:
This kernel works great with Magisk 24301. Why not use it with this Kernel?
[Google Pixel 6 Pro] Freak07:
Follow the instructions in the FAQ, involving flashing an older boot.img to get rid of the corruption message.

There still seem to be users running into this corruption issue. Unfortunately there´s nothing I can do about it. The last few Magisk canary releases and some google stuff seems to be wonky, as google faces the corruption issues themselves and dropped a patch note about it.

The issues some users are getting unfortunately have nothing to do with the kernel. It´s a mixture of google having some problems with the corruption thingy themselves as they revealed in the patchnotes and the other issues are due to magisk canary being experimental canary builds.

If everything is "working as expected" on a device and you follow the instructions in the OP and the release post, flashing should go without a hitch.

Good question ;)
[Google Pixel 6 Pro] vassosman:
FWIW QPR3 B1.1 is running 5.10.81 BD: Feb 9 18:57
[Google Pixel 6 Pro] Prey521:
Switched to Magisk Beta and all is well now.....this kernel rocks!
[Google Pixel 6 Pro] Freak07:
thanks for the info :)

what´s even better:

https://twitter.com/i/web/status/1507397884941115428

great to hear. (y)
[Google Pixel 6 Pro] vassosman:
Saw that. Loved it. Can't wait for the next kernel.
[Google Pixel 6 Pro] dubt17:
I hope this also opens up UVC capture card support 🤞
[Google Pixel 6 Pro] ttle54:
I'm in love with the 2.00 Kirisakura Kernel so far. Great battery performance, stability and no crash at all.
[Google Pixel 6 Pro] krystiano:
New kernel on board 🥰🥰
[Google Pixel 6 Pro] ttle54:
Installed the latest 2.0.1 Kirisakura Kernel and no boot lops nor crash. Things are running great, confirmed.
[Google Pixel 6 Pro] vassosman:
Really making me debate switching to the March Update for this lmao
[Google Pixel 6 Pro] dubt17:
Launching the camera feels the same on 2.01, but closing it now is instant, on 2.00 it lagged a bit each time, now it's 🧈
[Google Pixel 6 Pro] knopie:
Nice, I was waiting for this fix. Thanks.
[Google Pixel 6 Pro] DanielF50:
Awesome work on 2.0.1!

Maybe a stupid question, but was the below ever looked into? I still see it happening in my logcat every few seconds if I don't have the Cleanstate apps installed (I don't need need them) & also seem to have the selinux permissive 1/0 thing happening after it looks for those config files too.

03-26 12:41:39.950 16208 16208 E : [uci]File Open Error:/storage/emulated/0/Android/data/org.cleanslate.csconfig/cache/uci_user.cfg -2
03-26 12:41:39.950 16208 16208 I : parse_uci_cfg_file [uci] cannot read file /storage/emulated/0/Android/data/org.cleanslate.csconfig/cache/uci_user.cfg
03-26 12:41:39.950 16208 16208 I : set_kernel_permissive --- setting to: 0, kp usage count: 0
03-26 12:41:39.950 16208 16208 I : set_kernel_permissive --- setting to: 1, kp usage count: 1
03-26 12:41:39.950 16208 16208 I : set_kernel_permissive --- setting to: 0, kp usage count: 0

Edit: I'm not too worried about it logging that the config files can't be found, but I am definitely curious about the selinux bit - is this just something that's supposed to be written to the missing file(s), or is selinux being switched from enforcing to permissive constantly (doubt this)? If I create those files manually, will these messages stop showing up?
[Google Pixel 6 Pro] Freak07:
Yeah. Discussed it with @tbalden a while ago and we concluded for now it doesn't hurt anything.

Sleep/performance is not impacted as that's just a kernel operation, but with a log that's being printed, which is visible to you.

If you worry about the selinux thing. It just changes a few selinux rules very very briefly (you can check them on my git) to permissive for kernel context (not apps, untrusted app, services etc), so the config file can get parsed.

It doesn't switch selinux completely permissive or disables it.

One of the problems is when to stop polling. If the device is up for a certain amount of time, and the CleanSlate apps are being installed later, if a time based limit is imposed it would break.

Similarly if the device is booted, time limit for polling passes but user hasn't yet unlocked, it would break.

I can remove the lines from printing to the log. But then you just won't see those lines appearing.

Also some debugging lines can be helpful when hunting bugs.

Some debug lines being printed to the kernel log, do not harm battery life/performance in a way that's clearly perceptible in real world usage.

I talked to @tbalden just now and maybe the retry isn't needed any longer. :)

It's being looked into and maybe another solution is found in one of the next releases. But for now, nothing really to worry about.

Edit: @DanielF50 should be gone in the next release. ;)

uci: make cfg parse on init optional · tbalden/android_kernel_gs_raviole@ae1cf1a

On newer androids it's not possible to parse the files before a user process touches sdcard, so it's useless to try and also adds a lot of unneeded logging too, when someone does not use th...

github.com
[Google Pixel 6 Pro] DanielF50:
Awesome, I was kind of worried that it allowed apps/services use of selinux in permissive mode, but that's great to know - thank you for the in-depth explanation! 🙌
[Google Pixel 6 Pro] bs3pro:
Nice work! Will color controls be added? My p6 has the worst green push, and colors are muted as fck.
[Google Pixel 6 Pro] x56x:
How do I run post defconfig commands so I can run make menuconfig?
[Google Pixel 6 Pro] vibrantliker:
Just curious, the boot. img in the op, won't that be different than the version I need (P6)?
[Google Pixel 6 Pro] ne0ns4l4m4nder:
nope it works i use this on my P6
[Google Pixel 6 Pro] x56x:
From my understanding, the base of the kernel is the same, just the drivers, modules, etc. are separate. Google is unifying the kernels when they release new devices now.
[Google Pixel 6 Pro] xflowy:
guys is there a telegram group?
[Google Pixel 6 Pro] xflowy:
Can someone explain what this means?
[Google Pixel 6 Pro] rav101:
If you have already rooted your phone, I would assume you have used the latest Magisk Canary to do this. You would have installed the Magisk Canary app and selected the option to patch a boot.img which you would then have flashed to your phone using fastboot.

If you want to maintain root on this device whilst using this Kirisakura kernel, you will need to patch the boot.img that Freak07 has provided in the same way before flashing it in the order he has suggested in the original post.

If none of this makes sense to you, I would strongly suggest you look around the Pixel 6 Pro XDA around guides to unlock and root your device.
[Google Pixel 6 Pro] rav101:
No,

This has already been asked and answered by Freak07 within this thread.
[Google Pixel 6 Pro] belair56:
Example fastboot boot XXXXXX.img where the XXXXXX is the name of your patched boot image.
[Google Pixel 6 Pro] xpdragon:
My understand is after you download the boot.ing, you will need to patch it with Magisk and then replace the boot.img filename with the name of your patched boot.img file.

fastboot flash boot boot.img
[Google Pixel 6 Pro] vibrantliker:
anyone know why I would be stuck in fastbootd mode like this: (waiting for any device?)
[Google Pixel 6 Pro] cultofluna:
Use latest platform tools
[Google Pixel 6 Pro] Burt Squirtz:
Only you don't. If you're already rooted on his kernel , all you have to do is patch his boot image release with magisk, and then take that new patched image and flash with FKM.

I didn't think this would work at first, but this is confirmed working by me, despair dev and a slew of others.
[Google Pixel 6 Pro] Freak07:
That way you won't get any changes that end up in the vendor_dlkm for example.

You still need to boot to fastbootd to flash vendor_dlkm.

No clue if fkm supports flashing a dtbo.img. Same logic applies there. If you don't flash it and there are changes in there you will miss them.

I already answered the question here:

https://xdaforums.com/t/kernel-11-1...pixel-6-pro-aka-raviole.4358435/post-85929677

Next version will modify vendor_dlkm. Patching boot.img and flashing via fkm or exkm will not be enough.

Follow the instructions in the first post and there won't be an issue now or in future releases.
[Google Pixel 6 Pro] xflowy:
Getting installation failed due to being unable to unpack boot image when trying to patch the boot.img in magisk. any ideas?
[Google Pixel 6 Pro] craigacgomez:
You need Magisk Canary. The stable version of Magisk won't work with the Pixel 6 boot images.
[Google Pixel 6 Pro] boxemall:
will this kernel have passthrough charging? i got a pixel 6 couple days ago but didn't find out if it has passthrough charging. would be an awesome way to preserve battery life.

regards
[Google Pixel 6 Pro] Texan1:
Fantastic to see @Freak07 developing for the Pixel 6 Pro!

Being a previous OnePlus 7 Pro user, this kernel was always one of my favourites. I've been out of the rooting and flashing game for a couple of years now (last phone was an Oppo Find X2 Pro, excellent phone) and so following all of these instructions was quite a grind again and I certainly don't remember it being this complicated when I was flashing my OnePlus?! Hopefully an easier method is found but for now Kirisakura is flashed!
[Google Pixel 6 Pro] ne0ns4l4m4nder:
It gets easier the more you do it tbh, takes me about 5mins to reflash the newest images when he uploads them. I'm pretty sure there's a flasher someone posted here the other day
[Google Pixel 6 Pro] Utini:
Works fine as always :)
[Google Pixel 6 Pro] bigJbig:
Updated to 2.0.1 version. But somehow it breaks some of the banking apps, thus those apps detected root. And it doesn't happen when I switch to other version of the kernel.
[Google Pixel 6 Pro] krystiano:
Clear cash/data ,set up again banking app and should be ok.

It happens for me on Both Barclays and Lloyds app. Now ok
[Google Pixel 6 Pro] TheLoonyRebel:
Am I able to flash 2.0.1 over 2.0 or should I do the clean flash by restoring the stock stuff and Magisk boot?
[Google Pixel 6 Pro] :
Dirty flash works flawless
[Google Pixel 6 Pro] Admiral2145:
I'm on magisk 24.3beta 3-10-22 build... Every time I flash the March boot imaged patched it boot loops right after the Google logo... What am I doing wrong to gain root access and then to flash this kernel?

Tia
[Google Pixel 6 Pro] krystiano:
Change magisk for stable channel.
[Google Pixel 6 Pro] Admiral2145:
I just uninstalled and reinstalled put on stable channel... Still showing 3-10-22 magisk... I'll report back
[Google Pixel 6 Pro] krystiano:
I'm on stable channel and same date.

No problem with boot lops.
[Google Pixel 6 Pro] Lughnasadh:
Stable 24.3, Beta 24.3 and Canary 24301 should all be the same Magisk version. Since the Stable 24.3 release on March 10, only the Canary channel has been updating (currently at 24304).
[Google Pixel 6 Pro] Lughnasadh:
Do you have any mods installed that may be causing it?
[Google Pixel 6 Pro] krystiano:
Also after update to march before patch boot.img I disabled all modules ,just in case
[Google Pixel 6 Pro] Admiral2145:
I'm back in the game... About to flash kernel... Thx again
[Google Pixel 6 Pro] Lughnasadh:
Just curious what the problem was...so others may learn from your experience.
[Google Pixel 6 Pro] Admiral2145:
Went to stable channel from Beta Channel... Nothing more nothing less.
[Google Pixel 6 Pro] neekless:
@Freak07 what's your process for merging f2fs-stable? Just merge and fix conflicts? It seems like you don't pick every commit. Just wondering how do you choose what to pick?
[Google Pixel 6 Pro] Freak07:
It depends.

Some commits are already in googles tree prior, some issues are fixed ahead or differently in googles tree or Linux stable or akc, some are not compatible with android/device specific changes.

Similar to merging linux-stable it´s based on experience, guesswork, testing the changes and then deciding.

Next release will probaby have the latest f2fs-stable, which dropped a few days ago, merged if testing goes well.

Google also merges f2fs-stable quite regularly, since approx a year ago. So usually I have confirmation if Google follows my decision a few months later.
[Google Pixel 6 Pro] shizonic:
Only works until next reboot.
[Google Pixel 6 Pro] krystiano:
Try use app for freeze banking app.

Set app ,check if working, freeze them and reboot.

After reboot freeze magisk - unfreeze banking app and check is ok or not.

I'm doing like this for Lloyds app. Barclays working fine

Didn't find others solutions at the moment
[Google Pixel 6 Pro] drew071:
Have you hidden magisk? Some apps look for magisk, in settings there is an option to hide magisk manager, as in it gets renamed to a different apk
[Google Pixel 6 Pro] krystiano:
Of course.

Hide app,

Configure DenyList aswell.

Working when I freeze....
[Google Pixel 6 Pro] drew071:
Bank with nationwide. They don't check for root 😂
[Google Pixel 6 Pro] krystiano:
I think we should stop talking about this in here.

This thread is about kernel 😉😉
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yep, this is the appropriate place -> [How To Guide] Working SafetyNet with Pixel 6 Pro Android 12
[Google Pixel 6 Pro] shizonic:
Thank you, I gonna try this. Can you suggest any app for freeze?
[Google Pixel 6 Pro] roirraW "edor" ehT:
This is off-topic to this thread, which is about the Kirisakura custom kernel for the Pixel 6 and Pixel 6 Pro. If you use XDA's search function, you'll find all sorts of recommendations for freezing apps.
[Google Pixel 6 Pro] pro_b:
Anyone got an alternative link to latest kernel 2.01 for Raven? I'm getting no mirrors found on AFH and it's not downloading.
[Google Pixel 6 Pro] Freak07:
seems like AFH has a problem at the moment.

there you go
[Google Pixel 6 Pro] ctfTijG:
Hi!

Thank you for this amazing kernel. Any news on the S3B1 (12L - v1.1 beta) release of your kernel?
[Google Pixel 6 Pro] xtravbx:
So if I'm on latest Magisk I CANNOT flash this kernel?
[Google Pixel 6 Pro] bush911:
with latest beta or Canary magisk, you are more likely to get corrupted message while booting after flash third-party kernels, if you didn't previously disable those flags
[Google Pixel 6 Pro] xtravbx:
Thank you. I just ran the latest stable instead.

Is there a configuration partner app that goes with this?

I flashed this kernel, I thought the description made a lot of sense over stock.
[Google Pixel 6 Pro] bush911:
I am not pretty sure about that. I just use EXKM to manage wakelocks, everything else are by default for me
[Google Pixel 6 Pro] scloutkst:
I'm trying to track down the source of poor battery life on the march update. Better battery stats does no show any information on kernel wake locks. Only partial wakelocks. However the graph option shows my phone in a constant wakelocks state when screen is off. I tried to use adb and the dumpsys power command to check wake locks and it says no cached wake locks. Could any changes in the kernel or the ak3 magisk module with this kernel cause wakelocks monitoring to break?

Adb command: adb shell dumpsys power | findstr -i wake_lockthisnreturns: no_cached_wake_locks=true

Thinking of going back to stock kernel to check but figured I may ask here first.

I'm not sure but perhaps the command I'm using is outdated for Android 12? Some light digging shows that better battery stats might be semi broken on Android 12 as well. This seems to be the case for all battery monitoring software. Nothing I have used seems to show apps behaving weirdly when even the built in android battery monitor shows them sucking up power.

I don't think the battery issue is related specifically to this kernel, but not sure if the monitoring is.
[Google Pixel 6 Pro] Freak07:
Hey :)

you´re welcome. Once I find time ;)

You don´t need to change any kernel parameters. Everything that´s intended to be set is done on boot automatically via either ramdisk or the ak3 helper module that gets flashed alongside the kernel.

If you want to control sweep to sleep and the other CleanSlate features please check the CleanSlate thread for those apps (y)

I haven´t noticed any regression in battery life on my end since march update. But unfortunately your issue could be due to many things. Broken app update, service stuck in background, bad reception due to some network changes...

As far as I´m aware A12 broke wakelock monitoring in most if not all apps. Check the better battery stats thread, there´s a command to at least get some functionality back. Don´t know about kernel wakelocks though.

You can check the total amount of kernel wakelocks time via EXKM or FKM. But there´s no option to either factor in charging time, screen on/off etc, which makes it pretty rudimentary and of not much use. As you´ll also see charging related wakelocks for example.

Don´t block kernel wakelocks there, they are needed for the device to work properly.

I´d recommend taking a look at battery historian. That inbuilt tool works just fine for me. Just take a bug report on your phone, feed the bug report to the browser interface and you´ll get a lot of information. Maybe you´ll be able to identify the cause with this tool.

on another note. AFH seems to be working correctly again.
[Google Pixel 6 Pro] Lughnasadh:
@Freak07 Just wanted to report....Canary Magisk 24305 was released today so I updated to it on Kiri version 2.0.1, March 12.1 Stable build and everything is good 👍
[Google Pixel 6 Pro] EndlessBliss:
I noticed Mile mentioning that Tidal doesn't work correctly. Oddly, I did have direct access playback in Tidal yesterday (it asked for direct access when the DAC was connected). Today, it stopped giving that prompt and doesn't get direct access. Not sure what changed

Kiri 2.01, March 2022 stable, Magisk 24.3 stable
[Google Pixel 6 Pro] drew071:
Do i have to be rooted to run this kernel or will it work fine without magisk?
[Google Pixel 6 Pro] Freak07:
Check the requirements in the first post :)
[Google Pixel 6 Pro] drew071:
I did, i was hoping magisk wasnt mandatory
[Google Pixel 6 Pro] Freak07:
That's not possible as this kernel is quite far from stock, which makes it necessary to change a few files in other parts of the firmware. There's no other way except systemlessly overlaying those files via magisk during bootup.
[Google Pixel 6 Pro] drew071:
I see. Well if i ever root i will be sure to give it a go. Thanks for repsonding
[Google Pixel 6 Pro] Beachbum2049:
I had the same problem. It was present on Kiri and stock rooted kernel for me. I think it was Better Battery Stats itself causing an issue. I use EXKM & BBS to monitor battery usage. With BBS installed, I was seeing 3-4% idle drain with default BBS settings ie no active monitoring, according to EXKM. Once I uninstalled BBS, the idle usage according to EXKM is slowly decreasing. Ironic, but with a shot to uninstall BBS and see what happens.
[Google Pixel 6 Pro] scloutkst:
Will do. Thanks.
[Google Pixel 6 Pro] thieftime1980:
it is worth installing the karnel trn as it is on the battery, as in the stock ?
[Google Pixel 6 Pro] Lughnasadh:
Battery is slightly better than stock.
[Google Pixel 6 Pro] thieftime1980:
How to check what version of android I have, whether it is version 12 or 12.1 or another 12.l ?
[Google Pixel 6 Pro] Admiral2145:
Are you on March update... If so you're on 12.1 aka 12L
[Google Pixel 6 Pro] thieftime1980:
how do i have the march update tk can i upload this kernel?