Disabling those flags requires an initial wipe if done for the first time unfortunately.
Was my mistake to post that last bit, copy and paste error from Pixel 7 devices.
Did you try to flash back vbmeta.img without the flag disable part? Maybe that can still prevent the wipe. But I'm not 100% sure.
verity disable do need to wipe before disabling right if not mistaken, Im using this kernel with verity enable since day one. Dont quite have the time to wipe and setup everything. So can I continue to use this kernel like before?
Where exactly to we must disable verity/verification flag in the process? Or is it only relevant for someone who wants to flash the kernel first time? I’m not sure I’ve done it when I started to use this kernel. I used to update like shown below and just flash the kernel afterwards:
2. Root & also update + re-root:
- Download latest factory image and extract it
adb reboot-bootloader
fastboot devices #to check if device is detected
fastboot flash bootloader xxx.img #updating to latest bootloader from downloaded image
fastboot reboot-bootloader
fastboot flash radio xxx.img #updating to latest radio from downloaded image
fastboot reboot-bootloader
fastboot --disable-verity --disable-verification update xxx.zip #updating to latest version and (again) disabling verification.
- Now the phone will reboot into Android without being wiped
- Install latest canary Magisk
- Extract and copy boot.img from factory image to phone
- Patch boot.img with Magisk
- Copy patched boot.img to PC
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
I hope everyone started well in the new week. Here´s the next release and it´s a really big one. I know some of you already peeked over to the Pixel 7/Pro forums and asked if the changes from there will also find their way to the Pixel 6/Pro release.
The answer is yes, except one change that´s not easy to cleanly implement as of now. If I´m going to implement something I want it to be done cleanly so that I´m content and happy releasing it, as of now this didn´t work out as I hoped. If time allows I plan to revisit that in the future however.
This release includes the QPR (quartly platform release) changes and is now on the same state as A13 QPR Beta was previously. You need to be on December firmware release to be able to install this kernel!
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.
MGLRU V15
Amongst the QPR changes from Google, which are a big step ahead of the initial A13 release (always the case the last years, the december update fixes tons of things of the major android version bump), MGLRU was bumped to latest V15 state, which was also merged to the linux-kernel recently. Was testing this out for nearly a month, before releasing. For those interested about MGLRU, here´s an excellent writeup by @MishaalRahman.
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!
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. (that´s why I wasn´t able to reproduce the behaviour)
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 and the framework part in regards to the different USB default configuration states is generally very wonky. That´s probably also why selecting default USB configuration is "hidden away" in developer options.
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!
I wish everyone a nice day.
If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.
Changelog:
- Import December QPR changes
- Linux-Stable bumped to 5.10.157
- Bump prebuilt clang to latest 16.0.1 from Google
- important improvements and fixes to binder
- bump MGLRU to latest V15 state
- 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
- 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
- fix to memory management
- 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
- patches to f2fs to sync with latest f2fs-stable
- binder fix
- updates from kernel/common to several subsystems
- import all improvements from google QPR to powerhint module
- tweak powerhal for improved performance/efficiency
Dynamically adjust target load for memory interface during interaction.
- other fixes please check github
Download:
Attached to release post as AFH does not allow me to upload files at the moment.
I´ll push to AFH once it´s back up.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
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
Hey freak just a question off topic I know it's early. But.. Could it be possible to port clear calling feature to older pixels? The same way adaptive sound was ported a few years back using magisk?
Hey everybody, I guess I was not the only one being a bit disappointed that google didn´t make adaptive audio available for the Pixel 4 devices as well. To be honest I personally think it´s a bit of a gimmicky feature that´s not very critical...
Hey freak just a question off topic I know it's early. But.. Could it be possible to port clear calling feature to older pixels? The same way adaptive sound was ported a few years back using magisk?
Hey everybody, I guess I was not the only one being a bit disappointed that google didn´t make adaptive audio available for the Pixel 4 devices as well. To be honest I personally think it´s a bit of a gimmicky feature that´s not very critical...
Had to donate... My battery life on p6 has improved dramatically... This is a massive update and now I'm really lovin my phone. 5g UC used to kill my battery now it's almost like having on 4g lte drainage. I almost want to switch back to lte to see how crazy the battery life is there now however, I'ma leave it on 5g from now on. Really appreciate the time and effort.
Had to donate... My battery life on p6 has improved dramatically... This is a massive update and now I'm really lovin my phone. 5g UC used to kill my battery now it's almost like having on 4g lte drainage. I almost want to switch back to lte to see how crazy the battery life is there now however, I'ma leave it on 5g from now on. Really appreciate the time and effort.
Had to donate... My battery life on p6 has improved dramatically... This is a massive update and now I'm really lovin my phone. 5g UC used to kill my battery now it's almost like having on 4g lte drainage. I almost want to switch back to lte to see how crazy the battery life is there now however, I'ma leave it on 5g from now on. Really appreciate the time and effort.
Latest kernel on December is noticeably cooler on setup and 0 lag in Gboard and recents. Sometimes it takes a big bump to notice how much micro jitter it had before.
- download Dec base
- extract boot.img, patch it in magisk and copy patched img to PC
- flash Dec base and patched img
- flash Kiri kernel with exkm or any other app
I dont know If it's kernel related but I hope u can tell me at least. The last months the Google timeline worked perfectly, but in the mid of October it completely stopped working. That's the time I flashed the October update and flashed back your kernel. Including my drive backup.
Yesterday I checked and just wondered why jts broken and checked my settings, that were still the same.
Today I flashed the Dec update and with stock kernel, the timeline is working again. After having flashed your kernel, its broken again. I did a clean flash with no backup.
Has something changed in the last revisions that could affect that?
I don't want to say it has something to do with your kernel, im just asking.
I dont know If it's kernel related but I hope u can tell me at least. The last months the Google timeline worked perfectly, but in the mid of October it completely stopped working. That's the time I flashed the October update and flashed back your kernel. Including my drive backup.
Yesterday I checked and just wondered why jts broken and checked my settings, that were still the same.
Today I flashed the Dec update and with stock kernel, the timeline is working again. After having flashed your kernel, its broken again. I did a clean flash with no backup.
Has something changed in the last revisions that could affect that?
I don't want to say it has something to do with your kernel, im just asking.
The timeline accessible in google maps? If you tap on the top right corner on your profile picture, then my timeline?
I can´t spot anything broken on my end there. What exactly do you mean by it´s broken?
So here´s the next release for stable March firmware, which is now QPR2 based. This results in quite a lot of changes and improvements in the vendor specific drivers!
Aside from that as already hinted at in the 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.
Please note there are still separate zips due to the powerhal being different and the ramdisk in vendor_boot not being exactly identical.
As part of this development all improvements from the linked pixel 7 release found its way into this release plus a few more. So this time you guys are the first.
Short explanation follows below.
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 canary or canary 25206.
Latest platform tools have issues flashing super.img, please use platform tools 33.0.3!
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.
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.
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
- 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
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- ported improvements from QPR3 beta
- 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
- 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 not delete and keep the powerhint ak3 module installed via Magisk Manager after flashing!
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing or simply dirty flash. 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
Yes, I understand. I have been using the CleanSlate battery saver to keep temps down myself. I was just curious where all the logic is for the thermal throttling that is based on the various sensors. I'd love to take a look at it myself. I'm not necessarily looking to just increase the limits. I want to understand it more.
As a side note, I find that a lot of heat is actually produced from the modem (even on LTE) as I'm often on the road and don't have WiFi. If you start transferring large files the phone quickly heats up.
Yes, cpu is only one source of heat.
As you already pointed out modem is another one, just like the camera array itself will produce heat while using it (especially noticeable while taking videos, which presents two issues, if cpu is throttled to much hi-res video might produce stutter, if heat is not kept in check camera sensors might get damaged).
If you want to take a look at the thermal throttling you can find this on the device tree. This one is for p6 pro (raven).
Can someone take a look at the attached logs and see why my phone's been shutting off randomly? It started after installing the Feb update and 4.4.2. I don't necessarily think it's the kernel, but want to rule it out. Thanks!
To keep it short: Here is Kirisakura - Kernel for the Google Pixel 6 Pro aka Raven and the Pixel 6 aka Oriole, together Raviole.
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.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
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
- Linux-Stable-Upstream included to 5.10.170
- 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!)
- FHD Support for Pixel 6 Pro (display is able to run at 1080p), more info here and here
- 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
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- Utilize an additional kswapd thread to increase throughput for memory reclaim
- 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
- improve trusty driver performance which connects to fingerprintscanner-hal by using high perf wq during fp unlock
- restrict maximum CPU-Freqs during screen off/ idle to 1.1GHZ 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 updates from linux-main
- use improved energy model for exynos cpu cooling/thermal control
- allow GPU to scale down to 150mhz, but boost to higher value in case of interaction via powerhal
- 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
- Include LRNG, see here and here for more info, bump to v45 with 3.0.0
- important patches from kernel/common for 5.10 (here are more details)
- 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)
- dirty pipe exploit fixed
- supports direct usb access for hi-res playback over USB-C DACs
- improve ZRAM usage
- flashing the kernel will preserve root
AK3 Helper Module:
- restrict little cluster to 1,19ghz mid cluster to 1,19ghz and big cluster to 1,1ghz during screen off, to reduce battery usage for example during music playback
- only use little cores during screen off/device suspend
- 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)
- dynamically adjust target load for memory interface during interaction
- boost memory interface controller during interaction (decreased missed frames, improved soc efficiency according to google docs)
DOWNLOAD:
Download is always located in this folder:
4.2.0, 4.3.0, 4.4.0, 4.4.1, 4.4.2 are attached to the release posts linked below as AFH is wonky at the moment.
- the kernel is made for the stock firmware provided by Google, pay attention to flash a kernel release matching the firmware (flashing on custom roms might work, but you may need workarounds!)
- 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 stable in case you want to be absolutely safe)
- IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13! (take a look here)
How to flash the Kernel:
1a. Make sure you tick all the requirements above
1. Download the correct kernel.zip depending on your device (Pixel 6 = oriole || Pixel 6 Pro = raven)
2. Flash the correct kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved. The AK3 magisk helper module will be automatically installed during flashing the kernel.zip and be present on next reboot.
Do not remove or disable the AK3 Magisk Helper Module otherwise the device will bootloop.
3. Reboot and profit.
Manual installation is no longer supported starting with release 3.0.0, as there´s a free open-source option to flash kernel.zips now.
Instead use the free kernel flasher, which can be found here.
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 pixel 6! @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!
I hope everyone started into a good week. Here´s the next release. It´s for stable Android 13.
Thanks to Google releasing the kernel source for the previews and the betas I´m able to push this update out very quickly. As in the past, the code didn´t change between last beta and stable release.
There are again a lot of changes in this release. I´ll try to keep the release post short as I don´t have that much time lately.
FHD/1080P Support for Pixel 6 Pro
The biggest change is FHD support for the Pixel 6 Pro. If you follow twitter you might have seen this tweet from @MishaalRahman.
Instead of using the display driver that´s supposedly for the Pixel 7 Pro, FHD support was added to the Pixel 6 Pro display driver. There were a few obstacles to make it run properly on the Pixel 6 Pro, but I got it working nicely so far. If anyone has more experience than me regarding panel timings, display drivers etc, feel free to push any improvement as a pull request to my github or point me towards any improvement.
As a result you can now select 1080p resolution from settings after flashing the kernel. Dynamic refresh rate works, brightness scaling works, no tints, colour shifts or contrast issues either. AOD has a 1080p Low-Power timing as well.
You´ll find a few more infos with a short video on my tweet here:
It´s perfectly usable on a daily basis so far. I ran it for a few days without issues on my end. While the advantage might be debatable (saving battery, less load on GPU, still needing to drive the same amount of pixels in the end even on lower resolution, etc etc) having options is nice and this is why I decided to ship it.
Apps need to redraw after switching resolution, sometimes 1080p on big display size selected in settings the UI looks a bit sketchy. So I think Google is still working on that.
There´s however one bug I found so far that makes me believe this is still very much a WIP from google. If having the "show current refresh rate" option from dev settings enabled while switching resolutions, the display will black out and a restart needs to be forced by keeping the power button pressed or using adb interface to restart the phone. This is not due to the kernel, but display settings in framework getting scrambled as it´s not yet implemented 100% on googles end. So be warned.
MM Subsystem Rework
MM subsystem was completely reworked including many improvements from linux-mainline. During this MGLRU was also reworked a bit and works better now. I´ll include links to a few of the improvements/patchsets in hide-tags below, if you´re interested beyond that please check out my github.
links:
Additionally tie in a few of the MM changes into the powerhal. For example Proactive compaction is more aggressive during screen-off/device suspended operations to improve long term-performance.
Other changes:
Also tune the powerhal and implement all A13 changes, according to the changes that were already present on A12.
Latest changes from f2fs-stable are included, which include several bugfixes and small improvements.
Binder improvments/fixes, scheduler improvements from kernel/common, performance for exfat formatted storage device improved (niche use case, but still nice) and other little improvements.
For other changes and details please take a look at github.
I wish everyone a nice day.
If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.
Changelog:
- Rebase kernel fully on A13 trees
- Linux-Stable bumped to 5.10.136
- FHD/1080p support for Pixel 6 Pro
- all previous features and improvements kept intact
- bump f2fs-stable to latest available
- rework mm subsystem (check git for more details)
- scheduler improvements
- binder improvements from kernel/common
- improve exfat performance (if someones uses exfat formatted devices)
- loads of other changes from kernel/common - update powerhal to account for a13 changes and port existing changes over
- loads of other changes, please check github
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
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
I hope everyone started well in the new week. Here´s the next release and it´s a rather big one with lots of under the hood improvements.
We already had all the changes in from the October security patch release released, due to merging linux-stable stable and kernel/common in advance.
The kernel is now at 5.10.146 way ahead of the stock kernel. To further emphasize the importance of this. About 90% of kernel security issues are solved in linux stable. While I didn´t check the actual number myself, I´d have estimated about the same (80-90%) before actually reading the slides from @arter97 presentation.
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 are about 3 months behind the discovery of those vulnerabilities.
Amongst linux-stable upstream there are a few other not minor updates in this kernel.
Clang
The kernel is now compiled with the latest prebuilt Clang from Google. This was quite a journey as this is a pretty big update to clang. This is quite experimental to be on googles side of a "bleeding" edge compiler, but after fixing several issues that originated from the new compiler it ran stable for over 2 weeks.
There´s a potential for CFI failures that originates from that new Clang rather than a "real attack", due to the changes in clang.
Short reminder what CFI actually does: Control flow integrity (CFI) is a security mechanism that disallows changes to the original control flow graph of a compiled binary, making it significantly harder to perform such attacks.
A typical crash (that´s not wanted and originates from compiler changes rather than an actual attack, which is already resolved of course ) would look like the following: Open camera app, due to compiler changes CFI is accidentally tripped every time this code is executed.
I think we catched all of these newly CFI failures and everything is nice and stable. In case you discover such a behaviour please send me the contents of sys/fs/pstore, once the phone booted back up.
There´s always the possibility of a "real" attack in which CFI will crash the phone, before the attacker can compromise the phone. That´s why keeping subsystems updated is important.
Powerhal
The powerhal was retuned due to changes to the scheduler introduced. It should work even better now, regarding efficiency and performance. Of course I try to tune it also to my personal needs, while trying to keep it working for all workloads. The changes are not drastic, so please don´t post after several hours you see drastic differences.
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.
If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.
Changelog:
- Linux-Stable bumped to 5.10.146
- kernel is compiled with latest prebuilt google clang 15.0.2
- improvements from linux-mainline
locking subsystem
memory management
more details please check github
- patches to f2fs
- updates from kernel/common to several subsystems
- tweak powerhal for improved performance/efficiency
Download:
Attached to release post as AFH is currently down.
I´ll push to AFH once it´s back up.
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
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
So here´s the next update. It´s kind of an off schedule update, as I planned to update the kernel with the next security update/feature drop.
But in the light of recent events regarding the new exploit called "Dirty Pipe" (more info here), which is similar to the "Dirty Cow" exploit from a while ago, but easier to exploit this time, I decided to release an update ahead of schedule.
This exploit was fixed in linux-stable 5.10.102, as opposed to a single commit in AKC (android kernel common, commit here). This shows once more why merging linux-stable is beneficial as explained in detail in the OP.
Since one of the key aspects of this kernel is security and staying on par with upstream (which often fixes exploits way ahead of android security bulletin updates, even before an exploit is even known or fixed via a patch on the security bulletin) I decided to release this update as quickly as possible, so this exploit is fixed on devices running this kernel.
Several other notable improvements and changes in this release:
Bring in scheduler updates from Android 13 Developer Preview, which aim at improving task placement. (adjust powerhal accordingly)
BFQ IO-Sched is now on par with linux-mainline.
Several fixes to mm subsystem, f2fs and others.
Several other improvements are included as well. More details in the changelog.
Download is below.
Updated instructions in the OP!
Changelog:
- linux-stable 5.10.103
- contains fix for the dirty pipe exploit
- built with clang 14.0.2 prebuilt by google
- improvments from kernel/common
- fix memory leaks
- security related patches
- mm improvments
- f2fs fixes
- scheduler fixes
- for details please check github
- built with improvements from A13 Dev Preview to display driver
- other changes please look at my github
Instructions can be found in the OP! Please follow the instructions to avoid any issues.
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
So here´s the next update. It includes the february security update. Most of the changes brought by the February kernel source drop, were already included in this kernel by merging kernel/common and linux-stable.
Several other notable improvements and changes in this release:
Improve f2fs performance by merging a patchset to prevent writer starvation for the checkpoint thread. This was discussed this month in the f2fs mailing list and is already merged to the kernel/common tree. It´ll improve performance under heavy I/O utilization.
You can find more information following the discussion here.
Necessary backports were brought to the kernel and the platform specific f2fs-implementation was also adjusted.
Latest f2fs-stable was also merged to the kernel.
Update the patchset to prevent frequency spikes caused by small tasks as well. Tie those new changes into the powerhal. (That means users not flashing the kernel.zip, but instead use the manual installation method, which are only a handful from the download count, need to flash the updated magisk helper module. Users that flash the kernel.zip via FKM/EXKM have to just flash and forget)
Several other improvements are included as well. More details in the changelog.
Download is below.
Updated instructions in the OP!
Changelog:
- February Security update merged
- linux-stable 5.10.96
- include latest f2fs-stable
- improvments from kernel/common
- fix memory leaks
- security related patches
- mm improvments
- for details please check github
- introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf
- update patchset to prevent freq spikes caused by small transient tasks (also tie this into powerhal)
- give pelt multiplier power hint for scheduler performance boost during fingerprint unlock
- 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
- update LRNG implementation (thanks to arter97 )
- improvements/fixes for CleanSlate features
- other changes please look at my github
Instructions can be found in the OP! Please follow the instructions to avoid any issues.
If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
