Development [Kernel][04.01.2023][Android 13.0.0]Kirisakura 4.4.1 for Pixel 6/Pro aka "RAVIOLE"

Search This thread
Hi, I just wanted to say THANK YOU SO MUCH to @Freak07. This kernel is absolutely amazing and has made my Pixel 6 Pro into a much better phone. A lot of people have complained that Android 13 has made their devices worse in some ways, and that battery life has suffered. I'm having the complete opposite experience.

Granted, I am very much a power user, and modify every app on my device so that only specific ones can run in the background. I use App Ops and Greenify for the majority of these things. Additionally, I use the Wakelock Blocker feature of this kernel to block long-running wakelocks.

Anyway, I'm now getting under 1% of battery drain per hour, which is even better than my OnePlus 7 Pro got (and I used this kernel on that phone as well). I have exactly 300 apps right now and getting battery life like this with that number of apps is almost unheard of. This is only possible because of this kernel. My phone's performance hasn't suffered in any way, shape, or form either. In fact, it's faster than ever, and I'm generally very picky about performance.

Basically, I'm very very happy with this phone all because of this kernel! It has definitely made life easier, and I'm very thankful for all the work you've put into it. I'm very excited to see what comes in the future!
 

Attachments

  • Screenshot_20220829-011226~2.png
    Screenshot_20220829-011226~2.png
    186.1 KB · Views: 183

Zetsubou Sensei

Senior Member
Sep 19, 2012
95
21
Google Pixel 4 XL
I'm not a very techy person, but my Google Pixel 6 pro keeps overheating way too fast when playing games. The only way this phone charges is if i lay it under an ice pack.

I don't quite understand the directions in order to install these packages, is there a way for simpler instructions to be added? I don't understand a lot of these terms.
As @triggerhappy_ said, if you're not a "techy person" I would recommend NOT doing this.

There is always a chance you may *permanently* destroy your phone. If that's a financial risk you're willing to take as someone who doesn't have the experience to try to remedy it, go for it.

To be clear, you could do everything right and still have something fail bc your computer hiccuped during a critical file transfer. Unless you're willing to potentially spend hours bringing your device back from an unwarranty-able dead, do NOT do this.
 
I'm experiencing a strange bug. I'm on Android 13 and my CPU literally can't go above 1197MHz or 1436 MHz on the fastest cores, even when the screen is on. If I understand the AK3 module correctly, it's supposed to limit the CPU while the screen is off, and then go back to normal when it turns back on. This isn't happening unfortunately.

And even in EXKM, I can't change the max CPU frequency at all. It just changes right back.

Is there anything you can do about this? I can't play certain games at all. The CPU is too limited.

Additionally, I don't have any apps that are authorized to use root that would modify the CPU in any way, shape, or form (I even disabled EXKM's root access). And I just have the AK3 module in Magisk. So nothing should be causing this. Also, this happens even after a reboot. And I'm not experiencing thermal throttling. I even tried putting my phone in the freezer for a while. No change.
 

Attachments

  • Screenshot_20220831-232700.png
    Screenshot_20220831-232700.png
    230.7 KB · Views: 111
Last edited:

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
I'm experiencing a strange bug. I'm on Android 13 and my CPU literally can't go above 1197MHz or 1436 MHz on the fastest cores, even when the screen is on. If I understand the AK3 module correctly, it's supposed to limit the CPU while the screen is off, and then go back to normal when it turns back on. This isn't happening unfortunately.

And even in EXKM, I can't change the max CPU frequency at all. It just changes right back.

Is there anything you can do about this? I can't play certain games at all. The CPU is too limited.

Additionally, I don't have any apps that are authorized to use root that would modify the CPU in any way, shape, or form (I even disabled EXKM's root access). And I just have the AK3 module in Magisk. So nothing should be causing this. Also, this happens even after a reboot. And I'm not experiencing thermal throttling. I even tried putting my phone in the freezer for a while. No change.
That's normal behaviour. You're not supposed to change the min/max cpufreqs manually.

Thermal-hal and power-hal both control these dynamically, based on device temperature and certain scenarios like touching the screen, opening apps, camera etc. If you change them, those will immediately change it back.

If you tap the live frequency view in exkm you'll see it uses higher freqs as well on the frequency distribution. Or hit reset in the frequency distribution, navigate a bit through your phone, open a few apps and check again.

If thermal-hal is active and restricts freqs constantly, you're running into thermal throttling.

Edit: @Phascinate you might have forgotten you enabled the batterysaver mode in CleanSlate config app. That restricts to exactly those freqs too.
 
Last edited:

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
Update to 4.1.6

Hey guys and girls,

I hope everyone started into a good week. Here´s the next release. Kind of a surprise update from Google, I suspected it would drop next Monday.
But here we go, the next update including the September security patch. The updates to the main kernel we already had in advance by having upstream merged. The other change is in the bms submodule, which controls charging.

Amongst linux-stable upstream there are a few other updates in this kernel, which I´ll mention shortly in the changelog.

Kernel is compiled for stable A13, not A13 QPR Beta!


I wish everyone a nice day.

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 bumped to 5.10.141
- scheduler improvements from linux-mainline
  • sched: Allow newidle balancing to bail out of load_balance
    [*]sched/fair: Introduce SIS_UTIL to search idle CPU based on sum of util_avg
    [*]nohz/full, sched/rt: Fix missed tick-reenabling bug in dequeue_task_rt()
    [*]sched/core: Do not requeue task on CPU excluded from cpus_mask
- updates from kernel/common


Download:


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
 
Last edited:

Gordietm

Senior Member
Sep 11, 2012
2,136
630
Toronto
Google Pixel 7
Google Pixel 7 Pro
Update to 4.1.6

Hey guys and girls,

I hope everyone started into a good week. Here´s the next release. Kind of a surprise update from Google, I suspected it would drop next Monday.
But here we go, the next update including the September security patch. The updates to the main kernel we already had in advance by having upstream merged. The other change is in the bms submodule, which controls charging.

Amongst linux-stable upstream there are a few other updates in this kernel, which I´ll mention shortly in the changelog.


I wish everyone a nice day.

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 bumped to 5.10.141
- scheduler improvements from linux-mainline
  • sched: Allow newidle balancing to bail out of load_balance
    [*]sched/fair: Introduce SIS_UTIL to search idle CPU based on sum of util_avg
    [*]nohz/full, sched/rt: Fix missed tick-reenabling bug in dequeue_task_rt()
    [*]sched/core: Do not requeue task on CPU excluded from cpus_mask
- updates from kernel/common


Download:


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
Thanks for the quick update. Donation sent. 😀
 

S8rooted&tooted

Senior Member
Sep 18, 2017
403
209
Google Pixel 3 XL
Google Pixel 6 Pro
I can confirm the frequency problems with AK3 and or kernel to stock. Just updated to see what would happen during start. Mine stayed at max frequencies on all cores then slowly came back down. With AK3 it didn't allow it to max out cores during boot. Using AK3 for me has always given problems. Mine also would hold during sleep at about middle frequency on all and not drop. My middle frequency on all cores would have most time and minimal on sleep and max. Just after updating to September patch and stock kernel, after just 10 minutes I see time on all different frequencies on all cores.. I noticed once custom kernels started using AK3, this has been an issue for me. Also, if the frequencies are dependent on system processes, why would a module be needed to hold those down? Wouldn't that conflict like changing them ourselves? System processes control it but the module limits it, right there sounds like a conflict if system processes need higher frequency with the screen off.
 
  • Like
Reactions: Freak07

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
I can confirm the frequency problems with AK3 and or kernel to stock. Just updated to see what would happen during start. Mine stayed at max frequencies on all cores then slowly came back down. With AK3 it didn't allow it to max out cores during boot. Using AK3 for me has always given problems. Mine also would hold during sleep at about middle frequency on all and not drop. My middle frequency on all cores would have most time and minimal on sleep and max. Just after updating to September patch and stock kernel, after just 10 minutes I see time on all different frequencies on all cores.. I noticed once custom kernels started using AK3, this has been an issue for me. Also, if the frequencies are dependent on system processes, why would a module be needed to hold those down? Wouldn't that conflict like changing them ourselves? System processes control it but the module limits it, right there sounds like a conflict if system processes need higher frequency with the screen off.
Thanks for the report. I´ll try to clear it up a bit for you.
I don´t know what other kernels do exactly, as I´m usually not following them very closely, but I can answer for my project.

The cores not maxed out constantly for two minutes directly after restart are by design. What you´re seeing is the PMU limiter restricting the frequencies, because the threshold for requesting more performance is not crossed. This prevents a lot of additional heat. Especially the higher frequencies are "inefficient" in more than one way. There´s a higher than linear increase in heat/powerdraw vs performance increase.
The PMU limiter feature is described in detail following this link. I suggest to give a good read, because this is vital background information for everything I´m trying to explain below. :)
Please note: The PMU limiter does not operate in this manner on the stock kernel.

If you use a CPU-Frequency overlay you will see higher frequencies are being used during app launches, like in the screenrecord below. Notice that this is not a real-time representation of what´s actually happening on the phone. So you can´t draw any definitive conclusions about it. Frequencies change much much faster than those overlays, or the live freq view in EXKM can show to a user. (Many many times in a 10th of a second) But to explain this topic in a simplified manner is possible with it.



For the explanation below keep the limits of the PMU limiter based on different conditions in mind. And also keep in mind that PMU limiter doesn't hard limit, it just limits higher freqs until a certain threshold of requested performance is crossed
You'll see at first I start devcheck app. The app is still in memory, that's why the cores don't max out on the overlay. (that doesn´t mean that max freq is not used for the fraction of a second, just the overlay won´t catch it) There's not much to load on the page that's being opened either on the app. Going back to the start page of devcheck, there are more elements in the UI, hence bigger freq bump.

Launching CPU benchmark app and running it, you'll see big cores are maxing out when max performance is requested by running the workload of this benchmark. During this benchmark the workload gets scheduled mostly to the big cores (you can't see this with apps or overlays just by tracing the scheduler). That's why you see max cores max out crossing the PMU limiter threshold easily.

EXKM app is cold launched. I force closed the app before the screen recording so it needs to be loaded completely from scratch. You'll see max freqs are reached, PMU limit for app launches (2,4ghz for big cores) is crossed during the launch to load the app as fast as possible.

Now here's the cpufreq distribution taken from exkm on my end since flashing yesterday evening.


All frequencies are being utilized on all cores. But you can also see the PMU limiter is doing its job. Let's take the efficient cluster with the little cores as example.
You'll see the maxfreq of 1.8ghz for little cores is utilized most of all higher freq steps (1.19GHZ and above). But you can also see the PMU limiter is kicking in, as 1.19GHZ and 1.4GHZ are just after that.

All of this is expected. This works completely different from stock and it's expected that you will be able to tell differences.

Now how does that tie in with other system processes?
The AK3 module you´re seeing in magisk manager after flashing this kernel allows to replace certain parts of those system processes, so that those work with the changes done on the kernel side. The kernel isn't a unit that stands just for it alone.

Example: The PMU limiting itself is done via kernel. But the different conditions on which PMU limiting is triggered (launching apps, 120fps, scrolling, display idle, screen content moving, etc, etc) are detected and handled not by the kernel side, because the system just has more information what's currently happening.
Same for the thresholds of the PMU limiting. The system detects what is happening on your phone like scrolling, screen content static, screen content moving, app launching etc, and different thresholds for the PMU limiting are set.
This information is fed to the kernel via the powerhal, so it can do its job.


You'll notice a difference in freq distribution on this kernel to stock, as it's a deliberate change.
Read the linked posts and I think you'll understand. I'm here for questions.
But keep in mind. All those end-user focused UI tools like CPU freq overlays, live freqs in exkm don't reflect what's actually happening, just give a rough idea. There's a lot of room for misinterpretation.
 
Last edited:

S8rooted&tooted

Senior Member
Sep 18, 2017
403
209
Google Pixel 3 XL
Google Pixel 6 Pro
Thanks for the report. I´ll try to clear it up a bit for you.
I don´t know what other kernels do exactly, as I´m usually not following them very closely, but I can answer for my project.

The cores not maxed out constantly for two minutes directly after restart are by design. What you´re seeing is the PMU limiter restricting the frequencies, because the threshold for requesting more performance is not crossed. This prevents a lot of additional heat. Especially the higher frequencies are "inefficient" in more than one way. There´s a higher than linear increase in heat/powerdraw vs performance increase.
The PMU limiter feature is described in detail following this link. I suggest to give a good read, because this is vital background information for everything I´m trying to explain below. :)
Please note: The PMU limiter does not operate in this manner on the stock kernel.

If you use a CPU-Frequency overlay you will see higher frequencies are being used during app launches, like in the screenrecord below. Notice that this is not a real-time representation of what´s actually happening on the phone. So you can´t draw any definitive conclusions about it. Frequencies change much much faster than those overlays, or the live freq view in EXKM can show to a user. (Many many times in a 10th of a second) But to explain this topic in a simplified manner is possible with it.



For the explanation below keep the limits of the PMU limiter based on different conditions in mind. And also keep in mind that PMU limiter doesn't hard limit, it just limits higher freqs until a certain threshold of requested performance is crossed
You'll see at first I start devcheck app. The app is still in memory, that's why the cores don't max out on the overlay. (that doesn´t mean that max freq is not used for the fraction of a second, just the overlay won´t catch it) There's not much to load on the page that's being opened either on the app. Going back to the start page of devcheck, there are more elements in the UI, hence bigger freq bump.

Launching CPU benchmark app and running it, you'll see big cores are maxing out when max performance is requested by running the workload of this benchmark. During this benchmark the workload gets scheduled mostly to the big cores (you can't see this with apps or overlays just by tracing the scheduler). That's why you see max cores max out crossing the PMU limiter threshold easily.

EXKM app is cold launched. I force closed the app before the screen recording so it needs to be loaded completely from scratch. You'll see max freqs are reached, PMU limit for app launches (2,4ghz for big cores) is crossed during the launch to load the app as fast as possible.

Now here's the cpufreq distribution taken from exkm on my end since flashing yesterday evening.


All frequencies are being utilized on all cores. But you can also see the PMU limiter is doing its job. Let's take the efficient cluster with the little cores as example.
You'll see the maxfreq of 1.8ghz for little cores is utilized most of all higher freq steps (1.19GHZ and above). But you can also see the PMU limiter is kicking in, as 1.19GHZ and 1.4GHZ are just after that.

All of this is expected. This works completely different from stock and it's expected that you will be able to tell differences.

Now how does that tie in with other system processes?
The AK3 module you´re seeing in magisk manager after flashing this kernel allows to replace certain parts of those system processes, so that those work with the changes done on the kernel side. The kernel isn't a unit that stands just for it alone.

Example: The PMU limiting itself is done via kernel. But the different conditions on which PMU limiting is triggered (launching apps, 120fps, scrolling, display idle, screen content moving, etc, etc) are detected and handled not by the kernel side, because the system just has more information what's currently happening.
Same for the thresholds of the PMU limiting. The system detects what is happening on your phone like scrolling, screen content static, screen content moving, app launching etc, and different thresholds for the PMU limiting are set.
This information is fed to the kernel via the powerhal, so it can do its job.


You'll notice a difference in freq distribution on this kernel to stock, as it's a deliberate change.
Read the linked posts and I think you'll understand. I'm here for questions.
But keep in mind. All those end-user focused UI tools like CPU freq overlays, live freqs in exkm don't reflect what's actually happening, just give a rough idea. There's a lot of room for misinterpretation.
I have used this kernel on this device and many others. Like the pixel 3 xl.. I stopped using kernels once AK3 was introduced. Problems across many devices. I tried helping the issue before, but can't help someone who thinks OnePlus is the defacto on Android. I used a few different UI apps to all see the same frequency issues. Now it's been a day since I updated, and I can see without a restart since yesterday, all my frequencies have been used at one time or another. Not real time but total calculated time via UI app. Dev check to be specific. I read your post and the last frequency set you list is the only one my phone ever used.. max frequencies would be stuck at that set you list and lowest possible frequency would go to variable.. battery drop whenever using the phone with games. And hard..like 10% in 10 minutes. Maybe get a total of 2 hours screen time total all day. I am at 2 hours screen time right now and have 83% battery. That is great for me. The past month has been charge the phone by lunch if I use anything that needed high power, my theory, it didn't get to use the high power therefore it would over use battery to compensate for not being able to run higher frequencies. Also lag issues once in awhile watching movies, buffering on perfect cell reception. Most of the time the kernel worked great. But, I would get once in awhile a freeze when opening the phone(not being able to go into higher frequencies). This was never an issue before on stock and isn't now. OnePlus isn't android. AK3 dev uses OnePlus as his defacto. He should use AOSP or a Pixel as defacto. That is the biggest issue with AK3.
 
  • Haha
Reactions: Mrcactuseater

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
I have used this kernel on this device and many others. Like the pixel 3 xl.. I stopped using kernels once AK3 was introduced. Problems across many devices. I tried helping the issue before, but can't help someone who thinks OnePlus is the defacto on Android. I used a few different UI apps to all see the same frequency issues. Now it's been a day since I updated, and I can see without a restart since yesterday, all my frequencies have been used at one time or another. Not real time but total calculated time via UI app. Dev check to be specific. I read your post and the last frequency set you list is the only one my phone ever used.. max frequencies would be stuck at that set you list and lowest possible frequency would go to variable.. battery drop whenever using the phone with games. And hard..like 10% in 10 minutes. Maybe get a total of 2 hours screen time total all day. I am at 2 hours screen time right now and have 83% battery. That is great for me. The past month has been charge the phone by lunch if I use anything that needed high power, my theory, it didn't get to use the high power therefore it would over use battery to compensate for not being able to run higher frequencies. Also lag issues once in awhile watching movies, buffering on perfect cell reception. Most of the time the kernel worked great. But, I would get once in awhile a freeze when opening the phone(not being able to go into higher frequencies). This was never an issue before on stock and isn't now. OnePlus isn't android. AK3 dev uses OnePlus as his defacto. He should use AOSP or a Pixel as defacto. That is the biggest issue with AK3.
I can't reproduce any of those issues.

But if stock is working fine for you, just use stock. 👍

I'm sorry but this thread is not about AK3, so I won't comment on anything regarding, also due to the fact that a few of those statements have no basis in fact.
There's a thread for AK3 on XDA.
 
Last edited:

Badger50

Senior Moderator / Moderator Committee
Staff member
Moderator Announcement
Thread aggressively cleaned! A friendly reminder to all. While it is always ok to ask legitimate questions of any Developer, starting an OT slugfest is definitely not ok!
Please be aware that posting argumentative statements, and responding to these statements with your own rebuttals is disrepectful at best to the thread owner who contributes
countless hours to his kernels in order to share them for free on XDA. So please just report member misconduct, and let the Mods take it from there.

Going forward. Should this occur again, I will have no hesitation in banning members from participating in this thread out of respect for the Developer
and in accordance with XDA Rules for member conduct:

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.​

So please, keep this thread on topic and respectful to the Developer as well as towards each other. As a member of XDA for 11 years, I have seen more than one Developer
leave XDA due to this kind of behavior, which we definitely do not want to see. After all, without the Dev's, what would we have to talk about??

Thank you all for your cooperation, and a pleasant day to all.

-Best regards: Badger50
 

reddvilzz

Senior Member
May 29, 2012
1,938
392
Jakarta
OnePlus 9
Google Pixel 6 Pro
Hi, I was trying to restore the stock image after installing the kernel for an OTA update.

I already removed the magisk modules and uninstall magisk, then adb reboot bootloader
but on the bootloader my devices can't be detected

what seems to go wrong? I tried installing the latest usb driver from google and rebooted but when I type adb devices it won't show anything.
and now I can't start my phone, it will bootloop back to recovery
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,017
20,732
Hi, I was trying to restore the stock image after installing the kernel for an OTA update.

I already removed the magisk modules and uninstall magisk, then adb reboot bootloader
but on the bootloader my devices can't be detected

what seems to go wrong? I tried installing the latest usb driver from google and rebooted but when I type adb devices it won't show anything.
and now I can't start my phone, it will bootloop back to recovery
If you uninstall magisk it will restore stock boot.img. Since this kernel modifies other partitions as well (including boot.img), you need to restore those too, otherwise you end up with a Frankenstein device that won't work. (boot.img from stock firmware, other partitions from my kernel)
To restore to stock images please read the FAQ, it mentions the partitions you need to flash.

Sounds like your fastboot drivers are not up to date, if the device is not detected in fastboot/bootloader.

So the easiest now is to dirty flash the firmware you're currently on, either via factory image or try the web tool as both will restore all the partitions. If you haven't already done so, make sure to flash A13 firmware to both slots.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Fantastic Work Sir! @Freak07 I do believe you've supplied every pixel and even the OP7TProNR McLaren I recently owned. I ditched Google for another year+ because my OGP1 Marlin suffered hardware failure and then my 4XL splder to lifted from battery plug and scattered solder like missiles lol.

    ANYWAYS For anyone On the January Bliss 6.3 from yet another fine Dev who I completely ignore at times (sorry doode) @stebomurkn420 . This kernel will not flash as OP states. However instead of using the Bliss January ASB boot.img use the TQ1A.230105.001.A2 boot.img patched with Magisk. You can then flash this Mona-Lisa-Linux kernel and keep root.

    That is all. GoodDay & Happy 2023! 🌿〽️🥳🍷🌿🍺🎊 🌿🚬😎
    🚬🪬
    5
    Off topic: pixel 6 here, i installed a gms doze magisk modules & uninstalled it, sometimes i receive notifications as a bulk at once when i switch from mobile data to wifi & vice versa, now on since yesterday im only receiving whatsapp notifications, i dirty flashed jan. Firmware image but nothing changed, cleared gms & google apps data but also nothing (sometimes after clearing google app data notifications arrive then stops again)

    Im sorry i know its off topic but if anyone have any tip on how to fix this, thanks
    If you know this is completely off topic why not open a new thread with a question tag and just describe your problem there?
    Or post in the XDA thread of that module. Maybe it's something that happens regularly.
    I'm pretty sure if somebody is aware of that problem, you'll find better help there.
    (I don't have any suggestion on how to help you other than staying away from all mods that alter background behaviour, doze behaviour, notification, etc etc. as problems like this are usually what's going to occur.)


    This just clutters up the thread here and may confuse (inexperienced) users reading or searching through the thread. This thread is really not the place to start a discussion about that topic.
    Thanks for your understanding!
    4
    Installed & uninstalled the modules & still no notifications, ran (dumpsys deviceidle disable) still also no notifications

    umm, youve been warned twice now to please post in the applicable thread. I even tried to give you a direct link to where that would be along with some troubleshooting steps (the one you quoted wasnt even the one related to what you reported, you only needed to read a bit further down), and even an alternative, not to mention the direct warning that even with the best Doze module some people will still have issues....if youre still having issues, backup (something like Migrate (v4) and the way ive used it forever might help shorten the procedure)) and factory reset, and restore, problem solved, plenty of people before you (me included) have had to do it...you'll often spend more time trying to find some obscure workaround than you will fixing it the 100% way...i dont like to enable this behaviour, so this will be the last reply from me on the subject, here or elsewhere...

    Please take another friendly hint....and dont post OT here again :)
    2
    Is it possible to force enable DP Alt Mode using this for the Pixel 6 Pro? Trying to find a way to achieve this, this seems like the most promising thing so far.

    Update: Read through the thread, someone asked this before, for those googling: No, this doesn't fix DP Alt Mode as apparently there are hard links to display firmware and other BS (thanks Google). Damn.
    2
    Is there any way to manually flash? I want to try it on latest beta cause I want full magisk. Rn I'm with p7 boot workaround for root. So I have root and magisk modules enabled for the already installed apps that need root but since magisk can't recognize root can't give root permission to new apps or flash modules. The thing is that I can't install this kernel as well since I can't grant root to kernel flashers. Funny thing I uninstalled kernel flashers done days ago cause I hadn't use it for long and it already had root.... Any way to flash this kernel? I don't even know if it will boot. Thanks
    the kernel is made for stable firmware, not qpr betas.

    manual process won´t work for the current kernel releases. flashing the kernel won´t work properly without being rooted as described in the requirements in the OP.
  • 118
    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 A13 kernel sources from Google, Kernel is made for Android 13
    - Linux-Stable-Upstream included to 5.10.161
    - Compiled with prebuilt Google clang 16.0.2
    - Backport entire RCU subsystem to Linux 6.0
    - Lazy RCU which should result in power-savings while the device is lightly-loaded or idling, more information here
    - FHD Support for Pixel 6 Pro (display is able to run at 1080p), more info here and here
    - merged kernel/common (improvements to android-common-kernel straight from google)
    - MM subsystem reworked (more info and some patchsets linked in this post)
    - Multi-gen LRU backported/reworked and enabled (more info here, here as well and here) to improve mm and reduce cpu cycles, latest V15 state
    - 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, more information here)
    - 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
    - SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
    - Scheduler updates from linux-main
    - use improved energy model for exynos cpu cooling/thermal control
    - allow GPU to scale down to 150mhz, but boost to higher value in case of interaction via powerhal
    - affine IRQS to CPU 7 during camera usage for improved performance as it tends to overload the little cores
    - use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
    - include bbrv2 from google, more info here
    - Enable support for TTL spoofing
    - Include LRNG, see here and here for more info, bump to v45 with 3.0.0
    - 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
    - only use little cores during screen off/device suspend
    - 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
    - setup and control PMU limiter via powerhal (more info here)
    - dynamically adjust target load for memory interface during interaction

    DOWNLOAD:
    Download is always located in this folder:
    4.2.0, 4.3.0 and 4.4.0 are attached to the release posts linked below as AFH is wonky at the moment.


    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 12.1.0 Stable (June feature drop and more recent)
    3.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86992705
    3.0.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86996237
    3.0.17 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87127695

    Android 13.0.0 Stable (not QPR beta!)
    4.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87290247
    4.1.6 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87399635
    4.2.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87524609
    4.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87697425
    4.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87823333
    4.4.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87944879



    Android 12L QPR Beta - Deprecated

    Requirements

    - the kernel is made for the stock firmware provided by Google, pay attention to flash a kernel release matching the firmware (flashing on custom roms might work, but you may need workarounds!)
    - 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)
    - IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13! (take a look here)


    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)
    2. Flash the correct kernel.zip via EXKM, FKM or kernel flasher. 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 is no longer supported starting with release 3.0.0, as there´s a free open-source option to flash kernel.zips now.
    Instead use the free kernel flasher, which can be found here.

    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!
    @capntrips for all his work on the pixel 6!
    @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
    44
    Update to 4.1.0

    Hey guys and girls,

    I hope everyone started into a good week. Here´s the next release. It´s for stable Android 13.
    Thanks to Google releasing the kernel source for the previews and the betas I´m able to push this update out very quickly. As in the past, the code didn´t change between last beta and stable release.

    There are again a lot of changes in this release. I´ll try to keep the release post short as I don´t have that much time lately.


    FHD/1080P Support for Pixel 6 Pro

    The biggest change is FHD support for the Pixel 6 Pro. If you follow twitter you might have seen this tweet from @MishaalRahman.
    Instead of using the display driver that´s supposedly for the Pixel 7 Pro, FHD support was added to the Pixel 6 Pro display driver. There were a few obstacles to make it run properly on the Pixel 6 Pro, but I got it working nicely so far. If anyone has more experience than me regarding panel timings, display drivers etc, feel free to push any improvement as a pull request to my github or point me towards any improvement.

    As a result you can now select 1080p resolution from settings after flashing the kernel. Dynamic refresh rate works, brightness scaling works, no tints, colour shifts or contrast issues either. AOD has a 1080p Low-Power timing as well.

    You´ll find a few more infos with a short video on my tweet here:
    Screenshot_20220816-083147.png
    Screenshot_20220816-083204.png

    It´s perfectly usable on a daily basis so far. I ran it for a few days without issues on my end. While the advantage might be debatable (saving battery, less load on GPU, still needing to drive the same amount of pixels in the end even on lower resolution, etc etc) having options is nice and this is why I decided to ship it.

    Apps need to redraw after switching resolution, sometimes 1080p on big display size selected in settings the UI looks a bit sketchy. So I think Google is still working on that.

    There´s however one bug I found so far that makes me believe this is still very much a WIP from google. If having the "show current refresh rate" option from dev settings enabled while switching resolutions, the display will black out and a restart needs to be forced by keeping the power button pressed or using adb interface to restart the phone. This is not due to the kernel, but display settings in framework getting scrambled as it´s not yet implemented 100% on googles end. So be warned. :)


    MM Subsystem Rework

    MM subsystem was completely reworked including many improvements from linux-mainline. During this MGLRU was also reworked a bit and works better now. I´ll include links to a few of the improvements/patchsets in hide-tags below, if you´re interested beyond that please check out my github.
    links:

    Additionally tie in a few of the MM changes into the powerhal. For example Proactive compaction is more aggressive during screen-off/device suspended operations to improve long term-performance.

    Other changes:

    Also tune the powerhal and implement all A13 changes, according to the changes that were already present on A12.

    Latest changes from f2fs-stable are included, which include several bugfixes and small improvements.
    Binder improvments/fixes, scheduler improvements from kernel/common, performance for exfat formatted storage device improved (niche use case, but still nice) and other little improvements.
    For other changes and details please take a look at github.


    I wish everyone a nice day.

    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:

    - Rebase kernel fully on A13 trees
    - Linux-Stable bumped to 5.10.136
    - FHD/1080p support for Pixel 6 Pro
    - all previous features and improvements kept intact
    - bump f2fs-stable to latest available
    - rework mm subsystem (check git for more details)
    - scheduler improvements
    - binder improvements from kernel/common
    - improve exfat performance (if someones uses exfat formatted devices)
    - loads of other changes from kernel/common
    - update powerhal to account for a13 changes and port existing changes over
    - loads of other changes, please check github



    Download:


    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
    43
    Update to 4.2.0

    Hey guys and girls,

    I hope everyone started well in the new week. Here´s the next release and it´s a rather big one with lots of under the hood improvements.
    We already had all the changes in from the October security patch release released, due to merging linux-stable stable and kernel/common in advance.
    The kernel is now at 5.10.146 way ahead of the stock kernel. To further emphasize the importance of this. About 90% of kernel security issues are solved in linux stable. While I didn´t check the actual number myself, I´d have estimated about the same (80-90%) before actually reading the slides from @arter97 presentation.
    What also needs to be kept in mind is that a big part of those security issues are resolved in linux-stable sometimes months ago before those patches end up in a monthly security patch. Additionally to that the security patches are about 3 months behind the discovery of those vulnerabilities.

    Amongst linux-stable upstream there are a few other not minor updates in this kernel.

    Clang
    The kernel is now compiled with the latest prebuilt Clang from Google. This was quite a journey as this is a pretty big update to clang. This is quite experimental to be on googles side of a "bleeding" edge compiler, but after fixing several issues that originated from the new compiler it ran stable for over 2 weeks.

    There´s a potential for CFI failures that originates from that new Clang rather than a "real attack", due to the changes in clang.
    Short reminder what CFI actually does: Control flow integrity (CFI) is a security mechanism that disallows changes to the original control flow graph of a compiled binary, making it significantly harder to perform such attacks.
    A typical crash (that´s not wanted and originates from compiler changes rather than an actual attack, which is already resolved of course ) would look like the following: Open camera app, due to compiler changes CFI is accidentally tripped every time this code is executed.
    I think we catched all of these newly CFI failures and everything is nice and stable. In case you discover such a behaviour please send me the contents of sys/fs/pstore, once the phone booted back up.

    There´s always the possibility of a "real" attack in which CFI will crash the phone, before the attacker can compromise the phone. That´s why keeping subsystems updated is important.


    Powerhal
    The powerhal was retuned due to changes to the scheduler introduced. It should work even better now, regarding efficiency and performance. Of course I try to tune it also to my personal needs, while trying to keep it working for all workloads. The changes are not drastic, so please don´t post after several hours you see drastic differences.

    Other improvements
    Several other improvements from kernel/common (for higher branches than 5.10) and linux-main were backported to this branch so we can benefit from those improvements. For details please check my git.



    I´d like to write all of this with more detail, but at the moment I lack the time to do so.

    Kernel is compiled for stable A13, not A13 QPR Beta!


    I wish everyone a nice day.

    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 bumped to 5.10.146
    - kernel is compiled with latest prebuilt google clang 15.0.2
    - improvements from linux-mainline
    • locking subsystem
    • memory management
    • more details please check github
    - patches to f2fs
    - updates from kernel/common to several subsystems
    - tweak powerhal for improved performance/efficiency


    Download:
    Attached to release post as AFH is currently down.
    I´ll push to AFH once it´s back up.



    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
    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.