Development [Kernel][14.09.2022][Android 12] Kirisakura 2.0.10_S for Asus Zenfone 8 aka "Sake"

Search This thread

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,735
19,114
Update to 2.0.8

Hey guys and girls,


Here´s the next update.
Source was updated for 31.1010.0411.113.
Details in the changelog below.

The link to the latest firmware can be found following this link.


More changes in the Changelog below:


Changelog:
- Import kernel source from 31.1010.0411.113
- Linux-Stable upstream bumped to 5.4.209
- merge latest CAF-Upstream
- import SSG IO scheduler from samsung galaxy s22 and set as default option
  1. -> asus switched to mq-deadline, which doesn´t work that well under load
  2. -> default google/qcom mq-bfq is a pretty gigantic driver
  3. -> ssg was developed by samsung to fit android needs, be compact should reduce overhead compared to the other two options and reduce cpu cycles
- implement display change, that might lead to reduced power consumption
- use prebuilt clang 14.0.7
- update f2fs fsck spoof
- other improvements and tweaks please check github


Download:



Instructions can be found in the OP!
But look at this post too :)

Have fun, enjoy the kernel and your phone.

Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
 
Last edited:

emc02

Senior Member
Jul 4, 2010
238
70
Vienna
Tried the latest version (2.0.8) and it boots always to fastboot...
My System:
LOS 19.1
Magisk 25.2
LSPosed

First tried to Flash with twrp-3.6.1_11-0-I006D then tried with los-recovery and both resulted in boot to fastboot.

I've flashed LOS new on 31.7. after updating ASUS-ROM to latest level.

Can this be related to the "old" ASUS firmware? How can I update ASUS firmware while using LOS?

edit: 2.0.2 not working...
 

Attachments

  • console-ramoops-0.zip
    71.5 KB · Views: 4
Last edited:

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,735
19,114
Tried the latest version (2.0.8) and it boots always to fastboot...
My System:
LOS 19.1
Magisk 25.2
LSPosed

First tried to Flash with twrp-3.6.1_11-0-I006D then tried with los-recovery and both resulted in boot to fastboot.

I've flashed LOS new on 31.7. after updating ASUS-ROM to latest level.

Can this be related to the "old" ASUS firmware? How can I update ASUS firmware while using LOS?

edit: 2.0.2 not working...
Try magisk 24.3 and see if that gets rid of this issue.
 
  • Like
Reactions: emc02

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,735
19,114
I now tried without Magisk => same result
Magisk 24.3 cannot be installed on my phone because of an error during installing the apk (tried 24.2 too)
I think you can't install older magisk APK over more recent. Need to uninstall and reinstall magisk completely.

The problem is verity related as far as I'm aware. The way magisk handles that has changed. That's why I think it will work with older magisk. Older magisk made verity not trip by accident as fstab was patched, this was removed in every magisk more recent than 24.3.

I'm not using custom roms so I can't look into it myself.

The options you have. Disable verity/verification manually (this will wipe the device) via fastboot or try to use older magisk.

Make also sure to flash the version for custom roms a few pages back. 2.0.8 won't work properly on los.

The ramoops you shared isn't from my kernel, but from the los kernel. It's a bit corrupted, but the build date of the kernel it logged is August 26th and clang version is 12.x.y, which can't be mine.
 
  • Like
Reactions: emc02

emc02

Senior Member
Jul 4, 2010
238
70
Vienna
I think you can't install older magisk APK over more recent. Need to uninstall and reinstall magisk completely.

The problem is verity related as far as I'm aware. The way magisk handles that has changed. That's why I think it will work with older magisk. Older magisk made verity not trip by accident as fstab was patched, this was removed in every magisk more recent than 24.3.

I'm not using custom roms so I can't look into it myself.

The options you have. Disable verity/verification manually (this will wipe the device) via fastboot or try to use older magisk.

Make also sure to flash the version for custom roms a few pages back. 2.0.8 won't work properly on los.

The ramoops you shared isn't from my kernel, but from the los kernel. It's a bit corrupted, but the build date of the kernel it logged is August 26th and clang version is 12.x.y, which can't be mine.
Thanks, completely uninstalling Magisk did the trick.
Unfortunately after installing your kernel (Kirisakura_Sake_S_2.0.1_cust.zip) I've got the message on boot, that there is a problem with the device and I should contact the vendor.
Because this is my daily-use and work-phone I don't want to risk to run into too big problems and reverted everything back. But thanks for your fast response and great work.
Is Overclocking and/or undervolting possible with you kernel?
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,735
19,114
Thanks, completely uninstalling Magisk did the trick.
Unfortunately after installing your kernel (Kirisakura_Sake_S_2.0.1_cust.zip) I've got the message on boot, that there is a problem with the device and I should contact the vendor.
Because this is my daily-use and work-phone I don't want to risk to run into too big problems and reverted everything back. But thanks for your fast response and great work.
Is Overclocking and/or undervolting possible with you kernel?
If it's just about that window you're worried, that's solely because my kernels defconfig is not the same as the stock LOS kernel.

On stock firmware i can circumvent this by spoofing the stock defconfig in my kernel during compile time. On custom roms i can't do this properly as some custom roms use modified kernels, and i don't have the time to build multiple versions of the kernel to spoof different defconfigs. The popup you're seeing is just "cosmetic".

No there's no overclock or undervolting.
 
  • Like
Reactions: emc02

Rokcy98

Member
Sep 25, 2018
48
42
Italy
ASUS ZenFone 8
Hi @Freak07, build 31.1010.0411.122 has been out for some days now, but it's source code hasn't been released yet. Do you know if Kirisakura 2.0.8 can be used on this latest build, or you can't say that without seeing it's source code?
Thanks
 
  • Like
Reactions: mkernitsky

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,735
19,114
Update to 2.0.10

Hey guys and girls,


Here´s the next update.
No changes kernel wise for firmware 31.1010.0411.122.

The link to the latest firmware can be found following this link.


More changes in the changelog below:


Changelog:
- Linux-Stable upstream bumped to 5.4.212
- merge latest CAF-Upstream
- other improvements and tweaks please check github


Download:



Instructions can be found in the OP!
But look at this post too :)

Have fun, enjoy the kernel and your phone.

Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
 
Last edited:

Rokcy98

Member
Sep 25, 2018
48
42
Italy
ASUS ZenFone 8
Update to 2.0.11

Hey guys and girls,


Here´s the next update.
No changes kernel wise for firmware 31.1010.0411.122.

The link to the latest firmware can be found following this link.


More changes in the changelog below:


Changelog:
- Linux-Stable upstream bumped to 5.4.212
- merge latest CAF-Upstream
- other improvements and tweaks please check github


Download:



Instructions can be found in the OP!
But look at this post too :)

Have fun, enjoy the kernel and your phone.

Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Thank you!
 
  • Like
Reactions: Freak07

skothiya

Senior Member
May 5, 2014
75
6
ASUS ZenFone 8
Update to 2.0.11

Hey guys and girls,


Here´s the next update.
No changes kernel wise for firmware 31.1010.0411.122.

The link to the latest firmware can be found following this link.


More changes in the changelog below:


Changelog:
- Linux-Stable upstream bumped to 5.4.212
- merge latest CAF-Upstream
- other improvements and tweaks please check github


Download:



Instructions can be found in the OP!
But look at this post too :)

Have fun, enjoy the kernel and your phone.

Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
@Freak07 Update to 2.0.10
 
  • Like
Reactions: Freak07

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Update to 2.0.10

    Hey guys and girls,


    Here´s the next update.
    No changes kernel wise for firmware 31.1010.0411.122.

    The link to the latest firmware can be found following this link.


    More changes in the changelog below:


    Changelog:
    - Linux-Stable upstream bumped to 5.4.212
    - merge latest CAF-Upstream
    - other improvements and tweaks please check github


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    1
    Tried the latest version (2.0.8) and it boots always to fastboot...
    My System:
    LOS 19.1
    Magisk 25.2
    LSPosed

    First tried to Flash with twrp-3.6.1_11-0-I006D then tried with los-recovery and both resulted in boot to fastboot.

    I've flashed LOS new on 31.7. after updating ASUS-ROM to latest level.

    Can this be related to the "old" ASUS firmware? How can I update ASUS firmware while using LOS?

    edit: 2.0.2 not working...
    Try magisk 24.3 and see if that gets rid of this issue.
    1
    I now tried without Magisk => same result
    Magisk 24.3 cannot be installed on my phone because of an error during installing the apk (tried 24.2 too)
    I think you can't install older magisk APK over more recent. Need to uninstall and reinstall magisk completely.

    The problem is verity related as far as I'm aware. The way magisk handles that has changed. That's why I think it will work with older magisk. Older magisk made verity not trip by accident as fstab was patched, this was removed in every magisk more recent than 24.3.

    I'm not using custom roms so I can't look into it myself.

    The options you have. Disable verity/verification manually (this will wipe the device) via fastboot or try to use older magisk.

    Make also sure to flash the version for custom roms a few pages back. 2.0.8 won't work properly on los.

    The ramoops you shared isn't from my kernel, but from the los kernel. It's a bit corrupted, but the build date of the kernel it logged is August 26th and clang version is 12.x.y, which can't be mine.
    1
    Thanks, completely uninstalling Magisk did the trick.
    Unfortunately after installing your kernel (Kirisakura_Sake_S_2.0.1_cust.zip) I've got the message on boot, that there is a problem with the device and I should contact the vendor.
    Because this is my daily-use and work-phone I don't want to risk to run into too big problems and reverted everything back. But thanks for your fast response and great work.
    Is Overclocking and/or undervolting possible with you kernel?
    If it's just about that window you're worried, that's solely because my kernels defconfig is not the same as the stock LOS kernel.

    On stock firmware i can circumvent this by spoofing the stock defconfig in my kernel during compile time. On custom roms i can't do this properly as some custom roms use modified kernels, and i don't have the time to build multiple versions of the kernel to spoof different defconfigs. The popup you're seeing is just "cosmetic".

    No there's no overclock or undervolting.
    1
    Hi @Freak07, build 31.1010.0411.122 has been out for some days now, but it's source code hasn't been released yet. Do you know if Kirisakura 2.0.8 can be used on this latest build, or you can't say that without seeing it's source code?
    Thanks
  • 20
    Kirisakura-Kernel for the Asus Zenfone 8

    Hello everyone,

    To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 8 aka Sake. The Zenfone line-up internal codenames are traditionally derived from alcoholic drinks. Two years ago the Zenfone 6 bore the title "Kirin". The Zenfone 7 was codenamed "Tequila".
    I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.

    Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
    If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
    However the kernel is built to keep battery life close to the same as you would experience the on stock kernel while being tuned to perform better in various UI related benchmarks. The same benches are used by google to verify and ensure UI smoothness on the Pixel devices. The scheduler is tuned to yield lower jitter and reduce jank frames.
    If that got your curious, I welcome you to continue reading if you´re still interested!


    This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.


    A very positive development. Google pushed for CFI and SCS to be enabled by default in the android-common kernel. In this years generation ( 5.4 linux kernel base/ SD 888 ) CFI and SCS are enabled by default. It was a lot of work to get these features working nicely on the kernel I did the years back. So it´s nice to see this is now there by default in everybody can profit from it.
    I put the explanations and links in hide tags here.

    Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features.
    The recently released Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
    If possible the latest Kirisakura-Kernel releases for various devices aim to include CFI in enforcing mode so users can benefit from this security features.

    Another security feature is Shadow Call Stack (SCS).
    SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
    ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
    If you´re interested here are a few good links:
    Google Security Blog explaining SCS.
    LLVM doc about SCS
    Android DOCs documenting SCS

    If reading about upstream in the paragraph above 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.
    Read more about the Release-Model following this link.
    This conversation on the LKML mailing list also shows the power of Linux-Stable and why it´s very beneficial to not just say it´s not worth and a potentiol source for bugs:
    Starting with the Initial Message , the following reply and a good summarizing statement.



    Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 888 that´s built into the different SKUs of the Zenfone 8.
    The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
    The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
    This kernel focuses amongst the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.

    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!


    Main Features:
    - Based on latest kernel sources from Asus for Android 12 and intended to be used on the latest Asus Stock-Firmware
    - compiled with Clang 14.0.7 and built with -O3 speed optimizations
    - Linux-Stable-Upstream included to 5.4.212
    - upstreamed CAF base for the Snapdragon 888 (qcoms internal codename "lahaina")
    - include important fixes/improvements from kernel/common
    - tune scheduler for improved jitter and less jank frames
    - reduce power consumption during deep sleep
    - remove logging while device is suspended
    - remove sleep debugging from Asus for release build
    - disable various debugging mechanisms for drivers which are not needed on a perf build (for example touchscreen, fingerprint reader, display, binder)
    - disable various debugging configs, that are not needed in a perf kernel build according to google.
    - disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
    - display tweaks to reduce power consumption on statically rendered images
    - disable unnecessary CPU errata for our specific SoC
    - disable per cgroup pressure tracking to reduce overhead
    - SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
    - free up RAM by removing reserved mem regions used only for debugging
    - implement LRNG (thanks @arter97, see arter kernel OP for more info )
    - Flashing the kernel will keep root!
    - Flashable via EXKM, FKM or TWRP (if available) on a rooted system!
    - Anykernel zip is based on the Anykernel3 release from @osm0sis


    EAS related features:
    - Implement dynamic WALT-Window size depending on current FPS, collecting information about CPU-Load to provide more precise information for the scheduler
    - EAS implementation patched up to latest CAF state
    - updates from kernel/common
    - scheduler updates from sd888/ 5.4 kernel
    - scheduler update from sony xperia 1 III kernel aiming to improve WALT

    CPU related features:
    - Power saving workingqueues enabled by default (toggleable in EXKM)
    - Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to use power efficient workingqueues. This compliments EAS in general
    - improvements to cpufreq/times/stats
    - vdso32 patches as found on Google Pixel devices (brief documentation here) (CAF 5.4 default, keep for documentation)
    - remove event debug logging
    - disable broken irq detection, disable debugmon
    - improve suspend/resume from audio driver (caf-upstream for audio-kernel)
    - cpuidle: wake only cpus for which qos has changed (this allows cores to keep idle states better)
    - disable debugging during sleep states as per qcom recommendation
    - remove RTB logging to reduce overhead
    - disable trace_printk as it shouldn´t be used on production/perf kernel builds
    - enable suspend_skip_sync to save power during suspend/resume
    - disable edac and coresight (following google on the pixel kernels)
    - disable jtagv8 debugging as recommended by qcom for perf builds to avoid potential power, performance and memory penalty
    - disable s2idle in favor of deep idle state -> improves deep sleep drain (google initially used 2idle for improved suspend/resume latency on pixel 3 and pixel 4, but disabled it on pixel 5. qcom followed suit for sd 888, but apparently didn´t see google reverting it on pixel 5. Other OEMs such as Xiaomi or OnePlus already disabled s2idle on their SD888 devices in favor of deep- read more about s2idle vs deep here)

    GPU related features:
    - GPU driver updated to latest CAF-State
    - gpu/kgsl improvements from pixel 4/pixel 5 kernel
    - add low_prio_worker thread for gpu driver (Improves performance when tearing down processes (eg, via LMK) and not blocking currently running UI from submitting work to the GPU

    File System related features:
    - upstream BFQ-MQ to latest state in linux-mainline and default to 128KB readahead
    - improve memory allocations in kernfs
    - ufs improvements from pixel 4/ pixel 5 kernel
    - improve GC as to not interfere while user interaction is happening and prevent possible jitter or latency spikes

    UI/UX/Usability related features from CleanSlate:
    - CleanSlate features made by @tbalden
    - Disclaimer: All CleanSlate features can be controlled via the free companion and config app found on CleanSlate thread here on the Zenfone 8 Forums on XDA. Please consider buying the premium versions if you enjoy using the CleanSlate features, to give a little something back to @tbalden.

    Network related features:
    - Wireguard Support (Details)
    - advanced TCP algorithms enabled
    - use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
    - includes new bbr
    - improved networking drivers from caf-upstream (especially wifi)
    - remove unnecessary wakelock from WLAN driver to reduce thousands of very short wakeups during a 7 hour deep sleep period
    - improved bluetooth performance (¹, ²)
    - Enable support for TTL spoofing

    Memory related features:
    - Speculative Page Faults left enabled (1. 2) (CAF 5.4 default, keep for documentation)
    - Fix various memory leaks in different subsystems
    - improved mm with patches from mainline
    - patches from kernel/common
    - improve memory allocations in various subsystems, video encode/decode, kernfs, cgroup
    - Backport to enable CONFIG_HAVE_MOVE_PMD (see here) , thanks @arter97
    - Backport to enable CONFIG_HAVE_MOVE_PUD (commit here) , thanks @arter97
    - free more RAM by removing unused reserved memory regions
    - mm: Micro-optimize PID map reads for arm64 (improves game performance, especially unity based games such as genshin impact)
    - MGLRU added (info here and here

    Security related features:
    - Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) (CAF 5.4 default, keep for documentation)
    - Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO (CAF 5.4 default, keep for documentation)
    - Shadow Call Stack (SCS) Security-Feature ( 5.4 default, keep for documentation)
    - enable init_on_alloc for even more security, more information can be found in the commit message (CAF 5.4 default, keep for documentation)


    Misc Features:

    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
    - blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!

    Other features:
    - clean up asus drivers and fix a few warnings in kernel log
    - disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
    - fix several coding issues detected by newer Clang-Toolchains
    - enlarge dmesg size to ease debugging


    Flashing Guide, Download and Changelog

    Requirements:
    - unlocked Bootloader (this will void warranty and kill future OTA updates on all asus phones at the moment)
    - USB-Debugging in developer options enabled
    - latest adb and fastboot binaries
    - working adb and fastboot environment
    - magisk root
    - a backup of stock boot.img, vendor_boot.img and dtbo.img so you can go back to stock conditions (simplest way is TWRP or to extract from stock firmware)

    How to flash the Kernel:
    1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Asus Stock-Firmware. When the Zenfone 8 receives an OTA update it takes Asus a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
    Always make sure to run the firmware the kernel is built for!
    If you feel adventurous and try in advance, make sure you have a backup ready!

    2. Flash the kernel.zip via latest TWRP (if available), EXKM or FKM app and do a full reboot.

    3. Reboot and profit.


    DOWNLOAD:
    Download is located always in this folder:

    Important: Read after Download
    Please take a look at the second post after flashing the kernel!

    Changelog:
    Android 11

    1.0.0 Initial Release
    1.0.3 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85230887
    1.1.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85369421
    1.3.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85471991
    1.4.7 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85580815
    1.5.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85708459
    1.7.5 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85845707
    1.7.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85845707
    1.7.9 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86004361

    Android 12
    1.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86200913
    1.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86219239
    1.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86221081
    1.0.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86546997

    2.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86856077
    2.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87005047
    2.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87053951
    2.0.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87244107
    2.0.10 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87432111


    Donations:
    Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea :)
    If you like my work: http://paypal.me/freak07

    Credits:
    Asus for the development device, giving me the opportunity to create this project!
    @osm0sis for all his work, including the ak3 installer!
    @tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
    @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!


    Source Code: https://github.com/freak07/Kirisakura_SAKE_Zenfone_8
    9
    Update to 1.7.5

    Hey guys and girls,


    I hope everyone is having a good day or starting into one. Here´s the next update.
    The kernel is updated for the latest firmware:
    30.12.112.36. Make sure to update to the latest firmware before flashing the kernel to have no compatibility issues.

    The link to the firmware can be found here:


    More changes in the Changelog below:


    Changelog:
    - Import zenfone8_zs590ks.MR1-30.12.112.36 source code
    - Linux-Stable Upstream to 5.4.155
    - Merge CAF (QCOM) upstream
    - remove logging while device is suspended
    - improvements to deep sleep power consumption (ufs driver, auto hibernate)
    - reduce auto suspend delay in various other drivers
    - improvements on various subsystem like memory management, bluetooth, display, gpu etc
    - implement LRNG (thanks @arter97, see arter kernel OP for more info )
    - updates from kernel common for several subsystems
    - updated ak3 zip, thanks to @osm0sis


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    8
    Update to 1.0.8

    Hey guys and girls,


    Alright so here´s the next update. The asus source for the new updates didn´t contain anything that we didn´t already have by merging CAF and linux-stable upstream.

    However it was time for an update.

    After flashing the kernel.zip there will be a magisk module in magisk manager called AK3 Helper Module. Do not delete it.

    The link to the latest firmware can be found here:
    [/URL]


    More changes in the Changelog below:


    Changelog:
    - Linux-Stable upstream bumped to 5.4.182
    - use prebuilt clang 14.0.2
    - CAF-Upstream
    - wifi driver updated with caf-upstream
    - update f2fs fsck spoof


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    8
    Update to 2.0.8

    Hey guys and girls,


    Here´s the next update.
    Source was updated for 31.1010.0411.113.
    Details in the changelog below.

    The link to the latest firmware can be found following this link.


    More changes in the Changelog below:


    Changelog:
    - Import kernel source from 31.1010.0411.113
    - Linux-Stable upstream bumped to 5.4.209
    - merge latest CAF-Upstream
    - import SSG IO scheduler from samsung galaxy s22 and set as default option
    1. -> asus switched to mq-deadline, which doesn´t work that well under load
    2. -> default google/qcom mq-bfq is a pretty gigantic driver
    3. -> ssg was developed by samsung to fit android needs, be compact should reduce overhead compared to the other two options and reduce cpu cycles
    - implement display change, that might lead to reduced power consumption
    - use prebuilt clang 14.0.7
    - update f2fs fsck spoof
    - other improvements and tweaks please check github


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    7
    Freak07,
    Hi,
    Will you update your kernel for current firmware (.43) ?
    Thanks!

    When I find time. They bumped the CAF-Base, but my kernel is still ahead.

    This creates a lot of conflicts during merging. Either I need to start from scratch again or check in detail how much work merging and fixing all the conflicts will be.