Development [Kernel][08.06.2022][Android 12.1.0]Kirisakura 3.0.1 for Pixel 6/Pro aka "RAVIOLE"

[Nemuritor01]

Update to 2.0.1

Hey guys and girls,

So here´s the next update for stable march 12.1.0 firmware! This kernel release is not meant to be flashed on Android 12L QPR3 Beta firmware. (for QPR3 beta kernel check this link, it is not yet updated to beta 1.1)
I´ll update the A12L QPR3 kernel to Beta 1.1 when I find time the next few days.

Android 12 QPR3 Beta 1.1 finally added direct USB access support. It means HiRes Playback via USB C DACs is now supported via the kernel. This release has that change "ported" to stable 12.1.0 march update as that is what most users seem to be still running, including myself.

HiRes playback is confirmed working over HiBy app as well as Neutron Player running stable 12.1.0 march update.
Check twitter for more information and screenshots:

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

This release also tunes the powerhal quite a bit. More tasks are scheduled to the little cluster during screen off.
Camera launching should be improved a bit as well.


I´ll keep the warning for preferably using magisk stable as well here in this post.
Important:
Make sure you´re being rooted with magisk 24300 stable before flashing the kernel. Any magisk version above 24303 will lead to a reboot back to bootloader since android 12.1.0 and A12L QPR3 Beta. At the moment this only affects canary, but I put the warning just in case this will not get resolved in upstream magisk in time until the next stable drops. I saw a post that some modules also have problems with latest canary, so there´s a lot going on at magisk´s side at the moment.
A post containing a short write-up how to "downgrade" magisk can be found following this link.


In case some did not have time to update their device to stable march and did not read the 2.0.0 release post I´ll keep this here as well:
This update has stable march 12.1.0 firmware merged (we already had most of this code, but the device specific drivers needed to be adjusted properly) and some other small fixes.
In case you missed it, since most people update their device once a new firmware is out each month, the previous release had the dirty pipe exploit fixed. This exploit is not fixed in the stock kernel on march stable 12.1.0 yet.
I´ll attach a link to the release post of 1.8.4 with a detailed changelog again, so changes are not missed. This post also contains info and links regarding the dirty pipe exploit. Link to 1.8.4 release post



Changelog:
- changelog for 2.0.0 in case it was missed
- add direct usb access which allows HiRes music playback over USB C DACs via HiBy or Neutron
- tune powerhal to reduce idle drain (schedule more tasks on little cores)
- improve camera launching


Download:

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

Instructions can be found in the OP! Please follow the instructions to avoid any issues and read this post carefully. Don´t use magisk canary 24303 or more recent!
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.

Hi, I was one of the first guys to report this issue, with DAC problems.
I've had the Beta installed on my pixel 6 pro, few weeks ago. When I tested it, it did not work properly, as far as I can state:
- Yes, Hibby App played music, but just phones native (processed) sampling rate. Most tracks just 24/48
Before the BeTaa Rom Hibby did not play music at all.
- USB audio Player pro played no music. Still error message.
- Neutron similar as Hibby App

So from my point of view, it a progress, that some apps play music, but I do not believe they really make use of the DACs full capabilities.
At least kn my devise. Few weeks ago (before I read this article) I switched back to the stable ROM, because of battery drain issues with the beta ROM. So I can not test right now.
Can you check if the apps are playing the correct bit rates?

 

[swieder711]

Running April update with Root using Magisk 24301 and Kiris 2.0.1.

All is good.

 

[Lughnasadh]

I see what you did there
While the kernel doesn't necessarily needs to be bumped to 5.10.102 to include the fix as the commit was merged separately to a few branches already, there's confirmation now.

Source for April dropped, it's not included.

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

Next update will allow adjusting vibration strength back to higher strength via the CleanSlate config app, thanks to @tbalden 's relentless work!



Alright I'm off for today. See you all tomorrow!

For what it's worth, thought you and others might find this interesting if you haven't seen it yet.

"Samsung, on the other hand, seems to have patched the Dirty Pipe vulnerability on its affected devices with the April SMR (security maintenance release)."

April Security Update Doesn't Fix Dirty Pipe Vulnerability... Or Does It?

Google has released the April 2022 security update to its Pixel phones but it doesn't seem to have patched the Dirty Pipe vulnerability.

www.androidheadlines.com

 

[Freak07]

Update to 2.1.0

Hey guys and girls,

Alright here´s the next update. And it´s again a really big update!
A few weeks ago google pushed a backport of Multi-Gen LRU for the 5.15 kernel to their aosp/kernel common branches. I went ahead and backported that to our 5.10 tree alongside other mm-improvements from linux-mainline. By now google pushed their own backport for 5.10, but I decided to go with my original implementation as it contains a lot more improvements alongside the main Multi-Gen LRU backport and ran stable for well over 3 weeks.

Powerhal was adjusted quite significantly too. CPU-freqs are restricted to 1.1GHZ max during screen off/device idle operations to save more power. App launches and camera operation are improved as well in the powerhal. General usage benefits from those changes too.

Latest linux-stable, f2fs-stable and kernel/common were merged as well.

Users that decide to not use the CleanSlate features and don´t install the apps won´t see the kernel parsing for the config files extensively.
Vibration Booster from CleanSlate was improved as well to kind of counter the weaker haptic feedback since the March update. Please check the linked thread from the changelog. Huge thanks to @tbalden for this. If you want to give a little bit back consider purchasing the apps via playstore or maybe a small donation.



I´ll keep the warning as to preferably using magisk stable to avoid potential issues as well here in this post.
Please note that 24305 works fine for me though on non beta, stable April firmware!
Important:
Make sure you´re being rooted with magisk 24300 stable before flashing the kernel if you´re unsure. Any magisk version above 24303 might potentially lead to a reboot back to bootloader since android 12.1.0 and A12L QPR3 Beta. At the moment this only affects canary, but I put the warning just in case this will not get resolved in upstream magisk in time until the next stable drops. I saw a post that some modules also have problems with latest canary, so there´s a lot going on at magisk´s side at the moment.
A post containing a short write-up how to "downgrade" magisk can be found following this link.



Changelog:
- Update for April Source
- Linux-stable merged to 5.10.109
- f2fs-stable merged
- fixes and improvements from kernel/common including several subsystems
- multi-gen LRU ( more info here, here as well and here)
- general LRU improvements from Linux-Mainline
- improve camera performance by tuning the powerhal during recording
- improve app launches via powerhal
- restrict maximum CPU-Freqs during screen off/ idle to 1.1GHZ for all clusters to save power
- remove cleanslate config files getting parsed excessively even if user did not install the CleanSlate apps
- improve vibration boosting feature in CleanSlate config app to allow stronger vibration again(please have a look at this post )
- other fixes for CleanSlate features such as sweep to sleep
- updated anykernel 3 zip, thanks to @osm0sis
- probably a lot more I forgot as time is short for me.


Download:

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

Instructions can be found in the OP! Please follow the instructions to avoid any issues and read this post carefully. Don´t use magisk canary 24303 or more recent to avoid potential issues!
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.

I wish everybody a great day/evening!
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

 

[roirraW "edor" ehT]

Thanks @Freak07! Now patiently waiting for AFH to quit the spinning "Searching for mirrors...". (both in Chrome on Windows and on Android)

Edit: I Control-F5'd and it loaded almost immediately on the PC.

 

[awakener777]

Of course I just updated Magisk prior to installing April update

 

[scott.hart.bti]

@Freak07 fantastic work as always. Thanks for the quick update. You are always on top of it.

 

[a63548]

@Freak07 You are simply amazing! Thank you so much for such a wonderful kernel. Also just a heads up the thread date still is for March I think instead of April

 

[bigJbig]

Sorry if it is off topic.

I am on the April patch and using Kirisakura latest 2.1.0 kernel. Bank Apps detected root. I have config Denylist, rename the Magisk App, and even frozen it. However, bank apps still detected root. When I flash back to the stock kernel or CleanSlate, bank apps work fine and can't detect root.

 

[Freak07]

Hi, I was one of the first guys to report this issue, with DAC problems.
I've had the Beta installed on my pixel 6 pro, few weeks ago. When I tested it, it did not work properly, as far as I can state:
- Yes, Hibby App played music, but just phones native (processed) sampling rate. Most tracks just 24/48
Before the BeTaa Rom Hibby did not play music at all.
- USB audio Player pro played no music. Still error message.
- Neutron similar as Hibby App

So from my point of view, it a progress, that some apps play music, but I do not believe they really make use of the DACs full capabilities.
At least kn my devise. Few weeks ago (before I read this article) I switched back to the stable ROM, because of battery drain issues with the beta ROM. So I can not test right now.
Can you check if the apps are playing the correct bit rates?

Your best bet is to flash back the beta and submit the feedback directly to Google if it´s not working as expected.
It´s on Google to add proper support for that. Once proper support is added apps might need to be updated to work correctly on the Pixel 6 since it´s kind of a "new" SoC.
You can let the UAPP devs know on their forum that Google started adding support on the A12L beta and see if they can start working on it.

It says 44kh/16bit during playback of a flac downloaded from bandcamp when using my dragonfly DAC via hiby.

For what it's worth, thought you and others might find this interesting if you haven't seen it yet.

"Samsung, on the other hand, seems to have patched the Dirty Pipe vulnerability on its affected devices with the April SMR (security maintenance release)."

April Security Update Doesn't Fix Dirty Pipe Vulnerability... Or Does It?

Google has released the April 2022 security update to its Pixel phones but it doesn't seem to have patched the Dirty Pipe vulnerability.

www.androidheadlines.com

It´s interesting that Samsung pushed ahead there and also great to see that some OEMs take the initiative and push ahead of the Google bulletin there.
I know for example that HTC in the past was pretty much up to date with security fixes ahead of the "official" android security update fixes.
But it requires testing and more resources to diverge so most OEMs are just happy to stick with whatever Google provides.


I checked the kernel build date of stock April kernel yesterday. It dates January 21st, the fix for dirty pipe was pushed February 20th to Linux.

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

Sorry if it is off topic.

I am on the April patch and using Kirisakura latest 2.1.0 kernel. Bank Apps detected root. I have config Denylist, rename the Magisk App, and even frozen it. However, bank apps still detected root. When I flash back to the stock kernel or CleanSlate, bank apps work fine and can't detect root.

The kernel has nothing to do with an app detecting root, at least I didn´t hear of any app that would check anything there. Are you sure it´s not just the reboots that fix it temporarily while flashing back stock?
Google pay works fine for me on my end and safetynet is passing as well.

Did you try flashing the universal safetynet fix to make sure you´re passing safetynet as well?
If your specific banking app really detects something that´s unique to my kernel it might be hard to fix. You can tell me which app and I can test on my end too if it´s available for download here. But if it requires a login to fail, you might need to check the logs.

 

[bigJbig]

Your best bet is to flash back the beta and submit the feedback directly to Google if it´s not working as expected.
It´s on Google to add proper support for that. Once proper support is added apps might need to be updated to work correctly on the Pixel 6 since it´s kind of a "new" SoC.
You can let the UAPP devs know on their forum that Google started adding support on the A12L beta and see if they can start working on it.

It says 44kh/16bit during playback of a flac downloaded from bandcamp when using my dragonfly DAC via hiby.



It´s interesting that Samsung pushed ahead there and also great to see that some OEMs take the initiative and push ahead of the Google bulletin there.
I know for example that HTC in the past was pretty much up to date with security fixes ahead of the "official" android security update fixes.
But it requires testing and more resources to diverge so most OEMs are just happy to stick with whatever Google provides.


I checked the kernel build date of stock April kernel yesterday. It dates January 21st, the fix for dirty pipe was pushed February 20th to Linux.

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

The kernel has nothing to do with an app detecting root, at least I didn´t hear of any app that would check anything there. Are you sure it´s not just the reboots that fix it temporarily while flashing back stock?
Google pay works fine for me on my end and safetynet is passing as well.

Did you try flashing the universal safetynet fix to make sure you´re passing safetynet as well?
If your specific banking app really detects something that´s unique to my kernel it might be hard to fix. You can tell me which app and I can test on my end too if it´s available for download here. But if it requires a login to fail, you might need to check the logs.

Thank you for your reply.

Yes, I flashed universal safetynet fix and it is
passed. Gpay is also working fine.

The bank app is call HSBC and CITI BANK.

 

[slickrasta]

This won't work on my Pixel 6 updated to the 12.1.0 April update, always gets stuck in boot loop. I'm manually flashing 2.1.0 after installing powerhint v9 and patching the boot.img using Magisk stable 24300 when that failed I tried 24305 as well. Downloaded multiple times, patched multiple times. After I flash all 4 files using the commands below it just gets stuck in a boot loop. I even tried flashing the 3 files before vendor_dlkm and vice versa, no luck. I'm very confused why others report no issues. Can someone help me?

adb reboot bootloader
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot bootloader
fastboot flash dtbo dtbo.img
fastboot flash boot magisk_patched.img
fastboot flash vendor_boot vendor_boot.img

 

[Lycidias]

Thanks new build is working awesome on raven April update

 

[spr33]

Just wanted to double check that the latest release works on the L beta before flashing?

 

[shizonic]

Sorry if it is off topic.

I am on the April patch and using Kirisakura latest 2.1.0 kernel. Bank Apps detected root. I have config Denylist, rename the Magisk App, and even frozen it. However, bank apps still detected root. When I flash back to the stock kernel or CleanSlate, bank apps work fine and can't detect root.

I have exact the same situation! With stock kernel everything works including my bank app. If I flash the kernel 2.1.0 SafetyNet passes still, but my bank detects root and won't open... I tried everything... Including clearing files of Google Play Services, multiple reboots, etc.

My bank app is "PostFinance". But I saw that the "Xiaomi Home" detects root too even if the app opens... It just gives a short message which says that root was detected.

 

[daniel.1983]

I have exact the same situation! With stock kernel everything works including my bank app. If I flash the kernel 2.1.0 SafetyNet passes still, but my bank detects root and won't open... I tried everything... Including clearing files of Google Play Services, multiple reboots, etc.

My bank app is "PostFinance". But I saw that the "Xiaomi Home" detects root too even if the app opens... It just gives a short message which says that root was detected.

Same here, my bank app is VR SecureGo plus. I already got this issue with the previous version of this kernel.

 

[awakener777]

Thank you for your reply.

Yes, I flashed universal safetynet fix and it is
passed. Gpay is also working fine.

The bank app is call HSBC and CITI BANK.

I'm on stock kernel. I also use Citi bank app and it always detects root. Hiding root used to work, but it seems it no longer does. No issues with other banking apps (I don't use HSBC). I'm not sure why this is.

 

[kevp75]

I'm on stock kernel. I also use Citi bank app and it always detects root. Hiding root used to work, but it seems it no longer does. No issues with other banking apps (I don't use HSBC). I'm not sure why this is.

Mine did the same... initially... I'm old school, coming from SuperUser to Magisk, to now..,. newer Magisk that no longer has MagiskHide...

I had to go to Preferences, then enable Zygisk, and then add my bank app, my card app, and my health insurance app to the deny list, and then they worked fine.

 

[roirraW "edor" ehT]

This won't work on my Pixel 6 updated to the 12.1.0 April update, always gets stuck in boot loop. I'm manually flashing 2.1.0 after installing powerhint v9 and patching the boot.img using Magisk stable 24300 when that failed I tried 24305 as well. Downloaded multiple times, patched multiple times. After I flash all 4 files using the commands below it just gets stuck in a boot loop. I even tried flashing the 3 files before vendor_dlkm and vice versa, no luck. I'm very confused why others report no issues. Can someone help me?

adb reboot bootloader
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot bootloader
fastboot flash dtbo dtbo.img
fastboot flash boot magisk_patched.img
fastboot flash vendor_boot vendor_boot.img

I had the same problem, but I wanted to wait to see if anyone else reported it.

I always use the full firmware flash with -w removed, I then boot up stock unrooted, make sure everything's working, then go back to fastboot and flash the stock rooted kernel, then I normally flash the custom kernel.

What didn't work for me at this point (use ExKM to flash the custom kernel):

• Flashing 2.1.0 from the stock rooted kernel - the 2.1.0 package didn't detect my Magisk Stable v24.3 rooted stock kernel.
• I then did the full flash-all.bat again (still without -w), and repeated the process - stock kernel, stock rooted kernel, then flash custom 2.1.0. It always resulted in bootloops.
• There are some other variations of things I tried that didn't work.

What worked for me:

• From the stock rooted kernel, I flashed the 2.0.1 package, which detected my Magisk Stable v24.3 rooted stock kernel and applied Magisk to the 2.0.1 kernel.
• Rebooted
• With the rooted 2.0.1 kernel successfully working, I then flashed 2.1.0 and it detected Magisk, and everything worked 100%.

Apologies @Freak07 - I haven't grabbed logs...yet.

 

[cmh714]

For me, IIRC, I flashed the new kernel (wasnt watching the screen), and then when I looked over it was finished, but the device hadnt rebooted.......so I just flashed again, watching the screen this time, and it rebooted and came up fine....TY for all your efforts!!!