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

[Freak07]

sorry for the noob question : how can I flash OTA over this kernel (w/o root)? Sideload OTA -> then flash the kernel again?
Thanks!

Just update your device with any full firmware package available, it will overwrite all partitions modified by this kernel. (Factory image, full OTA,zip or the web flash tool, guides for either method are available on this forum.) Just don´t forget to disable verity/verification if you plan to flash a custom kernel again.
Afterwards just flash the kernel according to the instructions in the OP!

 

[Paz9]

Just update your device with any full firmware package available, it will overwrite all partitions modified by this kernel. (Factory image, full OTA,zip or the web flash tool, guides for either method are available on this forum.) Just don´t forget to disable verity/verification if you plan to flash a custom kernel again.
Afterwards just flash the kernel according to the instructions in the OP!

I'm really holding out on the verity/verification wipe... I might have to just do it.

 

[Freak07]

I'm really holding out on the verity/verification wipe... I might have to just do it.

Post in thread '[Kernel][18.11.2022][Android 13.0.0 Stable]Kirisakura 1.1.0 for Pixel 7/Pro aka "Pantah"' https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87625259

I think it's intentional how it works at the moment.
In the everyone has to make the decision by themselves, but I understand how that wipe is just uncomfortable for most.
One advantage when disabling those flags is, you're no longer reliant on any workarounds if there are any, in case they're breaking due to updates.

 

[Ghisy]

I'm really holding out on the verity/verification wipe... I might have to just do it.

Honestly, I just disabled both right away when I got my P7P. I didn't want to have any issue regarding these. I don't see why people (who tinker) keep them enabled?

 

[Freak07]

Important

Just a heads up for everyone:

If the firmware update that's going to drop most likely today contains the QPR (=quarterly platform release, so the changes currently tested in the QPR A13 Beta) amongst the pixel feature drop, don't flash the current release of the kernel until I update the kernel with the new sources!

Otherwise there might be issues or the device refuses to boot due to the new firmware requiring the necessary kernel changes as well!

I'll try to update as fast as possible, but depending on how much conflicts there are and how fast google pushes the new source, merging the new source it might take a bit.

edit: while updating don´t forget to keep the verity/verfication flags disabled in case you plan to flash a custom kernel!

 

[JakeDHS07]

Appreciate the heads up mate. Will wait for word

 

[SkylinesHD]

December update is finally out and available for download

 

[djisma86]

Important

Just a heads up for everyone:

If the firmware update that's going to drop most likely today contains the QPR (=quarterly platform release, so the changes currently tested in the QPR A13 Beta) amongst the pixel feature drop, don't flash the current release of the kernel until I update the kernel with the new sources!

Otherwise there might be issues or the device refuses to boot due to the new firmware requiring the necessary kernel changes as well!

I'll try to update as fast as possible, but depending on how much conflicts there are and how fast google pushes the new source, merging the new source it might take a bit.

Ok i wait for update the pixel 7 pro until you release updated kernel for new sources. Thanks a lot

 

[Tracker31]

Just flashed newest google build. Waiting for your release and testing stock kernel in comparision

 

[matrixhaj]

Just flashed newest google build. Waiting for your release and testing stock kernel in comparision

have you flashed the stock kernel with the commands on the first page before installing?

 

[Tracker31]

have you flashed the stock kernel with the commands on the first page before installing?

Nope. Just did as this tutorial and working well

Platform-Tools v34.0.0 HAS ISSUES - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet

Pixel 7 Pro [Cheetah] Note that although the SDK Platform Tools release notes lists v34.0.1, the download links are 100% confirmed to still be for the problematic 34.0.0, so I recommend sticking with 33.0.3 until 34.0.1 is actually released and...

forum.xda-developers.com

 

[JakeDHS07]

Welp then you'll have to wipe before you can flash the custom kernel . You always have to run the disable Verity/verification commands otherwise they get switched back on when you update.

 

[Repear88]

Welp then you'll have to wipe before you can flash the custom kernel . You always have to run the disable Verity/verification commands otherwise they get switched back on when you update.

Step 2 of the tutorial he posted mention to disable verity/verification so I think he is covered

 

[JakeDHS07]

Hope so. It's brutal when someone forgets that small part and hasn't done a backup it's just like oof

 

[Freak07]

Update to 1.2.0

Hey guys and girls,

So here´s the next release. It includes the QPR (quartly platform release) changes and is now on the same state as A13 QPR Beta was previously. You need to be on December firmware release to be able to install this kernel!
Make sure to flash both, the kernel.zip and the powerhint magisk module as both are updated.

Amongst the QPR changes from Google, which are a big step ahead of the initial A13 release (always the case the last years, the december update fixes tons of things of the major android version bump), MGLRU was bumped to latest V15 state, which was also merged to the linux-kernel recently. Was testing this out for nearly a month, before releasing. For those interested about MGLRU, here´s an excellent writeup by @MishaalRahman.

Kernel is now compiled with latest 16.0.1 prebuilt Clang from Google.

A few important improvements to binder and memory management code. One of those fixes should improve performance during memory pressure quite a bit. (e.g. when taking pictures, extremely RAM intensive tasks with GCAM)

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


I wish everyone a nice day.


Changelog:

- Linux-Stable bumped to 5.10.157
- Bump prebuilt clang to latest 16.0.1 from Google
- important improvements and fixes to binder
- bump MGLRU to latest V15 state
- fix to memory management
- import all improvments from google QPR to powerhint module
- other fixes please check github



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

https://www.androidfilehost.com/?w=files&flid=336658

Make sure to update the powerhint module 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

 

[rage302]

...installed/flashed and booted up fine! THANK YOU.

greetings rage

 

[JakeDHS07]

Same all good over here as well. Cheers @Freak07

 

[liver20]

Flashed!!!! Thanks

 

[bobbarker2]

@Freak.007 Thanks for the link about MGLRU. I understood LRU pretty well, but wasn't as familiar with MGLRU. It sounds like a real boon to Android/Linux.

For those too lazy or not technically minded here's the TL;DR of the benefit:

According to Google’s fleetwide profiling, multi-generational LRU yields an “overall 40% decrease in kswapd [the kernel daemon that manages virtual memory] CPU usage,” an “85% decrease in the number of low-memory kills at the 75th percentile,” and an “18% decrease in app launch time at the 50th percentile.”

Thanks for getting this kernel out so quickly! You're a great contributor to the community. I'll send those coffee your way.

 

[russian392]

Flashing through adb tools still gives "Fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"

No one is yet to discuss this or find out why this is wrong. Been a month. I know the android community likes to act high and mighty and vague AF for no reason because it makes them feel good, but sometimes humble down and solve a problem?