so i wanna underclock my S4 for longer battery, so lets say i want to create a profile when the screen is off, i set it to 1000 MHz max and 250 MHz min. Now under 'Set CPU governor" does it matter what i set it as? the default is 'ondemand' whats that all mean? should i change it to 'powersave' or it does it really matter?
Powersave basically pushes your device to the 250-400 mhz range usually. Ondemand would fluctuate about your clock range based on background tasks. Are you using a stock kernel?? What other governors do you have?
AcreaperJB said:
Powersave basically pushes your device to the 250-400 mhz range usually. Ondemand would fluctuate about your clock range based on background tasks. Are you using a stock kernel?? What other governors do you have?
Click to expand...
Click to collapse
Im using adam kernel 1.5 for my galaxy S4 and stock kernel for my galaxy note 10.1. I just wanna set the cpu for screen off and when the battery is 50%. Whats a good range to set those on? and what governor?
Governors basically manage the cpu's behavior ( ondemand , powersave, etc. ) I don't use stock but I would use lowest freq (varies to chip) to 900 Mhz on conservative if you have it on your device.
Related
Is this possible on Androids (mostly, this phone?) Before this I had a windows phone and I had a software where I could set a minimum and maximum cpu clock rate.. and then it will overclock dynamically as needed! If you are running a game and it needs more power, it will overclock it while the game is running.. dynamically without you having to change the clock-rate manually.
This will solve battery life problems when overclocking to 1.8ghz. There is no need for it to be draining the battery at 1.8ghz if you are only texting and probably even a 200mhz cpu can do that lol
Hope what I said makes sense.
it's easily done by installing Setcpu,provided that your phone has been rooted and kernel modded to allow overclocking.
Sent from my IDEOS X5
Actually it is already done in stock ROM without root, setCPU provides a way to change the default way of handling the CPU frequencies and governors.
The stock ROM comes right out of the factory can do "cpu stepping" itself, just like the intel "Speedstep" thing. But the factory powersaving profile (or if you wish to call the scaling) might not match our taste. Then there it comes the apps called Setcpu which enhances the cpu stepping behavior according to our preference. The enhancement considers the frequency of sampling cpu load, thresholds modifications, and other considerations.
In Setcpu, we can accord one of the following scaling setting that suits our taste. From my experience, each scaling setting behaves as follows:
ondemand - runs at Min or at Max (eg. 200 MHz or 1200 MHz)
interactive - adjusts frequencies according to the real load
conservative - behaves like "interactive" but incline to power saving
performance - always runs at Max
powersave - always runs at Min
userspace - disables Setcpu scaling and uses stock scaling
smartass - behaves like "interactive" but always runs at Min when LCD screen is off
And again, the phone must be rooted and kernel modded for Setcpu to work properly.
I've been using setcpu with conservative. I like conservative because it gives you a lot of control over the throttling of the cpu. It seems to work pretty good.
Are you getting any benefit from overclocking to 1.8GHz? I also overclocked to 1.8GHz, but I didn't see any noticeable improvement past 1.0-1.2GHz.
I like to use interactive Cox I enjoy the fast sampling rate and hence the high responsiveness.
Sent from my IDEOS X5
Personally I have not tried overclocking yet.. still need to update the kernel, but I'm afraid it might get unstable.
Didn't know that CPU could do it dynamically using different profiles.
Thanks all for the help
Tcm9669 said:
Is this possible on Androids (mostly, this phone?) Before this I had a windows phone and I had a software where I could set a minimum and maximum cpu clock rate.. and then it will overclock dynamically as needed! If you are running a game and it needs more power, it will overclock it while the game is running.. dynamically without you having to change the clock-rate manually.
This will solve battery life problems when overclocking to 1.8ghz. There is no need for it to be draining the battery at 1.8ghz if you are only texting and probably even a 200mhz cpu can do that lol
Hope what I said makes sense.
Click to expand...
Click to collapse
I have setcpu but the x5 is not listed....??
okay im sorry if this is one of the most noobish questions, but what exactly are governors , and how do they help ?
Sent from my Mytouch 4G Running Capychimps Sense 3.5 rom (v.4.0)
Cpu governors "govern" how the cpu works. There is a list somewhere that explains what a few of them do. Basically they dictate how your cpu behaves and therefore the performance you see and power consumption you experience. I'll see if I can find that list.
Edit:
- The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. - The conservative sets the CPU speed in a similar way to the ondemand governor, but scales the CPU up much less rapidly. This would theoretically save battery power, but may lead to less responsiveness. - The userspace governor is currently useless. It's another way for applications to set the CPU speed that SetCPU does not use. - The powersave governor always keeps the CPU at the minimum set frequency. - The performance governor always keeps the CPU at the maximum set frequency.
Except for "userspace," no matter which governor you set, the CPU will always stay within the bounds of the maximum and minimum speeds you set in SetCPU.
smartass governor -is based on the concept of the interactive governor. I have always agreed that in theory the way interactive works -by taking over the idle loop -is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 -why?! -it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Sent from my HTC Glacier using XDA App
estallings15 said:
Cpu governors "govern" how the cpu works. There is a list somewhere that explains what a few of them do. Basically they dictate how your cpu behaves and therefore the performance you see and power consumption you experience. I'll see if I can find that list.
Edit:
- The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. - The conservative sets the CPU speed in a similar way to the ondemand governor, but scales the CPU up much less rapidly. This would theoretically save battery power, but may lead to less responsiveness. - The userspace governor is currently useless. It's another way for applications to set the CPU speed that SetCPU does not use. - The powersave governor always keeps the CPU at the minimum set frequency. - The performance governor always keeps the CPU at the maximum set frequency.
Except for "userspace," no matter which governor you set, the CPU will always stay within the bounds of the maximum and minimum speeds you set in SetCPU.
smartass governor -is based on the concept of the interactive governor. I have always agreed that in theory the way interactive works -by taking over the idle loop -is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 -why?! -it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
wow ! , thanks i guess im gonna get rid of my sleeping profile and start using smartass, thanks for the help
Sent from my Mytouch 4G Running Capychimps Sense 3.5 rom (v.4.0)
do you happen to know any info about smartassv2 ? , i just checked my list and i have both smartass and smartassv2
Sent from my Mytouch 4G Running Capychimps Sense 3.5 rom (v.4.0)
You're welcome! By the way, I'd appreciate it if you'd hit the Thanks button. I help people all the time and am rarely thanked. I'm starting to get a complex. Ha.
Sent from my HTC Glacier using XDA App
jjbat87 said:
do you happen to know any info about smartassv2 ? , i just checked my list and i have both smartass and smartassv2
Sent from my Mytouch 4G Running Capychimps Sense 3.5 rom (v.4.0)
Click to expand...
Click to collapse
Smart ass v2 is just an update of smart ass v1
Sent from my HTC Glacier using XDA App
Can someone tell me what the default values for the kernel that comes with build 5 are? I normally use Franco, but have been having some issues with it lately and want to try going back to regular kernel. After I flashed AOKP kernel back it shows the cpu settings as Minimum cpu 1026, On demand, and CFQ. I don't think those are right. I thought it was interactive with 384 min and deadline?
Any help would be appreciated. Thanks.
Hi,
All is fine. The 1026 Mhz min CPU freq is normal and it's like stock. It's for a "smoother experience" that when you touch the screen the min CPU freq goes to this freq for a time and after goes down to 384 Mhz, it's the Mpdecision stuff, some kernel devs have disable it for battery life and you can set the 384 Mhz freq as a minimum CPU freq "all the time" (related to the Cpu load). As for the governor it's Ondemand by defaut, i/o scheduler too.
Do a little search for more detailed information...
Nothing is wrong here...
Thanks for the confirmation!
Stock min CPU freq is 384 MHz.
Is there a benefit of changing this to a lower frequency?
Better battery?
nadastry said:
Stock min CPU freq is 384 MHz.
Is there a benefit of changing this to a lower frequency?
Better battery?
Click to expand...
Click to collapse
I believe after a certain frequency the voltages become the same. Meaning it takes as much power to run a processor at 384MhZ than it does at per say 126MhZ
Sent from my SM-G900T using XDA Free mobile app
Yeah, I believe the above poster is correct, but even if there is a slight variation in voltages, the battery savings are negligent and not worth the possible instabilities or slow downs that result from running the device at a frequency that low. However, if you wish to give it a shot, flashing the hellscore kernel will allow you to drop the minimum frequency to 81 MHz. Please use with caution and make a backup if you choose to proceed.
geowolf1000 said:
Iarge amount of cpu which are enable by default can modified if you do not want extra press the stock pefomance per app at setings
Is was too on cm.12 nightles too but has optoon
Now disable it
IMPORTAMD
FIRST TIME BREAKS DIALER
ONLY REBOOT IS FINE!!
Download an cpu tool you preferp
I downloaded from here
Set to 300 minimum
Get userspace And linux governor cfq.
Set on boot .
Try it .
Noop breakes wifi
Click to expand...
Click to collapse
:good::good:
+50 mA battery power less
Watt?
No need to post
Last battery issue was less than 30 mA and consume your batterry
In one day
Default cyanogen clocks is 1572 minimum....
Perfomance will not affect
Has only stable little heat all the time
And sweater heat with full sensors awake
Lte.,nfc , bluetooth...and calls with proximityis bigger
Heater but not so obvious from previous sudden
Real hot Situations.
Is this battery saver app ?
The minimum frequency is so high because the stock kernel is using MPDecision as the hotplug. This boosts the minimum frequency when you use your phone to the 1.5 GHz frequency. When you dont use your phone that intensively it clocks itself down to lower frequencies. No need to put the min freq to 300 MHz, because it already is, it just says 1.5 GHz because of the hotplug :good:
mumaster20 said:
The minimum frequency is so high because the stock kernel is using MPDecision als the hotplug. This boosts the minimum frequency when you use your phone to the 1.5 GHz frequency. When you dont use your phone that intensively it clocks itself down to lower frequencies. No need to put the min freq to 300 MHz, because it already is, it just says 1.5 GHz because of the hotplug :good:
Click to expand...
Click to collapse
When?
The apps in background still runing and if they are in background the cpu still hold same frequencies as minimum.
geowolf1000 said:
When?
The apps in background still runing and if they are in background the cpu still hold same frequencies as minimum.
Click to expand...
Click to collapse
Only when you touch the screen and a little while after that the min freq will be 1.5GHz, after that it chenges back to 300 MHz, thats how MPDecision works!
mumaster20 said:
Only when you touch the screen and a little while after that the min freq will be 1.5GHz, after that it chenges back to 300 MHz, thats how MPDecision works!
Click to expand...
Click to collapse
I will collect you the cpu stats with and op settings for all day
Perfomance will be same and post it after for more .
So the stats show that profile per app keep device at 1452mhz double time than without
I examine with same settings almost same hours and almost same usage
The white background screenshots is without
The black background is with
My perfomance is absolute same i only feel diference at low battery level
Lower than 8% at wake up
Ps there is a bug when change this settings
Battery show always awake device but is false
After full charge and shutdown all normal