No problems on my end with google wallet.
Might be a problem with either some safetynet fix module or other means that try to get safetynet spoofed.
Or google is tightening the screws yet again.
Development [Kernel][23.03.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.0.1 for Pixel 7/Pro aka "Pantah"
- Thread starter Freak07
- Start date
Might be a problem with either some safetynet fix module or other means that try to get safetynet spoofed.
Or google is tightening the screws yet again.
Oh man, I really messed up:
I really did not have much time past few weeks so I'M behind in system updates.
Yesterday phone ran our of battery, I connected it to charge without thinking twice.
As I did not have automatic updates disabled (really my fault here) it started up and applied the pending system update, restarting in the other slot.
So I guess vbmeta has been reset and I will have to wipe the whole phone over again to get back.
I'm so frustrated. Pretty disappointed in myself honestly.
Sorry, just venting.
I really did not have much time past few weeks so I'M behind in system updates.
Yesterday phone ran our of battery, I connected it to charge without thinking twice.
As I did not have automatic updates disabled (really my fault here) it started up and applied the pending system update, restarting in the other slot.
So I guess vbmeta has been reset and I will have to wipe the whole phone over again to get back.
I'm so frustrated. Pretty disappointed in myself honestly.
Sorry, just venting.
They do for kernel, because of GPL I guess.
A few bits are in there yes, but nothing too special.
TY! Did not realize that....They do for kernel, because of GPL I guess.
A few bits are in there yes, but nothing too special.
I may be a bit late, but ive observed that the Safetynet Module spoofs your Phone as Nexus 5G and that interferes with features like ,,Tap to Login,, and GPay etc etc. For me.
To try to conclude this topic:
I´m still using the module "safetynet-fix-v2.3.1-test" as I heard the 2.4.0 one causes issues. I used wallet to pay yesterday without any problems.
It´s not related to anything from kernel so please try to search for threads where this actually belongs before the off topic takes overhand, e.g. this one.
Otherwise it may get really confusing for new/inexperienced users.
Thanks everyone.
Slim2none4u
Senior Member
- Oct 28, 2011
- 882
- 546
- 49
Thank you!!!!To try to conclude this topic:
I´m still using the module "safetynet-fix-v2.3.1-test" as I heard the 2.4.0 one causes issues. I used wallet to pay yesterday without any problems.
It´s not related to anything from kernel so please try to search for threads where this actually belongs before the off topic takes overhand, e.g. this one.
Otherwise it may get really confusing for new/inexperienced users.
Thanks everyone.
To try to conclude this topic:
I´m still using the module "safetynet-fix-v2.3.1-test" as I heard the 2.4.0 one causes issues. I used wallet to pay yesterday without any problems.
It´s not related to anything from kernel so please try to search for threads where this actually belongs before the off topic takes overhand, e.g. this one.
Otherwise it may get really confusing for new/inexperienced users.
Thanks everyone.
I could figure it out eventually. After flashing the module and kernel via FKM, and rebooting the phone I got the same issue. Bummer. But after going to stock kernel I had to wipe Google Play Services and Wallet, and reboot to get rid of the problem. So did I after flashing your kernel. The error message in Wallet is gone and I just paid in a bakery. You might want to add this to your FAQ/ troubleshooting category. Finally I'm back on your fine kernel.To try to conclude this topic:
I´m still using the module "safetynet-fix-v2.3.1-test" as I heard the 2.4.0 one causes issues. I used wallet to pay yesterday without any problems.
It´s not related to anything from kernel so please try to search for threads where this actually belongs before the off topic takes overhand, e.g. this one.
Otherwise it may get really confusing for new/inexperienced users.
Thanks everyone.
I did everything as described but my device keeps getting stuck in a bootloop =/
Any suggestions?
I'd love to run this kernel
Any suggestions?
I'd love to run this kernel
Nice catch, glad you found a workaround that solved the issue.I could figure it out eventually. After flashing the module and kernel via FKM, and rebooting the phone I got the same issue. Bummer. But after going to stock kernel I had to wipe Google Play Services and Wallet, and reboot to get rid of the problem. So did I after flashing your kernel. The error message in Wallet is gone and I just paid in a bakery. You might want to add this to your FAQ/ troubleshooting category. Finally I'm back on your fine kernel.
But I´m still pretty sure something else might be up on yourend that´s causing that issue in the first place. I went back between stock kernel and my kernel probably a few hundreds of times, as well as running with or without the module and google wallet never stopped working.
which firmware are you running?
custom roms might be hit or miss and qpr beta firmware is not supported.
I'm running TQ1A.230105.002
I have done a full wipe, fresh install with PixelFlasher so it takes care of the verity/verification and stil I get stuck in this bootloop every time.
Hello everyone,
I haven't had success installing this kernel, when I tried to install it using both FKM and Kernel Flasher it would get into a reboot loop at the "Google" logo (sometimes it would occasionally animate into the single G but then reboot again). I reflashed the stock firmware using Android flash tool and ensured disable verification and disable DM-Verity were turned on however I still have not been able to install it successfully. I installed the magisk module and the kernel itself then rebooted. Is there a step I'm missing? I'm on the Pixel 7 Pro with the January 2023 security patch.
I haven't had success installing this kernel, when I tried to install it using both FKM and Kernel Flasher it would get into a reboot loop at the "Google" logo (sometimes it would occasionally animate into the single G but then reboot again). I reflashed the stock firmware using Android flash tool and ensured disable verification and disable DM-Verity were turned on however I still have not been able to install it successfully. I installed the magisk module and the kernel itself then rebooted. Is there a step I'm missing? I'm on the Pixel 7 Pro with the January 2023 security patch.
Were you asked to wipe the device after disabling verity/verification when it booted back up?
There´s no other thing that could interfere other than verity/verification not being disabled properly if you follow the instructions. No issue flashing/running the kernel on TQ1A.230105.002 google firmware. (custom roms can be a different story, no support for qpr betas)
If you check the FAQ there´s a magisk module to check the state of the verity/verification flags on your device.
No I wasn't asked to wipe it, although I did check the status of Verity and verification using the magisk module and it says both are disabled. I'm quite unsure of what the problem is. My exact build number is TQ1A.230105.002.A1 if that makes a difference.
Edit: Also I have a question, in case I retry installing your kernel again and it doesn't work, am I able to restore back to stock by flashing the appropriate images and I won't lose data instead of flashing the whole firmware and wiping in Android Flash Tool? And then to retain root, I can use my Magisk patched boot_init image instead of the stock firmware's one?
Last edited:
You can try manually flashing the vbmeta.img (from the factory image of the firmware you´re currently running) with the disable flags command via fastboot and see if that changes anything instead of using the flash tool.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.imgAlternatively try to only flash the kernel.zip without the module, maybe you have a magisk module that conflicts. Remove any other mods you´re running in any case.
Check the FAQ on how to restore back to stock.
If you manually restore only the single images mentioned there, root won´t be impacted (as kernel don´t touch init_boot.img), if you flash whole firmware you need to re-root. If you flash whole firmware vbmeta flags will reset to default (enabled) if not specified otherwise.
Okay thanks I'll try it and see, does running the disable flags fastboot command require a data wipe? Or will it work fine as is?You can try manually flashing the vbmeta.img (from the factory image of the firmware you´re currently running) with the disable flags command via fastboot and see if that changes anything instead of using the flash tool.
Code:fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Alternatively try to only flash the kernel.zip without the module, maybe you have a magisk module that conflicts. Remove any other mods you´re running in any case.
Check the FAQ on how to restore back to stock.
Also, if I restore those single images required to go back to the stock kernel, will that need a data wipe?
Top Liked Posts
-
There are no posts matching your filters.
-
31Update 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!
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/freak0728Update 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/freak0722Thanks @Clark Joseph Kent for cleaning the thread up.
The source for the March update hasn´t been pushed yet. A kernel with the QPR2 Beta changes is being tested at the moment and it´s running fine so far on march stable. If it´s like the last QPR bump in December there are no kernel changes between the last QPR Beta and the stable QPR release (at least kernel wise).
Interestingly it seems the previous release might still be working/booting on March update. If you want to make sure there are no issues and don´t feel adventurous it´s probably best to wait for the next release.
Depending on when google pushes the source for stable march firmware (usually during night time on my location) for me to check and when I find time I´ll try to update as soon as possible.
Please keep things civil and friendly in here.20Update to Raviantha 1.0.1
Hey guys and girls,
That´s a hotfix for 1.0.0 and the previous release. The recent update to the f2fs drivers from beginning of March seem to have introduced a null pointer exception that happens very very rarely. Thanks to @JakeDHS07 for providing the logs! I also submitted this to f2fs-stable so hopefully it can be fixed there.
Until a proper fix is found I´m going to revert the tag of f2fs patches that introduced this bug. That´s the only change in 1.0.1.
I´ll include the previous release post with all the information below.
Changelog 1.0.1:
- revert latest f2fs stable patches
Changelog 1.0.0 above:
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 -
78Kirisakura-Kernel for the Pixel 7/Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Google Pixel 7 Pro aka Cheetah and the Pixel 7 aka Panther, together Pantah.
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.
By merging linux-stable regularly we get most security updates months ahead of the stock kernel and also before they even end up in the android security bulletin.
The kernel includes a lot of improvements and contributions from other developers as well. Without those contributtion this kernel would not exist as it is.
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 Stable
- Linux-Stable-Upstream included to 5.10.175
- Compiled with prebuilt Google clang 17.0.0
- 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
- Backport Maple tree from Linux 6.1
- Per VMA-locks in conjunction with Maple Tree RCU-Mode (improve app launch time, this feature in general benefits greatly from lazy rcu!)
- Dynamic Energy Models depending on device state
- improve CPU throttling behaviour
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- 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
- 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
- restrict maximum CPU-Freqs during screen off/ idle to 1.4GHZ 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
- merge and enable f2fs block_age-based extent cache (improve the accuracy for data temperature classification, reduce the garbage collection overhead after long-term data updates)
- TCP backports from mainline
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- scheduler backports from linux-main
- mm updates from linux-main
- locking updates frm linux-main
- improve memory performance by tweaking google´s eh zram implementation
- fix sysfs endpoint for googles eh zram
- 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
- important patches from kernel/common for 5.10 (here are more details)
- increase priority of GPU work
- several updates from QPR beta, and a few from Pixel 6 that googles missed to include in the pixel 7 kernel
- improve thermals
- change compaction proactiveness based on device state for improveed memory management
- improve ZRAM usage
- flashing the kernel will preserve root
CleanSlate Features
- 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)
- Check the CleanSlate thread for more information about those features
- The CleanSlate thread also contains the apps that allows you to control those features!
- If you consider those features useful, maybe consider purchasing the apps in the PlayStore or a small donation to @tbalden, he deserves it! Don´t forget to switch to beta channel for those apps, as this is needed for device running A13!
Various Optimizations:
- update several drivers to use power efficient workingqueues (for example wlan driver)
- f2fs: reduce timeout for uncongestion
- f2fs: Demote GC thread to idle scheduler class
- f2fs: set ioprio of GC kthread to idle
- tcp: enable advanced tcp, give user more options for tcp alorithm
- mm: vmstat: use power efficient workingqueues
Wakelock Blocker:
- advanced wakelock blocker with the ability to block kernel wakelocks (dangerous, use with caution, please read this for further info). You should only block kernel wakelocks in case you face uncontrollable scenarios, like company wifi causing a wakelock to be active 100% of the time! Blocking kernel wakelocks to "improve" battery life almost always backfires and causes issues!
Powerhint Module:
- restrict little cluster to 1,4ghz mid cluster to 1,4ghz and big cluster to 1,4ghz during screen off, to reduce battery usage for example during music playback
- only use little cores during screen off/device suspend
- account for scheduler and other changes done to the kernel
- boost memory interface controller during interaction (decreased missed frames, improved soc efficiency according to google docs)
- 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)
- switch between default and custom idle energy model on device is being interacted with / device idle.
- reduce missed frames during scrolling/device interaction by adjusting 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
- more small improvements
DOWNLOAD:
Download is always located in this folder:
Mirror for Download 1.0.0, in case AFH is not working
Mirror for Download 1.1.0, in case AFH is not working
Mirror for Download 1.2.0, in case AFH is not working
Mirror for Download 1.2.1, in case AFH is not working
Mirror for Download 1.2.2, in case AFH is not working
Mirror for Download 1.2.3, in case AFH is not working
Mirror for Download 1.2.4, in case AFH is not working
Changelog:
Android 13.0.0 Stable (not QPR beta!)
1.0.0 Initial Release | Mirror for Download in case AFH is not working
1.1.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87743627
1.2.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87822161
1.2.1 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87878321
1.2.2 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87944505
1.2.3 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87960183
1.2.4 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88108123
1.3.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88286027
Raviantah_1.0.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88316285
Raviantah_1.0.1 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88323527
Requirements
- 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
- 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, use stable in case you want to be absolutely safe)
- IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13 before you flash anything to your device!
- it´s handy to have a backup and a way to return back to stock (check the faq for that)
- make sure to download the correct kernel version for your firmware. (you can´t flash a kernel made for stable firmware on a QPR beta or dev preview and expect there to be no isses)
- read the first and second post, there's a lot of valuable information
How to flash the Kernel:
1a. Make sure you tick all the requirements above
1b. Make sure to flash the release made for your firmware! Usually the release post contains information on that
1. Download the kernel.zip (unified for both devices) and the correct powerhint module depending on your device (Pixel 7 = panther || Pixel 7 Pro = cheetah)
2. Flash the powerhint module via magisk manager as you would any other magisk module! Make sure to flash the latest one. It will be mentioned in the release post if there´s an update.
3. Flash the kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved.
4. Reboot and profit.
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 pixels, avb, hashtree patcher, the counsel and the kernel flasher!
@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/freak0751Update to 1.2.4
Hey guys and girls,
So here´s the next release. February source did basically not contain anything new for this kernel (as all patches were already included since months due to merging linux-stable and kernel/common in advance) except a stability and a security fix for the GPU driver (which is vendor specific so of course not impacted by linux-stable etc).
Nonetheless this is a very big release with large underlying changes.
Short explanation follows 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
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.
App launch times in ms for cold launching slack app with and without the Per-VMA lock patchset:
F2FS block_age-based extent cache
Latest f2fs-stable update contained an interesting new feature called block_age-based extent cache. It´s another optimization done in hindsight to android needs. It´s always nice to see different OEMs (in this regards xiaomi) cooperating and improving android as a whole and not just keep those patches to themselves. Since it´s pushed to f2fs-stable it will sooner or later (probably rather later as trickling through until it ends up on actual production devices always takes a lot of time) find its way to the majority of android devices.
The features allows to record data block update frequency of the extent per inode, in order to provide better temperature hints for data block allocation thereby improving the accuracy for data temperature classification and reducing the garbage collection overhead after long-term data updates.
Memory Interface Controller Boosting
Boost Memory Interface Controller slightly to a fixed min_freq value during interaction, instead of relying solely on the governor taking the decision as it doesn´t ramp up fast enough during interaction in some cases.
Research of exynos/tensor characteristic shows that the SOC does not perform optimally when cpu freqs ramp up quickly (during interaction, scrolling, touch the screen) and memory interface controller not following suite quite fast enough. This makes the soc overall perform less efficient. The boost aims to correct this behavior.
The boost also results in a tiny few less missed frames during interaction as a bonus.
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.167
- Backport Maple tree from Linux 6.1
- Per VMA-locks in conjunction with Maple Tree RCU-Mode (this benefits greatly from lazy rcu!)
- bump f2fs to latest f2f2 stable state
- merge and enable f2fs block_age-based extent cache (improve the accuracy for data temperature classification, reduce the garbage collection overhead after long-term data updates)
- improvements to the scheduler from QPR2 Beta 2 and Beta 3
- improvements to memory management from QPR2 Beta 2
- improve ZRAM usage
- boost memory interface controller during interaction (decreased missed frames, improved soc efficiency according to google docs)
- import security fixes and performance improvments to camera driver from QPR2 Beta
- fixes/improvements to to memory management
- security fixes/ improvements from kernel/common
- 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/freak0749Update to 1.2.1
Hey guys and girls,
So here´s the next release. As already hinted it includes some of the kernel changes from the QPR2 Beta. Please note the kernel is made for the stable firmware! You need to be on December stable firmware release to be able to install and run this kernel properly!
Make sure to flash both, the kernel.zip and the powerhint magisk module as both are updated.
Google did some significant updates in that latest qpr2 update, which is great to see.
The GPU driver is now based on version r38p1. This fixes several vulnerabilities that made the news recently.
AOC driver and WiFi driver were also updated and most of those improvements ended up in this kernel release as well.
There were several improvements to memory management done by google, which should result in improved efficiency, improved reclaim and also reduced jank.
There are a few other nice patches that should improve performance and generally improve system responsiveness. For specifics please check those on github.
Scheduler patches from linux-main are also included.
The lazy rcu patchset was updated to the latest state that was also recently merged into the linux kernel. (more info about lazy rcu check here)
Kernel is now compiled with latest 16.0.2 prebuilt Clang from Google.
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.159
- Bump prebuilt clang to latest 16.0.2 from Google
- include most of the QPR2 improvements so we can enjoy them ahead of time
- fixes/improvements to to memory management
- import all improvments from google QPR2 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.
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/freak0741Update 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
-
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
-
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
-
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
- 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.
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 - scheduler
