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.
Related
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
I am noticing that 300 mhz cpu frequency is never used, as per cpu spy. Wondering if it's just me.
P_
Not just you, if it gives you some relief.
Sent and typofied with Note II
I wasn't worried at all. I wonder if all these cpu frequency steps are really needed, and if the never used 300mhz can be considered a kernel bug.
The way the governor is set, 300 mhz will not be used. It is not a bug.
Hi,
Can anyone direct me to some info on altering CPU settings on my N10?
I've recently rooted and flashed the latest AOKP ROM and am interested in the performance control.
The current max is set to 1700Mhz which, of course, is the rated value for the CPU. Will I do any damage by increasing it and what effects do changing the voltage setting have?
Also, is there a guide to using Governor and IO schedulers?
Thanks in advance.
Pharmbob said:
Hi,
Can anyone direct me to some info on altering CPU settings on my N10?
I've recently rooted and flashed the latest AOKP ROM and am interested in the performance control.
The current max is set to 1700Mhz which, of course, is the rated value for the CPU. Will I do any damage by increasing it and what effects do changing the voltage setting have?
Also, is there a guide to using Governor and IO schedulers?
Thanks in advance.
Click to expand...
Click to collapse
Well I have to say that I haven't come across any device specific tutorials for governors or schedulers, and I would love to see someone put one together for the N10. My understanding is that the stock MHz value is purposely set on the slightly lower side to prevent any possibility of electrical issues. In regards to the voltage, lowering it may cause loss of display due to a lack of power and a major problem with increasing voltages is usually thermal throttling from high CPU temperatures.
But if you're interested in more governor and over clocking capabilities you should look at the KTManta kernel, I'm running it right now. You should be able to relatively safely over clock up to 1800MHz without crazy effects, but much more than that and you'll significantly reduce the tablet life.
Sent from my Nexus 10 using XDA Premium HD app
Huggogguh said:
Well I have to say that I haven't come across any device specific tutorials for governors or schedulers, and I would love to see someone put one together for the N10. My understanding is that the stock MHz value is purposely set on the slightly lower side to prevent any possibility of electrical issues. In regards to the voltage, lowering it may cause loss of display due to a lack of power and a major problem with increasing voltages is usually thermal throttling from high CPU temperatures.
But if you're interested in more governor and over clocking capabilities you should look at the KTManta kernel, I'm running it right now. You should be able to relatively safely over clock up to 1800MHz without crazy effects, but much more than that and you'll significantly reduce the tablet life.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Does overclocking to 1800MHz make much of a difference to performance?
I've just flashed the KTMANTA kernel and I am impressed.
Would it be detrimental to increase the GPU Max?
Pharmbob said:
I've just flashed the KTMANTA kernel and I am impressed.
Would it be detrimental to increase the GPU Max?
Click to expand...
Click to collapse
im not on AOKP ROM so i dont know how the CPU performance is optimized but on original rom the CPU speed rarely/never gets over
1000mhz
so overclocking to 1800mhz is pointless.
you need to upper the boost pulse instead
Patrik G said:
im not on AOKP ROM so i dont know how the CPU performance is optimized but on original rom the CPU speed rarely/never gets over
1000mhz
so overclocking to 1800mhz is pointless.
you need to upper the boost pulse instead
Click to expand...
Click to collapse
And what does the boost pulse do?
Pharmbob said:
And what does the boost pulse do?
Click to expand...
Click to collapse
it will boost the CPU speed higher when its under load
change this settings (leave the rest at default) in KTweakerT and the N10 will fly
CPU Governor: pegasusq
I/O Scheduler: ROW
under "Governor Adjustmensts" change these:
boostpulse_value: 1700
up_threshold: 40
up_threshold_at_min_freq: 20
Under Extras:
to keep your saved settings when the screen i off you will need to change the "Screen off profile Mhz" to something else than the Defualt setting
change it to 100mhz
also go in under the "Thermal Throttle Control" (settings for kids)
change these values to:
CPU start Throttle: 100
CPU Stop Throttle: 99
Memory Start Throttle: 100
Memory Stop Throttle: 99
that is the only way to get rid of the Throttling control.
one note is when you play games lock the min/max mhz to the same speed for an example (MIN 1500mhz/MAX 1500mhz)
its the up/down CPU speeds changes that causes it to lag
for movies lock the min/max speed at 800mhz and your blu ray movies will play without microstutter
also use BS player that has the fastest HW decoding
NOW Enjoy your Nexus 10 as it was ment to be used
Patrik G said:
it will boost the CPU speed higher when its under load
change this settings (leave the rest at default) in KTweakerT and the N10 will fly
CPU Governor: pegasusq
I/O Scheduler: ROW
under "Governor Adjustmensts" change these:
boostpulse_value: 1700
up_threshold: 40
up_threshold_at_min_freq: 20
Under Extras:
to keep your saved settings when the screen i off you will need to change the "Screen off profile Mhz" to something else than the Defualt setting
change it to 100mhz
also go in under the "Thermal Throttle Control" (settings for kids)
change these values to:
CPU start Throttle: 100
CPU Stop Throttle: 99
Memory Start Throttle: 100
Memory Stop Throttle: 99
that is the only way to get rid of the Throttling control.
one note is when you play games lock the min/max mhz to the same speed for an example (MIN 1500mhz/MAX 1500mhz)
its the up/down CPU speeds changes that causes it to lag
for movies lock the min/max speed at 800mhz and your blu ray movies will play without microstutter
also use BS player that has the fastest HW decoding
NOW Enjoy your Nexus 10 as it was ment to be used
Click to expand...
Click to collapse
Thanks for the info, I'm apprehensive about altering the thermal settings though. Will letting the processor get as hot as 100 degrees not reduce the life of the chip?
Pharmbob said:
Will letting the processor get as hot as 100 degrees not reduce the life of the chip?
Click to expand...
Click to collapse
sure if it would
i have already measured the CPU temp without the back case and its nowhere near 100 degrees
50 is more true so you are safe even without the Throttling control.
the thermal throttling control isnt measuring temps it only guess them.
Patrik G said:
it will boost the CPU speed higher when its under load
change this settings (leave the rest at default) in KTweakerT and the N10 will fly
CPU Governor: pegasusq
I/O Scheduler: ROW
under "Governor Adjustmensts" change these:
boostpulse_value: 1700
up_threshold: 40
up_threshold_at_min_freq: 20
Under Extras:
to keep your saved settings when the screen i off you will need to change the "Screen off profile Mhz" to something else than the Defualt setting
change it to 100mhz
also go in under the "Thermal Throttle Control" (settings for kids)
change these values to:
CPU start Throttle: 100
CPU Stop Throttle: 99
Memory Start Throttle: 100
Memory Stop Throttle: 99
that is the only way to get rid of the Throttling control.
one note is when you play games lock the min/max mhz to the same speed for an example (MIN 1500mhz/MAX 1500mhz)
its the up/down CPU speeds changes that causes it to lag
for movies lock the min/max speed at 800mhz and your blu ray movies will play without microstutter
also use BS player that has the fastest HW decoding
NOW Enjoy your Nexus 10 as it was ment to be used
Click to expand...
Click to collapse
Sorry for being such a noob but this is my first android device. I installed the kt room and the tweaker it all works fine. Bit whem i changed the room all my stift dissapeard. I vacker up my last rom can i just switch to that and backup with titan?
Btw it improved gta gaming very much. Bit what happens IF i always have the min/max on 1500?
Sent from my Nexus 10 using XDA Premium HD app
p0xis said:
Bit what happens IF i always have the min/max on 1500?
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
the tablet will explode after 30 minutes.
its the new Self destruction detection from samsung.
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.
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