Develop Bugs

[Kernel][All Quark]BHB27-Kernel android [5.1.1] to [10.x]. For Custom and Stock ROM's - Moto Maxx Android Development

{
"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"
}
I have start this project to bring a more features and updates to Quark Kernel, and put the user on the control of the Kernel configuration
ROM Support:
This will work on any CM/LOS Custom ROM that is up to date to CM/LOS Repo or my custom ROM repo (in doubt check with the ROM developer) And latest Motorola Stock Marshmallow ROM for all devices (for the stock ROM use Kernel V3.5 and up only)
TWRP will display what is flashing during installation if the TWRP screen show something odd print the screen and post on the thread
SuperSu support on Stock ROM:
Link for BETA-SuperSU-v2.62-3-20151211162651_3
If you never flash SU on Stock ROM first Flash that version reboot then go back to recovery and Update using the latest from SU thread
This Kernel has safetynet verification Support on unlocked bootloader of course without ROOT, if you wanna ROOT checks latest hide root support threads use XDA search for that
Main features:
I will bring any featuring and improves that is possible to Quark, but the main point is provide the better experience balance battery vs performance, keep a update kernel and full user control.
Kernel is a slow process to improve I will take my time and will make updates when I can, every update will be tested before release, any bug found please let me know.
Some of the below features can only be see on the app when using this thread Kernel, the below are just some of many featuring of this app/kernel...
CPU and GPU - Over and under clock;
Linux Kernel always update to the latest version;
Many custom CPU GOV optimized for Krait 450;
CPU optimizations;
CPU Per core control;
CPU Per core Frequency control;
CPU Per core Governor control;
CPU Schedule workqueues;
CPU Boost ;
CPU Wakeup Boost and Hotplug Boost;
CPU voltage control;
Custom CPU Hotplug;
Custom Thermal control;
Ram control;
GPU optimizations;
GPU idling algorithm;
Wake gestures Doubletap2wake and Sweep2wake ;
KCAL - Advanced color control;
Sound control module;
Power and suspend Improves;
I/O Scheduler optimizations;
Many custom I/O;
Wake Locks controler;
KSM kernel same-page merging;
Virtual Memory;
Zram;
Network optimizations;
Many custom TCP Cong algorithm;
Custom Kernel Adiutor app with special features just for Quark (to better support my kernel I make my on Kernel adiutor check Downloads)
Check Changelog L, Changelog M, Changelog M and N, Changelog O, Changelog P and Mod Kernel adiutor changelog for full list of features.
Installation instruction Kernel:
Download the latest version
Take a TWRP backup (system, boot and data)
Flash the zip using latest TWRP recovery (wipes are't necessary)
Reboot
Enjoy!
On Oreo, will take two tries to finished the boot process after the update, first is slow and reboot at the end second is fast and after all must work OK
Installation instruction app:
Just Install the apk like anormal app on any ROM it need's ROOT access to work.
Installation Files
Download Kernel Oreo, Nougat and Marshmallow (Marshmallow only version 3.5 and up, Oreo 9.5 and up):
Main:
Gdriver Mirror Click Here (This contains current and previously version)
Secondary:
AFH Mirror Click Here (This contains all old versions)
Download Kernel Lollipop click here
Download App Mod Kernel adiutor for Quark:
XDA Labs Click Here or use XDA Labs app to install update and received updates warning (search for KA27)
AFH Mirror Click Here (This contains all old versions)
TWRP For Quark click here
To go back to Stock ROM kernel:
Oreo:
Is possible in Oreo to just restore or reflash the Stock ROM boot.img, if you did not made a backup of the boot partition, you can extract the boot.img from the ROM zip and install it over TWRP the process is the same as any .zip flash but you must chose "images (is in the bottom right of the install screen) after select the image and image type "boot"
Older than Oreo OS::
As quark kernel is not just a boot.img before Oreo, it has some modules that are on the system partition, to restore is need to re-flash yours ROM zip (a dirty flash) it will re-flash the stock kernel + all the modules of that ROM, but will erase any modification that you made to system like xposed or gapp so is need to re-flash any zip that changes the system partition. Make a TWRP backup first just in case, the dirt flash may bootloop, in that case clean install.
Thanks:
@Skrilax_CZ for his hard work on CyanogenMod for this device.
Big thanks:
A big thank for those that donating to thanks for my work on this kernel
Developer donation link:
To donate via paypal click here
No other donation option is available.
XDA:DevDB Information
BHB27-Kernel, Kernel for the Motorola XT1225, XT1250 and XT1254 -- Moto Maxx, Moto Turbo and DROID TURBO.
Contributors
baybutcher27
Source Code:
Kernel: fgl27/BHB27Kernel/tree/N_c
Toolchain: UBER from matthewdalex/arm-eabi-4.9
How to Build: how_to_build_this.sh
Mod Kernel Adiutor app: fgl27/KA27
Kernel Special Features: Check Changelog L, Changelog M,Changelog M/N Unified, Changelog O, Changelog P/Q
Version Information
Linux: 3.10.x
Status: Stable
Created: 2015-09-21
Last Updated: Check Changelog L, Changelog M,Changelog M/N Unified, Changelog O, Changelog P/Q

Below is some help for the most know problems.
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2)Check the boot reason prop "ro.boot.bootreason" if it is like the example bellow set to power_key_press the device didn't reboot it sled power off.
Code:
[ro.boot.bootreason]: [power_key_press]
Check the prop using :
Kernel Audiutor app > logs section > search in a log > mark getprop > search key word "reason".
If the Random power off are related to battery, BCL can help mitigate the problem.
BCL can be controlled via BHB27 kernel adiutor Power and battery section.
Lowering the BCL Max frequency or Making the number of hot unplugged core higher will help to mitigate the CPU power.
But if the problem persist is necessary to change the BCL low and high voltage threshold to higher values to make BCL to start sooner, the recommendation is to set they to 3700mV (Low) and 4000mV(High) and if the problem is resolved after that, the device stops randomly power it self off, lower the values 100mv it until you find a perfect value, or if the problem persist make the values 100mV higher.
Is also recommended to set the battery "Automatic power saver" from default 15% to a higher value, with is today max at 25%
If the device did just reboot just share a log as recommended on next post.
There is a help like this on the ROM's I share it may help as some problem are ROM related and not kernel so they are not here, so try to check there for more .

This kernel is tested and is fully working.
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.
Always start a post with a bug report with @fgl27 and always attached a log .zip
fgl27 Kernel Adiutor > Logs > One click all Logs to a ZIP
If is a Reboot/Power off related bug make the log as soon the device finishes boot up
Bugs without logs, without @fgl27 will probably not be read, there is too much posts on the thread sometimes and I don't have time to read it all, anyone can post as much as is need of course as long is a things related to this thread
Feature request are welcome too, but understand not all feature that exist is possible to bring to quark.

What's difference between this and kernel of NX?
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1

Flashed, looking forward to seeing if it makes a difference during class and such tomorrow, thanks!

RSDamasceno said:
What's difference between this and kernel of NX?
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1
Click to expand...
Click to collapse
Never used, can find source dev does not seem to publish, can look.
Will ask him for the source.

baybutcher27 said:
This kernel is tested and is fully working.
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.
Feature request are welcome too, but understand not all feature that exist is possible to bring to quark.
Click to expand...
Click to collapse
One request, if possible? "Westwood Plus" TCP congestion control. I know "Cubic" is the Android default, but many tests show Westwood Plus (also written Westwood+) is better under lossy conditions. (Not to be confused with the original "Westwood", Westwood + is a newer version. ) Many custom ROMs include it in their kernels, and some custom kernel devs make it the default over Cubic.
Yes, there is debate over which one is better -- Cubic or Westwood Plus. But isn't choice a good thing?
http://androidmodguide.blogspot.com/p/tcp-algorithms.html
Westwood/Westwood+:
A newer version of Reno, and another commonly used one. It controls parameters better, helping out streaming and overall quality of browsing the internet. One of the most 'fair' algorithms out there, and is one of the most efficient algorithms to date.
Click to expand...
Click to collapse
If it's not possible to include it, I can live with Cubic. Just a request. :good:

ChazzMatt said:
One request, if possible? "Westwood Plus" TCP congestion control. I know "Cubic" is the Android default, but many tests show Westwood Plus (also written Westwood+) is better under lossy conditions. (Not to be confused with the original "Westwood", Westwood + is a newer version. ) Many custom ROMs include it in their kernels, and some custom kernel devs make it the default over Cubic.
Yes, there is debate over which one is better -- Cubic or Westwood Plus. But isn't choice a good thing?
http://androidmodguide.blogspot.com/p/tcp-algorithms.html
If it's not possible to include it, I can live with Cubic. Just a request. :good:
Click to expand...
Click to collapse
Yes The + i did not find because did not know about, i will search, I have included some already in the test version that i'm using, check the pic.
I know how to make things work for quark Kernel, but i don't now all the things that exist, so keep me inform, i will search and if is possible to port to quark i will.
will try to release a new version later today 6 to 8 hours from now, test is very good.

@ChazzMatt the Westwood in the next build is already the Westwood+
check the C file in here
The file is name just westwood but you can read in the file description that is the +... Test kernel is really stable, will released today, let all test and see what is the best for it use...

baybutcher27 said:
Never used, can find source dev does not seem to publish, can look.
Will ask him for the source.
Click to expand...
Click to collapse
You want some screenshots of Kernel Adiutor?
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1

Kernel update! BHB27-Kernel-V1.0.2
Download-Kernel
Changelog-Kernel
Change:
====================
09-22-2015
====================
* V.1.0.2
* Implemented KSM
* Add TCP-CONG Westwood, bic, Highspeed, Hybla, Htcp
* Implemented CPU otimizations Flags to the Kernel (more otimizations to come in next build)
Test and let me know...
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.

BTW try to implemented DT2W and S2W but quark doesn't accepted it (the config is ok but noting happen ), maybe i future update. Can be a conflict with moto screen wave and pick i disable it but not work...
Will try if success will release a separated version with DT2W because it can be a wakealock.

Removed the last update something is wrong on my device will check.

baybutcher27 said:
Removed the last update something is wrong on my device will check.
Click to expand...
Click to collapse
Working fine here

goalando said:
Working fine here
Click to expand...
Click to collapse
I tested it over 24h, It may work well but from noting it start to produce bugs. maybe a none kernel related i looking
Making a new build remove a wrong entry to see if help.

Kernel update! BHB27-Kernel-V1.0.3
Before install it, uninstall or clean data of any kernel control app you're using.
Download-Kernel
Changelog-Kernel
Change:
====================
09-22-2015
====================
* V.1.0.3
* Remove incompatibility (CPU optimizations flags and Remove per-cpu workqueue) To find a bug will add improves latter.
Test and let me know... I test this, i remove some improves that may cause bugs, is more to stock as possible, but still have, CPU gov, KSM and TCP govs.
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.

Gpu governor > simple ondemand = freeze and reboot. In v.1.0.3
Edit for requests:
1) add mako hotplug
2) GPU frequency minimum to 27MHz
3) volume and microfone gain
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1

Thanks for all your hard work man

RSDamasceno said:
Gpu governor > simple ondemand = freeze and reboot. In v.1.0.3
Edit for requests:
1) add mako hotplug
2) GPU frequency minimum to 27Hz
3) volume and microfone gain
----
Moto Maxx - XT1225
Xposed NXRom 5.1.1
Click to expand...
Click to collapse
Yes it does, did not have time to go over gpu_gov, I recommend to leave as default msn-adreno-tz. Will remove or fix simple ondemand. :good:

Implemented, now I'm testing new features that user's ask... No new hotplug, mako is not ported right now to MAXX, will try to port other improved hot plug or improve msm
Voltage, sound, FS and screen control. FS can only be change with some kernel app (like trickster mod ).
All is good bu twill test longer to make shore.

Related

WildKernel
for LG Optimus G Pro (E98x & F240x Variants)
Go check out Tame! It goes great with this and it handles OTA updates for this kernel.
Unrelated: Is your Gpro camera buggy?
This is a Linux based (3.4.0) Kernel which is maintained by me, and kept inline with the CyanogenMod Kernel so this is compatible with ALL the latest 5.x AOSP Roms (unless otherwise stated in the ROM).
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Feeling like a critic? Leave a review!
Link broken? Try one of the mirrors, Still a no go? Goto my signature and click the file backups link, then navigate to what you were looking for.
So what is this mysterious zip file doing to my device?
Code:
[B]Note: Your phone must already have a booting ROM installed for WildKernel to work. If you find yourself not booting
after installing WildKernel, reinstall your ROM zip then reboot. Ensure that it boots now, then try installing WildKernel again.
If it fails a second time, yell at me below in this thread preferably with a log of some sort attached.[/B]
1. Extracts boot partition and de-lokifies it for manipulation.
2. Takes our new file and decompiles a now readable boot image to utilize its ramdisk, the one currently installed in your ROM
3. Then, it fuses my kernel image with your ROM's ramdisk to form a new boot image
4. Our new boot image is loki-fied and flashed to your boot partition
Assuming that these 4 steps were successful, you can now show your new phone off to your friends.
{
"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"
}
There is NO need to clear caches, kernel installer handles everything. Just flash and reboot.
E98x Build #5 Reloaded: Primary | Mirrors: #1 / #2
F240x Build #5 Reloaded #2: Primary | Mirrors: #1 / #2
All Releases: AFH | TRU Mirrors
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
SultanXDA
mcaserg
TeamDS
faux123
Tamcore
cretin45
showp1984
RomanBB
Mito Takatori
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
What Do I Pack?
Tame (duhh)
CM 12.1 10/2/16 & Minimal Gapps 5.1
Ondemand on 1st core @ 384-1782mhz
Performance on other cores @ 1458mhz
CFQ Scheduler
4th core disabled
Stock Voltage
GPU: 320mhz
Did you read the announcement? (page header)
​
XDA:DevDB Information
WildKernel for the LG Optimus G Pro (E98x & F240x Devices), Kernel for the LG Optimus G Pro
Contributors
Emmanuel U
Source Code: https://github.com/EmmanuelU/wild_kernel_lge_gproj/
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Build #5
Stable Release Date: 2015-10-28
Created 2015-04-01
Last Updated 2015-11-07

Changelog:
Code:
[B]November 7, 2015 - Build #5 Reloaded #2[/B]
1. Fixed blackouts for [B]F240x[/B] (my changes weren't previously applied in last update)
[B]October 28, 2015 - Build #5 Reloaded[/B]
1. Reverted CM's color adjustment code that created the possibility for blackouts, this is a workaround. There is still a problem with mdp but this will prevent any more blackouts.
[B]September 23, 2015 - Build #5[/B]
1. Mpdecision re-enabled (recommended), intelliplug still available just disabled by default
2. Support for customizing HBLN's pattern style
3. Updates from CM Upstream
4. Misc memory patches
5. Interactive governor updated from upstream
[B]August 16, 2015 - Build #4[/B]
1. Implement DoubleTap2Wake and Sweep2Wake
2. Improve lge_touch_core logic for wake features
[B]June 21, 2015 - Build #3[/B]
1. Touch Boost updates and revamps
2. Added Governors: Adaptive, Intellidemand, Lionheart, SmartassV2 and Wheatley
3. Patch and tweak govenors
4. Added TCP Congestion controllers: Westwood and Veno
5. Made CUBIC the default TCP Congestion Controller
6. Disabled mpdecision
7. Added [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/03fd621788eb48a77e88cff990048687ca6e877d"]Intelliplug[/URL]
8. Misc patches for my drivers
[B]April 19, 2015 - Build #2 Reloaded[/B]
1. Synchronized F240x Kernel to include FauxSound (oops heh should've already been added)
2. 5.1 Bootloop issues seem to have been fixed as reported by my testers, but let me know. Thanks SultanXDA for the pointer.
[B]April 16, 2015 - Build #2[/B]
1. Support for the LG F240x Variants
2. Thermald Re-enabled, but [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/46ee361bc0023a75a47381ec0cfdc9b341ce6e7c"]limited[/URL].
3. Created the ability to [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/dc3f14b3c5a234fe8d83f93bb8a551efe21e5c45"]disable secondary CPUs[/URL], to save power.
4. Added ability to use USB Fast Charge
5. Added FauxSound Support
6. Increased regular charge current max to 1500mA for faster regular charging too
7. [STRIKE]Lollipop 5.1.x is now supported[/STRIKE]
[B]April 1, 2015 - Build #1[/B]
1. Initial Release - Official CM Kernel
2. Home Button: Added Support for Forcing Notification Pulse Intervals
3. Home Button: Added Support for Forcing Notification Pulse Blink Colors
4. Ondemand & Interactive patches
5. Input Boost Driver by SultanXDA
6. My [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/42e759fda2d4643334452ddc6866926e510f29a3"]Retain Cpufreq driver[/URL]
7. Thermald HAL disabled, [URL="https://github.com/EmmanuelU/wild_kernel_lge_gproj/commit/1dee7142d398677aa6814d454f1619ebd9244970"]here's why[/URL].
8. Disabled some unneeded debugging
9. ROW patches
10. Voltage Control Support
11. 2.1ghz support (overclock with discretion, no device is built the same)
Things You Should Know:
This kernel supports overclocking of up to 2.1ghz, however don't report instability as no 2 devices are built equal. If you feel the need to overclock, experiment with what your device can handle.
Automatically Disable HW Overlays:
As you know, our ROMs currently have graphical issues caused by our MDP drivers and need HW Overlays disabled as a workaround. Well you can add this to a Run At Boot Script in my app Tame (or your own script, ran with su) to save yourself having to manually re-enable it.
Code:
service call SurfaceFlinger 1008 i32 1
Every custom feature in this kernel can be easily configured with Tame (highly recommended), however here is how you can configure things using your favorite ADB/Terminal shell if you're feeling independent.
CPU Control:
Code:
You should be able to understand what I'm doing here. replace cpu0 with cpu[1-3] to change your secondary cores.
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1728000"> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Voltage Control:
Code:
Overvolt CPU by 25mV
echo "+25000" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Undervolt CPU by 25mV
echo "-25000" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Note:
Values are complimentary. so to undo voltage changes, reboot or input the opposite of what you had previously input.
Home Button Light Notification Control:
Code:
Force all notifications to pulse red (you must input a RGB value)
echo "FFFFFF" > /sys/class/leds/R/device/led_blink_rgb
Force all notifications to pulse for 300 milliseconds, every 1.5 seconds
echo "300 1500" > /sys/class/leds/R/device/led_blink_interval
Input Boost Control:
Code:
Dynamically raise minimum frequency for touch events (in 3 levels).
Enable
echo 1 > /sys/kernel/cpu_input_boost/enabled
Set the boost levels for CPU #1-3 (CPU #1 is the highest level)
echo "1134000 918000 702000" > /sys/kernel/cpu_input_boost/boost_freqs
GPU Control:
Code:
View available GPU clock frequencies
cat /sys/class/kgsl/kgsl-3d0/gpu_available_frequencies
Set max GPU Clock to 400mhz
echo 400000000 > /sys/class/kgsl/kgsl-3d0/max_gpuclk
USB Fast Charge:
Code:
This only effects non-wall chargers, wall charging is already allowed max current (1500mA)
Enable maximum speed charging (1500mA under best conditions)
echo 1 > /sys/kernel/fast_charge/force_fast_charge
Limit USB charging to 1300mA
echo 2 > /sys/kernel/fast_charge/force_fast_charge
echo 1300 > /sys/kernel/fast_charge/fast_charge_level
CPU Toggler:
Code:
I recommend disabling CPUs in greatest to least order (4-1) to avoid any possible issues, so disable your 4th core before your 3rd etc. Disabling cores can save power, but also be wary that disabling too many with to little power may slow your device down to a point of it being detrimental.
Disable 4th CPU
echo 0 > /sys/devices/system/cpu/cpu3/enabled
Disable 3rd CPU
echo 0 > /sys/devices/system/cpu/cpu2/enabled
Custom Wake Triggers:
Code:
Note: These features prevent your touchscreen from fully entering sleep, which can consume (slightly noticeable) battery
DoubleTap2Wake - Double tap the center of your screen
echo 1 > /sys/android_touch/doubletap2wake
Sweep2Wake - Sweep your finger from the left part of the screen to the right
echo 1 > /sys/android_touch/sweep2wake
TCP Control:
Code:
Note: It's a common misconception that certain protocols are the best for everyone. While this has a small truth, it ultimately depends on your connection speeds and distance. I would disregard what you may have read about reviews of various protocols, and experiment to see which one works the best for you.
See available protocols
sysctl net.ipv4.tcp_available_congestion_control
Change protocol to westwood
sysctl -w net.ipv4.tcp_congestion_control=westwood

How to make your Developer's Day
Bug Reporting:
Things marked in bold are things you should mention in a bug report to any developer, to make our lives easier.
To be clear as I'm writing this, almost all bugs you encounter are unrelated to your kernel. Most issues stem from the ROM/app/mod you're running, however on the rare occasion, I may be at fault
Well first off, let's narrow down the bug. Assuming your phone rebooted at some point, what caused your phone to reboot? Assuming you're running the latest version of my kernel, did your phone reboot when you were using it, or did you notice it reboot by itself when you weren't using.
Were you overlocking or playing a game? - IF SO stop yourself right here. This is your fault haha I win, otherwise keep going down.
Okay, can you reproduce this reboot? If so, this is a major giveaway that it is indeed an issue.
Reproducing your bug, to capture:
So now I'm gonna need 2 files off your device. Note, you need ADB drivers installed on your computer (google it), and your device plugged in.
First: Plug your device into your computer, to prepare to capture your error.
2nd: Logcat.
Once device is plugged, run:
Code:
adb logcat > logcat.txt
While this is running, reproduce your bug. If your phone doesn't reboot, this is probably not a kernel issue, but reboot yourself and keep going anyway.
Next we will retrieve your KMSG, once phone has rebooted run
Code:
adb pull /proc/last_kmsg kmsg.txt
Note: above will retrieve kernel logs right up until your phone powers off, from the LAST session. Battery pulling, or rebooting twice will overwrite this log and make it irrelevant.
You will now have 2 files logcat.txt and kmsg.txt. Attach em to a Pastebin or attach them to your post.
moe coming soon​

Will there be any release in future for Korean versions?

asingha94 said:
Will there be any release in future for Korean versions?
Click to expand...
Click to collapse
most likely yes, but for now I'm sticking with my current device only through beta stages.

Emmanuel U said:
most likely yes, but for now I'm sticking with my current device only through beta stages.
Click to expand...
Click to collapse
Thanx & good luck..

Does this work with android 5.1?

warthog1997 said:
Does this work with android 5.1?
Click to expand...
Click to collapse
Wow that was quick, I didn't even notice there was a 5.1 ROM available for this device. While the kernel most likely won't require any changes on 5.1, the kernel installer will fail when trying 5.1 because it's only set to install on 5.0.x versions.

Awesome!
Nice build dude. Rock solid on ressurection remix 5.3.8 thx to @Alezzander_ . Its first OC capable kernel since android 4.3 time (that rus mcaserg was a real genius too bad he abandoned this phone)
Maybe you two can combine your intelligence and give us something unseen on g pro scene @Snepsts
Didnt checked my pvt but i need +20 mV to get 2GHz stable (on default instant reboot)
And btw faux sound would be nice Thx dev!

Links updated.

Emmanuel U said:
Links updated.
Click to expand...
Click to collapse
Awesome! Thanks for this @Emmanuel U.. I could include it in BlissPop if you wouldn't have a problem with that (with credits to you of course).. It's running so smooth on my latest version..Do you have plans for underclocking?

nerdyblonde said:
Awesome! Thanks for this @Emmanuel U.. I could include it in BlissPop if you wouldn't have a problem with that (with credits to you of course).. It's running so smooth on my latest version..Do you have plans for underclocking?
Click to expand...
Click to collapse
I used to believe that this would be beneficial for the primary core, but after gathering knowledge, now I believe that adding lower clock steps on phones like these (~384mhz) has more harm than good. If the phone is willing to idle, it'll suspend into low power otherwise we shouldnt allow it to scale to such low freqs as it won't be getting any work done at those freqs. I'm working on ideas for battery consumption (I do already get about 7.5 SOT), but I cant see myself adding lower freq steps. Feel free the lower your CPU voltage though.
Oh yea feel free to include this kernel in your ROMs, and this goes for any developer wishing to do the same

Emmanuel U said:
I used to believe that this would be beneficial for the primary core, but after gathering knowledge, now I believe that adding lower clock steps on phones like these (~384mhz) has more harm than good. If the phone is willing to idle, it'll suspend into low power otherwise we shouldnt allow it to scale to such low freqs as it won't be getting any work done at those freqs. I'm working on ideas for battery consumption (I do already get about 7.5 SOT), but I cant see myself adding lower freq steps. Feel free the lower your CPU voltage though.
Click to expand...
Click to collapse
Wow... Is that with a stock battery or the big Zero Lemon batteries?

nerdyblonde said:
Wow... Is that with a stock battery or the big Zero Lemon batteries?
Click to expand...
Click to collapse
Stock, but my phone in general heavily modified though because coming from a kid who's had dual cores all his life, you grow accustomed to cutting down on performance.

Emmanuel U said:
Stock, but my phone in general heavily modified though because coming from a kid who's had dual cores all his life, you grow accustomed to cutting down on performance.
Click to expand...
Click to collapse
Hi. What about quick charge and gpu overclocking?
Sent from my LG-E980 using XDA Free mobile app

please have mercy on the F240k/L users . we barely see any kernel for us

Alezzander_ said:
Hi. What about quick charge and gpu overclocking?
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
Most likely, just give it time.
ecrum said:
please have mercy on the F240k/L users . we barely see any kernel for us
Click to expand...
Click to collapse
Emmanuel U said:
most likely yes, but for now I'm sticking with my current device only through beta stages.
Click to expand...
Click to collapse
^^

Emmanuel U said:
Most likely, just give it time.
^^
Click to expand...
Click to collapse
can i flash this on stock kitkat rom?

[email protected] said:
can i flash this on stock kitkat rom?
Click to expand...
Click to collapse
No, it's a CM kernel

nerdyblonde said:
No, it's a CM kernel
Click to expand...
Click to collapse
for lollipop only?

{
"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"
}
This is a port of Optimus Kernel by Flashhhh for Titan​
Make sure to thank him - Here
I present to you my own kernel which has been built with many optimizations and tweaks. This kernel will work ONLY on Marshmallow roms(Not for stock roms) only.The main aim is to provide a stable kernel with optimizations.
I hope you all will like it
Custom Kernel Features:
- Updated to latest cm-13.0 Sources
- Compiled With Custom UBER 5.2.1 Toolchain
- Compiled With -O3 & Graphite Flags
- Additional many optimization flags
- Compiled With Cortex A7 Tweaks
- ARM v7 Optimizations
- Intelliplug
- Mpdecision hotplug driver(Using custom powerhal by CM)
- GPU underclock/overclock(Min:100 MHz & Max:533 MHz)
- Add dev/frandom
- Added Support for Kernel Neon Mode
- Enabled Pipe Flag
- Adreno Idler Algorithm
- PowerSuspend Driver v1.5
- Add BioShock/DanceDance Govs
- Added SmartMax/LionHeart Govs
- LCD Kcal Control by Savoca
- Faux's Sound Control
- Optimized ARM RWSEM Algorithm
- Optimized Square Root Algorithm
- LMK tweaks
- block: disable add_random
- Enable unaligned capability for ARM
- CpuFreq and CpuBoost Optimizations
- Disabled Gentle Fair Sleepers
- Enabled Many TCP Congestions
- Added SIO,VR & ZEN IO Scheduler
- Sched & Mutex Tweaks
- Pushed Read Ahead value to 512
- Use your android device as USB Keyboard/Mouse
- Enabled FSync by default
- Optimized Slub
- VFP HardFloat
- Power Efficient WorkQueues
- Reclaimed RAM from loggers
- Power Efficient WorkQueues
- Kexec patched
- Many more things (Check Github)
Disclaimer:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this KERNEL
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.​
Pls Read This before flashing:
You need ROM's default kernel before flashing this, as this kernel makes use of AnyKernel 2 by @osm0sis. Make sure you have it otherwise clean flash the kernel with the rom to avoid any issues.(At least dirty flash rom+kernel) Credits to @attack11 for some part of install script.Read FAQ's and changelogs in 2nd post. THIS KERNEL COMES FINE TUNED OUT OF THE BOX. Some useful battery saving tipshttp://forum.xda-developers.com/showpost.php?p=64850959&postcount=198
DOWNLOADS:
Grab it here
#ROM infos on the 4th post, be sure to check it
How to Flash:
1. Download the kernel and place it into your phone storage
2. Reboot into recovery
3. Install the kernel
4. (optional) Wipe Dalvik Cache and Cache partitions
5. Reboot and enjoy!​
PLS DON'T MIRROR THE LINKS
Recommended app:
Synapse or Kernel Adiutor
Flash UKM.zip from the below link: (credits to @apb_axel)
http://forum.xda-developers.com/android/software/zip-synapse-script-universal-kernel-t2736986
And then install synapse from play store.
I would like to say thanks to @flashhhh for allowing me to port the kernel. Also a big thanks to @faux123 @YoshiShaPow @fermasia @Alberto97 @TeamMex @Quasar @Mazda @FabioSan @Blechdose @neobuddy89 @RenderBroken @savoca @deadman96385 @pinkflozd @alin.p @Cl3Kener @Shivam Kuchhal @cust0mworx for the awesome graphics and CYANOGENMOD TEAM
and MANY MORE...
XDA:DevDB Information
Optimised CM and Viper Kernel for Titan, Kernel for the Moto G 2014
Contributors
Vatsal
Source Code: https://github.com/koradiavatsal/Viper-kernel
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v6
Stable Release Date: 2016-01-15
Created 2015-12-02
Last Updated 2016-01-17

FAQ
F.A.Q. - Read this before complaining!
1. My phone exploded, HELP!
A: I don't answer to problems without a log. The log file is in /proc/last_kmsg. Paste it on hastebin.com and link it on your post. Logcats are useless for Kernel purposes, don't bother posting them.
2. This kernel works on Y or X rom?
A: Works on all CM13 based roms. Not for stock roms!!
3. OMG BATTERY SUCKZ, ITZ DEAD IN 45 MINUTES, HELP!
A: As you can imagine I don't build kernels to decrease battery life. All the battery life problems come from your apps, either Facebook, or Maps, or some Location Service being enabled etc etc. Check your damn wakelocks and fix them, the kernel is not responsible for them.
4. How do I flash this?
A: Read the OP, theres a reason why I added instructions on it.
5. What is a data loss? Did I just had one?
A: Data loss is simply having the connection cut for X periods of time, usually few seconds. Grey bars means the device is not connected to Google services for some weird reason, but you'll still have internet connection.
6. OP is arrogant, I'm gonna call the Internet Police?
A: Deal with it.[/QUOTE]

Info
Many thanks to showp1984 for this info
What is msm_mpdecision?
100% kernel based multi core decision! (should cpu1/2/3 be online or not?)
This is a special version modded by neobuddy Plus the idle frequency and some load thresholds have been adjusted by me.
Some Configuration:
startdelay = time until mpdecision starts doing it's magic (20000)
delay = time between checks (130)
pause = if something else plugs in the cpu, fall asleep for 10000ms (10 secs)
scroff_single_core = if the screen is off, don't plug in cpu1/2/3. Additionally: Unplug all cpus except cpu0 when screen is turned off (1)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
min_cpus = min cpus to be online, cannot be < 1. Default: 1
max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
idle_freq = a value against that will be checked if a core +/- is requested. (600 MHz)
mpdecision's input event boost, aka project butter
This will boost your min cpu speed if you touch the screen or press a button and gives you full control.
In those events the min cpu freq will be risen to a predefined value on every online cpu. This boosts overall reaction times and smoothness a lot. (works similar to the qcom mpdecision binary)

So here's the surprise
Hello folks,
I am using my own optimised builds since initial phase of CM13. Rom and kernel are both build with Uber 5.2.1 and few more optimisations on the kernel (It's same like in the first post). The Uber Toolchain developer said due to new neon optimisations in Uber toolchains, the battery life has increased by 25%. Well using since a long time, I almost get 6hrs+ SOT(Ofcourse will vary with you) and a mindblowing performance. So I am going to provide weekly Uber CM13 builds with optimisations(It is somewhat close to pf-cm by Diamond Bond). The people interested, could use it , It will stay really close to CM and few picks here and there. I would really appreciate feedbacks I am using the build posted and it's really rock stable.
Download :-
All optimised buildshttps://www.androidfilehost.com/?w=files&flid=44644
Installation :-
A clean wipe is mandatory.
Wipe cache,dalvik cache, system, data
Flash the zip
Flash gapps ( I use slim zero gapps)
Reboot, Enjoy!
FAQ:-
Differences between UBERTC and other Toolchains
Changelog for the 1st December Toolchain updates
Regards

Awesome work brother
Vat Bro
This is cool.
Good going
Keep it UP

Check #4th post for the Optimised cm13 builds, Really didn't feel like making a new thread..

Is it fully functional, Like Working mobile data , camera Themes Etc... Is there any way you can provide delta updates to ur rom instead of downloading the whole file.. I'm currently using cm 13 which has no Major issues as of now , so is this rom(dec 2 build) Recommend or should I wait for future builds ?
Thanks IA ��

james11705 said:
Is it fully functional, Like Working mobile data , camera Themes Etc... Is there any way you can provide delta updates to ur rom instead of downloading the whole file.. I'm currently using cm 13 which has no Major issues as of now , so is this rom(dec 2 build) Recommend or should I wait for future builds ?
Thanks IA ��
Click to expand...
Click to collapse
Everything working same as CM, No OTA/delta updates sorry..

Vatsal said:
Everything working same as CM, No OTA/delta updates sorry..
Click to expand...
Click to collapse
Thanks for the quick response , I'll try it out and let you know .., . And thanks for the rom ��

I can't install your kernel over CM's stock kernel. there's an error with the updater-script. I am using the 02/12 CM13 build, how can I help?
(zip placed on the root of internal storage)

Vatsal said:
Everything working same as CM, No OTA/delta updates sorry..
Click to expand...
Click to collapse
Does that mean XT1068 users with one sim cannot use this?
Sent from my Moto G 2014 using Tapatalk

Vidhanth said:
Does that mean XT1068 users with one sim cannot use this?
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
I guess thats fixed in cm as well

Vatsal said:
I guess thats fixed in cm as well
Click to expand...
Click to collapse
Sweet. Have you tried it though? Cuz I can't risk 310 MB lol
Sent from my Moto G 2014 using Tapatalk

Vidhanth said:
Sweet. Have you tried it though? Cuz I can't risk 310 MB lol
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
I have msim

mpeL said:
I can't install your kernel over CM's stock kernel. there's an error with the updater-script. I am using the 02/12 CM13 build, how can I help?
(zip placed on the root of internal storage)
Click to expand...
Click to collapse
Installs really fine here, can someone else confirm the issue?

Vatsal said:
I have msim
Click to expand...
Click to collapse
Thanks man. I'll try it asap. I always wanted to be on 6.0 but the battery life held me back. But now that u have said its increased by 25%, I'll have to try it
Sent from my Moto G 2014 using Tapatalk

Vatsal said:
Installs really fine here, can someone else confirm the issue?
Click to expand...
Click to collapse
Same here , I tried flashing this Kernel over ur rom(didnt know it already had this kernel) , I tried mounting n unmounting system, still got error updating binary...

james11705 said:
Same here , I tried flashing this Kernel over ur rom(didnt know it already had this kernel) , I tried mounting n unmounting system, still got error updating binary...
Click to expand...
Click to collapse
Yes rom has the same kernel inbuilt. I'll reupload kernel.
EDIT : Uploaded Download
Please test this and tell me

Vatsal said:
Yes rom has the same kernel inbuilt. I'll reupload kernel.
EDIT : Uploaded Download
Please test this and tell me
Click to expand...
Click to collapse
Still the same error, tried it on crdroid 6.0 also .. Other than the kernel, the rom is awesome, better than cm 13 official in performance n also is bAttery Friendly ?

Some amazing stats with quiet heavy use
Sent from my Moto G 2014 using Tapatalk

{
"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"
}
WARNING :
This kernel is for OnePlus 5 (cheeseburger)
Code:
You will NOT void your warranty after flashing this kernel.
Be sure to make all necessary backups first before processing to installation.
I'am not responsible of any damage caused to your device or data lost after flashing this kernel.
Of course, these are only basic warnings ! but generally you'll not get any problem :)[/COLOR][/FONT]
Some reading..
Welcome to SimpleGX kernel ! a kernel that aims for simplicity, stability, better performance, smoothness and battery life over a pure stock kernel.
This kernel is designed for people who are (like me) bored to flash kernels which integrate tons of unneeded things.
Main goals of it is to stay MUCH closer to stock than every kernels shared here and almost not to be a “custom kernel” on its own. So beware, no exotic stuffs here !
No need for any third app or whatever to control this kernel. Just "flash-n-joy" ! this is how I always liked thing.
Keep in mind that this kernel has been designed for my daily use first.
I would like to personally thanks @Lord Boeffla for his precious help to build my first OP5 kernel ! without him, this kernel won’t be there ! so please consider it.
As always, I'm enjoying sharing my contribution here on XDA for free, which taking me a lot of (my free) time to test before releasing. So, if you can offer me a little beer, it will be really appreciated!
This kernel must be only flashed over an official OnePlus 5 OxygenOS (OOS) ROM !
Feel free to include my kernel to your ROMs / threads but please don't forget to inform/ask first via PM and credit me properly in your original thread. It's always appreciated.
​
★ WHAT TO EXPECT ★ :​
(over a pure stock kernel) :
Better battery life
Overall better performance
Trying to include only efficient (but definitely no experimental) tweaks
Stay as close as possible from pure stock source
★ FEATURES (up-to-date) ★ :​
Base :
Always directly based from latest available "android_kernel_oneplus_msm8998" Android 7.1.1 source from OxygenOS / OnePlus 5 (for clean work)
Compiled with stock Google (4.9.x / aarch64-linux-android) toolchain (for best stability)
Featuring Anykenel2 (for all ramdisk compatibility)
Stock Linux 4.4.21
Main :
USB fast charge support (disabled by default)
Kernel logger disabled
Disabled adaptive LowMemoryKiller
Minimum backlight level control support (stock value by default)
Wakelocks control support (all wakelocks disabled by default)
Several fixes/optimizations patches for stock cpufreq_interactive governor
MAPLE I/O scheduler added (and set as default)
Completely optimized stock 'cfq' I/O scheduler
Xbox controller (and other USB pads) support
All TCP congestion control modules activated with Westwood currently as default
Removed verify and forced encryption + patched SafetyNet flags to pass CTS
Wlan module from official OOS source
Some miscellaneous tweaks, fix, patches and security patches to improve overall smoothness and battery life experience
Various tweaks :
Full changes to be discovered directly in my Github source below
Features that will NEVER be included in this kernel :
adding any other governor (than those stock)
root/busybox auto-installation
CPU/GPU overclocking/undervolting
KCAL
adreno idler
state_notifier
any upgrade of Linux kernel
dual-boot
etc
★ PREREQUISITE ★ :​
An unlocked Bootloader
An Android Nougat firmware (based on OxygenOS)
A custom recovery (TWRP recommanded), to flash the kernel
Optional : to control some kernel tweaks, you can install Kernel Adiutor)
★ SOURCE (up-to-date) ★ :​
Github >> SimpleGX.
★ INSTALLATION PROCEDURE ★ :​
Backup everything you need (internal & external)
Unlock your bootloader
Flash your favorite TWRP recovery (official or unofficial)
Reboot to TWRP
Wipe system/cache/dalvik partitions
Flash your full usual ROM/firmware
Flash SimpleGX kernel
Flash root (Magisk or SuperSU)
Reboot and enjoy !
★ FAQ ★ :​
How can I update my SimpleGX kernel version ?
Follow THESE steps.
How can I go back to stock kernel ?
Just flash back your full usual rom back.
Is there a LineageOS (LOS) version of you kernel ?
There was, but it has been discontinued. HERE is the old thread.
How to recover excellent battery life ?
Check my personal tips HERE.
★ LATEST VERSION ★
★ ARCHIVES ★
/!\ CHECK MD5 BEFORE FLASHING IS ALWAYS HIGHLY RECOMMENDED /!\
/!\ PLEASE DO NOT MIRROR MY DOWNLOADS /!\​
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read at least completely this first post before asking any question.
If you enjoy this kernel, don't forget to rate this thread
stars, and clicking the 'thanks' button (right below). It's always appreciated to keep this thread maintained ​
LIKE MY WORK ?
OFFER ME A
:good::highfive::good:​​

Changelog
★ CHANGELOG ★ :​
02.11.2017 : v1.18 released.
Synchronize codes for OxygenOS 4.5.14
23.10.2017 : v1.17 released.
Removes Spectrum support
Anykernel2: updated to latest version
19.10.2017 : v1.16 released.
Add Spectrum support (please read post #5 for all informations you need to know).
17.10.2017 : v1.15 released.
Re-included all queue work on power efficient wq patches (for overall better deep sleep).
Brings back minimum backlight to stock value (user may still set its favorite value).
09.10.2017 : v1.14 released.
Re-include (CVE-2017-1000251) security patch for Bluetooth BlueBorne attack (thx @nathanchance for the advice)
09.10.2017 : v1.13 released.
Synchronize codes for OxygenOS 4.5.12
Revert (CVE-2017-1000251) now useless security patch for Bluetooth (already included from OxygenOS 4.5.12 security patch)
03.10.2017 : v1.12 released.
Synchronize codes for OxygenOS 4.5.11
21.09.2017 : v1.11 released.
init.simplegx.rc: add (and disable) missing "wcnss_filter_lock" wakelock
21.09.2017 : v1.10 released.
Add (CVE-2017-1000251) security patch for Bluetooth BlueBorne attack
20.09.2017 : v1.09 released.
Added two cpufreq_conservative (fixes/optimizations) patches
Added wakelocks control back and disable them by default (for better battery life)
18.09.2017 : v1.08 released.
Anykernel2: updated to latest version
07.09.2017 : v1.07 released.
Removed all queue work on power efficient wq patches from franciscofranco. (Less experimental, more close to stock now).
Added OnePlus5 minimum backlight fix (current value has been set to 8 for now).
03.09.2017 : v1.06 released.
Added two minor (and safe) patches about performance and battery.
29.08.2017 : v1.05 released.
Synchronize codes for OxygenOS 4.5.10
23.08.2017 : v1.04 released.
USB fast charge support (disabled by default, use Kernel Adiutor to enable it if you need)
block: add MAPLE I/O scheduler and set it as default
cpufreq: interactive: Remove the jump_to_max hack
cpufreq_interactive: remove boost functionality
Anykernel2: finally fixed all available ramdisk simplegx tweaks
Anykernel2: updated to latest version
Anykernel2: new styling retouch during kernel flashing
18.08.2017 : v1.03 released.
Removed wakelocks control stuff.
I wasn't happy with it (not to say useless) and anyway it needed an app to control this, so...
16.08.2017 : v1.02 released.
Much better deep sleep.
15.08.2017 : v1.01 released.
Completely rebuilded from OP5 source from zero. I decided to now include only few recognized commits (many previous commits has been removed).
Wakelocks control available (ON by default, but may be turned OFF via Kernel Adiutor for exemple).
12.08.2017 : v1.00 released.
Initial release (check actual features).

Thanks & greetings
★ THANKS & GREETINGS ★ :​
(by alphabetic order)
Lord Boeffla
osm0sis
ZaneZam
. . . and of course to all talented devs credited in my commits!

Donations
★ DONATIONS ★ :​
Many thanks @dr.zook :good:
Many thanks @gillboyzz :good:
Thank you to support my work ! :highfive:

Spectrum explanation
This kernel is now NO MORE compatible with Spectrum app (author: @frap129)
Obsolete details (for reference) :
Since all spectrum profiles are all different between switching from kernels, here is my vision of things : instead of spending time to fine tune interactive gov (etc) in the purposed 4 scenarios offering typically what other kernels may do, I still wanted want to keep simple but efficiency (and not dangerous) settings/tweaks that me be useful for everybody.
Here is all you need to know, what SimpleGX kernel may offer, and the main differences between each profiles.
Full view of the currently integrated Spectrum file (for advanced users) :
Code:
# Balance (default profile)
on property:persist.spectrum.profile=0
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor interactive
write /sys/module/cpu_boost/parameters/input_boost_ms 100
write /sys/class/kgsl/kgsl-3d0/devfreq/governor msm-adreno-tz
write /sys/class/leds/lcd-backlight/max_brightness 255
# Performance
on property:persist.spectrum.profile=1
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor performance
write /sys/module/cpu_boost/parameters/input_boost_ms 1500
write /sys/class/kgsl/kgsl-3d0/devfreq/governor msm-adreno-tz
write /sys/class/leds/lcd-backlight/max_brightness 255
# Battery
on property:persist.spectrum.profile=2
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor conservative
write /sys/module/cpu_boost/parameters/input_boost_ms 100
write /sys/class/kgsl/kgsl-3d0/devfreq/governor powersave
write /sys/class/leds/lcd-backlight/max_brightness 100
# Gaming
on property:persist.spectrum.profile=3
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor performance
write /sys/module/cpu_boost/parameters/input_boost_ms 1500
write /sys/class/kgsl/kgsl-3d0/devfreq/governor performance
write /sys/class/leds/lcd-backlight/max_brightness 255
BALANCE profile :
This is the stock default profile after flashing kernel. It will be applied as default if you don’t want to switch to another profile. Balance profile will benefit from all you guys know already about this kernel for it’s great stock experience and stock values, looking for best of performance and battery life for everyday use.​
PERFORMANCE profile :
Performance profile is looking those who only cares about performance at the cost of battery life. Excellent for UI and overall top tier performance during apps use. I definitely not recommended to let this profile 24/7. Please do not report any bad battery experience while using this profile.​
BATTERY profile :
Battery profile is probably the most only interesting profile (at my eyes). Extremely useful in some situations, it will provide you best battery life without scarifying too much performance and keep your device usable everyday. Very useful for days at work or when you reach really low percentages, this profile will probably save your day. Note that also, the min screen brightness has been intentionally lowered to 100 (instead of 255), to reduce consummation.​
GAMING profile :
This profile is completely based on performance profile, at the exception of GPU governor changed to performance. Only useful for gaining some extra FPS’s during your gaming sessions. I definitely not recommended to let this profile 24/7. Please do not report any bad battery experience while using this profile.​

Welcome in the Kernel OP5 family mate, i'm also a french user (Nice)
Thanks

Can't wait to try this one out..Thanks mate.

Already flash this kernel~

Here we go
Enviado desde mi ONEPLUS A5000 mediante Tapatalk

thanks for the new kernel which is a good alternative for all users who just used the stock kernel so far Fortunately, I didn't post an update yet for the rom so I can still implement you kernel to the aroma installer menu.
Good luck!

Pho3nX said:
i'm also a french user (Nice)
Click to expand...
Click to collapse
Welcome to the club ! :highfive::good:
xXx said:
thanks for the new kernel which is a good alternative for all users who just used the stock kernel so far Fortunately, I didn't post an update yet for the rom so I can still implement you kernel to the aroma installer menu.
Good luck!
Click to expand...
Click to collapse
Thank you very much for that, appreciated :good::highfive:
You are my rom base since the beginning of my OP5, so thank you for your hard work! :good:
Cheers'

Just flashed your kernel mate
Thanks for your work so far kernel seems smooth like butter

UPDATE
★ CHANGELOG ★ :​
15.08.2017 : v1.01 released.
Completely rebuilded from OP5 source from zero. I decided to now include only few recognized commits (many previous commits has been removed).
Wakelocks control available (ON by default, but may be turned OFF via Kernel Adiutor for exemple).
N-JoYz :good:

Testing... Works fine for now
Few deep sleep: remains awake often
Other things work perfectly, and im testing on Los based

mystique47 said:
Testing... Works fine for now
Few deep sleep: remains awake often
Other things work perfectly, and im testing on Los based
Click to expand...
Click to collapse
Thanks for LOS working confirmation, I didn't know it was compatible :highfive:
I will add it into first post :good:
Concerning deep sleep, it works fine for me, but yeah, there is something to ameliorate a bit (I alrerady have some ideas) but this time I will take time (before releasing next version) to decide which precise things to add :good:

AndroidGX said:
★ CHANGELOG ★ :​
15.08.2017 : v1.01 released.
Completely rebuilded from OP5 source from zero. I decided to now include only few recognized commits (many previous commits has been removed).
Wakelocks control available (ON by default, but may be turned OFF via Kernel Adiutor for exemple).
N-JoYz :good:
Click to expand...
Click to collapse
Was having issues with elementalX and battery drain. Switched to this rom and problem solved. Thanks for the awesome kernel!

AndroidGX said:
Thanks for LOS working confirmation, I didn't know it was compatible :highfive:
I will add it into first post :good:
Concerning deep sleep, it works fine for me, but yeah, there is something to ameliorate a bit (I alrerady have some ideas) but this time I will take time (before releasing next version) to decide which precise things to add :good:
Click to expand...
Click to collapse
like all oos kernels on los roms notification slider don't work and hardware buttons are inverted (can change from options obviously). I haven't find other issues for oos kernels on los

We cannot disable touch boost? Why..
Sorry for bad english :good:

ponkz said:
We cannot disable touch boost? Why..
Sorry for bad english :good:
Click to expand...
Click to collapse
Where do you see it cannot be disabled ? I tried to disable via Kernel Adiutor app and it seems to work without any problem :good:
Anyway, I don't advice to disable touch boost since you will face some slight stutters during some activites (gaming, browsing, etc), stock value is better.

UPDATE
★ CHANGELOG ★ :​
16.08.2017 : v1.02 released.
Much better deep sleep.
Enjoy ! :good:
(@mystique47, this release is for you :highfive

{
"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"
}
Do You Want Lineage16 kernel features? tired of lineage 16 bug and want to use nougat like groovy or oreo like RR? here use my forked lineage16 kernel compiled using latest toolchain alongside with your rom for better performances and more features than rom built-in minimal kernel~
TESTED WORK PROPERLY IN GROOVY AND POSSIBLY OTHER ROM AS WELL
Kernel Feature:
CPU Governor: interactive,conservative,powersave,performance,ondemand,userspace
I/O Scheduler: cfq,bfq,deadline,noop,row,sioplus,maple
TCP Congestion Algorithm : cubic, bic, htcp, reno, westwood
F2FS Support(i am using /data f2fs)
ZSWAP,Z-RAM (lzo,lz4,deflate)
Fsync (Enabled by default)
Software CRC Control (disabled by default)
Gentle Fair Sleepers (enabled by default)
Adreno Idler (enabled by default)
Arch Power (enabled by default)
wq_power_saving (enabled by default)
[*]WireGuard VPN
What is New?:
CPU Governor: blu_active sakura_active
I/O Scheduler: zen,anxiety
few patch for improved performances
Kernel name (obviously xD)
Tested Rom:
GroovyAndroid (Nougat) (Z00T)
Lineage16 (obviously lol)
ResurrectionRemix (Pie) (Z00T)
Patched to get more performances without root
(patch zip included below)
AOSP-Extended
Download:​
CLICK/TAP HERE
FAQ:
Q: Z00L?
A: i only have Z00T,but i did built it for you, if something goes awfull dont blame me and specify what kinda things happen (if possible, with logs too)
Q: If i've install this on my rom, does it will cause same bug that happen under lineage16?
(For example you're using RR-6 or GroovyAndroid 7.0)
A: No, that was rom bug under Pie custom rom we currently have that unfortunately i couldn't fix unless i find it, fix it and test whole things, i build this kernel for my personal uaage
(For example RR-7.0, Lineage16,AOSPExtended V6.0)
Q: I Want this FEATURE
A: sure, i'll think about it and try merge it later if i have time
Q: Help, There is something WRONG
A: send me your log in proc/kmsg or from log apps
Q: What are you gonna add next?
A: More IO, Governor, Patch, Filesystem Fixes, etc.. if i forgot something please remind me
Q: MSM-Thermal was bugged, it keep enabling itself
A: Dont ask me, i dunno why too.. just delete thermal.conf in system/etc/ to disable them FOREVER
Q: Can I Use F2FS?
A: You can, if your rom support it and also our fstab only support /data f2fs, i might modify it to support cache and system too but for me /data was enough, or you could try messing with that~
Q: When you're gonna release kernel updates?
A: As long i have time to do it and there is something i want to merge, since i also use this kernel as daily driver (My Phone was Z00T).
Known Issues:
My Unity Games Freeze after a slight Stutters!
Fix: " I/O Stats" and " add_random" set to 1 if they're 0
Fixed Issues in this kernel:
Z00T Device Now Show Properly "Snapdragon615" "MSM8939"
(Just Try devcheck/aida64/etc if you didnt believe me)
fixed gpu/cpu hwmon error in kernel (causing loop)
Unity Workaround(add_random,I/O stats) for user who didnt install any root solution(example:magisk)
Information:
Linux kernel version: 3.10.108
Based from:Lineage16-unnoffical mg712702 minimal-branch
Compiler Used
GCC Experimental (ARM64) (Aarch64-ELF)
Kernel Source:Here
Note: i am very new at xda, i apologize for this kinda awfull template for thread
Thanks:
mg712702 for maintaining lineage16-Z00L/Z00T
theimpulson for firekernel
osm0sis for anykernel
and lot of people that i couldnt mention here that actually contribute to kernel

Changelogs:
2019-08-30
ICEY-Zephyr 0.1
Initial Builds (Fresh fork from Lineage16)
2019-08-30
ICEY-Zephyr 0.1a
Build Z00T and Z00L Together
Added CPU Governor : blu_active
Added I/O Scheduler : Anxiety, Zen
Merged Some Improvements
2019-08-31
ICEY-Zephyr 0.1b
Builds Using Newer Compiler Linaro-8.3.0
2019-09-02
ICEY-Zephyr 0.1c
Specific Unity-based games issues workaround applied
(by default enable I/O Stats and add_random, if any of this two still 0, please change it to 1)
Show Correct CPU
silenced some Kernel Error log
(this error was caused by bw_hwmon gpu governor)
2019-09-17
ICEY-eXperimentalZephyr 0.2
Switched to latest GCC-Experimental
Added two variant builds:
-XZ (linux-gnu)
-Yata-No-Kagami(bare-metal-elf)
0.2a:
-boot faster, fixes for tcp(ipv4), and other things
(buggy lz4hc disabled, lz4 zram was fine if you want to use this gimmick as you wish)
0.2ab:
-clean up
-migrate to AnyKernel3
2020-05-27
ICEY-S 1.0.0 :
Forked from latest (basically rebase maybe?)
Compiled Using GCC11
2020-05-29
ICEY-S 1.0.1 :
Added back ANXIETY, ZEN
Disabled Governor sakuractive
2020-05-30
ICEY-SC 1.0.1a NO_CC :
Disabled several stuffs, faster but it wasn't recomended
Z00T Only so i could find out what went wrong if someone report any issues with this builds
Planned Updates
Nothing, i am busy~

Patch List
GroovyAndroid (Nougat) :
No need, run perfectly fine
ResurrectionRemix (Pie) :
-tune vm
-disabled zswap,zram
-Unity freeze workaround
Note: this patch mean for Z00T user
userdebug_fixes :
bypass annoying "user" check on certain apps

Does it improve battery life on lineage 16?

joelchris said:
Does it improve battery life on lineage 16?
Click to expand...
Click to collapse
if you install it, and change CPU Governor to blu_active it will save more battery than interactive/ondemand while retaining good performance, it also have "fastlane" mode in governor option to scale faster (good for gaming), i recomend to use it and set min cpu to 200mhz.
You could also try Zen if Maple didnt work really well for you~ other than that,this kernel also have performance improvement than your lineage16 because i fork it and apply various change that will accumulate from now.
if you want a very good battery life Try This Kernel Configuration:
Disable MSM Thermal by deleting/moving every thermal-engine.conf you could find under system/etc/
Set min cpu 200mhz and max 1,1ghz(big),800mhz(little), change governor to blu_active or use powersave for extreme low power usage since it scale very slowly
(Note:not recomended, i rather use blu_active)
Also disable perfd to make sure your system didnt change anything on your CPU settings
if your phone was Z00L variant, 800mhz was better than making your phone goes higher
(higher than this will use more voltage and cause more heat, even thermal lock your phone into maximum 800mhz most of times)
Set CPU core big min 0, max 4, little min 4, max 4
Disable any touchboost if you had any configured
Use Maple>Zen>SIOPlus (try any of this three)
Set GPU Max 400mhz, Target 400mhz, min 200mhz, for extreme battery saving measure change governor from msm-adreno-tz to powersave
Disable Zswap,Zram
Reduce Entrophy Amount to 64/128
(Also your choice to disable or enable add random)
Disable Gentle Fair Sleepers
Enable I/O Stats
(some apps maintain performance and usage by using this especially mobile games that use Unity)
I might add hotplug later for better battery usage and see if that can be merged also work, hotplug function was managing core better (on/off itself) than system especially since our device usually have 4 little core allways online.
(it wont scale automatically, dunno maybe bugged that's why i've said little core min 4 to make sure there is no lose in performance caused by system for using power-efficient little core less than 4)

Where is the kernel source link? Can't find it in first post.

TheImpulson said:
Where is the kernel source link? Can't find it in first post.
Click to expand...
Click to collapse
added, sorry~ its my first time posting a thread and i kinda forgot to mention source.

ReikaRin said:
added, sorry~ its my first time posting a thread and i kinda forgot to mention source.
Click to expand...
Click to collapse
Thanks
That commit history seems to be a mess. Are you trying to get travis set up for kernel repo?

TheImpulson said:
Thanks
That commit history seems to be a mess. Are you trying to get travis set up for kernel repo?
Click to expand...
Click to collapse
i am very sorry, i am doing this on git-web instead of pull and push commit like everyone else did, its really bad right.. and yes, its build using travis instead locally.. currently im pushing new build using linaro-8.3.
Edit: Build pass, everyone can try if they want it

Okay, enjoy 0.1c~ do tell me if you run into problem especially Z00L because i've only test run Z00T.
Note: do read .zip name properly so you didnt flash wrong variant for your phone

For Every Z00T User, i heavily recomend you to flash new 0.1c build for fixing your cpu display and minor kernel error silent

Z00L 0.1c was available now
What Changes Included:
Restored CPU Info
Fix kernel error loop caused by bw_hwmon
(it barely have effect, but why not?)

ReikaRin said:
Z00L 0.1c was available now
What Changes Included:
Restored CPU Info
Fix kernel error loop caused by bw_hwmon
(it barely have effect, but why not?)
Click to expand...
Click to collapse
I try change to bw_hwmon, my phone suddenly restart. I change with kernel adiutor.

What app do you use to tweak kernel? (I'm new)

joelchris said:
What app do you use to tweak kernel? (I'm new)
Click to expand...
Click to collapse
try kernel adiutor from playstore

Z00l?

andy_dch said:
I try change to bw_hwmon, my phone suddenly restart. I change with kernel adiutor.
Click to expand...
Click to collapse
it wasnt mean to be used, i only fixed kernel error that caused by this.. just use msm-adreno-tz or simple-ondemand/performance

joelchris said:
Z00l?
Click to expand...
Click to collapse
Z00L too, just download .zip with Z00L name

joelchris said:
What app do you use to tweak kernel? (I'm new)
Click to expand...
Click to collapse
EX KERNEL, SMARTPACK KERNEL MANAGER (Basically improved Kernel Adiutor made by Smartpack kernel author for smartpack kernel but usable with other kernel as well), LHANTANUM SYSTEM TOOLBOXES, 3C ALL IN ONE

Download link?

Kirisakura-Kernel for the Asus Zenfone 7/Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 7/Pro aka Tequila. The Zenfone line- up internal codenames are derived from alcoholic drinks, last year the Zenfone 6 bore the title Kirin.
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. Instead there is an option called battery saver in the options of your phone.
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.
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.
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 different SKUs of the Zenfone 7/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 the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 12 and intended for use on the latest Asus Stock-Firmware
- compiled with Clang 13.0.1 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.19.2240
- CAF base for the Snapdragon 865/+ (SD865/+) updated to upstream CAF
- Kernel Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 5/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 for full program visibility (needed by CFI)
- fix CFI-Violations found in various subsystems like Asus/device specific 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!
- Flashable via EXKM, FKM or TWRP on a rooted system!
- Anykernel zip is based on the Anykernel3 release from @osm0sis
- disable various debugging configs, that are not needed in a perf build kernel 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
- option to limit max cpu frequency (3 levels) also to cpu boosting during input, without enabling powersaver mode that restricts background data sometimes killing notifications
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- updates from kernel/common
- scheduler updates from Googles Pixel kernel
- tune scheduler for improved jitter and less jank frames
- scheduler updates for RT tasks
- scheduler updates from sd888/ 5.4 kernel
- mainline scheduler updates for better load balancing on sched_idle cpus
CPU related features:
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This compliments EAS
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
- vdso32 patches as found on Google Pixel devices (brief documentation here)
- arm64: lse: Prefetch operands to speed up atomic operations, thanks @kdrag0n
- implement fast refcount checking
- remove RTB logging to reduce overhead
- remove event debug logging
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
- 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:
- 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
- ufs improvements from pixel 4/ pixel 5 kernel
- default IO scheduler to CFQ and readahead to 128
- improve GC as to not interfere while user interaction is happening and prevent possible jitter or latency spikes
UI/UX/Usability:
- Backlight Dimmer (reduce minimal brightness on a solid white background from 2,3 lux to 1,6 lux)
- sweep to sleep
- touch sampling override option (set stock touchsampling rate from 120hz to 200hz for reduced touch latency)
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 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
- Backport to enable CONFIG_HAVE_MOVE_PMD (see here) , thanks @arter97
- Backport to enable CONFIG_HAVE_MOVE_PUD (commit here) , thanks @arter97
- allow max swappiness over 100, to favor swapping instead of dropping the cache
- free more RAM by removing unused reserved memory regions
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 5 Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- Shadow Call Stack (SCS) Security-Feature
- fix various CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message
- Backport mainline Selinux commits for improved performance in the selinux subsystem, thanks @arter97 (you must be on magisk 21.0 or higher, otherwise the kernel won´t boot)
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled, enable them with your favorite kernel manager
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- 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
- implement ramoops functionality to be able to easily debug kernel panics
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
Flashing Guide, Download and Changelog
Requirements:
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root (magisk 22.0 or higher), usually magisk stable works best
- a backup of stock boot.img and dtbo.img so you can go back to stock conditions (simplest way is TWRP)
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 7/Pro receives an 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, make sure you have a backup ready!
2. Flash the kernel.zip via latest TWRP, EXKM or FKM app and do a full reboot.
3. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
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.1.3 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-85018787
1.2.0 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-85369449
1.2.1 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-85432205
1.2.5 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-85797313
1.2.6 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-86238683
Android 12
1.0.0 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-87106135
1.0.1 https://forum.xda-developers.com/t/...nfone-7-pro-aka-tequila.4269677/post-87949953
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_TEQUILA_Zenfone_7

FAQ
F.A.Q:
Question: Why does the kernel version show as "unavailable" in settings after flashing it.
Answer: Asus does not allow for custom kernel names in their settings. Use a kernel manager to check the kernel version.
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 as well as dtbo.img from matching firmware you are on and flash the extracted boot.img and dtbo.img via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: Android 10s changes to partitions, doesn´t allow files in system/ and vendor/ to be replaced. This kernel is very far from the stock kernel. To account for this I can´t force load the stock kernel-modules for certain drivers as it happens on kernels that are closer to stock.
Instead we use Magisks function to overlay certain files during boot. Without a working Magisk environment the kernel cannot function.
Question: I have a phone that is converted from CN to WW and now there´s a warning from hardwarestub. Can I hide it?
Answer: Yes, I created a Magisk Module for those that want to hide the notification, so nobody needs to rely on paid apps.
The Magisk module can be found attached to this post.
Please note that refresh rate can´t be changed when the module is flashed. To able to change refresh rate or to remove the module, simple remove it in Magisk Manager and do a full reboot. I´ll attach it to the third post on this thread. There will be no support for this module from my side and no other support for converted devices.
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 one too

and the final one, because one never knows.

In case anyone asks, make sure to update to the firmware that dropped today.
[210421] ZenFone 7 Pro / 7 _WW_30.41.69.51
【Version】 30.41.69.51 【Model Name】 ZenFone 7 Pro (ZS671KS) ZenFone 7 (ZS670KS) 【Release Date】 2021/04/29 Since the server pushes update notice to different serial numbers by batches, it may take some days for you to receive the FOTA notice. Thanks for your patience. You may tap “System...
zentalk.asus.com
Download link for full firmware is here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS670KS/UL-I002D-WW-30.41.69.51-user.zip

Thank you for this! The phone is much faster, but also warmer in daily use. DeepSleep is perfect.

Seosam said:
Thank you for this! The phone is much faster, but also warmer in daily use. DeepSleep is perfect.
Click to expand...
Click to collapse
My phone runs on the same temperature compared to stock kernel.
Whats your ambient temperature? Maybe it's related to that.
Or it's coincidence and an app is stuck in background or got recently an update. Give it a reboot or maybe a few days.

Freak07 said:
My phone runs on the same temperature compared to stock kernel.
Whats your ambient temperature? Maybe it's related to that.
Or it's coincidence and an app is stuck in background or got recently an update. Give it a reboot or maybe a few days.
Click to expand...
Click to collapse
I think this is due to the higher boost from the kernel compared to stock. There is also only a 4-5 degree Celsius difference. And only when using apps. You can feel it a little in your hand.
Reboot was carried out, of course. As I said, I think it's simply due to the higher frequencies overall and is completely within the limits.

Seosam said:
I think this is due to the higher boost from the kernel compared to stock. There is also only a 4-5 degree Celsius difference. And only when using apps. You can feel it a little in your hand.
Reboot was carried out, of course. As I said, I think it's simply due to the higher frequencies overall and is completely within the limits.
Click to expand...
Click to collapse
The kernel doesn´t boost anything higher than stock. The powerhal and all boosts on input are unchanged compared to stock. Improved UI performance isn´t due to higher boosting.
Might be that some of the scheduler changes, paired with your unique usage lead to overall higher used freqs and the mild temperature increase.
Interesting that it seems to be the case for you.
Temps are basically the same on my end also during benchmarks, because I monitored temps while verifying the improved UI performance.
Thanks for the report! There is still more to come (also for the scheduler)

Thanks for your work, but I noticed than the consumption of the battery was high.
How can I flash the original kernel, I'm always on the stock a11 rom but I will flash soon the omnirom.

gui3gui said:
Thanks for your work, but I noticed than the consumption of the battery was high.
How can I flash the original kernel, I'm always on the stock a11 rom but I will flash soon the omnirom.
Click to expand...
Click to collapse
See post #2

Ok but perhaps, can you provide this file ?

gui3gui said:
Ok but perhaps, can you provide this file ?
Click to expand...
Click to collapse
No, it's best if you extract them yourself.
If you followed the instructions in the OP you should have a backup from boot.img and dtbo.img made via TWRP.
If you don't have them download the full firmware and extract them via payload extractor. You will be able to find that on XDA.
Edit: to flash Omni you need to have stock rom on both slots anyway. So just flash stock rom twice (that will restore original boot.img and dtbo.img anyway) and follow the Omni instructions!

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:
{
"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"
}
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.

Hey everybody,
I was a bit busy. Regarding new firmware update:
all changes from the 30.41.69.66 were already present in my kernel by merging CAF-Upstream.
So just flash away on the new firmware, link is here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS670KS/UL-I002D-WW-30.41.69.66-user.zip

Freak07 said:
Hey everybody,
I was a bit busy. Regarding new firmware update:
all changes from the 30.41.69.66 were already present in my kernel by merging CAF-Upstream.
So just flash away on the new firmware, link is here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS670KS/UL-I002D-WW-30.41.69.66-user.zip
Click to expand...
Click to collapse
Hi,
I'm considering to get a zenfone 7 Pro but I would like to know do your kernel support permissive mode with fully /system write?

TheEndHK said:
你好，
我正在考慮購買 zenfone 7 Pro，但我想知道您的內核是否支持完全 /system 寫入的許可模式？
Click to expand...
Click to collapse
no

TheEndHK said:
Hi,
I'm considering to get a zenfone 7 Pro but I would like to know do your kernel support permissive mode with fully /system write?
Click to expand...
Click to collapse
That's not related to the kernel any longer.
Permissive selinux can be set via terminal or a script.
Read/write is difficult on devices with dynamic partitions. Magisk modules are the easiest solution for this. They allow to systemlessly replace files during bootup.
However there are solutions like this:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
I'd be very cautious of stuff like this, it has the potential to mess up the device completely, so it can be only restored by wiping everything including all data on the device.

Any new updates? On the actual 78 firmware, the cores don't reduce the frequences on my phone.
Thank you

Double post