Development [Kernel][03.05.2022][Android 12.1.0][Android 12.1.0 QPR Beta 2] Kirisakura 2.4.0 for Pixel 6/Pro aka "RAVIOLE"

Search This thread

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,530
18,328
Does this kernel need disabled verify and verification? I am just rooted and used the latest magisk canary on november build.
So I think both are enabled for me.

Thanks
The information you're looking for is in this post, which I found by choosing the "Search This thread" button at the top of each page in a thread, typed verity as a search term, and for the username of posts to search in this thread I typed Freak07, then looked to see which search result was the most recent: https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86109665

It also turns out I could've just followed the link in the OP for the changelog to the most recent version:
don´t flash 1.4.0 on November build. It´s made for december and won´t boot on november firmware.


If you´re running November firmware you need to flash 1.3.0, which can be found in the download section and by following the instructions in the OP for version 1.3.0 and below on the bottom.
1.3.0 is not in a flashable zip format, but instead you need to flash the images provided following the download link.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Does this kernel need disabled verify and verification? I am just rooted and used the latest magisk canary on november build.
So I think both are enabled for me.

Thanks
don´t flash 1.4.0 on November build. It´s made for december and won´t boot on november firmware.


If you´re running November firmware you need to flash 1.3.0, which can be found in the download section and by following the instructions in the OP for version 1.3.0 and below on the bottom.
1.3.0 is not in a flashable zip format, but instead you need to flash the images provided following the download link.
Oops, glad you noticed that.

To spell it out for @Lycidias, Verity and Verification *do* need disabled (and you'll have to factory reset) in order to use the 1.3.0 kernel, but if you manually update to the December firmware (third link in my signature below), then you can use the 1.4.0 kernel and not disable Verity and Verification.
 
  • Like
Reactions: Lycidias

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,530
18,328
Oops, glad you noticed that.

To spell it out for @Lycidias, Verity and Verification *do* need disabled (and you'll have to factory reset) in order to use the 1.3.0 kernel, but if you manually update to the December firmware (third link in my signature below), then you can use the 1.4.0 kernel and not disable Verity and Verification.
I think it should work to not disable the vbmeta flags on 1.3.0 if the boot.img provided in the download section is patched with magisk 23016 and the instructions are followed correctly.

Same as patching stock boot.img with magisk 23016 works on the november build as is seemingly confirmed by @Lycidias previous post.
There shouldn´t be a difference between stock boot.img and the boot.img of my kernel if magisk 23016 is used, that´s why I´d assume so.

However I´m not able to confirm this 100%, since I´m no longer on November firmware and have the vbmeta flags still disabled from when I rooted initially.
 

roirraW "edor" ehT

Forum Moderator
Staff member
I think it should work to not disable the vbmeta flags on 1.3.0 if the boot.img provided in the download section is patched with magisk 23016 and the instructions are followed correctly.

Same as patching stock boot.img with magisk 23016 works on the november build as is seemingly confirmed by @Lycidias previous post.
There shouldn´t be a difference between stock boot.img and the boot.img of my kernel if magisk 23016 is used, that´s why I´d assume so.

However I´m not able to confirm this 100%, since I´m no longer on November firmware and have the vbmeta flags still disabled from when I rooted initially.

Okay, thanks. It's a confusing situation. I got the below response regarding this subject and @Freak07's kernel:
It has nothing to do with the kernel itself. The anykernel.zip uses magiskboot to "repack" the kernel during the flashing kernel.
 

Lughnasadh

Senior Member
Mar 23, 2015
3,323
3,288
Google Nexus 5
Huawei Nexus 6P
Okay, thanks. It's a confusing situation. I got the below response regarding this subject and @Freak07's kernel:
I think the difference is that there is no flashable zip for 1.3, so the 3 separate images have to be flashed. But patching the provided boot image with Magisk 23016 before flashing should bypass the need to disable verity & verification.

1.4, however, has a flashable zip with the magiskboot binaries updated to 23016.
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,530
18,328
Okay, thanks. It's a confusing situation. I got the below response regarding this subject and @Freak07's kernel:
yes, it´s ultimately related to magisk, but it also affects the kernel.zips.

If magisk 23016 is used to patch/repack the boot.img vbmeta flags don´t need to be disabled as there´s a commit that removed the need for this.

So if somebody manually patches a boot.img with magisk 23016 or flashes a kernel.zip with magiskboot binary (which the kernel.zip uses to essentially switch out the zImage) updated to magisk 23016 vbmeta flags don´t need to be disabled.

If the kernel.zip contains however magiskboot 23015, the user will end up in a bootloop as magiskboot 23015 needs the vbmeta flags disabled, even if the user previously rooted fine with 23016.

If the user flashes 1.4.0 on November firmware (that´s no longer possible as it should abort, since I updated the kernel.zip a few days ago) there will be a bootloop.

There´s no flashable kernel.zip for 1.3.0 (which works fine on November firmware) so the user needs to manually patch the provided boot.img with magisk 23016 and flash all provided images via fastboot/d at the moment.

It´s a bit of a confusing situation, with vbmeta, the magisk canaries and now the removed firmware images for December firmware...
 

Lycidias

Senior Member
Thank you very much for the great support and the detailed answers ☺️

So I'll wait for the upcoming january update (and probably the corresponding kernel update?) before flashing this beauty.

I want to flash it as a flashable zip and do not want to do a factory reset. For my understanding I don't need to disable the verify and verification flags for future kernel updates with the latest magisk canary?

All a bit confusing. Wasn't that complicated on the phones I had before 😆
 
  • Like
Reactions: roirraW "edor" ehT

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,530
18,328
Thank you very much for the great support and the detailed answers ☺️

So I'll wait for the upcoming january update (and probably the corresponding kernel update?) before flashing this beauty.

I want to flash it as a flashable zip and do not want to do a factory reset. For my understanding I don't need to disable the verify and verification flags for future kernel updates with the latest magisk canary?

All a bit confusing. Wasn't that complicated on the phones I had before 😆
That's probably the easiest solution if you're patient enough :)

Or try to see if somebody has a mirror of the December factory image, update to December and flash 1.4.0.zip :)

If you're brave patch boot.img 1.3.0 with magisk 23016 or higher and flash all images according to instructions. Maybe someone did and reports back here. Maybe it's not possible, but I can't confirm to be absolutely sure.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Okay, thanks. It's a confusing situation. I got the below response regarding this subject and @Freak07's kernel:
yes, it´s ultimately related to magisk, but it also affects the kernel.zips.

If magisk 23016 is used to patch/repack the boot.img vbmeta flags don´t need to be disabled as there´s a commit that removed the need for this.

So if somebody manually patches a boot.img with magisk 23016 or flashes a kernel.zip with magiskboot binary (which the kernel.zip uses to essentially switch out the zImage) updated to magisk 23016 vbmeta flags don´t need to be disabled.

If the kernel.zip contains however magiskboot 23015, the user will end up in a bootloop as magiskboot 23015 needs the vbmeta flags disabled, even if the user previously rooted fine with 23016.

If the user flashes 1.4.0 on November firmware (that´s no longer possible as it should abort, since I updated the kernel.zip a few days ago) there will be a bootloop.

There´s no flashable kernel.zip for 1.3.0 (which works fine on November firmware) so the user needs to manually patch the provided boot.img with magisk 23016 and flash all provided images via fastboot/d at the moment.

It´s a bit of a confusing situation, with vbmeta, the magisk canaries and now the removed firmware images for December firmware...
Thanks! I must've been confused and thinking that I was responding in someone else's kernel thread. Oh crazy me! :)
 
  • Like
Reactions: Freak07

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,530
18,328
just a heads up. there´s no january source code released yet and it´s getting late here.

Working day for me tomorrow, but I´ll try to update the kernel as soon as possible once January sources are released.

In the meantime the 1.4.0 zip works fine for me on January update. There seem to be not that many kernel changes as the stock kernel still has a November build date. :)
 

Jerreth

Senior Member
Mar 9, 2011
496
110
Oregon
unable to flash update via flash-all.bat gets stuck at boot partition missing or some such thing anyone else having that issue?

AHAHAHAH!!! i found it i guess that the Fastboot stuff i had in my path was old i just plopped the latest fastboot files in to the image folder and boom its working sorry for off topic by the way
 
Last edited:
  • Like
Reactions: roirraW "edor" ehT

KedarWolf

Senior Member
Apr 27, 2012
295
157
Yes flashed it too, it works fine.

Boot failure, but on a dirty flash of the January factory image using the below method and flashing the kernel with the EK Kernel Manager.

Rooting with the newest Magisk.

 

P6P

Senior Member
Boot failure, but on a dirty flash of the January factory image using the below method and flashing the kernel with the EK Kernel Manager.

Rooting with the newest Magisk.

I was on December build.
1. dirty flashed January Update
2. Patched the stock boot image with latest magisk canary and flashed it
3. Installed kirisakura 1.4.0 with exkm

Works fine so far.
 

P6P

Senior Member

Attachments

  • Screenshot_20220115-023040.png
    Screenshot_20220115-023040.png
    199.8 KB · Views: 53
  • Like
Reactions: roirraW "edor" ehT

Top Liked Posts

  • 5
    Some would even say that you need to "commit" to this hobby in order to root safely. 🙃

    I'll see myself out now...
    Well, some people are rooted in tradition....
    4
    Sorry, but I was referring to the above guideline. Returning to stable now. :)
    This is only for the stock kernel. A few things have changed with the Pixel 6 boot image that have required Magisk fixes. If a kernel developer is using the stock kernel as a base and incorporates the same changes, then yes one would want to use the latest Canary. However, many developers either use an old base, or build their kernel from scratch using the original kernel source; in those cases one could probably use almost any version of Magisk since 24000.
    2
    Hi, I am trying to flash this kernel (2.4.0) on stock Pixel 6 pro rooted with magisk and updated to the latest canary (24312) and May update. Every time I flash it via EXKM or FKM it flashes normally but after reboot, it gets up to the google logo but then hard crashes and starts looping. I managed to go to the bootloader and was able to restore it to the stock kernel. What am I doing wrong here? I can't figure it out! Any suggestions.
    Use Magisk stable 24300
    2
    This is only for the stock kernel. A few things have changed with the Pixel 6 boot image that have required Magisk fixes. If a kernel developer is using the stock kernel as a base and incorporates the same changes, then yes one would want to use the latest Canary. However, many developers either use an old base, or build their kernel from scratch using the original kernel source; in those cases one could probably use almost any version of Magisk since 24000.
    Didn't know that. Thank you.
    2
    It's important to pay attention to the commits and update notes :)
    Some would even say that you need to "commit" to this hobby in order to root safely. 🙃

    I'll see myself out now...
  • 34
    Update to 2.4.0

    Hey guys and girls,


    Alright here´s the next update and it´s fine to flash on May firmware. As I suspected we already had all the changes for May by merging upstream.
    I´ll include the changelog from 2.3.0 as well in this release post, since I think a lot of people flash the kernel on a monthly basis when the security updates drop. So this post pictures the changes going from 2.1.0 to 2.3.0! As I said 2.3.0 was kind of a final rehearsal to make sure everything is good for the May update.
    I´ll put a remark behind changes going from 2.3.0 to 2.4.0.
    This release is made for stable Android 12.1.0 May firmware. Not QPR Beta or A13 Beta!
    Once I find enough time or QPR beta gets updated, I might update the QPR beta release. No plans to support A13 beta.

    I also finished up the tables/graphs in regards to different binnings with the respective voltages on different tensor chips thanks to the dmesgs you all provided. I really want to put out a big thanks here to everyone for taking the time and participating. It was really great to see this kind of response.
    I´ll provide them in a post in this thread soon.
    So with that in mind we´ll get to the next paragraph were I could put those tables to good use.

    A few changes from A13 Beta are merged to the kernel so we can enjoy the improvements on A12 ahead of time. Most of them aim to improve the scheduler and task placement.

    However the recently dropped A13 Beta source contains a commit that can restrict max-cpufreqs based on PMU (Power monitor unit) reading. I setup this mechanism (lets call it "PMU Limiter") to mildly cut back max-freqs when they aren´t needed. It works quite well so far, with no performance impacts during scenarios where max cpufreq is beneficial. (e.g. app launching, camera launching, interaction etcetc)
    That means if a certain threshold is not crossed the max-freqs will be restricted to 1,4GHZ/1,6GHZ/2,4GHZ (for little/mid/big cores). As soon as the PMU detects enough pressure, those limits will be lifted.
    The frequency limits are based on tracing during various scenarios, benchmarking and also factor in the voltage table I was able to create. For example: 2.4GHZ for the big cores is the last freq step where a steady linear increase in voltage can be seen. Freq steps higher than 2,4ghz have a steeper slope.
    Keep in mind CPU-Freqs shouldn´t be touched in EXKM/FKM or other kernel managers. They are controlled by various mechanisms now (thermal hal, powerhal, pmu limiter etc) and values will get overwritten based on input.
    That means if you open the CPU section in a kernel manager, the maxfreqs will not be the actual maxfreqs that are possible. or the minfreqs might be raised. That´s normal and there´s nothing wrong if that´s the case.

    Additionally to the previous changes tasks of rt, sf and ta groups are now biased to start on high capacity CPUs during app launches, interactions etc.
    As usual, depending on your usage you may or may not notice a difference during these scenarios. :)

    While tracing I noticed kswapd often takes 100% cpu share when reclamation is happening. Since we use an 8 core cpu, an additional kswapd thread is being spawned during boot, which increases throughput for kswapd in these scenarios. Reasoning behind this can be found here.

    The trusty driver which connects to the fingerprintreader hal uses now a high prio workqueue when the phone is unlocked via fingerprint scanner. This means better performance, especially under stress. Keep in mind this is a kernel level change, it won´t magically improve fingerprint reader times manifold.

    DAMON and DAMON-Reclaim were removed from 2.3.0 going to 2.4.0. I tested the feature privately and it unfortunately collides with googles EH zram implementation causing the phone to crash at the moment. Tried to debug this issue, but no luck for the May release here.
    If you previously enabled the feature without adjusting the parameters properly and your phone didn´t crash, DAMON-Reclaim just didn´t do anything.

    2.4.0 also has an updated anykernel3.zip, which includes all the latest anykernel3 changes.
    Thanks to @capntrips we now have full support to resize vendor_dlkm partition which is part of the super partition. That means we finally can flash larger than stock vendor_dlkm partitions via anykernel3.zips and resize the partition properly instead of just dd´ing to it.
    A huge thanks to @capntrips for working on this and to @osm0sis for maintaining anykernel3.


    Disclaimer:
    I´ll keep the warning as to preferably using magisk stable to avoid potential issues as well here in this post.
    Please note that 24306 works fine for me though on non beta, stable May 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.

    If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.



    Changelog:

    - Linux-stable merged to 5.10.113
    - Use prebuilt Google Clang 14.0.5 for compilation
    - Utilize an additional kswapd thread to increase throughput for memory reclaim
    - remove DAMON and DAMON-Reclaim from kernel build (2.4.0)
    - improve trusty driver performance which connects to fingerprintscanner-hal by using high prio wq during fp unlock (2.4.0)
    - mm improvements from kernel/common (2.4.0)
    - improvements from kernel-common a13 to page_pinner
    - mainline backports for BFQ scheduler
    - rework Multi-Gen LRU implementation
    - scheduler improvements for RT (realtime) tasks
    - other scheduler improvements
    - include scheduler improvements from A13 Beta regarding better task placement
    - introduce and setup PMU limiter (prevents CPU from spiking to max when it isn´t needed, based on PMU reads)
    - bias tasks of rt, sf and ta groups to prefer high capacity cpus during app launches, interactions, camera launches, etc
    - updated anykernel3.zip (thanks to @osm0sis) -> adds full support for resizing vendor_dlkm ( huge thanks to @capntrips )



    Download:


    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
    29
    Update to 2.3.0

    Hey guys and girls,


    Alright here´s the next update. It´s a major one. I want to put it out shortly before we hopefully receive the next monthly security update on Monday kinda as a final rehearsal.
    This kernel is made for stable Android 12.1.0 April firmware. Not QPR Beta or A13 Beta!
    Once I find enough time or QPR beta gets updated, I might update the QPR beta release. No plans to support A13 beta.

    A few changes from A13 Beta are merged to the kernel so we can enjoy the improvements on A12 already. Most of them aim to improve the scheduler and task placement.
    A13 Beta source contains a commit that can restrict max-cpufreqs based on PMU reading. I setup this mechanism to mildly cut back max-freqs when they aren´t needed. It works quite well so far, with no performance impacts during scenarios where max cpufreq is beneficial. (e.g. app launching, camera launching etc)
    Tasks of rt, sf and ta groups are now biased to start on high capacity CPUs during app launches, interactions etc.
    As usual, depending on your usage you may or may not notice a difference during these scenarios. :)

    While tracing I noticed kswapd often takes 100% cpu share when reclamation is happening. Since we use an 8 core cpu, an additional kswapd thread is being spawned during boot, which increases throughput for kswapd in these scenarios.

    DAMON patch-series is included to this release as it was merged to kernel/common. It includes DAMON-reclaim. You can read more about it here.
    This feature is currently disabled by default on this kernel. If you want to use it you can tune it to your liking as per the documentation linked above.
    The feature can be enabled via:
    Code:
    echo 1 > /sys/module/damon_reclaim/parameters/enabled
    I think Google might start to use it in the not so far future, but for now it´s disabled by default.


    Disclaimer:
    I´ll keep the warning as to preferably using magisk stable to avoid potential issues as well here in this post.
    Please note that 24306 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.

    If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.



    Changelog:

    - Linux-stable merged to 5.10.113
    - Use prebuilt Google Clang 14.0.5 for compilation
    - Utilize an additional kswapd thread to increase throughput for memory reclaim
    - improvements from kernel-common a13 to page_pinner
    - mainline backports for BFQ scheduler
    - rework Multi-Gen LRU implementation
    - merge DAMON to the kernel, which includes DAMON-Reclaim (this feature is not enabled by default, you need to enable it manually if you want to test)
    - scheduler improvements for RT (realtime) tasks
    - other scheduler improvements
    - include scheduler improvements from A13 Beta regarding better task placement
    - introduce and setup PMU limiter (prevents CPU from spiking to max when it isn´t needed, based on PMU reads)
    - bias tasks of rt, sf and ta groups to prefer high capacity cpus during app launches, interactions, camera launches, etc



    Download:


    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
    25
    May update is out. :)

    no source update pushed from google yet. I guess it´ll happen in a few hours when I´ll be asleep.
    I went ahead and flashed the latest release for stable 12.1.0 without any issues so far.

    If you can´t wait, it should be fine to flash based on that short experience.

    If you want to be absolutely sure there will be no issues due to incompatible source/firmware, I´ll try to update the kernel with any new potential changes in the source for May as soon as I find time, which will hopefully/probably be tomorrow if everything goes as expected. :)

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

    Code:
    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.
    12
    Hey everyone :)

    I´ll bump this up so it doesn´t get lost on the previous page.

    I´d like a favor to ask from all of you. I´m trying to create some graphs/mapping about the binnings of different tensor chips so the differences in voltages used for the CPU freq steps can be evaluated.
    I´m not after trying to undervolt the CPU or similar I just want to see the differences in voltages for the binnings so we can get an idea for the range that inevitably exists there.

    If you want to help me, all you need to do is to reboot the phone and immediately after boot is finished take a dmesg and upload it here so I can check.
    The easiest way to take the dmesg is to just open exkm if you have the app installed, go to tools -> save logs -> current kernel log (dmesg).
    Other apps can do this as well or via terminal. Instructions for terminal/adb shell can be found here.
    The most important thing is to take the dmesg as fast as you can after boot finished!

    I´ll collect all the data and create a spreadsheet for everyone to check.

    I´d be really happy if as many as possible could share a kernel log here, the more data of different devices I can gather the better the picture we will see later will be.

    Thanks for your help and I wish everyone a great day.
  • 97
    Kirisakura-Kernel for the Pixel 6/Pro

    Hello everyone,

    To keep it short: Here is Kirisakura - Kernel for the Google Pixel 6 Pro aka Raven and the Pixel 6 aka Oriole, together Raviole.
    I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.

    The kernel aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security, stability and performance!
    This includes Linux-Stable, F2FS-Stable and kernel/common!
    If that got you curious,have a read about linux-stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.

    The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
    A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
    A big thanks to all of them at this place!

    Now lets continue with a list of features in the next paragraph!

    Features:
    Main Features:
    - Based on latest kernel sources from Google, Kernel is made for Android 12
    - Linux-Stable-Upstream included to 5.10.113
    - Compiled with prebuilt Google clang 14.0.5
    - merged kernel/common (improvements to android-common-kernel straight from google)
    - Multi-gen LRU backported (more info here, here as well and here) to improve mm and reduce cpu cycles
    - Utilize an additional kswapd thread to increase throughput for memory reclaim
    - pelt multiplier tied into powerhal to speed up scheduler during interaction (more info here)
    - prevent frequency spikes caused by small transient tasks when the device is idle(more info here)
    - tie mechanism to prevent frequency spikes caused by small tasks also into powerhal
    - scheduler improvements for RT (realtime) tasks
    - introduce and setup PMU limiter (prevents CPU from spiking to max when it isn´t needed, based on PMU reads)
    - improve camera performance by tuning the powerhal during recording
    - bias tasks of rt, sf and ta groups to prefer high capacity cpus during app launches, interactions
    - improve app launches via powerhal
    - improve trusty driver performance which connects to fingerprintscanner-hal by using high perf wq during fp unlock
    - restrict maximum CPU-Freqs during screen off/ idle to 1.1GHZ for all clusters to save power
    - introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf under heavy load
    - fuse: give wakeup hints to scheduler to speed up compress/decompress in internal storage (details)
    - enable RCU_BOOST (details here), also fix RCU_BOOST behaviour
    - F2FS-Stable updated
    - TCP backports from mainline
    - BFQ updates backported from mainline
    - use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
    - Enable support for TTL spoofing
    - Include LRNG, see here and here for more info (thanks @arter97 for the work on his op9 kernel)
    - important patches from kernel/common for 5.10 (here are more details)
    - CleanSlate Features from @tbalden, big applause here! (s2s, notification booster, battery saver, flashlight notifications. Please note: cleanslate features that work otherwise with rooted devices like kadaway (adblocking) are not implemented on this kernel since I´m running rooted)
    - dirty pipe exploit fixed
    - supports direct usb access for hi-res playback over USB-C DACs
    - flashing the kernel will preserve root

    Various Optimizations:
    - update several drivers to use power efficient workingqueues (for example wlan driver)
    - kernfs: use buffer from the stack space
    - printk: use buffer from the stack space
    - kthread: use buffer from the stack space
    - bpf: avoid dynamic memory allocation for small value buffers
    - binder: Reserve caches for small, high-frequency memory allocations
    - kernfs: use kmem_cache pool for struct kernfs_open_node/file
    - cgroup: use kmem_cache pool for struct cgrp_cset_link
    - f2fs: reduce timeout for uncongestion
    - f2fs: Demote GC thread to idle scheduler class
    - f2fs: set ioprio of GC kthread to idle
    - mm: vmstat: use power efficient workingqueues
    Wakelock Blocker:
    - advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
    - please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info

    AK3 Helper Module:
    - restrict little cluster to 1,19ghz mid cluster to 1,19ghz and big cluster to 1,1ghz during screen off, to reduce battery usage for example during music playback
    - tie pelt multiplier into the powerhal (more info here)
    - prevent frequency spikes caused by small transient tasks during idle operation (more info here)
    - boost scheduler using the pelt multiplier during fingerprint unlock operation

    DOWNLOAD:
    Download is always located in this folder:

    Changelog:
    Android 12.0.0

    1.0.0 Initial Release
    1.0.2 https://forum.xda-developers.com/t/...r-pixel-6-pro-aka-raven.4358435/post-85910621
    1.0.5 https://forum.xda-developers.com/t/...r-pixel-6-pro-aka-raven.4358435/post-85924419
    1.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-85976139
    1.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86109665
    1.5.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86259863
    1.7.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86390563
    1.8.4 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86541727

    Android 12.1.0 Stable (March feature drop and more recent)
    2.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86617873
    2.0.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86637233
    2.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86695911
    2.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86821331
    2.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86834981

    Android 12L QPR Beta
    Build for Android 12 QPR Beta: https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86857033

    Requirements

    - unlocked Bootloader
    - USB-Debugging in developer options enabled
    - latest adb and fastboot binaries
    - working adb and fastboot environment so you can flash back to stock in case something goes wrong
    - working magisk environment (a device rooted with latest magisk stable in case you want to be absolutely safe, magisk 24303 and higher will bootloop on QPR beta and might act up on stable A12.1.0 too!)


    How to flash the Kernel:
    1a. Make sure you tick all the requirements above
    1. Download the correct kernel.zip depending on your device (Pixel 6 = oriole || Pixel 6 Pro = raven)
    (if you´re for whatever reason on November firmware -> use 1.3.0! More recent kernel releases will bootloop)
    2. Flash the correct kernel.zip via EXKM or FKM. Root will be preserved. The AK3 magisk helper module will be automatically installed during flashing the kernel.zip and be present on next reboot.
    Do not remove or disable the AK3 Magisk Helper Module otherwise the device will bootloop.
    3. Reboot and profit.

    Manual installation without relying on paid apps like fkm/exkm:
    Please have a look at the linked post.



    Donations:
    Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea/beer :)
    If you like my work: http://paypal.me/freak07

    Credits:
    @osm0sis for all his work on AK3.
    @tbalden for being the best HTC, Pixel, OnePlus and Asus wingman!
    @LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
    @Captain_Throwback for all the mentoring and guidance!
    @Eliminater74 for bringing me into the game and the Inspiration
    @nathanchance for his upstream guidance and assistance
    @RenderBroken for helping me out
    @flar2 for all his work
    @joshuous for all the help he provided to me in the past!
    @arter97 for giving me advice
    @kdrag0n for his help and advices!
    @topjohnwu for magisk and his entire work!


    Source Code: https://github.com/freak07/Kirisakura_Raviole
    37
    Update to 1.8.4

    Hey guys and girls,


    So here´s the next update. It´s kind of an off schedule update, as I planned to update the kernel with the next security update/feature drop.

    But in the light of recent events regarding the new exploit called "Dirty Pipe" (more info here), which is similar to the "Dirty Cow" exploit from a while ago, but easier to exploit this time, I decided to release an update ahead of schedule.

    This exploit was fixed in linux-stable 5.10.102, as opposed to a single commit in AKC (android kernel common, commit here). This shows once more why merging linux-stable is beneficial as explained in detail in the OP.

    Since one of the key aspects of this kernel is security and staying on par with upstream (which often fixes exploits way ahead of android security bulletin updates, even before an exploit is even known or fixed via a patch on the security bulletin) I decided to release this update as quickly as possible, so this exploit is fixed on devices running this kernel.

    Several other notable improvements and changes in this release:
    Bring in scheduler updates from Android 13 Developer Preview, which aim at improving task placement. (adjust powerhal accordingly)
    BFQ IO-Sched is now on par with linux-mainline.
    Several fixes to mm subsystem, f2fs and others.

    Several other improvements are included as well. More details in the changelog.
    Download is below.
    Updated instructions in the OP!


    Changelog:
    - linux-stable 5.10.103
    - contains fix for the dirty pipe exploit
    - built with clang 14.0.2 prebuilt by google
    - improvments from kernel/common
    - fix memory leaks
    - security related patches
    - mm improvments
    - f2fs fixes
    - scheduler fixes
    - for details please check github
    - built with improvements from A13 Dev Preview to display driver
    - other changes please look at my github


    Download:


    Instructions can be found in the OP! Please follow the instructions to avoid any 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.
    37
    Update to 1.7.0

    Hey guys and girls,


    So here´s the next update. It includes the february security update. Most of the changes brought by the February kernel source drop, were already included in this kernel by merging kernel/common and linux-stable.


    Several other notable improvements and changes in this release:
    Improve f2fs performance by merging a patchset to prevent writer starvation for the checkpoint thread. This was discussed this month in the f2fs mailing list and is already merged to the kernel/common tree. It´ll improve performance under heavy I/O utilization.
    You can find more information following the discussion here.
    Necessary backports were brought to the kernel and the platform specific f2fs-implementation was also adjusted.
    Latest f2fs-stable was also merged to the kernel.

    Update the patchset to prevent frequency spikes caused by small tasks as well. Tie those new changes into the powerhal. (That means users not flashing the kernel.zip, but instead use the manual installation method, which are only a handful from the download count, need to flash the updated magisk helper module. Users that flash the kernel.zip via FKM/EXKM have to just flash and forget)

    Several other improvements are included as well. More details in the changelog.
    Download is below.
    Updated instructions in the OP!


    Changelog:
    - February Security update merged
    - linux-stable 5.10.96
    - include latest f2fs-stable
    - improvments from kernel/common
    - fix memory leaks
    - security related patches
    - mm improvments
    - for details please check github
    - introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf
    - update patchset to prevent freq spikes caused by small transient tasks (also tie this into powerhal)
    - give pelt multiplier power hint for scheduler performance boost during fingerprint unlock
    - fuse: give wakeup hints to scheduler to speed up compress/decompress in internal storage (details)
    - enable RCU_BOOST (details here), also fix RCU_BOOST behaviour
    - update LRNG implementation (thanks to arter97 )
    - improvements/fixes for CleanSlate features
    - other changes please look at my github


    Download:


    Instructions can be found in the OP! Please follow the instructions to avoid any 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.
    36
    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:


    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
    34
    Update to 2.4.0

    Hey guys and girls,


    Alright here´s the next update and it´s fine to flash on May firmware. As I suspected we already had all the changes for May by merging upstream.
    I´ll include the changelog from 2.3.0 as well in this release post, since I think a lot of people flash the kernel on a monthly basis when the security updates drop. So this post pictures the changes going from 2.1.0 to 2.3.0! As I said 2.3.0 was kind of a final rehearsal to make sure everything is good for the May update.
    I´ll put a remark behind changes going from 2.3.0 to 2.4.0.
    This release is made for stable Android 12.1.0 May firmware. Not QPR Beta or A13 Beta!
    Once I find enough time or QPR beta gets updated, I might update the QPR beta release. No plans to support A13 beta.

    I also finished up the tables/graphs in regards to different binnings with the respective voltages on different tensor chips thanks to the dmesgs you all provided. I really want to put out a big thanks here to everyone for taking the time and participating. It was really great to see this kind of response.
    I´ll provide them in a post in this thread soon.
    So with that in mind we´ll get to the next paragraph were I could put those tables to good use.

    A few changes from A13 Beta are merged to the kernel so we can enjoy the improvements on A12 ahead of time. Most of them aim to improve the scheduler and task placement.

    However the recently dropped A13 Beta source contains a commit that can restrict max-cpufreqs based on PMU (Power monitor unit) reading. I setup this mechanism (lets call it "PMU Limiter") to mildly cut back max-freqs when they aren´t needed. It works quite well so far, with no performance impacts during scenarios where max cpufreq is beneficial. (e.g. app launching, camera launching, interaction etcetc)
    That means if a certain threshold is not crossed the max-freqs will be restricted to 1,4GHZ/1,6GHZ/2,4GHZ (for little/mid/big cores). As soon as the PMU detects enough pressure, those limits will be lifted.
    The frequency limits are based on tracing during various scenarios, benchmarking and also factor in the voltage table I was able to create. For example: 2.4GHZ for the big cores is the last freq step where a steady linear increase in voltage can be seen. Freq steps higher than 2,4ghz have a steeper slope.
    Keep in mind CPU-Freqs shouldn´t be touched in EXKM/FKM or other kernel managers. They are controlled by various mechanisms now (thermal hal, powerhal, pmu limiter etc) and values will get overwritten based on input.
    That means if you open the CPU section in a kernel manager, the maxfreqs will not be the actual maxfreqs that are possible. or the minfreqs might be raised. That´s normal and there´s nothing wrong if that´s the case.

    Additionally to the previous changes tasks of rt, sf and ta groups are now biased to start on high capacity CPUs during app launches, interactions etc.
    As usual, depending on your usage you may or may not notice a difference during these scenarios. :)

    While tracing I noticed kswapd often takes 100% cpu share when reclamation is happening. Since we use an 8 core cpu, an additional kswapd thread is being spawned during boot, which increases throughput for kswapd in these scenarios. Reasoning behind this can be found here.

    The trusty driver which connects to the fingerprintreader hal uses now a high prio workqueue when the phone is unlocked via fingerprint scanner. This means better performance, especially under stress. Keep in mind this is a kernel level change, it won´t magically improve fingerprint reader times manifold.

    DAMON and DAMON-Reclaim were removed from 2.3.0 going to 2.4.0. I tested the feature privately and it unfortunately collides with googles EH zram implementation causing the phone to crash at the moment. Tried to debug this issue, but no luck for the May release here.
    If you previously enabled the feature without adjusting the parameters properly and your phone didn´t crash, DAMON-Reclaim just didn´t do anything.

    2.4.0 also has an updated anykernel3.zip, which includes all the latest anykernel3 changes.
    Thanks to @capntrips we now have full support to resize vendor_dlkm partition which is part of the super partition. That means we finally can flash larger than stock vendor_dlkm partitions via anykernel3.zips and resize the partition properly instead of just dd´ing to it.
    A huge thanks to @capntrips for working on this and to @osm0sis for maintaining anykernel3.


    Disclaimer:
    I´ll keep the warning as to preferably using magisk stable to avoid potential issues as well here in this post.
    Please note that 24306 works fine for me though on non beta, stable May 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.

    If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.



    Changelog:

    - Linux-stable merged to 5.10.113
    - Use prebuilt Google Clang 14.0.5 for compilation
    - Utilize an additional kswapd thread to increase throughput for memory reclaim
    - remove DAMON and DAMON-Reclaim from kernel build (2.4.0)
    - improve trusty driver performance which connects to fingerprintscanner-hal by using high prio wq during fp unlock (2.4.0)
    - mm improvements from kernel/common (2.4.0)
    - improvements from kernel-common a13 to page_pinner
    - mainline backports for BFQ scheduler
    - rework Multi-Gen LRU implementation
    - scheduler improvements for RT (realtime) tasks
    - other scheduler improvements
    - include scheduler improvements from A13 Beta regarding better task placement
    - introduce and setup PMU limiter (prevents CPU from spiking to max when it isn´t needed, based on PMU reads)
    - bias tasks of rt, sf and ta groups to prefer high capacity cpus during app launches, interactions, camera launches, etc
    - updated anykernel3.zip (thanks to @osm0sis) -> adds full support for resizing vendor_dlkm ( huge thanks to @capntrips )



    Download:


    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