Database Develop

Chaos Kernel users' thread—tips, experiences, and NXTweaks settings

Hello everyone.
A few people in the Chaos Kernel development thread suggested that there should be a thread in the general section devoted to the use as opposed to the development of this great kernel.
For those who don't know, Chaos is a CAF kernel developed by @neobuddy89 for use with Cyanogenmod. Rather than being a place for discussing Chaos's pros and cons with respect to all the other great custom kernels available, this thread is for sharing the NXTweaks settings that we have found work well for us, whether this is with a view to achieving great performance, great battery life, or some balance of the two.
My own settings are based roughly on @neobuddy89's own settings that he posted several pages back on the dev thread. I'm looking for a solid balance between performance and battery, and I find that these settings deliver both (at least vs stock CM kernel).
Every setting not mentioned is left at the default setting for the built-in 'balanced' profile.
CPU:
PE WQ: enabled
OC: 2.496GHz
Gov: Intelliactive
Sleep gov: Conservative
IO: FIOPS
Sleep IO: ROW
Hotplug: Intelli HotPlug (eco mode disabled)
Colour Profile: Piereligio TrueRGB V7
Fast Charge: Auto
Cron zipalign task enabled.
What do you guys and gals think? (As an aside, I used to be able to oc to 2.576GHz on Chaos 10.2 with earlier CM11 M builds, but since Chaos 11 with M4, 5 and 6, I get an instant kernel panic as soon as I enable this. I'm going to post on the dev thread with my last kmsg when I hit ten posts. I don't talk much!) Specifically, what's your experiences with FIOPS vs ROW?
I find that this gives me an utterly smooth UX across every app, combined with enough battery to get me from 0700 to late in the evening. Sorry I don't have screenshots or SO states (or benchmarks) but I prefer to use the entirely subjective criterion of whether my phone *feels* fast and long-lived.
Hope people like this thread. Also, I'm new here, so sorry if I've got any etiquette wrong.
Edit: I should've said, I'm running a D821 N5 with CM11 M6, and the latest Chaos 12 nightly. I was on CM nightlies but I got sick of it.

Kernel: 12.0 5/12
Rom: SOKP MS-1
Profile based: Balanced
CPU:
PE WQ: enabled
UC: 1.728 GHz
UV: -20 MHz
Sleep Freq: 1.497 GHz
Boost Freq: 1.267 GHz
Sync Freq: 1.574 GHz
Gov: Intelliactive
Sleep gov: Intelliactive
IO: FIOPS
Sleep IO: Row
GPU: 320 Mhz
Polling: 14 ms
Hotplug: Cyanogen
DT2W: Enabled
Power key toggle: Enabled
Sound: Custom
Headphone: 260
Speaker: 262
Attenuation: 39
Mic: 260
Camera: 258
Colour Profile: Piereligio TrueRGB V7 / Vivid
Gentle Fair Sleepers: Disabled
Dynamic Fsync: Enabled
Fast Charge: Auto
Cron: All enabled
GPS: North America
Thanks for creating the thread =]

Kernel: Always latest.
Rom: AICP RC-4.0
PE WQ: Enable
CPU Freq: All Default.
UV: -25mV (from Kernel Tweaker)
Gov: Intelliactive.
Sleep gov: Conservative
IO: FIOPS
Sleep IO: ROW
Hotplug: Intelli-Hotplug (Eco Mode Disable)
GPU: Default
KSM: All Disable
Sound: Quality
Color Profile: Piereligio TrueRGB V7
Color Tweak: Stock
Dynamic Fsync: Enable
Cron Jobs: All Enable except Update Ad-Block.
This is my favourite settings and it's running great

fluther said:
My own settings are based roughly on @neobuddy89's own settings that he posted several pages back on the dev thread. I'm looking for a solid balance between performance and battery, and I find that these settings deliver both (at least vs stock CM kernel).
Click to expand...
Click to collapse
I have changed back to default settings of default profile with KSM, ZRam (for testing), Quality Sound, TrueRGB Color profile. :fingers-crossed:

Trying to change color profile display with nxtweaks but I'm not able to apply it
Used Franco display control and seems to apply correction Piereligio_v7
CM 11 build 05/12 and chaos latest nightly
Anyone?
Inviato dal mio Nexus 5 utilizzando Tapatalk

NXtweaks:
max CPU freq: 1.574
max CPU susp freq: 1.190
min CPU susp freq: 300
boost duration: 0ms
input event boost duration: 0ms
input event boost freq: 1.190
sync threshold: 1.190
cpu governor: interactive
cpu sleep governor: conservative
io sched: fiops
io sleep sched: fiops
hotplug: MSM
boosted cpus: 1
max cpus online: 2
max gpu freq: 200
polling interval: 30ms
gpu governor: MSM
dirty ratio: 20
dirty background 5
set ZRAM to 200MB
swappiness: 80
freq throttle: 65
freq throttle suspend: 60
core throttle: 70
core throttle suspend: 70
TRICKSTER MOD (beta tester app version):
tcp congestion: westwood
read ahead buffer size: 384
GOVERNOR (interactive):
above: 20000
go_hispeed_load: 99
hispeed_freq: 652800
min_sample_time: 20000
sync_freq: 300000
target_loads: 90
timer_rate: 20000
timer_slack: 40000
up_threshold_any_cpu_freq: 960000
up_threshold_any_cpu_load: 90
multicore power saving: 2
gpu max freq: 200
UNDERVOLTS:
300: -65
422: -65
652: -65
729: -65
960: -65
1574: -65
all the other: -50

giajp said:
dirty ratio: 20
dirty background 5
set ZRAM to 200MB
swappiness: 80
Click to expand...
Click to collapse
80 swappiness?? Any diff?

neobuddy89 said:
80 swappiness?? Any diff?
Click to expand...
Click to collapse
I don't know, try it. I always use this recommended settings by Faux
Sent with my Google Nexus 5

It seems that some of you are underclocking and undervolting quite aggressively. How does this work out for you in terms of battery? And how much does performance suffer?
@neobuddy89 is there any particular reason why you use KSM and ZRAM, given that the N5 has 2gb of ram already? Also, what's your take on the various governors and schedulers?

With the chaos is the only one situation when the performance doesn't suffer so much (try and give me your opinions). Battery incredible
{
"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"
}
Half WiFi, half data
Edit: @fluther i think the ZRAM, on CM11 is indispensable. The memory leak is still too strong, unlike stock/aosp
Sent with my Google Nexus 5

giajp said:
With the chaos is the only one situation when the performance doesn't suffer so much (try and give me your opinions). Battery incredible
View attachment 2744321
Half WiFi, half data
Edit: @fluther i think the ZRAM, on CM11 is indispensable. The memory leak is still too strong, unlike stock/aosp
Sent with my Google Nexus 5
Click to expand...
Click to collapse
Not to offend.....seriously.....but that is OK battery life..... And with all that under clocking and volting..... You've basically shown it is unnecessary. You've gained little, if anything doing it....and I imagine your performance must be suffering.
I think realistically.... You can under volt or under clock the phone into the ground and at best gain only minutes of screen time....and an hour or 2 overall total life.
Just my experience with it. Never touch clock and volts now.....there's no significant change to battery, yet performance degrades the lower you go.
My 2 cents. ?

lezzi said:
Trying to change color profile display with nxtweaks but I'm not able to apply it
Used Franco display control and seems to apply correction Piereligio_v7
CM 11 build 05/12 and chaos latest nightly
Anyone?
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Yeah, I have the same problem. Not sure why. It used to work just fine when I first flashed the kernel. Let me know if you figure it out.

Hi everyone. I said in the OP that I'm not terribly interested in benchmarks, and while this holds true, I though I'd share this great antutu result. However, I've a question: why the poor integer performance? @neobuddy89 ?
Sent from my Nexus 5 using XDA Premium 4 mobile app

fluther said:
Hi everyone. I said in the OP that I'm not terribly interested in benchmarks, and while this holds true, I though I'd share this great antutu result. However, I've a question: why the poor integer performance? @neobuddy89 ?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe because we use our own hotplug engine? Someone with more Antutu test knowledge might able to help.

Sorry, I should've said this was using intelliactive and intellihotplug.
Sent from my Nexus 5 using XDA Premium 4 mobile app

guys, got really frustrated with DT2WAKE issue, it could work flawlessly all day long, and all of a sudden it fails to wake the device up.
if i wait about one minute without using the power button, dt2wake works again and keep working for some time - then it happens again.
it happens on freshly installed and wiped system with all the latest nightlies of Chaos kernel + pacman rom.
from DEFAULT SETTINGS i only lower CPU freqs to 1.7
PE WQ on
GPU 320, polling 30ms
MSMhotplug with 2 cores
DT2W enable
color profile TrueRGB
vibrator strength 0
what can POSSIBLY relate to WAKE issue, any apps/settings? maybe nxtweaks are being killed in background? really annoying, especially while driving.
suppose to wake and get to dialer without looking and with one simple action, look at the phone once to find contact and dial.
and its like: look at the phone to check if DT2wake worked, if not try again, then slide the phone in palm to use the power button etc. etc.
i rely on this function and really need it working all the time.

oo0 said:
guys, got really frustrated with DT2WAKE issue, it could work flawlessly all day long, and all of a sudden it fails to wake the device up.
if i wait about one minute without using the power button, dt2wake works again and keep working for some time - then it happens again.
it happens on freshly installed and wiped system with all the latest nightlies of Chaos kernel + pacman rom.
from DEFAULT SETTINGS i only lower CPU freqs to 1.7
PE WQ on
GPU 320, polling 30ms
MSMhotplug with 2 cores
DT2W enable
color profile TrueRGB
vibrator strength 0
what can POSSIBLY relate to WAKE issue, any apps/settings? maybe nxtweaks are being killed in background? really annoying, especially while driving.
suppose to wake and get to dialer without looking and with one simple action, look at the phone once to find contact and dial.
and its like: look at the phone to check if DT2wake worked, if not try again, then slide the phone in palm to use the power button etc. etc.
i rely on this function and really need it working all the time.
Click to expand...
Click to collapse
As I told over PM, will clean up that code next week which may help..
Sent from my Nexus 5 using XDA Free mobile app

@neobuddy89, thanks! it's an old post. also, i guess, no one else has that issue. good thing - i have no SODs like many people reported with any of your builds. tested Furnace kernel for a while, dt2wake works perfectly, but having better battery with Chaos.

Anyone have a high performance set up that can be used for daily use that they want to share?
Sent from my Nexus 5 using XDA Premium 4 mobile app

JLO155 said:
Anyone have a high performance set up that can be used for daily use that they want to share?
Click to expand...
Click to collapse
Interactive governer,
sleep governor conservative
CPU 300-2500mhz
Hotplug see picture
After 2 load circles the battery consumption and performance is amazing (latest AICP nightly) with a sot time of ~5 hours with auto brightness. Regards, Matt

Changing CM11S Performance profiles with Tasker - Can it be done?

Note: I'm not referring to the CM Profiles such as Home, Work, etc.
I haven't purchased Tasker, nor have I used the program before. Is it possible to get Tasker to change CM11S kernel profile to Performance when screen comes on, and Power-saving profile during night hours? I am preferring Performance instead of Balanced at the moment because it makes quite a difference in responsiveness and smoothing out scrolling, but it's probably eating away at battery during non-use.
Or am I just better off waiting for a non-mpdecision custom kernel to be more stable and just use that instead? Franco for e.g.
{
"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"
}

U can modify the highest and lowest CPU frequency with tasker which is sort of what you're looking for

Yes, you can modify the performance profile using Tasker but I you need to be rooted to change it. This is how I am using Tasker to change my CPU profile when my screen is on and off. Obviously you can change CPU settings on your own accord.
Screen off (powersave mode):
(leave CPU at 0)
CPU governor to powersave
max frequency to 1036800
(everything else leave alone)
Screen on (balanced mode):
(leave CPU at 0)
CPU governor to interactive
max frequency to 2457600
(everything else leave alone)
You don't have to limit the CPU frequency, but I figured it would be the best way to maximize the benefits of powersave mode, not to mention restricting any apps to crank up the CPU while phone is sleeping.
I would not recommend using powersave mode normally. The phone will become very unresponsive. However, I am setting my phone to screen off setting if battery is between 0-15%. That may change to 10% if if ever becomes troublesome.
Here are all the different governor settings: http://tasker.dinglisch.net/userguide/en/cpu.html

So I just updated my OPO to 30O and now Tasker says the CPU option is not available one my device.
Anyone know what is going on? Is there another option to use?
[UPDATE] Oops, I lost root.

Bump! I want this too...

I've used this but i noticed battery drain.

128
hmm i consider if it's needed to use Tasker on Lollipop

butro said:
Yes, you can modify the performance profile using Tasker but I you need to be rooted to change it. This is how I am using Tasker to change my CPU profile when my screen is on and off. Obviously you can change CPU settings on your own accord.
Screen off (powersave mode):
(leave CPU at 0)
CPU governor to powersave
max frequency to 1036800
(everything else leave alone)
Screen on (balanced mode):
(leave CPU at 0)
CPU governor to interactive
max frequency to 2457600
(everything else leave alone)
You don't have to limit the CPU frequency, but I figured it would be the best way to maximize the benefits of powersave mode, not to mention restricting any apps to crank up the CPU while phone is sleeping.
I would not recommend using powersave mode normally. The phone will become very unresponsive. However, I am setting my phone to screen off setting if battery is between 0-15%. That may change to 10% if if ever becomes troublesome.
Here are all the different governor settings: http://tasker.dinglisch.net/userguide/en/cpu.html
Click to expand...
Click to collapse
What about having one profile to set the CPU to Balanced mode when the screen is on, and having an exit task to set it to powersave?
I think I'll try that, but maybe with a delay of a minute or two before running the exit task.

Frankyg said:
What about having one profile to set the CPU to Balanced mode when the screen is on, and having an exit task to set it to powersave?
I think I'll try that, but maybe with a delay of a minute or two before running the exit task.
Click to expand...
Click to collapse
That's how I have it set up but my profile is screen off. powersave when off, exit task (screen on) is back to balanced. I do like your wait a minute after screen off idea. I just implemented that. Thanks!

Thanks, this is what I was looking for. But why only CPU 0, do we not have to repeat the same for CPU 1,2,3. I guess CPU number refers to respective cores.
And how much is tasker effecting the battery discharge being in background.

I had up and downs using Tasker to set CPU Governor, so ended up using Boeffla kernel which supports this kind of management natively as described in the FAQ page: http://www.boeffla-kernel.de/index.php/faq.
Boeffla kernel has both CM 11s and CM 12 versions, so you are covered whichever ROM you are running.

it is possible, but not with tasker!
i will write an app therefore
it's just a hour task or so, will upload it to the playstore later this week.
i don't know exactly but i think you need to be rooted, but maybe i'm wrong, will look into it later

butro said:
Yes, you can modify the performance profile using Tasker but I you need to be rooted to change it. This is how I am using Tasker to change my CPU profile when my screen is on and off. Obviously you can change CPU settings on your own accord.
Screen off (powersave mode):
(leave CPU at 0)
CPU governor to powersave
max frequency to 1036800
(everything else leave alone)
Screen on (balanced mode):
(leave CPU at 0)
CPU governor to interactive
max frequency to 2457600
(everything else leave alone)
You don't have to limit the CPU frequency, but I figured it would be the best way to maximize the benefits of powersave mode, not to mention restricting any apps to crank up the CPU while phone is sleeping.
I would not recommend using powersave mode normally. The phone will become very unresponsive. However, I am setting my phone to screen off setting if battery is between 0-15%. That may change to 10% if if ever becomes troublesome.
Here are all the different governor settings: http://tasker.dinglisch.net/userguide/en/cpu.html
Click to expand...
Click to collapse
i have set cpu , i have set governor to ondemand but don't know what to do with scheduler. Also is there screen off and on setting in it ?

AAA118 said:
i have set cpu , i have set governor to ondemand but don't know what to do with scheduler. Also is there screen off and on setting in it ?
Click to expand...
Click to collapse
Not sure what you mean about the scheduler. But the screen off and on is controlled by a new profile. Add a profile and select event, then display off. When display off is active, you select your powersave task. The exit action of display off profile, or screen on, should be activating the ondemand task, returning the device to full speed.
I did it like this to have one profile to control that one action. More efficient than two profiles, one for screen on and off.

k.harish.r said:
Thanks, this is what I was looking for. But why only CPU 0, do we not have to repeat the same for CPU 1,2,3. I guess CPU number refers to respective cores.
And how much is tasker effecting the battery discharge being in background.
Click to expand...
Click to collapse
I'd like to know that, too.

Time delay for task... how?
Frankyg said:
What about having one profile to set the CPU to Balanced mode when the screen is on, and having an exit task to set it to powersave?
I think I'll try that, but maybe with a delay of a minute or two before running the exit task.
Click to expand...
Click to collapse
Hi there! How do you set the 1 minute delay to start task?? Thanks
For example, i have it set to display off, governor battery saving and 1036800 max freq and min 300000 freq, but i want it to start the task about 1 min later, becouse sometimes rigth away we go tether again, for some reason...

Anyone knows more about this nowadays?

aussieglis said:
Anyone knows more about this nowadays?
Click to expand...
Click to collapse
user boeffla kernel + tasker. just follow the guide from boeffla site.

Tuning your CPU (for [ROM][WT88047][M][6.0.x] CyanogenMod by ketut.kumajaya)

A tip for interactive governor
It seems that many have faced CPU fixed at 800mhz.(including me)
Let's not declare It as a bug, but rather do something about it.
Aim: to make the CPU utilize 400mhz and 200mhz
Step1: Open build.prop find"ro.min_freq_0"
Set it to '200000' .
(Note there are two such property ,find and change them both)
Reboot.
Step2: ( this reportedly not working ! :so try the workaround in 2nd post)
i)download '98interactive' from attachment. Extract the file.
ii)paste the file in system/etc/init.d
And give permission as rwx rx rx (same as other files there)
iii)the script will be automatically applied at reboot.
Or you execute it via kernel auditor app /init.d section
DONE
Try this out see if it works for you
CREDITS:
ketut.kumajaya for his tremendous unbelievable hard work
He has made these ROMs possible.
Cyanogenmod (for the ROM)
Google(for android)
XDA for its knowledge.
Press thanks if I helped you:good::good::good:

what does the script do ?
better battery savings when CPU is idle
Sets up interactive governor using default values (used in many ROMs)
+ little tweaks to enable use of lower CPU frequencies like 200mhz and 533mhz.
+reduced above_hispeed_delay : so that CPU can scale to higher frequencies very quickly.
how can I remove the script?
Well just delete the init.d script '98interactive'
script not working?
First do step 1
Then,
open kernel auditor app
CPU->CPU governor tunables-> set these values
{
"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"
}
Set apply on boot ON
Downloads

I wouldn't recommend lowering min frequency to 200 or 400 MHz, i set the CPU to 200mhz when screen locked,and when i would,unlock the CPU would lag a bit to climb to higher frequency delaying lock screen.this operation would require a governor which will have to raise CPU frequency to upper limit in min steps(like straight to 1000)

GeorZ said:
I wouldn't recommend lowering min frequency to 200 or 400 MHz, i set the CPU to 200mhz when screen locked,and when i would,unlock the CPU would lag a bit to climb to higher frequency delaying lock screen.this operation would require a governor which will have to raise CPU frequency to upper limit in min steps(like straight to 1000)
Click to expand...
Click to collapse
you do have a sound logic but practically interactive calculates its next freq with the rate of 30ms which is .03 sec.
a lag of .03 sec too small with respect to the battery savings achieved by staying at 200mhz when idling.
how ever I will try to come up with something better,
PS: remember I kept a reserve post

GeorZ said:
I wouldn't recommend lowering min frequency to 200 or 400 MHz, i set the CPU to 200mhz when screen locked,and when i would,unlock the CPU would lag a bit to climb to higher frequency delaying lock screen.this operation would require a governor which will have to raise CPU frequency to upper limit in min steps(like straight to 1000)
Click to expand...
Click to collapse
Updated the OP with better/simpler values

im not much of a developer.. so from step 2 how do u place file and how to give it permission?? and when i check my cpu frequency from kernal auditor, it increases and decrease from 400mhz to 1200 mhz... so do i need to tune the CPU and does it increase battery lasting long?
---------- Post added at 03:36 PM ---------- Previous post was at 03:16 PM ----------
kushal.bhandari37 said:
im not much of a developer.. so from step 2 how do u place file and how to give it permission?? and when i check my cpu frequency from kernal auditor, it increases and decrease from 400mhz to 1200 mhz... so do i need to tune the CPU and does it increase battery lasting long?
Click to expand...
Click to collapse
Some how i replaced the file and installed.. sorry to trouble you
the script didnt work. so i am going to change from cpu governor. so what value should i place for above_hispeed_delay?? confused.

kushal.bhandari37 said:
im not much of a developer.. so from step 2 how do u place file and how to give it permission?? and when i check my cpu frequency from kernal auditor, it increases and decrease from 400mhz to 1200 mhz... so do i need to tune the CPU and does it increase battery lasting long?
Some how i replaced the file and installed.. sorry to trouble you
the script didnt work. so i am going to change from cpu governor. so what value should i place for above_hispeed_delay?? confused.
Click to expand...
Click to collapse
Copy paste this whole line "25000 1094400:50000 1152000:80000"
This means 25000 is default value while others are for specific CPU frequency.
:good:

@Saurabh_Umadikar

prodigy_dev said:
@Saurabh_Umadikar
Click to expand...
Click to collapse
Now my device is using the 200MHz frquency after the mod.
Sent from my HM2014818 Prime using Tapatalk

[KERNEL]Huawei Ascend P6S / P7 K-Tuned Kernel

Ascend P6S / P7 K-Tuned Kernel​Hello! Finally I decided to make a new thread for kernel with description of all features.
So, here they are:
CPU Governors:
PegasusQ
AbyssplugV2
Optdemand
Interactive
Impulse
Pwrctrl_hotplug default
I/O Schedulers:
CFQ
Deadline
ROW
Noop
FIOPS default
TCP Congestion:
HTCP
Reno
BIC
CUBIC
Westwood+ default
Upstreamed to 3.0.101 version
SELinux permissive for 5.1.1
LZ4 kernel & ramdisk compression
Backport random from kernel 4.0 branch
ExFAT version updated from 1.2.5 to 1.2.9
F2FS support
Fixed 5.1.1 GPU performance regression bug
USB Fast Charge
Intelli-Plug
Asynchronous Fsync
CPU overclock: enabled 1996MHz CPU frequency and 1795MHz for P6S
CPU undervolting
GPU overclock: enabled 700MHz GPU frequency for P6S
GPU undervolting
Adjusted stock CPU & GPU governor thresholds for better performance
DoubleTap2Wake
Sweep2Sleep
init.d support
set_immutable binary removed from ramdisk for 4.4.2
Speed up system startup
Now more detail about some features:
Governors
PegasusQ
Governor from Samsung with hotplug support. Perhaps, the most tunable and flexible one.
Parameters description:
sampling_rate: the interval with which governor will be carried out. Less value - better responsiveness, but at the same time, more load for CPU by governor itself.
sampling_down_factor: amount of iterations governor will stay at highest frequency before go down.
up_threshold: load threshold in % above which CPU frequency will be increased.
up_threshold_at_min_freq, freq_for_responsiveness: at frequency lower than freq_for_responsiveness will be used up_threshold_at_min_freq threshold - provided for better responsiveness.
down_threshold: load threshold in % below which CPU frequency will be decreased.
freq_step: step of frequency encrease in % from maximum frequency.
hotplug_freq_*: high and low frequency thresholds for making decision about hotplug of each core.
For clarity, it looks like this:
Code:
static int hotplug_freq[4][2] = {
{0, 1596000},
{208000, 1795000},
{416000, 1996000},
{624000, 0}
};
In this array left column is frequency at which core will be disabled; right column - frequency at which will be enabled next core.
hotplug_rq_*: analogous parameters set (array), defining queue task length for making decision about hotplug of each core.
Code:
static int hotplug_rq[4][2] = {{0, 50}, {50, 100}, {100, 150}, {150, 0}};
For example, second core will be disabled after reaching 208MHz frequency and amount of tasks must be less than 50;
third core will be enabled after reaching 1795MHz frequency by second core and amount of tasks more than 100.
cpu_up_rate: amount of governor iterations cpu should stay at defined frequency for enabling next core.
cpu_down_rate: amount of governor iterations cpu should stay at defined frequency for disabling last active core.
down_differential: defines load in % which must be less than up_threshold to go to lower frequency.
hotplug_lock: lock amount of active cores.
min_cpu_lock: limits min value of enabled cores.
max_cpu_lock: limits max value of enabled cores.
up_nr_cpus: defines how many cores to enable at a time.
AbyssplugV2
Based on Conservative, has hotplug support. Pluses: pretty simple, hence doesn't load CPU by himself. Frequency increases sequentally, after reaching max frequency - enables next core. And vice versa. Minuses: often enables / disables cores (what in itself is energy intensive).
Distinctive parameters:
up_threshold_hotplug: load threshold in % above which will be enabled next core.
down_threshold_hotplug: load threshold in % below which will be disabled last active core.
boost: load threshold above which frequency will be increased through step (for exaample., from 208000 immediately on 624000)
Optdemand
Governor by Hisilicon, based on Ondemand. Backported from Honor 4X/4C. Distinctive feature is each frequency has its own thresholds to go to higher or lower frequency.
Distinctive parameters:
go_hispeed_load, hispeed_freq: after exceeding go_hispeed_load threshold, CPU goes immediately to hispeed_freq frequency.
up_thresholds, down_thresholds: above and below load thresholds for each frequency. For clarity:
Code:
static unsigned int operating_points[7][3] = {
/* kHz up_threshold down_threshold */
{208000, 60, 0},
{416000, 60, 30},
{624000, 70, 40},
{798000, 80, 50},
{1196000, 85, 50},
{1596000, 90, 60},
{1795000, 95, 70},
{1996000, 100, 80},
};
For example, for frequency 624MHz, if load will go below 30%, will be calculated new lower frequency according to new load value; if load will go above 70% - frequency will be increased.
boost: frequency will be increased to hispeed_freq
bostpulse_duration: duration of boost in microseconds.
Interactive
Google's gold standard governor. Updated to 3.4 kernel branch
Impulse
Based on Interactive governor. Good responsiveness.
USB Fast Charge
Increases charge current when connected to USB. It has sense only when connected to USB 3.0
Can be enabled by writing "1" into /sys/kernel/fast_charge/force_fast_charge file or by third party applications.
Disabled by default
Intelli-Plug
Hotplug driver for governors not supporting hotplug.
Activated and deactivated automatically depending on chosen governor.
Parameters are in /sys/module/intelli_plug/parameters
nr_possible_cores: max cores affected by driver.
nr_run_profile_sel: has several profiles :
0: balance default
1: performance
2: conservative
3: eco
4: eco extreme
screen_off_max: max frequency at screen off.
touch_boost_active: enables additional core at screen touch disabled by default
CPU undervolting
Undervolting values can be set for each frequency individually. Regulator has step 8mV starting from 700mV. I've got such stable values:
{
"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"
}
But you should start from higher values. I've made a test: CPU locked at frequency 1795MHz, RAR creates archive with 4 threads in 10 minutes. Average CPU temperature during this time was 56.124 degrees, with undervolting average temperature became 51.119 degrees. I.e. average temperature became lower for 5 degrees which means less power consumption.
Comparative graph:
GPU undervolting
Since I couldn't find any common used sysfs interface and applications supporting it, you can make it using script (see init.d spoiler).
My stable values are:
Code:
160: 860 -> 700
266: 860 -> 732
355: 876 -> 764
533: 956 -> 860
700: 1052 -> 924
But most probable, you will have troubles with such values, try to find suitable for your own.
3DMark Ice Storm Extreme showed average temperature decrease from 61.587 to 55.502 degrees.
Comparative grapth:
DoubleTap2Wake
Screen on by double tap on it. Has two parameters in /sys/android_touch
doubletap2wake: enables dt2w. Possible values are:
0: disabled default
1: active at all screen
2: active at top half
3: active at bottom half
4: active at navbar
dt2w_duration: Since I couldn't implement waking up device from deep sleep by irq from touch panel, so kernel doesn't go to deep sleep when dt2w is active, I added parameter defining how long dt2w stays active after screen off. After this duration dt2w becomes inactive and kernel can go into deep sleep.
Sweep2Sleep
Swipe on navbar for screen off. Can be enabled by writing "1" into /sys/android_touch/sweep2sleep file. Disabled by default.
s2s_length: swipe length in dots. By default, equal to 25% of screen width.
init.d
For executing scripts at startup, put them in /system/etc/init.d folder and set permissions to 0755
Several scripts examples (doubletap2wake, sweep2sleep, fast_charge, gpu_undervolting): View attachment scripts.rar
Scores
For correct governors switching I recommend to use Kernel Adiutor
It also lets to manage IO schedulers, TCP congestion, fast charge, CPU undervolting.
Requirements:
Unlocked bootloader
TWRP
Installation:
Just install zip-archive from TWRP
Download:
View attachment K-Tuned_kernel-4.4.2.zip
View attachment K-Tuned_kernel-5.1.1.zip
Source: Github
Updates:
31.10.2016
CVE-2016-5195 "Dirty COW" fixed.
Now CPU voltage values take effect right after frequency changes.
30.07.2016
Adjusted voltages for overclocked frequencies due to cases of appearing stability issues on some devices.
15.05.2016
Removed GPU undervolting applying at booting due to some users had stability issues. Now for GPU undervolting use init.d script individually.
Adjusted governor thresholds.
Reduced min online CPUs from 3 to 2 when screen is on for stock pwrctrl_hotplug governor.
Regards,
Kostyan_nsk

Battery is better from stock kernel??
Version lollipop compatible?

roxkiller said:
Battery is better from stock kernel??
Click to expand...
Click to collapse
for me it is the same if you set dt2w to 3 minutes
roxkiller said:
Version lollipop compatible?
Click to expand...
Click to collapse
just download K-Tuned_kernel-5.1.1.zip
if someone want to set dt2w and s2s without init.d can use this apk made by Printusrzero http://forum.xda-developers.com/asc...ap-to-wake-t3036327/post62542196#post62542196

Thank you so much! I've been waiting for ages for a kernel which isn't only for emui 2.3

I'd installed kernel 5.1.1 ktuned on my P7 B852 and it's continuously restarts. Anyone had a kernel stock for TWRP?

What is your preferred setting?
Mine:
GOVERNOR: Impulse
CPU : maximum frequency 1596mhx
I/O : fiops with 128kb readahead
INTELLIPLUG :disabled
I discovered that with Intelliplug enabled, my phone has some glitches.....
With the settings above i get 50-60% battery when i go home, 8-10 pm
What are your settings ?

leleallof said:
I'd installed kernel 5.1.1 ktuned on my P7 B852 and it's continuously restarts. Anyone had a kernel stock for TWRP?
Click to expand...
Click to collapse
Someone else tried it on P7?

Installed with cwm on B861. Working, but I see no difference.

@Kostyan_nsk kernel comes overclocked, when I try to select the default clock and start the cell with the standard clock is not, always coming back to overclock, so I went back to stock kernel

@roxkiller, just set "Apply on boot" in Kernel Adiutor after limiting max. cpu frequency and enable Kernel Adiutor in Startup Manager, so KA will aplly your settings after reboot.
And btw, if you didn't notice, cpu voltage at 1996MHz is the same as at 1795MHz, therefore I doubt that power consumption will noticably increase relatively to 1795Mhz frequency...

I have set the cpu undervolting according to your recommandation. Today , i received a message on whattsap , when i picked up the phone to read it, the phone was already rebooting. It enter the system but saying no root available !!!
Rebooted the phone again, all ok.

kye04 said:
I have set the cpu undervolting according to your recommandation.
Click to expand...
Click to collapse
It is not a recommendation, it's just my stable values as "play around" point.

@Kostyan_nsk it would be possible to compile a version without overclock ? I and perhaps most people do not like under / overclock the device, just heating up ... or pack the kernel to the option selected remain in next boot?

Kostyan what are you settings?

Updated version and details in first post.

Kostyan_nsk said:
Updated version and details in first post.
Click to expand...
Click to collapse
Thank you for the update. Has the screen glitches bug found in the P7 been resolved in this release?

jordi-chant said:
Thank you for the update. Has the screen glitches bug found in the P7 been resolved in this release?
Click to expand...
Click to collapse
+1
I really want to try it on my p7

As my memory serves me right, this issue was solved a few months ago. But you better have to ask P7 owners about it.

I thought the problem was solved for 720p but with 1080p there were still glitches?

720p never had glitches at all.

Pure Nexus/Elementalx : CPU Throttling (Low Battery)

I am running the latest version of Pure Nexus, with the latesst version of the Elementalx Kernel. I have also installed the EX Kernel Manager. This is my first attempt at a custom kernel and it is working very well.
The only 'issue' I am having or the last hurtle I am trying to get over is the CPU throttling at low battery power. I haven't done extensive testing but in the small amount of testing I have done it seems that when the phone gets around 40%, the Max CPU speed reported in the EX Kernel Manager drops to 1958MHz, with all the cores still enabled. It will remain that way until I charge up the phone above approx 40%, and at that point it will go back to 28800MHz (max value).
I have tried this https://forum.xda-developers.com/nexus-6/development/mod-disable-throttling-battery-low-t3440814 but it doesn't seem to work for me.
Is there a way to achieve this through Elementalx itself. I believe if I change the CPU Gov. to Performance the CPU returns to its maximum value of 28800 MHz even under 40% but using the Elementalx Gov. yields such a good mix of performance and battery life I would rather keep it.
Any thoughts or suggestions welcome.
Thanks.

Just looking at it again...... I'm hitting a max CPU frequency of 1985 MHz earlier than expected. It has happened at 50% battery usage. I can also confirm that changing the Gov. to Performance will up the CPU to the expected, max, value of 2880MHz.

I have discovered a couple things..... First, throttling, from the posts I have read means ' Throttling is turning cores off at lower percentages and keeping frequencies down, not at regular.' So the issue that I am experiencing is not throttling entirely as I have all 4 cores working throughout the battery range. What I do have happening and want to resolve is the Max CPU value, in Ex Kernel Manager changing from 28800 MHz, which is the maximum CPU frequency I have set, to 1958 MHz when the device battery drops below approximately 45%. Second... Changing the CPU Gov., while the battery is under 40% (1958MHz), will increase the CPU frequency back to 28800MHz until the phone drops another battery percentage, which will trigger the underclock (1958Mhz).

EXKM - Tools- User Settings Navigate to file sys/devices/qcom,bcl.39/mode and set "disabled".
And, ofc, edit threshold (99) in thermal conf file.

nemanja066 said:
EXKM - Tools- User Settings Navigate to file sys/devices/qcom,bcl.39/mode and set "disabled".
And, ofc, edit threshold (99) in thermal conf file.
Click to expand...
Click to collapse
Phone was at 43% and running at an underclocked speed of 1958 MHz. Made the changes in EXKM to the Mode file and enabled the 'Apply on Reboot'. Rebooted the phone. Once booted took a look at EXKM and the CPU speed was still underclocked at 1958 MHz. Check the Temp and it was at 45. Checked EXKM and the CPU temp threshold is set for 60. Didn't change the ofc value. I don't want to disable the thermal as I don't want to damage the hardware accidentally. I also couldn't find the value. It isn't in the Mode file. Where could I find that? Is the ofc file required as well to allow this method to work?
I will continue to tinker.
Thanks for the reply and your help.

ofc= of course. [emoji12]
For me, work ok, only edited thermal conf file (cpufreq, hotplug, gpu threshold 100 threshold clear 99). Please wait some time to.phone cooling down (sleep phone 10-15 minutes) and open EX Manager and see again. Sometimes does not change max freq value at the begining. At least, i had this situation.
Sent from my Nexus 6 using Tapatalk

nemanja066 said:
ofc= of course. [emoji12]
Click to expand...
Click to collapse
Lol! Oops.....
For me, work ok, only edited thermal conf file (cpufreq, hotplug, gpu threshold 100 threshold clear 99). Please wait some time to.phone cooling down (sleep phone 10-15 minutes) and open EX Manager and see again. Sometimes does not change max freq value at the begining. At least, i had this situation.
Click to expand...
Click to collapse
Thanks for the reply. I'm getting closer. I am able to run at 28800 Mhz until 20% battery life and then it underclocks to 1958 MHz on all cores. This is definitely a step forward. Below are the three sections you referred to, CPUFreq, HotPlug, and GPU. This is the modified file. My understanding of what this configuration accomplishes is that at 5% battery power the CPU will throttle back (underclock) to conserve battery power. Unfortunately this isn't happening.... yet.
Any other ideas on why this isn't working as expected? Is there another part of the file that needs to be changed?
Also is there a resource that explains what each line in these files do? I couldn't locate one.
Thanks!
:good:
sampling 5000
[BAT-SOC-CPUFREQ]
algo_type monitor
sensor soc
sampling 5000
thresholds 95
thresholds_clr 94
actions cpu
action_info 2649000
[BAT-SOC-HOTPLUG]
algo_type monitor
sensor soc
sampling 5000
thresholds 90 92
thresholds_clr 89 91
actions hotplug_3 hotplug_2
action_info 1 1
[BAT-SOC-GPU]
algo_type monitor
sensor soc
sampling 5000
thresholds 88 90 95
thresholds_clr 89 89 94
actions gpu gpu gpu
action_info 600000000 389000000 300000000

@monteie2016
I find your shamu thermal conf file a bit strange. I have a pure nexus and elementalx and it's not like that. All you need to edit in this file (with text editor) is set the thresholds to 100 a thresholds_clr at 99.
Thresholds is the battery percentage at which the throttling occurs (at 0% (100-thresholds))
Thresholds_clr is the battery percentage at which the throttling clear (at 1% (100-threshold_clr)).
In practice, this will never happen because in that time your device is already dead.
I will upload a screenhoot of EXKM dashboard to see max freq in my case when battery was bellow 20%. It's stay on 2.6 Ghz.

Can you also post the CPU, GPU, and hotplug values. I would like to see how yours is configured.
Thanks
:good:

monteie2016 said:
Can you also post the CPU, GPU, and hotplug values. I would like to see how yours is configured.
Thanks
:good:
Click to expand...
Click to collapse
Also, I have an older version of the elementalX 4.23 as you can see on screenshot (with july security patches) , because the PureNexus rom does not have august and september kernel patches.
Here is SS thermal conf:
[emoji106] [emoji482]
{
"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"
}
Sent from my Nexus 6 using Tapatalk

Couple of things...... Above you are showing me a status from EXKM at 62% battery. I don't have and underclock issue anywhere between 100% and 20%. When the battery life drops below 20% is where I get the issue (Underclocks to 1958Mhz from 2880Mhz).
Here is what my file looks like
sampling 5000
[BAT-SOC-CPUFREQ]
algo_type monitor
sensor soc
sampling 5000
thresholds 100
thresholds_clr 99
actions cpu
action_info 2649000
[BAT-SOC-HOTPLUG]
algo_type monitor
sensor soc
sampling 5000
thresholds 100 100
thresholds_clr 99 99
actions hotplug_3 hotplug_2
action_info 1 1
[BAT-SOC-GPU]
algo_type monitor
sensor soc
sampling 5000
thresholds 100 100 100
thresholds_clr 99 99 99
actions gpu gpu gpu
action_info 600000000 389000000 300000000
I should also mention that I have disabled BCL, /sys/devicds/qcom,bcl.39/mode and changed the value to disabled.
I have attached two images. One is the battery at less than 20% and what I am seeing for CPspeed (underclock) and the other is above 20%.

Off topic thoughts @monteie2016
What you had asked for was posted in the previous post. The additional information was provided additionally. But you jumped on the extra info. And not one time in this thread have you "thanked" (thumbs up) the only person who had been trying to help you.

I did thank nemanja066 for his post on 20th September 2017, 04:51 PM (thanks button in thread) and my reply on September 23rd had a thanks and a thumbs up.
Also is there a resource that explains what each line in these files do? I couldn't locate one.
Thanks!
:good:
Click to expand...
Click to collapse

[emoji106] No throttling yet.
I will post SS for battery bellow 15%, too.
Sent from my Nexus 6 using Tapatalk

@monteie2016
Looks like a bug with the aroma installer. Try again with flashing kernel in recovery and then in aroma set max freq cpu to 3033MHz. After flashing, reduce the frequency to the desired one in EXKM. After that, it might be fine, and the freq can be reduced only due to the increase in temperature, which is quite OK. When the phone cools down, freq will go back to the old value. If all this fails, then I do not know what to do next.

nemanja066 said:
@monteie2016
Looks like a bug with the aroma installer. Try again with flashing kernel in recovery and then in aroma set max freq cpu to 3033MHz. After flashing, reduce the frequency to the desired one in EXKM. After that, it might be fine, and the freq can be reduced only due to the increase in temperature, which is quite OK. When the phone cools down, freq will go back to the old value. If all this fails, then I do not know what to do next.
Click to expand...
Click to collapse
Thanks for the information. I will take a look at it later. Got busy doing other things
:good:

nemanja066 said:
EXKM - Tools- User Settings Navigate to file sys/devices/qcom,bcl.39/mode and set "disabled".
And, ofc, edit threshold (99) in thermal conf file.
Click to expand...
Click to collapse
Hello, just curious if you can specify the file location of the thermal config file? Thank you for your help.

ozzmanj1 said:
Hello, just curious if you can specify the file location of the thermal config file? Thank you for your help.
Click to expand...
Click to collapse
/system/etc/thermal-engine-shamu.conf
Sent from my Nexus 6 using Tapatalk