Development [Kernel][04.05.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.0.4 for Pixel 7/Pro aka "Pantah"

[AnierinB]

@elong7681
"It's an ota but when I read the changelog I thought it said that we would no longer have to disable vbmeta flags because the rom would do it during install but when I tried to flash the kernel it didn't work so I had it install the ota.zip through Evo X recovery and before I booted into Android I disabled the flags and tried the kernel again and again I was in a bootloop."

Nowhere in the latest updates changelog was that mentioned:

Panther/Cheetah: 03/07/2023 Update · Evolution-X-Devices/[email protected]

Signed-off-by: AnierinB <[email protected]>

github.com

Also, keep in mind updates get installed to the inactive slot which subsequently gets switched to such upon rebooting.. So any additional changes you make in recovery/fastbootd without switching the slot will be done to the current active slot, not the slot you just applied the update to.

 

[ffuser1]

For anyone updating to March, do not use the new platform tools. Use 33.0.3

 

[t-ryder]

For anyone updating to March, do not use the new platform tools. Use 33.0.3

Yep, Google did really f* up this one and first users are having hard bricks as it seems...

 

[Freak07]

Update to 1.3.0

Hey guys and girls,

So here´s the next release for stable March firmware, which is now QPR2. It´s a big release that´s why I decided to bump to 1.3.0.
Google included a lot of changes for the device specific drivers and kind of unified the main repo for pixel 6 and pixel 7 series. So I probably will be able to unify my main branch too.
Most of the "generic" android changes from the QPR drop we already had included in this kernel for months by merging linux-stable and kernel/common in advance.
The device specific drivers are very much welcome on my end.
Other changes to the kernel I´ll explain below.

Please note that this release is not for the QPR Beta firmware, but the stable android 13 firmware!
Make sure to update/flash the new powerhint module attached to this post via magisk manager as it´s been updated!

Maple Tree / Per VMA-locks via Maple Tree in RCU-Mode
Updated this patchset to a new refined version that´s currently been tested.
Bit of a graph that shows app launch times with and without this patchset:
Link to the graph can be found here.

Explanation of the patchset in hide tags below!

Spoiler

Linux 6.1 finally merged the Maple Tree patchset. I had my eyes on that patchset for quite a while now. I backported it a few months ago (back in november iirc) but at that time I still ran into a few problems with it so it never made it into a release on XDA.
However after discovering work done on per vma-locks, which builds directly on the benefits that maple-tree provides interest was sparked again. Decided to pull it in again and fix the remaining issues.
If you´re interested in details read the linked topics.
Basically those patches reduce app launch time as well as lock contention. Additionally per vma-locks directly utilizes lazy-rcu, which was backported in 1.1.0. Usually I´m very hesitant when it comes to kernel changes actually translating to real world power consumption improvements, but lazy-rcu is one of the few patchsets that translate to a small improvement for everyone regardless of the usage.
So the new per VMA-lock patchset directly benefits from the previous backport of lazy-rcu.

There are other small improvements as well. Please check my github for those.

The kernel is made for stable A13 firmware, not beta.

I wish everyone a nice day.


Changelog:

- Linux-Stable bumped to 5.10.174 containing tons of stability and security fixes
- kernel is now built with latest clang 17.0.0 prebuilt from google
- Update Per VMA-locks patchset from previous release (this benefits greatly from lazy rcu!)
- improvements to MGLRU
- bump f2fs to latest f2f2 stable state
- improvements to the scheduler
- fixes/improvements to to memory management
- security fixes/ improvements from kernel/common
- optimize code around nr_cpus from latest linux
- other fixes please check github



Download:
Attached to release post as AFH is currently down.

Make sure to update and keep the powerhint module installed via Magisk Manager!


If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_kernel_boot.img and vendor_dlkm.img before flashing. Thank you.

Make sure to meet the requirements and read the OP as well as the FAQ before flashing.

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

 

[swieder711]

Installed 1.3 and powerhint 6 on the March update. Seems buttery smooth.

 

[Tracker31]

can I flash it on Feb stable? I don't have PC to flash march update atm

 

[Freak07]

can I flash it on Feb stable? I don't have PC to flash march update atm

Might cause issues, due to loads of changes brought by QPR. Some might be firmware dependant, but I haven´t tried.
If you want to be safe and also have no PC to flash safely back just stay on the previous release for feb stable!

 

[Ghisy]

Updated to March, re-rooted, installed both the powerhint module v6 and newest version of Kirisakura, all seems fine so far on my P7P!

Thanks @Freak07 as always!

 

[Burt Squirtz]

Update to 1.3.0

Hey guys and girls,

So here´s the next release for stable March firmware, which is now QPR2. It´s a big release that´s why I decided to bump to 1.3.0.
Google included a lot of changes for the device specific drivers and kind of unified the main repo for pixel 6 and pixel 7 series. So I probably will be able to unify my main branch too.
Most of the "generic" android changes from the QPR drop we already had included in this kernel for months by merging linux-stable and kernel/common in advance.
The device specific drivers are very much welcome on my end.
Other changes to the kernel I´ll explain below.

Please note that this release is not for the QPR Beta firmware, but the stable android 13 firmware!
Make sure to update/flash the new powerhint module attached to this post via magisk manager as it´s been updated!

Maple Tree / Per VMA-locks via Maple Tree in RCU-Mode
Updated this patchset to a new refined version that´s currently been tested.
Bit of a graph that shows app launch times with and without this patchset:
Link to the graph can be found here.

Explanation of the patchset in hide tags below!

Spoiler

Linux 6.1 finally merged the Maple Tree patchset. I had my eyes on that patchset for quite a while now. I backported it a few months ago (back in november iirc) but at that time I still ran into a few problems with it so it never made it into a release on XDA.
However after discovering work done on per vma-locks, which builds directly on the benefits that maple-tree provides interest was sparked again. Decided to pull it in again and fix the remaining issues.
If you´re interested in details read the linked topics.
Basically those patches reduce app launch time as well as lock contention. Additionally per vma-locks directly utilizes lazy-rcu, which was backported in 1.1.0. Usually I´m very hesitant when it comes to kernel changes actually translating to real world power consumption improvements, but lazy-rcu is one of the few patchsets that translate to a small improvement for everyone regardless of the usage.
So the new per VMA-lock patchset directly benefits from the previous backport of lazy-rcu.

There are other small improvements as well. Please check my github for those.

The kernel is made for stable A13 firmware, not beta.

I wish everyone a nice day.


Changelog:

- Linux-Stable bumped to 5.10.174 containing tons of stability and security fixes
- kernel is now built with latest clang 17.0.0 prebuilt from google
- Update Per VMA-locks patchset from previous release (this benefits greatly from lazy rcu!)
- improvements to MGLRU
- bump f2fs to latest f2f2 stable state
- improvements to the scheduler
- fixes/improvements to to memory management
- security fixes/ improvements from kernel/common
- optimize code around nr_cpus from latest linux
- other fixes please check github



Download:
Attached to release post as AFH is currently down.

Make sure to update and keep the powerhint module installed via Magisk Manager!


If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_kernel_boot.img and vendor_dlkm.img before flashing. Thank you.

Make sure to meet the requirements and read the OP as well as the FAQ before flashing.

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

It looks like I might be the only one having this issue:

After flashing power hint v6, my phone starts locking up about a minute after reboot. The only thing that gets me out of it is a hard reset. I don't know how this happened to me because I made sure to remove the power hint v5 before flashing V6. This is happening to anyone else?

 

[t-ryder]

Disabled the old powerhint, flashed the March stock ROM to the inactive slot using Pixel Flasher. Really a hassle free thing, patching the new factory image boot and flashing the image in a few clicks keeping Magisk hidden and the other modules as they were. Flashed Kirisakura in FKM, enabled new powerhint module after the reboot. My P7 runs smooth as hell and snappy.

Thanks @Freak07

 

[t-ryder]

It looks like I might be the only one having this issue:

After flashing power hint v6, my phone starts locking up about a minute after reboot. The only thing that gets me out of it is a hard reset. I don't know how this happened to me because I made sure to remove the power hint v5 before flashing V6. This is happening to anyone else?

No such thing here on Pixel 7. Are you sure you flashed the right powerhint module for your device?

 

[Ghisy]

I made sure to remove the power hint v5 before flashing V6. This is happening to anyone else?

I never remove the old powerhint module when updating: it'll just uninstall itself when the stock firmware is flashed since the stock kernel is installed as well.

I would make sure that you flashed the correct module for your phone: cheetah is P7 Pro and panther is P7.

 

[Freak07]

It looks like I might be the only one having this issue:

After flashing power hint v6, my phone starts locking up about a minute after reboot. The only thing that gets me out of it is a hard reset. I don't know how this happened to me because I made sure to remove the power hint v5 before flashing V6. This is happening to anyone else?

Can't reproduce this here. Flashed both modules as well to test.

P7 or P7 pro?
You need to flash the kernel as well. The latest release on latest march stable firmware. Should always match.
It might not be compatible with other kernels and/or stock kernel.
Maybe magisk messed something up while deleting the old module and flashing the new one simultaneously.

If all above conditions are met can you take a logcat and a dmesg via PC until the moment it locks up?

 

[Mrcactuseater]

It looks like I might be the only one having this issue:

After flashing power hint v6, my phone starts locking up about a minute after reboot. The only thing that gets me out of it is a hard reset. I don't know how this happened to me because I made sure to remove the power hint v5 before flashing V6. This is happening to anyone else?

Can confirm this issue on my end. Kernel will flash and boot no issues, but any combo of v6 or v5 will cause a hard lock. @Freak07 will assist more in the morning

 

[gj4560]

For what it's worth, I'm also on March update with 1.3.0 kernel and v6 powerhint on my 7 Pro and all seems fine, running very smoothly. I did however uninstall the powerhint module before I updated to March so I'm not sure if that made a difference.

 

[yurishouse]

1.3.0 works great on March update, Thanks for your works

 

[thefinger]

On March update here also. I did not uninstall the previous module but mine was turned "off" before I installed the new one.
First installed the module, then flashed the kernel and then rebooted. Been just a few hours but so far so good

 

[Teet1]

Not asking for support but letting know for those with custom roms, especially on Evolution X, 1.3.0 causes a bootloop. Going back to 1.2.4 fixes it. Most likely because the custom rom needs to be updated with the March update

 

[x111]

can I flash it on Feb stable? I don't have PC to flash march update atm

I flashed 1.3.0 update on feb stable and it caused 5 min reboot time and some magisk modules not working properly.
at least it didn't cause a bootloop

 

[Queentus]

Flashed the powerhint module then the kernel with Kernel Flasher, the system failed to boot and suggested me to do a factory reset. F...

Edit: Reflashed the factory image without any editing related to vbmeta and now it boots successfully. If it's something with the powerhint module then I guess the problem might be with this issue (which has not yet been merged by topjohnwu): https://github.com/topjohnwu/Magisk/issues/6688 ?

I was using an older version of Magisk Canary bc of this issue. Don't know if that was to blame.

BTW now that I have vbmeta verity enabled, do I have to disable it first to flash this kernel after everything is sorted out?