Develop Bugs

-THE ULTIMATE =BATTERY LIFE + GAMING PERFORMANCE=[setup/guide/UNDERVOLTING-explained]

Hello everyone i know there are few threads about battery/gaming so i tought to make a thread with a review about battery life + gaming performance and add guides along with it.
Ok 1st i'd like to say i've pretty much flashed every single rom ,kernel, battery saving apps, performance boost apps, mods etc that are currently avilable so trust me i know what i'm writing here.
THREAD NAVIGATION:
Post 1 contains: Undervolting guide & everything related to undervolting CPU & GPU, EMC Overclocking, Rom setup guide, kernel setup (gaming / battery ), kernel settings list of updates
Post 2 contains: Rom & kernel battery life reviews + benchamrks , Performance may cry setup added (battery life settings)
Post 3 contains: Additional info about kernels / governors and what they do , schedulers and what they do & additional scrips.
FAQ Link for rookies and EVERY other question / guide about your HTC One X - Thx to Geko95 = HERE
Wakelocks guide for those with bad battery life - Thx to Goku80 = HERE
=========================================================================
First of all i'd like to give credits and massive thank to these guys who made all this possible:
- Hamdir - for all his guides and contribution for One X , he is one of the main reasons why we have smooth gaming !
- Xmister - kernels ( xm106 )
- Maxwen - the battery saving governor - Smartmax Governor
- Mwilky and his team for Renovate rom
- Patrics83 and his team for RomCleaner tool
- RichmondUK and his venom team for ViperX Rom
- n3ocort3x Kernels
- TripNdroid Kernels
---Excuse me if i've forgot someone.
----------------------------------------------------------------------------------------------------------------
Thread Updates:​
FInally cleaned the whole damn thread , still some left overs
PMC v8 interactive/battery setups added @ post 2. UPDATED 15.5.2013 ///bottom of the post 2
Added New SetCPU v2 profiles Read post 2 at the bottom UPDATED 15.5.2013 ///bottom of the post 2
Added AOSP/AOKP/CM SetCPU , profiles Read post 2 at the bottom UPDATED 2.4.2013 ///bottom of the post 2
Added NEW SetCPU , profiles Read post 2 for changelog ( everything fixed ) UPDATED 25.3.2013 ///bottom of the post 2
Added SetCPU GUIDE and my Save with SetCPU Profiles BALANCE Version this is only for those who have SMARTMAX & PMC GOVERNORS in their kernel UPDATED 25.3.2013 ///bottom of the post 2
Added EMC OC Guide, this is only for those who use XM kernel 235# and above UPDATED 12.3.2013 /// post 1
Added PMC v5 this is only for those who use XM kernel 226# and above (PMC is now the new governor at XM kernel read post 2 for more info ) UPDATED 10.3.2013 /// post 2
Added *Performance may cry setup v2* (battery life setup)- UPDATED 3.3.2013 /// post 2
Added info about schedulers and what they do - UPDATED 22.2.2013 /// post 3
Added info about governors and what they do - UPDATED 26.2.2013 /// post 3
Kernel updates:
XM kernel beta version(s) :
#304
Disable JRCU, according to maxwen it caused lockups.
#303 cpu clock changes reverted.
Switching governors will no longer update calibration control.
Touch-screen updates(S2W,DT2W) from maxwen.
Variant info added back.
#303
Included maxwen's double-tap to wake (needs sysfs enable), and inner CPU clock changes.
#302
Included maxwen's fixes for freq. locks and LP mode switch with OC.
#301
Default UV removed.
​Xm-Kernel STABLE version(s) :
#106
#106v2
#106v3
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Kernel reviews @ Post 2​
========================================================================================[/CENTER]
- If you'd like to donate to any of these ppl please do so because they're the ones who made this possible, i'm just making it simple and hopefully preventing questions from everywhere about battery/kernels/roms , which is the best etc etc. And remember the kernel is most responsable for your battery life. So the point is you can use any rom of your choice with this kernel as long as you do things right. And follow what i wrote down there.
As for me i'd be happy just with simple *thanks* button if this was helpful to you in any way.
------------------------------------------------------------------------------------------------------------------------------------------------
ROM, Kernel, Undervolting, underclocking, overclocking settings:
ROM Settings:​
Roms should be cleaned with RomCleaner tool just i used my own scrip since i wanted to keep some apps and widget, after cleaning i had 114 system apps on my hox , Renovate rom comes with around 200 or so + the apps you'll install. (rom cleaner also improves the battery and rom speed a little) Other then that nothing else changed except i added tons of mods but thats up to you what you'll add. And the only setting you'll need to enable in Renovate rom is 2d rendering This improves alot scrolling times in apps especially the ones like *Advanced system care and Rom Toolbox lite*​
Kernel settings: ​
Battery settings​
the only thing you'll have to do manualy is switch the governor after flashing Xm kernel onto Smartmax And thats all you have to do to have great battery life, in my case i underclocked my CPU to 1200mhz with smartmax governor + RoW scheduler , if you want to keep it faster (but you don't really need any more speed with this governor) leave it as it is, or to make it even faster use Smartmax + deadline + sampling rate 30000 + touch poke freq 1500000 ] , you can make it even faster but trust me no need for that. Use this governor and it's settings as daily settings for light tasks and light usage of your phone.
Gaming settings:​​​
For this you should be using interactive / gaming governor + deadline scheduler and that's all you need to do of course if you do underclock your CPU make sure you reset it back to 1500 after you change the governor , no need for apps that boost your phone, if you wanna make things even faster and governor more aggressive change this value in governor settings : go max speed load 45 this will increase speed ( remember this will make battery drain even faster ) , and if you wanna push max performance that your hox can deliver at current time change min frequency 1500 as well remeber THIS will make your hox battery drain fast as hell ! And sd card read ahead speed should be 4096 if is not set like this by default you can use system tuner and change it. For tuning governors and freqs you could use SetCPU easier and faster to do so.
Games that i used for testing are: NFSMW, MC4 , Shadown gun deadzone, Wildblood.
Each of this games were incredibly smooth and playable like never before.
Undervolting​
Ok so as many of you heard undervolting should improve your battery life and it does by maybe 5% tops 10% if you're lucky.
But the main reason why i undervolt is so i keep my phone cooler when gaming you wont notice big difference in avarage daily use without gaming but with gaming you should notice the difference but again this mainly depends on your CPU variant, in my case i have variant 3 which means i can undervolt more then variant 2-1-0 , thats the only good thing about undervolting , of course i could overclock more then other variants but we don't need overclocking with this kernel and rom.
The difference and battery improvement you'll be able to see only this way really and none other this is how : without undervolting and lets say playing NFSMW my phone ON charger reaches around 55c TOPS ( which is overheating and you lose more battery then what your charger can recharge for you ) but with undervolting my phone is reaching TOPS 45C and avarage 40C ( this also depends on the room temperature and your hands body temperature ) The reason why i did tests on charger is because thats the fastest way to test overheating and undervolting and NO do NOT play heavy games while charging this is KILLING your battery and lowering it's life cycle ! it's like eating while sh1tting !!!
Now i can't tell you which values to use since like i said above none chip is the SAME nor the variant so you'll have to figure out this on your own but i can give you the ROUGH idea how-to.
Update - rough idea how to undervolt​ CPU​ properly:​
ok i'll mark frequencies with colors:​
Before we start remember this: Undervolting depends mostly on your ROM , Kernel , USAGE !​
RED = Don't undervolt too much
BLUE = Undervolt normally as you do
BLACK =Don't undervolt or undervolt just a little this will depend on your variant and rom mostly
1500+ , 1400,1300,1200,1100,1000 e.g 1500mhz freq. has 1237mV by default if you're a gamer you can undervolt this one to lets say -50-100 (up to the variant) if you're not a gamer you can go even up to -125/150 , now this can depend also on which freq do you use the most in gaming lets say , if you're using quad lock e.g 1500 , -75 should be enough, === freqs under 1500 can be undervolted more since they wont be used, but if you don't use quad locking then you need to balance the undervolting between -50-100 (this depends on the game and which freq it uses the most)
860 , 760, 640 are the freqs in the *middle* those can be undervolted even more , up to -150 (default UV should be around -100 here) since they are barly used but you can use cpySpy to check which freqs your device uses the most and then use that info to balance your undervolting and find right freqs.
475,340,204,102,51 are the freqs more like *screen on standby freqs, mostly 340/51* or the LP core freqs, these should be undervolted MAX -50/75or not at all these freqs are used also for e.g. listening to music while screen off , if you undervolt too much you can experience laggs etc.
Important: Variant 3 can undervolt more then this but it *shouldn't* really up to you to decide​
IMPORTANT: Those who use XM kernel USE TRICKSTER MOD APP ONLY !
First of all you can use guide what i made above for undervolting but since we have accurate undervolting now you SHOULD undervolt THIS way and this way only:
Variant 0 = you can use undervolting max up to -50 MAX ! or if you're doing step by step undervolting you might push some freqs -75
Variant 1/2: You can undervolt MAX up to -75 or at some steps -100 tops.
Variant 3: you can undervolt MAX -100/125 and on some freqs MAYBE -150 , but of course you need to do step by step.
Remember: this are the SAFE undervolting values for all 4 variants You can try undervolting more if you like but i wouldn't recommend it since i'm sure it will most likely cause issues for you.
Remember: The UV values i've used above are supposed to be *DEFAULT* uv you should use , but users with variant 0 MIGHT suffer and have to use lower values
Note: I guess 90% of ppl are lazy to mess with per freq undervolting and finding what works for them and what not since consumes alot of time, anyway you guys should be good with -50-75 variants 0, 1 ,2 , as for variant 3 you should be able to go up to -100-125 on all freqs.[/SIZE]
GPU - Undervolting - Safe values​
[*]Ok so for GPU undervolting you need to be on XM #153 kernel and above and follow this steps:
Use some root explorer to enable GPU undervolting and navigate here:
sys/devices/system/cpu/cpu0/cpufreq/gpu_voltage
Click to expand...
Click to collapse
, open it , the default value is
0 to enable GPU undervolting type 1
Click to expand...
Click to collapse
and SAVE make sure to enable *system as writable*
After you do that you need to download this app from playstore *Trickster MOD* This is the ONLY app whit which GPU undervolting works for now. After that install app and you'll see GPU freqs like this: For e.g. *520000, 484000* etc those are the GPU freqs and their voltage.
The safe values:
Variant 0 = -25MV on all freqs.
Variant 1/2 = -25/50 on all freqs.
Variant 3 = -50-100 on all freqs.
The 1st freq i wrote is 100% safe, the second is ASSUMED to be safe as well, but you wont know unless you try it :cyclops:​
How to test are these values safe and wont freeze/reboot your phone.​
Probably many of you know when you undervolt too much your phone eventually feezes and reboots this happens because phone can't give enough of voltage to the certain frequency that is in that time used mostly so it has no other way out but to freeze and reboot. and the way to test this is it *safe* is either to use *antutu bechmark app* , *epic citadel* or *stability test* Those 3 tend to push max performance very fast and easy out of your phone so if any app gonna show you is it safe it's these , tho sometimes but rarely your phone will run them both without reboots so i suggest you do each of them 2x just to be sure, and even if then sometimes very very rarely if your phone doesn't reboot the last way you could've find out is it gonna reboot is by playing NFSMW for 10mins.
----------------------------------------------------------------------------------------------------------------------------------​
GPU Overclocking & underclocking - Safe freqs​
For this to work use some root explorer and navigate here: sys/devices/system/cpu/cpu0/cpufreq/gpu_oc , open it there you'll see default GPU freqs like this: 520 520 520 520 484 400 304 267 247 those are the DEFAULT freqs on XM kernel and make sure to enable *system as writable* before you start doing anything. Those freqs are great balance for GAMING and BATTERY but if you're an ADVANCED USER you might wanna make those freqs EVEN HIGHER for better performance (not needed imo ) or LOWER for better battery life
- Maximum performance freqs that works for everyone: 560 560 560 560 560 484 400 304 247
- Freqs for battery life while keeping some poor performance (gaming speaking): 304 304 304 304 304 304 304 304 247
- Default freqs ( battery & gaming ): 520 520 520 520 484 400 304 267 247
Thx to Neo for this freqs. ​
-----------------------------------------------------------------------------------------------------------------------------------------​
All kernel settings: S2W Configs: , DoubleTap2Wake Configs: , Activate fast charge: , Enable smartdimmer: , To get your variant: , 3D Tuning: , 2D Tuning: , EMC Tuning ( ram ): , Auto-BLN Control: , Backlight button brightness: , GPU Voltage control: , LP OC: , Audio Min. Freq.:​
Thx to Xmister for this.
S2W Configs:​
Turn off:
Code:
echo "0" > /sys/android_touch/sweep2wake
Click to expand...
Click to collapse
Or you can download "Sweep2Wake-Widget" from Google Play.
Button panel locks to s2w after this distance:
Code:
/sys/android_touch/s2w_register_threshold
Click to expand...
Click to collapse
Screen turns on/off after this distance:
Code:
/sys/android_touch/s2w_min_distance
Click to expand...
Click to collapse
Direction independent(1 - Yes, 0 - No):
Code:
/sys/android_touch/s2w_allow_stroke
Click to expand...
Click to collapse
DoubleTap2Wake Configs:​
Turn on:
Code:
echo "1" > /sys/android_touch/s2w_allow_double_tap
Click to expand...
Click to collapse
Activate fast charge:​Code:
echo '1' > /sys/devices/platform/htc_battery/fast_charge
Click to expand...
Click to collapse
Enable smartdimmer:​Code:
echo "1" > /sys/devices/tegradc.0/smartdimmer/enable
Click to expand...
Click to collapse
To get your variant:​Code:
cat /sys/kernel/debug/t3_variant
Click to expand...
Click to collapse
(Or see it in a root explorer)
cpu_process_id is your variant.
3D Tuning:​If you want to change clocks, you have to write the whole clock table again, from up to down. In case you want to reset to default, this is it:
Code:
echo '520 520 520 520 492 484 380 247' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Click to expand...
Click to collapse
If you want to set them at boot, use an init script. Here is one. Just copy to /system/etc/init.d and set the permissions to executable by everyone with a root explorer. (Thx to Byrana)
Here is a flashable script that will work on newer kernels too for everyone. It also enables fast_charge. (Thx again Byrana)
2D Tuning:​If you want to change clocks, you have to write the whole clock table again, from up to down. In case you want to reset to default, this is it:
Code:
echo '520 520 520 520 492 484 380 247' > /sys/devices/system/cpu/cpu0/cpufreq/two_d_oc
Click to expand...
Click to collapse
You should NOT OC this higher than 3D.
EMC Tuning:​If you want to change clocks, you have to write the whole clock table again, from up to down. In case you want to reset to default, this is it:
Code:
echo '667 667 667 667 408 408 408 408' > /sys/devices/system/cpu/cpu0/cpufreq/emc_oc
Click to expand...
Click to collapse
If you want to OC let's say to 800MHz:
Code:
echo '800 800 800 800 667 667 408 408' > /sys/devices/system/cpu/cpu0/cpufreq/emc_oc
Click to expand...
Click to collapse
Auto-BLN Control:​​Interface:
/sys/class/leds/button-backlight/auto_bln
Click to expand...
Click to collapse
Values:
0: BLN OFF/Green led ON
1: BLN ON/Green led ON
2: BLN ON/Green led OFF
Example:
Turn off Auto-BLN:
Code:
echo '0' > /sys/class/leds/button-backlight/auto_bln
Click to expand...
Click to collapse
The changes will apply from the next notification.
Backlight button brightness:​Interface:
/sys/class/leds/button-backlight/button_brightness
Click to expand...
Click to collapse
Values:
0-255: 0 is off, 255 is the maximum possible.
Example:
Code:
echo '50' > /sys/class/leds/button-backlight/button_brightness
Click to expand...
Click to collapse
The changes will apply from the next backlight turn on.
GPU Voltage control:​If you want to enable this you should write '1' to /sys/devices/system/cpu/cpu0/cpufreq/gpu_voltage.
In command line that is:
Code:
echo '1' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_voltage
Click to expand...
Click to collapse
After that you need to restart your voltage control app (Trickster Mod).
Now you will see the GPU frequencies multipled by 1000 to separate them from the CPU frequencies. So you will see 520000MHz, etc.
Be advised that there are a really few HOX's that can handle more UV on Core, than the preset 50.
Also incrasing your Core voltage over 1300mV is NOT ADVISED AT ALL. Almost everything uses this voltage on your motherboard.
If you want to enable the values at boot, you need an init script that enables it, so later Trickster mod or anything can set them.
LP OC:​Interface:
/sys/module/cpu_tegra/parameters/enable_lp_oc
Click to expand...
Click to collapse
Values:
0: LP OC OFF
1: LP OC to 620MHz
Example:
Turn on LP OC:
Code:
echo '1' > /sys/module/cpu_tegra/parameters/enable_lp_oc
Click to expand...
Click to collapse
Audio Min. Freq.:​Interface:
/sys/module/snd_soc_tlv320aic3008/parameters/audio_min_freq
Click to expand...
Click to collapse
Example:
Change audio min. freq. to 204MHz:
Code:
echo 204000 > /sys/module/snd_soc_tlv320aic3008/parameters/audio_min_freq
Click to expand...
Click to collapse
Save settings:
If you want any of the above settings saved, you can use Ibas21 recovery package
Click to expand...
Click to collapse
=======================================================================​
Remember you wont probably get same screen on time as i did , you could get even more then i did or less, it ALL DEPENDS on your USAGE/Screen brightness!
That should be all enjoy.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​The screenshots and my usage are in post 2, hope this helps , if not sorry for wasting your time if you read this , cheers and good luck to everyone
If you have any question please feel free to post them and i'll give my best to answer them.
Also as the kernel updates and rom updates go i'll try to update in here as well.
----------------------------------------------------------------------------------------------------------------------------​
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
And lastly i will not be held responsible for anything that may or may not happen to your device ! All you do you do at your own risk.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
And of course please hit *thanks* button if this was helpful​ :highfive::good:
==================================================================================​

Bechmarks - updated.
------------
------------
Viper X Rom 3.3.7 XM Kernel 139#[Beta]
Usage:
Somewhere between normal and heavy , battery life was great, not so much on the wifi this time, and all in all great kernel with one tiny bug, if you use autobrightness you'll see flickering , tho this got fixed in 147#. And i plugged the phone right before screen shots for maybe a minut to put pics on the pc and in the meantime i made those screenshots, you can see that in the usage. Brightness varied between low (15%) and maximum. The most used brightness used was 35%.
-----------------------------------------
-----------------------------------------
Black Pearl unofficial beta Rom 4.0.4 - XM Kernel 188#[Beta]
Usage:
- 1st of all , extreme undervolting and underclocking was done for this test.
- The rom and kernel were also flashed for the very 1st time.
--------
--------
================================================================================================
1st how PMC works:​
Well simply i made it use as *ideal_freq* 340mhz , minimum freq is 51mhz , the freq you'll be using alot would be 340/475 , that is your main freq on PMC for boost to avoid huge laggs, another thing is it will try and use most of the time only 1 core unless that core is at 90% cpu load , and min cpu load is 50 to make sure you don't get frequent wakes of 2nd/3/4th cores.​
Interactive PMC Version:
This version is 90% similar to PMC Battery setup except this version is much faster since it acts like INTERACTIVE Governor.
@ Those who don't have PMC Governor in their kernel until / if their kernel dev includes it use *Smartmax governor* for tunning and using my setup
Important ! : While setting your CPU/GPU values don't enable *Set on boot* unless the values are 100% safe for you and by ALL MEANS DO NOT USE MY CPU/GPU VALUES even if you're VARIANT 3 i wouldn't advise it , if you DO USE my values you will 99.9% end up in freeze or reboot !
GPU UV For max battery
2d GPU Underclocking: 304 304 304 304 267 267 267 200
3d GPU Underclocking: 247 247 247 247 247 200 200 200
As for GPU uV i'd suggest -50mv if you're not variant 3. Try first -25 then -50.
NOTE:
Don't even think about gaming with this setup , you'll notice laggs mainly at loading apps and speed of loading apps and mainly speed reduction overall in system , but not so much , the main slowdown is with loading apps and when multitasking you'll see some laggs as well, or for e.g. when playing music and then using volume up/down , that will lagg as well, if you wanna keep it *smoother* you can set *Ideal freq to 475000*
Performance may cry - setup v8a( XM Kernel 302# + ONLY or Kernels with latest Maxwens updates)​
A This settings of PMC Governor should / will deliver you the performance 90% identical to Interactive governor with much much less battery drain ! , this settings can be / should be used for those who MULTITASK alot , this settings/governor should give you 95% lag free experience whatever you do except gaming ! [/I][/B]
PMC v8 INTERACTIVE SETUP for EVERYONE ( Xm kernel users don't need this since PMC governor is in the kernel by default with these values ):​
awake_ideal_freq 475
boost_duration 0
boost_freq 760000
debug_mask 0
down_rate 60000
ignore_nice 1
input_boost_duration 90000
io_is_busy 1
max_cpu_load 75
min_cpu_load 40
ramp_down_step 200000
ramp_up_during_boost 1
ramp_up_step 300000
sampling_rate 20000
suspend_ideal_freq 340
Touch_poke_freq 620000 ( 640 if your kernel kept the old freq table )
up_rate 20000
Cpu freqs:
Min CPu freq : 51
[*]Max Cpu freq: 1100
[*]Scheduler: RoW
Multicore power saving : 2
GPU max frequency : 416
Undervolting: At your choice and how much your variant can support:
Suggested SAFE values for all 3 variants NO GAMING for gaming use +25 more then my values under, example : if variant 1 is -100 NON GAMING , for gaming use -75.
This goes for both INTERACTIVE and BATTERY PMC setups.​
variant 0 : -75
[*]variant 1/2: - 100 ( use -75 if you experience reboot )
[*]variant 3: - 150 / -175 in my case.
PMC BATTERY SETUP v8 For everyone with TUNNABLE Smartmax/PMC governors:​
awake_ideal_freq 204000
boost_duration 0
boost_freq 760000
debug_mask 0
down_rate 60000
ignore_nice 1
input_boost_duration 90000
io_is_busy 1
max_cpu_load 90
min_cpu_load 50
ramp_down_step 200000
ramp_up_during_boost 1
ramp_up_step 300000
sampling_rate 40000
suspend_ideal_freq 204000
Touch_poke_freq 620000 ( 640 if your kernel kept the old freq table )
up_rate 20000
Cpu freqs:
Min CPu freq : 51
[*]Max Cpu freq: 1000
[*]Scheduler: SiO
Multicore power saving : 2
GPU max frequency : 416
Undervolting SAME AS on interactive ( look above )
And heres what users reported with PMC V7 performance setup =)
fade2blak said:
XM 188v2 with your PMC v7 performance version gave me the best results ever. period. thank you :highfive:
Click to expand...
Click to collapse
Insecret said:
now v241 on Viper 3.4.0 with row and pmc gov, UC at 1200 and the rest like Shan89 sayed in previus page ... Unthinkable how much improves in performance and batt life <3 Xmister and Shan89
Click to expand...
Click to collapse
bienjie said:
U r superb dude! U are gifted! Damn u r sooo good in this....(^~^)/
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
kkarnaout said:
im using the the new kernel with viperx 3.4.0 and all pmc settings, phone is amazing FB app is working i didnt see any problem till now this is the best kernel i tried till now from all the passed weak!
All thanks go to Xmister and Shan89
Click to expand...
Click to collapse
-------------------------
---------------------------
===============================================================================================
How to use FULL PMC setup.
Simple:
1st: thing to do enable 2d GPU rendering in developers options.
2nd: lower your CPU max freq to 1000mhz ! Yes 1000 mhz ( you wont feel much of a difference in terms of fluidity except when loading apps )
3rd: Use RoW or Sio scheduler ( for more info about these schedulers look at my signature guide theres explanation of every scheduler we use )
4th: Undervolt your CPU - here are the SAFE FREQS for these variants v0 - 50 , v1/2 , -75 , v3 - 100/125 (this are safe you could do more on some freqs)
5th: This is for those who don't play GAMES Underclock the GPU freqs here are the freqs you should use:
2d UC = 304 304 304 304 267 267 200 200
3d UC = 267 267 267 267 200 200 200 200
6th: Those who game you SHOULDN"T play with GPU UC only CPU UC.
Important: Make sure you use Trickster MoD app from playstore when using XM kernel for tuning and another vital thing to do is set in trickster app Multicore Power saving to 2 This will try to use as long as it can 1/2 cores unless desperate need for 4 cores.
A tip how to speed up loading times of the apps:
Since we have boost at 500 mhz if you open some app , lets say for example *Trickster MoD* after clicking on it you can hold your finger on the screen and move it in any direction , that way your CPU wont be locked onto 51 MHZ freq it will be on either 620 / 640 mhz ( boost freq ) or at MAX freq you set for CPU ( 700 if you use full PMC setup )
Final words:
PMC will try to force your phone spend 90% of the time in LP (low power) cores which barely use any power , if you do use PMC full setup the only real battery drain you'll have is your SCREEN and when in desperate need for some boost it will use your highest CPU freq you set.
Note:
Don't complain about bad speed etc etc etc , this governor is made only and only for BATTERY LIFE with basic usage.
And of course if this governor is *too laggy/slow* you can always use original *Smartmax governor*
NEW - SetCPU profiles setup balance v2 = SENSE =:​
SENSE SetCPU profiles v2
This profiles fixed every little issue that exited in 1st release , just make sure to re-read the guide , some things has changed.
Anyway to make some kind of *changelog* if i can even call it like that this is what has got fixed / added:
Gaming works perfect now
Added profile for 2d games
Added profile for safety ( over heating to prevent it 2 steps )
Added more apps into profiles
Changed freqs on some things for better performance/battery life
Some other stuff i can't remember right now lol
Click to expand...
Click to collapse
Q) What does this do ?
A) Makes your phone smarter , boosts it when needed and downscales CPU freqs when not needed , It changes Governor / scheduler / CPU Freqs / .
Improves Loading times alot vs old PMC setups. The default loading times speed varies between 1100 mhz and 1300 mhz now.
Example:
Sense launcher: is set to use 640 MAX Cpu freq with smartmax governor + SiO scheduler.
Messaging: email / sms / gmail / etc = It will switch governor to PMC v7 ( Interactive version ) Boost max CPU freq to 840 and use Deadline scheduler so it makes sure it's liquid smooth and rotation works perfect.
Gaming: When you hit some , in my case NFSMW , MC4 , RR3 it will change to interactive governor + Row Scheduler and use MAX Cpu FREQ 1300mhz.
HOW TO SETUP ( Important ! )​
1st: download SetCPU ( google it if you can't buy it you should be able to find it for free)
2nd Set max CPU Freq to 1300 and min freq to 51
3rd: Go to trickster and do the following:
Trickster settings:
PMC Governor = Leave as it IS
Scheduler = SiO
Multicore power saving = 0
Gpu Max freq = 520
Smartmax Governor settings = Change the settings to PMC V7 BATTERY Settings ( This is important thing to do if you want the profiles to work )
Undervolting - UPDATED:
Variant 1/2 = freqs 51/1250 undervolt - 100 ( if is unstable for you use -75 ) Freqs 1300-1500 Undervolt - 50 ( if is unstable use -25 )
Variant 0 should use 25mv more compared to v1/2 and variant 3 can do additional -50 on freqs 51/1250 and 1300/1500 freqs -25 compared to variants 1/2.
And last thing to do is *Set on boot / enable* - Do this only if UNDERVOLTING doesn't cause any reboots for you , it shouldn't anyway.
4th: copy my SetCPU Profiles to your SDcard and open SetCPU App , load the profiles and Apply them , make sure to tick * Enable Profiles * Also on the *MAIN* settings for CPU / Governor / Scheduler tick *Set on boot* and finally @ *Governor* also tick *Set on boot & Set With profiles*
5th: Download greenify app from playstore:
Set greenify app at your likings but make sure you don't put Trickster and SetCPU Apps in there.
6th: Downlaod LagFix (Fxstreem) App from playstore as well. Use this app once a day or whenever you like it.
Note: This will work ONLY With XM kernel unless another kernel dev includes PMC Governor in their kernel.
Tips:
[*]New - for MAX Speed when not using apps listed in profiles set in trickster & SetCPU Max Freq 1300 ( For absolute max performance 1500 ) min 51 INTERACTIVE governor and DEADLINE Scheduler. What will this do: Well simply it'll use max freq 1300 / 1500 depends on your choice whenever you're using something that is not listed in the profiles E.G. when you hit *Settings* it'll use interactive + deadline , same goes for other things that are not listed in the profiles.
[*]If you do full reboot make sure to open SetCPU app so profiles start working after the reboot.
[*]For 2d games *temple run* Etc just add them into *2d gaming profile*
[*]Tip for heavy 3d games sucha are Mc4 NFSMW , RR3 etc etc , i've set on 1300 max CPU freq so we avoid heat etc , note that those games are on MAX DETAILS for me and i don't have laggs so you guys who use those games without those details you should be fine in fact you can change max freq from the profile onto 1200 if you like. If you play some other 3d heavy games just add them in *Gaming* profile.
[*]A Tip for gaming with low details: Change the max freq from my profiles to 1100/1000 , i played NFSMW on max details with some FPS Drops on 1000mhz freq.
[*]@Those who use more social apps then facebook , simply add those apps in my profile where is facebook. If you use another messaging apps simply add them to my messages profile. Do the same to the other apps that you use which are similar to the apps in my profiles.
Click to expand...
Click to collapse
@Those who don't game at all and want maximum battery life they can get , also this would be useful for those who game as well , just apply those 2 things after you done with gaming:​
Go to trickster app and do the following:
Max Gpu speed = 416
Multicore power saving = 2
If you want even more battery life visit my signature theres everything else you need to know on the post 2.
IMPORTANT: I've set on every profile *Notification* just so you guys can see it does it work , for those who want to remove it simply do this:
SetCpu > Profiles > click on the profile > Next > Untick *Show a notification* and that's it , do the same for other profiles.
Click to expand...
Click to collapse
If by any chance you don't see notifications after first time applying my profiles make sure you enable *Set on boot * where ever i wrote above and reboot your phone. That should fix it.
If anyone experience any issues ETC please lemme know.
AOSP/AOKP/CM SetCPU profiles + PMC v7 Setup - NEEDS UPDATE DON"T USE THEM - Will add them in few days when i switch to AOSP.:​
DOWNLOAD THE AOSP PROFILES HERE​
Download these tools 1st:
SetCPU app
Trickster app
Greenify app
Trickster settings:
Choose smartmax governor and apply these values in governor control:
Boost_freq: 620
Ideal_freq: 340
max_cpu_load: 90
min_cpu_load: 50
touch_poke_freq 620
Click to expand...
Click to collapse
Apply the values
Scheduler:
Deadline
Click to expand...
Click to collapse
Cpu settings:
Max freq 1000
Min freq 51
Click to expand...
Click to collapse
After that change to PMC Governor and apply.
Next thing to do swipe to specific settings
Smartdimmer: ON
Multicore power saving 2
GPU Max freq: 416
Undervolt how much you can.
Click to expand...
Click to collapse
APPLY all these and SET ON BOOT
Next thing to do open SET-CPU app make sure it's showing same CPU freqs as on trickster and same governor and scheduler.
Set on boot
Go to PROFILES and load my AOSP profiles after that tick Enable profiles
Important:
This profiles will work ONLY on AOSP rom and ONLY on XMkernel since other kernels don't have PMC interactive governor.
After applying the proffiles go to LAUNCHER and if you don't USE NOVA remove NOVA from that profile and ADD your launcher that you use.
TIPS / IMPORTANT:
[*]After you apply the PROFILES and you don't use INVERTED BLACK FACEBOOK APP delete that from profile and add the facebook app you use.
Click to expand...
Click to collapse
As for your own apps just go to profiles and add those apps into profile you like.
Click to expand...
Click to collapse
Lastly Thx to Xmister for the great kernel and his devhost link for uploading the profiles.
Heres the screenshoots from ICJ 2.8.1 with PMC v7 battery/interactive SetCPU Profiles:
----------
--------
-------
==================================================================================================
Note:
You shouldn't really relay and trust benchmarks at least not in antutu and quadrant , the most reliable and most accurate benchmark we have is Epic citadel , almost every single time same results. and 52.6 is quiet high result for sense rom. Btw for those who care s3 scores average 44-45fps on epic and note 2 scores average 46-47fprs.
]]=====>>> Wakelocks guide thx to Goku80 <=====[[
This is for those who have bad battery life !
http://forum.xda-developers.com/showthread.php?p=38629490#post38629490

Guys who follow this guide and use it , Please leave us the feedback about your battery life and rom you used. It's gonna be easier for us to locate the best battery life RoM, Thx in advance ! Also rating the thread would be nice
And those who USE this guide but apparently *doesn't help them* please post a replay with what you did and what happened, your battery/undervolting , whatever that came out from this guide, theres a chance you didn't do something RIGHT so we can try and help out. THX !
ADDITIONAL INFO - UPDATE:
I tought it would be nice to add some info about schedulers , and governors so ppl better understand what they are and what they do
Update: added governor info.
Update: added info about MpDecision and Cpu Quiet per request..
---------------------------------------------------------------------------------------------------
Governors:
- OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.
OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.
This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.
- Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
- Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.
- Suggestion : Use this governor (Interactive) for GAMING , it's the best when using Xm kernel for this purposes +deadline or Row scheduler.
- Smartmax
Long story short if you want crazy battery life USE this governor with either noop/sio/row governor, depending on what you want , read about schedulers under and chose what fits your needs.
- PMC ( Performance may cry )
ok so i made this governor based on Smartmax except it's heavily tweeked for better and maximum battery life you can get out of HOX.
- TouchDemand:
This governor pretty much do what the name says, boosts cpu freqs by touches, this one actually can be pretty great for battery life if you underclock the CPU imho and use max 2 cores, you can do that by doing this: edit touch_min_cores under governor tuneables and set 2
Anyway i still prefer *SmartMax* for battery life. But up to you to test and find out.
As for other governors like : Conservative and powersave , i wont be adding info about them since i doubt anyone ever uses them , all they do is take more space in the list
-----------------------------------------------------------------------------------------------------------------------------------------------------
Schedulers:
- Noop:
This scheduler assumes I/O performance optimization will be handled at some other layer of the I/O hierarchy , on the more simple way this scheduler is MOSTLY used for battery life since it's slow - it raises freqs slower then other schedulers.
- Deadline::
This scheduler attempt to guarantee a start service time for a request It does that by imposing a deadline on all I/O operations to prevent starvation of requests. It also maintains two deadline queues, in addition to the sorted queues (both read and write). Deadline queues are basically sorted by their deadline (the expiration time), while the sorted queues are sorted by the sector number. To make it more simple this scheduler raises freqs much faster then noop and keeps them longer active then noop which means more battery drain ( not by much anyway ) and faster I/O as well the gaming should be the best with this scheduler.
- SIO:: - ( my favorite )
This scheduler in simple words is basically this : It's a mix of noop and deadline schedulers , noop is more for battery while deadline is more for performance , and sio is perfect balance between them ^.^ to be more specific it's more like almost having noop+deadline activated at the same time.
- ROW::
ROW: stands for "READ Over WRITE* The ROW scheduler is in favor for user experience upon everything else (means it should make things stupidly smooth ),so that why ROW scheduler gives READ IO requests as much priority as possible. Usually it¡¯s a single thread or at most 2 simultaneous working threads for read & write. Favoring READ requests over WRITEs decreases the READ latency greatly. == Even more speed.
The main idea of the ROW scheduler is // == If there are READ requests in pipe - it WILL dispatch them but don't starve the WRITE requests too much.
Also this scheduler is much better optimised for our phones since in the smart phones we use flash memory and not hard drives.
Finally : Think of this scheduler as a mix OF deadline+ Performance governor put in scheduler while you can use another governor e.g. Smartmax. It's quiet fast scheduler and even good for daily usage without much of impact on the battery life.
Hope this prevents the question about schedulers / governors and which one to use
And a tip: Sio scheduler should be PERFECT with smartmax governor for battery life + speed , in fact it's the best scheduler if you guys want speedy performance while saving the battery life.
-------------------------------------------------------------------------------------------------------------------
MPdecision:
MORE INFO >
For us mpdecision is a cpu hotplug system, which replaced the default nvidia hotplug system. It was written by showp1984(Dennis Rassmann).
It's more configurable, better for battery life, and much much better for gaming.
Cpu quiet:
- Cpu quiet driver regulates the cores by them acting more syncronized. they scale up n down in a more uniform fashion. therefore it gets better battery life without losing performance. You can't manage each core like with morrifics. so the cpu quiet driver is doing all the regulating. So the cpu quiet driver basically replaced hotplugging as far as cpu core management goes.
- In simple words it should give better battery life.

Good thread mate!
I know people have been looking for a guide for ages.
Goku was gonna do one in fact, guess you beat him and me to it.

geko95gek said:
Good thread mate!
I know people have been looking for a guide for ages.
Goku was gonna do one in fact, guess you beat him and me to it.
Click to expand...
Click to collapse
Lol thx, i was actually waiting for you or him to make one, i guess i got tired of waiting and besides that i saw tons of questions in past few days about *which kernel , rom* are the best so i guess they have their answer now.
Oh and if you have anything to add that i might forgot or anyone else please feel free to do so.
Edit - I'll probably add new screenshots when i manage to waste this 9% i got left, this battery refuses to die, i feel like i have note in my hands lol.

Shan89 said:
Lol thx, i was actually waiting for you or him to make one, i guess i got tired of waiting and besides that i saw tons of questions in past few days about *which kernel , rom* are the best so i guess they have their answer now.
Oh and if you have anything to add that i might forgot or anyone else please feel free to do so.
Click to expand...
Click to collapse
I'll have a think, I've got a little battery guide of my own that I wanted to write.
I'll have to see if wilky will want to put it in the OP, if not then you can use it in this thread.
Also I'll talk to wilky and see if he wants to add a link to your thread when we next edit the OP.

geko95gek said:
I'll have a think, I've got a little battery guide of my own that I wanted to write.
I'll have to see if wilky will want to put it in the OP, if not then you can use it in this thread.
Also I'll talk to wilky and see if he wants to add a link to your thread when we next edit the OP.
Click to expand...
Click to collapse
Sure , i'd be honored :good:

Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
What is maxwen governor? Where can i find it?
Sent from my HTC One X using xda app-developers app

jarein95 said:
What is maxwen governor? Where can i find it?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Its called Smartmax and its included in NCX and XM kernels.

Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
geko95gek said:
Its called Smartmax and its included in NCX and XM kernels.
Click to expand...
Click to collapse
xD jajajaa is what I am using since yesterday jajajaa but i didnt recognised it with the name of maxwen!! Jajajajaa
Sent from my HTC One X using xda app-developers app

jarein95 said:
xD jajajaa is what I am using since yesterday jajajaa but i didnt recognised it with the name of maxwen!! Jajajajaa
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Maxwen is the nick of the guy who wrote it.

jarein95 said:
xD jajajaa is what I am using since yesterday jajajaa but i didnt recognised it with the name of maxwen!! Jajajajaa
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Lol, anyway looks like i'll have to edit OP so ppl know the name of the governor

Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
If you use the repacked xm I posted it's set to smartmax automatically
Sent from my HTC One X using xda premium

mwilky said:
If you use the repacked xm I posted it's set to smartmax automatically
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah i did use your repack cuz of original s2w Also cuz of Smartmax as default on boot. thx for that.
Btw OP updated with final battery results. Ppl i think we have the perfect match here about battery + gaming + speed. It's simply revolution of HoX. And all thx to everyone who developed for HoX sucha amazing stuff, and we must not forget things can get only BETTER for hox from now on not worse, so we might expect even better stats.

Just a small comment on smartmax
Setting boost_freq has actually not much of an effect
This is only used for the "external" boost interface of smartmax
This can be used e.g. from the android power module to boost
the cpu if required. But thats of course not implement in most roms
So only touch_poke_freq has an effect since this is use to boost
on input events from the touchscreen

maxwen said:
Just a small comment on smartmax
Setting boost_freq has actually not much of an effect
This is only used for the "external" boost interface of smartmax
This can be used e.g. from the android power module to boost
the cpu if required. But thats of course not implement in most roms
So only touch_poke_freq has an effect since this is use to boost
on input events from the touchscreen
Click to expand...
Click to collapse
Thx on the correct info.
Edit - Benchmarks updated.

Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
Hi. What app did u use to change governers? Any preferred?
Sent from my HTC One X using XDA Premium HD app

gilbertvpuen said:
Hi. What app did u use to change governers? Any preferred?
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Hello , for changing the governors and schedulers undercloking , overclocking and changing the governor values i use SetCpu you can find it on apkmania site, as for undervolting and further more tweeking i'm using System tuner , you can find that one on the playstore. Btw it's in the Op

Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
Shan89 said:
Hello , for changing the governors and schedulers undercloking , overclocking and changing the governor values i use SetCpu you can find it on apkmania site, as for undervolting and further more tweeking i'm using System tuner , you can find that one on the playstore. Btw it's in the Op
Click to expand...
Click to collapse
Hi shan,thanks. One last thing. I noticed you have changed your fonts, im also in renovate rom with xm106. I dont see any options for that. Can u guide me too a link? Cnt find it in themes/ add ons thread.
Sent from my HTC One X using XDA Premium HD app

Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
Thnks shang, will try it in SkyDragon rom to see how it works, as Base 3.17 its better, hope to get better results,
Btw.. Kernel Devs makes our roms better.
Cheers
SkyDragon Team© No Kangy rom allowed.

[KERNEL][AOSP4.4/5.1/6.0/7.1] dkp - d2att - 2/4/18

Welcome to decimalman's kernel playground!​
As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.
Features:
Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)
Underclocking down to 54 MHz, with stability improvements
Undervolting compatible with most apps
Fast charge without unplugging first
Glorious animations for the notification and softkey LEDs
Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)
freelunch and tierservative governors for optimal battery life without sacrificing responsiveness
Automatic mpdecision and auto-hotplug are only enabled when needed
Adjustable minimum voltage for stability on finicky processors
Optimized UKSM to free up some extra memory
Code optimizations for size and speed
Compiler optimizations (-O3, LTO, and more) because faster is better
Donors: Thanks, everyone! Your generosity is much appreciated. :good:
drpenguino, 0xScott, vmancini3 (twice! :good, Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict
Remember:
Nandroid!
last_kmsg and/or logcat or it didn't happen.
Other kernels have their own threads or forums. Discuss them there.
Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.
Be silly. We're here to have fun.
Installation:
Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called.
Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).
Reboot.
Undervolting:
Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).
Downloads:
MediaFire:
All Downloads
dkp-vmin-XXX.zip
Solidfiles (Make sure you have an adblocker!):
All Downloads
dkp-vmin-XXX.zip
Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.

Bugs:
Let me know.
Stable changelog:
3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.
4/8/13 (3.0):
FauxSound support
Strip more useless stuff
A few bonus optimizations
4/8/13 (3.4):
Port everything except erandom from 3.0
Enhance cpufreq for easier configuration
4/24/13 (3.4):
Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.
Lots of CM/CAF/Linux updates
Working AssWax governor
Trinity colors support
sio, zen I/O schedulers
erandom is back!
Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness
Probably lots more, but there's hundreds of commits to sort through...
5/29/13 (3.4):
Bugfixes: better overclocking support, better hwrng support, etc.
Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface
Automatic auto-hotplug
New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain
6/14/13 (3.4):
Bugfixes: fix several critical bugs in the 5/29 release.
9/7/13 (3.4):
Fixes for OC, UV, auto-hotplug.
A few new optimizations.
Synced up with CM.
9/20/13 (TW):
Ported everything from AOSP to TW.
9/20/13 (4.3):
Merged 4.3 from CM into the existing 4.2 code.
Current experimental branches:
Nothing interesting at the moment.

Goodies:
dkp doesn't come with its own splash screen. However, the dkp installer (i.e. the install zip) is smarter than you think, and can apply a custom splash screen for you. Here's how:
Create a folder on your internal storage named "dkp"
Copy a PNG image into the directory, and rename it "splash.png". Alternatively, copy an RLE image (i.e. from a flashable custom splash screen zip) and rename it "splash.rle". Ideally, the image should be roughly 1280x720 to begin with, since it won't be resized.
The image will be used as your splash screen whenever you flash dkp. Reflash to apply initially.
mikedavis120 has put together a how-to video that covers tweaking dkp for optimal battery life. If you're new to dkp, take a look! He also put together a zipped collection of apps that will come in handy while tuning dkp. It also includes a flashable zip, "dkp-debug_v1.zip". After flashing it, running
Code:
su
dkp
from a terminal emulator will collect lots of useful debug information that will make it much easier for me to track down the issue you're having. :good: mikedavis120 recommends installing SuperSU (included in the zip) instead of what's included in you ROM.
sysfs:
It's possible to adjust all the settings available in dkp without using apps. Because they show up as files, settings can be adjusted with file managers, terminal emulators, adb and initscripts. Here's the most interesting files inside sysfs:
/sys/devices/platform/mipi_samsung_oled.513/lcd/panel/panel_colors (not available on newer AOSP builds): display tint (0 = very red, 2 = default, 4 = trinity colors)
/sys/class/misc/gammacontrol (only available on newer AOSP builds): various color controls. See this post for details on enabling Trinity colors on builds that use these controls.
/sys/devices/system/cpu/cpu<N>/cpufreq/UV_mV_table: voltage table
/sys/devices/system/cpu/cpu<N>/cpufreq/scaling_...: scaling_governor is the governor, scaling_min_freq and scaling_max_freq are the minimum and maximum frequencies, scaling_available_governors and scaling_available_frequencies show the available governors and frequencies
/sys/kernel/dkp/force_fast_charge: fast charge
/sys/kernel/dkp/link_core_settings: when linked (the default), frequency settings and some governors are automatically copied to the other core
/sys/kernel/dkp/vmin: minimum processor voltage in mV
/sys/kernel/mm/uksm/run: activate UKSM
auto-hotplug tuners:
These show up in the governor settings for any governor that doesn't do its own hotplugging. They only take effect when using auto-hotplug, so you'll probably need to disable mpdecision in Trickster.
hotplug_intpulse: when set to 1, automatically turns core 2 on whenever the screen/buttons/whatever is pressed. Default is 0.
hotplug_sampling_periods: number of samples to use for average number of running tasks. Default is 15.
hotplug_sampling_rate: number of 'jiffies' (currently 1 jiffy = 10 ms) between each sample of running tasks. Default is 20 (0.2 sec).
hotplug_enable_one_threshold: the average number of running tasks required to turn core 2 on, multiplied by 100. Default is 125 (1.25 tasks on average).
hotplug_disable_one_threshold: the average number of running tasks required to keep core 2 on, multiplied by 100. Default is 250 (2.5 tasks on average).
freelunch/nanolunch tuners:
freelunch and nanolunch aren't materially based on other governors, so their configuration is quite different than other governors. There's lots of tuners, since I haven't really decided on an ideal tuning. I encourage experimentation! I'll explain a bit of how these governors work before actually listing the tuners.
Generally speaking, there are two modes: in "normal" mode, sampling is done occasionally and frequency is generally increased slowly; in "interactive" mode, sampling is done much more quickly, and frequency increases much more quickly. "Interactive" mode ends after several samples of very low usage. The idea of a "hispeed" frequency is used in lots of governors, and it refers to the frequency that the CPU will jump to when more CPU usage is needed; generally, it's a generous estimate of how much CPU will be needed. Here, the hispeed frequency is adjusted on-the-fly, increasing when more CPU is needed and gradually decreasing when the CPU is idle. In "interactive" mode, the hispeed frequency is kept fairly high so that everything will feel snappy.
Hotplugging is taken care of in the least complicated (and in my opinion, most reasonable) way possible: if core 1 is using lots of CPU, and there are several tasks running (in other words, if it's likely that core 2 will have something to do), core 2 is turned on; if either core isn't doing much except using power, core 2 is turned off.
sampling_rate: the usual
hotplug_up_cycles: number of consecutive heavily-loaded samples before core 2 is turned on
hotplug_down_cycles: number of consecutive lightly-loaded samples before core 2 is turned off
hotplug_up_load: number of running tasks required to bring core 2 online
hotplug_up_usage: number of used CPU cycles (in thousands per second) required to bring core 2 online
hotplug_down_usage: number of used CPU cycles (in thousands per second) required on both cores to keep core 2 online
overestimate_khz: number of CPU cycles to overshoot usage by in "normal" mode
hispeed_thresh: if CPU usage is within this many cycles (in thousands per second) of the maximum frequency, frequency will be increased to the hispeed frequency. Generally, hispeed is pretty low in "normal" mode, and fairly high in "interactive" mode.
hispeed_decrease: when the CPU is sitting idle, the hispeed frequency is decreased by this amount each sample (this isn't ideal, but it works)
interaction_hispeed: the initial hispeed frequency when switching to "interactive" mode
interaction_return_cycles: number of consecutive lightly-loaded samples before returning to "normal" mode
interaction_return_usage: number of used CPU cycles (in thousands per second) required to stay in "interactive" mode
interaction_panic (nanolunch only): when set to 1, allows aggressively jumping past the current hispeed frequency under some circumstances
interaction_sampling_rate/overestimate_khz: equivalent to the "normal" versions of the tuners, these take effect in "interactive" mode

Just loaded it on pa 3.15
Sent from my SAMSUNG-SGH-I747 using xda premium

It doesn't say that it has morfic colors, but looks like it does. Gonna give it a whirl
Sent from my SGH-I747 using xda app-developers app

rmead01 said:
It doesn't say that it has morfic colors, but looks like it does. Gonna give it a whirl
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It doesn't, but I'll merge it and put out a test build.

decimalman said:
It doesn't, but I'll merge it and put out a test build.
Click to expand...
Click to collapse
Is it possible they are left over from a previous kernel? Because I can def tell the difference usually and seems like it does.
Either way, advise when its updated. This governor seems solid so far.
Sent from my SGH-I747 using xda app-developers app

rmead01 said:
Is it possible they are left over from a previous kernel? Because I can def tell the difference usually and seems like it does.
Either way, advise when its updated. This governor seems solid so far.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
dkp is based off clean CM source, so it shouldn't have been merged already.
I've got test builds compiling now, and the 3.4 builds will be up shortly. Flashing the trinity-colors test build and this zip will enable trinity colors. You can toggle it with
Code:
su
echo X >/sys/class/mdnie/mdnie/trinity_colors
where X is 0 to disable or 1 to enable.
Edit: and sorry for taking so long to respond.
Edit 2: 3.4 builds are up. http://d-h.st/7Ae

Thnx for this kernel

decimalman said:
dkp is based off clean CM source, so it shouldn't have been merged already.
I've got test builds compiling now, and the 3.4 builds will be up shortly. Flashing the trinity-colors test build and this zip will enable trinity colors. You can toggle it with
Code:
su
echo X >/sys/class/mdnie/mdnie/trinity_colors
where X is 0 to disable or 1 to enable.
Edit: and sorry for taking so long to respond.
Edit 2: 3.4 builds are up. http://d-h.st/7Ae
Click to expand...
Click to collapse
Maybe I was just seeing things, had just watched jurassic park in 3d.
New "test" build flashed as well as the file to enable it. Thanks for the addition. It's very hard to go back to normal once you've been smurfed depending on your display.
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?

rmead01 said:
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
Click to expand...
Click to collapse
+1 on these questions
Sent from my AT&T Samsung Galaxy S III

rmead01 said:
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
Click to expand...
Click to collapse
Answered my own problem. I installed trickster as mentioned in OP and all voltage settings stick no problem with no issues.

rmead01 said:
New "test" build flashed as well as the file to enable it. Thanks for the addition. It's very hard to go back to normal once you've been smurfed depending on your display.
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
Click to expand...
Click to collapse
Personally, I don't like trinity colors, but I definitely understand the appeal. I merged this into 3.0 and 3.4, so it'll be standard from here on. I'll add a link to the enabler zip in the OP as well.
What app would you normally use? I'll try to support it, since I already provide several voltage interfaces. I didn't realize performance control was crashing (I'm not a fan either, so I only lightly tested). I recently installed Trickster and liked it, so I've been going out of my way to support it. It's also really easy to write support for, so that's a bonus for me.
As for schedulers, I'm not fussy. I've never exhaustively tested performance and battery life, so I don't have a preference and usually run noop or deadline. However, I've had nothing but bad results with ROW (phone never deep sleeps, and I haven't looked into why).

decimalman said:
Personally, I don't like trinity colors, but I definitely understand the appeal. I merged this in, so it'll be standard from here on. I'll add a link to the enabler zip in the OP as well.
What app would you normally use? I'll try to support it, since I already provide several voltage interfaces. I didn't realize performance control was crashing (I'm not a fan either, so I only lightly tested). I recently installed Trickster and liked it, so I've been going out of my way to support it. It's also really easy to write support for, so that's a bonus for me.
As for schedulers, I'm not fussy. I've never exhaustively tested performance and battery life, so I don't have a preference and usually run noop or deadline. However, I've had nothing but bad results with ROW (phone never deep sleeps, and I haven't looked into why).
Click to expand...
Click to collapse
good to know. Trickster mod works fine and you mention it in the OP and it's at no cost in the play store. I wouldn't worry.
I was using an app called kernel tuner because some others would only set 1 core to the governor and not both. I checked that trickster does indeed set both cores to freelunch so once that figured out I removed kernel tuner. Kernel Tuner also has the options for profiles which can be toggled in tasker for varies states. freelunch so far hasn't needed any changing so not worried about it at this point. just as an example, some governors would be better for screen on/off and tasker could switch these to edge out battery life.
The voltage app i was using is simply called voltage control. Kernel tuner doesn't do a nice job of voltage changes. But since trickster does both governor and voltage adjustments well. i'm using that with no problems now.
Thanks for the morfic, having a way to toggle it works well for people. it's as simple as a script so there's that.

rmead01 said:
good to know. Trickster mod works fine and you mention it in the OP and it's at no cost in the play store. I wouldn't worry.
I was using an app called kernel tuner because some others would only set 1 core to the governor and not both. I checked that trickster does indeed set both cores to freelunch so once that was made it was no problem. Kernel Tuner also has the options for profiles which can be toggled in tasker for varies states. freelunch so far hasn't needed any changing so not worried about it at this point.
The voltage app i was using is simply called voltage control. Kernel tuner doesn't do a nice job of voltage changes. But since trickster does both well, i'm using that with no problems now.
Thanks for the morfic, having a way to toggle it works well for people. it's as simple as a script so there's that.
Click to expand...
Click to collapse
I meant to test Voltage Control but Google wasn't letting me download anything. It's a common app, so I'll try to get it working regardless. Kernel Tuner doesn't currently work well with freelunch, and tends to hang when it's trying to read settings in the CPU screen. Otherwise, it's a nice app. I didn't realize it had Tasker support (I use Llama).
I've added a few extra bits to the cpufreq core, so governors that need to be set on both cores (like freelunch) will automatically apply to both cores regardless of what app is used. cpufreq will even enable and disable mpdecision depending on whether a hotplugging governor is running (though Trickster won't show that it's disabled).
I owe ktoonsez for the toggleable trinity colors. I slightly rewrote his patch, but it's still largely his code. It's my policy that anything that not all users will want should be optional and easily configurable.
Edit: I think I've got Voltage Control fixed. I should be able to get Kernel Tuner working without too much work. I haven't even looked into Performance Control yet.

decimalman said:
I meant to test Voltage Control but Google wasn't letting me download anything. It's a common app, so I'll try to get it working regardless. Kernel Tuner doesn't currently work well with freelunch, and tends to hang when it's trying to read settings in the CPU screen. Otherwise, it's a nice app. I didn't realize it had Tasker support (I use Llama).
I've added a few extra bits to the cpufreq core, so governors that need to be set on both cores (like freelunch) will automatically apply to both cores regardless of what app is used. cpufreq will even enable and disable mpdecision depending on whether a hotplugging governor is running (though Trickster won't show that it's disabled).
I owe ktoonsez for the toggleable trinity colors. I slightly rewrote his patch, but it's still largely his code. It's my policy that anything that not all users will want should be optional and easily configurable.
Click to expand...
Click to collapse
well good job so far. batt life has been top notch. minimal drain in use and my over night idle drain was only a few %. I have things setup to disable wifi when sleep and also turn off mobile data when wifi is connected. A bit over the top but every bit helps.
:good::highfive:

I know I've been grilling you today but...
Kind of curious what the new tunables do. I haven't touched anything since it's working so well but there is always that part of me that wonders what adjust parameters will do. Is there any kind of reference for this governor that could indicate that type of info?

Does your kernel support faux sound app?

stevehkim said:
Does your kernel support faux sound app?
Click to expand...
Click to collapse
Yes. 3.0 and 3.4 both have support.
As for tuneables, I've been meaning to post a writeup but haven't gotten around to it. You're not the first to ask about it.
Sent from my SPH-L710 using xda app-developers app

This is a fantastic Kernel! The battery life has been outstanding so far. Thank you for your amazing work!

KT-SGS4 [Kernel] Builds [Discussion] ◆ALL VARIANTS◆ [AOSP/TW/GE] ★KTWEAKER SHOP★

KT-SGS4 [Kernel] Builds [Discussion] ◆ALL VARIANTS◆ [AOSP/TW/GE] ★KTWEAKER SHOP★
ALL CREDITS GO TO THE ONE AND ONLY KTOONSEZ FOR THIS AWESOME KERNEL AND GIVING ME THE OPPORTUNITY TO PROVIDE THESE BUILDS.​
Welcome!
Some of you may know me from the S3 forums but to clarify, I had offered a number of kernel builds for users to easily obtain all within a single thread. I am proud to say it has gained a significant amount of feedback. So I come to YOU today with the same purpose in mind. I am in no way affiliated with Ktoonsez or his work. I’m just a simple member of the XDA community who happens to be a huge supporter of this kernel and its creator. This is just my way of giving back. I am aware of some of the issues that may occur on updated builds for some users as well as the difficulties faced when fine tuning the kernel and this is my response to that:
This is by no means intended to replace any of the original KT-SGS4 kernel threads. The purpose of this thread is simply to work in conjunction with them by providing a variety of builds for users to experiment with and see which versions function properly on each of their respective phone models. I'm also bringing to you my Ktweaker Shop filled with tons of pre-configured settings compiled by myself and others in attempt to further assist S4 users with improving their overall experiences on this device or to simply use as a baseline to work upon tweaking further. So I’ve gathered just about all of the current and previous kernel builds I had hidden within my pc as well as all the various Ktweaker settings and am sharing them with the public. I hope this makes a difference for all you guys. ENJOY!! :good:
POST #2: Reserved for T-MOBILE users
POST #3: Reserved for AT&T users
POST #4: Reserved for SPRINT users
POST #5: Reserved for VERIZON users
POST #6: Reserved for INTERNATIONAL users
POST #7: Reserved for the KTWEAKER SHOP
POST #8: Reserved for SCRIPTS & TEST PROFILES
No need for flashing previous builds to receive OTA's as all posts will be updated regularly upon future releases. So please be sure to refer back here for all builds from this point moving forward!
Please make absolutely sure you are downloading from the post intended for your phone. Nor I or Ktoonsez will be held liable for anything that may occur to your device. So please...
***FLASH AT YOUR OWN RISK***​
"Smart stay and smart scroll on pre-MF4 TouchWiz ROMs require the 2013-06-10 TW build."
Click to expand...
Click to collapse
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
Click to expand...
Click to collapse
If you are manually UPDATING the kernel, follow my recommended procedure for best possible results:
1) Backup current Ktweaker settings
2) Navigate to Settengs > Apps > Ktweaker
3) Clear cache and data then force stop
4) {Optional} Open any root browser, mount as r/w, then navigate to /system/app/ and delete Ktweaker apk
5) {Optional} Clear all Superuser logs
6) Reboot Recovery
7) Flash kernel
8) Wipe cache/dalvik
9) Fix permissions
10) Reboot
11) Restore Ktweaker settings
12) Profit?
If you get this message after booting up the kernel:
"The device has detected an application attempting ..."
Go to the "/system/app/" folder and delete the files that begin with "knox"
Click to expand...
Click to collapse
NOTE: If at any point Ktoonsez no longer wants this thread open it will be closed without question.
Please visit original kernel thread for change logs, extras, etc...
If you like and support his work, donate with this link:
http://forum.xda-developers.com/donatetome.php?u=4325945

**********T-MOBILE**********​
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM
•Must have CWM or other custom recovery installed
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•Updated USB driver
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/k9ryAE0dwLHs
Google Edition KitKat 4.4 VERSIONS:
https://copy.com/hsciC7dkz66V
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/9Gtgf0GUJkS4IU8
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/4ZzqCaMCwfDx
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/kEWuwwaGj8j2
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/EGHYzNqxuLGd
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/P0SYiTNnxfIj
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/doRqwyyJgbNz
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2289140

**********AT&T**********​
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM
•Must have CWM or other custom recovery installed
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•Updated USB driver
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Canadian users, DO NOT FLASH the kernel from this post. You MUST flash the TMO version from post #2
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/bTEPKJuknXn3
Google Edition KitKat 4.4 VERSIONS:
https://copy.com/X0ZwwQVRHPKd
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/6a8eptTrL6gD3hT
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/lSb0xRxqmICV
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/deGgFdixXTXW
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/BIusi3ksxYws
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/hfKGlCGgCSB1
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/O02Gej8ozbOw
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2292341

**********SPRINT**********​
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM
•Must have CWM or other custom recovery installed
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•Updated USB driver
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/aNXcVH2QVfB9
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/fj30ECCfQzVf
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/lpekDcQZijcg
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/ujl1pB38cP7W
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/oinxlW3Uq9Ai
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/WLvmsMj4YCdr
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/jsvgAUpq39ti
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2288309

**********VERIZON**********​
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM for TW version
•Must have a AOSP Rooted ROM for the AOSP version
•Must have CWM or other custom recovery installed
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•Updated USB driver
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/87bRx3sudelf
Google Edition KitKat 4.4 VERSIONS:
https://copy.com/hgsxlxegZ3WD
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/6JDHcwscMNuzQyq
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/XxBonTWMjCwf
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/Z7WeSmat4YTN
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/3PkFEpycgAqU
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/rTDTNhruhpsR
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/HtHyI4MhQyPc
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2294083

**********INTERNATIONAL**********​
KT-SGS4 Jellybean kernel features
•Must have a Touchwiz Rooted ROM
•Linux kernel 3.4.86
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•CPU Overclocking
•CPU Underclocking
•Boots on stock table (USE KTweaker app to enable OC steps all the way to 2322 Mhz. BE AWARE THAT I WAS VERY CONSERVATIVE ON THE LOW SIDE OF THE OC STEPS, SO THEY WILL NEED SOME TWEAKING!)
•KTweaker app for kernel control
•KTweaker Widget
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•Thanks to Talustus we now have exFAT for Touchwiz and AOSP
Click to expand...
Click to collapse
Downloads
AOSP KitKat 4.4 VERSIONS:
https://copy.com/jcvkN6ELhSyw
Google Edition KitKat 4.4 VERSIONS:
https://copy.com/ajiB89TGosd0
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/UQPuEEUNYc04
AOSP JELLYBEAN 4.3 VERSIONS:
https://copy.com/sw8XSJUsZk09
Touchwiz JELLYBEAN 4.3 VERSIONS:
https://copy.com/rDjb2DBt6C2A
Google Edition JELLYBEAN 4.3 VERSIONS:
https://copy.com/Wk9iHznO3haQ
Touchwiz JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/yUl248Xo2RcU
AOSP JELLYBEAN 4.2.2 VERSIONS:
https://copy.com/ZyuctnlWseGE
Original kernel thread: http://forum.xda-developers.com/showthread.php?t=2297379

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the Ktweaker Shop!
Here you will find all of the pre-configured settings provided by myself and some of our fellow users. As a proud member of Team Kernelizers, I am offering a variety of profiles specifically for S4 users with their personal needs in mind as it's pretty clear no one favors the same governor, scheduler, etc.. Any suggestions are always welcome. All future settings will be added here for sharing and discussing our settings as well as gaining approval on a profile to be added into the built-in Shop in Ktweaker. Keep in mind that results will always vary per device regardless on the settings being used.
All profiles have been grouped into 3 sub-categories; "Conservative", "Balanced", and "Performance", which are used to classify each profile based on their overall performance and what they are expected to deliver to your device. The 4th sub-group is where you can find some of our best "Projects" in which offers 2 or more profiles for each. Make your selections based on your usage and apply what works best for you and your phone. We're here to help eachother out and with more options comes better experiences for everyone running this kernel. Big thanks to ALL who have contributed!
So shop around.. pick and choose.. load and go!!
Installation
Download links will include the specified profile(s) as well as an "Adjustments" and an "About" file. The "Adjustments" file is just for easy view of all the changes made to a profile compared to stock settings.
1. Download the file(s) to your phone.
2. Copy ONLY the XML(s) (DO NOT copy the "Adjustments" or "About" file) to /sdcard/KTweaker/Profiles folder using a file Manager of your choice.
3. Open Ktweaker app and click on "Profiles & Scripts" then click "Restore Prefs from sdcard".
4. The file you just copied should be listed there. Select the one you want to apply.
5. After applying, make sure the "Set options on boot" setting on the main menu of KTweaker has a little green text bellow confirming that the settings will be applied upon reboot.
6. Profit!​
Conservative​
Asking Alexandria
This is a battery driven profile in which focuses on saving as much juice as possible while also maintaining stability and providing an extremely snappy feel to your phone. It is quite possibly one of the smoothest and snappiest battery saving profiles available.
Why Asking Alexandria?
It's named after yet another one of my top favorite metalcore bands and I chose this because Alexander The Great basically ruled the world at one point and "Alexandria" is the female equivalent to that name, which has become known to mean the "one who comes to save warriors".
"Asking" was an addition to the title name as an indication in the sense that we are all asking Alexandria what she can really do to our phone.
https://copy.com/kqIXuJ1N8LLh
Bless The Child v3 (updated: 10~25~13)
Based on Ktoonservateq and aimed towards battery. This is specifically for all the battery hungry users out there wanting to conserve as much power as possible. So don't expect the BEST but rather decent performance out of this one.
https://copy.com/K1bNhNx6nFYd
Dead By April v2.2 (updated: 11~15~13)
This profile attempts to bring some of the best battery life possible to your device. It is similar to Bless The Child but takes things a step further . It now focuses more on snappiness but still maintains it's well known battery conservation. It manages to maintain a smooth ui for your average daily use.
https://copy.com/J8lnimxbvwpF
Infamous 1.0 by @PiggySmalls502
Infamous is a work of pure and utter boredom, and a desire to use the SLP governor. Profile uses very low CPU frequencies, yet still runs very smooth, while still seeing great battery life.
Click to expand...
Click to collapse
https://copy.com/qqCrRDZiZBNh
Moonlight v3 by @Tunasty (updated: 2~12~14)
This profile is based on Ktoonservateq and Mamba's Daylight profile. This profile is aimed towards battery and be able to use your phone without any lags. Performance has not been sacrificed either. Max Mhz is 1890 which works out pretty awesome. KT's AWESOMEEE kernel and Moonlight profile will make you fall in love with your phone
Click to expand...
Click to collapse
https://copy.com/yoLhPpe1QY0Q
Smooth Criminal by @ORT14
Why Smooth Criminal you ask? Simple, this profile will keep your phone running as Smooth as ever, so smooth that it is Criminal to still get this type of battery life. Last test my phone went over two days with six plus hours of screen time without a charge (see below) while still running super smooth. This profile will change your life (well maybe not). Give it a try and let me know what you think.
Click to expand...
Click to collapse
https://copy.com/yQyI4ejR7uPE
Super Battery Saver 3.0 by @MavereXx (updated: 10~7~13)
This profile is not about performance, even though its surprisingly smooth. Gentle Undervolting.. your s4 now has only a 1.1ghz processor. .. but remember: This is when battery life is all you care about!
Click to expand...
Click to collapse
https://copy.com/GKQ0OqDVociy
What Lies Beneath
This is an extreme battery performance setup in which essentially transforms your quad-core device into a dual core device.
Why "What Lies Beneath"?
You'll find that during light to moderate operations the cpu remains at lower frequencies for an extended period of time and will only jump to max when needed. Although it's clocked at a max of 1.3ghz it maintains a surprisingly smooth and snappy feel to your device at such low frequencies. This is where battery life is also expected to come in to play as well.
https://copy.com/m0EnRGUpkEMp
Balanced​
3hands by @sew3521
This profile is a combination of my 3 favorite profiles; Ktoonsified v2, Project Icarus-Kamikaze, and Balanced Bull: Reloaded. Each of these 3 different profiles has great aspects however I thought I could combine them to make one super efficient profile and this is what I came up with. There is an extreme amount of undervolting going on here however my S4 runs extrmely stable (Sprint S4 purchased on release day) and thanks to the Balanced Bull and Ktoonsified portions of this the interface is very snappy.
Click to expand...
Click to collapse
https://copy.com/wEHQOssGuSVw
Balanced Bull: Reloaded v2 (updated: 4~17~14)
These settings are very special to me as they were my very first, dating back to the Galaxy S3, and has gained an incredible amount of feedback. It has become notable for it's fairly smooth interface and amazing battery life. If this stacks up to your standards then I encourage you to use it!
https://copy.com/4XbEpD6HRYx6Qzw
Day Of Reckoning
Very similar to Nightmare To Remember but is aimed slightly more towards battery without deteriorating much of the performance. It is based off the Pegasusq governor.
https://copy.com/NkNqyUKjaudY
ECLIPSE v2 (updated: 10~25~13)
This is a performance oriented option where great battery life is also expected to intervene. This not only will bring an incredibly stable, smooth, and snappy feel to your device but will also benefit towards longer lasting battery so you can love and enjoy your phone the way you were meant to.
https://copy.com/BDIln0KrVplK
Hydra
Eclipse and Kamikaze clash with one another in this hybrid profile (BIG thanks to @mamba720027 for the amazing work done on Kamikaze!). This is perfect for those who favor one or both of these profiles. With the merging of some of the essential performance and battery elements of each profile as well as a few minor adjustments, this one also stands as it's own profile and it flies!.
https://copy.com/GuQZmkARaHKI
Ktoonsified v6 (updated: 4~17~14)
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a performance oriented option in which also offers a great deal of battery life. Haven't tried these settings yet? then what are you waiting for!! Load em up and be prepared for one of the smoothest and snappiest experiences ever!
https://copy.com/yJJgpIi40Ddp
Lateralus v2 by @CamFlawless (updated: 1~15~14)
This profile was designed in an attempt to strike a balance between battery and performance with a focus on conservative CPU scaling to maximize battery life while maintaining a smooth, fluid, and stable UI. I tested it with the Hydra script, but your personal favorite will work all the same.
Click to expand...
Click to collapse
https://copy.com/H6bXpcr0bEJr
Misanthrope by @CamFlawless
The misanthrope profile seeks to optimize the balance between battery life and a smooth, lag-free UI by following the sampling logic laid out by LuigiBull23. By allowing frequent sampling and increased polling, the profile will result in the CPU being at the optimal frequency more often and quickly. Additionally, the hotplugging parameters should allow the secondary cores to come online when needed and quickly turned off following the boost. Misanthrope is named as such, because this profile hates lag and battery drain.
Click to expand...
Click to collapse
https://copy.com/LljHyKj384rk
Nightmare To Remember
This will likely become your beautiful, never ending nightmare.. It offers a unique balance between battery and performance but unlike Balanced Bull, it is slightly more performance oriented due to the more aggressive scale up to max CPU. However, only 2 cores will be used for the majority of the time so you can still enjoy a nice buttery smooth interface with just enough juice to last you through the day.
https://copy.com/VMFboPCy2CwU
Ragnarok v2 by @mamba720027
This profile is tweak with 2 things in mind. Normal usage and gameing.
when doing normal tasks the governor would scale the frequency less aggressive and use minimum cores but would also climb to higher frequencys as required to complete a task depending on what apps you are useing.
Gameing or other high intensity tasks will have all cores active and cpu will utalize max cpu frequency.This will provide smooth gameplay for games such as Asphalt 8 and of course other similar games that requires a powerfull processor to justify its awesomeness. So if you want a low profile setup for regular usage to conserve battery and high profile setup for gameing and other high performance demanding tasks and dont want to swap between two profiles then this profile configuration should work nicely in such a scenario.
Click to expand...
Click to collapse
https://copy.com/rM3YflojYz9k
SRV v3.1 by @s3icc0 (updated: 2~14~14)
This profile focuses on excelent battery life with no restraints to performance but still keeping pretty conservative settings to allow all users to be able to use this profile (and script) without any problems. The Core 0 is driven by heavily tuned ktoonservativeq governor, ROW scheduler is used to maximize the read performance. The frequency used is 189Mhz - 1890MHz for CPU and max 450 for GPU, the voltages are -35mV for CPU and -50mV for GPU. There is no Screen Off profile. Vibrator strength is set to 50. Read Ahead is set to 1024. LED fade mode is set to slow blinking once a time.
Click to expand...
Click to collapse
https://copy.com/77TRXloQfKRm
Smooth Operator v5 by @mamba720027 (updated: 4~17~13)
This profile utalize all 4 cores on demand and serves as being a balance between battery and performance. Its as smooth as possible and utalize the full cpu power while operateing sensibly in governor scaleing.
Click to expand...
Click to collapse
https://copy.com/vmLLvFKhwwqV
*Stardust v2* by @mamba720027 (updated: 12~7~13)
This Profile I put together is based on the "AbyssplugV2" governor.
Everything is tweaked and the profile can run by itself or either use the "smooth operator V2" Script or Luigi's "Hydra" Script.
Both are found in Post#8 of the OP. The choice is yours.
Click to expand...
Click to collapse
https://copy.com/EalqZpGb4Gnh
Super Bull 2.1 by @MavereXx (updated: 9~24~13)
A derivative of Balanced Bull but aiming towards more extreme polarity of performance and battery life. Stable Undervolting for i337, i337m, m919, and i9505 CPU and GPUs. Overclocks up to 1998mhz going all the way down to 81mhz without causing severe lag or stuttering or slow wake ups. Tries to find the right balance between ultimate performance and battery life.
Click to expand...
Click to collapse
https://copy.com/Opsu7y1FLJx9
Undisputed 3 (updated: 12~11~13)
This is a universal performance setup in which combines the essential elements of other profiles by providing equal battery life, speed, performance, and stability to bring the ultimate experience to your device.
https://copy.com/UFreCzB1Wcpt
Performance​
Crimson Dragon v2.1 by @mamba720027 (updated: 1~8~14)
This is a profile that i put together from a lost in the thread Dual Core profile "Lazy Dragon". What was suppose to be a V2 Update of it turned into a 4 Core profile and something totally new, Crimson Dragon. This profile is a variable of Performace and keeping things balance. Its very smooth on TW and produce great results on AOSP as well threw testing and feedback. Please enjoy this new addition :good:
Click to expand...
Click to collapse
https://copy.com/QjuMNNyyucBD
Feed The Machine
The exact opposite of Bless the Child. This is a performance oriented option for all hardcore users. If battery isn't a priority for you then this is a great option.
https://copy.com/oKLPQmmgzc1C
Ghost Rider by @galaxys3man30
this setup can benchmark on 1890,1944 and 1998 and its been really good on battery even thou its a performance setup think im going to call it ghost rider cuz its a sleeper yea it shows good battery life but behind that is the raw performance that is on demand when needed.
Click to expand...
Click to collapse
https://copy.com/pKAMrciYgUFo
KTGaming
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a super performance oriented option which allows me to play any game with ZERO LAG!!!!!!!
Click to expand...
Click to collapse
https://copy.com/iJzItwZxSYlp
Lightning Blade v2.2 by @mamba720027
This profile is aimed at performance and efficiently uses the 4 cores somewhat better than my first performance base profile.Â
Although it's aimed at performance it could conserve on battery as well because of the way cores are handled. If you play lots of games that require speed and processor power then this profile provides both.
Click to expand...
Click to collapse
https://copy.com/zs89qlw4CQr2
Notorious by @PiggySmalls502
This is a derivative of Feed The Machine. Hotplugging was turned back on and I/O scheduler was switched to ZEN along with a few other minor changes to the profile. It's aimed towards slightly better battery life but doesn't deviate too much from the performance aspect of things found in the original profile.
https://copy.com/Ip1PJtY7LCdI
Overactive Imagination by @CamFlawless
The profile aims to be as smoooooth as possible and draws inspiration from @LuigiBull23's Rebirthing profile.
Click to expand...
Click to collapse
https://copy.com/YyyJat03RZMtH7o
Projects​
Comatose
This project was inspired by the album of the same name by my #1 favorite rock band of all time, Skillet. It consists of 3 profiles of which are also named after 3 of my favorite tracks from this album (included in the "Extras" folder) and all focus on one key element; VARIETY.
As the name suggests, "Comatose" is geared towards battery conservation. It focuses on keeping CPU low for a prolonged period but utilizes 3 of the 4 cores on touch and the 4th on demand for fluidity. Sample rates have been decreased heavily as to increase polling and allow the other cores to quickly spike towards higher frequencies for a given task then immediately drop back down as if the component had been knocked unconscious.
The second profile is "Rebirthing". This profile will counteract the affects of Comatose by heavily boosting performance as a means to bring life and energy back into this profile that remains unconscious. Rebirthing is intended for those seeking a performance-based version of Comatose but who knows... For such a power hungry profile you may just be surprised by the great battery life it also delivers.
Some of you may not favor the heavy battery conservation that "Comatose" offers or the overall power consumption of "Rebirthing" and much prefer a mashup of elements delivered between the 2 and that is the purpose of "Whispers In the Dark". This profile is directed towards finding the right balance between these 2 profiles while still acting as a it's own profile. It utilizes most of the performance aspects from "Rebirthing". The only major differences from that are touch_boost_cpu_all_cores has been disabled and touch_boost_cpu is set at 1134Mhz instead of 1458Mhz.
Like "Comatose" it uses super_conservative_screen_on as well as a high up_threshold for that extra boost in battery performance. The profile also idles at the same minimum cpu and gpu frequencies as "Comatose" but ALL profiles run at stock 1890Mhz.
All profiles maintain the same concept of rapid cpu polling. So yes, cpu will be working consistently but my theory here is that more polling will allow the kernel to rapidly check CPU usage, thus allowing CPU to change more frequently according to the load, which in turn will prevent persistent pegging of even higher frequencies and instead consume various amounts of power in various scenarios depending on your usage and consume even less when a specific task has completed and immediately drops the load.
This also applies to screen off states but that goes back to what was explained in this post regarding high vs low sampling rates and how they can greatly increase idle times depending on your screen off max.
https://copy.com/VMuyGiGJbxIc
Lucretia by @CamFlawless
The name draws inspiration from a Megadeath song with the same title. Great tune.
Balanced
This profile is based on my V1 of Lucretia and seeks to strike a balance in terms of performance and battery life. Offering exceptional performance and a fluid experience, Lucretia Balanced is a great profile for all your needs.
Performance
This profile is based on my V2 of Lucretia and is intended for those seeking high performance from their devices for the likes of gaming and such. Lag should be non-existent and your experience should be smooooooth. :fingers-crossed:
Click to expand...
Click to collapse
https://copy.com/sjCgexEGB1jo
Project Daylight v2 by @mamba720027 (updated: 12~23~13)
Day Light is focused mainly on battery conservation. I felt that its useless if its not smooth and lags alot so I add performance into the mix createing a profile that offers both while its first and foremost goal "battery performance" is still preserved and not diminish. This profile is yet unique and on a different level from my early release of "Icarus"
The contents are 3 profiles unique in their own way, "Daylight", "Daybreak" and "Experimental" along with a "Extra" folder containing wallpapers I created on our S4 for fun while testing . Kind of gives me some inspiration and sense of feel of what my objective is.
Daybreak is a crossbread profile of my Icarus Performance profile and Daylight. Its simply utilizing the performance power behind Icarus Performance profile while useing Daylight profile governor settings as its core to boost battery performance
The experimental profile is heavily undervolted/Underclocked with tweaked scheduler and governor. I taught if some of you could run it stable then it may produce great or mix results
Click to expand...
Click to collapse
https://copy.com/2vBCFVZP68gV
Project Icarus by @mamba720027
So some may wonder why the name "Icarus",why not Hyper Performance or Deadly Good Battery.
Well the reason and to begin explination,short history.
Icarus is a greek mythology who is seen today as a mythical pioneer that tried to conquer the skies.
I like that mythology cause it kinda corresponds to my own saying "fly high or fall hard" which means to aim high or fail trying. So their you have it folks and thus the profile name "Icarus".
And onto explination of each profiles.
The first is "Performance" which is catered for straight out performance with also good battery performance.
This one is for when u dont give a rats flying balls about battery really and just want everything super fast and smooth. But you maybe surprise of battery performance. I recommend everyone try this profile first. My current favorite
The second is "Conservative" this is for those seeking performance but also better battery performance than the first.
This one is the middle man or lady as u may want to refer to it. It gives the best of both worlds,performance and battery. So if the first leave you stranded then fear not, this is the one to turn too
The third is "Kamikaze" which means "god wind". It either knocks the daylight out of your Galaxy S4 due to its high undervolteing and mean intent on Battery Performance but still snappy.
This one the undervolting is of my personal voltage table that runs stable for me with other tweaks. If it runs successfully for anyone else then battery performance may be great.
This one is for those that likes the thrill of trying something new and unsure if it will work
Click to expand...
Click to collapse
https://copy.com/87kzjPQShn3Z
Sleeping Dragon by @mamba720027 (updated: 12~23~13)
Sleeping Dragon V2.1 Single Core
This is a single core profile aimed at consumeing the least battery for a time when you will be away from home or at work and away from the charger. It was a profile i played with at first as i did not expect it to mount as much with apps and system UI needing a right amount of performance from a CPU to meet todays tasks in performance. In the end i was able to tame the dragon and make it work as best as possible to achieve its goal
Sleeping Dragon V1.2 Quad-Core
This is the counter part of Sleeping Dragon Single Core but with many tweaked parameters to make it a fully functional 4 Core base profile in hopes to achieve close or same battery performace as its single core entity. Unfortunately i still am not sure if it measures up but what i know from previous test with settings @Stock it hold its own in battery department. I am pleased with the results although i would wish to see some light usage results from users. I am pleased to present users with this 4 Core or Quadcore profile
Click to expand...
Click to collapse
https://copy.com/vkDfMNiu2Sbs
If you'd like to contribute to the Ktweaker Shop all you need to do is post a profile/script you want to share and include a brief description of it's purpose. It will then be tested thoroughly by the community and based on feedback will be submitted here in the Shop for approval and sent out to the dev for confirmation on adding to the Shop in Ktweaker!
Useful Links​
Information about our scripts/profiles can be found HERE
Interested in learning how to fine tune the kernel but not sure of where to start?
Please refer to this Ktweaker User Guide (thanks to @Perseus71) and you'll be tweaking in no time!
What in the world are CPU block cycles? Please check HERE
HERE is a great app by @elesbb that will allow the end user to set individual governor options for Ktoonservativeq when turning on the screen, charging, keyboard typing, or playing media.
Link to downloadable zip for all available ktweaker Profiles (Thanks to @CamFlawless)
https://www.copy.com/s/EhjYpSmACIyz

Profile scripts
Post #8 is dedicated to Scripts that will be used with some profiles. I also added a section for current test profiles and old test/experimental profiles.
[[Quick information]]
These scripts will either control CPU Cores 2,3,4 or all 3 and are only intended to work with the Ktoonservativeq governor. They may bring performance improvements or battery improvements based on the script governor parameters and how well they function for each user's daily activities.
[[#Ktweaker Script Guide#]]
First I want to thank KT aka Ktoonsez for provideing us with his kernel and all the wonderfull features and options at our disposal to tweak and make all these profiles and script possible. Also for implementing the Ktweaker Shop into his Ktweaker app so that it would be more convenient and easy for users to utilize these custom profiles and script as to maximize users experience.
I also want to thank Luigi for letting me join his band of misfits and being part of the Shop community. This opportunity have help me to use my potential to provide profiles and scripts that users have come to enjoy and help further in the thread.
Also thanks to everyone else that is actively supporting in the thread, some that are working behind the scene to help provide improvements and better experience for everyone. Big thanks.
::#Beginning of Guide#::
This is a quick step by step guide put together to help clear up any questions or help out those new to the Profile and Scripts section found in Ktweaker.
:#Before continuing take note#:
Swapping profiles and scripts you need to apply them in the following order first:
*Script first
*Profile Second
This order is to ensure Superuser Permission is given to both the script and profile.
Also note that you could choose to run a profile without the script. Running it with the script is optional. But for best results it's advised to first try the profile with the script it was intended to use with.
#
So now you're ready to try a script with your own profile or one from the shop but undecided as which to choose or how to go about loading the script.
#
Step#1
[[Chooseing a Script]]
To choose a script navigate to "Profiles and Script/Ktweaker Shop Scripts".
Here you will find a list of Scripts. Each script is named after its designated profile that it is intended to be used with. Choose one to view "ABOUT" which gives a brief description and additional information of the script and how it can be used with addition profiles. Some may or may not give this option to be used with other profiles as it may produce undesirable results but you are free to experiment.
Choose to download the script you want to use and in the "Profiles and Scripts" section choose "LOAD SCRIPT ON BOOT". This will allow the script to run on every boot of the device once their is a script loaded.
On the go you could also choose to load another script then apply another profile in this order as to let Ktweaker give both the script and profile SU permission to run.
Step#2
[[Chooseing a profile]]
Decide on how you want to use your device for the specific day,occasion or you may just want to set it and forget it based on being a performance user, conservative or needing a Balance of both to suit your demanding needs. You could also just be curious and want to try them all to see what works for you.
So open the Ktweaker app. Navigate to the "profiles and scripts" section.
Choose "ktweaker Shop Profiles" to bring up a list of profiles avaliable to you.
Here you can choose to view "ABOUT" which gives a brief profile description as to help you decide if the profile fits what you're looking for. You can also choose to view "ADJUSTMENTS" to see the tweaked parameters of the profiles or choose the option to "DOWNLOAD" the profile which will be saved in the ktweaker folder on your internal storage.
Now that you have chosen a profile,downloaded it and want to apply it. In the profiles and script section choose "RESTORE PROFILE FROM SDCARD" and you're done.
Click to expand...
Click to collapse
[[ Script Download Section]]
Dead by April V2.2 Script
This script utilizes the Conservative governor for CPU1. It was decided to apply this to the 2nd core and leave the others at default interactive in order to better serve battery life while still maintaining the only true performance aspects of the profile within the other cores. However, as CPU1 serves more priority over any other remaining cores, this governor was tweaked with slight performance enhancements as to allow for a faster ramp up to max CPU for that core during middle to heavy operation levels but will scale back down almost instantly and thus maintaining it's goal of keeping things low as often as possible, conserving battery. It's highly recommended to use with a balanced or straight performance profile very similar to Dead By April if applying this to any other profile.
Created by: LuigiBull23
Click to expand...
Click to collapse
Dead by April V3 Script
Core 1 - Conservative
Core 2 - asswax
Core 3 - interactive
A more detailed description about this script will be updated when the script is official.
Created by: LuigiBull23
Click to expand...
Click to collapse
Balanced Bull Reloaded Script
This script applies the Asswax governor to cpu1, Intellidemand to cpu2, and Adaptive to cpu3. Much like the profile it's twealed to focus on a direct balance between performance and battery. With the utilization of these 3 governors, CPU will spend less time at higher frequencies making scaling less aggressive during light to moderate activity but use the on demand performance of Intellidemand during performance critical situations, such as in game.
It can be used with other profiles much like this one in which uses moderate thresholds as well as a touch boost of 1134 or greater. As always redults will vary.
Created by: LuigiBull23
Click to expand...
Click to collapse
Smooth Operator V3 Scripts
This Smooth Operator script uses the Abyssplugv2 governor for Core1 ,badass for Core 2 and Adaptive for Core3. Each governor is set as to not scale too quickly nor too aggresively. The smooth operator profile on the other hand was tweaked with parameters to allow these cores to run when it is truely needed and to deliver performance with the right amount of cores online and save on battery.
So on another profile this script could deliver performance or save on battery depending on how the profile is tweaked. It's Characteristics will vary. It would be interesting to see how it performs with a performance base profile
Click to expand...
Click to collapse
Smooth Operator Infinity
Core 1 - Intellidemand
Core 2 - Intellidemand
Core 3 - Intellidemand
This script was tweak to work as a univeral and future here forth along side the 3 profiles smooth operator V5, Lite and Ultra.Thus the name "Infinity" at the end. The older scripts are also welcome to be used with these as users favor or see fit.
Created by: Mamba720027
Click to expand...
Click to collapse
Hydra script
This script uses the Dancedance governor for CPU1, Wheatley for CPU2, and Badass for CPU3. This script focused mostly towards battery conservation with some performance elements. With the high ramp rates of Dancedance and Badass's limited frequency logic, the script will bias the CPU at low frequencies and will scale up conservatively or immediately shift to an optimal frequency, depending on the task at hand if or when a larger and more persistant load is placed on the CPU. Wheatley will act more as the "On demand" partner here for that extra call in performance such as in games but for the most part the last 2 cores will remain off due to the adjustments within the profile.
This can also be used alongside other profiles but is recommended to apply to those similar to Hydra in which serves as a balance between battery and performance or one that merely performance oriented.
Created by: Luigibull23
Click to expand...
Click to collapse
Stardust Script
This Stardust script uses the badass governor for Core 1 and 2 while Core 3 uses the intellidemand governor.
This script was put together specifically for the Stardust profile as it is a profile based on the AbabyssplugV2 that utilizes the Autohotplugging feature in Ktweaker. This method of hotplugging was too aggresive to acquire the desired results needed to conserve on battery so I put together this stardust script as my other option to limit the scaleing up frequency for Core 1,2 and 3. Each respective governor limits the scaleing of their assigned core to a specific frequency which can be seen useing a software to monitor core activity. This way the script helps saves on battery as the same way the theory of underclocking applies.
So if you're gonna use this script on another profile I recommend it being on a performance or balanced profile as a already aggressively tweaked powersaveing profile may deem its outcome very laggy or sluggish.
Click to expand...
Click to collapse
Undisputed 3 Script
This script utilizes the badass governor for CPU1, Intellidemand, and Asswax for CPU3. Much like the Balanced Bull Reloaded script this is a balance between battery and performance. The only mere difference is that this script ALONE is slightly more battery conservative compared to BBR but results will obviously vary, especially depending on the profile this is used with.
It can be used alongside other profiles such as Balanced Bull Reloaded as the these 2 are very similar.
Created by: LuigiBull23
Click to expand...
Click to collapse
Crimson Dragon V2 Script
This Crimson Dragon script utilizes the wheatley governor for Core 1, intellidemand for Core 2 and Dancedance governor for Core 3.
The script is focus to use these 3 cores as to help conserve on battery threw the wheatley and dancedance governor while provideing ondemand performance useing Intellidemand.This script should work best with the Crimson Dragon profile but could also be used on similar profiles that's focus on delivering a balance between battery and performance.
Click to expand...
Click to collapse
Sleeping Dragon Quad- Core Script
This Sleeping Dragon quad-core script uses the intellidemand as core 1, Adaptive as Core 2 and Asswax as Core 3. Asswaxing is probably not for everyone but whatever works right. It works wonderful for Core3 here. Anyways these 3 governor helps mainly to Balance battery and performance here as with Sleeping Dragon profile it is tweaked in a way to keep things smooth/performance enough without scaleing the cpu too high frequently and extend the battery usage per cycle.
So this script you could try it with other profiles as well that have a touch boost value higher than 810mhz implemented to simulate a similar output that Sleeping Dragon profile and script combine produces or evin better with this script
Click to expand...
Click to collapse
Day Break V2 Script
This Daybreak script uses the Adaptive governor for Core 1,dancedance for Core 2 and intellidemand for Core 3. Each of these governor is tweaked to scale each core more of on-demand as to provide fluidity and performance to the Daybreak profile because of its high conservative property. Thus this script makes it possible to add performance into a profile that may not scale aggressively to highest frequencys often as to maintain battery conservativeness.
This script could also be used with similar profiles that fits similar description as Daybreak or shows similar properties threw monitoring of the profile to learn it's characteristics
Click to expand...
Click to collapse
Day Light V2 Script
This Daylight Script uses the dancedance governor for both core 2 and 3 as core 4 is locked offline in the daylight profile. The script delivers a fast rampup of speed boost and quickly sends the cores back offline to help the profile remain true to its severe battery saveing properties.
This script could also be used with other profiles that have the cpu underclocked to help maintain battery conservative fairness.
Click to expand...
Click to collapse
Lateralus Script
This profile uses
- CPU1 = Badass
- CPU2 = Conservative
- CPU3 = Adaptive
The governors for each cores tend to keep things on the conservative side. Its a script with potential to tweak upon and use as a base.
The combination of this script along with any profile should provide a good user experience in terms of battery.
Created by : CamFlawless
Click to expand...
Click to collapse
SRV V2 Script
The script is trying to keep the philosophy of the SRV profile therefore for Core 1 wheatley governor is used and intellidemand is used for Cores 2 and 3. Works best with SRV profile or any profile with ktoonservativeq or wheatley governor for Core 0.
Click to expand...
Click to collapse
3hands Script
- CPU1 = intellidemand
- CPU2 = abyssplugv2
- CPU3 = dancedance
Click to expand...
Click to collapse
●Ragnarok Script ●
- CPU1 = Asswax
- CPU2 = Wheatley
- CPU3 = abyssplugv2
This script is tweak to work along side the Ragnarok profile to help balance out performance and battery conservativety.
Click to expand...
Click to collapse
[[Experimental Profiles]]
This section all old or new test and experimental profiles will be deposited and accessed by anyone to try or test and provide feedback by PM to the respective profile creators.
New Test and Experimental
Old Test and Experimental
This section covers preset scripts geared to help save battery and deliver performance on almost any available profile with or without an available script. These scripts also give users the ability to mix and match profiles with a wider variety of scripts of their own choosing which in-turn delivers the result they desire.
It is very important to read the description of each scripts before trying one as they contain important information to help have a successful experience.
Profiles not mention in the recommended list of each scripts are still ok to be used with any of the scripts providing you read the description before proceeding . Scripts marked with a ES (Energy Saveing) symbol means dureing my test run doing medium/heavy usage i was able to achieve screen usage times of 5 hours and higher. This does not guarantee same results for users but a guideline to follow and try.
General Battery Saveing Scripts Presets
*Conservative Preset 1
The following governors are assigned to each core
Core 1 - Badass
Core 2 - Adaptive
Core 3 - Conservative
This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Some recommend profiles tested on to use with are
-3hands
-Asking Alexandria
-Daybreak
-Lateralus
-Sleeping Dragon Quadcore
- ¤Skyline Profile¤ llllll
- ¤Skyline Profile¤ llllllll
- Ktoonsefied
- Ktoonsefied Mod
- Rebirthing
- Whispers in the Dark
Click to expand...
Click to collapse
*Conservative Preset 2
Each cores consist of the following governors
Core 1 - Asswax
Core 2 - Badass
Core 3 - Abyssplug V2
This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Recommended Profiles tested on to use with are
- Daybreak
- Ktoonsefied
- Ktoonsefied Mod
- ¤ Skyline Profile¤
- Whispers in the Dark ES
- Lateralus
Click to expand...
Click to collapse
*Conservative Preset 3
Core 1 - SmartassH3
Core 2 - Dancedance
Core 3 - Adaptive
::Note::
This script keeps the cores scaleing frequency very low to save on battery. It is not recommended to be use if you play games that require a lot of cpu power.This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Recommended profiles tested on to use with are
- ¤Skyline Profile¤ l
- ¤Skyline Profile¤ ll ES
- ¤ Skyline Profile¤ lll
- ¤Skyline Profile¤ lllll
- ¤Skyline Profile¤ llllll
- Whispers in the Dark
- Bat Pig ES
- Crimson Dragon V3
- Icarus Conservative V2
- Misanthrope
- Balanced Bull Reloaded
- Dead by April V2.2
- Ghost Rider 1.0
- Hydra
- KT Gameing
- Ktoonsified V5
- Lucretia Balanced
- Lucretia Performance
- Notorious
- Project Daylight Experimental
- Project Icarus Conservative
- Project Icarus Kamikaze
- Project Icarus Performance
- Rebirthing
- Smooth Criminal
- Undisputed 3
- Sleeping Dragon Quad - Core
Click to expand...
Click to collapse
Conservative Preset 3 V2
The following Cores are assigned:
Core 1 - Asswax
Core 2 - Dancedance
Core 3 - Adaptive
This updated version of the script brings asswax governor to be uses as core 1 while the other cores uses same governors as V1 but with updated tweaked parameters to help manage core activity more efficiently to extend your battery usage per cycle. This script was tested extensively on the profile Smooth Operator Lite V2 as a substitute to help extend battery performance. It will also work along side any other profiles based on the ktoonservativeq governor.
Click to expand...
Click to collapse
*Conservative Preset 4
Core 1 - Wheatley
Core 2 - Wheatley
Core 3 - Wheatley
This script was tweaked to provide a balance between battery and performance. This script should work on just about any profile but should not be pared along with a profile useing the Wheatley governor.
Some profiles tested on and recommend to be tried with are
- ¤Skyline Profile¤ lllll ES
- ¤Skyline Profile¤ llll
- ¤Skyline Profile¤ lll
- ¤Skyline Profile¤ llllll
- Whispers in the Dark
- Crimson Dragon V3
Click to expand...
Click to collapse
*Conservative Preset 5
Core 1 - Adaptive
Core 2 - Adaptive
Core 3 - Adaptive
This script was tweaked to keep a balance in performance and battery using the Adaptive governor for the 3 cores.
This script should work on just about any profile but should not be pared along with a profile useing the Adaptive governor.
Some recommended profiles it was tested on are
- ¤Skyline Profile¤ llllll
- ¤Skyline Profile¤ lllll ES
- ¤Skyline Profile¤ llll
- Sleeping Dragon Quad-core
- Crimson Dragon V3 ES
Click to expand...
Click to collapse
*Conservative Preset 6
Core 1 - Asswax
Core 2 - Asswax
Core 3 - Asswax
This script is tweak to be used with a balanced or performance based profile such as the "Rebirthing" profile where the CPU polls very quicky and cpu ramps up frequently. It is aimed at keeping the rest of cores activity to a minimum and use lower clock frequencies as often as possible to help reduce battery drain and provide a better experience.This script should work on just about any profile but should not be pared along with a profile useing the Asswax governor.
Profiles tested on are
- Rebirthing ES
- whispers In the Dark
- Crimson Dragon V3
Click to expand...
Click to collapse
General Performance Scripts Presets
*Performance Preset 1
All 3 cores are controlled by the wheatley governor. This script should work on just about any profile but should not be pared along with a profile useing the Wheatley governor.
Recommend profiles tested on to use with are
- Sleeping Dragon Quad-Core
- ¤Skyline Profile¤ ll
- ¤Skyline Profile¤ llllll
- Icarus Performance V2
Click to expand...
Click to collapse
*Performance Preset 2
Core 1 - SmartassH3
Core 2 - Dancedance
Core 3 - Adaptive
This profile was tweaked to maximize overall performance.
This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Recommended profiles tested on to use with are
- ¤Skyline Profile¤ l
- ¤Skyline Profile¤ ll ES
- ¤Skyline Profile¤ llllll
- Icarus Performance V2
Click to expand...
Click to collapse
*Performance Preset 3
Core 1 - Dancedance
Core 2 - intellidemand
Core 3 - Abyssplugv2
This script was tweak to have cores 1&2 scale very quickly delivering performance on demand while the last core 3 works in a slight conservative manner and not too very aggressive although it will still deliver excellent performance considering the nature of governor assigned.This script should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Some recommended profiles tested on to use with are
- Icarus Performance V2
Click to expand...
Click to collapse
*Performance Preset 4
Core 1 - Asswax
Core 2 - Adaptive
Core 3 - Abyssplugv2
This was tested on unknown profiles with incomplete data entry. It should work on just about any profile but should not be pared along with a profile useing any of the governors assigned to core 1-3.
Click to expand...
Click to collapse
*Performance Preset 5
Core 1 - Abyssplugv2
Core 2 - Abyssplugv2
Core 3 - Abyssplugv2
This was tested on unknown profiles with incomplete data entry. It should work on just about any profile but should not be pared along with a profile useing the Abyssplugv2 governor.
Click to expand...
Click to collapse
Performance Preset 6
Core 1 - Interactive
Core 2 - Interactive
Core 3 - Interactive
This script is tweaked to deliver a more fluid performance oriented interactive governor experience. Do not use this script if useing interactive as the primary governor at Core0. Will work nicely with any other governors such as ktoonservativeq and the rest found in ktweaker.
Click to expand...
Click to collapse
~~Screen Brightness Adjustments To Save Power~~
=[[Lux Autobrightness]]=
I use the app Lux Autobrightness to set the screen brightness of my device. I find it helps to miminize power consumption used by the screen and taught of shareing my profile.
To use this profile just download it from the provided link below. Be sure to backup your current LUX profile settings. Useing a file manager,navigate to the "Lux" folder on your internal storage and rename your current profile to "lux_profiles.bak". Then move the downloaded profile to your "Lux Folder" and restore it from within the Lux app.
You may want to set your method of backlight adjustment to "ON WAKE" as i have or leave it to your own desire preference as their are 4 to choose from which can be found by running the Lux App settings wizard or by going into settings/brightness and chooseing one of the 4 prefered method of backlight adjustment.
Lux Autobrightness Profile 1 Download
This lux profile is more of a balanced brightness to make the screen not too dark or bright under various light conditions.
Click to expand...
Click to collapse
Lux Autobrightness Profile 2 Download
This profile is adjusted with lower brightness values and takes more of a gradual step to make the screen brighter compare to the above profile 1
Click to expand...
Click to collapse
.
Lux Autobrightness Profile 3 Download
This Profiles uses higher screen brightness percentage as its min and upward lux thresholds to deliver a more alive and vivid screen viewing experience in just about any surrounding with little to maximum ambient lighting source. This profile is not as conservative as profile 1 or 2 but will deliver exceptional experience.
Click to expand...
Click to collapse
TIP
To help lower the screen power consumption along with the lux profile,leave the "Screen Power Saveing" mode feature turned on in your Rom power saveing mode section.

Nice!
Great work, Luigi my friend!!! Not driving an S4 yet, but I like to keep up with emerging trends and new technology...
Besides, I'll support you anytime!

shenry1307 said:
Great work, Luigi my friend!!! Not driving an S4 yet, but I like to keep up with emerging trends and new technology...
Besides, I'll support you anytime!
Click to expand...
Click to collapse
Thanks buddy!! Hopefully when and if you get the S4 this thread will come of use to you

Hey bud. Thanks for doing this thread! It was well needed. Sometimes the updated kernels don't sit right and I'm sure that's for alot of folks. I'm looking for his second set of settings that he posted in his thread. I've searched all over and cant find them. Not the ones in the op of his thread but they were extra settings about all instances of boost or something like that. Thanks in advance.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2

jdub251 said:
Hey bud. Thanks for doing this thread! It was well needed. Sometimes the updated kernels don't sit right and I'm sure that's for alot of folks. I'm looking for his second set of settings that he posted in his thread. I've searched all over and cant find them. Not the ones in the op of his thread but they were extra settings about all instances of boost or something like that. Thanks in advance.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Thanks buddy. Really appreciate the feedback. The only thing I recall him saying was that setting "sync_extra_cores" and "touch_boost_cpu_all_cores" to 1 should help with battery and responsiveness but for some users who have issues with lags or reboots should set those to 0. I have them both set to 0 and my phone runs smoothly just fine like that. All the other settings are the recommended settings by Ktoonsez.

LuigiBull23 said:
Thanks buddy. Really appreciate the feedback. The only thing I recall him saying was that setting "sync_extta_cores" and "touch_boost_cpu_all_cores" to 1 should help with battery and responsiveness but for some users who have issues with lags or reboots should set those to 0. I have them both set to 0 and my phone runs smoothly just fine like that. All the other settings are the recommended settings by Ktoonsez.
Click to expand...
Click to collapse
Man awesome. Thanks. Ok you guys are att correct? I'm verizon and what I've found is the 6/23 is the most smooth with our new base me7. Just my findings but there is zero lag. For the first time man I've set my transition scales to 1. I know you know what that means for the s4. And with our VZW me7 roms the stock kernel has been the smoothest but pip and smart stay didn't work. This is odd cause this is the very Ktoonsez kernel that broke these features in mdk. So I flashed it on me7 and all things in the world are marvelous. Lol
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2

jdub251 said:
Man awesome. Thanks. Ok you guys are att correct? I'm verizon and what I've found is the 6/23 is the most smooth with our new base me7. Just my findings but there is zero lag. For the first time man I've set my transition scales to 1. I know you know what that means for the s4. And with our VZW me7 roms the stock kernel has been the smoothest but pip and smart stay didn't work. This is odd cause this is the very Ktoonsez kernel that broke these features in mdk. So I flashed it on me7 and all things in the world are marvelous. Lol
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Actually Ktoonsez is ATT while I'm on T-Mobile but as you can see, like the S3, I've been collecting every build from each variant of the S4 just because Ktoonsez is awesome in what he does and I'd do anything to help him out!
Glad to hear all is running smoothly

boterkaaseneieren said:
I really don't get this thread, you mean to say all these builds are the original kernels of KT? And you post it in dev section. You can only make a thread in dev section of its your build. Going to report this and see wat a moderator think of this. Why make a mirror thread?
Click to expand...
Click to collapse
You obviously don't know who luigibull23 is. You'll thank him later.
Sent from my SGH-M919 using xda premium

boterkaaseneieren said:
In general where this belongs.
Click to expand...
Click to collapse
LuigiBull23 said:
Yup. Me and a mod spoke about it and all is well now
Click to expand...
Click to collapse
That shut you up didn't it boterkaaseneieren! Stop hating on people! and chill out! The guy gave plenty of credit and as he mention he got permission so why you on his cause like a nagging women? even on his thread!!! stop trying to seek brownie points please!
Sent from my GT-I9505 using Tapatalk 4 Beta

So...just flashed Liquid Smooth, my first aosp rom on the S4. For some reason the on demand governor which I usually use stays at max clock speed and doesn't go down. So I'm going to try out ktoonsez now. What settings do you recommend for that crazy 7 hour battery life you were able to get on the S3 @LuigiBull23? Lol
Sent from my SGH-M919 using xda premium

marcoxx626 said:
So...just flashed Liquid Smooth, my first aosp rom on the S4. For some reason the on demand governor which I usually use stays at max clock speed and doesn't go down. So I'm going to try out ktoonsez now. What settings do you recommend for that crazy 7 hour battery life you were able to get on the S3 @LuigiBull23? Lol
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I'll pm you my current setup. Nothing fancy.. Just warming up lol

LuigiBull23 said:
I'll pm you my current setup. Nothing fancy.. Just warming up lol
Click to expand...
Click to collapse
What Rom are you currently running Luigi?

ahoslc said:
What Rom are you currently running Luigi?
Click to expand...
Click to collapse
Slim Bean

[GUIDE] Custom Kernels: A Guide on What you Need to Know

I was searching for info about MPDecision and stumbled upon this..it's a very good read specially for beginner and those that want to know more about kernel specifics and how they work..this was written back in 2012:
---What IS a kernel?---
The ELI5 answer: "An analogy: the Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car." - faux123
In other words, the kernel is the software that controls the hardware at a very low level.
---The Stock Kernel---
The "stock" kernel is the kernel that comes with your Nexus 4 out of the box. It's compiled directly from Google's kernel source code and shipped on your device with zero modifications. A custom kernel, on the other hand, compiles the stock kernel source and adds various modifications to that code.
What are those modifications that kernel devs employ?
To understand what they mean, you need to understand the features of the stock kernel first!
What are the stock kernel parameters?
CPU min frequency: 384 MHz
CPU max frequency: 1512 MHz
Governor: Ondemand
I/O Scheduler: CFQ
What does each parameter represent?
CPU frequency: you can simply think of this as the "speed" the CPU is running at
Governor: regulates the CPU frequency based on many different parameters such as load and time-in-state. Here is an excellent list of many of the most common CPU governors and how each works. Note that you will only see a couple of the CPU governors on this list in whatever kernel you use. Ondemand and Interactive are by far the most widely used, and are the ones you should look at.
I/O Scheduler: handles how the system makes disk access; Please refer to the previous linked thread and scroll down to the 4th post for a detailed list.
What else do you need to know?
--PowerHAL--
PowerHAL is what makes Project Butter. The powerHAL is a ROM component that tells the kernel to BOOST the CPU frequency to higher values in response to UI inputs. The higher CPU frequencies can better respond to UI demands so the overall experience is smoother than without. - faux123
--mpdecision--
All Qualcomm based phones have Qualcomm prorprietary userspace binary called "mpdecision" aka m(ake)p(oor)decision. Instead of letting the kernel itself to decide what frequencies and how many cores to run, this "mpdecsion" binary polls the kernel run queue statistics and decides for the whole system the "optimal" frequency and the "optimal" number of cores to use. The concept is fine, except the decision making is done in userspace and it's 100% closed source so there's no way to tweak it and there's a latency (because all userspace binaries needs to "poll" the kernel for the latest information which is slightly delayed). - faux123
ELI5: mpdecision is a proprietary Qualcomm daemon that makes calls to the SoC (the entire chip your phone uses) to manage the cores. The OS (PowerHAL) makes a request to mpdecision and then mpdecision makes a request to the first two cores to ramp them up. - _motley
Why do kernel devs mess with these?
In practice, the PowerHAL ramping up trick successfully got rid of a lot of the UI lag since Android 4.1. However, this comes at the cost of battery life (and heat generation!) The reason for this is because the system ramps up its CPU on every touch input, rather than waiting for the kernel to calculate the load and ramp up accordingly. On the Nexus 4, when the PowerHAL makes a call to mpdecision it locks the minimum CPU to 1026 MHz upon touch input for the first two cores. While this DOES give you the buttery-smoothness you would expect, it's a bit overly aggressive. This is part of the reason why stock kernel tends to heat up your phone when you play around with it a lot.
---Custom Kernels---
What changes should I look out for?
--mpdecision--
Many kernel devs don't like Qualcomm's implementation, so they work around or get rid of it. Franco, Faux, Bricked, Matr1x, Motley, and Trinity have gotten rid of it/used their own implementations. Harsh and IntersectRaven's leave it intact. Every kernel dev implements things in their own way, and the only way to tell which is better for you is to try each one. This is by far the biggest change any kernel dev can make, as it completely alters how the system handles hotplugging and CPU scaling. In general, you'll find kernels without mpdecision running cooler, with greater battery life, but with a little more lag (made up for by other tweaks).
--thermald--
A binary that controls how to throttle your CPU based on CPU and battery temperatures. You can find the config file in /system/etc/thermald.conf. Stock configs lead to aggressive thermal throttling (battery temp. at 36 degrees C for example, which is easily achieved). You can look into the file and see the various thresholds and actions that the system takes to lower the temperature of the CPU and battery, but it isn't really necessary. Just know that some kernel devs may have changed this in order to allow your phone to run at higher frequencies for an extended period of time, or to further make your phone run cooler.
--Underclocking--
Quite straightforward, by limiting the max frequency your CPU can use, you use less power (higher frequency results in more power dissipated by the CPU).
P = C(V^2)f where C is capacitance, V is the voltage, and f is the current frequency
..gives you an idea of how underclocking (and undervolting) uses less power.
--Undervolting--
This is all the rage today, with many users trying to get as low as possible stable voltage. It's arguable how much undervolting saves battery life, but there's no doubt it reduces heat dissipated from the CPU (see: the above formula). Your CPU is located on the top half of your phone, which is likely where you've felt the heat before. How much your chip can successfully undervolt depends on what type of binned CPU you have. If you want to undervolt, I recommend checking if the voltages you set are stable by running the StabilityTest app and doing the Scaling Stability Test. The frequencies' voltages definitely don't scale linearly, so don't assume that doing global undervolts will be the best you can do. You'll have to apply voltages one by one if you truly want the lowest your chip can possible handle.
--Overclocking/overvolting--
Bricked, Trinity, and Motley's kernel implement this, because it CAN be dangerous. Overclocking usually requires overvolting the processor (so the overclock is stable) but overvolting carries with it the risk of bricking your phone by frying the CPU. Know that doing this has some risks before you try it. Some kernels like Matr1x and Faux's also allow for the GPU to be overclocked if games run a little slowly for you.
--Hotplugging--
Hotplugging is where the individual cores on your phone switch on/off depending on the load on the CPU. The advantage of hotplugging is a reduction in power used because the cores will only turn on when needed. Kernels that use the auto_hotplug binary by Thalamus (that would be Matr1x, Motley, Trinity, Bricked at the moment) allow you to fine tune the enabling and disabling thresholds. These parameters are generally for advanced users only as they require you to write scripts to control them.
--Color Control--
Gives you the ability to change color multipliers and gamma settings to calibrate your display. If you feel your display is too yellow, or you miss the previous feel of your previous phone, then you can mess around with this to get better color reproduction. You can find some user examples here to give you a good idea of what can be done. Gamma control currently requires either Faux's control app or for certain kernels you can use scripts to control them.
--Wakelock reduction--
Some kernels have reduced the msm_hsic_host wakelock duration so your phone enters deep sleep more often. How much improvement this makes is debatable, and whether or not this wakelock is even an issue is also debatable.
--Kernel modules--
Some kernels make modifications to the low-level drivers that interact with the components of your phone. An explanation of what is commonly touched can be found here. You don't really have to worry about this, just know that something is being improved when a kernel dev mentions it.
---Installing a Custom Kernel---
Just flash the zip in your recovery of choice. No need for wiping cache or anything. However, one thing to note that might save you some headache in the future is: what exactly are you flashing? When you flash a kernel, you are not just flashing the kernel, you are writing to the entire boot partition. The boot partition is made up of the kernel AND the ramdisk (the ramdisk is an image that the kernel mounts read-only at boot, it is basically used by the kernel to mount the rest of the system images). Some kernel devs pack their own ramdisk into their boot.img that you are flashing, so when you try to flash a DIFFERENT kernel, you end up in a bootloop. (An example: flash Franco kernel --> flash Faux kernel on top = bootloop.) To solve this you need to reset the ramdisk by flashing a stock reset kernel with the stock ramdisk.
Click to expand...
Click to collapse
all content taken from [URL="http://www.reddit.com/r/nexus4/related/158t1i/custom_kernels_a_guide_on_what_you_need_to_know/"]a reddit post i found which was originally written [/URL]by reddit user IAmAN00bie

Red Magic 5G MOD Kernel GPUOC 900/940mhz +battery 1.4 STABLE!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*** NOTE THAT 3.16 NA OR 4.13 Red Magic 5G SPECIFIC ROMS SHOULD BE USED WITH THIS KERNEL! THE COMBINED ROM (WITH RM5S) HAS UPDATED KERNEL CODE THAT IS NOT FULLY COMPATIBLE AND NUBIA HAS NOT UPDATED THEIR SOURCE CODE ***
*** Please click Thanks (Thumbs up icon) on my post here if you like my kernel and rate the thread 5 stars, then just use it and enjoy - if you want to send me a beer or two feel free - you don't have to use PayPal - Revolut and Amazon.com (USA) gift cards avoid fees. I like to hear from happy users I hope you are glad that you have the fastest phone in the world currently. The active cooling in this device is utilized to the extreme with MOD kernel, meanwhile your battery usage will be much improved at the same time. How? Well, that's all in the source code, free for all to fork it on GitHub and modify to your liking. Just don't forget to credit me and the many great devs that made the improvements possible... without them, there would be no MOD kernel. This is just a hobby of mine and I like to produce a nice product that all can enjoy. I'm also quite friendly and although I may tell you no I won't add that feature (such as network hacking tools), I won't hold anything against you for asking. I have not been compensated other than by some generous folks on my Telegram channel, so this whole project is basically self funded. Red Magic will not support it, unfortunately, but you can if you feel the improvements are worth it. I believe they are, but I come from a biased point of view as the sole developer for RM5G ***
********************************************************************************************************************************************************************************************************************************
NOTICE: YOU ASSUME FULL LIABILITY FOR ANYTHING THAT MAY HAPPEN TO YOUR PHONE USING THIS KERNEL. ALTHOUGH IT WORKS 100% ON MY PHONE, IT MAY NOT WORK THE SAME ON YOURS. THE PROCESS OF ROOTING A PHONE AND INSTALLING A CUSTOM KERNEL ALWAYS HAS RISKS, SO IF YOU ARE NOT COMFORTABLE ASSUMING THOSE RISKS, DON'T INSTALL THE KERNEL! THIS IS A TYPICAL DISCLAIMER FOR CUSTOM KERNELS I HAVE FOUND NO BUGS WITH IT AT ALL. USERS ON CN, GLOBAL, AND NA ALSO HAVE NOT FOUND ANY PERFORMANCE ISSUES OR BUGS (DO NOT USE V7.14 or V8.11) IF YOU DON'T KNOW WHAT YOU ARE DOING, IT'S BEST TO REMAIN STOCK. OR JOIN THE TELEGRAM GROUP, AND GET SOME REAL HELP.
********************************************************************************************************************************************************************************************************************************
Easy root method: https://forum.xda-developers.com/nu...nner-tutorial-unlock-bootloader-t4131585/amp/ although I suggest still using Magisk 20.4 for root.
Note: if you've already rooted and want to upgrade, people have had success saving the kernel as boot.img and TWRP as recovery.img in SmartPack, vbmeta skip as vbmeta.img and placing into the ROM update.zip using MT Manager (a root browser) and saving the updated file. Then do a Settings / System Update / click the 3 dots / local update and select your modified file. In fact I upgraded from 3.13 to 3.16 NA ROM without losing anything this way. Now for normal installation:
Custom kernels require root and Magisk to be installed. This is due to the signature not being signed by Red Magic (the company) itself. Following the above method you will still pass SafetyNet and most apps will work without trouble. If you have a specific app that detects root, well, Magisk Hide the app from Magisk Manager and see if that fixes it. You should also Hide Magisk Manager from various forms of detection (under Settings). Last case is to move the installation of Magisk under a random directory (which I have not had to do and all my banking apps still work), only if the root detection methods used by your app providers are more picky.
MOD KERNEL 1.4 STABLE:
RELEASE NOTES:
Block mode I/O has been changed to Multi-Queue from Single-Queue so your default scheduler is now MQ-deadline (credits to PappaSmurf, excellent kernel dev). You can choose between mq-deadline, kyber, and none in a kernel manager under I/O scheduler. From my benching with Androbench, it doesn't make much difference which one you use. Some have parameters you can tweak. None literally means no scheduler which is fine on an SSD, and has no overhead if you want to select it in a kernel manager. I always recommend SmartPack. To get settings to stick you Toggle "Apply on Boot" and it will go to what you've selected after 5-10 seconds on the next boot.
All debugging has been turned off completely on BBRv2 - thanks to PappaSmurf (I missed a few spots), and debug can't be turned back on from the userspace now. BBRv2 is selected as the default TCP algorithm which users have explained as a "no-lag" algorithm while gaming. It's just generally a fast algorithm all around. For me it works great, but you can still choose from many different algorithms in a kernel manager if you want to.
In SmartPack / Misc / TCP Congestion Algorithm, you have many choices: reno / bbr / bbr2 / bic / cdg / cubic / dctcp / westwood / highspeed / hybla / htcp / vegas / veno / scalable / lp / yeah / illinois. A SmartPack script is included below you can add in SmartPack to show the true TCP algorithm as it will always show Reno (a bug also shared by FK kernel manager). Below it's called Check_TCP.sh just go to SmartPack / Script Manager / Import / Check_TCP.sh. Afterwards, click Execute to see the active algorithm. If you set it on boot, this is the algorithm that will run, despite what the field says in Misc.
Battery is running very well on normal usage I'm getting around 7.5% active screen on drain over 7 hours and <0.7% screen off drain over 13 hours at 90hz screen setting. This is with actively using the phone for multiple "normal" purposes, reading emails, browsing websites with Chrome, reading news, streaming videos, etc. various shopping (Amazon/eBay) and tracking, Reddit feeds and live video, and other random "daily" tasks, up to 10 apps open at a time. Gaming of course will drain more, as will 144hz. I also have dark mode enabled in Settings. To get idle drain down I disabled 3 additional wakelocks that were causing high screen off drain, and so far I haven't seen an issue with blocking them. I also removed wakelocks that no longer exist since the Boeffla WL Blocker default list was created (it was quite old) so it now should be relevant for this device, with no interaction on the users part to disable anything via a kernel manager. Still, in SmartPack you will see a Wakelocks menu in case you install an app that causes idle drain to rise, this can be used to find and block wakelocks causing the problems. It can sort by wakeups and also by time. As it states though, you should be very careful what you disable. There can be unintended consequences and most wakelocks are not well documented as to what they actually control.
Dynamic Stune Boost is entirely removed from the kernel code now, as I didn't see any benefit from using it with this kernel.
Don't forget Dynamic Fsync is hidden under Misc in SmartPack which if you turn on will speed up your SQLite speeds. AnTuTu will penalize you for this, ignore it, your phone will be faster - but I leave it off by default. Androbench will show the true memory benefit. It is significant if an app does a lot of operations on databases. Journaling for the database is held in memory until the screen is off, then it is written. Although there is a chance of a data loss or corruption with this on if the device were to crash, it is safer than just turning off fsync. If you have any unstable apps, just leave it off - better to be safe. On a solid system though, you may notice better performance.
Also remember under SmartPack / GPU there is AdrenoBoost - it is set to low. You can alter to medium or high to get faster transfer between GPU frequencies, although it has worked great for me the way I use the phone. For you another setting may suit you better. Recall RedMagic OS only allows several frequencies which I spaced out as well as possible at 305mhz, 400mhz, 525mhz, 670mhz, 800mhz, and either 900 or 940mhz depending on the version you installed.
Overall I'm very satisfied with this kernel build and don't plan on adding or subtracting anything from it for the time being. It does what it should do, gives solid performance, and good battery life. My last score on AnTuTu setup with defaults 12GB/256GB was 682K which currently is still the top performing phone out there - running at 940mhz GPU. Not all phones can handle 940mhz so use 900mhz if yours cannot. If there are enough requests for an intermediate build (say 925mhz) I can add one later off the same code base. Also note in releases there are "gaming" builds that don't keep track of CPU times at each frequency, which was a request by users to remove any potential lag while gaming. I run the non gaming version, useful if you want to tweak battery usage, but nonetheless, both versions are there for you to use.
I'm on Telegram t.me/NubiaRedMagic5G_Mods as long as I have the phone. Which will be quite a while if Red Magic / Nubia decides to fix N41 5G in the USA.
Also note that all the features of this kernel (besides ones specifically added by me) are the creation of other developers whose contributions are all notated in the kernel source code. Some of the developers that have contributions here or helped me in some fashion: Resurrect88, DD3Boh, PappaSmurf, kdrag0n, Ayrton990, Flar2, Lord Boeffla, plus many more across the globe. Without them, I wouldn't be making any kernels! And I'm sure there are many other devs I've forgotten to mention, I thank all you guys for your help and support.
MOD 1.4 Download Link:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.4
PRIOR RELEASES BELOW:
8th Release:
MOD KERNEL 1.35-BBRv2 STABLE:
RELEASE NOTES:
This is an intermediate release - I realized that the prior release was draining far more battery than it should, and I found the source was debug related code in BBRv2 from Google. So this is the updated kernel that gives you battery life like before this TCP algorithm was added.
CONFIG_CPU_FREQ_TIMES=y has also been added so you can see in a kernel manager how much time is spent in each mhz block for each set of processors. This can be useful if you set in a kernel manager (like SmartPack) a minimum CPU mhz to see how much time is actually spent at each level.
The code base also has Dynamic Stune Boost, but I haven't had time to optimize it for the device, so it's just on default settings. So there are 2 versions of this 1.35-bbr2 release. At some point it will be enabled as part of a regular release (some 17 commits squashed together into 1, Stune Assist was causing issues so I turned it off). The main idea of that set of code additions is to run the device at lower frequencies, saving battery, while still achieving the same performance level to the user of the phone. If you want to try different options for it in SmartPack or FK Kernel Manager you can.
Downloads:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.35-bbr2
7th Release:
MOD KERNEL 1.3-BBRv2 STABLE:
RELEASE NOTES:
Added the 31+ commits for BBRv2 from Google. Squashed the commits down to 6 by author from Google (for easy code maintenance). It's said to be the best TCP (internet congestion) algorithm so this sets it by default. You can still select from the others added in 1.3, as mentioned only EX Kernel manager properly shows them. But SmartPack if you choose the one you want under Misc, then click Apply on Boot, it actually will load the TCP algo you selected. It's just a visual defect. I also made a script for SmartPack uploaded to show you the TCP algo that's selected in my repo you can install so you can verify for yourself. Give it 10 seconds (default on boot setting) before you check.
Downloads:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.3-bbr2
6th Release:
MOD KERNEL 1.3 STABLE
RELEASE NOTES:
All this release adds is TCP congestion algorithms. The only kernel manager which correctly shows the algo set correctly is EX Kernel Manager. Using SmartPack or FK Kernel Manager will tell you that you're always on Reno, when in fact, you aren't. I'm not quite sure if this is bug related to 865 kernels as a fellow dev had the same experience (on an Op8 Pro). Now the default is set to BBR. Why? No reason specifically, although it is one of the better algorithms for internet usage. You can easily change in any kernel manager and set on boot which one you'd like to use (see above RELEASE NOTES if using SmartPack). But this gives you plenty of options:
BBR, BIC, CDG, CUBIC, DCTCP, WESTWOOD, HSTCP, HYBLA, HTCP, VEGAS, RENO, VENO, SCALABLE, LP, YEAH, ILLINOIS
You can Google the benefits of each and pick what you like. Or just leave it alone. The prime idea of MOD kernel is that you don't need to adjust anything it just works optimally without any intervention. Read the release notes for prior features that have been added. There are many just not summarized in a single place at the moment. All the optimization has been done for Red Magic OS.
Downloads:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.3
5th Release:
MOD KERNEL 1.25BETA
RELEASE NOTES:
This release is mostly about battery savings. I'm averaging around 6.5% active drain on normal tasks with this version (90hz setting), and around 0.5% screen off drain. A big improvement over the stock kernel. So I ended up with about 13 hours SOT + 24 hours screen off on 1 charge! See the picture, I stopped at 11% left. Now I didn't say anything about gaming. If you want to game and have power saving benefits, don't enable any of the built in boosting modes in the game launcher - the Red Magic OS will override everything. Let the kernel do the work for you. And if you're seeing any graphics lag, go into SmartPack kernel manager (free) and go under GPU, Adreno Boost is enabled on low, you can set it to medium or high. That will increase the speed at which the GPU throttles up and down.
1) Switch to the Energy Model for CPUs: Several subsystems (thermal and/or the task scheduler for example) can leverage information about the energy consumed by CPUs to make smarter decisions. This config option enables the framework from which subsystems can access the energy models.
2) Added CPUMASKS for the Little, Big, and Prime cores from Sultan Alsawaf Sultan: SultanXDA, prime added by Danny Lin: kdrag0n.
3) Added kernel control of the minimum frequencies for the little and big clusters by Danny Lin kdrag0n. They are set to run at their minimum running frequencies when idle 691mhz (little) and 710mhz (big) which results in nice power savings when web browsing or just under low load in general. Prime cluster min is not set as it makes the CPU scheduler function poorly.
4) Added AdrenoBoost by Aaron Segaert: Flar2, with all its changes squashed into 1 commit. Defaults to low setting. As mentioned before, you can change in SmartPack, and set on boot if you need a higher value than low: https://github.com/SmartPack/SmartPack-Kernel-Manager/releases
5) Uploaded the various GPU OC files to the repo, It still will just build off the default one, but they are here to be complete. 940mhz version again is posted, Building direct from the repo will give you 900mhz max GPU.
Downloads:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.25BETA
4th Release:
MOD KERNEL 1.2 BETA
RELEASE NOTES: (Note a 940mhz GPU clock edition is available, if you want to try it, a few of us have had good results on it. Likely the max an 865 GPU can run. You'll sacrifice the power savings, however):
1) Enable Power-efficient workqueues by default, add a toggle that can turn this off via a kernel manager (under CPU in SmartPack). Enabling this makes the per-cpu workqueues which were observed to contribute significantly to power consumption unbound, leading to measurably lower power usage at the cost of small performance overhead. Have also added many other power saving features to the defconfig. The phone is a beast, power savings is a good thing to implement.
2) Update the LZ4 decompressor algorithm with a much faster variant for the ZRAM swap, now version 1.8.3-9 credits Gao Xiang [email protected] and many others (check commits). Speed improvement below (should help on 8GB devices):
Compressor name Compress. Decompress. Compr. size Ratio Filename
lz4hc 1.7.3 -9 12 MB/s 653 MB/s 42203253 42.20 enwik8
lz4hc 1.8.3 -9 11 MB/s 965 MB/s 42203094 42.20 enwik8
3) Default scheduler is set to SQ deadline. Should see minimal improvements in speed until I get a MQ variant working. On the task list ahead.
Download Link:
1.2BETA: https://github.com/mrslezak/NX659J_Q_kernel/releases/download/1.2BETA/MOD-RM5G-GPUOC-Beta1.2.zip
940mhz GPU release here, it's still 1.2BETA, just with the max clock a few of us have been able to use. That doesn't mean your device can for sure handle it, but give it a try if you'd like! Note the power savings will likely not be there vs the other release at 900mhz:
https://github.com/mrslezak/NX659J_...oad/1.2BETA/MOD-RM5G-GPUOC-940mhz-Beta1.2.zip
3rd Release:
1.15BETA: https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.15BETA
This is a HEAVILY updated release of the MOD kernel 1.10BETA - I realized the phone's software will allow 6 frequency clocks, although 1 did not have a regulator defined (now patched). NOW I VERY HIGHLY suggest installing SmartPack Kernel manager. It will give you insights into the kernel and how it's performing and it's free. It also will let you adjust added options now in the kernel. Just root your phone and flash from TWRP. If you haven't already installed Magisk, then install that too. There's a guide I posted on XDA about that. Use the experimental method there is no reason to unlock your bootloader. https://forum.xda-developers.com/nu...how-to-unlock-bootloader-redmagic-5g-t4081743
RELEASE NOTES:
1) Bugfix: there was 1 missing 800mhz GPU frequency regulator clock on the prior version. This has been set to TURBO, 1 level under the 900mhz regulator of TURBO_L1.
2) Boeffla WakeLock blocker (v1.10 + tweaks) has been added to reduce battery drain when the phone is not being used, using the latest version and all patches. A default block list is included. You can access in SmartPack Kernel Manager under the new menu that will appear "Wakelocks" - especially investigate if your phone has high idle drain, you can experiment with blocking other wakelocks (which don't allow your phone to sleep). Or you can leave as is. I get just under 1% drain (screen off) and the phone sleeps quite often with this version. Take a look at the screen shot! That's just normal phone usage, not gaming.
3) All debug entries (except those required) have been stripped completely out of the kernel. This results in less wasteful debug information being generated.
4) The default algorithm for ZRAM has been changed from LZO (high compression, but slow) to LZ4 (slightly less compression, but fast). LZ4 algo was added. It still defaults to 4GB.
5) Dynamic Fsync has been added to the kernel as well. This patch allows journal entries to be written only when the screen is off. I.e. they are cached and written afterwards. This increases database performance. It is disabled by default so in SmartPack Kernel manager, if you'd like to turn it on, go under Misc, select Dynamic Fysnc, and select apply on boot. There is always a risk of data loss when delaying writes, although I've personally never have had issues - it only happens if the phone crashes, and mine has never crashed on this kernel. This won't normally increase your benchmark scores (except AndroBench), it increases SQLite database access speed. Up to you to use or not, works fine on my device.
6) Here are the updated frequencies (note there is 1 more). Will have to wait for AOSP before I can add back more. Note the 670MHz is likely the 865+ max frequency per the release notes today on the device (which I assumed by the source code anyhow pre-announcement): 900MHz / 800MHz / 670MHz / 525MHz / 400MHz / 305MHz
AS ALWAYS, USE AT YOUR OWN RISK!!!
Github Source:
https://github.com/mrslezak/NX659J_Q_kernel
Initial Release:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.0.BETA
Second release - gets over the "reset to 490mhz" bug caused by the system software, at the expense of reducing frequencies to 6 total:
https://github.com/mrslezak/NX659J_Q_kernel/releases/tag/1.10BETA
Newest release -> will be posted on the top from now on.
Telegram:
https://t.me/NubiaRedMagic5G_Mods
And note the AnTuTu benchmark is just a first run after installing. 670K is likely a record on any 865 phone. The last bench turning off 4GB ZRAM (12gb/256gb device) I got 673K. AnTuTu doesn't equal performance, but if you've benched you'll see this is an insane improvement over the stock kernel. Only when the demand is there will it scale up to 900mhz. I've been using for a while now and notice no difference in battery life. The Adreno driver is very good at handling extra clock frequencies efficiently without modification (despite an "Adreno Boost" that is often added to kernels). The gamers using the kernel are making statements that they couldn't imagine the game play any better than it already was, but now it's even smoother.
Unfortunately the way the Nubia software behaves, it auto-resets to power level 5 (which was 490mhz) on the 1.0BETA on boot and also after boosting the frequencies up. I tried every possible way to bypass this but eventually just gave in and removed frequencies. So the BETA1.10 and above have less frequencies but will always revert to 305mhz, the base minimum frequency of the device. Hopefully once we have AOSP ready I can add more.
MattoftheDead
I.e. M.O.D. Kernel Developer
The first Red Magic 5G OC kernel.
Xiaomi Mi9 / Mi9T Pro Pie V2 and Q V1.5 Kernel Dev

Nice work. Do you notice any benefits to OCing the GPU like that? I don't think there are many games that would benefit atm.

This is amazing !!! :laugh:

Is this going to work on all roms like CN, NA or EU Roms? Im currently running NA 3.11 flash from CN rom with root and twrp

We have people using it on CN Global and NA versions no problem at all. Works fine on every model.

Kernel is fully functional no issues at all.
CN Rom to NA Rom v3.11
305mhz min to 900mhz max confirmed and using smart pack to control the frequency
Thank you for this hopefully there is more development i really appreciate ur effort

Kernel building is just a hobby of mine, I was posting a minimal kernel to get some more kernel developers on board to hopefully add more features. I usually add Boeffla Wakelock Blocker and Dynamic Fsync and call it a basic kernel. The last super kernel I made took way too long, and I don't have that kind of time anymore - boost functions and underclocking to balance out the battery life and such. Development work doesn't pay anything, I didn't get the phone free, all my donations go to other developers. And I have a full time job and family. But if anyone wants to port over my MOD Kernel Q 1.5 Mi9 features, well that would be a super kernel. It's just really, really time consuming, time I don't have at the moment. And the merging of source has to be EXACT or you end up with a really slow phone rather one that balances underclocking, boost, and overclocking.

MishaalRahman said:
Nice work. Do you notice any benefits to OCing the GPU like that? I don't think there are many games that would benefit atm.
Click to expand...
Click to collapse
All the gamers using the kernel are reporting that the games run smoother than before, which no one thought was possible. It is already a flagship device. But the GPU OC with the Adreno driver scales when needed up to the frequencies that it has in the table and has no issue on 670, 800, and 900mhz reported so far. There are gamers on NA, Global, and CN ROMs, with no bugs reported. No issues and everything works properly. I have tested myself and although I'm not a gamer, all the functions work as they should. It still connects via Bluetooth, it still takes photos and videos, etc. There is no lag whatsoever. Overall I think the frequencies are ideal for this device with it's advanced active cooling system. Other devices however, with passive cooling, are unlikely to handle the increased GPU clocks.

I found an unusual bug where the GPU Minimum Frequency will reset on its own to 490mhz even if i set the minimum frequency to 305mhz im using smart pack kernel manager that you provided and cool tool btw to monitor the gpu frequency.
I also set the battery optimization to off on smart pack so it wont turn off itself.
This also happens when i played games that actually boost to 800 to 900mhz then after i close the game it sets back the minimum frequency to 490mhz so i have to set it again to 305mhz on the kernel manager to save more battery and lower the temps.
I also notice it sets back to 490mhz minimum frequency by just watching youtube videos so i have to set it back to 305mhz again. I tried different kernel manager too like Franco Kernel Manager and Kernel Audiator and still doesnt fix the issue
I think this was a minor bug for sure
I never touch the GPU governor btw
Performance was super nice thou i scored 645k on antutu on my first run but for now im going back to stock and gonna wait for your next update

What to do to root the phone without breaking the fingerprint please. I read the article publish nothing understood someone can explain to me step by step. I am an amateur I never root a phone. I have cn 2.55 16gb.

I don't have the same issue - I just tried to recreate it by watching a YouTube video and I went back to SmartPack and it still shows 305MHz GPU frequency. Although I'm using the debloated / optimized ROM I created Black Magic 5G which has everything setup properly, Nubia apps frozen, everything moved to 3rd party apps. NETFLIX patched to 4K HDR10, YouTube Vanced, a ton of root utilities, AdAway ad blocker, etc. You can find it on the Telegram channel (I'm using the NA/Global version of Black Magic 5G). Then I watched Netflix, still at 305mhz. As I have no idea how you've setup your phone, I just can't recreate it.
shaifabra5 said:
I found an unusual bug where the GPU Minimum Frequency will reset on its own to 490mhz even if i set the minimum frequency to 305mhz im using smart pack kernel manager that you provided and cool tool btw to monitor the gpu frequency.
I also set the battery optimization to off on smart pack so it wont turn off itself.
This also happens when i played games that actually boost to 800 to 900mhz then after i close the game it sets back the minimum frequency to 490mhz so i have to set it again to 305mhz on the kernel manager to save more battery and lower the temps.
I also notice it sets back to 490mhz minimum frequency by just watching youtube videos so i have to set it back to 305mhz again. I tried different kernel manager too like Franco Kernel Manager and Kernel Audiator and still doesnt fix the issue
I think this was a minor bug for sure
I never touch the GPU governor btw
Performance was super nice thou i scored 645k on antutu on my first run but for now im going back to stock and gonna wait for your next update
Click to expand...
Click to collapse

Yeah maybe because you modified the rom.
Im currently running Flash Global V3.11 when i tested your kernel no modification made im just rooted with TWRP Installed and i posted this kernel on red magic 5g group on facebook and 3 of us having the same issues as well.
Im gonna try it again on V3.13
UPDATE:
still returning to 490mhz as minimum frequency after gaming and after watching one youtube clip
kinda sad hopefully you can fix this bug on the global rom that nubia provided if you have the time, great kernel for gaming because of the 900mhz boost and the phone can sustain this boost because of the active fan

Why don't I have a roughly similar score?

Is it possible to overclock the CPU as well? They officially release the specs sheet of ROG Phone 3 it has overclocked CPU (3.091ghz) and an overclocked GPU. I know this phone can keep up with those clocks because of the cooling system but the problem is the battery life. But still, its worth it.

Blink003 said:
Is it possible to overclock the CPU as well? They officially release the specs sheet of ROG Phone 3 it has overclocked CPU (3.091ghz) and an overclocked GPU. I know this phone can keep up with those clocks because of the cooling system but the problem is the battery life. But still, its worth it.
Click to expand...
Click to collapse
I believe Qualcomm blocked overclocking of CPUs quite a while ago from SD845. Only GPUs can be overclocked.
Though I don't know if devs have gotten tools to get around it.

The 490 bug looks like it's related to the gaming mode APK resetting the min frequency. I can't decompile or recompile APKs so I don't have a way to get around the system reverting to 490 without removing 3 other frequencies. It seems hard-coded in the app that it only expects to see 5 frequencies so to have all working properly, 3 need to be removed. This is in contrast to what my buddy dev on the Op8 Pro can do, but this device is designed differently in how it boots and custom apps that increase frequency clocks. If any devs are good with APKs it's a very simple function call that sets the minimum GPU frequency. The only odd thing I see is that the minimum power level stays at 8 (minimum) which corresponds to the lowest clock speed. That number doesn't change in a kernel manager when the min GPU clock reverts to 490.
I'm off on vacation not near a PC but will try to come up with a stock # of clock frequencies that still scrolls smoothly between them and the Adreno GPU driver. May take a few tries but it's quite easy to modify. I already think 180mhz is too low from using it, it's more of a sleep frequency some suggested going this low but I think the phone design is for 300+. I prefer to use more clocks for better throttling but have to work with what we are given and do the best inside those boundaries.
No you can't raise CPU clocks on 865 devices that ROG device is supposedly using the 865+ or whatever the mid device is named between the 865 and 875. They have blocked CPU OC hardware wise for some time now.

mslezak said:
No you can't raise CPU clocks on 865 devices that ROG device is supposedly using the 865+ or whatever the mid device is named between the 865 and 875. They have blocked CPU OC hardware wise for some time now.
Click to expand...
Click to collapse
Qualcomm's Meizu’s CMO Wan Zhiqiang recently commented on Weibo saying that there won’t be a Snapdragon 865 Plus this year.
We will see!

No 865+ this year..
Trust me whatever they call it it's already defined in the source code as a second GPU bin clock for another device ID. So maybe it won't be called an 865+ but there is some device between the 865 and 875 coming out. I have OEM confirmation as well this device exists the name isn't important. I can tell you the top GPU frequency is 670mhz that's it, vs. the 587mhz default on the 865. Still the 865 handles 900mhz GPU no problem the only benefit would be higher CPU clocks. And an extra GPU clock. Which I'll attempt to spoof next time I get near a PC.

mslezak said:
Trust me whatever they call it it's already defined in the source code as a second GPU bin clock for another device ID. So maybe it won't be called an 865+ but there is some device between the 865 and 875 coming out. I have OEM confirmation as well this device exists the name isn't important. I can tell you the top GPU frequency is 670mhz that's it, vs. the 587mhz default on the 865. Still the 865 handles 900mhz GPU no problem the only benefit would be higher CPU clocks. And an extra GPU clock. Which I'll attempt to spoof next time I get near a PC.
Click to expand...
Click to collapse
Is it possible to overclock the memory clock too? I assumed that 900mhz is the core clock.

mslezak said:
Trust me whatever they call it it's already defined in the source code as a second GPU bin clock for another device ID. So maybe it won't be called an 865+ but there is some device between the 865 and 875 coming out. I have OEM confirmation as well this device exists the name isn't important. I can tell you the top GPU frequency is 670mhz that's it, vs. the 587mhz default on the 865. Still the 865 handles 900mhz GPU no problem the only benefit would be higher CPU clocks. And an extra GPU clock. Which I'll attempt to spoof next time I get near a PC.
Click to expand...
Click to collapse
You're right, that makes sense.
I'm glad they are making a refreshed chip.
On another note, do you think we will see an overclocking tool in the future?
Possibly with a custom ROM?