Development [Kernel][11.06.2023][Android 13] Kirisakura 3.0.2_T for Asus Zenfone 8 aka "Sake"

[Freak07]

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:

https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/UL-I006D-ASUS-30.11.51.103-1.1.27-user.zip

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:

https://www.androidfilehost.com/?fid=7161016148664785281

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]

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]

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.

 

[badboys87]

is there a twrp for zen 8 ?

 

[HyperCriSiS]

Hi,

is there any chance this awesome kernel will work on custom Roms like Omni for example?

Regards,
Hyper

 

[HyperCriSiS]

is there a twrp for zen 8 ?

Development is ongoing:

GitHub - CaptainThrowback/android_device_asus_I006D: TWRP device tree for ASUS ZenFone 8 (a.k.a. "sake", a.k.a. ZS590KS)

TWRP device tree for ASUS ZenFone 8 (a.k.a. "sake", a.k.a. ZS590KS) - CaptainThrowback/android_device_asus_I006D

github.com

 

[saferisk]

Hi folks, this is super exciting to see. Just wondering if we could have VOLTE and VOWIFI enabled by default?

 

[dron39]

Hi

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]

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]

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]

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.

 

[Freak07]

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]

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:

https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/UL-I006D-ASUS-30.11.51.115-1.1.28-user.zip

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:

https://www.androidfilehost.com/?w=files&flid=326388

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]

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.

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]

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]

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]

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]

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]

Trying to compile because I'll want modules.

errors at this

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

Trying to compile because I'll want modules.

errors at this

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