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

[Queentus]

So I've been having this strange idle drain (~30% over night) since I got my Pixel 7 Pro. Was hoping the custom kernel could help with this but no luck. Anyone else? Would be appreciated if Freak07 could look into this and hopefully provides some advice.

Here's the wakelock detail with GSam if anyone's interested: https://photos.app.goo.gl/TJzBR94qBcJmxRSaA

 

[HipKat]

So I've been having this strange idle drain (~30% over night) since I got my Pixel 7 Pro. Was hoping the custom kernel could help with this but no luck. Anyone else? Would be appreciated if Freak07 could look into this and hopefully provides some advice.

Here's the wakelock detail with GSam if anyone's interested: https://photos.app.goo.gl/TJzBR94qBcJmxRSaA

There's a thread about this. A lot of us have been through this, It's odd. Every month, some people say the newest Firmware fixed the crazy battery drain, and some say the same update caused it on their phones.

It's not the Kernel, but what I did, and it's a little painful, I have gigs of photos I keep on my phone for one thing - but back everything up, reflash with a full wipe and run stock for about a week. I do this every other month anyway.
Back in the old days of flashing ROMs constantly, "dirty flashing" or flashing over another ROM was a terrible thing that caused a lot of problems.

Let your phone settle in and then flash the kernel.

See how that works

 

[chxei]

Hello guys, I'm on the latest evolution x, with the latest march stable firmware. latest stable magisk. I flashed powerhal via magisk and kernel via kernel flasher. rebooted and rom bootlooped. I this even supposed to work on custom roms or it's only for stock rom? The op page doesn't state that, so I assumed it wouldn't be a problem.

 

[radekmazur]

Hello guys, I'm on the latest evolution x, with the latest march stable firmware. latest stable magisk. I flashed powerhal via magisk and kernel via kernel flasher. rebooted and rom bootlooped. I this even supposed to work on custom roms or it's only for stock rom? The op page doesn't state that, so I assumed it wouldn't be a problem.

Your verity is probably not set up.

 

[radekmazur]

Hello guys, I'm on the latest evolution x, with the latest march stable firmware. latest stable magisk. I flashed powerhal via magisk and kernel via kernel flasher. rebooted and rom bootlooped. I this even supposed to work on custom roms or it's only for stock rom? The op page doesn't state that, so I assumed it wouldn't be a problem.

vbmeta flags for verity/verification disabled (this requires a wipe if you´re coming from stock with those flags enabled), check the FAQ for information on how to do this

 

[chxei]

vbmeta flags for verity/verification disabled (this requires a wipe if you´re coming from stock with those flags enabled), check the FAQ for information on how to do this

I had those disabled already

 

[Freak07]

So I've been having this strange idle drain (~30% over night) since I got my Pixel 7 Pro. Was hoping the custom kernel could help with this but no luck. Anyone else? Would be appreciated if Freak07 could look into this and hopefully provides some advice.

Here's the wakelock detail with GSam if anyone's interested: https://photos.app.goo.gl/TJzBR94qBcJmxRSaA

There's a thread about this. A lot of us have been through this, It's odd. Every month, some people say the newest Firmware fixed the crazy battery drain, and some say the same update caused it on their phones.

It's not the Kernel, but what I did, and it's a little painful, I have gigs of photos I keep on my phone for one thing - but back everything up, reflash with a full wipe and run stock for about a week. I do this every other month anyway.
Back in the old days of flashing ROMs constantly, "dirty flashing" or flashing over another ROM was a terrible thing that caused a lot of problems.

Let your phone settle in and then flash the kernel.

See how that works

I don´t think your problem would be kernel related, no matter if stock kernel or a custom kernel. Even if deep sleep in kernel would be broken, if no service or app constantly requests resources, the drain wouldn´t exceed 6-8% during a night.
That´s why I ultimately think it´s best to open a new thread or search for an existing one matching that problem, describing your issue and posting all the relevant information you gathered. Symptoms of the issue, what you tried so far etc.

Since it´s not kernel related posting it in here might confuse other less experienced users. I know the thread is quite popular so somebody might reply sooner or later, but it´s really off-topic in the end.


I have a few advices and will reply here, but i´d like to ask you and anyone else to not continue this here but rather open a new thread or find an existing one that covers this topic already. You might want to link this post in this new topic.

1. Use either better battery stats or battery historian if you want to diagnose such issues. Google is your friend. Better Battery stats is a bit more beginner friendly and battery historian is a bit less accessible. (you can just feed a bug report taken on the phone into here in the end.)

Do all the below steps with those two tools.

1a. Learn how to read logcat and just check it when the issue happens.

2. Try different configurations, try to set it a night on airplane mode, a night on data only, a night on wifi only, one night only bluetooth enabled, one night only

3. From your screenshot it seems you´re using dual sim configuration. Try without

3a. Wipe your phone. Try without anything installed, just sim and logged in to Google account.

4. Don´t restore google backup

5. Try without apps on a freshly wiped phone. Add all apps one by one

6. Same as for apps, try adding network changes one by one. e.g. wifi, then mobile first one sim, then the other, then bluetooth


Also thanks to @HipKat for the advice and chiming in.
It's very unfortunate for those that have it happen.

Hello guys, I'm on the latest evolution x, with the latest march stable firmware. latest stable magisk. I flashed powerhal via magisk and kernel via kernel flasher. rebooted and rom bootlooped. I this even supposed to work on custom roms or it's only for stock rom? The op page doesn't state that, so I assumed it wouldn't be a problem.

Your verity is probably not set up.

It's primarily made for the stock ROM, but i know users have it working on custom ROMs and some custom ROMs include it as default.

Your problem could either the vbmeta flags as already mentioned or that your ROM is not yet updated to march firmware.
At least the Evox build on XDA (the date mentioned in the title) is not on march firmware level. Since March contains the qpr code drop this will result in issues. (same one was already reported a few pages back)

So the previous release might work fine if vbmeta flags are disabled.

 

[chxei]

It's primarily made for the stock ROM, but i know users have it working on custom ROMs and some custom ROMs include it as default.

Your problem could either the vbmeta flags as already mentioned or that your ROM is not yet updated to march firmware.
At least the Evox build on XDA (the date mentioned in the title) is not on march firmware level. Since March contains the qpr code drop this will result in issues. (same one was already reported a few pages back)

So the previous release might work fine if vbmeta flags are disabled.

Thanks, I will try the previous build or wait for the next rom build.

 

[dd805bb]

Anyone tried this with QPR3?

No one went off the rails yet...
Really??

 

[Freak07]

I think I´m going to drop a little update later today with quite some nice changes

stay tuned

 

[JakeDHS07]

Oh boy a mid month update. How exciting!

 

[dd805bb]

I think I´m going to drop a little update later today with quite some nice changes

stay tuned

I got a question, instead of messing with dtbo.img, vendor_kernel_boot.img and vendor_dlkm.img to get KMI into system, couldn't a module be written to replace files within those system images on start? GKI has brought new ways of doing things, but, I am on GKI kernel that is not yours without replacing everything mentioned. Just a boot.img. KMI is dynamically loaded from vendor_boot, but couldn't that be fooled via module instead of replacing so much? The update process is a pain. Unlocked BL will allow anything to boot from boot.img, but once both vendor images get touched, that is when it doesn't and need the flags disabled. So if a module replaced system files at boot, there would be need to disable flags. Just a thought.

 

[Freak07]

I got a question, instead of messing with dtbo.img, vendor_kernel_boot.img and vendor_dlkm.img to get KMI into system, couldn't a module be written to replace files within those system images on start? GKI has brought new ways of doing things, but, I am on GKI kernel that is not yours without replacing everything mentioned. Just a boot.img. KMI is dynamically loaded from vendor_boot, but couldn't that be fooled via module instead of replacing so much? The update process is a pain. Unlocked BL will allow anything to boot from boot.img, but once both vendor images get touched, that is when it doesn't and need the flags disabled. So if a module replaced system files at boot, there would be need to disable flags. Just a thought.

Short answer no but interesting thought.

Any chance you can link the source of this kernel you're using?

The gki part itself (the zImage contained in the boot.img) can be modified as long as stable abi is not modified and kept by those changes. However I'm not interested in this at all.

Simply replacing files on system during boot can be done by magisk already, but it runs way too late during boot for a reason.
Magisk dropped support to overlay anything super early in boot as it often results in corruption.
If you find a way or there is a way to do it differently please let me know.


I don't think it's a pain to pass the flags during a monthly update via fastboot or tick the box in the webflash tool.
Yes it´s annoying and just one more thing google introduced that now needs to be done each month, it´s new to users and if you forget about it you´re screwed.
I need about 5 minutes to update my phone each month. I wiped initially when I unlocked the bl and just followed the same procedure linked in the FAQ every month since the pixel 6 dropped without wiping since then on both devices.


Aside from that:
It would probably be possible to build a monolithic kernel instead of the module based gki style kernel like I did on Zenfone 9, that means build all drivers into the zImage rather than building those as seperate modules. However there are several problems to this approach on Pixels.

Googles sources are shipped properly and the kernel build environment can produce exactly what's needed.

If I deviate from the gki part to a monolithic build the source google pushes gets "incompatible" making monthly updates a lot more tedious as the source needs to be restructured.

 

[dd805bb]

Short answer no but interesting thought.

Any chance you can link the source of this kernel you're using?

The gki part itself (the zImage contained in the boot.img) can be modified as long as stable abi is not modified and kept by those changes. However I'm not interested in this at all.

Simply replacing files on system during boot can be done by magisk already, but it runs way too late during boot for a reason.
Magisk dropped support to overlay anything super early in boot as it often results in corruption.
If you find a way or there is a way to do it differently please let me know.


I don't think it's a pain to pass the flags during a monthly update via fastboot or tick the box in the webflash tool.
I need about 5 minutes to update my phone each month. I wiped initially when I unlocked the bl and just followed the same procedure linked in the FAQ every month since the pixel 6 dropped without wiping since then on both devices.


Aside from that:
It would probably be possible to build a monolithic kernel instead of the module based gki style kernel like I did on Zenfone 9. However there are several problems to this approach.

Googles sources are shipped properly and the kernel build environment can produce exactly what's needed.

If I deviate from the gki part to a monolithic build the source google pushes gets "incompatible" making monthly updates a lot more tedious as the source needs to be restructured.

GitHub - tiann/KernelSU: A Kernel based root solution for Android

A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.

github.com

Here is an example of GKI kernel working depending on kernel version. I get though module theory maybe late. That makes sense. It wouldn't be soon enough in boot. Didn't think of that. I know you do it this for KMI and magisk module would be too late on boot. Just a thought. Thank you for clarifying.

Edit. This doesn't need anything vendor based.

 

[Freak07]

GitHub - tiann/KernelSU: A Kernel based root solution for Android

A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.

github.com

Here is an example of GKI kernel working depending on kernel version. I get though module theory maybe late. That makes sense. It wouldn't be soon enough in boot. Didn't think of that. I know you do it this for KMI and magisk module would be too late on boot. Just a thought. Thank you for clarifying.

Edit. This doesn't need anything vendor based.

Yeah I had a feeling you were maybe refering to this as I saw it a few weeks ago.

KernelSU ships a new (GKI) kernel image that´s keeping the stable abi, so the kernel can still "communicate" fine with all the modules that are in vendor_kernel_boot.img and vendor_dlkm.img on stock images.
That´s one of the good things about GKI as such mods are theoretically possible.
As long as the stable abi is compatible, you can theoretically replace the zImage inside the boot.img, without the need to recompile the vendor specific drivers.
KernelSU does not need to touch a single driver that´s not part of the GKI kernel already and manages to keep the stable abi intact.
On a GKI compatible device you´re able to simple use any of the prebuilt GKI from here in the same fashion.

That´s exactly what´s not possible with this kernel here, as a lot of changes completely break the stable abi, therefore making this approach not possible. Otherwise I´d be greatly limited in the changes I could apply to the kernel.
The compilation of my project here needs to have matching kernel and modules shipped, otherwise it would just crash. And there´s no other way to get those in the correct place than shipping the images you mentioned other than building the monolithic kernel.

edit: if you check the magisk module you´ll also notice that I need to restart the powerhal after booting, as the powerhal file is also replaced too late during boot by magisk.

 

[Freak07]

Update to Raviantha 1.0.0

Hey guys and girls,

So here´s the next release for stable March firmware, which is now QPR2.
Aside from that as already hinted at the previous Pixel 7/Pro release for March google kind of unified the main kernel tree for the Pixel 6 and Pixel 7 series. That means I´m now able to compile the release for Pixel 6 and Pixel 7 from the same main kernel tree after some modifications to my own changes! This saves me a bit of time and means all not vendor/firmware/hardware specific improvements added to the kernel are now shared automatically, without me constantly merging them back and forth.
Hence the name change and starting from 1.0.0 again. Pixel 6 Oriole/Pixel 6 Pro Raven combined are Raviole, Pixel 7 Panther/Pixel 7 Pro Cheetah combined are Pantah, so Raviantha is the combination of both Raviole and Pantah.

Improve Uclamp
Improve uclamp patchset and detect capacity inversion. This greatly reduces the few missed frames we had.


Camera Launch Speed
Speed Up Camera launch by quite a bit. Also improve animations around camera compared to stock kernel.



Make sure to update/flash the new powerhint module attached to this post via magisk manager as it´s been updated!
Please note that this release is not for the QPR Beta firmware, but the stable android 13 march firmware!
Please make sure to not use magisk canary 25210. It breaks module loading and causes a lot of issues! Please use either stable magisk or canary 25206.
Latest platform tools have issues flashing super.img, please use platform tools 33.0.3 when updating your firmware to march updae.


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.175 containing tons of stability and security fixes
- improvements to the scheduler
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- ported improvements from QPR3 beta
- 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

 

[Ghisy]

Ohhh, fun!

Can I flash Raviantha 1.0.0 on top of Pantha? Or should I go back to the stock kernel first?

 

[Freak07]

Ohhh, fun!

Can I flash Raviantha 1.0.0 on top of Pantha? Or should I go back to the stock kernel first?

You can flash on top

 

[Ghisy]

You can flash on top

Spoiler

And here we go! (screenshot behind the spoiler tag because I forgot to resize it!)
Thanks!

 

[Archie k]

Thank you very much!!!