Related
Hey there, I just a few days ago rooted and flashed the Syndicate Frozen rom and am not getting such good battery life...
I was wondering how big of a difference SetCpu makes on battery life/performance in general? With moderate/heavy use (internet browsing, facebook, email, txt messaging) how much should it improve battery life? am getting around 10hours at the moment with moderately light use... Is there any free alternative app that runs comparatively well?
I guess what I'm really asking is: is it worth it to buy setcpu, and will it make a dramatic difference on my battery life? This Rom is supposed to improve battery life, and I think I read is overclocked to 1.2... Will setcpu let me set this underclocked to 1,0 and then like 800 with screen off, 600 idle? Am new to the android thing [have had my EPIC only around 2 weeks today]
Thanks for any help!
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
You can set the speed to.anything you want. If you want battery to be the best then.set it to 100/1000 on demand. If you emwant performance then 100/1200. Also I don't set profiles cause I was reading somewhere that they aren't good to use on any galaxy phone.
Sent From My Evo Killer!
http://www.setcpu.com/
Nice info read up on it and yes you can set it anyway you want like stated above. I bought mine from the market to support the dev for the hard work involved in making setcpu, dont know if you know but it is free for xda members just search for setcpu. It is only $2.00 well worth the price so please support the dev if you can.
063_XOBX said:
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
Click to expand...
Click to collapse
20Mhz would freeze the phone. :O
I personally like running it @ 100 Mhz when screen is off and 1Ghz when screen is on.
Overstew said:
20Mhz would freeze the phone. :O.......
Click to expand...
Click to collapse
I am pretty sure XOBX meant 200, cause your right 20 is pretty much crawling...
Yep, I meant 200, the damn autocorrect kept changing mhz to Hz and I must've clicked backspace one too many times.
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
androikid said:
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
Click to expand...
Click to collapse
Don't expect it to magically give you another 4 hours up time. 1 extra hour would be high hopes.
I use SetCPU with the CPU set to 200/1000 and ondemand, and the battery life has improved GREATLY, well worth the $2 to support the Dev, IMO, even though XDA members get it free.
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
I have mine set to 100/1200 on demand, and it works well for the demands I put on it. Way low consumption at idle, but when I need something it instantly responds.
I routinely get 16-18 hours off the charger, and put it back on the charger with sometimes as much as 40% remaining, but as always YMMV. A lot of it has to do with the ROM, but I'd say that CPU scaling has realized a tangible gain for me.
dwallersv said:
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
Click to expand...
Click to collapse
Talking about Bonsai ROM tweaks on a Syndicate thread would be like me talking about BMW mods on a Honda forum. Either way, I looked around in the system folders and I can't find the 24-cpu file you're talking about. I upgraded yestereday from the 2.1 SyndicateROM to this, and for the first few hours, the ROM itself was definately quicker...I don't know if that's just because I came from 2.1 to 2.2, not to mention all the other 2.2 tweaks. After a few hours, I completely forgot that I could overclock this to 1.2Ghz. Installing SetCPU and bumping it to 1.2Ghz felt like just another jump. System resource consumption aside, it makes the phone all that much quicker while going between screen, apps list, closing apps, etc.
I could care less about battery life because I've learned to always have a charger around me since my days of the Moment, of hell, even my Treo's. I want fast, SetCPU is something I can see the difference in just from turning it on and off and seeing the differences.
Anyone else Trying CPU Tuner?
https://market.android.com/details?id=ch.amana.android.cputuner
OMG!!! I can't believe the difference it has made!!!!
What difference has it made? Does it let u overclock or what?
________________________________________________________________________
ZTE Blade - Rooted OC 729mh CM7 RC2 V nice
Advent Vega - Rooted OC 1.4gh - Corvous5 rom gorgeous smooth and qqqick
Iconia A500 - Rooted - HComb Sweet
From what I understanb, the A500 and other mobile devices are under-clocked at the factory to save on battery. The allows you to adjust the CPU up to 1Ghz. So, not really overclocking, but you will see a big difference.
So you have already done it?
Enviado desde mi A500 usando XDA Premium App
ithink2020 said:
From what I understanb, the A500 and other mobile devices are under-clocked at the factory to save on battery. The allows you to adjust the CPU up to 1Ghz. So, not really overclocking, but you will see a big dif
just so you know this app is not needed for our CPU to run at the full 1ghz. the CPU runs full speed when the system demands it by default. this app is more for setting profiles to extend battery life. if you use system panel or a similar app you will see that the CPU runs full speed when needed. CPU tuner seems to be a great app for extending battery life though, so thanks for the tip.
Click to expand...
Click to collapse
how fast have you gotten it?
ithink2020 said:
From what I understanb, the A500 and other mobile devices are under-clocked at the factory to save on battery. The allows you to adjust the CPU up to 1Ghz. So, not really overclocking, but you will see a big difference.
Click to expand...
Click to collapse
Wrong. None of the devices are "under clocked" at the factory. There is just no reason that your device needs to run at 100% speed 24/7, so the CPU and the OS scale the speed back if the device is idle. Just like a laptop or desktop PC.
so if honeycomb automatically scales back the CPU when its not need does that mean that this kind of app is really needed to save battery?
Sorry, I must have miss-read something some place and was understanding it incorrectly. All I know, is thing are running faster.
Thank you das7771 and geeknik for the info!
No apology needed. We are all here for help, info, reseach, and hacking. I learn something new every day myself.
codemansGT said:
so if honeycomb automatically scales back the CPU when its not need does that mean that this kind of app is really needed to save battery?
Click to expand...
Click to collapse
Depending on your preference. One thing this app will do is scale down your frequency according to the profile you select ,for example, if your battery is at 50% and you want it to last longer, than what it would at stock settings, you can create a profile for your CPU to run at a lower speed like 800mhz. That way your battery will last longer throughout the day if you can not charge it. You can set multiple profiles for different battery levels of your preference and have the cpu run at slower speeds to preserve battery. So if your anal about your battery state then it can be very useful. Becuase at stock settings the sytem will run at whatever the speed is demanded by the system. Whether it be the minimum or maximum processor speed.
I usually prefer performance over battery life myself so unless I am going on a long road trip or I am out camping I would not use it as I have no need, but every one is different.
The question is simple, the higer the freq. the more battery consumption? i am asking because i cannot see any difference from 1.4GHZ to 1.0GHZ, the battery consumption is the same under oxygen and francos kernels. i would be grateful if the experts would give us some advise or their opionion. I know it is subjective but i would like a second opinion.
Thanks alot guys
If you look with any cpu spy app, you cab see on what clock the processor is used. I mainly have it the lowest and sometimes higher. When you change the max, it should still automatically choose what clock is used, so battery should last as much as before, if not used in high clock.
Sent from my Huawei u8800 using XDA App
Invicta said:
The question is simple, the higer the freq. the more battery consumption? i am asking because i cannot see any difference from 1.4GHZ to 1.0GHZ, the battery consumption is the same under oxygen and francos kernels. i would be grateful if the experts would give us some advise or their opionion. I know it is subjective but i would like a second opinion.
Thanks alot guys
Click to expand...
Click to collapse
Probably not much difference, when you overclock, think the cpu voltage remains the same as it is on 800mhz... And the highest cpu freq is rarely even at use...
Invicta said:
The question is simple, the higer the freq. the more battery consumption? i am asking because i cannot see any difference from 1.4GHZ to 1.0GHZ, the battery consumption is the same under oxygen and francos kernels. i would be grateful if the experts would give us some advise or their opionion. I know it is subjective but i would like a second opinion.
Thanks alot guys
Click to expand...
Click to collapse
Well, thanks to most devoted users of U8800, we have somewhat better speed+battery life than stock also. To answer your question, yes depending on your activity the frequency have some impact, but overall shouldn't be huge in change, for example from .800 to 1.0GHz will not affect so much in daily use. However from .800 to 1.5GHz would make a somewhat huge gap difference. This doesn't mean it will drain faster if you do same activity as with .800 to 1.0GHz, for example check the watch, answer sms or few "entertainment" breaks. Only when using the phone over a longer period of time that's when you will notice the change of battery life with different frequency. Hope it clears up most hums and huhs for you. I am pretty sure some expert within this field will give a better explanation than me.
Bye~
higher freqs uses more energy, but lower uses less energy but do things slower (so energy consumption is longer). ALSO imo - if you set cpu to 1Ghz the lowest value so it always is 1ghz - it will not consume the same amount of energy if it's in idle mode - it's like your laptop - if cpu is working only in 4-7% of it's power - then the power consumption is lower no matter what freq - how do we know that? - because of heat - the more heat you get - the more energy was used. and when cpu is idle - it will not be hot.
So the answer is - if it saves then in VERY minimal amounts. But even so - i use min freq - 360mhz. it's good for me i do not get any lag so i use it.
I use the "Root System Tool Free", option CPU and I see the graphics of all clocks.
For ex. now at 245 mhz ->46%, at 368 ->10%, at 768 mhz ->18% .... and at 1612 mhz -> 1,8%, at 1804 mhz ->4,9%. Not very mutch use at 1804.
Oxygen-test-140911 + Franco.Kernel1709#1. Clock at 1804 Mhz by Menu-settings-cpu ... and smartassV2 (no profils).
The battery, I charge it all 24 hours. But I like my work... and testing things. When then will dead...I see...
ValenteL said:
I use the "Root System Tool Free", option CPU and I see the graphics of all clocks.
For ex. now at 245 mhz ->46%, at 368 ->10%, at 768 mhz ->18% .... and at 1612 mhz -> 1,8%, at 1804 mhz ->4,9%. Not very mutch use at 1804.
Oxygen-test-140911 + Franco.Kernel1709#1. Clock at 1804 Mhz by Menu-settings-cpu ... and smartassV2 (no profils).
The battery, I charge it all 24 hours. But I like my work... and testing things. When then will dead...I see...
Click to expand...
Click to collapse
cpu spy is more pretty, anyway all those apps just reads text file of cpu stat and that's it
Tommixoft said:
cpu spy is more pretty, anyway all those apps just reads text file of cpu stat and that's it
Click to expand...
Click to collapse
Thanks
But I like more the Root System Tool, because has also a Linux Console. I use it when I want make some cmd's Linux in #. I don't like the Terminal Emulator.
Well, there is a "catch" somewhere in there. The frequency does indeed affects the power consumption of the CPU and greatly at that too! But the thing is, your CPU is not the worst enemy of your battery life. Even though CPU consumes more power in higher frequencies, it still can not compete with what your screen LEDs or your GSM module or your GPS chip consumes leisurely. So, if you're looking at the overall picture -meaning if you're wondering if it will affect how long you'll be able to use your battery in your phone- the answer is, "yes but not so much". Especially if you're switching the CPU frequency based on the demand (like using smartass or on-demand governors)
Here are the thing that sucks your batteries life juice like a vampire :
Your Screen (especially background LEDs)
GSM module (talking, using GPRS/Edge/3G network communication)
GPS chip
Wireless module (this also includes Bluetooth, even though it does not consume as much as Wireless network access but everything is relative -think about playing music through A2DP headphones compared to having your wireless network active but not using it much-)
(oh yes, I love to use lots of parenthesis -and even this hyphenation thingy- )
Correct me if I'm wrong about anything by the way ..
Regards ..
I did some experiments with a msm8250 a while back and there's a graph here:
http://forum.xda-developers.com/showpost.php?p=14324649&postcount=3786
msm7x30 should be fairly similar though the graph is probably shallower since it's a smaller process size.
The CPU uses no power when it's not in use, even with the display on, the CPU is powered down completely when idle (power collapse).
Hey guys, Kyuubi10 back once again with another Guide.
I thought it might be useful to pop in a couple results of my trial and error for the HTC One M8.
Note: This is not scientifically, calculated accurate, but it's close enough, based on estimates.
After following these guides:
http://forum.xda-developers.com/showthread.php?t=2769899
https://vjnaik.wordpress.com/2015/06/25/kernel-tweak-interactive-governor-paramaters-rooted-phone/
I decided to make a summary guide of the above but with specific HTC One M8 values.
Since I agree with the idea of "race to idle" embodied in the Wheatley governor, I tried emulating that on the Interactive governor while also keeping it as efficient as possible.
Here are the values (all others not mentioned, leave default):
Code:
[B]above_hispeed_delay [/B]- 80000 2265600:10000
[B]go_hispeed_load[/B] - 95
[B]hispeed_freq[/B] - 1728000
[B]io_is_busy[/B] - 1
[B]min_sample_time[/B] - 10000
[B]target_loads[/B] - 45 729000:80 883200:50 1267000:85 1497600:50 1728000:90 1958400:50
[B]timer_rate[/B] - 10000
[B]timer_slack[/B] - 5000
"above_hispeed_delay" makes sure that longer time is spent on the frequency step 1.72Ghz, before quickly raising higher into max freq.
1.72Ghz is the most energy efficient frequency with a good performance, e.g. it will not cause lag during casual usage, while it uses minimal voltage.
If the load is too high for this frequency to handle, I set the time short once it's gone over this freq step so that it will not waste time before reaching max freq. Thus dealing with the issue asap.
Another important parameter is "target_load", with this I have defined that at each efficient freq step the load needed to overcome it would be higher than normal. But it would up-scale quickly when using non-efficient frequencies.
The other parameters I have set so that the frequency is lowered as soon as CPU load is finished, so that it will rush back to idle as quickly as possible.
The interesting thing about this set-up is that for general, non heavy usage, it basecally functions as if I have underclocked to 1.72Ghz, but when the CPU is truly pushed it reaches up to 2.5Ghz which is my Overclocked max freq value.
Thus both saving battery and providing high performance.
I have felt no lag, and it's been quite a smooth experience while I used this
Combined with using GPU rendering (found in developer settings), and Seeder, the over all usage is pretty good.
Battery usage has been very efficient and I have managed to squeeze out an extra hour or two using this.
I highly recommend it!
Hope I helped you guys... don't forget to press the thanks button if you also feel that I did!:good::good:
I noticed I have some governor settings left at 0 or blank. I did some quick googling, found some other tweaks for the M8 and the interactive governor. So I played around a bit, and I think the following would be useful to add to the above tweaks.
-----------------------
sampling_down_factor: 60000
sync_freq: 1036800
up_threshold_any_cpu_load: 65
up_threshold_any_cpu_freq: 1190400
boost: 0
boostpulse_duration: 80000
--------------------
Also of note there is not a entry for " io_is_busy " under the Interactive governor under ElementalX Sense kernel v6.03. I believe it's possible to modify the governor to add the function, if it's desired.
Hope this helps others.
nice one i read the links that you posted and follow the guides there also to tweak the interactive governor on the first link that you posted is really interesting he has updated that post also, i followed his guide inspired by your guide and i have been getting good results on my phone with battery and performance i mean almost no battery drain at all while my phone is idle. thanks for the help mate!
Plugged the settings into Yankactive on DU. Quick, freqs stay low when nothings going on, seems legit. I set my timer_rate higher tho, 10000 feels a little low, makes me think that the CPU will spend too much time polling loads.
SaskFellow said:
I noticed I have some governor settings left at 0 or blank. I did some quick googling, found some other tweaks for the M8 and the interactive governor. So I played around a bit, and I think the following would be useful to add to the above tweaks.
-----------------------
sampling_down_factor: 60000
sync_freq: 1036800
up_threshold_any_cpu_load: 65
up_threshold_any_cpu_freq: 1190400
boost: 0
boostpulse_duration: 80000
--------------------
Also of note there is not a entry for " io_is_busy " under the Interactive governor under ElementalX Sense kernel v6.03. I believe it's possible to modify the governor to add the function, if it's desired.
Hope this helps others.
Click to expand...
Click to collapse
Some of those actually make no difference. Since they are overruled by other perameters. E.g. up_threshold aren't used in interactive, since they follow target_load instead.
Sampling_down_factor on the other hand is overrulled by the timer features of interactive.
When you use ondemand, or conservative, sampling_down_factor is a fun parameter to play with, but not interactive.
While Sync_Freq I don't like using because it raises minimum frequency to its value...although temporarily, the timer features can already deal with CPU loads efficiently.
lil_kujo said:
nice one i read the links that you posted and follow the guides there also to tweak the interactive governor on the first link that you posted is really interesting he has updated that post also, i followed his guide inspired by your guide and i have been getting good results on my phone with battery and performance i mean almost no battery drain at all while my phone is idle. thanks for the help mate!
Click to expand...
Click to collapse
Great The links are important!! They are my sources, and often contain much more detail than what I use in my guides. I attempt creating a well ordered summary, but my sources are better if you don't mind reading loads.
I'm glad I could help
munkyvirus said:
Plugged the settings into Yankactive on DU. Quick, freqs stay low when nothings going on, seems legit. I set my timer_rate higher tho, 10000 feels a little low, makes me think that the CPU will spend too much time polling loads.
Click to expand...
Click to collapse
That's the idea. And never heard of Yankactive...but I'm gonna assume it's good lol.
And about time_rate, you are right, but you are also wrong.
There isn't a true right answer unless someone performs a scientific experiment in order to fully test which one is better.
But I'll explain why I put my one short... I want the frequencies returning to IDLE asap. While yes, you are right it's polling often, it also returns to idle much faster, rather than staying at higher frequency uselessly wasting battery.
I'll try to run some tests checking CPU load, if CPU load considerable lowers I'll come back and report.
Yankactive is Interactive with some under the hood tweaks, I believe, same tunables. I also looked at some documentation on Interactive and I think the target_loads have to be in ascending order based on load when paired with clock speeds, I'm gonna mess with them a bit and see what I get. Link
munkyvirus said:
Yankactive is Interactive with some under the hood tweaks, I believe, same tunables. I also looked at some documentation on Interactive and I think the target_loads have to be in ascending order based on load when paired with clock speeds, I'm gonna mess with them a bit and see what I get. Link
Click to expand...
Click to collapse
And no, target_loads has to be in ascending order based on FREQUENCY. You are applying load percentages to frequency ranges, therefore it is imperative that its the frequency defining the order.
e.g. 50 4:80 10:20 12: 50 means:
50% load before going to the next frequency step, until you reach frequency 4, then use 80% instead until frequency 10, then use 20% instead until 12, then use 50% until max frequency.
Feel free to play with them as much as you want, just make sure to keep the idea of using efficient frequency steps in mind.
Kyuubi10 said:
And no, target_loads has to be in ascending order based on FREQUENCY. You are applying load percentages to frequency ranges, therefore it is imperative that its the frequency defining the order.
e.g. 50 4:80 10:20 12: 50 means:
50% load before going to the next frequency step, until you reach frequency 4, then use 80% instead until frequency 10, then use 20% instead until 12, then use 50% until max frequency.
Feel free to play with them as much as you want, just make sure to keep the idea of using efficient frequency steps in mind.
Click to expand...
Click to collapse
Thank you for the knowledge dump, been scraping the barrel for weeks trying to figure out tunables!
munkyvirus said:
Thank you for the knowledge dump, been scraping the barrel for weeks trying to figure out tunables!
Click to expand...
Click to collapse
Hehe it's a pleasure.
It's a way I find to give back to the community, since I learn so much through it. I can try help make life easier for those who follow the same path I did.
Hello kyuubi10 thanks for your help, would it be ok to change mp decision to battery saver mode ? Whats your take on that?
Wow, this is awesome! I had the performance gov on, which just destroyed my battery. Now, I have a question for you!
What is your take on "Multicore Power Savings" ? I'm using a flarport kernel which has it set to aggressive by default. Should this be changed to anything else while using your gov settings? Thanks for any assistance!
lil_kujo said:
Hello kyuubi10 thanks for your help, would it be ok to change mp decision to battery saver mode ? Whats your take on that?
Click to expand...
Click to collapse
I have never heard of mpdecision having a battery saver mode XD
Would you please expand on that? Also tell me which tweaking app you are using?
Kyuubi10 said:
I have never heard of mpdecision having a battery saver mode XD
Would you please expand on that? Also tell me which tweaking app you are using?
Click to expand...
Click to collapse
It's in the ex app mate, it uses a less aggressive version of mpdecision to saver on battery power but I can't say that I noticed much improvement TBH.
Sent from my HTC One_M8 using Tapatalk
Anonaru said:
Wow, this is awesome! I had the performance gov on, which just destroyed my battery. Now, I have a question for you!
What is your take on "Multicore Power Savings" ? I'm using a flarport kernel which has it set to aggressive by default. Should this be changed to anything else while using your gov settings? Thanks for any assistance!
Click to expand...
Click to collapse
You had performance on?? You do realise that the perf gov basically keeps your CPU cores running on max frequency all the time right?
No wonder your battery was dying XD
Anyhoo....good thing you found my guide
Now, about multicore power savings, as usually with most things you will be compromising something to gain something else...always keep that in mind.
With MPS you'll be giving up some multitasking, in order to gain some battery savings.
Why (you may ask)?
Well, think about a to-do list, and for each list you have one person completing the tasks within that list. Let's say you have four lists and 4 people completing those tasks.
What MPS does is it takes as many tasks as possible and places them within a single list, for one person to do. At the end of the day that one person will have done a lot of work, while the other 3 will have done very little work. The drawback? The work was completed much slower, because only one person was doing it.
Why can MPS be good? It is the way it chooses which CPU to use to add the tasks to, it chooses CPUs which are already turned on, rather than turning a new one on.
The frequency voltages on each core range from the lowest of 775mV, to the highest of 1075mV. That's a 300mV increase in battery consumption between lowest frequency and highest. (Mind you, 1075 for me is an overclocked value, if you are not OC then it will be even less)
When CPU cores have nothing to do they get turned off....they don't idle at 775mV....they are literally off. Therefore around 0mV usage XD
If you get tasks which would have run on 2 CPUs at minimum frequency, using only 775mV each, and put them to run on only 1 CPU at MAX frequency at 1075mV, you still have about 400mV battery savings. Now lets say its something which would have used 4 CPUs, but you end up using only two.... then the battery savings double to 800mV.
Final answer...it depends on your tastes, what do you prefer most? Multitasking or battery saving.
Personally I keep it enabled, but not aggressive.
But if you really don't care about multitasking, you may as well leave it as aggressive.
lil_kujo said:
Hello kyuubi10 thanks for your help, would it be ok to change mp decision to battery saver mode ? Whats your take on that?
Click to expand...
Click to collapse
smeejaytee said:
It's in the ex app mate, it uses a less aggressive version of mpdecision to saver on battery power but I can't say that I noticed much improvement TBH.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Well, I use adiutor, so I don't have that option.
I am happy with my phone how it is (if it wasn't for the damned plug issues XD)
But @lil_kujo, as @smeejaytee said....he hasn't noticed much improvement.
So I'd trust his advice
Kyuubi10 said:
You had performance on?? You do realise that the perf gov basically keeps your CPU cores running on max frequency all the time right?
No wonder your battery was dying XD
Anyhoo....good thing you found my guide
Now, about multicore power savings, as usually with most things you will be compromising something to gain something else...always keep that in mind.
With MPS you'll be giving up some multitasking, in order to gain some battery savings.
Why (you may ask)?
Well, think about a to-do list, and for each list you have one person completing the tasks within that list. Let's say you have four lists and 4 people completing those tasks.
What MPS does is it takes as many tasks as possible and places them within a single list, for one person to do. At the end of the day that one person will have done a lot of work, while the other 3 will have done very little work. The drawback? The work was completed much slower, because only one person was doing it.
Why can MPS be good? It is the way it chooses which CPU to use to add the tasks to, it chooses CPUs which are already turned on, rather than turning a new one on.
The frequency voltages on each core range from the lowest of 775mV, to the highest of 1075mV. That's a 300mV increase in battery consumption between lowest frequency and highest. (Mind you, 1075 for me is an overclocked value, if you are not OC then it will be even less)
When CPU cores have nothing to do they get turned off....they don't idle at 775mV....they are literally off. Therefore around 0mV usage XD
If you get tasks which would have run on 2 CPUs at minimum frequency, using only 775mV each, and put them to run on only 1 CPU at MAX frequency at 1075mV, you still have about 400mV battery savings. Now lets say its something which would have used 4 CPUs, but you end up using only two.... then the battery savings double to 800mV.
Final answer...it depends on your tastes, what do you prefer most? Multitasking or battery saving.
Personally I keep it enabled, but not aggressive.
But if you really don't care about multitasking, you may as well leave it as aggressive.
Click to expand...
Click to collapse
Hah, thanks for the guide-- I am pretty well versed in task / resource allocation on multi-threaded systems, though
Main reason I was asking was because I haven't a clue what some of the values are on this interactive gov. Just wanted to make sure they didn't clash! I'll chance it to "Enabled" rather than "Aggressive," because a compromise between the two sounds the best
As for Performance gov-- default setting on this flarport kernel, didn't bother to check it until I noticed that any time a core was on, it was racing at 2.5ghz, even with nothing going on. Battery pretty much committed suicide
Anonaru said:
Hah, thanks for the guide-- I am pretty well versed in task / resource allocation on multi-threaded systems, though
Main reason I was asking was because I haven't a clue what some of the values are on this interactive gov. Just wanted to make sure they didn't clash! I'll chance it to "Enabled" rather than "Aggressive," because a compromise between the two sounds the best
As for Performance gov-- default setting on this flarport kernel, didn't bother to check it until I noticed that any time a core was on, it was racing at 2.5ghz, even with nothing going on. Battery pretty much committed suicide
Click to expand...
Click to collapse
LOL I suggest you change kernel asap! If the dev uses uses Performcance gov as his default he doesn't know what he is doing XD
And no, as far as I know governor tunables won't ever clash with MPS.
Thanks!
rjavc said:
Thanks!
Click to expand...
Click to collapse
You're welcome! Pleasure to help.
But I'd appreciate if you press the thanks button on the relevant posts which helped you. That's the XDA way :good::good:
Kyuubi10 said:
You're welcome! Pleasure to help.
But I'd appreciate if you press the thanks button on the relevant posts which helped you. That's the XDA way :good::good:
Click to expand...
Click to collapse
Hi mate, I wondered if I could ask your advice, I want to set interactive up on my maw Android TV box it's quad 1.5gb and I want maximum performance as its constantly plugged in, there is no battery so that's not an issue,
Sorry if you think this OT but I thought I'd ask you as you know the governor well, thank you in advance mate.
Sent from my HTC One_M8 using Tapatalk
In many of the old threads here I see recommendations about underclocking the CPU in the NST, usually with either SetCPU or No-Frills CPU Control.
Has anyone ever actually been able to get a max_freq that's lower than 800MHz (or 1000MHz with guevor's kernels), though? I never have. The setting sticks and the correct value is written to /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq (which you can also do manually from a terminal emu or adb), but the setting seems to have no effect. ./stats/time_in_state or the current freq still show that higher frequencies are used just as much. Oddly enough, increasing the scaling_min_freq does work, though I don't want to do that.
I even tried modifying the init.rc and setting a lower max_freq there, but still no luck.
Am I the only one that has this issue? Maybe it's some kind of conflict with another setting I use or something?
I'd really like to be able to use guevor's 166 kernel, but I don't want the 1000MHz overclock, since it definitely drains the battery faster when you're doing anything other than reading. Alternately, does anyone know if there's another kernel out there that works with both NoRefresh and Fastmode2, but doesn't have the overclock?
SweaterFish said:
Has anyone ever actually been able to get a max_freq that's lower than 800MHz (or 1000MHz with guevor's kernels), though? I never have.
Click to expand...
Click to collapse
Back in the day I did use No Frills CPU Control and I seem to recall being able to reduce clocking and have that persist. But that was many years and quite a few grey cells ago.
SweaterFish said:
I'd really like to be able to use guevor's 166 kernel, but I don't want the 1000MHz overclock, since it definitely drains the battery faster when you're doing anything other than reading. Alternately, does anyone know if there's another kernel out there that works with both NoRefresh and Fastmode2, but doesn't have the overclock?
Click to expand...
Click to collapse
I know I certainly had the CPU down to 800MHz, never at 1GHz. All the FastMode compatible kernels are overclocked and only 166 is able to run NoRefresh (which doesn't actually require any kernel modification, although multi-touch is nice to have with it) and FastMode (not at the same time, of course).
nmyshkin said:
I know I certainly had the CPU down to 800MHz, never at 1GHz.
Click to expand...
Click to collapse
Hm, odd. Did you ever actually confirm that the CPU didn't run at 1000MHz by looking at the time_in_state stats?
I've never been able to underclock with any kernel. My system is based on fw1.2.1 rooted with NookManager, with many small modifications and all the stock apps removed, but I don't see why any of that would affect the CPU max freq, especially in a way that would still have the min freq setting work.
The best I've been able to do is adjust the scaling governor settings to make it less likely to step up, but that doesn't work all that well.
SweaterFish said:
Hm, odd. Did you ever actually confirm that the CPU didn't run at 1000MHz by looking at the time_in_state stats?
I've never been able to underclock with any kernel. My system is based on fw1.2.1 rooted with NookManager, with many small modifications and all the stock apps removed, but I don't see why any of that would affect the CPU max freq, especially in a way that would still have the min freq setting work.
The best I've been able to do is adjust the scaling governor settings to make it less likely to step up, but that doesn't work all that well.
Click to expand...
Click to collapse
I did not get as technical as you. It's been a long time since I used one of those kernels and I only recall that there were a bunch of arcane settings in the CPU governor app which I did not fully understand but set according to some list somewhere.
As far as the app was concerned, the CPU freq was under control. Whether that was actually the case or not was beyond my pay grade.
What it comes down to is how important is FastMode to you? I personally found the ghosting intolerable. It's certainly not for reading as the fine image quality is so degraded by the dithering. In the end, USB Audio and NoRefresh were more important to me and there is no kernel that supports both of the enhanced display modes and USB host. So I didn't have to deal with the overclocking issue.
FastMode and NoRefresh have different uses, in my opinion. FastMode is nice because it keeps working even when you change apps. I use it mostly to reduce the amount of screen flashing when I'm doing things like moving files around. NoRefresh would be worse than the regular behavior since it would keep disabling.
Overall, I'd prefer to be able to use both even if it means more battery drain in some cases, which is what I've been doing for years.
I was just curious if other people had this issue or not since I've never seen anyone else mention it. The time_in_state stats are shown in both No-Frills and SetCPU and I figured most people would look at them if they were trying to adjust the freqs.