Database Info

[KERNEL][GB SENSE][05/10-2011]tristan202-gb-desire v05 (OC/UV/HAVS/BFS/CFS/V(R))

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.

[KERNEL][DEFUNCT]CM10/CM9/AOKP Kernel v6.3.6 [8/23] - UV/OC/GPU-BLN-Governors

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

[KERNEL] [DISCONTINUED] [06/15/14] AURORA R11v2

Aurora Kernel - N900xxx TW
This kernel is intended for battery-saving with keeping maximal possible performance
based newest NE6 sources
Linux 3.4.93 Update
Optimized Cortex-A15 4.10 LINARO Toolchain
see Features for details
​
Features:
- based on newest NE6 sources
- Linux upstream patches to 3.4.93
- SELINUX permissive
- Synapse support
- init.d support
- OC up to 2.8GHZ
- GPU OC from Snapdragon 801 (up to 587MHz)
- complete dts based kernels Voltage control by faux123
- IntelliPlug driver (for mpdecision replacement) by faux123
- IntelliThermal control driver (better than stock thermal control) by faux123
- Hardlimit CPU control interface by yank555:
- TouchWake by yank555
- PowerSuspend driver by yank555 with default set to hybrid-mode (autosleep and panel hook)
- FauxSound
- UKSM
- FastCharge Support
- LED Control
- mdnie Control by wootever
- Many governors: nightmare, dancedance, intelliactive, intellidemand, uberdemand, wheatley, smartmax, smartmax_eps, lionheart, pegasusq, darkness, hyper, badass, abyssplugv2, adaptive, conservative, ondemand, userpsace, powersave, interactive, performance
- More schedulers: noop, deadline, row, cfg, bfq, fiops, sio, zen
- enabled all TCP congestion controls: veno, westwood, cubic, reno, bic, highspeed, hybla, htcp, vegas, scalable, lp, yeah, illinois
- TCP congestion control default to veno
- new ARMv7 l2 cache
- Filesystem support: Ext2, Ext3, Ext4, FAT32, NTFS, USB OTG, exFAT with many fixes and optimizations (AIO, etc...)
- added multiple compression support for example LZ4, many patches
- F2FS support
- faster glibc
- frandom
- faster crypto libs
- Kernel XZ
- Ramdisk LZ4
- many fixes, updates, patches and enhancements from many sources
- many I already forgot
Check Synapse and thread to know all features
Changelog:
this post
Synapse profiles:
this post
DOWNLOADS
Direct downloads, look at my hosting:
mojosmirror.com
Downloads @ dev-host
​
Source: Github
Credits and many thanks to:
Much thanks to faux123 and yank555 for their great kernel
thanks to wootever for having always nice and useful commits
thanks to Imoseyon for having always nice and useful commits, too
thanks to civato for helping me starting here with studying his code
thanks to Myfluxi, labodj and Cl3Kener for commits
thanks to UpInTheAir for all his work with his Synapse interface
thanks to GuneetAtwal for some single picks
thanks to franciscofranco, zamcum, ZaneZam, CM-team, Codeaurora, ... and everyone else I forgot!
PM me, if you find your work not mentioned here
XDA:DevDB Information
Aurora Kernel Note 3, Kernel for the Samsung Galaxy Note 3
Contributors
MojoManagement
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R11v2
Stable Release Date: 2014-06-15
Created 2014-05-09
Last Updated 2014-08-29

Reserved

Reserved

Changelog
R11 (aka Synapse release)
NOTICE:
Due to heave Synapse changes again, I recommend to clear Synapse data, before you flash
If you feel unsnappy, raise Touchboost values, completely set both down to 300MHz at init
Synapse settings added & reworked (spent whole day into Synapse primarily)
Synapse can now make a flashable zip from your backup profile to share with others (look under tab Synapse)
Removed some sound pre-settings and removed FauxSound control for now to prevent still unknown issues
a few more fixes
R10 (beta)
NOTICE:
I recommend to clear Synapse data!!!
Synapse should now have enough options for daily settings
So please dont mix apps for setting kernel features
Synapse settings added (very hard work.....half day wasted here...)
S-Browser crash fixed on S5 ports
Sound issues fixed and quality should be improved
completely switched to UKSM now
a few more fixes and patches from different sources again
PS:
Please dont complain about voltage control in Synapse
If you want to experiment with voltages, you can set them one by one yourself
R9 (beta)
NOTICE: this will break some of Faux Control App functions, especially frequency setting, until Faux updates
If you dont want to run a beta, stick with R8 until stable release
There is currently not voltage, thermal, screen, zswap control in Synapse!
update to Linux 3.4.92
Synapse is back (but not everything is implemented), check yourself, big thanks to UpInTheAir, which made a very detailed Synapse layout, which I used as base
Hardlimit Interface update to 2.0a, you can now set screen on and screen off max/min frequencies separately, wakeup kicks, touchboosts, DVFS lock... check Synapse
GPU OC with Snapdragon 801 values (up to 587MHz)
Ramdisk is now LZ4 compressed (need to check kernel for LZ4, too)
Led Control updated to V1.2
IntelliPlug updated to newest version
Logger can be enabled/disabled through sysfs interface
many fixes and patches from different sources again
R8
finally working NE6 base with all known features
R7
updates base to NE6
same as R6
R6
switched to faux123-yank555 kernel as new base
over 300 commits added, patches, fixes, enhancements, etc...
see features
r5
lower power frequency 268,8MHz should work now as expected
lowered voltage for 268,8MHz (its really low, report if unstable)
new govs: lagfree and smartassv2, both tuned
updated and optimized fiops scheduler (which I recommend for internal)
optimized BFQ scheduler (which I recommend for external...)
linux update to 3.4.91
CIFS support (experimental)
enabled ksm (experimental)
swap support
updated toolchain to Linaro 4.9.1 05/2014
LZ4/LZO updates
some sound patches
many arm patches
some memory patches
more I forgot ...
r4
more fixes and enhancements
more govs: intelliactive, abyssplugv2, conservativex, adaptive
Dynamic FSYNC is back
permanent async FSYNC from HTC
PowerSuspend updates: hooked to AutoSleep and Panel, first sleep hook wins
experimental low power frequence
zen scheduler added
few more things
r3
over 60 fixes, patches and enhancements since r2
LZ4
crypto optimizations
faster glibc
very fast random generation (10-50 times faster)
gpu patches
linux update
many more
r2
over 50 fixes, patches and enhancements at all from beta
support for N900T
updated busybox (problems fixed)
updated ramdisk
mpdecision improved (also recommend Intelli Hotplug)
more compiler improvements
scheduler patches
dynamic fsync disabled (more later)
cpu patches for msm
enabled last kernel message
many more

Community profiles for Synapse:
How to use shared profile?
Flash shared profile in recovery
Reboot to system
OpenSynapse
Go to tab "Synapse"
Check if last backup says "flashed" at the end (time buggy at the moment sorry)
Press "Restore & Close Synapse"
Open Synapse
Press X[ Cancel/B] at the top to use restored settings (if you press "✓ Apply" your last settings will be restored)
R11:
gianton:
Here's my current setup I'm testing on r11. It's more for battery saving, if you play lots of games set the governor to intelliactive.
Click to expand...
Click to collapse
Link to post for download

Tried to download but link empty
Sent from my SM-N9005 using Tapatalk

Does it have ntfs r/w support?
Sent from Hacker OS

IzArsha said:
Does it have ntfs r/w support?
Sent from Hacker OS
Click to expand...
Click to collapse
Should work if I did not make any mistake

panjaby said:
Tried to download but link empty
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Downloads tested, all links should be working

Awesome kernel. Just one question, does it support GPU OC?

blogslogger said:
Awesome kernel. Just one question, does it support GPU OC?
Click to expand...
Click to collapse
Not yet, because I remember problems with frequencies are not used and also decrease performance with gpu set to 550
I just find the correspondending post by sorg
sorg said:
http://forum.xda-developers.com/member.php?u=3986004
About GPU overclock:
My phone is Samsung SHV-E330S, which is basically GT-N9005 in S4 case, so 99% hardware is the same.
According to my investigation in GPU overclocking, frequencies are handled fully inside RPM firmware. Frequencies in .dtsi files aren't used. RPM uses its own frequency table and cannot be changed from linux side. So, your GPU OC simply doesn't affect actual GPU frequencies. Linux GPU governor will think it uses new frequencies and will actually switch to a wrong frequency (because RPM will use hardcoded unmatched freq table) - so everything will go wrong (as you already noticed, probably).
I've monitored GPU/PLL hardware registers and saw, they work according RPM's table and not affected by .dtsi settings.
There is the only way to overclock SD800 GPU is by modifying PLL settings (as it was done for SD600 GPU). There is PLL for highest GPU powerlevel's frequency which used solely by GPU (just like in SD600). But performance increase is not so high as it could be from increasing RAM frequency OC (which i didn't manage to tweak yet).
P.S.: I don't know about N9005, but in E330S standard highest frequency is 550MHz (according to PLL settings) instead of 450MHz as advertized in MSM8974 (not AB or AC), although in .dtsi files max frequency is 450MHz. Good bonus from Samsung
Probably, in N9005 it's the same.
Click to expand...
Click to collapse
I might have a look into that in the future

Does it work with ND5 update

bhasg1007 said:
Does it work with ND5 update
Click to expand...
Click to collapse
Yeah, I am on ND5 rom with ND5 bl and NC2 modem

Downloaded Thanks for the reply will try now

Can I flash this kernel over lean kernel?
Tia
Sent from my SM-N9005 using XDA Premium 4 mobile app

Cool! A new kernel! gonna try it now and will be back with results in a day or two
Sent from my SM-N9005 using XDA Premium 4 mobile app

ghalib87 said:
Can I flash this kernel over lean kernel?
Tia
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Of course

MojoManagement said:
Downloads tested, all links should be working
Click to expand...
Click to collapse
Apologies. The fault must be on my end.
If I open the first link with chrome it goes blank with mojo wesite bit if I open the link directly with es downloader it downloads
Sent from my SM-N9005 using Tapatalk

MojoManagement said:
Not yet, because I remember problems with frequencies are not used and also decrease performance with gpu set to 550
I just find the correspondending post by sorg
I might have a look into that in the future
Click to expand...
Click to collapse
Thankyou for your patience. It was quite helpful to learn a new thing.

I have got a problem when put on usb charge it stays on high frequency and instead of charging, the phone battery gets dischaged slowly. anything i have to do.

[Kernel][3.0.101] faZevoLv.kernel [5.0.x]

faZevoLv.kernel​
This is a new kernel based off the more stable Hashcodes kernel rather than the previous kernel named thomasin kernel which was based off MWisbest's kernel source which was unstable and caused many random reboots for me and a few other users. This is why this kernel was created, fast, feature packed, updated and most importantly STABLE. no random reboots.
Features and Updates
3.0.101 patches from franciscofranco
OMAP4460 overclocking from MWisbest
Makefile: Linaro build flags
Optimised LPDDR2 RAM timising for a 12% throughput increase
tweaked CFQ tunables from franciscofranco
cpuidle: update to saner values and optiisations
binder: fix memory leak
update LZO compression to upstream
ARM: enable unaligned memory access
use GNU implementation of lib/string & lib/memcpy
force kernel to follow unaligned code path
cfg80211: fix memory leak
ARM memset fixes
readahead: make context readahead more conservative
vmalloc: updates and fixes
net/loopback: set mtu to 64k
CPU hotplug: update debug
cpufreq: optimise frequency table verify and updates
vmscan: allow it to sleep if running too long
SELinux: updates and workarounds
omap4-common: activate scu speculative linefills
omap4-comon: enable full zeroes write mode
omap4-common: tune values to fit changes without double linefill
OMAP4: update ARM errata options
OMAP4 NAND updates
Add ultra-KSM
import lowmemorykiller from 3.4 kernel and tune & update
readahead: add dynamic read-ahead
dynamic management of dirty page writebacks
add support for lz4 compressor and decompressor module
add lz4 cryptographic api
use lz4 for kernel compression
add Lagfree governor
SIOplus i/o schedular and tune
ARM: implement optimised percpu variable access
permanent filesystem TRIM
Optimise apply_stack() for size and speed
network speed tweak
wakeup: use irqsave/irqrestore for events_lock
add Hyper governor
interactive governor fixes and updates
net: add APIs for manipulating skb page fragments
random: entropy tweaks
increase clock rate for dpll_core_m6x2_ck for OPP100
use SLUB allocator as default
use RCU boost
lib/sha1: use the git implementation of SHA1 as it is faster
ashmem: fix deadlock when low memory
bcmdhd: decreased wakelocks
mmc: decrease wakelock timeout
bcmdhd: workaround for broken AC video queue in IBSS mode
pcm_native: code fix
OOM tweaks: many oom tweaks and fixes (5 commits)
procfs: speed up /proc/stat
ARM: add optimised swahb32()
ARM: implemented cpu topology for multicore devices (12 commits)
introduce effective timer slack and PR_GET_EFFECTIVE_TIMERSLACK
introduce timer slack control
Dynamic management of timer slack
XDA:DevDB Information
Advanced kernel for lollipop, Kernel for the Amazon 7" Kindle Fire HD
Contributors
faZevoLv, Hashcode
Version Information
Status: Stable
Current Stable Version: 002
Stable Release Date: 2015-03-01
Created 2015-02-27
Last Updated 2015-02-27

Frequencies
> 350mhz (default min)
> 525mhz
> 768mhz
> 998mhz
> 1200mhz (default Max)
> 1350mhz
> 1500mhz
> 1632mhz
> 1747mhz
Governors
> Conservative
> Ondemand
> Powersave
> Interactive (default)
> Performance
> Hotplug
> Hyper
> Lagfree
I/O Schedulers
> CFQ (default)
> NOOP
> Deadline
> SIOplus
TCP Congestion Algorithm
westwood (default), reno, bic, cubic, htcp, vegas, veno, yeah​

Has it fixed battery life? As it was draining significantly than stock kernel..

You rock dude! Flashing right away.

xWolf13 said:
Has it fixed battery life? As it was draining significantly than stock kernel..
Click to expand...
Click to collapse
Yeah deep sleep is fixed, in the other kernel it did not go into deep sleep which was where the battery drained.

So when will it be completed? (And if it is completed, when can we download?) I'm itching to test it out.

Fireator said:
So when will it be completed? (And if it is completed, when can we download?) I'm itching to test it out.
Click to expand...
Click to collapse
Go to the downloads section at the top of the OP (the black bar) and download it

faZevoLv said:
Go to the downloads section at the top of the OP (the black bar) and download it
Click to expand...
Click to collapse
Thanks!

faZevoLv.kernel.002 is out!
Check the features list for the updates, the download link as always is in the downloads section

So how high does the GPU overclock to? And where can I go to change the frequency? Can I use trickstermod app?
BTW, its a pretty good kernel. Nice and smooth. Ever better when I use Seeder. Only thing I noticed was that it reboots every time I try to overclock it to 1747Mhz. 1500Mhz is the most stable for me so I'm sticking with it for now. Keep up the good work!!

Fireator said:
So how high does the GPU overclock to? And where can I go to change the frequency? Can I use trickstermod app?
BTW, its a pretty good kernel. Nice and smooth. Ever better when I use Seeder. Only thing I noticed was that it reboots every time I try to overclock it to 1747Mhz. 1500Mhz is the most stable for me so I'm sticking with it for now. Keep up the good work!!
Click to expand...
Click to collapse
ive not added the option to set your own gpu overclock yet, but it will be implemented in a future release thankyou!

Thanks a lot. Very stable and fast so far. I couldn't install double tap to wake. Your old kernel supports this right? Or did I use it elsewhere? Sorry been flashing lots of ROMs lately.
**seems my kindle can't handle a high oc for even short bursts. I set it to 1747 and 10 seconds later it went to bootloop. Shutting it down manually then restarting didn't work. Had to reboot in recovery. But I don't pretend to know precisely what I'm doing.
Have you or anyone else tested above 1500? And if it's working could you share the exact settings? Thanks.

KLit75 said:
Thanks a lot. Very stable and fast so far. I couldn't install double tap to wake. Your old kernel supports this right? Or did I use it elsewhere? Sorry been flashing lots of ROMs lately.
**seems my kindle can't handle a high oc for even short bursts. I set it to 1747 and 10 seconds later it went to bootloop. Shutting it down manually then restarting didn't work. Had to reboot in recovery. But I don't pretend to know precisely what I'm doing.
Have you or anyone else tested above 1500? And if it's working could you share the exact settings? Thanks.
Click to expand...
Click to collapse
Highest I can go to is 1632. No hiccups so far. Using Interactive Governer with Min Frequency set at 1200Mhz. At the moment I am testing out the new I/O Scheduler that was added, sioplus.

xWolf13 said:
Highest I can go to is 1632. No hiccups so far. Using Interactive Governer with Min Frequency set at 1200Mhz. At the moment I am testing out the new I/O Scheduler that was added, sioplus.
Click to expand...
Click to collapse
That's what I was doing except with a lower min value and it crashed. Not the system just the browser this time. I'm thinking not all kfhds are created equally.
Overall this has been pretty stable though when I keep it at or below 1500

KLit75 said:
Thanks a lot. Very stable and fast so far. I couldn't install double tap to wake. Your old kernel supports this right? Or did I use it elsewhere? Sorry been flashing lots of ROMs lately.
**seems my kindle can't handle a high oc for even short bursts. I set it to 1747 and 10 seconds later it went to bootloop. Shutting it down manually then restarting didn't work. Had to reboot in recovery. But I don't pretend to know precisely what I'm doing.
Have you or anyone else tested above 1500? And if it's working could you share the exact settings? Thanks.
Click to expand...
Click to collapse
This doesn't support double tap to wake as it stopped the device from going into deep sleep which caused the huge battery drain, sorry about that.
And yeah I usually stay at 1500, but the option is there for kindles that can handle higher

Not sure if this is related to kernel or ROM (beanstalk) but I'm getting incompatible a lot in play store. I tried market helper but apparently its not ready for lollipop yet. Is there a workaround or like I just considered now--lots of the apps aren't compatible with 5?

KLit75 said:
Not sure if this is related to kernel or ROM (beanstalk) but I'm getting incompatible a lot in play store. I tried market helper but apparently its not ready for lollipop yet. Is there a workaround or like I just considered now--lots of the apps aren't compatible with 5?
Click to expand...
Click to collapse
Yeah its because a lot of apps don't support lollipop, however most of them can be downloaded from your browser with a quick google search

I know this is way out there a year later, but any plan on updating to 5.1.1 CM based?

[KERNEL] Ares-Kernel {KlteXXX}

****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?