Related
This is my personal kernel, that I decided to release now. It is extremely lean to minimize memory footprint and optimize perfomance. It is built from HTC official GB sources, with some of bananacakes, siberes, snq-s and my own patches. I intend to keep it at 2.6.35.10, as I see more problems than advantages in upstreaming to newer revisions.
Features:
-Hybrid adaptive voltage scaling (HAVS)
-V(R) i/o scheduler
-TinyRCU
-Overclock up to 1190
-Undervolt
-Ondemand, Virtuous and SmartassV2 governors (I use Virtuous for wake and Ondemand for sleep)
-AXI
-Lowered WiFi voltage
-EXT4 support
-snq-'s Autobrightnessmod (Enable all 10 levels)
-sibere's Battfix
-USB fast charge
-Optional 2 way call recording
-Hardcoded SD Speed Patch to 2048. No need for init script anymore
-Hardcoded highly tweaked Lowmemkiller (3584,4096,8192,20992,23040,25088). Throw away Autokiller and/or init scripts.
To make it more lean, I have disabled EXT2 support. SWAP isn't supported either, as I find it completely useless.
I have added CIFS and TUN as modules. To install, download and extract the file and push it to /system/lib/modules like so:
Code:
adb remount
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
And add the following line to your modules init script:
Code:
insmod /system/lib/modules/cifs.ko
insmod /system/lib/modules/tun.ko
The kernel comes in 2 flavors. BFS and CFS. Differences between them are here:
BFS - Brain F**k Scheduler
The scheduler essentially handles CPU resource allocation. It controls how the CPU ramps up in frequency and down again when not needed. The BFS version is generally very snappy (possibly more so than CFS) but is an older scheduler. It is designed to minimise latency on low spec'd machines (desktops generally)
Further details here:
http://en.wikipedia.org/wiki/Brain_****_Scheduler
CFS - Completely Fair Scheduler
This particular scheduler is newer than BFS. It is designed to make the best of High end machines (desktops again). In the early days, CFS seemed much laggier than BFS but now there is not too much in it. I am quite happily running a modern CFS kernel and I don't experience any lag issues.
Further details here:
http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
I am aware that the BFS version throws some errors about 'bad cgroup data' in logcat, I haven't been able to get rid of them. I have disabled everything cgroup related in the kernel, but vm still throws the errors. Don't know why. Doesn't seem to impact performance.
I personally use the BFS version, as I find it somewhat faster than the CFS one. I have absolutely no wake lag, and I get good battery time.
Thanks go out to: snq-, bananacakes, sibere, tobi01001, thalamus, eviollet. If I forgot anyone, pls inform me.
CHANGELOG:
V05:
XZ compression
Fixed Wifi sleep
Tweaked OJ settings for better responsiveness (bananacakes)
Changed ramdisk compression method to gzip.
Rebuilt tun.ko and cifs.ko
v04b:
Fixed WIFI. (My bad. Forgot to adapt install script after including new ramdisk.)
v04:
Added Lowmemkiller tweak to ramdisk (3584,4096,8192,20992,23040,25088) No need for Autokiller or init scripts anymore. Over time I will move more tweaks into the ramdisk to minimize the need for init scripts.
Updated BFS to 0.406
Reverted battery gauge polling to 60 secs.
Added Virtuous governor. Virtuous is a highly tweaked SmartassV2.
Removed Lagfree governor again, as I found OndemandX better.
v03:
Hardcoded SD Speed Tweak to 2048. No need for init script anymore
Made 2-way call recording optional. Check downloads
Reduced battery gauge polling from 60 to 5 secs. (Untested)
A few bits more, can't remember it all.
v02:
Added Lagfree governor. Gives me a wee bit better battery, but sometimes lags when listening to music. Maybe I'll remove it again. Tell me what you think.
Added a minor change from tobi01001 to the lightsensor driver. Details here
Hopefully fixed USB fast charge.
Compiler optimizations
Link to my github: https://github.com/tristan202
Earlier i heard lot's of people complaining about reboots / hang up's when browsing internet with lowered WIFI voltages, i will give it a try today anyway thanks.
k3lcior said:
Earlier i heard lot's of people complaining about reboots / hang up's when browsing internet with lowered WIFI voltages, i will give it a try today anyway thanks.
Click to expand...
Click to collapse
I have been running with lowered wifi voltage for a few days without any problems at all. Doesn't browse much though, but market another wifi stuff have been working fine.
I'll give you feedback soon.
Thx and congratz.
Tapatalking.
tristan202 said:
I have been running with lowered wifi voltage for a few days without any problems at all. Doesn't browse much though, but market another wifi stuff have been working fine.
Click to expand...
Click to collapse
I've been using your kernel for several weeks now (tried all the rest) is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Thanks a lot mate the combination of HAVS, BFS, 1190 OC with UV to 825 working very nicely for me
beanbean50 said:
is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Click to expand...
Click to collapse
Just ask HTC they know everything about your phone
beanbean50 said:
I've been using your kernel for several weeks now (tried all the rest) is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Click to expand...
Click to collapse
siberes battery fix is included, and I have been making some tweaks to since the last release. Some minor stuff, but still some improvement.
tristan202 said:
siberes battery fix is included, and I have been making some tweaks to since the last release. Some minor stuff, but still some improvement.
Click to expand...
Click to collapse
wow, many thanks....
is there much difference between the 2 governors ondemandx and smartassV2...?
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
ziggy1001 said:
Thanks a lot mate the combination of HAVS, BFS, 1190 OC with UV to 825 working very nicely for me
Just ask HTC they know everything about your phone
Click to expand...
Click to collapse
haha...!
Yes, HTC, Google and every other Tom, **** and Harry...
beanbean50 said:
wow, many thanks....
is there much difference between the 2 governors ondemandx and smartassV2...?
Click to expand...
Click to collapse
Ondemand:
The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. This is available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Smartass:
This is based on the concept of the interactive governor. This is included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Interactive:
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
This is available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
ironjon said:
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
Click to expand...
Click to collapse
tobi's autobrightnessmod is included. Adding to OP.
Thanks, I'll be testing this! I've been using snq-'s kernel builds but since the OC/UV ones have freezing problems, and gingercakes won't work for me without MASSIVE lag, I look forward to seeing how this works out.
ironjon said:
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
Click to expand...
Click to collapse
It seems to work, yes. I've just pushed my patched framework-res.apk, and auto-brightness seems to do exactly what it did on snq-'s patched kernel.
EDIT: Ah, ninja'd. Well, there you have it then.
tristan202 said:
Ondemand:
The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. This is available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Smartass:
This is based on the concept of the interactive governor. This is included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Interactive:
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
This is available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
Click to expand...
Click to collapse
but we only have the first two governors to choose from, Interactive is not an option (in setcpu) or am I being stupid as per usual ...?
is usb fast charge enabled?
ZeGuitarist said:
Thanks, I'll be testing this! I've been using snq-'s kernel builds but since the OC/UV ones have freezing problems, and gingercakes won't work for me without MASSIVE lag, I look forward to seeing how this works out.
It seems to work, yes. I've just pushed my patched framework-res.apk, and auto-brightness seems to do exactly what it did on snq-'s patched kernel.
EDIT: Ah, ninja'd. Well, there you have it then.
Click to expand...
Click to collapse
where can I find the patched framework ?
beanbean50 said:
where can I find the patched framework ?
Click to expand...
Click to collapse
You have to patch your own framework-res
Tapatalking.
ironjon said:
You have to patch your own framework-res
Tapatalking.
Click to expand...
Click to collapse
can you guess my next question ...? hehe
Here you go i like helping the aged especially when, poor eyesight, liver damage, and tropical diseases have taken their toll
[How to] Adjust auto-brightness on GB Sense ROM
beanbean50 said:
where can I find the patched framework ?
Click to expand...
Click to collapse
You can't find it anywhere, you need to patch your own framework. The framework apk differs for each ROM, and contains each individual user's UOT kitchen mods too... So to be safe, you really shouldn't use someone else's framework.
Anyway, here's how to do it:
http://forum.xda-developers.com/showthread.php?p=17713587
It's pretty easy, as long as you know where your ROM's framework apk is (in internal /system, or in /sd-ext). Also, the thread suggest you put your framework mod in a flashable zip, but it's easier to just boot in recovery, and use adb to remove your old framework and push the new one.
This kernel no longer works with current CM10/AOKP ROMS - PLEASE DO NOT USE
PLEASE READ THIS ENTIRE POST THOROUGHLY BEFORE PROCEEDING...
This is a customized kernel built from SGH-I727 (aka Skyrocket) source code. This ROM has all the fixes from CyanogenMod & Team Chopsticks tree along with some other stuff.
It's very simple to install.
Ensure you've already installed a working ROM
Install Zip from CWM.
Wipe both caches (just to be safe)
Reboot
FSync Control - Courtesy of Ezekeel
FSync Control which can be used to disable the fsync system calls for single files and filesystems (echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled). These fsync syscalls are used by kernel modules and user space programs to flush an I/O buffer (which is in RAM) to disk to make sure that this data is actually savely stored on the disk before executing the next step. Disabling fsync can result in data loss on a crash/freeze since the data is still in the I/O buffer and has not been saved to disk as it should be and can also lead to problems due to race conditions if two or more processes access the same file. On the other hand disabling fsync reduces the number of I/O operations which potentially could reduce the battery drain and also improve I/O performance.
Click to expand...
Click to collapse
Governors
Wheatley Governor - Courtesy of Ezekeel
http://rootzwiki.com/topic/14685-kernel27-jul-glados-v20-for-jb/page__st__90__p__405813#entry405813
Badass (default)
Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 1080Mhz and therefore use less power. To trigger a frequency increase, the system must run a bit @ 1080MHz with high load, then the frequency is bumped to 1350MHz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 2-5 seconds, depending on the load your system is experiencing).
You can tweak the Phase 2 (1080MHz) and Phase 3 (1350MHz) via sysfs (if you don't know, then just leave it alone).
NOTE: Due to it's nature, this is not a benchmark governor. It is meant as a governor that gives you a smooth experience while saving battery.
InteractiveX
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
Lazy
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.
GPU Overclocking
GPU is stock clocked at [email protected] & [email protected] (default).
Example: To increase maximum GPU frequency in 3D mode to 320 MHz:
echo 320000000 > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk
Example: To increase maximum GPU frequency in 2D mode to 266 MHz:
echo 266667000 > /sys/devices/platform/kgsl-2d0.0/kgsl/kgsl-2d0/max_gpuclk
echo 266667000 > /sys/devices/platform/kgsl-2d1.1/kgsl/kgsl-2d1/max_gpuclk
Available frequencies:
3D: 320000000, 300000000, 266667000, 228571000, 200000000, 177778000, 27000000
2D: 266667000, 228571000, 200000000
Kernel-based MPDecision
100% kernel-based multi-core decision! (should cpu1 be online or not?)
This replaces your /system/bin/mpdecision binary which is disabled by the CWM flashable.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (70000)
delay = time between checks (500)
pause = if something else plugs in the cpu, fall asleep for 10000
scroff_single_core = if the screen is off, don't plug in cpu1 (1)
nwns_threshold_up = runqueue threshold, if this is reached cpu1 will be hotplugged (35)
nwns_threshold_down = runqueue threshold, if this is reached cpu1 will be unplugged (5)
twts_threshold_up = time threshold, this amount of time must have passed (250)
twts_threshold_down = same as above (250)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
(all times are in ms)
CURRENT
Version 6.3.6 - http://tinyw.in/L1BW <-- JB: CM10 or AOKP 4.1.x
Version 6.3.4 - http://d-h.st/L8K <-- JB: CM10 or AOKP 4.1.x
Version 6.2.1 - http://d-h.st/NWo <-- JB: CM10 or AOKP 4.1.x
Version 6.0.3 - http://d-h.st/hEI <-- ICS: CM9 or AOKP 4.0.4 <- Updated 8/22 - WiFi fixes
Version 5.4.5 - http://d-h.st/ngT <-- ICS: CM9 or AOKP 4.0.4
Governor scripts
NOTE: Not needed for v6.0.2 or v6.2 and beyond
These scripts will set the CPU0 & CPU1 governors correctly. Using a tool like System Tuner only sets CPU0 to the selected governor, but leaves CPU1 running the default. This was the only way I found to ensure both CPUs had the correct governor set. Basically this overwrites your init.qcom.post_boot.sh script with one that sets both CPUs to the same governor.
SmartAssV2 - http://d-h.st/zeQ
Badass - http://d-h.st/2CU
OnDemand - http://d-h.st/GAH
Non-CM9 Camera Fix
http://db.tt/vvMoadEo <-- Thanks endlessevo for this and thanks eliminat for pointing it out!
Battery life problems?
Read this first...http://forum.xda-developers.com/showthread.php?t=1759541
Then go here to grab Better Battery Stats (BBS) ... http://forum.xda-developers.com/showthread.php?t=1179809
Mega thanks to...
Team Chopsticks
Cyanogenmod Team
showp1984
gokhanmoral
faux123
TamCore
Ezekeel
FraciscoFranco
h0tw1r3
...and the other many countless kernel devs that I've Kang'd from
I don't claim credit for any unique code. I've managed to cobble this together from the following sources with various tweaks of my own to get it all running.
Faux123 (OC/UV code) - https://github.com/faux123/msm8660-htc-ics
Tegrak (Lulzactive governor) - http://tegrak2x.blogspot.com/2011/11/lulzactive-governor-v2.html
Erasmux (SmartAssV2 governor) - https://github.com/erasmux
showp1984 (BadAss, mpdecision, some very cool stuff here) - https://github.com/showp1984
TamCore (GPU OC) - https://github.com/TamCore
Hope I'm not violating any form of informal code of conduct in grabbing your guys' code.
CHANGELOG
Version 6.3.4
Removed Governor's that just plain do NOT work on our devices
Upgrade Adreno GPU drivers
Removed WiFi PM
Various CAF updates
Added ROW I/O scheduler
OnDemand Governor enhancements to support better battery usage - Applied to OnDemand-based governors (Badass, Wheatley, Lazy).
Added Gallimaufry, Aggressive, and Scary governors
Version 6.2.1
Merged Kernel up to 3.0.41
InteractiveX and Interactive screen off max freq set to 594Mhz
ram_console added to help debug CM10 - post /proc/last_kmsg to pastebin and link here
Version 6.2
Added new Governors: Lazy, Lagfree, InteractiveX (this is V2), Interactive updated to V3 (Imoysen didn't change the name for V3)
Fixed governor change not setting CPU1 (thanks to Imoysen) - No more governor setting scripts!
Added BFQv4 i/o scheduler
Version 6.1
Merged Kernel up to 3.0.40 (works great this time)
FSync control
WiFi PM control
Added fixes from Team Chopsticks git to get Alpha 2 working...not everything, but some of the juicer pieces
LMK from 3.4 kernel
Wheatley governor added - Please test and report back
As always see Github for all the bit/bytes
Version 6.0
Reverted back to 3.0.8 kernel core
Incorporated JB necessities
See Github for the bits/bytes
Version 5.5.3
Disabled ZRAM, Westwood, and LZO kernel compression
Removed some frequency steps - UnderVolting should be a little easier since there will be less knobs to turn
Changed some GPU iofractions
Updated pegasusQ governor - Works pretty good. Disable mpdecision, though. See OP to set "enabled" to 0.
Added some JB compiler options - Would be curious to see if this works OOB if someone wants to try on JB ROM
Version 5.5.1
Big update - Merged Linux kernel up to 3.0.39 (latest and greatest fixes/enhancements)
Enable ZRAM
TCP congestion control changed to Westwood (Google it)
jRCU for small systems
WiFi tweaks for battery life and flexiblity
Check out my Github commit log for a complete list - There's just too many
Version 5.4.5
Fixed 2D GPU bus speed
Implemented fixed ala Team Chopsticks to prevent emmc erasure to prevent bricking
Minor tweaks - Trying to fix vbus_present wakelock
Version 5.4.4
Added kernel-based 3-phase thermal management
OC GPU by default
DVFS disabled
Version 5.3.2
Updated OC code to default to 1.512Ghz, but OC up to 1.89Ghz (doesn't work for me very well, but ymmv) - Thanks to jjiggens for the help!
Volume bug fixed (would remain max or silent)
New BLN code
Check Github commit log for full details
Version 5.3
Really removed 1.836Ghz OC this time
UTF-8 support added back in
Reverted voltages back to the default - should fix instabilities for some. I would suggest under-volting as they start pretty high
Version 5.2z
Removed 1.836Ghz OC - Use 5.2 if you reallllly want that extra juice.
Version 5.2
SGH-I717 (Note) Source code base
GPU Overclocking support (see OP)
Upped max OC to 1.836GHz (defaults to 1.782Ghz)
Version 5.1
UTF-8 support
Various fixes
Compiler optimizations
BLN support
Version 5.0
UCLF6-based Source (e.g. official SGH-I727 from Samsung)
BadAss, SmartAssV2 Governors
OC to 1.782Ghz
Added GPU-level control to BadAss
Lowered BadAss Phase 2 Freq to 702Mhz (you can chance ala sysfs)
Hopefully reduced wifi wakelocks by filtering more unnecessary packets
VR and SIO schedulers added (let me know how they work out)
Version 3.3
RAMDISK updates from CM9
Badass tweaked for better battery (e.g. lowered phase2/3 frequencies)
Installs init.qcom.post_boot.sh with badass set as default for CPU0 & CPU1 and disables mpdecision <-- IF YOU MADE CHANGES TO THE ONE INSTALLED, MAKE A BACKUP OF YOUR'S AND COPY OVER MINE AFTER YOU INSTALL
Added support for HFP 1.6 wideband speech
Disabled GENTLE_FAIR_SLEEPERS
Version 3.2
BLN added back in
Governors: Badass (thanks showp1984), PegasusQ, SmartAssV2, standard ones
Toolchain updated to 4.6.3
Compiler optimizations
Raised max OC to 1.782Ghz
Kernel-based MPDECISION (thanks showp1984)
Various fixes (you can check my github commit log)
WiFi: WiFi wakelock reductions (tell me if things are out of whack)
WiFi: Power off wlan interface when wifi disabled to save battery
Touchscreen lock fix (ala Team Chopsticks)
Version 2.8
Non-standard governors removed - Not really aSMP aware and caused all sorts of funky weirdness
Underclocking enabled
Clock voltages tweaked - UV for some battery savings
Version 2.5e
Reverted back to fixed max freq @ 1.728Ghz (temp until I get some other things fixed)
SmartAssV2 tweaks
Fixed L2 Frequency inconsistencies (I think this was causing the freq to stick at 1.242Ghz)
Updated PegasusQ code
Version 2.4d
Added Pegasusq governor
Version 2.3
Min/Max CPU Frequency can now be set
SmartAssV2 Governor tweaked for battery life
Version 2.2.1a
Reverted early suspend/late resume driver mod
Version 2.2
Tweaked SmartAssV2 and Lulzactive governors
Added some other power tweaks
Disabled BLN - I think this is causing some problems atm. Will add back once they're ironed out.
Version 2.1
Tweaked Lulzactive and SmartAssV2 governors
Added OC/UV code from Faux123 repo
Version 2.0
Added Lulzactive governor
Version 1.0
Stock Kernel compiled from source with SmartAssV2 governor
My Github - https://github.com/InstigatorX
First good work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Downloading. Will report back in a few minutes.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
Downloading! Gonna test this on Chimera beta 2 flashed over CM9 A5. Will report back shortly, stay tuned...
Sent from my SGH-I727 using xda premium
Edit/Update.... Running GREAT! Set to smartass V2 and set min freq to 192. I used NSTools to set and double checked the govenor and frequencies with Rom Toolbox pro and Set Cpu, everything is sticking and running smooth. Been running this for an hour now, will report back if I find any issues in the future. Thanks again for the kernel, InstigatorX, GREAT WORK!!!!!!!!! (high 5)
Nothing broken
Set to smartass v2 min 192
Feels smooth. Really smooth. Hopefully this means i can leave my charger at home now
Edit: holy crap! Phone is on usb charging from laptop. This is the first time on cm9 its actually charging FAST while I'm using it!
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
I know it says that to be on a cm9 from but could I possibly flash this on sky ics?
Sent from my SAMSUNG-SGH-I727 using xda premium
No.
Btw-loses backlight after screen off. Not every time though, weird.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
Kole_Ackerson said:
I know it says that to be on a cm9 from but could I possibly flash this on sky ics?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
dont do it.
But yeah this kernel rocks!
Ok I'm on chimera flashed over aokp where are the performance settings at on here?
Edit: Using rom toolbox to set it. It seems to be sticking..
Sent from my SGH-I727 using Tapatalk 2
Should i be able to underclock? Not sticking.
If not, is it a PITA to enable?
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
mindmajick said:
Should i be able to underclock? Not sticking.
If not, is it a PITA to enable?
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
Click to expand...
Click to collapse
Works for me on CM9. Will check it out.
Sent from my SAMSUNG-SGH-I727 using xda premium
Am running cm9 too. I can set it, but when i go back in to performance its back to 1512.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
wow i flashed this and i was on stock gingerbread rom.... now i'm bricked!!!
thanks for not putting cm9 only!!!!! What am i going to do.... Shifty eyes
haha no but i'm going to flash this tonight!!!
thanks for all the hard work!!!!!
tacotino said:
wow i flashed this and i was on stock gingerbread rom.... now i'm bricked!!!
thanks for not putting cm9 only!!!!! What am i going to do.... Shifty eyes
haha no but i'm going to flash this tonight!!!
thanks for all the hard work!!!!!
Click to expand...
Click to collapse
Dude I read the first line and was like holy shi-....oh thank god
Sent from my GT-P7510 using xda premium
BaconStep said:
Dude I read the first line and was like holy shi-....oh thank god
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
hahaha
So this is good to flash with aokp? I know it says for cm9 but someone posted up about aokp
softballjunkee13 said:
So this is good to flash with aokp? I know it says for cm9 but someone posted up about aokp
Click to expand...
Click to collapse
I'm running it just fine
Sent from my SGH-I727 using Tapatalk 2
tacotino said:
wow i flashed this and i was on stock gingerbread rom.... now i'm bricked!!!
thanks for not putting cm9 only!!!!! What am i going to do.... Shifty eyes
haha no but i'm going to flash this tonight!!!
thanks for all the hard work!!!!!
Click to expand...
Click to collapse
Are you kidding? The title of the thread says cm9 kernel. I really hope you are joking....
Sent from my SAMSUNG-SGH-I727 using XDA
sk8erwitskil said:
Are you kidding? The title of the thread says cm9 kernel. I really hope you are joking....
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Read the last two lines, he's obviously kidding.
You change/add a color filter btw? Noticing the colors are a bit warmer than usual.
Sent from my SAMSUNG-SGH-I727 using xda premium
Hey guys. This is Badass Kernel, a modified version of AU Kernel with a little bit too many additions to fit in the Original Development section.
Logs are disabled in this kernel. This is not a bug, it's a feature.
Compatibility:
Android 4.2.2
CM10.1
AOSPA
PAC
AOKP
Android 4.0.4/4.1.2
CM9
CM9.2
AOSP
Touchwiz ICS V5
So.. new stuff:
1.0
CPU Undervolt down to (0-1-2-4-6).
A_U's bootsplash
Added Badass CPU Governor
Added Badass GPU control
Replace ZRAM LZO compression with Google Snappy compression which is a lot faster
Kernel Samepage Merging enabled by default
Writeback tweaked to do the work only when the screen is off
Added ROW I/O scheduler
Tweaked smartassV2 for more battery saving
Tweaked CFQ and Deadline
1.1
Added frandom support for CrossBreeder to finally work properly
Fixed memory leak in android binder
Restored and updated Lazy CPU Governor (expected: smooth UI, much better battery life and some lag in the first 20-30 seconds after boot)
Filesystem tweaks
Memory tweaks
Added SFB net scheduler and Veno TCP congestion algorithm for better use of internet
Disabled a lot of debugging
1.2
Implemented Dynamic Filesync and enabled by default
Proportional Rate Reduction for TCP
Correct AXI bus values for CPU
Re-added 825 and 844 MHz frequencies (be careful with these as they're not stable, they were left out with a reason)
Trimming /cache every 15 minutes if media playback is stopped.
Updated LowMemoryKiller driver (if you use ram manager or scripts for setting minfree, here are some really good values:3072,4096,12800,14336,15360,19200)
New bootsplash (HTC-alike)
1.2.1
Fixed Snappy
Further UV (0-1-2-3-6)
1.2.2
Enabled Compaction and linked it to LowMemoryKiller
Updated Deadline(now it's better than ROW)
Changed kernel compressor/decompressor from GZIP to the much faster LZ4.
Writeback tweaks from Linus Torvalds
Added TCP congestion algorithms: Hybla, Westwood, Highspeed-TCP. Default is Hybla because in tests, performed better than the rest.
1.3
Enabled Triple Buffering (component of Project Butter by Google)
Added Tiny RCU for smaller memory footprint
Added BoostPulse interface for SmartassV2
1.3.1
Added BoostPulse interface for SmartassH3 and updated it with a new variable(boost_freq) to suit the governors ramping policy
1.4
Lots of code optimizations
AHB Overclocking for faster R/W operations[787 MHz and higher don't have this kind of overclocking because of instability)
New 652 MHz undervolted frequency
CPU Unaligned Access (much faster booting time because of better kernel decompression)
Buffer values updated from Samsung original sources(Triple Buffering, Camera)
SmartassH3 and KSM parameters tweaked for better battery life
1.5
CPU clocks rework
Modified AXI Bus to allow lower CPU frequencies
Added completely stable 68 MHz frequency
New undervolt settings (0-0-1-2-3-5-6-7)
Rewritten Badass CPU and GPU control driver to make more use of 68 MHz frequency
Tuned SmartassH3 to make more use of low frequencies
Added fully functional zCache and ZsmAlloc, backported from 3.4 kernel
1.5.1
Added LowBattery Powersave feature for Badass governor
Badass parameters are more performance biased now
Recalculated Frame Buffer Size for Triple Buffering
Clean-up(remove deprecated CPU governors)
1.6
Add newest Adaptive RED Net Scheduler from 3.4 kernel and make it default.
Replace Snappy Compression with LZ4 Compressor(this is the fastest compressor on the market)
Make our kernel probably the first 2.6 kernel to have these two features
1.6.1
Update LZ4 Compressor from original sources and make it fully functionable
1.7
Replace zRam XvmAlloc with the better ZsmAlloc integration
Update zRam from 3.0 drivers
Make zRam LZ4 decompressor work faster in the same CPU cycles
1.8
Add SIOPlus scheduler (finally something equal or better than deadline)
Add CPU Idle driver to support C4 Deeper Sleep state
Add Wheatley governor to make more use of the new C4 state.
Change Bootsplash
1.9
New governor: WheatleyPlus
Reworked scaling down logic for less calculation
Added BoostPulse interface
Linked BoostPulse to the touchscreen driver (now the governor can really "sense" a touch and boost the frequency after a specific time threshold)
Added Triphasic scaling up logic from Badass (Phase2 is 360 MHz and Phase3 is 480 MHz)
Fixed the Deep Sleep states verification for scaling
Added GPU Control Driver
Added Sampling Down Momentum for dinamically changing the factor for scaling down
Updated OnDemand governor (it's pretty good at the moment)
Remove Badass and Lazy as they were deprecated
Link BoostPulse to the touchscreen driver for SmartassH3 and OnDemand
Optimize the CPU clock structure for WheatleyPlus
Update SIOPlus and add fluid tunables
Introduce Dynamic Cache Pressure
Revise Dynamic Writeback algorithm
Introduce Timer Slack Controller (aka Timer Coalescing, explanation below)
Deep Sleep tweaks
Backport OOM Killing algorithm from 3.8 kernel
Backport LowMemoryKiller and Timed GPIO drivers from 3.8 kernel
Add Whitelist feature to LowMemoryKiller (you can write PIDs of the processes you want to whitelist, in this file > /sys/module/lowmemorykiller/parameters/w_list ~ below you'll find the script for doing this at boot)
Android Binder update
CFS kernel scheduler optimizations
GPU driver optimizations and code cleanup
Make sure that the GPU turns off when the screen is off
Make the sleep states transitions faster
1.9.1
Finetune WheatleyPlus for better responsiveness
Optimize WheatleyPlus for overclocking on 652 MHz and 768 MHz
Fixed graphical glitches(hopefully)
1.9.2
Every bug fixed
Removed WheatleyPlus
Updated Interactive governor to the latest version from 3.8 sources
Add Dynamic Interactive governor (98% the same as Interactive, but it dynamically changes its parameters according to the load)
Dynamic PLL Overclock
Further undervolt until 768 MHz (the latter allows us to do this without losing performance)
Predefine minfree and adj values
Fully functional App Whitelist (example script here)
Forced unaligned access
Fast Charge (use this to enable it: FastCharge.apk - 1.29 MB) [Disconnect USB Cable - Turn ON - Connect USB Cable]
Timer Slack Controller: (this is a copy-paste from boype's thread)
What does the timer slack feature do?
Timer slacking aims to synchronize applications' and processes' CPU requests. The goal is to wake up the CPU less often in oder to save battery. What you need to know here is the following: waking the CPU up and putting it back to sleep again consumes power. Imagine that four apps wake the CPU up four times each in one second. While without timer slacking the CPU would be woken up 16 times, it is desirable to coordinate the wakeups. If done right, the CPU would wake up less often, effectively allowing power savings and longer sleep periods. This is what timer slacking does.
I have activated timer slacking only for background applications, so that everything else stays as responsive as you know it.
Apple has recently introduced this feature under the name 'timer coalescing' with their Mac OSX Maverick (link).
More information: How Apple does timer slacking ('Timer coalescing') (Scroll a little down to the diagrams)
LZ4 Compressor:
LZ4 is a very fast compressor, based on well-known
LZ77 (Lempel-Ziv) algorithm. Originally a fork from LZP2, it provides
better compression ratio for text files and reaches impressive decompression
speed, in the range and beyond 1GB/s per core (!), especially for binary files.
These speeds are scalable with multi-threading modes, quickly reaching
RAM speed limits on multi-core systems.
ROW I/O scheduler:
The ROW scheduling algorithm will be used in mobile devices as default
block layer IO scheduling algorithm. ROW stands for "READ Over WRITE" which
is the main requests dispatch policy of this algorithm.
The ROW IO scheduler was developed with the mobile devices needs in mind.
In mobile devices we favor user experience upon everything else, thus we want
to give READ IO requests as much priority as possible. The main idea of the ROW
scheduling policy is just that: - If there are READ requests in pipe - dispatch them,
while write starvation is considered.
Download:
AOKP/AOSP ICS:BadassKernel-AICS.zip - 4.78 MB
AOKP:BadassKernel-AOKP.zip - 4.79 MB
CyanogenMod 9.2BadassKernel-ICS.zip - 4.76 MB
AOSPA:BadassKernel-PA.zip - 4.79 MB
CyanogenMod 10:BadassKernel-CM10.zip - 7.03 MB
CyanogenMod 10.1:BadassKernel-JB.zip - 4.79 MB
Various tweaks
Script for adding apps to LowMemoryKiller's whitelist:Whitelist
(you have to edit it to add your own apps, then move it to init.d and set correct permissions. right now you can only add one app, I'll fix this in the next version)
Script to enable zRam with optimized disksize for Fit: View attachment zRamV2.zip (flashable zip) [UPDATED]
Jeeko's PureAudio fixed for CM10.1 and AOKP: View attachment PureAudio__1.0_-_STUDIO.zip [ Please thank Jeeko for this awesome mod. ]
NOTE: This version of PureAudio is compatible with absolutely any equalizer or player.
If you have Titanium Backup installed, in the menu you'll find an option named "Integrate sys Dalvik into ROM". Use it.
This is something like odexing your system, but keeps the classes.dex files inside the apps. Don't worry if you don't have a lot of system space, Titanium will odex as much as it can until the free space runs out.
TIP: So in latest version of CrossBreeder, the OP added some system tweaking which interferes with our kernel. So I edited those parts to match our settings and device limits.
If anyone wants to install CrossBreeder:
-First uninstall by flashing this file: CrossBreeder_Uninstall_7.2.13.zip - 943.12 KB
-Then install this custom version: CrossBreeder_7.2.13-Badass.zip - 1.59 MB
Sources:
GitHub
Credits:
A_U for compiling the base kernel
franco for the various tweaks I cherry-picked from his source
androidarmv6 for fixing bluetooth
Ezekeel for his Wheatley governor
How to install the kernel?
Subdin said:
How to install the kernel?
Click to expand...
Click to collapse
Flash the zip.....
Sent from my GT-S5670 using xda premium
droider007 said:
Flash the zip.....
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
to install cm(9,10,10.1)
and just flash the kernel??????
CM 10.1 kernel isn't a zip...
NM99 said:
CM 10.1 kernel isn't a zip...
Click to expand...
Click to collapse
rename it to .zip
---------- Post added at 11:50 PM ---------- Previous post was at 11:49 PM ----------
droider007 said:
rename it to .zip
Click to expand...
Click to collapse
but don't try its not booting.......wait for a fix....:good:
I'll wait for the fix.
NM99 said:
I'll wait for the fix.
Click to expand...
Click to collapse
Changed the ramdisk, now it should boot. All versions are flashable zips, you don't have to reinstall the ROM for installing a kernel.
Keep a flashable zip with your original kernel on sd in case this doesn't boot.
I flashed kernel for CM10.1 RC6 of erikcas and it works without problems for me.
ZmisiS said:
I flashed kernel for CM10.1 RC6 of erikcas and it works without problems for me.
Click to expand...
Click to collapse
Alright, good to hear that.
Thanks for reporting. This means that the other versions will work too.
alin.p said:
Changed the ramdisk, now it should boot. All versions are flashable zips, you don't have to reinstall the ROM for installing a kernel.
Keep a flashable zip with your original kernel on sd in case this doesn't boot.
Click to expand...
Click to collapse
I'll be sure to flash it soon.
Just a question, I flashed the tweaks on this thread and Fly-On Scripts.. After flashing the kernel, do I need to flash them again?
---------- Post added at 06:33 PM ---------- Previous post was at 05:34 PM ----------
Just a little update, just flashed the kernel. No problems at all, it feels smooth as it can be. I'm running it 68-768Mhz with no problems.
Wake up in the morning..
Open xda (5670 forum)..
see something new anddd..
ohmyglob! FINALLY! SIR ALIN.P's KERNEL!
Best morning news and goodness in the morning! ooohh yeah! Time to test this baby out! By the way, I'd love to see your ROM here sir Alin! THANKYOU!
Kernel works perfectly at 768Mhz, something that I couldn't OC to before. I tryed to OC to 806Mhz and my Fit rebooted automatically. :lol:
Now I'm trying to use 787Mhz to see what can happen.
EDIT: Can't OC over 768Mhz. At 787 the G-Fit keeps running for 15 mins until it locks at whatever it's doing for forever and from 806 onwards it just reboots automtically. At least that's what my G-Fit does, don't know what about the others. Just sharing my personal experience so far with the Badass Kernel.
NM99 said:
I'll be sure to flash it soon.
Just a question, I flashed the tweaks on this thread and Fly-On Scripts.. After flashing the kernel, do I need to flash them again?
---------- Post added at 06:33 PM ---------- Previous post was at 05:34 PM ----------
Just a little update, just flashed the kernel. No problems at all, it feels smooth as it can be. I'm running it 68-768Mhz with no problems.
Click to expand...
Click to collapse
The kernel installs in its own partitions, it doesn't mess with the /system or /data. So you don't need to reinstall anything, only the kernel will be modified when flashing.
About the OC, the kernel uses the same clocks as the stock kernel, with a little tweaks for stability and battery life(Undervolt and refined AXI bus). I was expecting 768 to be the maximum, that's a physical limit. I can't do anything about it. Anyway, I added 748 MHz in case 768 is unstable for some of you.
Jhayzt said:
Wake up in the morning..
Open xda (5670 forum)..
see something new anddd..
ohmyglob! FINALLY! SIR ALIN.P's KERNEL!
Best morning news and goodness in the morning! ooohh yeah! Time to test this baby out! By the way, I'd love to see your ROM here sir Alin! THANKYOU!
Click to expand...
Click to collapse
Thank you too!
I just ported my ROM too. The no-gapps might still have some problems, not sure about it. I had only two reports and 30 downloads, maybe the errors are /data related and individual.
I'll be away for two weeks to prepare for my exams, so I'll answer your questions then.
alin.p said:
The kernel installs in its own partitions, it doesn't mess with the /system or /data. So you don't need to reinstall anything, only the kernel will be modified when flashing.
About the OC, the kernel uses the same clocks as the stock kernel, with a little tweaks for stability and battery life(Undervolt and refined AXI bus). I was expecting 768 to be the maximum, that's a physical limit. I can't do anything about it. Anyway, I added 748 MHz in case 768 is unstable for some of you.
Thank you too!
I just ported my ROM too. The no-gapps might still have some problems, not sure about it. I had only two reports and 30 downloads, maybe the errors are /data related and individual.
I'll be away for two weeks to prepare for my exams, so I'll answer your questions then.
Click to expand...
Click to collapse
For 768 MHz which governor, minimum and maximum CPU frequency?
camera!
video camera dont work on cm9!
with this kernel!
[/url][/IMG]On CM10.1 RC6 of erikcas all works except Skype.
Please answer the question: For 768 MHz which governor and minimum CPU frequency?
ZmisiS said:
On CM10.1 RC6 of erikcas all works except Skype.
Please answer the question: For 768 MHz which governor and minimum CPU frequency?
Click to expand...
Click to collapse
Governor....smartassH3 or badass
Min freq......122 or 68.....
Sent from my GT-S5670 using xda premium
alin.p said:
Alright, good to hear that.
Thanks for reporting. This means that the other versions will work too.
Click to expand...
Click to collapse
Thanks for such a speedy update... :good:
Hey guys, a new version of Crossbreeder has been released.. Can I install it or it can give problems with the kernel?
Introduction
This kernel is based on Smartpack kernel by @sunilpaulmathew. The kernel has undergone many changes to further improve both battery life and performance from already what was an excellent kernel for the S5.
Features
CPU Governors - yankactive, impulse, ondemandplus, adaptive, smartmax, smartmax_eps, wheatley, nightmare, alucard, intellidemand, intelliactive, zzmoove, interactive, conservative, ondemand, powersave, lionheart, performance
IO Schedulers - zen, sioplus, deadline, cfq, bfq, tripndroid, vr, row, noop, fifo
GPU governors - simple_ondemand, msm_adreno_tz and more
Hotplugs - mpdecision, intelliplug
TCP algorithms- All enabled. Westwood default for best performance.
Franco Sound Control
Dynamic Hotplug
Dynamic Fsync
LCD notifier
Disabled CRCs for performance
Linaro 7.2 Toolchain
Supported Variants
klte: SM-G900F, SM-G900V, SM-S902L
kltekor: SM-G900K, SM-G900L/SM-G900S
kltedv: SM-G900I ,SM-G900P
klteduos: SM-G900FD, SM-G900MD
No other variants are supported
Download
AFH - https://www.androidfilehost.com/?w=files&flid=240642
How to install
1. Ensure you are not running a custom kernel already (can conflict)
2. Flash my kernel
3. Wipe dalvik/cache
4. Reboot
Credits
Sunilpaulmathew - For kernel base and scripts
Linus Torvalds - For linux kernel
Lord Boeffla - For many tweaks and patches
nathanchance - For Linaro TC
faux123 - For intell* governors/hotplugs
alucard12 - For alucard hotplug
haggertk - For LOS14.1
franciscofranco - For franco sound control
Source:
Github - https://github.com/gsstudios/LOS-plus-kernel
Changelogs
See github page
Kernel Adiutor Suggestions
Battery Savings
CPU Governor - Nightmare
Hotplug - Intelliplug
IO sched - ZEN
GPU governor - simple_ondemand
Performance
CPU Governor - Ondemandplus
Hotplug - Intelliplug
IO sched - ZEN
GPU governor - msm_adreno_tz
You can change around these settings or add your own if you like
What app do I use to tune this kernel?
I highly recommend Kernel Adiutor. It's free, open-source and is on the Google Playstore.
When will feature xyz be added?
I'll add it if I think everyone will benefit from this change, and that also means that I must find this feature to be useful.
Donations
While I am glad people want to help with the development through donations, I am generally opposed to accepting any form of donation.
Microphone not working?
Make sure the microphone gains in the sound section of KA is > 0. Alternatively, ensure that apply on boot has been unticked.
How do I use intellithermal?
In the CPU hotplug tab in KA, disable the two sliders underneath the slider for intellithermal. Then you may switch on intellithermal.
How can I help with development?
If you see or encounter any issues, let me know on github or on an XDA post. If you want to help develop, you can easily fork this project on github, add your own changes, then submit a pull request.
I'm back into kernel development after taking a long break since maintaining Dorimanx kernel for the S5. :highfive:
I've just released my first build (v1) which I've tested for some time now. Please let me know if there are any issues with the usual bug report format (dmesg + logcat + description of issue).
I just like a give another special thanks to @sunilpaulmathew for allowing me to use his kernel as base and for being open to the opensource community
Enjoy
Good to see you back to Kernel development... :good:
It will be a good deal for our S5 users
and hope you will still be active in my thread...
Saber said:
I'm back into kernel development after taking a long break since maintaining Dorimanx kernel for the S5. :highfive:
I've just released my first build (v1) which I've tested for some time now. Please let me know if there are any issues with the usual bug report format (dmesg + logcat + description of issue).
I just like a give another special thanks to @sunilpaulmathew for allowing me to use his kernel as base and for being open to the opensource community
Enjoy
Click to expand...
Click to collapse
I'll try it, I just want perf fixes
Further testing has reveal that Faux sound control values don't stick after setting them in KA. This issue will be resolved in the next build.
Regards, Saber
Is this the kernal that was going to help with the RR issues? Thanks for this kernal.
BadToThePhone said:
Is this the kernal that was going to help with the RR issues? Thanks for this kernal.
Click to expand...
Click to collapse
If you mean the performance issues with Smartpack + RR, then yes. However, it will take some tweaking it get it "buttery smooth".
Saber said:
If you mean the performance issues with Smartpack + RR, then yes. However, it will take some tweaking it get it "buttery smooth".
Click to expand...
Click to collapse
already noticing a HUGE difference in performance. It's phenomenal. Howcome I/O for internal is missing in KA
Does Faux audio interfere with V4A?
GeTex said:
already noticing a HUGE difference in performance. It's phenomenal. Howcome I/O for internal is missing in KA
Does Faux audio interfere with V4A?
Click to expand...
Click to collapse
I guess you mean internal IO scheduler? Works fine on my end. Maybe reflash kernel or try one of the modded KA apps.
As for faux sound control and V4A, I think you can have both, as long as you don't tune the values for faux sound (which BTW is broken until the next release).
Saber said:
I guess you mean internal IO scheduler? Works fine on my end. Maybe reflash kernel or try one of the nodded KA apps.
As for faux sound control and V4A, I think you can have both, as long as you don't tune the values for faux sound (which BTW is broken until the next release).
Click to expand...
Click to collapse
Internal I/O is missing from menu's, kernel clearly is flashed
good to know
GeTex said:
Internal I/O is missing from menu's, kernel clearly is flashed
good to know
Click to expand...
Click to collapse
Odd, I would imagine it would be an issue with KA unable to detect the paths required for IO tuning. Maybe problems with permissions? Any logs because I'm running out of ideas...
@Saber and @GeTex Can you please post your recommended settings? Battery is more important to me than performance. Would appreciate it very much.
BadToThePhone;75181281 [user=5811506 said:
@Saber[/user] and @GeTex Can you please post your recommended settings? Battery is more important to me than performance. Would appreciate it very much.
Click to expand...
Click to collapse
There's many ways to go about it, I cannot comment immediately and I'd rather work with @Saber first on a good configuration but so far I can recommend this
Change CPU gov to ondemandplus
Change CPU hotplug to intelliplug, change hytersis value to 4, change screen of freq to 10xx MHz, use profile balanced and touch boost on
Change internal I/O to sio or sioplus, readahead to 1024, external I/O to noop and readahead 2048, change swappiness to 30 and vfs cache pressure to 130, or keep 100 for neligable benefits, turn on KSM with an interval of 1000 or 500 for slightly better performance at cost of minor battery, make sure Zram is set to 420mb or less. Turn off the thermal drivers and use intellithermal on defaults
With a brand new battery I have 4hr10 screentime and 1d standby, that is with alot of background stuff such as 20 minute GPS pings and weather updates, wifi and data and GPS always on
Battery life isn't up to date yet, will need to test a few more days
I was previously using these settings. Do any of these still apply? Thanks
Cpu governor: nightmare
Cpuhotplug: intelliplug
Touchboost: on
Cpu threshold: 1250
Thermal: intellithermal on, vdd and corecontrol off
Gpu: adreno idler
I/o scheduler: zen
Sleep between scans: 1000ms
Power suspend mode: autosleep
Fast charge on
Fsync On
BadToThePhone said:
I was previously using these settings. Do any of these still apply? Thanks
Cpu governor: nightmare
Cpuhotplug: intelliplug
Touchboost: on
Cpu threshold: 1250
Thermal: intellithermal on, vdd and corecontrol off
Gpu: adreno idler
I/o scheduler: zen
Sleep between scans: 1000ms
Power suspend mode: autosleep
Fast charge on
Fsync On
Click to expand...
Click to collapse
No adreno idler in this kernel. Best to use power suspend mode hybrid for better battery life (uses display state + kernel sleep).
Edit: Also no UKSM. You can enable KSM if you like, but I personally don't need it.
BadToThePhone said:
@Saber and @GeTex Can you please post your recommended settings? Battery is more important to me than performance. Would appreciate it very much.
Click to expand...
Click to collapse
Please read my second post. Main goal of my profile is good battery + performance balance without that "lag" in RR. Change around the profile if you like to suit your taste (e.g. zzmoove instead of ondemandplus).
Saber said:
Please read my second post. Main goal of my profile is good battery + performance balance without that "lag" in RR. Change around the profile if you like to suit your taste (e.g. zzmoove instead of ondemandplus).
Click to expand...
Click to collapse
Is following your suggested settings plus what @GeTex recommended doing too much? Thanks alot
BadToThePhone said:
Is following your suggested settings plus what @GeTex recommended doing too much? Thanks alot
Click to expand...
Click to collapse
It's a little more extra compared to my recommendations, but either is fine for good balance.
When turning on intellithermal do I have to turn off vdd and corecontrol? Also do I have to turn off mpdescion?
****Ares-Kernel****
****By****
****The~Skater~187****
This kernel is a combination of SmartPack/Boeffla-Venom Samsung Galaxy S5 Lineage OS kernel, with some tweaks and additions from around the net. I have decided that since SmartPack was EOL and with sunilpaulmathews ok, I would just combine our two kernels (since fbs has Boeffla-Kernels covered) to make it easier for me to maintain his work and my own.
/* DISCLAIMER! *\
*I am not responsible for any damage to your device*
* Everything you are doing on your device is at your own risk*
*Don't forget to make a back up before flashing*
~~~~~~~~~~~~~~~Flash at own risk~~~~~~~~~~~~~~~~~~
/* Supported devices *\
klte: SM-G900F, SM-G900AZ, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
kltekor: SM-G900K/L/S
kltedv: SM-G900P/I
klteduos: SM-G900FD, SM-G900MD
kltekdi: SCL23
/* Compatibility *\
DO NOT FLASH OVER CUSTOM KERNELS!
This kernel is only meant to work on Lineage-OS 15.1/16 and nothing else. However, it may work on other LOS-15.1/16 (and AOSP) based Oreo/Pie ROMs
This kernel will NOT work in Samsung Stock and other TW ROMs.
/* How-to-Install *\
*Download Kernel*
1. Go to recovery (TWRP recommend)
2. Flash Kernel
3. Reboot and enjoy
/* Incorporated SmartPack Features *\
Build from latest Lineage OS source code.
Built using latest GCC-8.x.
Anykernel for compatibility with maximum devices.
Linux Kernel version is updated to 3.4.113
Kernel tweaker app recommend: SmartPack-Kernel Manager (Please note: official Kernel Adiutor is NOT fully compatible with this kernel).
Added features include...
CPU voltage control
CPU Freq Gov: INTELLIDEMAND, INTELLIACTIVE, SMARTMAX, LIONHEART, NIGHTMARE, ADAPTIVE, ALUCARD, ZZMOVE, etc.
(for those who want to use zzzmove, I strongly suggest to carefully read this forum post by @Saber)
CPU hotplugs: Lazyplug, Alucard, and mako hotplug.
Full control over AC, USB and Wireless charging rate in SmartPack-Kernel Manager (Default charging rates: AC: 1800 mA; USB 700 mA; Wireless: 900 mA).
Boeffla Sound to control speaker and headphone volume.
(for official KA users, follow these instructions by @Exzu to create respective custom controllers for Boeffla Sound and Fast Charge.)
Adreno_Idler
CPU Input boost (configurable in SmartPack-Kernel Manager)
IO schedulers: FIOPS, SIO, VR, ZEN, FIFO, TRIPNDROID.
TCP congestion algorithms: Westwood, reno, cubic etc.
FRandom
Dynamic sync control 2.0
Boeffla Generic Wakelock Blocker
268 MHz CPU underclocked frequency cycle
Additional 27 MHz GPU frequency step (idle frequency)
KCAL v2
SELinux "Enforcing" by default (can be switched to "Permissive" in SmartPack-Kernel Manager)
a lot more...
/* Incorporated Boeffla-Venom Features *\
*Enable OC to 2995:
-DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. (I AM NOT RESPOSIBLE FOR YOUR DEVICE)
*Fast Charge
*ZZmoove adjusted to acommodate Overclocking (Thanks to Legitsu)
*Tweak bandwith on higher OC steps (Thanks to ktoonsz)
*Deadline I/O Tweaks (Ktoonsz)
*Fix memory leak with sysfs when stats table are freed (Ktoonsz)
*Bump up Max Voltage (Adjusted for higher OC) (Ktoonsz)
*Dirty Writeback Tweaks
*Increased VM_MAX_READAHEAD to 512 (default)
*Increased default entropy levels (both read and write)
*Optimized Kernel Samepage Merging
*QuickWakeup (Thanks CrazyGamer)
*PowerSuspend (Thanks Faux123)
*Cortex_A15 Optimizations (Fusion-Rom Dev Team)
*Slimbus Overclock (Ktoonsz)
*Slimbus Optimized Overclocking Of Master Component (CrazyGamer)
*VFP Tweaks (Ktoonsz)
*EXT4 Tweaks(Ktoonsz)
*GPU Overclocked up to 657 (Ktoonsz)
*Disable Swap Readahead
*Increase Maximum Swappiness
*Kernel mode neon (ShinySide)
*Disable Direct Reclaim File Pages
*Enable Unaligned Capability For ARM (CrazyGamerGR)
*Update min-default adreno frequency to be 200 MHz (kholk)
*Fixed memory entry leak when calling Adreno Convertaddr (Shubhraprakash Das)
*Changed clock rates to 19.2 MHz (Faux123/Qualcomm)
*Optimized Sched/Fair a bit (Faux123)
*Applied many new compiler optimizations (Synergy kernel Team & Decimalman)
*Zswap: Uses LZ4 now (if available)
*Support for LZ4-compressed kernel
*Fix memory leak in Mass Storage
*Added back Intellithermal V.2 Thermal Engine (for those who prefer it)
*Modified LowMemoryKiller (fbs)
/* Downloads Can Be Found Here *\
https://app.box.com/s/nx7nuf7vb2eubd5sfrr5rerjsatcp42i
/* Special note to Korean S5 users *\
(Thanks to sunilpaulmathews defconfig files)
Flashing this kernel after AOSP/LOS based Oreo/Pie ROMs originally build for the klte (SM-G900F) variant SHOULD allow the use of those ROMs on SM-G900S/K/L.
/* Acknowledgements *\
@haggertk for LineageOS for Galaxy S5
@Lord Boeffla
@franciscofranco
@Sultanxda
@arter97
@faux123
@CrazyGamerGR
@Saber
@nathanchance
@ZaneZam
@osm0sis for AnyKernel project
@Grarak for Kernel Adiutor
@sunilpaulmathew
@justjr for SmartPack efficiency profile
@ktoonsez
@KazuDante
@fbs
@kholk
@decimalman
@Synergy Kernel Team
Many other XDA developers
XDA:DevDB Information
Ares-Kernel, Kernel for the Sprint Samsung Galaxy S5
Contributors
The~Skater~187, sunilpaulmathew
Source Code: https://github.com/187MoD/Ares-Kernel
Kernel Special Features: Boeffla-Venom + SmartPack Kernels
Version Information
Status: Beta
Current Beta Version: Beta-v1.6
Beta Release Date: 2019-02-15
Created 2019-02-15
Last Updated 2019-08-26
***Ares Kernel Changelog***
~~~~~Beta-v1.7~~~~~
*Up-to-date with Lineage-OS source as of 01.01.2020
*Update Intelli-plug to version 3.9 (Compliments of Pascua28)
*sound: Compiled with -Os optimization (Compliments of Pascua28)
*A few other optimizations
~~~~~Beta-v1.6~~~~~
*Up-to-date with Lineage-OS source as of 08.25.2019
*Compiled using Bleeding-Edge Toolchain 9.2
*Cortex A-15 MSM-memutil optimizations for better memory performance
*GPU compiler optimizations
*Enable: Frontswap
*Enable: Runtime compcache
*Removed un-supported SOC features (Thanks pascua28)
*Fix possible memory leak in slub.c (Thanks pascua28)
*Add Missing xor-neon file
*Compiled with many new compiler optimizations
*Plus more
~~~~~Beta-v1.5~~~~~
*Up-to-date with Lineage-OS source as of 07.15.2019
~~~~~Beta-v1.4~~~~~
*Up-to-date with Lineage-OS source as of 05.27.2019
*Compiled with "Bleeding-Edge-Toolchain" 9.1
*Compiled with 03 compiler optimizations
~~~~~Beta-v1.3~~~~~
*revert: disabled "CAF" cpu policy save code (Fixed cores not scaling properly)
*MSM Limiter updated
~~~~~Beta-v1.2~~~~~
*Up-to-date with Lineage-OS source as of 03.19.2019
*reverted to stock Lineage-OS LMK (Low Memory Killer)
*bumped OC up to 3072 -DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. I AM NOT RESPONSIBLE FOR YOUR DEVICE!)
*bumped up voltage overhead to hopefully help stabilize new OC step
*added Intelliplug_hotplug driver (Now default hotplug service)
*added Touchboost driver (adjusted for 3072 oc)
*added MSM CPU Limiter (adjusted for 3072 oc)
*enabled Arch Power
*added the ability to Toggle Arch Power And Sleepers (compatible with SmartPack Manager)
*disabled "CAF" cpu policy save code (Faux123)
*added msm_mem_utils for added memory performance
*disabled constant spam in dmesg from 'undefined instruction' print statement in traps.c
*ZZmoove: adjusted to acommodate Overclocking to 3072
*added Boeffla-compiled In-Kernel Busybox
*some other things
~~~~~Beta-v1.1~~~~~
*Up-to-date with Lineage-OS source as of 03.02.2019
*Ares-Kernel boot script: update default profile settings (credits: justjr)
*import Core Control fix (sunilpaulmathew)
*import "Hotspot" fix (sunilpaulmathew)
*added a compatible version of "Tuned" LowMemoryKiller (fbs)
*added support for lz4 compressed kernel
*added some compression tweaks to help with boot performance
*driver/char: add missing frandom commits
*fs/sdcardfs/mmap.c: add AIO optimization flag compatibility fix up
*kernel/power: add missing quickwakeup commit
*Optimized ARM RWSEM Algorithm (Faux123)
*Tuned thermal management a bit
*Some other stuff
~~~~~Beta-v1.0~~~~~
-Initial Merge of SmartPack/Venom Sources
*Synced With latest LineageOS Sources as of 02.13.19
*Built with Latest 8.2.1 toolchain using SunilPaulMathews build Framework
*Compatible With Kernel Auditor & Should Be Compatible SmartPack-Kernel Manager
*Enable OC to 2995:
-DISCLAIMER: (You Must Adjust Voltages for you OWN specific device on higher OC steps. I AM NOT RESPOSIBLE FOR YOUR DEVICE)
*Boeffla Sound
*Fast Charge
*ZZmoove: adjusted to acommodate Overclocking (Thanks to Legitsu)
*Enable 268 mhz underclock (Thanks to SunilPaulMatthew)
*Tweak bandwith on higher OC steps (Thanks to ktoonsz)
*Tweak deadline: Allow 0ms deadline latency, increase the read speed (Ktoonsz)
*Set audience sleep delay to 0 to fix delay upon making phone calls
*Async I/O latency to a ssd greatly increased (34% gain,kleikamp & Ktoonsz)
*Fix possible memory leak with sysfs when stats table are freed (Ktoonsz)
*Bump up Max Voltage (Adjusted for higher OC) (Ktoonsz)
*Dirty Writeback Tweaks
*Increased VM_MAX_READAHEAD to 512
*Increased default entropy levels (both read and write)
*Optimized Kernel Samepage Merging
*QuickWakeup (Thanks CrazyGamer)
*PowerSuspend (Thanks Faux123)
*Cortex_A15 Optimizations (Fusion-Rom Dev Team)
*Add Missing Graphite Define (Ktoonsz)
*Slimbus Overclock (Ktoonsz)
*Slimbus Optimized Overclocking Of Master Component (CrazyGamer)
*VFP Tweaks (Ktoonsz)
*EXT4 Tweaks(Ktoonsz)
*GPU Overclock up to 657 (Ktoonsz)
*Disable Swap Readahead
*Boeffla wakelock blocker (Thanks to sunilpaulmathew & franciscofranco)
*Increase Maximum Swappiness
*Kernel mode neon (ShinySide)
*Disable Direct Reclaim File Pages
*Enable Unaligned Capability For ARM (CrazyGamerGR)
*Update min-default adreno frequency to be 200 MHz (kholk)
*Fixed memory entry leak when calling Adreno Convertaddr (Shubhraprakash Das)
*Change clock rates to 19.2 MHz (Faux123/Qualcomm)
*Optimize Sched/Fair a bit (Faux123)
*Applied many new compiler optimizations (Synergy kernel Team & Decimalman)
*Zswap: Uses LZ4 now (if available)
*Support for LZ4-compressed kernel
*Fix memory leak in Mass Storage
*Alucard, LazyPlug & Mako Hotplugging
*Enabled VNSWAP
*Added back Intellithermal V.2 Thermal Engine (for those who prefer it)
*Modified LowMemoryKiller (fbs)
# All Changes
# Signed Off
# By
# The~Skater~187
Reserved
~~~~~~~~~~~ Please note~~~~~~~~~~~
If you need support, please supply the following or support will not be given:
*Device Variant
*Current Rom & Android Version
*Bootloader & Baseband version
*Recovery & Version
*Recovery Log
I can't help if the only details given are "It didn't work" or "I can't flash this".
One More For Good Measure
YES.!!!!
sdfat code have syntax errors, aren't even compiling here.. humm
ok, fixed it and stealed it
Thanks for ur good kernel. Flashed on haggertk android pie no problem so far. At first I was getting random reboots,it caused by my magisk modules. I disable them and the problem fix. Thanks again.
LKT magisk module on this kernel cause random reboots.
Thanks for your work
So I popped over to this thread you linked to from the Venom thread and want to make sure I'm clear. This kernel (Ares-Kernel) should not be used on a Resurrection Nougat based ROM? I think that Resurrection Nougat ROM is a Lineage 14 based ROM, correct? Or even though it is Lineage 14 based, can the Areas-Kernel still be used because it is based off Lineage.
Thanks for any clarification. Left this post in other thread to just to make sure I got it in right spot. Disregard which ever one is posted in wrong spot. Thanks.
awesome dude!!! thank you so much! i'm really glad that someone continues the smart-pack kernel!
:laugh: big, Big, BIG Thank you @The~Skater~187! Really appreciate your effort and dedication in helping to keep this old phone alive and competitive! :highfive:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as the tunable io_is_busy 0 to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
justjr said:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
Click to expand...
Click to collapse
I do apologize about the credit issue, I thought I had put your name in the acknowledgment section right before ktoonsz last night, as I noticed your name on a few of the files in the RamDisk. I will definitely straighten that out and thank you for pointing that out. You are correct, I so far have just synced SmartPack source, then started applying things from my other kernel for now. I wanted to get something up-to-date and stable out for you guys before I started diving deeper into other kernel related things.
As for the rest of your suggestions, I will look into them for sure. Feel free to p.m. me with any thoughts or other suggestions.
Sent from my kltespr using Tapatalk
The~Skater~187 said:
I do apologize about the credit issue, I thought I had put your name in the acknowledgment section right before ktoonsz last night, as I noticed your name on a few of the files in the RamDisk. I will definitely straighten that out and thank you for pointing that out. You are correct, I so far have just synced SmartPack source, then started applying things from my other kernel for now. I wanted to get something up-to-date and stable out for you guys before I started diving deeper into other kernel related things.
As for the rest of your suggestions, I will look into them for sure. Feel free to p.m. me with any thoughts or other suggestions.
Sent from my kltespr using Tapatalk
Click to expand...
Click to collapse
Many thanks!
On other news, I was getting some random reboots, and found out that it was because of my undervolt settings. It's super weird, because they never gave me any problems since 3~4 months with the smartpack kernel, and it should be a setting particular to my specific device/cpu, and have the same limits across any kernel. I used the same across lots of roms, and different versions of smartpack, for nougat, oreo and pie, so, I hope you can see why I find this very weird.
But, I don't know if it's actually a 'bug', I will find some time to fine tune it, raise some voltages to see where I can go with Ares kernel without crashing. For now I'm using the default voltages.
justjr said:
Many thanks!
On other news, I was getting some random reboots, and found out that it was because of my undervolt settings. It's super weird, because they never gave me any problems since 3~4 months with the smartpack kernel, and it should be a setting particular to my specific device/cpu, and have the same limits across any kernel. I used the same across lots of roms, and different versions of smartpack, for nougat, oreo and pie, so, I hope you can see why I find this very weird.
But, I don't know if it's actually a 'bug', I will find some time to fine tune it, raise some voltages to see where I can go with Ares kernel without crashing. For now I'm using the default voltages.
Click to expand...
Click to collapse
I did do a bit of an overhaul on the voltage table when I added the higher oc steps, due to the fact that on my other kernel lower voltages stock we're causing problems and random freezes.
Sent from my kltespr using Tapatalk
Yeah, I'm sure you know, undervolting need to be done step by step, making sure the lowest you can go, device specific, so risking repeating myself, same voltages should probably 99,99% of the time works across any kernel/rom on a given device. I don't think it is the undervolt anymore.
It took a while but I still had some reboots with default voltage, once I was finally able to press up and home right after it, so it rebooted directly to TWRP and I copied the last_kmsg, it's attached, all configs were on default. I hope it helps to find out what it may be.
I'm back on smartpack for now, cause the same setup and profile runs without no problems, so I think it should not be a problem just on my end, is it? Anybody else?
Fun fact, I was are able to dirty install smartpack kernel over ares and vice-versa and it detected and updated itself without any problems.
I'm able to go kinda low here with no crashes:
660
670
680
690
700
710
720
730
745
750
775
795
825
865
925
965
990
1005
1035
1060
@The~Skater~187 edit: oh, I just noticed, there's no option to input 268 MHz voltage. My voltages are getting placed on the wrong frequency because of that, found the problem!
I recovered the backup I just made before installing the kernel, I had installed the shushified bootleggers 3.0 on top of the unshushified 3.0, they are the same rom except for official (shushified) status, but anyway, that may be the cause of some of my problems, adding up to the 268 missing voltage that was overlooked by me.
After that I installed Ares kernel again with no undervolt and gone to sleep. Woke up today, and no reboots, then I was trying to test undervolting it and found out about the missing 268 voltage, so every previous voltage I used was getting used on 1 clock step above, so, not enough power for sure.
Just put my exactly same volts on their correspondent freq and no reboots until now!
It also seems that Core Control is staying enabled and VD Restrictions is disabled correctly now too. So, if you experience the same you may disregard it as well.
Thanks for this!!
Great so far, this with Pie ROMs is the best battery life I've had since stock.
4-5 hours sot, 7h active, 12h idle..(gsam stats) on this original 2800mah. I've gone from 4-5 charges a day to 1-2.
And kernel brightness control keeps the flickers away.
Edit: did notice both vdd and core thermals being active, didn't cause any overheating/reboots (i often run cpu info as overlay) but I stuck with core control only to be safe. It doesn't stick after reboot.
S5 klte
Latako said:
Edit: did notice both vdd and core thermals being active, didn't cause any overheating/reboots (i often run cpu info as overlay) but I stuck with core control only to be safe. It doesn't stick after reboot.
S5 klte
Click to expand...
Click to collapse
Yeah, after some further analysis, I came to find out exactly the same.
After a reboot both VDD and CC come back up, and I have to do a little dance, like, disable vdd and cc, enable intellithermal, then enable only cc, or something like that, then it will stick with only cc until the next reboot.
Ok, so I decided I'm going keep an "unofficial" SmartPack kernel going (nothing more than source updates will be applied) as well as my off shoot kernel project. I will have it available for you guys tomorrow evening.
Sent from my kltespr using Tapatalk
justjr said:
Hey, good work mate!
Thanks for it, we were orphan but you came and adopted us, LOL, kidding.
Just some thoughts on it.
I've found that, on thermal tab, vd restriction cant be disabled while core control is enabled. That used to happen on smartpack kernel but sunil get rid of it, maybe he can help. They are not made to be active together and can make the phone super slow and prone to crashes when it gets hot and they both kick in.
I also couldn't help to notice it's using my efficiency profile as defaults (on signature), and it's awesome, they work great don't they? Haha. I assume you grabbed it with the smartpack source code, since sunil's kernel used my profile as defaults.
There are some things that are outdated thought, specially page-cluster should be back to 0 on virtual memory as it is also prone to failures (apps don't working properly, like, a black screen without responses, based on my experiences) and crashes, min_sample_time is 0 and should be 40000 (one of the interactive governor tunables), which is an overlook by myself on an early release of my profile but fixed on the latest one already. I would recommend this small changes on the defaults, as well as the tunable io_is_busy 0 to let multicore power saving disabled.
I'm glad that you're also using it but I would also like to ask proper credits for it, I know, is not code, but demanded me months of studying and testing to get it almost where I wanted! There's a little history on the thread on my signature.
Click to expand...
Click to collapse
So is it possible to use your profile without any errors?