• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Development [Kernel][26.11.2021][Android 11] Kirisakura 1.7.9 for Asus Zenfone 8 aka "Sake"

Search This thread

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,135
16,460
Update to 1.3.1

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.11.51.103. 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.MR0.5-30.11.51.103 source code
- Linux-Stable Upstream to 5.4.139
- bump clang to latest prebuilt clang by google, 13.0.1
- Merge CAF (QCOM) upstream
- implement async probing to reduce time to first boot stage by a small margin
- fix where the device would crash during suspend when usb c headphones stay plugged in after media playback
- remove some qcom debugging from config we won´t need
- other improvements please take a look at 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
 

Fy00zh3n

New member
Aug 14, 2021
1
0
Awesome to see someone instantly jump on this phones development.

Thank you for that. As a PC modder Asus has long been the leader when it comes to quality and bleeding edge. This phone is a great mix (SD 888) and and decent screen size to please most, 3.5mm connect etc.

Hopefully Zen phone 9 will include a big brother addition (X, Pro? ) With larger screen and perhaps cam upgrade. That would really put a dent in competition. For the price this phone rocks and puts Asus firmly on the map (ROG is a little overboard for majority I believe but staying true to gamers is also what I would expect from Asus)
 

andelf_x

New member
May 28, 2021
3
2
Awesome to see someone instantly jump on this phones development.

Thank you for that. As a PC modder Asus has long been the leader when it comes to quality and bleeding edge. This phone is a great mix (SD 888) and and decent screen size to please most, 3.5mm connect etc.

Hopefully Zen phone 9 will include a big brother addition (X, Pro? ) With larger screen and perhaps cam upgrade. That would really put a dent in competition. For the price this phone rocks and puts Asus firmly on the map (ROG is a little overboard for majority I believe but staying true to gamers is also what I would expect from Asus)
I'm pretty sure Asus tried to separate themselves from the rest of the market by choosing a smaller form-factor - which is why I bought it (and the price/performance factor :) ). If many people end up buying this (like we did), if be surprised if they made a bigger screened phone.
 

HyperCriSiS

Senior Member
Nov 23, 2010
390
80
Samsung Galaxy S7
ASUS ZenFone 8
  • Like
Reactions: DerSteppo

saferisk

Member
Jun 26, 2008
16
3
Hi folks, this is super exciting to see. Just wondering if we could have VOLTE and VOWIFI enabled by default?
 

dron39

Senior Member
Sep 20, 2009
659
92
Why do you need it? If your cell phone provider do not support ZF8 then you will get nothing.
By the way author has different topic where he clearly explain how to enable such switches in settings. But w/o support from provider you won't get such features in real. Only switches will be enabled :)
 

dron39

Senior Member
Sep 20, 2009
659
92
Freak07
Hi, I'm on .103 FW.
I had reboot or crash when phone was just lying on the table near me in standby mode (with disply switched off).
I have Kirasakura v1.3.1 kernel installed. Straight after reboot I opened LogCat and exported logs.
Do you need them to check if it's kernel-related ?
If yes please pm with instruction how can i send it to oyu, because as far as I understand it could consist some private data or some s/n and etc.
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,135
16,460
Freak07
Hi, I'm on .103 FW.
I had reboot or crash when phone was just lying on the table near me in standby mode (with disply switched off).
I have Kirasakura v1.3.1 kernel installed. Straight after reboot I opened LogCat and exported logs.
Do you need them to check if it's kernel-related ?
If yes please pm with instruction how can i send it to oyu, because as far as I understand it could consist some private data or some s/n and etc.
logcat is not useful for this situation. :)
you can navigate to asdf/ASDF and see if one of those folders in there match the time you had the crash. it´s some part of asus logging and sometimes contains something useful.
You can share it via pm if you want to :)

usually in this situation I´d ask you for a ramoops, which can be found in sys/fs/pstore, it would show the last few minutes of the kernel log of the previous session. Unfortunately I haven´t found a way to make pstore/ramoops work on the zenfone 8.
 

dron39

Senior Member
Sep 20, 2009
659
92
logcat is not useful for this situation. :)
you can navigate to asdf/ASDF and see if one of those folders in there match the time you had the crash. it´s some part of asus logging and sometimes contains something useful.
You can share it via pm if you want to :)

usually in this situation I´d ask you for a ramoops, which can be found in sys/fs/pstore, it would show the last few minutes of the kernel log of the previous session. Unfortunately I haven´t found a way to make pstore/ramoops work on the zenfone 8.
Yeah, I definitely would like to share it with you. Please check pm for asdf. Hope it helps.

By the way I confused catlog with logcat. lol. Just want to clarify I took logs with Logcat reader if it is change something :)

I also remember that on Samsung I could take logs with dmesg or some other commands in terminal. I do not remember exactly how, but i did it on my old S8+ few years ago.
Or this asdf is the only proper way at the moment?

By the way new FW .115 is out (it's present on ASUS support page) and I hope sources will be released quckly as always. ;)
 
Last edited:

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,135
16,460
Yeah, I definitely would like to share it with you. Please check pm for asdf. Hope it helps.

By the way I confused catlog with logcat. lol. Just want to clarify I took logs with Logcat reader if it is change something :)

I also remember that on Samsung I could take logs with dmesg or some other commands in terminal. I do not remember exactly how, but i did it on my old S8+ few years ago.
Or this asdf is the only proper way at the moment?

By the way new FW .115 is out (it's present on ASUS support page) and I hope sources will be released quckly as always. ;)
those apps all do the same. they gather logcat and dmesg. both just show logs from the currently running session.
so all logs that lead to the reboot on the session where your phone crashed are gone.

pstore stores the kernel log from the last session just before your phone crashed after the reboot. unfortunately I haven´t found a way to make this work on the zf8 so far.

if there´s a kernel issue, we need to find out how to reproduce it and take a dmesg in the exact moment the phone crashes, which can be quite difficult.

I haven´t had a crash so far and I use the phone on a daily basis so there´s nothing I can do.

the asdf files you sent me also didn´t help. no logs for that date were in it. but that´s not your fault, asdf just doesn´t work well for me. maybe me or somebody else gets pstore working in the future, then I can tell for sure if it´s a kernel panic or not.
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,135
16,460
Update to 1.4.7

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.11.51.115. 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.MR0.53-30.11.51.115 source code
- Linux-Stable Upstream to 5.4.144
- Merge CAF (QCOM) upstream
- adjust batterysaver levels accessible via CleanSlate config app to match the PNP-Tuner magisk module
- disable per cgroup pressure tracking to reduce overhead
- improve gpu driver
- improve cpufreq driver (optimizations from pixel kernel)
- update wifi driver with latest sources from qcom
- update audio driver with latest sources from qcom
- improve eventpoll logging to get a more accurate reading on timerfd wakelocks
- use rt_mutex for binder (sony xperia 1 III kernel)
- pull in some scheduler changes from sony, mainly improving walt functionality (xperia 1 III kernel)




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

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,135
16,460
here´s an example on how to combine the battery saver function accessible via CleanSlate config app (check the cleanslate kernel thread for it), with the recently released PNP-Tuner magisk module.

Set battery saver level to 1 and enable touch limiting like in the following screenshot.
Screenshot_20210904-081431931.jpg


Make sure you´re running the PnP- Tuner magisk module and set the default system-mode to dynamic.

The CleanSlate Battery Saver will limit the phone to hard limits of 1,7ghz/2,1ghz/2,496GHZ for Little Cluster/Big Cluster/ Prime Core. No matter what happens this will be the limits, even during scenarios where the powerhal boosts the phone, so app launches for example.
When no interaction is happening, for example during watching videos, navigation, reading stuff in the browser the phone will not go over 1612/1766/2035 MHZ due to the limits defined in dynamic mode.


Just an example that works good for my personal usage.
 

badboys87

Member
Aug 21, 2021
10
0
ASUS ZenFone 8
here´s an example on how to combine the battery saver function accessible via CleanSlate config app (check the cleanslate kernel thread for it), with the recently released PNP-Tuner magisk module.

Set battery saver level to 1 and enable touch limiting like in the following screenshot.
View attachment 5401359

Make sure you´re running the PnP- Tuner magisk module and set the default system-mode to dynamic.

The CleanSlate Battery Saver will limit the phone to hard limits of 1,7ghz/2,1ghz/2,496GHZ for Little Cluster/Big Cluster/ Prime Core. No matter what happens this will be the limits, even during scenarios where the powerhal boosts the phone, so app launches for example.
When no interaction is happening, for example during watching videos, navigation, reading stuff in the browser the phone will not go over 1612/1766/2035 MHZ due to the limits defined in dynamic mode.


Just an example that works good for my personal usage.
what rom are you using?
 

SoulMachina

Member
Nov 25, 2015
46
21
ASUS ZenFone 8
here´s an example on how to combine the battery saver function accessible via CleanSlate config app (check the cleanslate kernel thread for it), with the recently released PNP-Tuner magisk module.

Set battery saver level to 1 and enable touch limiting like in the following screenshot.
View attachment 5401359

Make sure you´re running the PnP- Tuner magisk module and set the default system-mode to dynamic.

The CleanSlate Battery Saver will limit the phone to hard limits of 1,7ghz/2,1ghz/2,496GHZ for Little Cluster/Big Cluster/ Prime Core. No matter what happens this will be the limits, even during scenarios where the powerhal boosts the phone, so app launches for example.
When no interaction is happening, for example during watching videos, navigation, reading stuff in the browser the phone will not go over 1612/1766/2035 MHZ due to the limits defined in dynamic mode.


Just an example that works good for my personal usage.

Awesome! Gonna try them both and let you know how it goes.

Kudos!
 

ryshd296

Senior Member
Mar 15, 2014
121
14
oita
ASUS ZenFone 8
I came back after a long time.
Please tell me everyone.
1. Unlock boot loader with official unlock app
2.fastboot boot twrp3.5.2_11.img
3.flash this kernel
4.reboot

*non root this kernel→non root?
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,135
16,460
I came back after a long time.
Please tell me everyone.
1. Unlock boot loader with official unlock app
2.fastboot boot twrp3.5.2_11.img
3.flash this kernel
4.reboot

*non root this kernel→non root?
requirements and instructions are in the first post :)
 

zlice0555

Member
Aug 6, 2021
9
0
Trying to compile because I'll want modules.

errors at this

Code:
../techpack/audio/soc/pinctrl-wcd.c:19:10: fatal error: 'pinctrl-utils.h' file not found

#include "pinctrl-utils.h"
         ^~~~~~~~~~~~~~~~~

1 error generated.
make[4]: *** [../scripts/Makefile.build:288: techpack/audio/soc/pinctrl-wcd.o] Error 1
make[3]: *** [../scripts/Makefile.build:558: techpack/audio/soc] Error 2

But that header is in the same directory it seems. Have you seen this? Checked out branch master_caf_release_9_2

Also, I think I got the right toolchains from google, but where did you get "DU_Tools/dtc-aosp" from ? Assume dtc helps make a compatible img iirc
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
5,135
16,460
Trying to compile because I'll want modules.

errors at this

Code:
../techpack/audio/soc/pinctrl-wcd.c:19:10: fatal error: 'pinctrl-utils.h' file not found

#include "pinctrl-utils.h"
         ^~~~~~~~~~~~~~~~~

1 error generated.
make[4]: *** [../scripts/Makefile.build:288: techpack/audio/soc/pinctrl-wcd.o] Error 1
make[3]: *** [../scripts/Makefile.build:558: techpack/audio/soc] Error 2

But that header is in the same directory it seems. Have you seen this? Checked out branch master_caf_release_9_2

Also, I think I got the right toolchains from google, but where did you get "DU_Tools/dtc-aosp" from ? Assume dtc helps make a compatible img iirc
No I don't get that error you're seeing.

dtc-aosp is dtc compiled from the aosp source.
 

Attachments

  • dtc-aosp.zip
    51.9 KB · Views: 6

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Update to 1.7.8

    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.56. Make sure to update to the latest firmware before flashing the kernel to have no compatibility issues.

    Asus brought the change I did in 1.7.5 to the ufs driver, which improves deep sleep behaviour/reduces suspend drain a bit, into the stock kernel. :cowboy:

    The link to the firmware can be found here:


    More changes in the Changelog below:


    Changelog:
    - Import zenfone8_zs590ks.MR1-30.12.112.56 source code
    - Linux-Stable Upstream to 5.4.161


    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
    3
    Update to 1.7.9

    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.62. 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.62 source code


    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
    2
    no changes in the .46 source code, feel free to flash away if you haven´t already done so.
    1
    The kernel is updated for the latest firmware:
    30.12.112.66
    .56. You are living in future)))

    Asus brought the change I did in 1.7.5 to the ufs driver, which improves deep sleep behaviour/reduces suspend drain a bit, into the stock kernel.
    Haha. It seems after next few updates of Kirisakura we will have stable stock firmware :)
  • 18
    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 11 and intended to be used on the latest Asus Stock-Firmware (currently 30.12.112.62)
    - compiled with Clang 13.0.1 and built with -O3 speed optimizations
    - Linux-Stable-Upstream included to 5.4.161
    - 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
    - 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)

    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

    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
    6
    Update to 1.0.3

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

    md5sum: 0f30d5e043f4a675e7db3250d5218125


    More changes in the Changelog below:


    Changelog:
    - Import zenfone8_zs590ks.MR0.4-30.11.51.67 source code
    - Linux-Stable Upstream to 5.4.128
    - bump clang to latest prebuilt clang by google (12.0.7)




    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
    5
    Update to 1.7.8

    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.56. Make sure to update to the latest firmware before flashing the kernel to have no compatibility issues.

    Asus brought the change I did in 1.7.5 to the ufs driver, which improves deep sleep behaviour/reduces suspend drain a bit, into the stock kernel. :cowboy:

    The link to the firmware can be found here:


    More changes in the Changelog below:


    Changelog:
    - Import zenfone8_zs590ks.MR1-30.12.112.56 source code
    - Linux-Stable Upstream to 5.4.161


    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
    5
    Update to 1.5.1

    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.22. 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.22 source code
    - Linux-Stable Upstream to 5.4.148
    - Merge CAF (QCOM) upstream up to tag LA.UM.9.14.r1-18300-LAHAINA.0
    - GPU driver improvements
    - updates from kernel common for several subsystems


    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