Development [Kernel][06.03.2024][Android 14.0.0]Kirisakura 2.2.0_Raviantah for Pixel 6/Pro aka "RAVIOLE"

Search This thread

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,441
23,040
Update to 1.3.0

Hey guys and girls,

Alright here´s the next update and it´s a really big one.
Some of you used to run Kirisakura on the Pixel 4 XL and just like on that device today we were joined by @tbalden and his excellent features available in his CleanSlate kernel. Thanks a lot to him for his dedication and time he put into the features again. Finally sweep to sleep made its glorious return. :)
This release has the CleanSlate features working for Pixel 6 Pro users. Unfortunately they don´t work on the Pixel 6 at the moment.
Please follow the instructions in the CleanSlate thread to get the CleanSlate apps working correctly.

As previous kernels of mine, this kernel has now been upstreamed to latest linux-stable 5.10.79 (at least latest at the time of testing)
kernel/common 5.10 for android 12 has been completely merged as well, which includes a lot of updates and optimizations as previously mentioned. The previous release only had some excerpts from that. kernel/common 5.10 for android 12 is currently at 5.10.66, I except this drops to stock in the next few months.

Several other improvements are included as well. More details in the changelog.

Please flash all three provided images according to the instructions. If you don´t flash vendor_dlkm CleanSlate features will not work and you´ll lose some of the other optimizations. dtbo.img should be stock for now, but eventually there will be changes. It´s best to adjust to the instructions now to provide confusion later. :)
I hope I can work out non-userdebug vendor_boot.img later, so we can just flash all four images and be fine all the time.


I´ll keep that here just in case.
I discovered that my compiled vendor_boot.img is a userdebug build. That´s the reason developer settings crashed on 1.0.0, due to a selinux-denial that happens because of userdebug.
Since we don´t modify anything yet that ends up in vendor_boot.img please flash back the original one from the factory image you´re device is running on in case you´re still running it.
Boot to bootloader and execute the following command:

Code:
fastboot flash vendor_boot vendor_boot.img

Then proceed to flash the other images as described in the guide in the OP!



Changelog:
- linux-stable 5.10.79
- kernel/common merged
- CleanSlate features added
- update several drivers to use power efficient workingqueues (for example wlan driver)
- kernfs: use buffer from the stack space
- printk: use buffer from the stack space
- kthread: use buffer from the stack space
- bpf: avoid dynamic memory allocation for small value buffers
- binder: Reserve caches for small, high-frequency memory allocations
- kernfs: use kmem_cache pool for struct kernfs_open_node/file
- cgroup: use kmem_cache pool for struct cgrp_cset_link
- f2fs: reduce timeout for uncongestion
- f2fs: Demote GC thread to idle scheduler class
- f2fs: set ioprio of GC kthread to idle
- mm: vmstat: use power efficient workingqueues


- optional powerhint magisk module to possibly save a little bit of battery on screen off scenarios like music playback.



Download:


Instructions can be found in the OP! Please follow the instructions to avoid any issues.
Don´t forgot to restore the stock vendor_boot.img found in the factory image of the firmware you´re currently running if you flashed 1.0.0 vendor_boot.img in the past!
 

DanielF50

Senior Member
Jul 22, 2010
580
400
Hampshire, England
Google Pixel 6 Pro

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,441
23,040

Texan1

Senior Member
Dec 22, 2008
939
301
Australia
Google Pixel 7 Pro
Boot from fastbootd to fastboot/bootloader to flash dtbo.img, vendor_boot.img and boot.img:
Either select Reboot to bootloader option via buttons
or type:
Code:
fastboot reboot bootloader

Now in fastboot flash boot.img and dtbo.img
Commands:
Code:
fastboot flash dtbo dtbo.img
fastboot flash boot boot.img

4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit!

Hi mate, I'm assuming where it says in the instructions to flash vendor_boot.img that it is not required as the subsequent instructions just say to flash dtbo.img and boot.img?

(BTW, many thanks for the new kernel, love your work (y))
 

Exel

Senior Member
Dec 31, 2010
3,256
1,476
Southern California
Google Pixel 6 Pro
Followed the instructions to a T from OP and everything flashed perfectly.

Coming back from using an iPhone for a long time, so excited to be tweaking stuff again.

Thank you @Freak07!

Side note, if we don't care about the CleanSlate tweaks just better stability, faster updates and battery life, just don't install the app and all of those features should be disabled by default?
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,441
23,040
Hi mate, I'm assuming where it says in the instructions to flash vendor_boot.img that it is not required as the subsequent instructions just say to flash dtbo.img and boot.img?

(BTW, many thanks for the new kernel, love your work (y))
Thanks for the kind words.

Correct. Thanks for spotting it, already corrected!
what idle drain people getting on here?

I'm losing about 2-3% over 7-8 hours overnight. Basically similar to stock. :)
Signal strength, network quality, wifi, installed apps, background apps/processes have way bigger impact on that as kernel changes.
Followed the instructions to a T from OP and everything flashed perfectly.

Coming back from using an iPhone for a long time, so excited to be tweaking stuff again.

Thank you @Freak07!

Side note, if we don't care about the CleanSlate tweaks just better stability, faster updates and battery life, just don't install the app and all of those features should be disabled by default?
Great to hear it worked out well for you.
Yes, if you don't care about the CleanSlate features don't install the apps and they will be disabled.
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
6,174
7,673
Google Nexus 5
Huawei Nexus 6P
what idle drain people getting on here?
Screenshot_20211121-140322.png
 
do you only need the cleanslate app if you want the gesture controls?
will you add wakelock blocking?
You need clean slate app(s) for clean slate features.

Which does not effect stability. Maybe minimal increase in battery usage.

You don't get kernel updates quicker or a more smooth experience if you don't use, as someone else above implied.
 

Exel

Senior Member
Dec 31, 2010
3,256
1,476
Southern California
Google Pixel 6 Pro
You need clean slate app(s) for clean slate features.

Which does not effect stability. Maybe minimal increase in battery usage.

You don't get kernel updates quicker or a more smooth experience if you don't use, as someone else above implied.

That's not what I implied, I implied I use this kernel for a smoother experience and faster upstream updates rather than waiting on Google's monthly patches, not for gimmicky features (not that some people don't use them, they're just not for me.)

I didn't say that if you don't use CleanSlate features it would be smoother or be updated faster.
 
  • Like
Reactions: Texan1
That's not what I implied, I implied I use this kernel for a smoother experience and faster upstream updates rather than waiting on Google's monthly patches, not for gimmicky features (not that some people don't use them, they're just not for me.)

I didn't say that if you don't use CleanSlate features it would be smoother or be updated faster.
This is off topic. Using clean slate features wouldn't effect updates of anything.

Wrong to say otherwise in anyway.

You said "Side note, if we don't care about the CleanSlate tweaks just better stability, faster updates and battery life, just don't install the app and all of those features should be disabled by default?"
 

Exel

Senior Member
Dec 31, 2010
3,256
1,476
Southern California
Google Pixel 6 Pro
This is off topic. Using clean slate features wouldn't effect updates of anything.

Wrong to say otherwise in anyway.

You said "Side note, if we don't care about the CleanSlate tweaks just better stability, faster updates and battery life, just don't install the app and all of those features should be disabled by default?"

I never said it did, but agree to disagree -- it's easy to misinterpret posts, let's stay on topic here. :)

Day 1 of using this kernel and so far so good.
 
  • Like
Reactions: Texan1

Jhoopes517

Senior Member
Oct 10, 2010
357
88
Mobile, AL
OnePlus 9
Google Pixel 6
So, I attempted to flash version 1.3 on my Pixel 6 and keep getting bootloop in to bootloader.

Downloaded all 1.3 images from afh.

Grabbed Vendor boot from latest OTA on google's servers.

Started with
fastboot flash vendor_boot vendor_boot.img

then followed the rest of the instructions from the OP but no go. Tried wiping to confirm not issue with data and no go.

Any suggestions?
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,441
23,040
do you only need the cleanslate app if you want the gesture controls?
will you add wakelock blocking?
you need the cleanslate apps, if you want to control the cleanslate features.

wakelock blocking maybe, which wakelock(s) do you want to block?
The latest release has two wlan wakelocks already removed from the wifi driver, that I could attribute to a lot of wakeups.

You need clean slate app(s) for clean slate features.

Which does not effect stability. Maybe minimal increase in battery usage.

You don't get kernel updates quicker or a more smooth experience if you don't use, as someone else above implied.
CleanSlate config app does nothing, except modify a file that has the configuration. It doesn´t affect battery life in any way.
CleanSlate companion app takes less cpu share than enabling any of the battery monitors in EXKM or FKM. So it´s next to nothing.

Kernel support kcal?
no, not at this moment.
KCAL is implemented on drivers that are used on qualcomm based phones.
Answered previosuly here:

check the next posts too, another user found a few apps that made him happy and I mentioned CF-Lumen.
So, I attempted to flash version 1.3 on my Pixel 6 and keep getting bootloop in to bootloader.

Downloaded all 1.3 images from afh.

Grabbed Vendor boot from latest OTA on google's servers.

Started with
fastboot flash vendor_boot vendor_boot.img

then followed the rest of the instructions from the OP but no go. Tried wiping to confirm not issue with data and no go.

Any suggestions?
Were you rooted before attempting to flash this kernel? Did you already issue the vbmeta disable verity/verification command via fastboot?

your fastboot environment could be outdated.

always patch the boot.img via magisk on the device you´re flashing it on.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Hey everyone,

    2.2.0 is fine to flash on April stable firmware! :)

    I wish everyone a good day!
    2
    Just confirming that with stock kernel on April update, I still get wide variations in ping time to my router. So, it's not specific to the Kirirasura kernel.
    Same on my end. I could reproduce similar results on pixel 6,7 and 8 pro.
    There are next to no changes on the wifi driver on my kernel.
    Maybe it's just an "issue" in that specific scenario though and not while gaming or when ping matters more.
    2
    Thank you @majorfigjam and @Freak07 for your feedback.
    1
    Firs of all thank you for your kernel freak.

    I have a question, I'm encountering this weird issue. My ping fluctuates a lot.

    I noticed it when I tried pinging my router while I'm next to it. I tried 2.4ghz and 5ghz networks. Spikes are up to 80ms.
    I don't have this issue on my other devices.

    Can someone please ping their router and check if they have the same issue ? Thank you
    Yes, I have a a similar variation.

    Don't know if it's kernel related though. Would have to wait until next monthly update (next week) to check out with the stock kernel.
    1
    definitely it happens here after installing kirisakura kernel
    all fine on my end.
    the kernel has no impact on displaying this information.

    It´s related to play services, google services, google app and the launcher, location services etc.
    If you use mods/magisk modules that alter this in any way, that´s were this can break.

    The kernel would only break mobile data, wifi or similar, but for the entire system/all apps/services.
    1000002831.png
  • 127
    Kirisakura-Kernel for the Pixel 6/Pro

    Hello everyone,

    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 A14 kernel sources from Google, Kernel is made for stable Android 14
    - Linux-Stable-Upstream included to 5.10.209
    - Compiled with prebuilt Google clang 18.0.0
    - EEVDF scheduler patches
    - lockless slab shrinker
    - 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
    - improve preallocations from maple tree (affects especially android)
    - reduce necessity to rewalk the maple tree
    - Per VMA-locks in conjunction with Maple Tree RCU-Mode (improve app launch time, this feature in general benefits greatly from lazy rcu!)
    - further improve maple tree/per-vma locks introduced in an earlier release
    - make TEO-Cpuidle util-aware (improves latency, performance and decreases energy consumption for certain workloads, more information here)
    - introduce runnable boosting, wire it up with pixel_sched
    - 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 (currently disabled as Google remotely disables the prop)
    - 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
    - reduce overhead
    - improve performance and efficiency by properly wiring up pixel_sched with teo util awareness (thanks @ada12 for spotting this!)
    - update to cpuset/cgroup subsystem (speeds up camera launches, device unlocks etc as cpusets are switched on those conditions, patches reduce overhead in those conditions)
    - flashing the kernel will preserve root

    Various Optimizations:
    - update several drivers to use power efficient workingqueues (for example wlan driver)
    - kernfs: use buffer from the stack space
    - printk: use buffer from the stack space
    - kthread: use buffer from the stack space
    - bpf: avoid dynamic memory allocation for small value buffers
    - binder: Reserve caches for small, high-frequency memory allocations
    - kernfs: use kmem_cache pool for struct kernfs_open_node/file
    - cgroup: use kmem_cache pool for struct cgrp_cset_link
    - f2fs: reduce timeout for uncongestion
    - f2fs: Demote GC thread to idle scheduler class
    - f2fs: set ioprio of GC kthread to idle
    - mm: vmstat: use power efficient workingqueues
    Wakelock Blocker:
    - advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
    - please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info

    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.


    Changelog:
    Android 12.0.0

    1.0.0 Initial Release
    1.0.2 https://xdaforums.com/t/kernel-07-1...r-pixel-6-pro-aka-raven.4358435/post-85910621
    1.0.5 https://xdaforums.com/t/kernel-08-1...r-pixel-6-pro-aka-raven.4358435/post-85924419
    1.3.0 https://xdaforums.com/t/kernel-11-1...pixel-6-pro-aka-raviole.4358435/post-85976139
    1.4.0 https://xdaforums.com/t/kernel-15-1...pixel-6-pro-aka-raviole.4358435/post-86109665
    1.5.0 https://xdaforums.com/t/kernel-16-1...pixel-6-pro-aka-raviole.4358435/post-86259863
    1.7.0 https://xdaforums.com/t/kernel-15-0...pixel-6-pro-aka-raviole.4358435/post-86390563
    1.8.4 https://xdaforums.com/t/kernel-08-0...pixel-6-pro-aka-raviole.4358435/post-86541727

    Android 12.1.0 Stable (March feature drop and more recent)
    2.0.0 https://xdaforums.com/t/kernel-08-0...pixel-6-pro-aka-raviole.4358435/post-86617873
    2.0.1 https://xdaforums.com/t/kernel-22-0...pixel-6-pro-aka-raviole.4358435/post-86637233
    2.1.0 https://xdaforums.com/t/kernel-25-0...pixel-6-pro-aka-raviole.4358435/post-86695911
    2.3.0 https://xdaforums.com/t/kernel-28-0...pixel-6-pro-aka-raviole.4358435/post-86821331
    2.4.0 https://xdaforums.com/t/kernel-30-0...pixel-6-pro-aka-raviole.4358435/post-86834981

    Android 12.1.0 Stable (June feature drop and more recent)
    3.0.0 https://xdaforums.com/t/kernel-03-0...pixel-6-pro-aka-raviole.4358435/post-86992705
    3.0.1 https://xdaforums.com/t/kernel-07-0...pixel-6-pro-aka-raviole.4358435/post-86996237
    3.0.17 https://xdaforums.com/t/kernel-08-0...pixel-6-pro-aka-raviole.4358435/post-87127695

    Android 13.0.0 Stable (not QPR beta!)
    4.1.0 https://xdaforums.com/t/kernel-09-0...pixel-6-pro-aka-raviole.4358435/post-87290247
    4.1.6 https://xdaforums.com/t/kernel-16-0...pixel-6-pro-aka-raviole.4358435/post-87399635
    4.2.0 https://xdaforums.com/t/kernel-06-0...pixel-6-pro-aka-raviole.4358435/post-87524609
    4.3.0 https://xdaforums.com/t/kernel-04-1...pixel-6-pro-aka-raviole.4358435/post-87697425
    4.4.0 https://xdaforums.com/t/kernel-08-1...pixel-6-pro-aka-raviole.4358435/post-87823333
    4.4.1 https://xdaforums.com/t/kernel-06-1...pixel-6-pro-aka-raviole.4358435/post-87944879
    4.4.2 https://xdaforums.com/t/kernel-04-0...pixel-6-pro-aka-raviole.4358435/post-88118201
    Raviantha 1.0.0 https://xdaforums.com/t/kernel-09-0...pixel-6-pro-aka-raviole.4358435/post-88316223
    Raviantah 1.0.2 https://xdaforums.com/t/kernel-21-0...pixel-6-pro-aka-raviole.4358435/post-88399941
    Raviantah 1.1.0 https://xdaforums.com/t/kernel-11-0...pixel-6-pro-aka-raviole.4358435/post-88645115
    Raviantah 1.1.2 https://xdaforums.com/t/kernel-14-0...pixel-6-pro-aka-raviole.4358435/post-88719665
    Raviantah 1.1.3 https://xdaforums.com/t/kernel-06-0...pixel-6-pro-aka-raviole.4358435/post-88847787
    Raviantah 1.1.5 https://xdaforums.com/t/kernel-08-0...pixel-6-pro-aka-raviole.4358435/post-89041877

    Android 14.0.0 Stable (NOT QPR BETA)

    Raviantah 2.0.0 https://xdaforums.com/t/kernel-24-0...pixel-6-pro-aka-raviole.4358435/post-89087375
    Raviantah 2.0.2 https://xdaforums.com/t/kernel-07-1...pixel-6-pro-aka-raviole.4358435/post-89149241
    Raviantah 2.1.0 https://xdaforums.com/t/kernel-08-1...pixel-6-pro-aka-raviole.4358435/post-89205122
    Raviantah 2.2.0 https://xdaforums.com/t/kernel-07-1...pixel-6-pro-aka-raviole.4358435/post-89384479



    Android 12L QPR Beta - Deprecated

    Requirements

    - 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.

    Manual installation without relying on paid apps like fkm/exkm:
    Please have a look at the linked post.



    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!


    Source Code: https://github.com/freak07
    44
    Update to 4.1.0

    Hey guys and girls,

    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:
    Screenshot_20220816-083147.png
    Screenshot_20220816-083204.png

    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



    Download:


    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
    43
    Update to 4.2.0

    Hey guys and girls,

    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
    37
    Update to 1.8.4

    Hey guys and girls,


    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


    Download:


    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.
    37
    Update to 1.7.0

    Hey guys and girls,


    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


    Download:


    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.