Related
** Note: This kernel is end-of-life and will no more be maintained. There will be no LineageOS 15.1 or newer kernel be available anymore **
Hi all,
this is the thread about the CM version of the well-known Boeffla-Kernel for the Samsung Galaxy S3 international.
Note: This kernel is only for CM based roms!!! Do not install it on a Samsung based rom!!!
For Omnirom, please do not use the CM kernel but the separate Omnirom kernel I also provide.
Difference NG kernels to normal kernels:
NG = next generation, it does use pure Samsung source codes only, not the smdk4412 kernel sources of the CM or Omnirom team anymore.
If you are unsure whether to use the NG or the normal kernel, I recommend NG kernel always! Try it first if it works fine for you.
For the Samsung Boeffla-Kernel, please go HERE.
If you have questions to settings, presets, others configuration and wanna share your configuration, head over to the unofficial Boeffla-Config App Config sharing thread:
http://forum.xda-developers.com/showthread.php?t=2621308
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Compatibility
Important: This kernel is only meant to be compatible with official Cyanogenmod and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app.
Click here to learn about using the config app.
I will refuse any support if you do any undervolting and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for CM12.0: KLICK HERE
Change log for CM11.0 NG: KLICK HERE
Change log for CM11.0: KLICK HERE
Change log for Omnirom: KLICK HERE
Change log for CM10.2: KLICK HERE
Change log for CM10.1 kernels: KLICK HERE
Features
* Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
* To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from here: DOWNLOAD
* Support for generic framework naming convention framework-2.jar instead of proprietary rom framework names
* Upstreamed to Linux 3.0.101(www.kernel.org)
* CPU "soft" overclocking to 1500 or 1600 MHz
* CPU undervolting interface
* GPU frequencies configurable (underclocking, overclocking up to 700 MHz)
* GPU voltages configurable (undervolting, overvolting)
* Configurable zRam
* Configurable touch-to-wake
* Configurable touch boost frequency
* Configurable early suspend time (for screen off animations, 100ms default)
* Configurable LED for fading mode, speed and brightness
* Softkey touch button LEDs controllable
* Configurable charger rate for AC, USB and wireless (default increased to 1100 mA for ac charging)
* Charge information display support via Boeffla-Config V2 app
* Charging logic supports ignore unstable power and remove safety margin
* Boeffla-Sound engine V1.6.5 to unleash the power of the Galaxy S3 audio chip
* Additional governors: zzmoove 0.7d, pegasusqplus, smartassv2 and lulzactiveq
* Governor profiles for pegasusq, pegasusqplus and zzmoove for performance, battery saving etc. (2 more zzmoove profiles added - credits to Yank)
* Additional schedulers: ROW, ZEN, BFQ (v6r2) and SIO
* Schedulers configurable separate for internal and external SD memory
* Hardcore speedmod sharpness fix implemented (default is off)
* Black crush fix for better balanced display
* SD card read ahead buffer configurable separate for internal and external SD memory (default increased to 256 kB)
* Ext4 File system tweaks (default to on, can be disabled)
* System Tweaks predefined supported (default is off, new Mattiadj tweak set included)
* WIFI Multicast filter for better battery life
* WIFI wakelock times reduction
* Proportional rate reduction for TCP
* TCP congestion changed from Cubic to Westwood
* Wifi mac address change support
* Dynamic fsync 1.2 implemented
* Timeout for external SD card changed to improve handling of crappy SD cards
* Swap supported (but not recommended, use zRam instead)
* init.d support (in /system/etc/init.d - set correct permissions!)
* NTFS (read-only access only!) compiled as a module
* CIFS compiled as a module
* NFS compiled as a module
* XBox controller support as module
* exFat support (if supported by used firmware)
* Battery monitor wakelocks reduced
* Android logger can be disabled
* Disabled various debug logs and traces
* Frandom compiled as a module (for mods like Crossbreeder)
* Triangle away supported
* Automatic EFS backup to external (priority) or internal SD Card (fallback) - now compatible with tools like kTool
* Kernel initialisation log file (with history of 3 log files)
* Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
* Compatibility to common standard apps (Voltage Control, SetCPU, System tuner etc.)
* Compiled with Google arm 4.7 toolchain
* Internal kernel busybox version 1.21.1
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History
Basically I created the Samsung version of Boeffla-Kernel as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!! Which in fact for the CM kernel means now... close to CM kernel sources.
This said, I will definitely NEVER implement:
dual boot (I do not need it)
color "calibration" (I do not like it, but I like the crispy stock colours)
real hard overclocking higher than 1600 MHz as this is outside of Exynos specs
f2fs - it is known to cause various issues and compatibility problems
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it. Everything else I am happy to check and decide.
Compatibility
To reiterate it again: This kernel is only for CM10.1 and CM10.2 based firmwares. It is not designed to run on Samsung based roms!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
Donation
If you like my work, feel free to donate: Donation-Link
You will receive a personal donation code which unlocks some nice comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* Yank555
* ZaneZam
* Hardcore
* Chainfire
* Harunjo
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Supercurio
* Mialwe
* Entropy512
* Faux
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change logs:
LineageOS 14.1
http://kernel.boeffla.de/sgs3/boeffla-kernel-cm/cm14.0/changelog.htm
CM13
http://kernel.boeffla.de/sgs3/boeffla-kernel-cm/cm13.0/changelog.htm
Configuration and profile thread
http://forum.xda-developers.com/galaxy-s3/general/unofficial-boeffla-kernel-app-profile-t2621308
reserved2
*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi
FINALLY. I can experience everything that is boeffla in both worlds. Incredible job, Andi.
All 4 zram swaps are set to different priorities. They should all share the same priority to be of any use beyond what a single swap partition can do... I'm using alpha16 cm10.2 kernel..
TP.
Yeaaaaaaaa
STAticKY said:
All 4 zram swaps are set to different priorities. They should all share the same priority to be of any use beyond what a single swap partition can do... I'm using alpha16 cm10.2 kernel..
TP.
Click to expand...
Click to collapse
Cool, during code migration it seems I imported some wrong lines (copy&paste error).
Good finding, will fix that soon.
Thanks
Andi
Can't wait for this
Sent from my GT-I9300 using XDA Premium 4 mobile app
faddys123 said:
Can't wait for this
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For official beta version you mean?
Yeah, soooon
Andi
Holy crap, I bet my mind will be totally blown in the nearest future before the final decision between the upcoming boeffla kernel & temasek with boeffla..
Hi to all the alpha testers with the dropbox link: I have reuploaded alpha16 for CM10.2, with the swap priorities fixed now.
I will compile 10.1 tomorrow, same goes for load&flash - this will be updated tomorrow. So if you want to try, take it from dropbox directly.
Will drop off for today, was a long and busy day
Cheers
Andi
Lord Boeffla said:
Hi to all the alpha testers with the dropbox link: I have reuploaded alpha16 for CM10.2, with the swap priorities fixed now.
I will compile 10.1 tomorrow, same goes for load&flash - this will be updated tomorrow. So if you want to try, take it from dropbox directly.
Will drop off for today, was a long and busy day
Cheers
Andi
Click to expand...
Click to collapse
Thank you very much for your great work. The CM 10.2 kernel alpha 16 is running without issues for me
Rubén
Same version of the config app?
Swyped from my Galaxy S3 using Tapatalk 4
Sure. 1.3.1 from playstore is latest.
Sent via Tapatalk2 from my Galaxy S3 IPhone killer
zRAM confirmed fixed. Nice even distribution of data.
Kyle07 said:
zRAM confirmed fixed. Nice even distribution of data.
Click to expand...
Click to collapse
Wooohooo - been waiting for this for, well, ever!!
great news!
Has anyone tried this in AOKP? I'm really dying to find out and Andi isn't around yet.
so where is the download link for the beta test build?
reywal said:
so where is the download link for the beta test build?
Click to expand...
Click to collapse
PM him for it.
Sent from my GT-I9300 using xda app-developers app
Cm10.2-alpha16-v2 working beautifully . all zram devices balancing nicely.
Great work man. Keep it up.
On small request, could you make the number of zram devices configurable as well as a configurable swappiness. I'm thinking that 2 devices may be the sweet spot for CPU cycles/performance if it infact uses one thread (core) per block device. Leaving the other 2 core asleep but still having multi threaded zram. Hope its not to much of an ask. Thanks
TP.
*** NOTE: All kernels are now officially end-of-life (EOL).
Please do not expect any more updates for them in future, no maintenance and no bugfixing. ***
Hi all,
this is the thread about my Boeffla-Kernel for the Galaxy Note 10.1 n80xx.
Some of you might know my kernel already from the Galaxy S3 area.
If you want to learn more about the kernel, it's features and how to configure what, I would recommend you to visit the Galaxy S3 thread of the kernel.
Compatibility
Important: This kernel is only meant to be compatible with official Samsung stock firmware and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
Notes:
From version 2.2 onwards, this kernel should work on the following devices: n8000, n8010 and n8013
This kernel is only for Samsung based Jelly Bean (Android 4.1.x) roms!!! Do not install it on CM or AOSP based roms!!!
If you have questions to settings, presets, others configuration and wanna share your configuration, head over to the unofficial Boeffla-Config App Config sharing thread:
http://forum.xda-developers.com/showthread.php?t=2621308
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app.
Click here to learn about using the config app.
I will refuse to give support if you do any undervolting and experience freezes or hot reboots.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for Android 4.1.x kernels: KLICK HERE
Features
* To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from here: DOWNLOAD
* Upstreamed to Linux 3.0.101 (www.kernel.org)
* Based on Samsung source code GT-N8000_JB_Opensource_Update7
* Initramfs from XXCMJ3 stock kernel
* CPU "soft" overclocking to 1500 or 1600 MHz
* CPU undervolting interface
* GPU frequencies configurable (underclocking, overclocking up to 700 MHz)
* GPU voltages configurable (undervolting, overvolting)
* Configurable charger rate for AC and USB (default increased to 1800 mA for ac charging)
* Charge info display support
* Configurable zRam
* Configurable touch boost frequency
* Configurable early suspend time (for screen off animations, 100ms default)
* Boeffla-Sound engine V1.6.5 to unleash the power of the audio hub wm1811
* Additional governors: zzmoove 0.7d, pegasusqplus,smartassv2 and lulzactiveq
* Governor profiles for pegasusq, pegasusqplus and zzmoove for performance, battery saving etc.
* Additional schedulers: ROW, ZEN, BFQ (v6r2) and SIO
* Schedulers configurable separate for internal and external SD memory
* Hardcore speedmod sharpness fix implemented (default is off)
* SD card read ahead buffer configurable separate for internal and external SD memory (default increased to 256 kB)
* Black crush fix for better balanced display
* Ext4 File system tweaks (default to on, can be disabled)
* System Tweaks predefined supported (default is off)
* WIFI Multicast filter for better battery life
* WIFI wakelock times reduction
* Proportional rate reduction for TCP
* TCP congestion changed from Cubic to Westwood
* Wifi mac address change support
* Dynamic fsync 1.2 implemented
* Timeout for external SD card changed to improve handling of crappy SD cards
* Custom boot animation support
* Swap supported (but not recommended, use zRam instead)
* init.d support (in /system/etc/init.d - set correct permissions!)
* NTFS (read-only access only!) compiled as a module
* CIFS compiled as a module
* NFS compiled as a module
* XBox controller support as module
* exFat support switchable (switch it off if you do not need it)
* Battery monitor wakelocks reduced
* Kernel can root if required (create file "autoroot" on internal sd and reboot)
* Android logger can be disabled
* Kernel logging can be disabled
* Disabled various debug logs and traces
* Frandom compiled as a module (for mods like Crossbreeder)
* Automatic EFS backup to external (priority) or internal SD Card (fallback)
* Kernel initialisation log file (with history of 3 log files)
* Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
* Compatibility to common standard apps (Voltage Control, SetCPU, System tuner etc.)
* Compiled with Google arm 4.7 toolchain
* Internal kernel busybox version 1.21.1
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
Objective
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
I will, also in future, only add features that make sense to me personally as well and are not against my initial objectives. You can always raise your wishes and requests, however there is absolutely no guarantee it will be implemented.
This said, I will definitely NEVER implement:
dual boot (I do not need it)
color "calibration" (I do not like it, but I like the crispy stock colours)
real hard overclocking higher than 1600 MHz as this is outside of Exynos specs
f2fs - it is known to cause various issues and compatibility problems
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it. Everything else I am happy to check and decide.
Compatibility
To reiterate it again: This kernel is only for Samsung based Jelly Bean (Android 4.1.x) firmwares. It is not designed to run on AOSP based roms!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
Donation
If you like my work, feel free to donate: Donation-Link
You will receive a personal donation code which unlocks some nice comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* Yank555
* ZaneZam
* Hardcore
* Chainfire
* Harunjo
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Supercurio
* Mialwe
* Entropy512
* Faux
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
--- reserved for future use ---
Last change log:
Version 3.2 stable - Final
19.02.2016
Merged latest Samsung KK kernel sources GT-N8000_KK_Opensource (XXUDOF1)
Internal kernel busybox updated to latest version 1.24.1 (self-compiled from sources, www.busybox.net)
Fixed improper file permissions in ramdisk (improve stability)
Changed some compiler switches (for stability)
Internal kernel superuser updated to su 2.52
--- reserved for future use2 ---
--- reserved for future use2 ---
Wow!! I was extremly pleased with your kernel for S3, just bad for me that I dont own the wifi version of this tab. Maybe do one for 8000 also? Anyways welcome to the party
Sorry nick. My rule of thumb is still in place: I only develop for a device I personally own and can test.
Andi
Thanks a lot. Have i9300 and n8010. Both with your kernel. :beer:
Sent from my GT-I9300 using XDA Premium 4 mobile app
Thanks, ATM I'm using it to change my scheduler to SIO and use the Boeffla sound engine. Most of what's in the Boeffla config are like airplane controls to me.
Would be nice if someone comes up with a guide with recommended settings.
It this capatible with GT-N8013?
Sent from my GT-N8013 using XDA Premium 4 mobile app
Finally a kernel for the N8010 and not the N8013. I know they are the same, but still
hope to have n8000 version of this kernel
WOW, great to see you here with a kernel for our device! I'm aware of your work for the Galaxy SIII. Gonna test the kernel NOW! Thanks!!
Looking good boss!
kalashenicof said:
It this capatible with GT-N8013?
Sent from my GT-N8013 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Honestly, I do not know. The 8013 seems to be the US variant of the 8010. Usually, kernels of US vs. European variants cannot be exchanged.
But I guess nothing can go wrong if you give it a try (do a nandroid backup first, so you have the current kernel safe).
If you tried it, please report back.
Nightf0x_007 said:
hope to have n8000 version of this kernel
Click to expand...
Click to collapse
Only if you guys put some buck together and buy me a n8000. Seriously.
I have a golden rule of thumb: I only develop for devices I have myself, as this is the only way to do proper testing and ensure quality.
Nikorasu said:
Thanks, ATM I'm using it to change my scheduler to SIO and use the Boeffla sound engine. Most of what's in the Boeffla config are like airplane controls to me.
Would be nice if someone comes up with a guide with recommended settings.
Click to expand...
Click to collapse
Hi,
well, it is a wide topic. That is why I recommended to head over to the S3 thread and search a little bit through it.
Also there is plenty (partially outdated) information on the kernel homepage under configuration as well.
However, my personal configuration currently is:
- governor zzmoove
- governor profile zzmoove -battery yank
- scheduler internal to row
- scheduler external to bfq
- read ahead buffer internal 512
- cpu idle mode to aftr+lpa
- boeffla-sound of course, but this is very much subjective
- touch boost down to 400 (to save some juice)
Andi
Lord Boeffla said:
Honestly, I do not know. The 8013 seems to be the US variant of the 8010. Usually, kernels of US vs. European variants cannot be exchanged.
But I guess nothing can go wrong if you give it a try (do a nandroid backup first, so you have the current kernel safe).
If you tried it, please report back.
Only if you guys put some buck together and buy me a n8000. Seriously.
I have a golden rule of thumb: I only develop for devices I have myself, as this is the only way to do proper testing and ensure quality.
Click to expand...
Click to collapse
Actually, about the europe and US variants - they appear to be absolutely identical. I personally purchased mine in Germany (obviously the N8010 europe variant), but I've been using a ROM and a kernel for the N8013 (US Variant) for quite a while and haven't lost any functionality or encountered any problems.
But it is very good that we do have a kernel for the europe variant finally.
++ for N8000 version as it lacks of kernels witch such funcionalities ;(
Documentation up-to-date
Hi all,
after many hours of hard work, I am now happy to announce, the documentation is now fully updated again.
Help on both Boeffla-Config app as well as every single configuration option with background information is now available on your finger tips.
How to get there?
1. In Boeffla-Config app go into menu, select help. This displays the Boeffla-Config app help to you. If you click the first link on that page, you are moved to the configuration section for all settings.
2. Just go on homepage www.boeffla-kernel.de and select from the left-hand menu.
3. Follow these links:
Boeffla-Config App help
Boeffla-Kernel Configuration
Hope it is useful for you. At least I will now point all people asking questions answered in these sections to that sections only.
Thanks
Andi
1.0-beta2
Hi all,
before I disappear into the weekend, a new beta version for you
1.0-beta2
Change Log
Added Zen scheduler
Added system fs to display asv level in Boeffla-Config app
Upstream to 3.0.97 Linux kernel from 27.09.13
Major cleanup
As always - get it via Load&Flash or grab it from the Kernel homepage.
Cheers
Andi
I was going to give it a shot on my 8013 and see if it would work. I'm not sure about something though. Your file for the kernel has "CWM" in the title. I am using TWRP. I didn't know if you HAD to use CWM for some reason or if TWRP would by okay? I guess I can change the recovery, but in the past I've seen people say CWM for this or that and TWRP worked fine. Want to be sure before I flashed it with TWRP.
Ups. Never used this recovery honestly. So I really do not know.
Maybe someone else can comment...
Sent via Tapatalk2 from my Galaxy S3 IPhone killer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
High performance & power-saving tweaks for all devices (THAT ACTUALLY WORK)
Introduction
LKT aims to achieve a fair balance between power consumption and performance. Instead of tuning the parameters manually, LKT adopts Project WIPE open-source interactive parameters for the mainstream SOCs that are generated by machine learning AI via simulation and heuristic optimization algorithms.
How does it work?
WIPE v2 focuses on meeting performance requirements when interacting with APP, while reducing non-interactive lag weights, pushing the trade-off between fluency and power-saving even further. QTI Boost Framework, which must be disabled before applying optimization, is able to dynamically override parameters based on perf hint. This project utilizes the QTI Boost Framework and extends the ability to override custom parameters. When launching APPs or scrolling the screen, applying more aggressive parameters to improve response at an acceptable power penalty. When there is no interaction, use conservative parameters, use small core clusters as much as possible, and run at a higher energy efficiency OPP under heavy load.
Features
Multi-Profile
Improved smoothness & battery life
Advanced interactive governor tuning (Project WIPE)
EAS devices Support
RAM management enhancements
IO blocks enhancements
Enabled & configured wakelock blocking
Disabled excessive logging at kernel level (Improves battery life as well as performance)
Other miscellaneous adjustments to enhance power efficiency
Profiles
Battery: Can achieve ~2 hours or longer on-screen battery life, may lag in some scenarios where the load fluctuates dramatically
Balanced: smoother than the stock config with lower power consumption(recommended)
Performance: Same as balanced profile, with more responsiveness
Turbo: Provides a stable performance utilizing the maximum capacities of the device without limitation .
Click to expand...
Click to collapse
Requirements
Magisk
Busybox (Required for terminal commands)
Installation
Flash in TWRP or Magisk manager
Follow the given instructions
Reboot
** Make sure to read FAQ from here or second post before asking anything. (regularly updated)
Credits
Code:
Project WIPE contributors [URL="https://github.com/yc9559/cpufreq-interactive-opt/tree/master/project/20180603-2"]Github[/URL]
yc9559 - @CoolApk
cjybyjk - @CoolApk
[U]Special Thank[/U]
Zackptg5 & ahrion - Unity template
topjohnwu - Magisk
@xLidz from falltorise - Banner design
Contributors
@korom42
Sources
Original XDA thread
Github
License
Licensed under the GNU General Public License v3
FAQ(frequently asked question)
Also check for FAQ here (More often updated)
• How do I apply these tweaks?
Simply flash LKT zip in recovery or Magisk app then reboot.
• Do I have to be rooted?
Yes, LKT needs either Magisk or SuperSU or init.d support.
Beware that LKT is a collection of advanced tweaks that act on kernel level. If you don't know how it works, then please try this at your own risk. I won't be responsible for any damage or loss. Never forget to make backups.
• What are the available profiles ?
Battery: Can acheive ~2 hours or more longer on-screen battery life, may lag in some scenarios where the load fluctuates dramatically
Balanced: smoother than the stock config with lower power consumption(recommended)
Performance: Same as balanced profile, with more responsiveness
Turbo: Provides a stable performance utilizing the maximum capacities of the device without limitation
Click to expand...
Click to collapse
• How to switch between profiles?
Method 1
To access the command controls screen using terminal type
Code:
su
lkt
Then follow the instructions
Method 2
Now you can also you run these commands to directly switch profiles (must run with root permissions)
Code:
lkt 1 (for battery profile)
lkt 2 (for balanced profile)
lkt 3 (for performance profile)
lkt 4 (for turbo profile)
Method 3
You can also to re-flash the module twice to change the profile but you will have to reboot using this way.
• Can I use LKT with another MOD ?
** Compatibility list** You can still these mods since they do not affect LKT parameters.
Universal XML Patcher
GMS Doze
ForceDoze, Naptime, Greenify, Amplify, Power Nap
MCS (Magic charging switch) & Charging control mods..etc
BlackenedMod (Pixel 2)
** Incompatibility list ** Do not use similar mods with LKT, here is a list of some known MODs that will interfere
AKT (Advanced Kernel Tweaks)
Spectrum
Helix Engine
L-Speed
GovTuner
Every bullsh*t placebo MOD like : CrossBreeder, NFS, KITANA, FeraDroid ..etc
Heavily tweaked ROM such as : xXx (OP6/6T)
• Will this work on my ROM & Kernel ?
It should work on almost every Stock, AOSP or Lineage based ROM & Kernel
The only problem is with heavily tweaked ROMs, they can interfere with LKT.
• Will this work on my device?
This mod support a large list of devices you can check the compatibility list.
• How to make sure that LKT is working ?
Using a file explorer with root access check LKT logs in the location below ( share & upload yours in case of having troubles)
Code:
/data/LKT.prop
•I cannot find or open LKT logs
To properly open LKT.prop you need a file manager with root access your app may not be working correctly. Here's some apps I can recommend
MiXplorer
FX File Explorer + ROOT addon
You can also access your alogs using terminal by running this code
First type su then copy and past this line :
Code:
cat /data/LKT.prop
• My logs are incomplete
Make sure you are using the latest version of Magisk 18.0+
Install busybox by @osm0sis
• My device Lags or not longer smooth What do I do?
This can happen and it's a normal thing. As I have stated before, all these tweaks have been done for fit certain usage which might not be the same as yours. Because this, your device may lag in some scenarios under heavy loads (If you are experimenting huge lags, you have done something wrong). And yes, this can be fixed. We have a couple of ways of fixing it. First of all if you are using battery profile try switching to another one, if this doesn't help you consider the following steps :
Do a factory reset
Get rid of unnecessary background apps
Try a different ROM or Kernel
Try another profile
• These settings don't work & I'm not getting great screen on time
Keep in mind these tweaks have been tested on certain scenario that might not the same as yours, read the introduction in OP to understand more about this. However if you are getting worse results than before you are probably doing something wrong and here are some recommendations for you
Do a factory reset
Get rid of unnecessary background apps
Try a different ROM or Kernel
Try another profile
• How to update LKT?
Dirty flash the new zip or install the update via Magisk manager and it will automatically upgrade.
• How to uninstall LKT?
Flashing the module for the second time will remove LKT. You can also remove it from Magisk app.
Compatibility
Snapdragon 855
Snapdragon 845
Snapdragon 835
Snapdragon 820-821
[*]Snapdragon 810-808
[*]Snapdragon 801-800-805
Snapdragon 660
Snapdragon 652-650
Snapdragon 636
Snapdragon 625-626-630
[*]Snapdragon 615-616
[*]Snapdragon 450
[*]Snapdragon 435
[*]Snapdragon 430
[*]Snapdragon 425
[*]Snapdragon 410-412
[*]Snapdragon 400
Exynos 9810 (Samsung)
Exynos 8895 (Samsung)
Exynos 8890 (Samsung)
Exynos 7420 (Samsung)
[*]Kirin 970 (Huawei)
[*]Kirin 960 (Huawei)
[*]Kirin 950-955 (Huawei)
[*]kirin 650-655-658-659 (Huawei)
[*]Helio x20-x25 (MT6797-MT6797T)
[*]Helio x10 (MT6795-MT6795T)
[*]Helio P10 (MT6755)
[*]Intel atom Z3560-3580
Click to expand...
Click to collapse
**Please note that even if your device isn't listed here some parameters may still apply
Changelog
Code:
v1.9 (15/08/2019)
- New EAS & HMP interactive parameters ([URL="https://github.com/yc9559/wipe-v2/"]WIPE v2[/URL])
- Better Support for EAS Custom kernels
- RAM management and Multitasking improvement
- New terminal UI
- Unity template update 4.3
- Bug fixes
- Added support:
*SD675
*SD730
*SD710
- Extended EAS CPU optimisations further via QTI Boost Framework for
*SD855
*SD845
*SD710
*SD730
*SD675
- Removed support for many SoCs for now, might add later if I have enough time
Downloads
• Google Drive
You can also download LKT from Attachments or Magisk repo
Beta testing & Support
• Telegram
• Slack
Donate to support future LKT development :fingers-crossed:
Hi, does include Google service drain fix?
battery usage screen shot plz
I installed this along with the recommended FSC thermal driver and my battery life actually got a bit worse, and my phone drains faster after the screen is off. Previous to installing this, my battery drain graph was basically vertical on screen off. How can I uninstall this mod and go back to my previous settings?
snake218 said:
Hi, does include Google service drain fix?
Click to expand...
Click to collapse
yes
rmb.gh said:
battery usage screen shot plz
Click to expand...
Click to collapse
nurav666 said:
I installed this along with the recommended FSC thermal driver and my battery life actually got a bit worse, and my phone drains faster after the screen is off. Previous to installing this, my battery drain graph was basically vertical on screen off. How can I uninstall this mod and go back to my previous settings?
Click to expand...
Click to collapse
what profile are you using ? also what kernel and rom if you are on custom rom you must you use the custom rom celaner zip
also you might want to check new version v3 .. profiles are more battery oriented now
to remove the mod simply flash the remover [Uninstaller]LXT™_Remover.zip
Didn't work for me. Phone got super laggy after flashing. Even switching between homescreens or scrolling through Google Now feed have terrible lag.
I'm on eXistenZ rom. Used cleaner, then flashed LXT Balanced, then FSC and wiped cache afterwards. Tried a couple more times without FSC and without cleaner all with the same result.
macaulay mcculkin said:
Didn't work for me. Phone got super laggy after flashing. Even switching between homescreens or scrolling through Google Now feed have terrible lag.
I'm on eXistenZ rom. Used cleaner, then flashed LXT Balanced, then FSC and wiped cache afterwards. Tried a couple more times without FSC and without cleaner all with the same result.
Click to expand...
Click to collapse
Definitely that lag you are complaining about IS NOT related to my mod, older versions v1/v2 maybe had few issues but sincr v3 everything is super smooth .. I'll post benchmarks and videos proof if you don't believe .. you saying that you are on custom ROM well keep mind that the rom cleaner zip only removes "init.d scripts" and restore stock "init.qcom.post_boot.sh" file .. So next time you want to try my mod and give a legit feedback.. do a clean firmware installation, use stock or/Androplus kernel ... follow the tips from #2nd_post then report back
korom42 said:
yes
what profile are you using ? also what kernel and rom if you are on custom rom you must you use the custom rom celaner zip
also you might want to check new version v3 .. profiles are more battery oriented now
to remove the mod simply flash the remover [Uninstaller]LXT™_Remover.zip
Click to expand...
Click to collapse
I used the balanced profile, and it seems like the phone was unable to get to deep sleep. I'm running stock ROM. I tried V3 as well, but I'm guessing it's not easy for everyone to get consistent results because of different usage patterns. I removed your script and now I'm back to my previous battery life. I will definitely try your mod again on your next release.
New version is up with major changes ..
-V4 | 15/11/2017
Gov Profiles :
- All profiles rebuilt from scratch .. Heavily tested under different usage patterns
- Significant improvements in battery life and performance for all profiles (the jackpot is to know how exploit efficient frequencies !!)
Misc :
- IO Tweaks : Switched to "noop"
- Some bug fixes
Thanks for your work, will test.
A question, do you think overall performance will be better setting zram higher? (currently just 60mb for what I see?) and set read ahead value to 2048 instead 512kb?
korom42 said:
New version is up with major changes ..
Greater battery life and improved smoothness .. please update !
-V4 | 15/11/2017
Gov Profiles :
- All profiles rebuilt from scratch .. Heavily tested under different usage patterns
- Significant improvements in battery life and performance for all profiles (the jackpot is to know how exploit efficient frequencies !!)
Misc :
- IO Tweaks : Switched to "noop" instead of "maple" (seems to be more power efficient)
- Some bug fixes
Click to expand...
Click to collapse
Bro thank you for mod. I want to ask a question. What is the "Cleaner for Custom Roms" in your download folder?
Mazellat said:
Bro thank you for mod. I want to ask a question. What is the "Cleaner for Custom Roms" in your download folder?
Click to expand...
Click to collapse
Read the first post
Mazellat said:
Bro thank you for mod. I want to ask a question. What is the "Cleaner for Custom Roms" in your download folder?
Click to expand...
Click to collapse
Maybe im not the one to answer, but it restore stock init.qcom.post_boot.sh file.
PD: anyone has the stock thermal-engine.conf?
Great job RXS bro @korom42 ^^
Verstuurd vanaf mijn D6503 met Tapatalk
Mazellat said:
Bro thank you for mod. I want to ask a question. What is the "Cleaner for Custom Roms" in your download folder?
Click to expand...
Click to collapse
Well it removes scripts from init.d folder and replaces init.qcom.post_boot.sh with stock one from 7.1.1
snake218 said:
Thanks for your work, will test.
A question, do you think overall performance will be better setting zram higher? (currently just 60mb for what I see?) and set read ahead value to 2048 instead 512kb?
Click to expand...
Click to collapse
For Zram.. overall performance won't be affected that much .. Total free RAM might be slightly less but with great battery savings .. for read ahead value it won't affect anything .. maybe in next version will apply some changes for the balanced profile strictly .
snake218 said:
Maybe im not the one to answer, but it restore stock init.qcom.post_boot.sh file.
PD: anyone has the stock thermal-engine.conf?
Click to expand...
Click to collapse
You can find it my fsc custom thermal.e mod thread downloads .. zip name [XZ]_Back_to_stock.zip
korom42 said:
Well it removes scripts from init.d folder and replaces init.qcom.post_boot.sh with stock one from 7.1.1
For Zram.. overall performance won't be affected that much .. Total free RAM might be slightly less but with great battery savings .. for read ahead value it won't affect anything .. maybe in next version will apply some changes for the balanced profile strictly .
You can find it my fsc custom thermal.e mod thread downloads .. zip name [XZ]_Back_to_stock.zip
Click to expand...
Click to collapse
Must I flash Cleaner before flashing mod?
Mazellat said:
Must I flash Cleaner before flashing mod?
Click to expand...
Click to collapse
Absolutely especially if you're using a custom rom
I also recommend switching to Androplus or stock kernel..
If you have other tweaks on your rom also remove them ..
Please read notes from #2nd posts
korom42 said:
Absolutely especially if you're using a custom rom
I also recommend switching to Androplus or stock kernel..
If you have other tweaks on your rom also remove them ..
Please read notes from #2nd posts
Click to expand...
Click to collapse
I am using eXzistenZ and Androplus v29. Thank you for your replies...
could you please set a delay after boot ?
and why make lowmemorykiller minfree so large, app reload like ****....
Kirisakura-Kernel for the OnePlus 8 Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the OnePlus 8 Pro aka InstantNoodle.
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!
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.
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. In fact this may be (and probably is) the first 4.19 msm kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If that got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
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 865 that´s built into the OP8 Pro.
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 others 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.
I´d like to mention @tbalden ´s excellent CleanSlate features at this place. They improve usability by a big margin for me personally. The highly customizable sweep to sleep implementation (adjustable to different navigation settings), long tap to bring down status bar (very useful on a big device), backlight dimmer and notification reminder are very useful features that I use personally every day, which can be enabled rootless if one desires to run without root.
Another 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 OnePlus for Android 10 and intended for use on OOS-Stable releases
- compiled with Clang 11.0.3 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.19.146
- CAF base for the Snapdragon 865 (SD865) updated to CAF-Tag LA.UM.8.12.r1-12500-sm8250.0
- Kernel Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO
- fix various CFI-Violations found in various subsystems like OnePlus drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Cleanslate Features included! See @tbaldens´s CleanSlate Thread for more information
- Flashable via EXKM and FKM on a rooted system!
- Anykernel zip is based on the Anykernel3 release from @osm0sis
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- Dynamic Stune Boost to inflate task utilization and not overload cores on interaction (thanks to @RenderBroken, @joshuous and @tbalden for the rootless implementation )
- updates from kernel/common
CPU related features:
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This compliments EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
GPU related features:
- GPU driver updated to latest CAF-State
- remove POPP functionality from GPU driver to avoid constant fight about downscaling with msm-adreno-tz
- don´t wake the gpu on touch input, instead wake when receiving an ioctl
- don´t copy fence names by default to save a bit of cpu-time (explanation)
- msm: kgsl: Stop slab shrinker when no more pages can be reclaimed
File System related features:
- improve memory allocations in sdcardfs
- improve eventpoll logging to stop indicting timerfd (improves kernel wakelock readability)
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
UI/UX/Usability related features from CleanSlate:
- CleanSlate features made by @tbalden
- Flashlight Notification/Call blinking
- Vibrating Notification Reminder
- Sweep to Sleep touchscreen gesture - highly customizable
- DoubleTap on Sweep2Sleep's area gestures - new way to pull down android Notification Area
- Face down screen off - new gesture
- Backlight Dimmer - possibility to use lower panel brightness (switch DC dimming off in Lab settings!)
- KCAL Color Control (credit to @savoca)
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbr2
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF default)
- various fixes for PSI-Monitor, which is used by the userspace lowmemorykiller-daemon
- Fix various memory leaks in different subsystems
- improved mm with patches from mainline
- various other changes from mainline
- included zstd as an option for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- improve memory allocations in various subsystems
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- fix various CFI-Violations found in various subsystems like OnePlus drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled, enable them with your favorite kernel manager
- includes new bbr2
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:
- 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
- add support for steam controller
- add support for nintendo switch controller
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching OnePlus firmware. When OOS receives an update it takes OnePlus 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.
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk-stable, if you choose to use Magisk.
3. Flash the kernel.zip via latest EXKM or FKM app, or TWRP (haven´t tested TWRP myself as I don´t need it) and do a full reboot.
4. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=313864
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 10
1.0.0 Initial Release
1.2.0 https://forum.xda-developers.com/showpost.php?p=83260487&postcount=67
1.2.2 https://forum.xda-developers.com/showpost.php?p=83521551&postcount=119
1.2.4 https://forum.xda-developers.com/showpost.php?p=83539543&postcount=125
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC wingman!
@LeeDroid and @mwilky for their awesome roms and work!
@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 too
@topjohnwu for magisk!
XDA:DevDB Information
Kirisakura Kernel, Kernel for the OnePlus 8 Pro
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_OP8PRO_InstantNoodle
Kernel Special Features:
Version Information
Status: Stable
Created 2020-06-19
Last Updated 2020-09-20
FAQ
F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img from matching firmware you are on and flash the extracted boot.img via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom.
Question: How to report bugs properly?
Answer: Have a look at post #3 in this thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re not using any mods, magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a ramoops file.
Easiest way is immediately after booting up, with a root explorer navigate to sys/fs/pstore. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
Useful Resources
How to report bugs:
It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).
The following guide from @nathanchance is a very good guideline on how to properly report a bug!
Please also take a log at the FAQ one post above. It covers some procedural steps as well and serves as a guideline too!
https://github.com/nathanchance/Android-Tools/blob/master/Guides/Proper_Bug_Reporting.txt
Hello everyone
I want to lose a few words about this kernel.
Before anybody asks, it´s made for the OP8 Pro only!
As you may or may not have noticed by reading the OP this kernel is very far from the stock base.
Adding linux-stable upstream and CAF-Upstream causes the commit-count to increase from 805000 to about 840000.
A "higher" commit count does not automatically translater to a better kernel. However upstreaming linux-stable and the CAF-Base to the latest code is an important aspect, that´s often cast aside. (after all the android kernel is based on the linux-kernel and the CAF-Base is the kernel base OnePlus bases the kernel for the OP8 Pro on) . Many developers work constantly on improving the linux-stable branches with commits that are tested, same goes for the qualcomm developers over at the CAF-Forums.
The main goals of this kernel are summarized in the OP. I encourage everyone to at least read once through it.
Here´s a short summary of what I think are the most characteristic and important aspects (also an excerpt from the first post of this thread ):
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security, stability and performance! This includes Linux-Stable, CAF-Upstream and kernel/common.
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. In fact this may be (and probably is) the first 4.19 kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If some of that got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
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 865 that´s built into the OP8 Pro.
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 others 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.
I invite everybody to try the kernel
If you face any bugs, I´d appreciate if bug reports are done in the proper way, like it is asked for and explained in the 2nd and 3rd post.
If you read the OP you probably noticed I´m not talking about any improvments (some call it even magic) to performance or battery life. This is not one of the direct goals of this kernel.
If the modifications present in the kernel make you feel a noticable difference in either of these I´m very happy for you. I know that artifical benchmarks are improved and some other things I tested.
If this kernel is not for you you can very easy return to the stock kernel, like it´s described in the FAQ as well!
There might not be updates of this kernel for every single linux-stable upstream revision that is released at kernel.org or every single new commit added to the tree, but rather less updates but bigger ones.
I guess that gives everybody a rough idea of where this project might be going.
I wish everybody a nice day
Loved this for the 7 pro. Welcome ?
Woohoo, welcome!
Congrats on this truly great achievement.
Keep it up.
[emoji106][emoji106][emoji122][emoji122]
Sent from my Pixel 4 XL using Tapatalk
Excellent, welcome!
Hey buddy! Nice to see you here! ?
possible to add option to disable touchboost?
tbalden said:
Woohoo, welcome!
Congrats on this truly great achievement.
Keep it up.
[emoji106][emoji106][emoji122][emoji122]
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Thank you! Glad to have you as a wingman for a very long time across different devices now!
Keep on rocking with all the CleanSlate goodies!
Reuben_skelz92 said:
Loved this for the 7 pro. Welcome
Click to expand...
Click to collapse
kristofpetho said:
Excellent, welcome!
Click to expand...
Click to collapse
TheKnux said:
Hey buddy! Nice to see you here!
Click to expand...
Click to collapse
Thank you
Nekromantik said:
possible to add option to disable touchboost?
Click to expand...
Click to collapse
Yes, since all Cleanslate features are included it´s accessible via CleanSlate config app.
https://forum.xda-developers.com/showpost.php?p=82598221&postcount=192
Gestures and Extras Section - Stock touchboost.
nice to see ya here
Doing a sexy dance right this minute! :victory: Dam glad your covering this device now also buddy Always a great solid kernel that runs smooth and fluid without issue! :good:
Omg the kernel was amazing on the OP7P, can't wait to use this one again on my 8!
Running smooth as butter for me ?
Thank you sir, donation sent.
Nice to see this Kernel here for the 8pro
Gesendet von meinem IN2023 mit Tapatalk
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Lxeon said:
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Click to expand...
Click to collapse
The lowmemorykiller daemon is no longer in the kernel. it’s handled from userspace on the op8 pro on android 10 OOS.
Unfortunately nothing I can do in the kernel to change this.
If apps are getting killed say thank you to OnePlus and OOS. Not related to the kernel.
Lxeon said:
seems it disable lowmemorykiller? i cant check it from FK kernel App and i want change it, **** OS with12g RAM still killng bg app
max its used 65% RAM, can not used more than it.
Click to expand...
Click to collapse
Try to disable zram/swap
cultofluna said:
Try to disable zram/swap
Click to expand...
Click to collapse
still around 65%
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
Freak07 said:
The lowmemorykiller daemon is no longer in the kernel. it’s handled from userspace on the op8 pro on android 10 OOS.
Unfortunately nothing I can do in the kernel to change this.
If apps are getting killed say thank you to OnePlus and OOS. Not related to the kernel.
Click to expand...
Click to collapse
good hardware, suck software
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.
Spoiler: Documentation Control-Flow-Integrity (CFI) / Shadow Call Stacj (SCS)
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 13 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.231
- 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:
https://www.androidfilehost.com/?w=files&flid=326387
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
2.0.12 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87641841
2.0.15 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87944971
Android 13
3.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88195025
3.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88326835
3.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88632657
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
F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img, vendor_boot.img as well as dtbo.img from matching firmware you are on and flash them via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom and re-root.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: The kernel uses a ramdisk overlay to apply some settings after boot. If you are not rooted these settings will not get applied and you miss some of the optimizations.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a .zip of /asdf.
Easiest way is immediately after booting up, with a root explorer navigate to /asdf. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
and this is mine too
justincase
last one I promise
Woah another kernel for sake ! Might give it a try later !
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:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/UL-I006D-ASUS-30.11.51.67-1.1.25-user.zip
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:
https://www.androidfilehost.com/?fid=14943124697586354960
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 said:
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:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/UL-I006D-ASUS-30.11.51.67-1.1.25-user.zip
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:
https://www.androidfilehost.com/?fid=14943124697586354960
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
Click to expand...
Click to collapse
Hello. I tried this kernel recently. But now I want to return to the stock core. But when I flash boot.img and dtbo.img, the settings stop working for me. There are also no items in Quick Settings. What am I doing wrong?
a7lanov said:
Hello. I tried this kernel recently. But now I want to return to the stock core. But when I flash boot.img and dtbo.img, the settings stop working for me. There are also no items in Quick Settings. What am I doing wrong?
Click to expand...
Click to collapse
Soory, wrong post
a7lanov said:
Hello. I tried this kernel recently. But now I want to return to the stock core. But when I flash boot.img and dtbo.img, the settings stop working for me. There are also no items in Quick Settings. What am I doing wrong?
Click to expand...
Click to collapse
Hey,
I forgot to mention to restore vendor_boot.img as well.
Sorry for the inconvenience, I adjusted the OP and the FAQ already.
So to get back to stock, extract boot.img, vendor_boot.img and dtbo.img from the matching stock firmware.zip. make sure you extract from the same firmware you're currently running.
Then flash these via fastboot.
If it doesn't work afterwards your problem lies elsewhere.
Freak07 said:
Hey,
I forgot to mention to restore vendor_boot.img as well.
Sorry for the inconvenience, I adjusted the OP and the FAQ already.
So to get back to stock, extract boot.img, vendor_boot.img and dtbo.img from the matching stock firmware.zip. make sure you extract from the same firmware you're currently running.
Then flash these via fastboot.
If it doesn't work afterwards your problem lies elsewhere.
Click to expand...
Click to collapse
Thank you. Today I will also try to flash the vendor_boot.img
no updates?
I know IT clearly says 'Zenfone 8', but is there any chance this Kernel will work on the 'Zenfone 8 Flip', too? (ZS672KS)... Ty!
elchmartin said:
I know IT clearly says 'Zenfone 8', but is there any chance this Kernel will work on the 'Zenfone 8 Flip', too? (ZS672KS)... Ty!
Click to expand...
Click to collapse
unfortunately no. 8 flip uses a separate kernel.
Hi @Freak07 ,
Thanks a lot for your effort and time that you invested into developing this kernel.
However, as is the case with other custom kernels, I would like to know what kind of battery life benefits I can expect from using this kernel on my device?
Unlocking the bootloader on Asus phones right now means a bit more hassle with the updates, also rooting the phone means a bit more hassle with using some apps (safety net etc),so I would really like to know what are the benefits in terms of battery life.
Update to 1.1.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.11.51.83. 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/zenfone8_zs590ks.MR0.5-30.11.51.83.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.5-30.11.51.83 source code
- Linux-Stable Upstream to 5.4.134
- bump clang to latest prebuilt clang by google
- Merge CAF (QCOM) upstream
- enable ddr cooling device
- raise lto inlining limit
- other improvements please take a look at github
Download:
https://www.androidfilehost.com/?fid=14943124697586372325
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 said:
Update to 1.1.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.11.51.83. 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/zenfone8_zs590ks.MR0.5-30.11.51.83.zip
md5sum: 0f30d5e043f4a675e7db3250d5218125
More changes in the Changelog below:
Changelog:
- Import zenfone8_zs590ks.MR0.5-30.11.51.83 source code
- Linux-Stable Upstream to 5.4.134
- bump clang to latest prebuilt clang by google
- Merge CAF (QCOM) upstream
- enable ddr cooling device
- raise lto inlining limit
- other improvements please take a look at github
Download:
https://www.androidfilehost.com/?fid=14943124697586372325
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
Click to expand...
Click to collapse
Hi. Thanks. And I have a question. I noticed through the Kernel Adiutor that big and prime cpu do not sleep when there is no load, they work at low frequency (original kernel). Is this a hotplug problem? Should they not go to Offline? Do they sleep in your kernel?
a7lanov said:
Hi. Thanks. And I have a question. I noticed through the Kernel Adiutor that big and prime cpu do not sleep when there is no load, they work at low frequency (original kernel). Is this a hotplug problem? Should they not go to Offline? Do they sleep in your kernel?
Click to expand...
Click to collapse
That´s expected behaviour on the few last gens of QCOM SoCs. and you´re also fooled by the ui of the app.
if there are no tasks/work the clusters go into idle c-states, but kernel managers/monitors will show you the frequency that you described.
depeding which battery mode you chose in settings, minfreqs for the clusters will be higher or lower.
dynamic should be at 300mhz for little cluster, 710mhz for big cores and and 844mhz for the prime core.
Freak07
Thanks for clarifying
Freak07 said:
Update to 1.1.8
Click to expand...
Click to collapse
Thanks man!
Could you please let us know if defconfig is stable or it's better to configure something (like cpu/gpu freq's) on the device ?
Does it support both 8GB and 16GB RAM devices?