Related
[O3D] Overclock/Downclock guide/tutorial?
- can someone explane safe way to downclock(or overclock) GPU/CPU for O3D, I want to downclock to safe some battery life.
Thanks
SetCPU (search xda-developers for free download or market for paid updatable version) works for me, detected cpu speeds and allowed me to change them from 300 to 1008 Mhz, also there are a few options how the processor freq change when needed. For now you can only downclock until a new kernel arrives (not 100% sure what kernel is and if it really enables overclocking - just saying). I didn't try anything with setcpu but if you do please post your feedback
i have installed but i cant set the clock, with setvsel for defy i can define 3 speed for the principal status, in set cpu i see only the maximum rate (1008).
help me tks
Have you rooted your device, before you run setcpu?
what about downclocking, is it really giving extra life for battery?
I use Antutu CPU Master to downclock, it has a cool widget.
wan0eve said:
I use Antutu CPU Master to downclock, it has a cool widget.
Click to expand...
Click to collapse
to what numbers you downclocking and how is battery life after downclocking?
Read new informations in installation guide
Click to expand...
Click to collapse
Click to expand...
Click to collapse
IF YOU HAVE REBOOTS WHEN YOU ARE USING THE PHONE, IT'S BECAUSE YOU SET A UV TOO AGGRESSIVE, SO, YOUR CPU CAN'T BE STABLE. CHOSE A LOWER UNDERVOLTAGE
IF YOU WANT TO KNOW HOW VOLTAGE CAN REACH YOUR CPU, START STABILITY TEST (DOWNLODABLE FROM MARKET) AND USE IT FOR ABOUT 10 MINUTES, IF PHONE REBOOTS IN THAT TIME, THAT VOLTAGE IS TOO LESS FOR A STABLE CHIP
NOT ALL CHIP ARE THE SAME, IF YOU HAVE A LUCKY CHIP, YOU CAN REACH A LOWER VOLTAGE (AS MINE)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ok Guyz, since show creates the badass governor, i'd want to use it for a better one multicore configurtion
What's the advantages of multicore sistem?
Symply, more parallelization means more performance per second, as i can say, 2 core can compile at last the double quantity of threads than 1, so, 1 core at double frequency can't compile the same number of thread, but it do it faster..
ex..
if you have 2 thread (impossibile), 1 audo and 1 video, a single core @ 2ghz compile firstly the audio, than the video.. the dualcore architecture can compile on core0 the audio and on core1 the video!! this is the powerfully of multicore system.
Ok, since i say it, i create a MOD witch TRY to use this logically.. this MOD uses the limitate frequency of the badass governor, that's why, with ondemand, all of 2 core goes at maxFreq too fast, now, with this badass, the system will not grow up the first limitate frequency until the single core uses more than that frequency.. so.. we can limitate the "ondemand" issue in 3 freq phases..
thus, the actual MOD configuration is it:
Click to expand...
Click to collapse
SCREEN ON:
- dualcore with all cores TURNED ON (hope you understand now )
- governor badass for all of 2 cores
- min freq at 384mhz for all of 2 cores
- max freq at 1.566ghz for all of 2 cores
- first phase freq at 810mhz for bla bla bla
- second phase freq at 1.188ghz for bla bla bla
- third phase freq at 1.566ghz (is the maxfreq)
SCREEN OFF:
- only core0 is TURNED ON
- governor conservative
- minfreq 192mhz
- maxfreq 540mhz
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Badass governor has the same configuration as last show's ondemand governor
So, now, with this MOD we have a pure functional dualcore with the advantages of multicore system, with limitate frequency. The stock situation is 384-810mhz, if the single core (is the same, qualcomm uses asyncronic frequency) needs more than 810mhz, it increases the max freq to 1.188ghz (the sensation original frequency), if 1.188 isn't sufficently, it increeses at 1.566
remember, qualcomm has asyncronic frequency, so, one core can be run at 1.56ghz, the other at minimum mhz..
Click to expand...
Click to collapse
Click to expand...
Click to collapse
How to use it?
Click to expand...
Click to collapse
INSTALLATION:
-) flash a kernel witch has badass governor (i advise bricked 1.1) with NO GPU OC and what governor you want, the same for the frequency, mod autochanges those, chose what scheduler you prefer.
1) Flash MOD zip file by recovery
2) Select what MOD YOU want
3) Reboot.
#) You have to reinstall at every Rom Upgrade
# If you want only the UV, select Remove in mod choseing (it's the same as no installing it); you can use the UV mod with all kernels, and all governors
# If you come from V2.0 to 3.0, go to recovery, wipe, format system partition, after that, reinstall rom, reinstall bricked kernel (if it hasn't), reinstall other mods (like battery %), install my mod, reboot.. You will not loose your data
# ONDEMAND VERSION IS NOT FOR GOOD BATTERY CONSUPTION, IF YOU HAVE HUGE BATTERYDRAIN (IT'S WHAT YOU'LL HAVE) INSTALL THE BADASS - BOOST+BOOST VERSION.
DISINSTALLATION:
1) Boot in recovery, flash the Mod
2) Select Remove
3) Reboot
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Code:
bricked 1.2 -above
V 11.9
> Fixed Screenoff chose
> Changed DEFAULT first phase for better reactive with less power usage
> Other minor changes
###
Added Version for AOSP kernel (NoSense)
V 11.8
> Changed some settings
V 11.7
> Changed some settings for a better fluidity
V 11.6
> Added Remove chose
> Fixed an installation issue of the Aroma
V 11.5
> Added possibility to know if MOD is working, you have to give a cycle on/off of the screen, after that, if it works, you will find a new file in home of sdcard!
V 11
> Changed configuration for less battery drain
V 10.5
> Tweaked badass experience for better battery life (only with bricked kernel 1.4)
V 10.1
> Tweaked screen off conservative
V 10.0
>> BIG RELEASE
> Added possibility to chose frequency
> Added possibility to chose screen off governor
V 1.01
> Fixed freq values in Aroma installer
V 1.0
> Initial Release
HaVe FuN!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FAQ in second post
VIDEO
Click to expand...
Click to collapse
FAQ
Click to expand...
Click to collapse
Witch version could you chose?
The versions of the mod are two:
The 3.7 is the older, it's for the bricked 1.1 version AND for other kernels (don't know if all rom will boot up with my mod, some has issues)
The version 10 and above are for bricked 1.36 and 1.40
What setting could you use?
You can intall what you want, i create those (expecially the 10 versions) witch has the possibilities to be changed as users experience.
I advice to use default settings if you don't know how change, but, you should try to, it will not brick your phone, in fact, you could find a new setting could it be better for your use.
So, try try try
One EX:
If you want a faster phone, grow up the minfreq to 300-400mhz, grow up the first phase at 1.2ghz, put the second to 1.2 or more, and change the maxfreq as you would, OC too.
If you want a better battery experience, decrese minfreq, the first and second phase, decrese the maxfreq too, maybe, with this settings: 192 - 648 - 1020 - 1180 mhz
If you want the lowest battery experience, try with this setting: 192 - 648 - 1020 - 1020 mhz
Be careful, you could have some lags if you chose the lower setting, but, for ex, if you don't play, you can chose a setting as like, 192 - 810 - 1020 - 1180 mhz
So, you have to install, select one setting with you think it's ok, try, if you have lags in some situation, grow up some setting, an re-try til you find your best settages. I don't have your use, so, i don't know if you could have a good esperience with my setting.
How to see if mod is working?
If you have the version 10 or above, you will find a new file in SD card, it calls IBA21ModWorking. if you don't find that, turn on the screen, wait 5 seconds, turn on, refresh the explorer app, and try to see if there is.
If you have the 3.7v you have to download and install system tuner, and see if all cores are turned on.
Why my phone doesen't boot after apply the mod?
Not al roms has the same quality, some doesen't have some little features; my mod uses a whyle cicle witch chages settings from screen-on use to screen-off (standby). If phone doesen't boot up, rom doesen't have the possibility to use the cycles in the script, so, script is unusefull.
Do you need to delete or wipe the rom at every upgrade?
ABSOLUTELY NO, mod auto removes the old script and changes that with the newer one, so, YOU DON'T NEED TO DO ANYTHING, ONLY FLASH THE UPGRADE OR THE NEW SETTINGS WITCH YOU ARE CHANING!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
enjoy my work and, press a lot of thanks buttons! :d
Very very good, the system is smooth and stable, I've only a lag after reboot, and sometimes when start synchronization...
Good work!
Hi nice script. Must the CPU values be truly stock ? Could it take something like 384-1566?
Sent from my Sensation running HyperNonsense v2.3
remus82 said:
Hi nice script. Must the CPU values be truly stock ? Could it take something like 384-1566?
Sent from my Sensation running HyperNonsense v2.3
Click to expand...
Click to collapse
Yep, i could do it.. but.. i tryed it, and.. it only increase the power consuption
framir said:
Very very good, the system is smooth and stable, I've only a lag after reboot, and sometimes when start synchronization...
Good work!
Click to expand...
Click to collapse
Lags depends on badass governor.. it's "normally".. but.. 1 lag per day is not bad, remember, with my configuration you have a better badass configuration with lower power consuption than faux kernel..
Looks awesome
Noticed bug appears after every reboot?
How to change second phase to 810-1134 and delete third phase? Or I don't need it
And soo.. It's fully better than original badass?
http://i.imgur.com/gavOn.png
Standby power consuption with data active!
D-SHEL said:
Looks awesome
Noticed bug appears after every reboot?
How to change second phase to 810-1134 and delete third phase? Or I don't need it
And soo.. It's fully better than original badass?
Click to expand...
Click to collapse
You don't need to delete it since system uses third phase (1.2 to 1.5) only in heavy games and web browsing+flash player.. in web usage cores goes to 1.2 max
Btw.. third phase is the maxfreq governor.. i can change it by script if you want to try
Take.. flash it as you would.. you can come back with stock script
For who doesen't understand.. the phase limis is a real limit.. since system needs more performance, system use the lower limit.. as i can see in my use:
For home scrolling 1 core goes to 1.2ghz, the other is at 192mhz (low power consuption)
For notice bar scrolling 1 or 2 cores goes to 810mhz, it depends on other app.. 1 core at 810mhz can calculate the notify bar
For chrome beta browsing.. in web rendering ( page loading) all of 2 cores goes to 1.2ghz, after that, core goes to 192-810 since heavy scrolls, heavy zoom, or animations in the web page (in google page cores goes to 192mhz )
For browser + flash player, 2 cores are uset at 100% at 1.56ghz since it comes down.. after that.. system uses 192-810.. sometimes only one core goes to 192-1.2
In games core i dont know why i dont play games
So.. the third pase is only a turbo boost, it's used only when system needs more and more power.. the phase is a real limit..
For example.. you have a stock 192-810.. when system needs more than 100% (810mhz) badass grow up the frequency to second phase.. it's the same for third phase.. so.. if system doesen't need more power, badass doesen't grow up the cpu frequency..
In my test i see.. ondemand tweaked + core1 off at my usage has a cpu temperature at about 55degrees C.. with badass, 47
So.. lower tenperature.. lower power consuption!
Sure.. ondemand has a faster one response.. since it grow up frequency every time, for low needs too..
you couldn't have performance plus heavy power..
The "busg" is too.. until system needs more than phase freq, it doesent grow up, so, when there's the necessity of more freq, upgrading is slower than ondemand, and it creates a little lag..
On boot, don't know why but.. only one core is turned on.. it's a system fault of reading script.. if you turn off screen, and turn on, it returns at normally (so.. needs an off-on cicle)
iba21 said:
You don't need to delete it since system uses third phase (1.2 to 1.5) only in heavy games and web browsing+flash player.. in web usage cores goes to 1.2 max
Btw.. third phase is the maxfreq governor.. i can change it by script if you want to try
Click to expand...
Click to collapse
Thanks! Maybe really don't need this
Noticed bug appears after every reboot?
"69force192-1188.zip"
As I can see, this is version without third phase?
D-SHEL said:
Thanks! Maybe really don't need this
Noticed bug appears after every reboot?
"69force192-1188.zip"
As I can see, this is version without third phase?
Click to expand...
Click to collapse
Yep that has only 2 phase.. 192-810 and 810-1.2
I edited last message with informations about your questions
Shouldn't this be in the Development section?
nope.. it's not a developement app.. those are some settages..
if you load the script, and delete it, the settages has been changed..
when you turn on display
screen ON:
- dualcore able
- governor badass for all of 2 cores
- min freq at 192mhz for all of 2 cores
- max freq at 1.566ghz for all of 2 cores
- first phase freq at 810mhz for bla bla bla
- second phase freq at 1.188ghz for bla bla bla
- third phase freq at 1.566ghz (is the maxfreq)
when you turn off
screen OFF:
- only core0 able
- governor conservative
- minfreq 192mhz
- maxfreq 540mhz
it changes that values at every turn on-off of the display.. only 1 time.. so.. if you load the script, and delete it, at display turning off, the script doesen't change the values, and, you will not have the "screen off" setting, so, you'll have the stock badass, so, more power consuption
i repeat, my script is only a numerical setting, it's not a kernel, it changes only the superficially values of the kernel, after that, is the kernel governor the real fault of frequency changing
sure.. with my script you have that 2 configuration.. and.. if you see.. conservative in standby means low power consuption (from 20 to 70ma in standby, depends on the system performance needed)
Is step 6 necessary? I don't have that function in root explorer
Sent from my Sensation running HyperNonsense v2.3
remus82 said:
Is step 6 necessary? I don't have that function in root explorer
Sent from my Sensation running HyperNonsense v2.3
Click to expand...
Click to collapse
it's not obbligatory.. but.. you have it.. long press.. OPEN WITH -> LINUX script (it's the third link from top)
http://i.imgur.com/BbeS0.png
Or you can reboot 2 times.. in first run script changes the name of the file witch turn on the second core.. the mpdecision.. so.. or you do a first manually run.. or you do a first reboot.. script changes the name, but the mpdecision script is already loaded.. second reboot use only my script
Thanks! Will report back after a day of use!
Sent from my Sensation running HyperNonsense v2.3
Edit: solved.
Sent from my Sensation running HyperNonsense v2.3
Iba I notice that media scanner takes extremely long to complete after applying the script. Is it possible to use badass or on demand as screen off governor?
Sent from my Sensation running HyperNonsense v2.3
Sure.. but you loose the advantages of low power consuption..
What is media scanner? How many mhz does it needs?
The Introduction
I'm about to tell you how to get buttery smooth, lag free performance with insanely good battery life, using an old school governor featured in practically every kernel... This tweak is applicable to every phone with any ROM or kernel--stock or custom--that provides the Interactive Governor.
Yeah, yeah... everyone promises good battery with great performance, but who actually delivers? Maybe it isn't as smooth as you want, or maybe it requires something your kernel or ROM don't support. Or maybe the battery life promises just aren't what you expected. There's always some awful compromise. Not here!
This isn't a guide to get 36 hour battery life... provided you never use your phone. That's deep sleep optimization, which is lovely and all, but what good is the phone if you can never use it?! And with the new Marshmallow Doze feature, this strategy is becoming a think of the past. What I'm talking about is 7-14 hour screen on, actual hands-on usage times! Without compromising anything, you can get 7-8 hour screen on usage with regular, no-compromise usage habits: daytime visible screen brightness, both radios on, sync on, network location on, all the regular usage features, the whole kit and kaboodle... all smooth as a baby's butt and snappy as a Slim Jim! (Up to 14+ hours if you can stand minimum brightness and WiFi-only with a custom ROM and other stuff turned off! And this is with stock voltages and full frequency range--you'll likely get even more if you choose to optimize those as well!)
However, it should be noted that this does not apply to gaming, heavy camera use, etc. Anything that is an automatic battery killer in and of itself. There's nothing that can be done about anything that forces the phone to utilize its maximum resources all the time. But you should know that by now. Further, this guide is about optimizing the CPU as much as possible. It does not cover things like eliminating wakelocks so your phone sleeps well, removing unnecessary and battery draining stock apps, keeping your screen brightness down*, and all that stuff that's been covered in other posts ad infinitum. Those optimizations are up to you.
*At least on the Mi4i, you shouldn't be turning your screen brightness above about 50%. It should be more than viewable in sunlight at that brightness, and keep in mind that the brightness power requirements increase exponentially, so a 100% bright LCD screen will use about 3.5-4.5x more power than a 60% bright screen. I don't see that fact brought up often, so I thought I'd mention it here.
After a bit of tweaking and experimenting, I developed some settings that provide absolutely incredible battery life, buttery smooth performance, and a lag free experience. And you don't need a fancy governor, or a custom kernel, custom clock rates, or even a Mi4i. This will work on any ROOTed phone with the Interactive governor!
The Nitty Gritty
Before I lay out all the settings so you can blindly enter them into your governor control, I should to explain some of the principals I employed to get the results I did. The primary thing to understand before I do is: little might you know, the settings in the Interactive governor can be tweaked on a clock range basis. That is to say, you can finely control how the governor responds at a variety of clock rates, thus better dictating how it should operate under various loads. This is integral to the configuration, because it means the difference between jumping from the slowest speed to the highest speed under load and sustaining lower clock speeds for tasks that don't really require higher clock speeds.
By default, the Interactive governor will jump from lowest speed to a "nominal" speed under load, and then scale up from that speed as load is sustained. That is lovely, but still too twitchy to provide serious efficiency and power savings. It spends most of its time at 2 or 3 clock speeds and barely hits other clock speeds that are ideal for other tasks or usage patterns.
Instead, what we want to do is configure it to handle different types of loads in different ways. A load suited for scrolling through a webpage is not the same as a load suited for downloading/processing streaming video is not the same as a load suited for snappy loading of an app is not the same as a load suited for high performance gaming. Every kind of load has different tolerances at which their minimal speed is indistinguishable from their maximal speed.
Nominal Clock Rates
Nominal clock rates are the minimum CPU clock rates that perform a given task smoothly and without stuttering or lag. To find the nominal clock rate for a given task, turn on only the first CPU using the Performance governor and turn them both down incrementally until you find the minimum clock rate that works best for what you're trying to do, without introducing hiccups. (If you have a CPU or kernel that hotplugs individual cores, multiply that clock speed by your number of cores.) Keep the 2nd CPU on the Powersave governor with the lowest frequency your kernel supports. (Or turn it off completely if hotplugging allows.)
(Note: If your device supports per-core hotplugging, you might be better off using the old guide to determine your nominal clock rates. The Mi4i and all current kernels only support hotplugging entire CPUs, so your results may vary if you use any other device.)
For example, on my Mi4i, scrolling (not loading, simply scrolling) through a large webpage smoothly will occur when the second CPU clock rates are no less than 460Mhz. (This is on mine without background tasks taking any CPU. Yours may be different depending on services running, the browser you use, your ROM, kernel, etc.) Thus, the nominal clock rate for scrolling a webpage on my Mi4i is 460Mhz.
To understand what's best under a variety of tasks, we have to identify two types of load profiles: nominal clock rates and efficient clock rates.
Efficient Clock Rates
Efficient clock rates are CPU clock rates that are unique in that they are the most optimal frequency given the range of voltage requirements. If you map out the frequency jump and the voltage requirement jump between each of the available clock rates, you will find that occasionally the voltage requirement will jump significantly without the frequency jumping proportionally to the previous differentials. For example, using stock voltages, the EvoLTE's msm8960 chipset clock/voltage ratios jump significantly higher from 702Mhz to 810Mhz than the ratios from 594Mhz to 702Mhz.
This section is INCOMPLETE! If you know the voltages, please post and I can update this guide to include the Mi4i's Efficient Clock Rates.
Clock Rate Biases
Using the information provided above, figure out both your nominal clock rates for the tasks you perform most often and your efficient clock rates depending on your kernel/custom voltage settings. For me, since I cannot determine the efficient clock rates, I use the nominal clock rates listed above. For the tasks I generally perform on my phone, my nominal clock rates are as follows:
Idle - 345Mhz
Page Scrolling - 533Mhz
Video -800Mhz
App Loading - 960Mhz
High Load Processing - 1612Mhz
(Note that you must calculate the values that are optimal for your phone for best battery and performance! Each phone is different because of the ROM, kernel, background tasks, etc!)
With this done, you will want to start the fine tuning phase! Correlate the efficient clock rates with their closest nominal clock rates, similar to below:
(This section of the guide is INCOMPLETE because I do not know the clock rate voltages for the Mi4i. If you know these, please post in the comments and I will update the guide!)
Idle - ???Mhz efficient / 345Mhz nominal
Page Scrolling - ???Mhz efficient / 533Mhz nominal
Video - ???Mhz efficient / 800Mhz nominal
App Loading - ???Mhz efficient / 960Mhz nominal
High Load - ???Mhz efficient / 1651Mhz nominal
Keep these handy, as they're going to be necessary for...
The Set Up
Now that we know what are the most efficient nominal clock rates we want to focus on and what the most optimal are for what we want to do, we will start low and scale up as necessary. It's always better to begin with underperforming and tweak the settings upward until we're satisfied with the performance of our target tasks.
In its default state, the Interactive governor has a hair trigger that will raise and lower the clock rates, which means it spends too much time at unnecessary clock speeds, wasting power, and scales down too quickly, leading to stuttering performance. We will take advantage of a seldom used feature of the Interactive governor. Specifically, that with which it determines when it is okay to scale up to each higher clock rate, on a frequency by frequency basis.
We have two primary goals: respond as quickly as possible to each load request for a lag free experience and exceed the desired clock rate for a given task as little as possible. To do this, we will instruct the Interactive governor to trigger certain clock rates in different ways depending on our expected load.
I won't explain all of the settings of the Interactive governor--there are plenty of summaries all around. (Go search now if you don't know what any of the settings for Interactive governor do. I'll wait here.) However, I will explain an incredibly powerful feature of the Interactive governor that is rarely included in those summaries: multiple frequency adjustments.
The above_highspeed_delay setting, for example, defines how long the governor should wait before escalating the clock rate beyond what's set in highspeed_freq. However, you can define multiple different delays that the governor should use for any specified frequency.
For example, we want the above_highspeed_delay as low as possible to get the CPU out of the idle state as quickly as possible when a significant load is applied. However, we don't want it to jump immediately to the fastest clock rate once it's gotten out of idle, as that may be overkill for the current task. Our target trigger (which you will later adjust to suit your system and usage profile), will begin at 20000μs. That means 20,000μs (or 20ms) after our idle max load has been reached, we want to assume idle has been broken and we want to perform an actual task. (We want this value as low as possible without false positives, because it is one of a few factors that determine how snappy and lag free the CPU's response is.)
But at this point we're not ready to take on a full processing load. We may just be briefly scrolling a webpage and don't need the full power of the CPU now that we've allowed it to break out of idle. So we need it to reach a particular frequency and then hold it there again until we're sure the load is justified before we allow it to push the frequency even higher. To do that, rather than just setting
above_highspeed_delay - 20000
we will instead use the format "frequency:delay" to set
above_highspeed_delay - 20000 460000:60000 600000:20000
"Waaaait... What does that do?!"
This tells the Interactive governor to hold out 20ms after our target load when it's at our highspeed_freq (which we're actually using as our idle frequency--not a burst frequency as originally intended), but then it tells the governor to hold for 60ms after it's reached 460Mhz. Once it has exceeded 460Mhz, it then has free reign to scale up without limitation. (This will be optimized with the target_loads setting in a minute. And if you don't know what I'm talking about when I say "highspeed_freq" then you didn't go search for the basic Interactive governor settings and read about it! Go do that before you read any further, because I will not explain the basics of this governor!)
These settings are among the most important, because they limit the phone's clock rates when you are not interacting with it. If it needs to do something in the background, chances are it does not need to run full throttle! Background and idle tasks should be limited to the lowest reasonable clock rate. Generally speaking, if you're just looking at your phone (to read something, for example), you want the phone to use as little CPU power as possible. This includes checking in with Google to report your location or fetching some pull data or... whatever. Things that you don't need performance for.
So now that we know how to specify different settings for different frequency ranges, let's finish it all up with...
What About Touchboost?
Touchboost is a nifty feature in a lot of kernels (including stock on Mi4i) that jumps up the frequency so that you experience minimal lag. However, with all the above settings, touchboost is usally detrimental to the efficiency of the device!
We generally want to keep the CPU on the lowest possible frequency as much as possible, and touchboost interferes with that. Further, because we've set up the maximal and minimal efficient clock rates, as well as burst processing from the 1st CPU core, we don't need touchboost!
If your kernel allows you to shut it off, try to do so and see if the responsiveness of your device is acceptable. On the Mi4i, touchboost adds no perceptual performance gain and only hurts efficiency and battery life. If your kernel doesn't allow you to turn off touchboost, try another one, like the excellent Sensei.
Your battery life will thank you!
The Setup
In the "CPU" section, turn off "Touchboost". (This is crucial!! YOU MUST TURN OFF TOUCHBOOST OR ELSE YOU WILL NOT SEE ANY BATTERY SAVINGS!!!) Make sure the "Max CPU Frequency" is set to the maximum possible value for each CPU. Make sure the "Min CPU Frequency" is set to the minimum possible value for each CPU. Under "CPU Boost", set "input boost milliseconds" to "0". Then set the following values for each CPU under "Governor options" for each CPU respectively:
CPU #1 (aka "Big", aka "has 4 cores", aka "maxes out at 1665Mhz")
target_loads - 1 960000:80 1113600:85 1344000:90
timer_slack - 80000
hispeed_freq - 1113600
timer_rate - 20000
above_hispeed_delay - 20000 1113600:50000
go_hispeed_load - 85
min_sample_time - 50000
CPU #2 (aka "little", aka "has 4 cores", aka "maxes out at 1113Mhz")
target_loads - 1 800000:80
timer_slack - 80000
hispeed_freq - 998400
timer_rate - 40000
above_hispeed_delay - 10000
go_hispeed_load - 90
min_sample_time - 40000
The Conclusion
I have achieved unprecedented performance, smoothness, snappiness, and battery life with the default settings I outlined above. However, your mileage may vary, as every phone, ROM, kernel, installed applications, etc are different. This is a very sensitive governor profile and must be tweaked to just meet the requirements of your system and your usage patterns!
If it is not optimally tuned, performance and battery life will suffer! If you're not seeing buttery smooth, snappy performance, you have not correctly tuned it for your system!! However, if you do have superb performance (and you tweaked the values conservatively and not in large steps), then you will also get the aforementioned battery life.
I will be happy to answer any questions, or provide any guidance I can. However:
You must otherwise optimize your phone first! This will not "fix" a poorly optimized system and will, in fact, reduce performance and battery life without further optimization and proper tweaking.
I will not answer questions about "what is a governor?" There are plenty of resources available already, so search for them.
I will not answer questions about "how can I tweak [some other] governor?" This is about the Interactive governor only.
I will not respond to "nuh uh! show proof!" posts. The fact that I spent 12 hours writing this up should be proof enough that I am satisfied with the results. You can take it or leave it; makes no difference to me. The default settings should work with any fully optimized Mi4i running any kernel, so just try them on your own. If you're not absolutely satisfied (and trust me, either it'll work out-of-the-box with flying colors and you'll know it works for your system, or it'll be an awful experience which means you must tweak it), then you haven't adequately adjusted the settings to suit your system.
Lemme know what you think, and good luck!
Thanks to @soniCron for the original thread here : http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
Woah, Will try it soon. Thanks for the awesome thread and work.
The interactive governor from your Sensei kernel already had all these settings tuned.
I will come back in 24-48 hours with results.
One question that I have is: will something like Amplify (deals with wakelocks) interfere with this?
mandarin91 said:
The interactive governor from your Sensei kernel already had all these settings tuned.
I will come back in 24-48 hours with results.
One question that I have is: will something like Amplify (deals with wakelocks) interfere with this?
Click to expand...
Click to collapse
I've dealt with a few wakelocks in the kernel, Amplify won't disturb anything I guess.. Also this is just for future refs for users who are either on stock or any other kernel...
How exactly does this target load list work - why the loads are not progressive, but 85 - 90 - 80? set target to 90% load at 1.1ghz, but then we want 80% at 1.3ghz? Shouldn't the target loads only go up?
target_loads - 1 960000:85 1113600:90 1344000:80
are you sure that above_highspeed_delay for CPU#2 is correct?
danb1974 said:
How exactly does this target load list work - why the loads are not progressive, but 85 - 90 - 80? set target to 90% load at 1.1ghz, but then we want 80% at 1.3ghz? Shouldn't the target loads only go up?
target_loads - 1 960000:85 1113600:90 1344000:80
Click to expand...
Click to collapse
Exactly. And where are the lower frequencies?
The lower frequencies are left untouched. I've been testing this for some time now. Look at the screenshots.
mandarin91 said:
Exactly. And where are the lower frequencies?
The lower frequencies are left untouched. I've been testing this for some time now. Look at the screenshots.
Click to expand...
Click to collapse
bump (?)
Will we get an answer?
I've fixed the settings, target load will now go up rather than up-up-down... Also these settigs are a WIP, right now this is the optimal settings I have that will provide battery life and performance. I will update the settings each time an improvement is made.
Lower frequencies aren't doing much fr me but I'll try to include them into the formula...
haikalizz said:
Lower frequencies aren't doing much fr me but I'll try to include them into the formula...
Click to expand...
Click to collapse
I am talking about these:
Idle - 345Mhz
Page Scrolling - 533Mhz
Video -800Mhz
App Loading - 960Mhz
High Load Processing - 1612Mhz
Click to expand...
Click to collapse
If these "aren't doing much" then there will be only five frequencies: 200, 960, 1113, 1344, and 1651.
And most of the time is spent on 200 or 960. Won't the frequencies between 200 and 960 give better battery life?
How can an awesome thread like this die?
mandarin91 said:
I am talking about these:
If these "aren't doing much" then there will be only five frequencies: 200, 960, 1113, 1344, and 1651.
And most of the time is spent on 200 or 960. Won't the frequencies between 200 and 960 give better battery life?
Click to expand...
Click to collapse
no it doesnt quite work that way. not all lower frequencies will give better battery life. it also depends on the SOC in question and the nature of the SOC. I think hakalizz has mentioned previously of several optimized voltages and frequencies which we don't know for the snapdragon 615. let's use the 615 and some hypothetical values
200mhz - 650mv
400mhz - 650mv
you would have thought that 200mhz would give better battery savings but that isnt the case over here. even though the 400mhz would use more power (even though it is rated the same as 200mhz), technically you get battery savings because 400mhz gets the job done in well, twice the speed of the 200mhz. So you need to either figure out which of your frequencies are optimized in such a way that it can take advantage of the race to idle factor too.
for now i'm still on zzmoove but only to a point where i figure out how to optimize interactive for my own usage (with hotplugging etc)
just to further the point on this advance interactive tweaks - theory-wise and practicality-wise it is sound, you use the best frequencies(Bare minimum that you can stand) and you enjoy battery savings as well. the only issue I see is if you use your phoen differently from the OP. that's why haikalizz says you need to tweak and adjust it on your own
davtse said:
no it doesnt quite work that way. not all lower frequencies will give better battery life. it also depends on the SOC in question and the nature of the SOC. I think hakalizz has mentioned previously of several optimized voltages and frequencies which we don't know for the snapdragon 615. let's use the 615 and some hypothetical values
200mhz - 650mv
400mhz - 650mv
you would have thought that 200mhz would give better battery savings but that isnt the case over here. even though the 400mhz would use more power (even though it is rated the same as 200mhz), technically you get battery savings because 400mhz gets the job done in well, twice the speed of the 200mhz. So you need to either figure out which of your frequencies are optimized in such a way that it can take advantage of the race to idle factor too.
for now i'm still on zzmoove but only to a point where i figure out how to optimize interactive for my own usage (with hotplugging etc)
just to further the point on this advance interactive tweaks - theory-wise and practicality-wise it is sound, you use the best frequencies(Bare minimum that you can stand) and you enjoy battery savings as well. the only issue I see is if you use your phoen differently from the OP. that's why haikalizz says you need to tweak and adjust it on your own
Click to expand...
Click to collapse
Dude, haikalizz mentioned those frequencies in the post but never implemented them in the settings. That is what I'm saying.
Idle - 345Mhz
Page Scrolling - 533Mhz
Video -800Mhz
App Loading - 960Mhz
High Load Processing - 1612Mhz
mandarin91 said:
Dude, haikalizz mentioned those frequencies in the post but never implemented them in the settings. That is what I'm saying.
Idle - 345Mhz
Page Scrolling - 533Mhz
Video -800Mhz
App Loading - 960Mhz
High Load Processing - 1612Mhz
Click to expand...
Click to collapse
dude, i was responding to your question, should these freq inbetween give better battery life
You must otherwise optimize your phone first! This will not "fix" a poorly optimized system and will, in fact, reduce performance and battery life without further optimization and proper tweaking.
Please tell me how to optimize my phone ?
rmusa06 said:
You must otherwise optimize your phone first! This will not "fix" a poorly optimized system and will, in fact, reduce performance and battery life without further optimization and proper tweaking.
Please tell me how to optimize my phone ?
Click to expand...
Click to collapse
Debloat, amplify, things like that...
haikalizz said:
Debloat, amplify, things like that...
Click to expand...
Click to collapse
Thank you sir
What app are you using to implement the changes?
Well I got some nice results applying this technique and have overall 1/2 hours more sot using interactive gov. The only profile that works and follows the normal rules is the Ghostpepper profile. I have a moto x play with the same soc so it should work for the mi4i to. First you must calculate the max and min target loads before you can do something power efficient using this technique.
My advice is try to translate the nexus5x ghostpepper profile and replace your min and max target_loads with the ones in the original profile.
And why is this thread just copied and pasted from the original nexus5 thread and only replaced some words with "mi4i". You also forgot the most important part: calculating the min and max target_loads.
Considering the fact that every s810 phone out there has over heating issues apart from the one plus 2 because time was actually spent on that phone would it be possible to disable 2 or even 1 core(s) on the s810 to get rid of the heating issues or can that only be done by Sony. You must think i am stupid but hey oh i am just uncomfortable with all the heat i don't mind a bit of performance loss when i know my phone does not feel like its being barbecued.
https://forum.xda-developers.com/xperia-z5/general/tweak-improve-performance-reduce-t3387879
I use this work from rytekk on mm and nougat it is flawless, you have control over cores annytime above 30% battery, if below then z5 takes over...
Oh... Stock roms tested ?
stipi69 said:
https://forum.xda-developers.com/xperia-z5/general/tweak-improve-performance-reduce-t3387879
I use this work from rytekk on mm and nougat it is flawless, you have control over cores annytime above 30% battery, if below then z5 takes over...
Oh... Stock roms tested ?
Click to expand...
Click to collapse
Thx for the reply but could you possibly elaborate further what do you mean because I have installed this before in the sense it would make it faster but not disable 2 cores or under preforming like just tell me what I have to do with this so I can underclock / disable 2 cores
Quantumkk123 said:
Thx for the reply but could you possibly elaborate further what do you mean because I have installed this before in the sense it would make it faster but not disable 2 cores or under preforming like just tell me what I have to do with this so I can underclock / disable 2 cores
Click to expand...
Click to collapse
I dont know the whole science about thos but i folowed the manual, pushed these file in correct folders and rebooted... I use kernel aduitor, app that alpows me to disable or enable cores as i choose ( except if phone is thermal throttling or battery below 30%) now i go to workf iy dou don't do it till evening i can at least telly you how i did it step by step...
stipi69 said:
I dont know the whole science about thos but i folowed the manual, pushed these file in correct folders and rebooted... I use kernel aduitor, app that alpows me to disable or enable cores as i choose ( except if phone is thermal throttling or battery below 30%) now i go to workf iy dou don't do it till evening i can at least telly you how i did it step by step...
Click to expand...
Click to collapse
Oh ok makes more sense so lemme get this straight copy the filez to system etc then reboot. Then go onto kernel auditor and turn off cores of my choice as it's enabled them?
Ok i have those files renamed and ready at my dropbox, just copy them in /system/etc
Make sure to backup original files...
https://www.dropbox.com/sh/ue4bbik61aair9u/AADLznjHZzmExXbiSnZ_iTkra?dl=0
Now reboot
And if you want total control rename thermal-engine.config to:
thermal-engine.configdisabled
Reboot
Now you have control over cores, again if battery above 30% or ifphone is not thermal throttling
It allso takes some knowing in kernel aduitor if you wish i can screenshot my settings
I allso sugest some good cpu governors tp make the mpst of it, you have some in androplus kernels for marshmallowi think, not sure for nougat, and you can allso add then manualy
stipi69 said:
Ok i have those files renamed and ready at my dropbox, just copy them in /system/etc
Make sure to backup original files...
https://www.dropbox.com/sh/ue4bbik61aair9u/AADLznjHZzmExXbiSnZ_iTkra?dl=0
Now reboot
And if you want total control rename thermal-engine.config to:
thermal-engine.configdisabled
Reboot
Now you have control over cores, again if battery above 30% or ifphone is not thermal throttling
It allso takes some knowing in kernel aduitor if you wish i can screenshot my settings
I allso sugest some good cpu governors tp make the mpst of it, you have some in androplus kernels for marshmallowi think, not sure for nougat, and you can allso add then manualy
Click to expand...
Click to collapse
yh thanks would be appreciated to see your settings but i copied the files from the post i will try yours now but the one from the post gave me no control over kernel auditor, however a friend told me it can be done via kernel and odex..? if you know this way please explain if not i will try the configdisabled thing and see if that works thanks again
Still getting a really hot phone
Sory to hear that, i guess it comes up to all factors than annyone can forsee... Best i could do with those files and with greenify was super cool phone almost no drainage, but when working ( if so choosen) it was a performer and yes... Scorched hot
If you wish to have good nougat rom flash xz2 rom from xnoob, leave /system/etc as is, change nothing i am amazed how cool it runs and how great it performs... Battery life best till now for me, But do a clean install,
An easy way to reduce heat is to adjust hotplugging thresholds for the big cores (you'll need root of course). You can do that easily through Kernel Adiutor in the CPU Hotplug settings. Lower the "minimum cpus big" and raise the "busy up threshold". If you really don't want your big cores on just set busy up threshold to 100 or something.
I personally have mine set to 0 minimum and 87 busy up threshold. You'll need to make an extra adjustment to get 0 minimum big cpus to stick, otherwise it will revert back to the default of 1. (note: I'm on the latest stock rom)
Also, setting your cpu governors to interactive and fine tuning the parameters will further reduce heat.
Thx for that I am using the xz2 Rom lol could you send me a pic of the kernel auditor settings?
Quantumkk123 said:
Thx for that I am using the xz2 Rom lol could you send me a pic of the kernel auditor settings?
Click to expand...
Click to collapse
Sure
crono9977 said:
Sure
Click to expand...
Click to collapse
Thx for the pic but I can't seem to find the core control option lol please tell me how you go there and also cool nav bar
stipi69 said:
Sory to hear that, i guess it comes up to all factors than annyone can forsee... Best i could do with those files and with greenify was super cool phone almost no drainage, but when working ( if so choosen) it was a performer and yes... Scorched hot
If you wish to have good nougat rom flash xz2 rom from xnoob, leave /system/etc as is, change nothing i am amazed how cool it runs and how great it performs... Battery life best till now for me, But do a clean install,
Click to expand...
Click to collapse
Yh lol thanks but I have installed the xz2 Rom and yh it was quite good but I was trying to eliminate the heat whilst the good performance oh well but anyway I kinda need those files from the xz2 because mine our kinda messed up now it would be appreciated if you sent me them via Google drive mega mediafire etc so I can redownload those files and not the whole rom thx
crono9977 said:
An easy way to reduce heat is to adjust hotplugging thresholds for the big cores (you'll need root of course). You can do that easily through Kernel Adiutor in the CPU Hotplug settings. Lower the "minimum cpus big" and raise the "busy up threshold". If you really don't want your big cores on just set busy up threshold to 100 or something.
I personally have mine set to 0 minimum and 87 busy up threshold. You'll need to make an extra adjustment to get 0 minimum big cpus to stick, otherwise it will revert back to the default of 1. (note: I'm on the latest stock rom)
Also, setting your cpu governors to interactive and fine tuning the parameters will further reduce heat.
Click to expand...
Click to collapse
thanks for explaining, it will help me further tweak my phone as i like
Hey guys so after some tinkering and tweaking with the kernel I've come up with some settings that can reduce "UI lag" and improve general performance and lower heat output without tanking battery life or "SOT" so what are these setting? you may ask, well before we get into that please note that your results may vary based on the ROM and kernel you are using, I'm using Bootleggers 9.0 with GrapheneKernel v1.5, the app I'm using to tweak the setting is Kernel Adiutor, don't worry it's really simple and we're not making major changes to the kernel settings. but before making any changes please make a back up of your current settings.
Also if you have any better settings for the kernel, share them below.
First off, Go the "CPU" tab and change the big cluster frequencies:
set the minimum frequencies to 400 MHz (0.4 GHz)
Max frequencies to 1800 MHz (1.8 GHz)
change the little cluster frequencies:
set the minimum frequencies to 400 MHz (0.4 GHz)
Max frequencies to 1400 MHz (1.4 GHz)
Next, Set both big and little clusters governors to "Interactive"
Next, Go to "CPU Hotplug"
Set minimum big cluster core to 2
Change the busy down threshold to 20
Change the busy up the threshold to 40
Offline Delay to 100 ms
Next, Go to "GPU"
Set the max frequency to 600 Mhz
set the minimum frequency 266 Mhz
Set GPU governor to "msm-adreno-tz"
Set Adreno Idler to on
Change Down differential to 20
Idle wait to 20
workload to 5
Next, go to I/O Scheduler
Change the Scheduler to cfq (why because noop sucks when it comes to CPU scaling and performance)
Read-ahead value to 2048
RQ affinity to 1
and that's it your done.
If you guys want me to make a .json fine which you can import just and apply all settings in one go let me know in the comments
for me, light use = checking Twitter, Instagram, web browsing and some Youtube
moderate use = Taking photos, light gaming, and editing photos
heavy use = Lot's of photo taking, photo editing, uploading and downloading of large files, heavy gaming such Hades star, (a GPU heavy game btw) Pubg and asphalt 9 and 8
My battery life with these settings
Light use 5 hours and 26 minutes on average
moderate use 4 hours and 38 minutes on average
Heavy use 3 hours and 10 minutes on average
Heat output when in light use is 33 to 36c on average
Heat output when moderate use is 34 to 39c on average
Heat output when in heavy use or gaming is 42 to 46c on average
Bro,how to disable thermal throttling on Le 2,I've found a magisk module of mi5s,I've flash it,but I think its not working,please help,I'm also a hardcore pubg player
Bro, could you please share the link of graphene kernel 1.5?
lambha48 said:
Bro,how to disable thermal throttling on Le 2,I've found a magisk module of mi5s,I've flash it,but I think its not working,please help,I'm also a hardcore pubg player
Click to expand...
Click to collapse
Try disabling Core control if you re using the stock kernel but i recommend using GrapheneKernel or overload 4.10 for Pie based roms or overload 4.5 for oreo based roms and change the thermal limit by a factor of 5 degrees, but do this at your own risk as high temps can damage your device You can also try the new overdose kernel too
lambha48 said:
Bro,how to disable thermal throttling on Le 2,I've found a magisk module of mi5s,I've flash it,but I think its not working,please help,I'm also a hardcore pubg player
Click to expand...
Click to collapse
Disabling thermal throttling is not recommended but of you're willing to take the risk, it can be done by editing the thermal engine config file in system/etc/ folder. Remember that the chipset has in-built thermal control that kicks in when the phone gets too hot with your upped thresholds. However, don't assume that this is a good enough safety net and go crazy with the temps. You might ruin your CPU! This is more so on non-eui based roms.
twistyplain said:
Disabling thermal throttling is not recommended but of you're willing to take the risk, it can be done by editing the thermal engine config file in system/etc/ folder. Remember that the chipset has in-built thermal control that kicks in when the phone gets too hot with your upped thresholds. However, don't assume that this is a good enough safety net and go crazy with the temps. You might ruin your CPU! This is more so on non-eui based roms.
Click to expand...
Click to collapse
Bro,please tell me how,I'm on cr droid nougat,please step by step,I want it to throttle at 60 degrees
lambha48 said:
Bro,please tell me how,I'm on cr droid nougat,please step by step,I want it to throttle at 60 degrees
Click to expand...
Click to collapse
If you're rooted, go to system/etc/ folder and look for a file called thermal-engine-s2.conf and send it to me. I'll edit it for you and send it back with your requested level of 60 degrees. Explaining what all the values mean will take too long.
twistyplain said:
If you're rooted, go to system/etc/ folder and look for a file called thermal-engine-s2.conf and send it to me. I'll edit it for you and send it back with your requested level of 60 degrees. Explaining what all the values mean will take too long.
Click to expand...
Click to collapse
Bro,its in Chinese language,thermal.conf
lambha48 said:
Bro,its in Chinese language,thermal.conf
Click to expand...
Click to collapse
Send me any thermal.conf files in that folder in a zip file. I'll figure out which one needs work.
twistyplain said:
Send me any thermal.conf files in that folder in a zip file. I'll figure out which one needs work.
Click to expand...
Click to collapse
Bro,i can't find.config when open with text editor,I can't understand its in chinese ive rename to bak,doesnt seem to work,only XML I found,I'm on cr droid nougat,please install cr droid,712 on yors and figure it out
Bro,please pubg I played at 736*414 screen resolution with easy DPI changer,but it throttle at 40 degree CPU,baterry 41 degree,um on illusion kernel with cr droid 712 I need to throttle it at 60.
lambha48 said:
Bro,i can't find.config when open with text editor,I can't understand its in chinese ive rename to bak,doesnt seem to work,only XML I found,I'm on cr droid nougat,please install cr droid,712 on yors and figure it out
Click to expand...
Click to collapse
Talk to the developer about it. I can't flash a new ROM right now.
Bro,are these files to be edit to disable thermal,throttling,please help
Please link graphenekernel v 1.5