Hi guys, I'll make this short and sweet. A few years ago, I stumbled on this little guide for the Interactive governor, which made a lot of changes in CPU scaling and has spread to many devices.
To make a long story short, OEMs usually ramp up your CPU to more than what is needed to ensure smooth performance. This guide, changes that by ramping up your CPU to the minimum amount needed to get the same effect. The result? Lower frequencies used equals more power saved without impacting performance.
It's like a car race. If you take on a tight corner at high speed, you go in fast but you still need to slow down or risk crashing. But if you decelerate to just the right speed, you consume less energy while ensuring not much of your acceleration is sacrificed in the process.
This will be the best time to release this thread because we now have our voltage values from the kernel source, which provides the real change in these tweaks.
Calculations and stuff
Soooo what now?
I'll be taking their Hawktail profile, as it seems to work the best. Any newer profile from that thread is built specifically for the Nexus 5x.
You should use a kernel manager app to implement these values, I recommend Kernel Adiutor Mod if you want free, or you can pay for EXKM made by one of the more senior developers in XDA.
Hopefully it helps you as it seems to help me. Discussion is more than welcome here, as these are just rough calculations that isn't fine tuned yet for our CPU.
Additionally, open a terminal emulator app and type these:
This will prevent the Qualcomm binaries from taking over the CPU scaling and leave it up to the governor instead.
To make a long story short, OEMs usually ramp up your CPU to more than what is needed to ensure smooth performance. This guide, changes that by ramping up your CPU to the minimum amount needed to get the same effect. The result? Lower frequencies used equals more power saved without impacting performance.
It's like a car race. If you take on a tight corner at high speed, you go in fast but you still need to slow down or risk crashing. But if you decelerate to just the right speed, you consume less energy while ensuring not much of your acceleration is sacrificed in the process.
This will be the best time to release this thread because we now have our voltage values from the kernel source, which provides the real change in these tweaks.
Calculations and stuff
Soooo what now?
I'll be taking their Hawktail profile, as it seems to work the best. Any newer profile from that thread is built specifically for the Nexus 5x.
You should use a kernel manager app to implement these values, I recommend Kernel Adiutor Mod if you want free, or you can pay for EXKM made by one of the more senior developers in XDA.
Code:
go_hispeed_load: 95
above_hispeed_delay: 0
timer_rate: 60000
hispeed_freq: 652800
timer_slack: 480000
[B]target_loads: [/B] 80 652800:57 1036800:67 1401600:22 1689600:84 1804800:83 1958400:87
min_sample_time: 0
ignore_hispeed_on_notif: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0Hopefully it helps you as it seems to help me. Discussion is more than welcome here, as these are just rough calculations that isn't fine tuned yet for our CPU.
Additionally, open a terminal emulator app and type these:
Code:
su
stop perfdThis will prevent the Qualcomm binaries from taking over the CPU scaling and leave it up to the governor instead.
Last edited:
