Development [Kernel][12.04.2023][Android 13] Kirisakura 3.0.1 for Sony Xperia 1 III aka "Sagami"

[steveglowplunk]

Hi all
I understand I'm not supposed to expect this kernel to save much battery magically, but how much difference does the "CPU-Frequency Limiting" feature make? I only use my phone for lightweight activities like web browsing or listening to music so I'd like to limit the CPU speed to reduce battery usage as much as possible. Without any modifications, this phone's battery usage is so ridiculously high that it's almost unusable.

 

[Freak07]

Hi all
I understand I'm not supposed to expect this kernel to save much battery magically, but how much difference does the "CPU-Frequency Limiting" feature make? I only use my phone for lightweight activities like web browsing or listening to music so I'd like to limit the CPU speed to reduce battery usage as much as possible. Without any modifications, this phone's battery usage is so ridiculously high that it's almost unusable.

Nobody will be able to tell you exactly, because everyones usage is unique.

CPU is only one part of the SoC and the SoC is only one component that draws power.
The display in general, display brightness, refresh rate, mobile data vs wifi, signal strength all of this draws power.
Even though sony doesn´t run the display all the time at 4K resolution, the display draws a lot.


If your phone is bootloader unlocked already why not give it a try. You can easily revert back to stock.
If you consider to unlock the bootloader to try, you have to decide yourself, no OTA, no widevine L1 etc vs the possibilities an unlocked bootloader opens up.

 

[steveglowplunk]

Nobody will be able to tell you exactly, because everyones usage is unique.

CPU is only one part of the SoC and the SoC is only one component that draws power.
The display in general, display brightness, refresh rate, mobile data vs wifi, signal strength all of this draws power.
Even though sony doesn´t run the display all the time at 4K resolution, the display draws a lot.


If your phone is bootloader unlocked already why not give it a try. You can easily revert back to stock.
If you consider to unlock the bootloader to try, you have to decide yourself, no OTA, no widevine L1 etc vs the possibilities an unlocked bootloader opens up.

I do intend to unlock the bootloader some time later, despite those drawbacks you mentioned. In fact a major reason I purchased this phone is that I saw it has LineageOS, TWRP and this custom kernel, which make this phone highly customisable. I did see how the reviews say the phone's battery life is subpar, but I did not expect it to be this bad now that I do own the phone.

 

[derin38]

@Freak07 Thanks a lot, 3.0.0 works great. But I think I'm missing something, is the Wireguard module not included in 3.0.0? FKM doesn't state it and the wireguard app won't let me switch over.

 

[Freak07]

@Freak07 Thanks a lot, 3.0.0 works great. But I think I'm missing something, is the Wireguard module not included in 3.0.0? FKM doesn't state it and the wireguard app won't let me switch over.

Maybe I forgot to include it in the build

 

[Freak07]

Update to 3.0.1

Hey guys and girls,

Seems I forgot to include wireguard kernel side implementation in the previous build. Thanks to @derin38 for spotting.
This release adds wireguard support.

More changes can be found in the Changelog below:


Changelog:
- Include wireguard kernel side implementation


Download:
Attached to this post as AFH is currently not working correctly.



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

 

[derin38]

Haha thanks! This must be the quickest bug fix turn-around ever

 

[Bumble17]

Any chance to implement the Adreno-idler GPU governor? Or any other governors for that matter. I know you said this kernel isn't designed for improving battery life (at least significantly), but battery life has been the biggest annoyance with this phone for me so any extra help is hugely appreciated. Thanks.

 

[Freak07]

Any chance to implement the Adreno-idler GPU governor? Or any other governors for that matter. I know you said this kernel isn't designed for improving battery life (at least significantly), but battery life has been the biggest annoyance with this phone for me so any extra help is hugely appreciated. Thanks.

that´s deprecated for years, but good idea. I completely understand the motivation.

Mabye sony should have waited for sd8 + gen1.

check post #3 and try to limit max cpufreq. even level 1 may result in a noticeable impact, based on usage.

 

[Bumble17]

that´s deprecated for years, but good idea. I completely understand the motivation.

Mabye sony should have waited for sd8 + gen1.

check post #3 and try to limit max cpufreq. even level 1 may result in a noticeable impact, based on usage.

I see, didn't know my bad. Yeah I've already done that, I've been having pretty damn good results with level 2. Guess I'll stick with what I have right now. Thanks for your time and quick reply.

 

[Freak07]

I see, didn't know my bad. Yeah I've already done that, I've been having pretty damn good results with level 2. Guess I'll stick with what I have right now. Thanks for your time and quick reply.

I might be looking into reducing boosts via the powerhal. But that goes on the cost of performance. Since qcom and therefore sony is pretty much done updating those platform changes, might be possible doing it without the need to constantly maintain for firmware changes.
Might make a separate magisk module out of this then. I just need to find a bit of time

 

[DrDrag0n]

Feature Documentation:
Here´s a brief documentation about some of the features included in the kernel that can be changed as the user desires.
They can be accessed via either terminal, scripts or for example EXKM manager ( tools -> user settings).

CPU-Frequency Limiting:
Another option is CPU-Freq Limiting. You can now limit the CPU frequency to a few different levels with a sysfs interface. Original implementation is from @tbalden, I only changed it to be accessible via traditional root methods.
Main Switch:
sys/module/cpufreq/parameters/batterysaver
Set this option to "1" to enable the feature

Max-Frequency Selection (Input boosts, such as scrolling boost or app launching boosts will still apply, if touch boost restriction is not set to 1)
sys/module/cpufreq/parameters/batterysaver_level
Set this to "1" to restrict the max CPU-Freqs to 1,7GHZ/2,1GHZ/2,49GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "2" to restrict the max CPU-Freqs to 1,6GHZ/1,7GHZ/2,0GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "3" to restrict the max CPU-Freqs to 1,49GHZ/1,4GHZ/1,6GHZ (Little Cluster/Big Cluster/Prime Core)

Touch-Boost Restriction
sys/module/cpufreq/parameters/batterysaver_touch limiting
Set this to "1" to restrict the powerhal from boosting over the limit defined in batterysaver_level
Set this to "0" to allow the powerhal to boost above the values defined in batterysaver_level, but only during interaction with the Phone!

Screenshots:
View attachment 5309899View attachment 5309901View attachment 5309903


This is for example very useful during gaming to prevent additional heat, if not the highest performance from the CPU is required. Check if the game is running fine on level 1 or 2, and you´ll notice much less heat. Powerdraw will be reduced as well.
Another very useful trick while doing video calls or long extended navigation sessions with google maps to preserve battery or keep the phone from heating. Especially during summer if the ambient temperatures are high.
This is a very easy way to preserve battery or reduce heat without toggling the battery save mode in settings as that restricts background data usage, which can lead to delayed notifications.

Every time i change the files they revert when i reboot

 

[Freak07]

Every time i change the files they revert when i reboot

yes, that´s expected behaviour.

if you use exkm like on the screenshot, you can make it persist across reboots by tapping on the circular arrow.
if you´re doing it manually, you need to use a script to set it automatically during boot.

 

[DrDrag0n]

yes, that´s expected behaviour.

if you use exkm like on the screenshot, you can make it persist across reboots by tapping on the circular arrow.
if you´re doing it manually, you need to use a script to set it automatically during boot.

Thank you for the recommendation
its been sticking after boot!!
another addition ive made is using konabess to massively under volt each gpu stepping. has reduced heat a lot

 

[STTec CEO]

Any possible for add ZRAM_WRITEBACK support？This is the mainstream trend and even Pixel has supported it, but Sony has not caught up yet.

 

[Freak07]

Any possible for add ZRAM_WRITEBACK support？This is the mainstream trend and even Pixel has supported it, but Sony has not caught up yet.

It´s not Sony that´s disabling this, but rather QCOM iirc.

Just enabling the config kernel side will also do nothing. The rest of the firmware also needs to support it, fstab, rc files etc.
Since files can´t be replaced permanently due to dynamic partitions this is not in the scope of a kernel only mod, but rather custom rom territory as the entire firmware would need be to rebuilt.
Other approaches would be super hacky and one crash or failed boot can easily mess up the phone.

 

[STTec CEO]

Could you please modify a special version CONFIG_ZRAM_WRITEBACK=y for me? I have my own script and module configured for loop27 and writeback strategies. Thanks a lot!

 

[szalaigabor1999]

Hi! Have been considering this phone lately mainly for the HDMI-over-USB-C function.
I intend to run ARM linux on the phone so I'd like to kindly ask if KVM support is planned for this kernel in the future?
The Asus ZenFone 2 received many KVM enabled unofficial kernels and the Pixel 6 comes with KVM enabled out-of-the-box so I'm asking if it would be possible on the Xperia1 III.

I know it's a difficult task and I don't expect it to come true anytime soon but this phone is more than capable of running linux.
Native speed would be the icing on the cake!

 

[Freak07]

Hi! Have been considering this phone lately mainly for the HDMI-over-USB-C function.
I intend to run ARM linux on the phone so I'd like to kindly ask if KVM support is planned for this kernel in the future?
The Asus ZenFone 2 received many KVM enabled unofficial kernels and the Pixel 6 comes with KVM enabled out-of-the-box so I'm asking if it would be possible on the Xperia1 III.

I know it's a difficult task and I don't expect it to come true anytime soon but this phone is more than capable of running linux.
Native speed would be the icing on the cake!

Unfortunately QCOM has disabled el2 deeper than kernel level so that's never going to happen. Except for some miracle.

 

[DrDrag0n]

Update to 3.0.1

Hey guys and girls,

Seems I forgot to include wireguard kernel side implementation in the previous build. Thanks to @derin38 for spotting.
This release adds wireguard support.

More changes can be found in the Changelog below:


Changelog:
- Include wireguard kernel side implementation


Download:
Attached to this post as AFH is currently not working correctly.



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

trying to install this on latest sony release and i get error unsupported android version