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?
Related
{
"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"
}
A simple kernel for the average user
This thread is for the TF300T version of the kernel. For the ME301T version, click here: GEASS for ME301T
GO TO THE SECOND POST FOR F2FS DOWNLOADS & INFO!
GEASS is aimed at a compromise between good battery life and high performance.
*Based off of CM kernel: https://github.com/CyanogenMod/android_kernel_asus_tf300t/tree/cm-11.0
*Overclock CPU to 1.7 GHz
*Overclock GPU up to 7xx MHz (I would recommend 650 max for stability)
*Adds SIO, V(R), Deadline, SIOplus, Zen I/O schedulers
*Adds Pegasusq, OndemandX, InteractiveX, Asswax, SmartassV2, Wheatley CPU governors
*Adds init.d support, insecure kernel
*Supports "adb reboot apx" to boot into APX mode
*Dynamic fsync
*TCP congestion control: cubic (recommended), westwood (recommended), vegas, veno, low priority, yeah, htcp, hstcp, hybla, scalable, illinois
*No need for ASUS performance profiles to set CPU speeds
*Compatible with TF201 on TF300T ROMs and 4.2 BL as well
*Compiled with Linaro 4.8.3 Toolchain optimized for Cortex A9s, which is found in Tegra 3
Download: Geass_Public7.zip (AndroidFileHost.com)
If you are using PacMan ROM please use the PAC compatible kernel download instead: Geass_Public7_PAC.zip
Source: https://github.com/ebildude123/Geass-Kernel-TF300T
Recommended ROM: CyanogenMod; but works with all KitKat ROMs.
Enable performance settings in most ROMs: About device > tap build number until developer options are enabled. Go back to settings and find performance section.
Use Trickster Mod to take full advantage of this kernel.
Screenshots (not up to date):
Antutu Benchmark (16665):
Settings used in screenshot below:
SmartassV2 CPU governor
Noop I/O scheduler
CPU clocked to 1.7GHz
GPU clocked to 600MHz
Changelog:
Code:
*Public7 (#7): 7th public release (bug fixes, enable tcp congestion algos, merge in upstream changes from CM, frandom support if you wish to use it)
*Public6 (#6): 6th public release (no more need for performance profiles, custom GPU overclocking (Go to specific section in trickstermod), cpu OC for TF201 (Prime))
*Public5 (#5): 5th public release (adds smartassv2 and wheatley cpu governor, adds apx reboot mode "adb reboot apx")
*Public4 (#4): 4th public release (adds pegasusq cpu governor, adds dynamic fsync, adds zen and sioplus i/o schedulers, insecure kernel [ro.secure=0], "fix 32-bit overflow in get_monotonic_boottime")
*Public3 (#3): 3rd public release (adds VR scheduler, enables deadline scheduler, fixes)
*Public2 (#2): 2nd public release (adds interactivex, init.d support)
*Public1 (#1): initial release (asswax, ondemandX, OC 1.7ghz, sio scheduler)
F2FS Kernel and Recovery
ONLY FOLLOW THESE INSTRUCTIONS IF YOU WISH TO TRY F2FS (FLASH FRIENDLY FILE SYSTEM)!
USE THE DOWNLOAD FROM THE FIRST POST FOR NORMAL KERNEL DOWNLOAD!
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극}) at Samsung for the Linux operating system kernel.[2]
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues[3] of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
http://en.wikipedia.org/wiki/F2FS
Code:
import this.is.your.standard.disclaimer;
public class youHaveBeenWarned
{
public static void main() {
System.out.println("[B][COLOR="Red"]I am not responsible if you damage or brick your device, encounter data loss or corruption, etc.[/COLOR][/B]");
System.out.println("[B][COLOR="red"]At your own risk![/COLOR][/B]");
}
}
Compatible ROMs
CyanogenMod 11, OmniROM 4.4, CROMBi-kk, Probably SlimKAT (untested)
Downloads
TWRP 2.7 for F2FS only: http://www.androidfilehost.com/?fid=23329332407580523
GEASS v7-f2fs for F2FS only: http://www.androidfilehost.com/?fid=23329332407582438
Steps: Read every single word and follow carefully!
1. Backup all your apps, data, music, videos, etc. to your PC or some other external location. They will be lost!
2. Download TWRP 2.7 for F2FS found above in this post. Reboot to your recovery, and flash it. Now boot into android (must).
3. Once in android, download GEASS for f2fs found above in this same post. Reboot to your recovery, and flash it. Now boot into android (must).
4. You will see something along the lines of Encryption Unsuccessful. This is normal.
5. Power off your device (hold power button and select power off).
6. Hold both power and volume down to power your device back on. You should see 3 icons, the first being RCK.
7. Hit volume up once you've confirmed RCK is selected (it should be by default.)
8. You should now be in recovery, and it should say "2.7.0.0-Geass".
9. Hit "Wipe" > "Format Data". When prompted, type "yes" and hit the enter key.
10. It should say it is formatting with mkfs.f2fs.
11. When that is complete, reboot into android.
12. Go through the ROM setup. If you want to double check you're on f2fs, open up terminal emulator and type "mount | grep f2fs" (no quotes) and make sure the /data partition is there (/dev/block/mmcblk0p8). (optional)
13. REMEMBER!: Whenever you are flashing or upgrading a ROM, either remove the boot.blob from the zip before flashing, or flash the F2FS kernel afterwards. For CROMBi-KK, pick "Do Not Flash a Kernel" option when it asks for you to choose a kernel, but still reflash the kernel to get the modules it installs.
Want to use a different kernel and still use F2FS?
These instructions will still apply!
Other confirmed working kernels ( besides GEASS ): _that v9 f2fs
Thanks To
Alex Page (F2FS kernel patch for tegra3)
@scanno (For this commit I needed for twrp -> https://github.com/omnirom/android_...mmit/3ce32690475d0dca09ae459f1ea75534b599bab2)
Please hit the thanks button if this helped.
ebildude123 said:
No issues with mega here.
Sent from my GS3 on BeanStalk 4.4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah please mirror this. MEGA is giving me a pathetic 3-12 KB/s down.
I can't even download it. Mega just fails and gives me an error.
tjk639 said:
I can't even download it. Mega just fails and gives me an error.
Click to expand...
Click to collapse
I uploaded it to mediafire for you guys, let me know if you can download it now :good:
ebildude123 said:
I uploaded it to mediafire for you guys, let me know if you can download it now :good:
Click to expand...
Click to collapse
Download speed seems better for me.
Downloaded from mega without any problems. Running it now and so far I am liking it!
Sent from my TF300T using Tapatalk
Thanks for this kernel! Seems to be a really smooth and stable. Got SoDs with GRIMLOCK Kernel ... now on GEASS Kernel everything works fine!
CM11 - NIGHTLY - 20140123
Posted an update.
Please let me know if there are any problems.
Does your kernel fit to PAC-man KK out of the box ?
@ebildude123,
I use a homemade version of PAC-man KK built three days ago; this morning i flashed your V2 kernel zip file from recovery and it booted but never reached the OS (even after a cache/dalvik wipe). So i decided to 'repo sync' your sources and then build your kernel along with PAC-man KK sources : the result was the same behaviour as described above...
After some time i've discovered this block in your defconfig file :
Code:
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDX is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_FREELUNCH is not set
[COLOR="Red"]CONFIG_CPUT_FREQ_DEFAULT_GOV_ASSWAX=y[/COLOR]
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_INTERACTIVE=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
CONFIG_CPU_FREQ_GOV_ONDEMANDX=y
CONFIG_CPU_FREQ_GOV_ASSWAX=y
... and i've changed it to this one :
Code:
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_GOV_ASSWAX=y
CONFIG_CPU_FREQ_GOV_ONDEMANDX=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
[COLOR="Green"]CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y[/COLOR]
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDX is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ASSWAX is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_INTERACTIVE=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
... compiled again along with PAC-man KK sources, flashed it and SUCCESS -> BOOT OK ! :good:
Then, i have three questions for you please :
-> In your defconfig file, 'CONFIG_CPUT_FREQ_DEFAULT_GOV_ASSWAX=y' is a mistyping of 'CONFIG_CPU_FREQ_DEFAULT_GOV_ASSWAX=y' isn't it ?
-> Is your V2 kernel supposed to work out of the box with PAC-man KK ROM ?
-> What settings should i use with your V2 kernel in order to maximize battery life ? My priorities are : stability, battery life and then performance...
Congratulations for your great work and thank you for taking time to answer me
ne0zone75 said:
@ebildude123,
I use a homemade version of PAC-man KK built three days ago; this morning i flashed your V2 kernel zip file from recovery and it booted but never reached the OS (even after a cache/dalvik wipe). So i decided to 'repo sync' your sources and then build your kernel along with PAC-man KK sources : the result was the same behaviour as described above...
After some time i've discovered this block in your defconfig file :
Code:
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDX is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_FREELUNCH is not set
[COLOR="Red"]CONFIG_CPUT_FREQ_DEFAULT_GOV_ASSWAX=y[/COLOR]
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_INTERACTIVE=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
CONFIG_CPU_FREQ_GOV_ONDEMANDX=y
CONFIG_CPU_FREQ_GOV_ASSWAX=y
... and i've changed it to this one :
Code:
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_GOV_ASSWAX=y
CONFIG_CPU_FREQ_GOV_ONDEMANDX=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
[COLOR="Green"]CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y[/COLOR]
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDX is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ASSWAX is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_INTERACTIVE=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
... compiled again along with PAC-man KK sources, flashed it and SUCCESS -> BOOT OK ! :good:
Then, i have three questions for you please :
-> In your defconfig file, 'CONFIG_CPUT_FREQ_DEFAULT_GOV_ASSWAX=y' is a mistyping of 'CONFIG_CPU_FREQ_DEFAULT_GOV_ASSWAX=y' isn't it ?
-> Is your V2 kernel supposed to work out of the box with PAC-man KK ROM ?
-> What settings should i use with your V2 kernel in order to maximize battery life ? My priorities are : stability, battery life and then performance...
Congratulations for your great work and thank you for taking time to answer me
Click to expand...
Click to collapse
Thanks bro, that's a typo indeed! Though its always booted for e even with that typo for some reason xD. Will commit a change to fix that, ty.
Sent from my GS3 on BeanStalk 4.4 using Tapatalk 4
Looks good, will give this a try.
It's been a while since I've flashed any custom kernels so just to make sure do I push this with fastboot?
Thanks
Sent from my TF300T
burt_ie said:
Looks good, will give this a try.
It's been a while since I've flashed any custom kernels so just to make sure do I push this with fastboot?
Thanks
Sent from my TF300T
Click to expand...
Click to collapse
Its a .zip so just flash it in recovery.
Sent from my SGH-T999 using xda app-developers app
andrewnelson23 said:
Its a .zip so just flash it in recovery.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Awesome thanks
Sent from my TF300T
#3 update posted, view changelog or github repo for details.
Regards.
is this compatible with the Omni rom?
ebildude123 said:
#3 update posted, view changelog or github repo for details.
Regards.
Click to expand...
Click to collapse
Hi
I want to use your kernel with OmniROM. Why do I need Trickster MOD and what settings should I use?
Trickster MOD is an app that can tweak the kernel settings... you dont need it but if you dont know what your doing, you can mess up your tablet..
gd6noob said:
Trickster MOD is an app that can tweak the kernel settings... you dont need it but if you dont know what your doing, you can mess up your tablet..
Click to expand...
Click to collapse
What kernel settings do you suggest for good battery life and acceptable performance?
I was asking about TricksterMOD because this didn't sound like it was optional:
ebildude123 said:
Using AOKP or OmniRom? You will need this:
Trickster MOD app to configure: https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
TricksterMOD can apply settings at boot, which I highly recommend turning on.
Click to expand...
Click to collapse
One suggestion for your githiub:
It looks like you are uploading to github after you have compiled the kernel. As a result, all the "compiled" stuff is getting uploaded which would make it impossible for someone to cherry pick your commits or even reference them for their own. I would suggest cleaning out the compiled stuff before committing to github, as in using the "make clean" command before making the commits. I hope this make sense because I'm pretty new to github and am still trying to find my way with it too.
{
"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"
}
- NOTICE: DEVELOPEMENT FOR THIS KERNEL HAS BEEN DISCONTINUED -
Compatible with OmniRom Marshmllow builds
and all Omni based roms (Omni Official builds, Omni Herna's builds, FusionJack's SlimSaber, SAOSP, etc.)
Hotplug Drivers
Omni's stock CPU-Quiet Hotplugging Framework
Blu_Plug (disabled by default) thanks to engstk
Alucard Hotplug (disabled by default) thanks to Alucard_24
MSM Zen Decision (disabled by default) - thanks to bbedward
Bricked Hotplug (disabled by default) - thanks to neobuddy89
Mpdecision (disabled by default)
CPU Governors
Smartmax / Ondemand / Interactive / Conservative / Powersave / Performance (Omni's stock)
Zzmoove (added) - thanks to ZaneZam - REFER TO 3RD. POST FOR INDICATIONS ON HOW TO SET PROFILES
Smartmax_EPS (added)
Alucard (added)
Blu_Active (added)
Custom Features & Optimizations
Built with UBER 5.3 optimized toolchain & optimization Flags
Upgraded linux version 3.4.110
Adreno Idler - tuned for Omni
State_Notifier - by NeoBuddy89
Charge_Level interface - thanks to Lord_Boeffla - FIND INDICATIONS TO HANDLE THIS IN THE THIRD POST
KCAL v2 Control - credits to Savoca
Voltage Control Interface - credits to Franciscofranco
Power Efficient workqueues (enabled by default)
Quickwakeup driver
Franco's thermal driver
Franco's Sound Controls
Faux/Yank's powersuspend implementation
Reduced wakelocks and power saving optimizations
Vibrator Intensity interface
Fsync toggle - thanks to franciscofranco
Wlan wakelock toggles - experimental
CRC toggle - disabled by default
Sync on Suspend toggle interface (disabled by default)
Dynamic management of dirty page writebacks
ARM Topology optimizations
Faux's Simple GPU Algorythm
Increased randomness
CDROM/USB emulation toggles (DriveDroid compatibility)
Many, many other optimizations (refer to the source code for more details)
- Flashable using Anykernel2 - thanks to osm0sis
DISCLAIMER: flash at your own risk; this is intented to improve your android experience, but I'm not responsible for anything unexpected it could happen - and sh** does happen sometimes. Yet, knowing what you are doing usually prevents it. So... be warned.
XDA:DevDB Information
Donkey ONE Kernel, Kernel for the ONEPLUS ONE
Contributors
fermasia
Source Code: https://github.com/fermasia/android_kernel_oppo_msm8974
Special thanks for their source to: OmniRom team ; ak ; savoca ; herna; RenderBroken ; franciscofranco ; LordBoeffla ; derromtester ; neobuddy89 ; and many others.
Created 2015-02-16
Last Updated 2015-12-27
DOWNLOADS - If you find my work useful, please consider buying me a beer :good:
- NOTICE: DEVELOPEMENT FOR THIS KERNEL HAS BEEN DISCONTINUED -
Current version: Version 15 - 27-Dic-2015
Older versions: here
Extras:
UKM-Donkey_Edition_v2
Screen Control App by savoca
Flashing Instructions:
- Flash through recovery (TWRP recommended)
- Flash UKM-Donkey Edition (optional)
- Clean cache (recommended)
- Reboot
- Install Synapse (optional)
- Enjoy (mandatory)
CHANGELOGS:
REFER TO MY KERNEL SOURCE FOR DETAILS ON EVERY COMMIT INCLUDED.
ON HOW TO HANDLE CHARGE_LEVES INTERFACE (proceed with caution, if you don't know what you are doing, just don't do it... I won't support any mess ups with this option!)
- You'll find the sysfs interface for this in this path: /sys/kernel/charge_levels
- The charge_level_ac file contains the value for the wall charger rate in mA; if the file contains a 0 value, it will charge at the standard rate, anything else will be user handled; values should go not more than to the 2100 limit.
- The charge_level_usb file contains the value for the usb charge rate in mA; if the file contains a 0 value, it will charge at the standard rate, anything else will be user handled; values should go not more than to the 500 limit.
- Te charge_info file provides info about the rate in mA and voltage when the phone is charging.
ON HOW TO APPLY ZZMOOVE PROFILES: For now, use Kernel Adiutor, Synapse or any other kernel tweaker to select Zzmoove as the Cpu Governor, and under Governor Optimizers (or in the Sysf folder) and choose the profile_number of your choice:
1 - for Default (set governor defaults)
2 - for Yank Battery -> old untouched setting (a very good battery/performance balanced setting DEV-NOTE: highly recommended!)
3 - for Yank Battery Extreme -> old untouched setting (like yank battery but focus on battery saving)
4 - for ZaneZam Battery -> old untouched setting (a more 'harsh' setting strictly focused on battery saving DEV-NOTE: might give some lags!)
5 - for ZaneZam Battery Plus -> NEW! reworked 'faster' battery setting (DEV-NOTE: recommended too! )
6 - for ZaneZam Optimized -> old untouched setting (balanced setting with no focus in any direction DEV-NOTE: relict from back in the days, even though some people still like it!)
7 - for ZaneZam Moderate -> NEW! setting based on 'zzopt' which has mainly (but not strictly only!) 2 cores online
8 - for ZaneZam Performance -> old untouched setting (all you can get from zzmoove in terms of performance but still has the fast down scaling/hotplugging behaving)
9 - for ZaneZam InZane -> NEW! based on performance with new auto fast scaling active. a new experience!
10 - for ZaneZam Gaming -> NEW! based on performance with new scaling block enabled to avoid cpu overheating during gameplay
11 - for ZaneZam Relax -> NEW! based on moderate (except hotplug settings) with relaxed sleep settings (to react audio/bluetooth/wakeup issues)
Thanks for this man, Just downloaded your unofficial omni build and now this.
Wow! Finally a Custom Kernel for Omni! Much Appreciated
Sent from My OnePlus Using XDA Premium 4
@fermasia well quite lucky you guys. You just steal our one of best devs. Just kidding. Well nice to see you you here brother @fermasia. Well I hope you will develop with same Passion for which you are known in community. Well flash flashing guys.
Sent from my XT1033 using XDA Free mobile app
@fermasia, Just installed the kernel on your latest build but its stuck at bootlogo for long time. Did clean cache.
anishz said:
@fermasia, Just installed the kernel on your latest build but its stuck at bootlogo for long time. Did clean cache.
Click to expand...
Click to collapse
I'm looking into it, tested it fine onto a dirty flash of the latest Omni build, but for some reason when I clean flashed the new Omni version, it doesn't work. As soon as I get it sorted out I'll re-upload the link.
fermasia said:
I'm looking into it, tested it fine onto a dirty flash of the latest Omni build, but for some reason when I clean flashed the new Omni version, it doesn't work. As soon as I get it sorted out I'll re-upload the link.
Click to expand...
Click to collapse
Take your time man, we'll wait.
where is the rom link please.
malavan said:
where is the rom link please.
Click to expand...
Click to collapse
Dude you are a senior member, Rom link is in Android Development thread HERE.
And if you meant Kernel link then fermasia is testing it as it wasn't booting for us.
anishz said:
Dude you are a senior member, Rom link is in Android Development thread HERE.
And if you meant Kernel link then fermasia is testing it as it wasn't booting for us.
Click to expand...
Click to collapse
Sorry i was on the old Omni theread maybe I'm getting blind lol thanks
malavan said:
Sorry i was on the old Omni theread maybe I'm getting blind lol thanks
Click to expand...
Click to collapse
Happens to all of us, also thread was just launched today.
@fermasia, when you are free and if taking requests, please take a look at This.
anishz said:
Take your time man, we'll wait.
Click to expand...
Click to collapse
Done, the link is back up. It was a dumb derp in the flashing script... lol.
malavan said:
where is the rom link please.
Click to expand...
Click to collapse
If you meant the kernel's link, it's back again, had to put it down for an hour to solve a small derp.
fermasia said:
Done, the link is back up. It was a dumb derp in the flashing script... lol.
Click to expand...
Click to collapse
Done, flashed and working well. Thanks!
anishz said:
Happens to all of us, also thread was just launched today.
@fermasia, when you are free and if taking requests, please take a look at This.
Click to expand...
Click to collapse
Yup, kcal, fastcharge, voltage control, etc are queueing in the to-do list
Dope! Are the default settings your recommended settings?
OmegaBlaze said:
Dope! Are the default settings your recommended settings?
Click to expand...
Click to collapse
Not really, I'm still testing -and will probably keep tuning- hotplugs and governors. I'm even considering adding Bricked Hotplug too.
The beauty -in my opinion- about Omni is how solid it works. With other roms I've allways stepped into A or B annoying bugs. Not talking down about anybody's work, but even when Omni takes more time to add features, things work better, and I like that. Plus these guys are making a true open source project, not meaning to bloat our experience with the goal of making money -like CM theme manager- but again, that's just my point of view.
Back to the kernel, there's still work to be done. For now, at least I'm getting a much more acceptable battery drain and, in my opinion, a very good idle/deepsleep drain. Yet I'm not too fond about excesive options, and 3 hotplug drivers qualify as way too much to choose from. I love mako_hotplug because of it's simple and clean approach, that's why it's defaulted. But I might find some other works better in lollipop. So please toy with settings and try to find ur better config. And... report back if you can, I could use the feedback.
Thanks for downloading and trying out.
Looks like a very interesting kernel for the omnirom!
What does the 'quick wake up' feature exactly do? Does it remove the slight delay between pressing the power button and the screen turning on?
Could not really find something describing it on google.
Omni is using cpuquiet hotplug, right ?
Is it working good ?
{
"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.
Disclaimer & Notes
I bear no responsibility towards any failure or malfunction of your device, use my kernels at your own risk.
I have no time or resources for support of any kind whatsoever.
The kernels are for my own use, recompiled from original boot images of respective roms, with the objective of prolonging battery backup, not performance.
The kernel features are compiled in only, meaning not optimized at all, you must use Kernel Adiutor to set the right options to achieve desired effect, see post #2
Yes, they work with XPOSED! (marshmallow only), but xposed modules should be enabled & configured ONE-BY-ONE-then-reboot-phone to take effect.
If wireless or sim cards are not detected after enabling some xposed modules, simply restart phone, or turn on-3mins-off airplane mode, or revert your xposed module settings (gravity-smart radio in particular)
Credits & Thank you
abhishekr700 | source
Fabb2303 | source
LuK1337 | source
Z00L & variants only, meaning these kernels are for Asus Zenfone 2 Laser models
- ZE550KL
- ZD550KL
- ZE600KL
Features (added)
- cpu hotplug: autosmp
- tcp-algorithm: westwood
- kernel config.gz at /proc
- filesystem: ntfs
- charging: usb fastcharge
- selinux: set to permissive via kernel
- kernel: samepage merging, frontswap, cleancache
Features (removed)
- cpu: cpu boost
- cpu hotplug: msm performance, including touch boost
- CRC check, in favor of 30% performance boost
Work-in-progress, no ETA
- gpu idler
- more cpu/gpu governor
- i/o scheduler
DOWNLOAD
edit: download link removed, to comply with GPLv3, will reinstate download link once sources are published, no ETA though
before flashing my kernel, read disclaimer at top of this post, make a backup of your phone partitions, imei, running kernel, settings, data etc
unzip & copy to sdcard, flash via fastboot or TWRP
file names & ROMs
ROM BeanStalk-6.25-20160919-Z00L (marshmallow)
kernel boot_m003_BeanStalk-6.25-20160919-Z00L.7z
ROM CM13 snapshot dated 2016-12-21 (marshmallow)
kernel boot_m003_cm13snapshot20161221.7z
ROM Resurrection Remix v5.7.4 dated 2016-09-23 (marshmallow)
kernel boot_m003_RR-M-v5.7.4-20160923-Z00L.7z
ROM Slim-Z00L-6.0.1.b1.7--20161019-1635 (marshmallow)
kernel boot_m003_Slim-Z00L-6.0.1.b1.7--20161019-1635.7z
ROM CM-14.1-20161225-NIGHTLY-Z00L (nougat)
kernel boot_m003_cm-14.1-20161225-NIGHTLY-Z00L.7z
ROM Resurrection Remix v5.8.0 dated 2016-12-22 (nougat)
kernel boot_m003_RR-N-v5.8.0-20161222-Z00L.7z
ROM XOSP-RL7-REV2-UNOFFICIAL-20170109-Z00L
kernel boot_m003_XOSP-RL7-REV2-UNOFFICIAL-20170109-Z00L.7z
New Upload, 2017 Jan 26th, features are the same as previous kernels (nothing new), just a re-compile
ROM aicp_Z00L_n-12.1-UNOFFICIAL-20170122
kernel v05-aicp_Z00L_n-12.1-20170122.7z
ROM aokp_Z00L_nougat_unofficial_2017-01-24_0801
kernel v05-aokp_Z00L_nougat_2017-01-24_0801.7z
ROM XOSP-RL7-REV2-UNOFFICIAL-20170115-Z00L
kernel v05-XOSP-RL7-REV2-20170115-Z00L.7z
ROM RR-N-v5.8.0-20170121-Z00L-OFFICIAL
kernel v05-RR-N-v5.8.0-20170121-Z00L.7z
My settings for reference:
Monitoring tools:
- Settings > Developer options > enable 'Show CPU info' (far bottom) OR
- Trepn Profiler (from Playstore), enable 'CPU Frequency Overlay' OR
- Kernel Adiutor > CPU drawer > CPU Frequency section
Kernel Adiutor Mod | thread | download
Note: After enabling 'Apply on boot', check Start-Up Commands and verify the settings are actually being applied
- I/O Scheduler > Internal Storage > noop | External Storage > noop | Enable 'Apply on boot' | read Recommendations & Benchmark for best settings
- Power and Battery > USB Fast Charge > enable | Enable 'Apply on boot'
- CPU Hotplug > AutoSMP > Downrate Limits 55% | Uprate Limits 75% | Cycle Down 2 | Cycle Up 3 | Delay 500ms | Max CPU 4 (if quad-core) | Min CPU 1 | Enable 'Apply on boot'
- CPU > Max Freq 998MHz | Min Freq 200MHz | Governor Interactive | Governor Tunables >>>
Code:
above_hispeed_delay 20000 100000:60000 200000:150000
(note: its 20 thousand, 100 thousand:60 thousand, 200 thousand: 150 thousand)
align_windows 1
boost 0
boostpulse_duration 80000
(note: its 80 thousand)
go_hispeed_load 99
hispeed_freq 200000
io_is_busy 0
max_freq_hysteresis 0
min_sample_time 40000
(note: its 40 thousand)
target_loads 98 100000:40 200000:80 400000:95
(note: its ninety-eight, 100 thousand:40, 200 thousand:80, 400 thousand:95)
timer_rate 46666
(note: its 46 thousand, 666)
timer_slack 80000
(note: its 80 thousand)
use_migration_notif 0
use_sched_load 0
After applying all settings, reboot phone, then wait for Kernel Adiutor Mod to apply settings, then check your monitoring tool
- during idle, 3 out of 4 cpu cores will be offline/shutdown, the remaining active core should hover between 200-400MHz
- when phone is in use, the offline cores will be activated, scale up the frequency, then slide towards idle state
if using marshmallow, enable xposed, install amplify, greenify to optimize wakelock & hibernate settings
if using nougat, try to edit doze settings
wakelock, hibernate, doze apps & settings, checkout
http://lifehacker.com/how-android-doze-works-and-how-to-tweak-it-to-save-you-1785921957
https://www.reddit.com/r/Android/co...doze_features_in_nougat_have/#bottom-comments
https://forum.xda-developers.com/an...doze-settings-editor-android-t3235130/page136
EDIT: the settings above is not 100% tuned, but it works, there's no stutter either (during idle, 1 core should be 200-400MHz, by right, it should stay 200MHz all the time during idle, this is affected by timer_rate 46666, which does NOT stick at all, may need to set manually each time at boot). To get the proper value of timer rate, increase or decrease by 5000, it's base value is 30000, u can start from there. I simply chose 46666 coz it hovers less.
Follow these guides to tweak further the cpu governor INTERACTIVE
https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
https://forum.xda-developers.com/showthread.php?t=2769899 (OLD GUIDE)
reserved also
Thanks for this amazing work. Will flash the kernel right now on cm13. I tried optimising cpu governers with one of the guides in nexus thread, but they all proved vague as a simple touch is boosting all cpu cores to their max. Also 'stop perfd' command in terminal did helped a bit to limit it but then, the performance was stuttering. A big thanks for this kernel. Will flash and post the results.. ??
hotplug autosmp totally disables touch boost by its very nature
Any chance of a CM14 25/12/2016 version for Z00L?
zackwire said:
Any chance of a CM14 25/12/2016 version for Z00L?
Click to expand...
Click to collapse
probably next week, no guarantees though.
I need to work on getting gpu idler functional. the idler works at all screens but not at screen off.
gpu frequencies
200Mhz, 310Mhz, 400Mhz
current gpu idler implementation which I tried:
during idle, the gpu should rest at 200Mhz, yes this works but the moment the screen goes off, it shoots back to 310Mhz and stays there.
try it on your current rom, at adb shell
Code:
cd "/sys/devices/soc.0/1c00000.qcom,kgsl-3d0/devfreq/1c00000.qcom,kgsl-3d0" ; while true; do cat trans_stat ; busybox sleep 0.1 ; done ;
observe the asterisk *, that's the current gpu speed,
then try using the phone, touch menus, launch apps etc, see the * switch to different speeds, then check idle speed
Code:
From : To
:400000000310000000200000000 time(ms)
400000000: 0 61 0 70233
*310000000: 60 0 26 755266
200000000: 1 25 0 43133
Total transition : 173
Thanks for the kernel
Flashed on the 22nd nougat build of RR
Does this kernel works on Resurrection Remix (nougat) and XOSP ROMs ?
ThanveerAliSayed said:
Thanks for the kernel
Flashed on the 22nd nougat build of RR
Click to expand...
Click to collapse
How is the battery performance ? is the kernel is specific batch builds like 22 Dec RR or can we use in any other batch builds too ?
pokipokipxorn said:
hotplug autosmp totally disables touch boost by its very nature
Click to expand...
Click to collapse
Awesome kernel man. Thanks. Been using it on cm13 since yesterday and I must say the battery savings were significantly improved without compromising performance at all. No stuttering at all.
Will try it on RR N today.
BTW, I have a doubt, in above_highspeed_delay and target_loads, the first frequency written in OP is 100Mhz but cpu frequencies in Z00L starts from 200Mhz. So what's the significance of putting these values of 100MHz?
I know little about CPU Gov tuning and I/O scheduling but whatever I found on searching over XDA for I/O schedulers is, Deadline to be better I/O Scheduler with following tunings-
fifo_batch 4
front_merges 1
read_expire 500
write_expire 3000
writes_starved 3
heerarana said:
Does this kernel works on Resurrection Remix (nougat) and XOSP ROMs ?
Click to expand...
Click to collapse
heerarana said:
How is the battery performance ? is the kernel is specific batch builds like 22 Dec RR or can we use in any other batch builds too ?
Click to expand...
Click to collapse
RR Nougat - yes, check 1st post under section file names & roms
The truth about kernels and battery life
Not sure about other roms, you could test the kernel via fastboot
Code:
fastboot boot testkernel.img
This will boot the test kernel one time, your original kernel remains intact, you could check the features & whether it works for you.
kunalchitara said:
Awesome kernel man. Thanks. Been using it on cm13 since yesterday and I must say the battery savings were significantly improved without compromising performance at all. No stuttering at all.
Will try it on RR N today.
BTW, I have a doubt, in above_highspeed_delay and target_loads, the first frequency written in OP is 100Mhz but cpu frequencies in Z00L starts from 200Mhz. So what's the significance of putting these values of 100MHz?
I know little about CPU Gov tuning and I/O scheduling but whatever I found on searching over XDA for I/O schedulers is, Deadline to be better I/O Scheduler with following tunings-
fifo_batch 4
front_merges 1
read_expire 500
write_expire 3000
writes_starved 3
Click to expand...
Click to collapse
I didn't test for optimized settings but just went through these 2 guides below
Follow these guides to tweak further the cpu governor INTERACTIVE
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life! (Old Guide)
What I remember: 100MHz is for the transition of sustained cpu loads of at least 60ms before crossing into the next frequency, while 200MHz is the cpu frequency stepping. Honestly speaking, if you go through the 2 guides above, you'll notice our cpu speed range is too small (200MHz > 400MHz > 533MHz > 800MHz > 998MHz).
You could replace it with the standard speed steppings ie 200 > 400 > 533MHz.
If you find better performance of any sort, pls post the settings.
Z00L battery may not be enough for my usage, no matter what I do, and I prefer not to carry a powerbank daily. I might get a Xiaomi Mi Max 4850 mAh and use Z00L as a backup. the Mi Max is just $70 extra, heck a 10,000 powerbank already costs $20, and the Mi Max gives 6.4" IPS, 3GB ram, 2 more power cores, plus the big battery. I could use at least 2 days w/o charging.
heerarana said:
How is the battery performance ? is the kernel is specific batch builds like 22 Dec RR or can we use in any other batch builds too ?
Click to expand...
Click to collapse
Iam using on 22nd build of RR perfomance is gud. And battery also with his given settings in the auto smp
Been using the kernel and suggested settings since yesterday on CM13 Snapshot and the battery life and performance of this is a beast! great work mate...got roughly 3:30hs SOT and lost only 47% of juice.
zackwire said:
Any chance of a CM14 25/12/2016 version for Z00L?
Click to expand...
Click to collapse
added kernels for the following ROMs:
ROM BeanStalk-6.25-20160919-Z00L (marshmallow)
ROM Slim-Z00L-6.0.1.b1.7--20161019-1635 (marshmallow)
ROM CM-14.1-20161225-NIGHTLY-Z00L (nougat)
check 1st post for filename & download link
ThanveerAliSayed said:
Iam using on 22nd build of RR perfomance is gud. And battery also with his given settings in the auto smp
Click to expand...
Click to collapse
can i flash this kernel in XOSP rom ?
heerarana said:
can i flash this kernel in XOSP rom ?
Click to expand...
Click to collapse
You can try. If any prob occur.
Just flash the boot.img from the xosp rom zip file to revert the effect
You should add for stock rom to.
pokipokipxorn said:
RR Nougat - yes, check 1st post under section file names & roms
The truth about kernels and battery life
Not sure about other roms, you could test the kernel via fastboot
Code:
fastboot boot testkernel.img
This will boot the test kernel one time, your original kernel remains intact, you could check the features & whether it works for you.
Click to expand...
Click to collapse
I tested in for XOSP ROM and got "Okay" message at the end. I tried to flash with TWRP Recovery but its not finding Winzip file in directory. I tried to convert into .zip file which came as "boot_m003_RR-N-v5.8.0-20161222-Z00L.7z.zip" and failed while flashing.
Also i tried with this command in fast boot mode: fastboot flash boot_m003_RR-N-v5.8.0-20161222-Z00L.img but it's not working.
can you plz make .zip file ?
{
"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?