Development [Kernel][26.03.2024][Android 14.0.0 Stable]Kirisakura_Raviantah 2.2.1 for Pixel 7/Pro aka "Pantah"

[HipKat]

You're like the fine print guy at a law firm. Not saying you didn't say it, but it isn't all that obvious.

also, the adb command line doesn't work (can't disable verity or verification, which I tried when I first got the device). The only real way is the flash tool, and this is with up to date sdk tools.

I know people have had success using the command line but for me, it’s just easier to use the flash tool because it does everything I needed to do with one click. You may have the same experience

 

[Thorin_Stone]

wanna flash this kernel ASAP! what's the best app to use for backing up my p7p before wiping?

I used swift back up

 

[HipKat]

CleanSlate is a stock kernel except the CleanSlate features.
Battery life is the same as on stock I´d say. Depending on usage, it might be slightly better (that´s the case for me, as I´m sharing with the community what I use personally) or maybe worse. But again, those shouldn´t make a difference to stock, that result in "horrid" as you described.

The only thing that interests me is which CleanSlate features do you actually use?

There´s no need to tweak anything. Make sure the powerhint magisk module is installed.

I´m sure your drain comes from an app or service that´s either hogging resources, stuck or constantly crashing.
Also keep in mind battery life depends on usage, network quality, your location, wifi quality, screen brightness, installed apps, background processes, server side updates etc.

There are a few tips I can give you however.

Use top command in terminal to check if something is hogging CPU while the screen is on and the device is idling (no interaction, no apps running, nothing touching the screen).
Attached is an example of how it looks on my phone while it's idle.

J
Use either battery historian or better battery stats to check idle drain.
In BBS set a custom reference point, let the phone sleep face down, screen off for a few hours and check wakelocks.
Or take a bug report in the morning and feed it to battery historian. The visualization there's is very nice and informative.


Yeah from time to time the "old spirit" of XDA is emerging here. I "felt" that as well.

I use Linux though I could use windows if I had to. Got docker installed, pulled a bug report this morning and have it saved. When I try to get to battery historian I’m getting an error and I’m pretty sure the error is in this line;

docker --run -p port_number:9999 gcr.io/android-battery-historian/stable:3.0 --port 9999

I’m not sure what’s supposed to go there

In the meantime, I went to bed last night at about 1030 and it was at 95% and I woke up this morning at 5:30 and it was at 88%. Two hours later after a few texts and checking my email and my workload for the day. Other than that sitting next to me with the screen off and I am at 74%.

 

[JakeDHS07]

Officially testing . PixelFlasher made disabling verification and verity super easy and should make it simple to keep data and those with future updates. Fantastic! Shout-out to both @Freak07 and @badabing2003 for their wonderful contributions. Cheers

 

[xiangyou]

Thanks a lot.
I am trying to build pixel 7 's kernel from source code.

I downloaded the source from the git in your post:

GitHub - freak07/Kirisakura_Pantah

Contribute to freak07/Kirisakura_Pantah development by creating an account on GitHub.

github.com

and I run type ./build_cloudripper.sh to build, but the build process never starts, and tell me can't find ./private/ something.

I also tried download the kernel source from source.android.com
repo init -u https://android.googlesource.com/kernel/manifest -b android-gs-pantah-5.10-android13-d1 ; repo sync -j16
here, I can run ./build_cloudripper.sh and build successfully.


My question is :
1, how can I build from your source ?
or,
2, if the images I build from google's source can flash as the images your provided in your post? the size is very different.



Thanks a lot!

 

[innit]

wanna flash this kernel ASAP! what's the best app to use for backing up my p7p before wiping?

Neo Backup. A good alternative to Titanium Backup which no longer works on A13 (apps crash after restoring data).

https://xdaforums.com/t/titanium-backup-android-13-issue.4486863/post-87376645

 

[Freak07]

Update to 1.1.0

Hey guys and girls,

So here´s the next release. I finally feel it´s ready to be publicly released as there was not a single issue encountered over the last two weeks.
Make sure to flash both, the kernel.zip and the powerhint magisk module!

The kernel is now at 5.10.155 way ahead of the stock kernel. To further emphasize the importance of this. About 90% of kernel security issues are solved in linux stable.
5.10.148 and 5.10.149 fixed the CVEs discussed here and here. Those were fixed on kernel common on November 2nd. It might take up to a few months until they trickly down into any officially shipped android kernel!
The initial 1.0.0 release, had those CVEs fixed already as 5.10.149 was merged.
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 on android devices are about 3 months behind the discovery of those vulnerabilities.

This release features a few major changes, which I want to explain in greater details, so excuse the longer release post. I´d appreciate if everyone takes the time to at least read it.

Introduction of Lazy RCU

1.1.0 has the entire(!) RCU subsystem updated to latest linux 6.0 kernel state. This also allowed for Lazy RCU to be merged into the kernel, which should result in power-savings while the device is lightly-loaded or idling (which is basically the case all the time a smartphone isn´t being interacted with (nothing touching the screen and no other workload such as video editing is done).
If you´re interested in details check the slides, which are also linked in the article I linked above.
A very simplified explanation: RCU functionality can be called 1000s of times a second, batching RCU calls can save power by not calling as often.

That´s one of the changes I wanted to be tested extensively, as there are a few 10000 lines of code changes.

Please keep in mind, those are kernel changes and battery life will not be improved magically by huge amounts, due to such a change, even if the change itself is massive.
Example: If you raise or lower the display brightness by around 10% over an entire day, you´ll see a bigger impact.
Reading the OP gives you a good idea what this project is about!


Dynamic Energy Model

Google introduced the possibility to use different Energy Models "on the fly" a while back in the Pixel 6 and Pixel 7 kernel.
I played around with this during the last few weeks and ironically Google did something similar in the QPR A13 Beta when I checked the firmware dump. Google switches to a different Energy Module while taking Videos. Based on my understanding to control heat better during video recordings.

However I had another idea, but the mechanism I use to switch the profiles taps into the same system.
While the device is idle, a different Energy Model is used, compared to when interaction is happening.
While interaction is happening there are many boosts in play already to bias tasks to get executed as quickly as possible anyway. But switching to a different energy model allows us to basically bias tasks to get even more prominently scheduled to the little and middle cores. Since the mid cores are a78 on p7 and way more energy efficient, this should give as a double positive effect. As during idle state there are no boosts active the scheduler can now freely decide how to use EAS to the best to place the tasks as efficiently as possible.
The energy module was tuned, so the scheduler prefers little and mid cores during idle. (nothing touching the screen, watching videos, listening to music, reading websites etc.)

Additionally to this I decided to include the changes Google did on A13 QPR Beta while taking video to also include already in the kernel.

Powerhal

Switch between default and idle energy model on device is being interacted with / device idle.
Reduce missed frames during scrolling/device interaction by adjust uclamp boosts.
Dynamically adjust target load for memory interface during interaction.
Remove dynamic GPU policy change as it´s causing instability and is unneeded due to GVFS period
Implement handling during video recording of CPU like Google did on QPR A13 stable
Raise minfreqs during screen off to 1,4ghz


Playback over USB C to 3.5mm Dongles
Some users were experiencing issues while using usb-c to 3.5mm dongles while running my kernel. After a long time I finally discovered how to reproduce the bug as the logs did not point towards any kernel error. It happens only if default usb configuration in developer options is set to anything else than "no data transfer". If "no data transfer" is selected there´s no issue at all.
A few commits from linux-stable for the usb dwc3 driver breaks playback when screen is shut off or cycling through the "default usb configuration" settings, which causes the aoc driver that´s responsible for playback to shut down.
Reverting those commits fixes the issue.

Thanks to @WhoIsJohnGalt1979 and @Hurt Copain for nagging me about the issue and providing logs, I finally found a way to reproduce the issue so I was able to debug it.

Given that playback is "glitchy" (a brief audio stutter) on stock kernel as well, when either cycling through different "default usb configuration" settings or turning screen on/off, that driver is generally very wonky. A user told me however that this glitch is solved in QPR Beta. So that´s good to hear if that´s the case.


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.


Changelog:

- Linux-Stable bumped to 5.10.155
- 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
- Dynamic Energy Models depending on device state
- Fix audio playback stopping for some users when turning screen off (thanks for @WhoIsJohnGalt1979 and @Hurt Copain for nagging me about the issue and providing logs)
- improve CPU throttling behaviour by backporting a QPR Beta change
- improvements to MGLRU
- improvements from linux-mainline for several subsystems

• scheduler
  • Spoiler

    02595c9fb4ec sched/core: Fix comparison in sched_group_cookie_match()
    407e4ccbb158 sched/fair: Move call to list_last_entry() in detach_tasks
    0ea56a65b686 sched/fair: Cleanup loop_max and loop_break
    0461c9736ec2 sched/fair: Make sure to try to detach at least one movable task
    f2489ca21b11 sched/fair: Cleanup for SIS_PROP
    5a3074a7ac79 sched/fair: Default to false in test_idle_cores()
    bb95868debb0 sched/fair: Remove useless check in select_idle_core()
    50112e040e6a sched/fair: Avoid double search on same cpu
    2457687f35d3 sched/fair: Remove redundant check in select_idle_smt()
• memory management
  • Spoiler

    6bf69138a12b mm: rename p4d_page_vaddr to p4d_pgtable and make it return pud_t *
    9819fcefb782 mm: rename pud_page_vaddr to pud_pgtable and make it return pmd_t *
    997cdba71861 mm: add vma_lookup(), update find_vma_intersection() comments
    eb1eccad20cb mm/page_alloc: fix obsolete comment in deferred_pfn_valid()
    1f30d4f3fb20 mm/page_alloc: remove obsolete gfpflags_normal_context()
    17dd220de848 mm/page_alloc: use costly_order in WARN_ON_ONCE_GFP()
    4d7be8d8d6d4 mm/page_alloc: init local variable buddy_pfn
    521b49f4067c mm/page_alloc: use helper macro SZ_1{K,M}
    9838ea6feaee mm/page_alloc: use local variable zone_idx directly
    d049e3821e8b mm/page_alloc: add missing is_migrate_isolate() check in set_page_guard()
    5dc1c3c60469 mm: remove obsolete pgdat_is_empty()
    55e89c7708e3 mm/page_alloc: fix freeing static percpu memory
    bd801ed8eace mm/page_alloc: add __init annotations to init_mem_debugging_and_hardening()
    ce00e122335e mm/page_alloc: remove obsolete comment in zone_statistics()
    cc20df37215b mm: remove obsolete macro NR_PCP_ORDER_MASK and NR_PCP_ORDER_WIDTH
    97e15d20dd79 mm/page_alloc: make zone_pcp_update() static
    f7425d856d30 mm/page_alloc: ensure kswapd doesn't accidentally go to sleep
    236a9831f7e4 mm: add merging after mremap resize
    bd1537226f30 mm: mremap: fix sign for EFAULT error return value
    4fe39974c254 mm/mremap: avoid unneeded do_munmap call
    3983a53d85a6 mm/mremap:: use vma_lookup() instead of find_vma()
    b832f38c3630 mm, hugepages: add mremap() support for hugepage backed vma
    23aa8d328a4c mm/mremap: allow arch runtime override
    b029910a3ec8 mm/mremap: use pmd/pud_poplulate to update page table entries
    53093a2f034d mm/mremap: don't enable optimized PUD move if page table levels is 2
    c7b8580c66ff mm/mremap: convert huge PUD move to separate helper
    d7e1ce9e582e mm/mremap: fix memory account on do_munmap() failure
    a2a195324435 mm/mremap: use vma_lookup() in vma_to_resize()
    7f87797e053b mm/mremap: don't account pages in vma_to_resize()
    bbebb360b5e2 mm: forbid splitting special mappings
    9fce5b920e9d mremap: check if it's possible to split original vma
    089557da4960 vm_ops: rename .split() callback to .may_split()
    c180d1867972 mremap: don't allow MREMAP_DONTUNMAP on special_mappings and aio
    e7404be1ba61 mm/mremap: for MREMAP_DONTUNMAP check security_vm_enough_memory_mm()
    5bae8c6fbfff mm/mremap: account memory on do_munmap() failure
    281904d82593 mm: refactor of vma_merge()
• PSI
  • Spoiler

    d95535a6cabf sched/psi: Fix periodic aggregation shut off
    73abf1a6b993 psi: dont alloc memory for psi by default
    UPSTREAM: psi: Fix psi state corruption when schedule() races with cgroup move
    df3995427bf1 sched/psi: Remove unused parameter nbytes of psi_trigger_create()
    feb99cdbd69e psi: Fix PSI_MEM_FULL state when tasks are in memstall and doing reclaim
    83fc90cd1a63 psi: Reduce calls to sched_clock() in psi
    f6af1db49cbd psi: Optimize task switch inside shared cgroups
    317f29565dd3 psi: Pressure states are unlikely
    7e17bae683a3 psi: Use ONCPU state tracking machinery to detect reclaim
    118d212fd15e psi: Add PSI_CPU_FULL state
• more details please check github

- patches to f2fs
- increase priority of GPU work
- binder fix
- updates from kernel/common to several subsystems
- tweak powerhal for improved performance/efficiency

• Switch between default and idle energy model on device is being interacted with / device idle.
• Reduce missed frames during scrolling/device interaction by adjust uclamp boosts.
• Dynamically adjust target load for memory interface during interaction.
• Remove dynamic GPU policy change as it´s causing instability and is unneeded due to GVFS period
• Implement handling during video recording of CPU like Google did on QPR A13 stable
• Raise minfreqs during screen off to 1,4ghz

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

 

[Schroeder09]

Awesome. I've been closely watching this thread. Waiting for your update. I've already got it flashed. Thanks so much.

 

[xflowy]

@Freak07 just sent u a little money. thanks for everything

you are german as well? saw the bayreuth location info on paypal. not far from where my gf is from heh

 

[swieder711]

Installed with no problem. Buttery smooth. Thrilled about the 3.5mm adapter fix.

 

[Not_Purgatory]

@Freak07 I can really say that the lazy stuff that you added did miracles for the idle- / deep sleep battery drain, great freak(ing) work!

Expect a beer donation when my salary comes.

 

[Tracker31]

flashed both, companion module and 1.1.0 kernel and runs great so far so good

 

[Lycidias]

Update to 1.1.0

Hey guys and girls,

So here´s the next release. I finally feel it´s ready to be publicly released as there was not a single issue encountered over the last two weeks.
Make sure to flash both, the kernel.zip and the powerhint magisk module!

The kernel is now at 5.10.155 way ahead of the stock kernel. To further emphasize the importance of this. About 90% of kernel security issues are solved in linux stable.
5.10.148 and 5.10.149 fixed the CVEs discussed here and here. Those were fixed on kernel common on November 2nd. It might take up to a few months until they trickly down into any officially shipped android kernel!
The initial 1.0.0 release, had those CVEs fixed already as 5.10.149 was merged.
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 on android devices are about 3 months behind the discovery of those vulnerabilities.

This release features a few major changes, which I want to explain in greater details, so excuse the longer release post. I´d appreciate if everyone takes the time to at least read it.

Introduction of Lazy RCU

1.1.0 has the entire(!) RCU subsystem updated to latest linux 6.0 kernel state. This also allowed for Lazy RCU to be merged into the kernel, which should result in power-savings while the device is lightly-loaded or idling (which is basically the case all the time a smartphone isn´t being interacted with (nothing touching the screen and no other workload such as video editing is done).
If you´re interested in details check the slides, which are also linked in the article I linked above.
A very simplified explanation: RCU functionality can be called 1000s of times a second, batching RCU calls can save power by not calling as often.

That´s one of the changes I wanted to be tested extensively, as there are a few 10000 lines of code changes.

Please keep in mind, those are kernel changes and battery life will not be improved magically by huge amounts, due to such a change, even if the change itself is massive.
Example: If you raise or lower the display brightness by around 10% over an entire day, you´ll see a bigger impact.
Reading the OP gives you a good idea what this project is about!


Dynamic Energy Model

Google introduced the possibility to use different Energy Models "on the fly" a while back in the Pixel 6 and Pixel 7 kernel.
I played around with this during the last few weeks and ironically Google did something similar in the QPR A13 Beta when I checked the firmware dump. Google switches to a different Energy Module while taking Videos. Based on my understanding to control heat better during video recordings.

However I had another idea, but the mechanism I use to switch the profiles taps into the same system.
While the device is idle, a different Energy Model is used, compared to when interaction is happening.
While interaction is happening there are many boosts in play already to bias tasks to get executed as quickly as possible anyway. But switching to a different energy model allows us to basically bias tasks to get even more prominently scheduled to the little and middle cores. Since the mid cores are a78 on p7 and way more energy efficient, this should give as a double positive effect. As during idle state there are no boosts active the scheduler can now freely decide how to use EAS to the best to place the tasks as efficiently as possible.
The energy module was tuned, so the scheduler prefers little and mid cores during idle. (nothing touching the screen, watching videos, listening to music, reading websites etc.)

Additionally to this I decided to include the changes Google did on A13 QPR Beta while taking video to also include already in the kernel.

Powerhal

Switch between default and idle energy model on device is being interacted with / device idle.
Reduce missed frames during scrolling/device interaction by adjust uclamp boosts.
Dynamically adjust target load for memory interface during interaction.
Remove dynamic GPU policy change as it´s causing instability and is unneeded due to GVFS period
Implement handling during video recording of CPU like Google did on QPR A13 stable
Raise minfreqs during screen off to 1,4ghz


Playback over USB C to 3.5mm Dongles
Some users were experiencing issues while using usb-c to 3.5mm dongles while running my kernel. After a long time I finally discovered how to reproduce the bug as the logs did not point towards any kernel error. It happens only if default usb configuration in developer options is set to anything else than "no data transfer". If "no data transfer" is selected there´s no issue at all.
A few commits from linux-stable for the usb dwc3 driver breaks playback when screen is shut off or cycling through the "default usb configuration" settings, which causes the aoc driver that´s responsible for playback to shut down.
Reverting those commits fixes the issue.

Thanks to @WhoIsJohnGalt1979 and @Hurt Copain for nagging me about the issue and providing logs, I finally found a way to reproduce the issue so I was able to debug it.

Given that playback is "glitchy" (a brief audio stutter) on stock kernel as well, when either cycling through different "default usb configuration" settings or turning screen on/off, that driver is generally very wonky. A user told me however that this glitch is solved in QPR Beta. So that´s good to hear if that´s the case.


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.


Changelog:

- Linux-Stable bumped to 5.10.155
- 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
- Dynamic Energy Models depending on device state
- Fix audio playback stopping for some users when turning screen off (thanks for @WhoIsJohnGalt1979 and @Hurt Copain for nagging me about the issue and providing logs)
- improve CPU throttling behaviour by backporting a QPR Beta change
- improvements to MGLRU
- improvements from linux-mainline for several subsystems

• scheduler
  • Spoiler

    02595c9fb4ec sched/core: Fix comparison in sched_group_cookie_match()
    407e4ccbb158 sched/fair: Move call to list_last_entry() in detach_tasks
    0ea56a65b686 sched/fair: Cleanup loop_max and loop_break
    0461c9736ec2 sched/fair: Make sure to try to detach at least one movable task
    f2489ca21b11 sched/fair: Cleanup for SIS_PROP
    5a3074a7ac79 sched/fair: Default to false in test_idle_cores()
    bb95868debb0 sched/fair: Remove useless check in select_idle_core()
    50112e040e6a sched/fair: Avoid double search on same cpu
    2457687f35d3 sched/fair: Remove redundant check in select_idle_smt()
• memory management
  • Spoiler

    6bf69138a12b mm: rename p4d_page_vaddr to p4d_pgtable and make it return pud_t *
    9819fcefb782 mm: rename pud_page_vaddr to pud_pgtable and make it return pmd_t *
    997cdba71861 mm: add vma_lookup(), update find_vma_intersection() comments
    eb1eccad20cb mm/page_alloc: fix obsolete comment in deferred_pfn_valid()
    1f30d4f3fb20 mm/page_alloc: remove obsolete gfpflags_normal_context()
    17dd220de848 mm/page_alloc: use costly_order in WARN_ON_ONCE_GFP()
    4d7be8d8d6d4 mm/page_alloc: init local variable buddy_pfn
    521b49f4067c mm/page_alloc: use helper macro SZ_1{K,M}
    9838ea6feaee mm/page_alloc: use local variable zone_idx directly
    d049e3821e8b mm/page_alloc: add missing is_migrate_isolate() check in set_page_guard()
    5dc1c3c60469 mm: remove obsolete pgdat_is_empty()
    55e89c7708e3 mm/page_alloc: fix freeing static percpu memory
    bd801ed8eace mm/page_alloc: add __init annotations to init_mem_debugging_and_hardening()
    ce00e122335e mm/page_alloc: remove obsolete comment in zone_statistics()
    cc20df37215b mm: remove obsolete macro NR_PCP_ORDER_MASK and NR_PCP_ORDER_WIDTH
    97e15d20dd79 mm/page_alloc: make zone_pcp_update() static
    f7425d856d30 mm/page_alloc: ensure kswapd doesn't accidentally go to sleep
    236a9831f7e4 mm: add merging after mremap resize
    bd1537226f30 mm: mremap: fix sign for EFAULT error return value
    4fe39974c254 mm/mremap: avoid unneeded do_munmap call
    3983a53d85a6 mm/mremap:: use vma_lookup() instead of find_vma()
    b832f38c3630 mm, hugepages: add mremap() support for hugepage backed vma
    23aa8d328a4c mm/mremap: allow arch runtime override
    b029910a3ec8 mm/mremap: use pmd/pud_poplulate to update page table entries
    53093a2f034d mm/mremap: don't enable optimized PUD move if page table levels is 2
    c7b8580c66ff mm/mremap: convert huge PUD move to separate helper
    d7e1ce9e582e mm/mremap: fix memory account on do_munmap() failure
    a2a195324435 mm/mremap: use vma_lookup() in vma_to_resize()
    7f87797e053b mm/mremap: don't account pages in vma_to_resize()
    bbebb360b5e2 mm: forbid splitting special mappings
    9fce5b920e9d mremap: check if it's possible to split original vma
    089557da4960 vm_ops: rename .split() callback to .may_split()
    c180d1867972 mremap: don't allow MREMAP_DONTUNMAP on special_mappings and aio
    e7404be1ba61 mm/mremap: for MREMAP_DONTUNMAP check security_vm_enough_memory_mm()
    5bae8c6fbfff mm/mremap: account memory on do_munmap() failure
    281904d82593 mm: refactor of vma_merge()
• PSI
  • Spoiler

    d95535a6cabf sched/psi: Fix periodic aggregation shut off
    73abf1a6b993 psi: dont alloc memory for psi by default
    UPSTREAM: psi: Fix psi state corruption when schedule() races with cgroup move
    df3995427bf1 sched/psi: Remove unused parameter nbytes of psi_trigger_create()
    feb99cdbd69e psi: Fix PSI_MEM_FULL state when tasks are in memstall and doing reclaim
    83fc90cd1a63 psi: Reduce calls to sched_clock() in psi
    f6af1db49cbd psi: Optimize task switch inside shared cgroups
    317f29565dd3 psi: Pressure states are unlikely
    7e17bae683a3 psi: Use ONCPU state tracking machinery to detect reclaim
    118d212fd15e psi: Add PSI_CPU_FULL state
• more details please check github

- patches to f2fs
- increase priority of GPU work
- binder fix
- updates from kernel/common to several subsystems
- tweak powerhal for improved performance/efficiency

• Switch between default and idle energy model on device is being interacted with / device idle.
• Reduce missed frames during scrolling/device interaction by adjust uclamp boosts.
• Dynamically adjust target load for memory interface during interaction.
• Remove dynamic GPU policy change as it´s causing instability and is unneeded due to GVFS period
• Implement handling during video recording of CPU like Google did on QPR A13 stable
• Raise minfreqs during screen off to 1,4ghz

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

Nice! Will we see these improvements also on your series 6 kernel?

 

[i5lee8bit]

Just wanted to mention, since I've seen it mentioned earlier in this thread, that latest release is working great on both cheetah and panther.

In particular, both phones are running AOSPMods 2.4.0... AND Dark Tricks 2.26 (I use only the battery estimate, hide user cert notification, and volume keys cursor control on the latter. Used to also use double tap lockscreen to sleep, until AOSPMods added that to 2.4.0). No reboots on either device. No guarantees, but at least with both our phones configurations, no problems at all.

 

[Schroeder09]

I've been using this all day. Not much to report yet. I started with a fresh install after having to wipe my phone last night from a simple better battery stats install. I have no idea what went wrong. The phone would run in safe mode all day. As soon as I stared normal it would freeze and reboot after about 1 minute when everything booted up. I'm not good enough to dissect ADB logs to see what's going on.

I have this kernel, magisk v25 2, lsposed, aosp mods, xprivacy lua, Pixelfy lsposed module, substratum with flux overlay theming, and the cleanslate apps installed so I can use sweep to sleep. Will a BBS install conflict with any of these?

 

[schmeggy929]

I've been using this all day. Not much to report yet. I started with a fresh install after having to wipe my phone last night from a simple better battery stats install. I have no idea what went wrong. The phone would run in safe mode all day. As soon as I stared normal it would freeze and reboot after about 1 minute when everything booted up. I'm not good enough to dissect ADB logs to see what's going on.

I have this kernel, magisk v24. 2, lsposed, aosp mods, xprivacy lua, Pixelfy lsposed module, substratum with flux overlay theming, and the cleanslate apps installed so I can use sweep to sleep. Will a BBS install conflict with any of these?

Any particular reason why you are on Magisk 24.2? There has been a lot of bug fixes since then, as the current version 25.2

 

[Schroeder09]

Any particular reason why you are on Magisk 24.2? There has been a lot of bug fixes since then, as the current version 25.2

Thanks. That was a typo. I'm on magisk 25.2. I've never heard of BBS doing this. It conflicted with something. It requested root but still didn't work. I had to issue the regular permissions via ADB. My suspicion is I fat-fingered something at that time. Based on my list of mods and setup, is there anything anyone sees as conflicting with BBS and the mods for this kernel and cleanslate features?

 

[thefinger]

What is the best order to update to the new kernel / powerhint module if we are coming from kernel v1 and powerhint module v1?

 

[binoysankar]

What is the best order to update to the new kernel / powerhint module if we are coming from kernel v1 and powerhint module v1?

I follow these steps

Flash new powerhint zip in MM
Reboot (optional)
Flash new kernel version in KF
Reboot
This works for me.

 

[thefinger]

I follow these steps

Flash new powerhint zip in MM
Reboot
Flash new kernel version in kKF
Reboot
This works for me. Not sure if this is correct or not

No uninstalling old powerhint module first?
I tried uninstalling the old module first and rebooting before installing the new one, and for a bit there magisk was complaining that it had lost root.
But after reinstalling the app it was all good again.
Had no issues installing the new kernel with Kernel Flasher though.