Any suggestions?[/QUOTE]
Download OSMonitor from the market and see what it shows for apps running and their CPU usage.
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
OverClocking 101
- Thread starter Skull One
- Start date
- Status
Any suggestions?[/QUOTE]
Download OSMonitor from the market and see what it shows for apps running and their CPU usage.
Below you will find an interesting test run I did this afternoon. The top set of data is using the OnDemand governor and the bottom set is using interactive. The test was simple.
Droid was in sleep/standby. Fully charged and with no profiles. I set the min to 125Mhz and max to 1000 Mhz. Advanced for OnDemand was 50000, 50 , 0, 0. For Interactive it was 50000. All things made as equal as humanly possible. No calls, no texts, no nothing. I simply wanted it to sleep. I was worried that the interactive governor would be a battery drainer. The first test was to see if it changed the "Time In State" significantly from OnDemand.
The data speaks for itself and shows the huge difference.
OnDemand spent 74.59% of its time at 125Mhz. On the other hand Interactive spent 70.40% of its time in 1000Mhz.
What does that mean? Interactive is going to drain your battery faster under this condition.
I plan on doing more tests over the next week. But this first serious attempt at collecting data shows interactive is not ready for general use yet in my opinion.
I would like to thank cvpcs for building the kernel needed to run this test.
Droid was in sleep/standby. Fully charged and with no profiles. I set the min to 125Mhz and max to 1000 Mhz. Advanced for OnDemand was 50000, 50 , 0, 0. For Interactive it was 50000. All things made as equal as humanly possible. No calls, no texts, no nothing. I simply wanted it to sleep. I was worried that the interactive governor would be a battery drainer. The first test was to see if it changed the "Time In State" significantly from OnDemand.
The data speaks for itself and shows the huge difference.
OnDemand spent 74.59% of its time at 125Mhz. On the other hand Interactive spent 70.40% of its time in 1000Mhz.
What does that mean? Interactive is going to drain your battery faster under this condition.
I plan on doing more tests over the next week. But this first serious attempt at collecting data shows interactive is not ready for general use yet in my opinion.
I would like to thank cvpcs for building the kernel needed to run this test.
Last edited:
JohnnyDepth
Member
Great Test.
Can you install the newer superuser over the one that my Rom came with?
Edit, needs to be flashed v ia recovery if you don't use adb.
Thread is here by ChainsDD
[APP] Superuser 2.3.2.1 - Now on the Market [2010-08-15] - xda-developers
Can you install the newer superuser over the one that my Rom came with?
Edit, needs to be flashed v ia recovery if you don't use adb.
Thread is here by ChainsDD
[APP] Superuser 2.3.2.1 - Now on the Market [2010-08-15] - xda-developers
Last edited:
Well you changed your post, but my post stands 
Hope this helps others who have questions...
You can now add interactive to it. This was first brought to light by slahyer, and then cvpcs added it to his kernels because of Skull One and I. I will just copy and paste an explanation of the governor as it explains it best...
Hope this helps..
Hope this helps others who have questions...You can now add interactive to it. This was first brought to light by slahyer, and then cvpcs added it to his kernels because of Skull One and I. I will just copy and paste an explanation of the governor as it explains it best...
Hope this helps..
The interactive governor shot my temps through the ceiling just by simply swiping through screens for 2 minutes.
Stress test under interactive brought temps to 138.8 degrees in about 2 minutes. I shut down the device and didn't push it any further.
I would have to agree with Skull at this time. Interactive is not ready at this time.
It is fast though : ) very fast
Sent from my Droid
Stress test under interactive brought temps to 138.8 degrees in about 2 minutes. I shut down the device and didn't push it any further.
I would have to agree with Skull at this time. Interactive is not ready at this time.
It is fast though : ) very fast
Sent from my Droid
JohnnyDepth
Member
Well you changed your post, but my post stands
You can now add interactive to it. This was first brought to light by slahyer, and then cvpcs added it to his kernels because of Skull One and I. I will just copy and paste an explanation of the governor as it explains it best...
Hope this helps..
I changed my post because I (thought) I had figured out the interactive setting isn't
a scaling preference like the ones I mentioned in the deleted text
-ondemand
-conservative
-userspace
-performance
-powersave...
However I am more confused...because I just figured out it IS, just doesn't show up for me.
How do you add interactive as a scaling governor?
I was also under the impression that the newest version of Superuser
played nice with Set CPU 2.0.2...however I am unable to set
my ChevyN01 ULV kernel to output 125mhz for the lowest setting?
I am also unable to set the sample value to the recommended 250000.
I don't know why, any takers?
Last edited:
You would have to flash a kernel that has the interactive governor added in.
Open the SU app and forget setCPU, then reopen setCPU and allow it rights again.
Open the SU app and forget setCPU, then reopen setCPU and allow it rights again.
JohnnyDepth
Member
Tank, thank you!
Via your instructions I was able to forget, then allow
SetCPU within the SU app.
I was even able to change the sample rate to 250000.
Unfortunately there isn't the interactive option via scaling governor.
The minimum frequency setting is still 250mhz, not 125?
furbearingmammal
Super Moderator
Chevy kernels spec out at 250min. It's due to VERY poor performance under Eclair at 125MHz and some people are loath to change.
I honestly think that the conservative governor doesn't get enough love.
I've been running my system at 156250/70/40/0/5 on conservative and have actually noticed less jerkiness as the CPU up-clocks and much cooler temps. As low as 65° F at rest and rarely gets above 85° F under average use with my
P3Droid LV 125-1000 kernel.
Currently not running any profiles as I'd like to learn more about the inner workings of the processor when it sleeps first.
On another note does anybody either have a good source for information on how the Omap processor reacts during sleep, or would mind giving some explanation into it further?
I'm wondering does the processor actually dip below the minimum clock speed in sleep like going into a low power state on full size computers or does it just act like it's not running anything and sit at the lowest frequency slot it's allowed to? It'd be a great help if someone could enlighten me in my quest for battery life utopia!
I've been running my system at 156250/70/40/0/5 on conservative and have actually noticed less jerkiness as the CPU up-clocks and much cooler temps. As low as 65° F at rest and rarely gets above 85° F under average use with my
P3Droid LV 125-1000 kernel.
Currently not running any profiles as I'd like to learn more about the inner workings of the processor when it sleeps first.
On another note does anybody either have a good source for information on how the Omap processor reacts during sleep, or would mind giving some explanation into it further?
I'm wondering does the processor actually dip below the minimum clock speed in sleep like going into a low power state on full size computers or does it just act like it's not running anything and sit at the lowest frequency slot it's allowed to? It'd be a great help if someone could enlighten me in my quest for battery life utopia!
furbearingmammal
Super Moderator
Conservative clocks up much slower than on demand, and I use it when my battery starts getting lower, or if I know I'll be hitting the 'net a lot when I'm on the road and won't be able to charge for over 8 hours.
No, the minimum clock speed is just that. Minimum. It can't go any lower.
No, the minimum clock speed is just that. Minimum. It can't go any lower.
JohnnyDepth
Member
Chevy kernels spec out at 250min. It's due to VERY poor performance under Eclair at 125MHz and some people are loath to change.
Oh, so the people that have posted screen shots have been
using a different kernel that allows the frequency to dip to 125mhz?
Makes sense, thanks.
JohnnyDepth
Member
furbearinganimal has it right.
Also, setting up profiles via SetCPU will give you more battery life as well.
SetCPU governs how the processor behaves via the profile
you set it for. Example: Sleep/Screenoff can be set to
250mhz or 125mhz if your kernel supports that low of a speed.
furbearingmammal
Super Moderator
The slot settings in the kernel are absolute values. That's why you don't see SetCPU showing 728MHz as a speed rating.
Ah the reason I ask is that I've always wondered whether a sleep profile was really necessary. Most, at least Intel, modern processors x86/x64 can be switched into a "stasis like mode running exceptionally low clock speed just enough to react to a signal to switch back into "regular" mode. If this were the case then it would render a screen off profile pointless.
I don't really do much high performance tasks on my phone, mostly things like using the internet, navigation, and running emulators. All of this runs fine for me at 500-600 MHz with Froyo so conservative really is the best for me. It's pretty pointless for me to run those tasks at 1 GHz, as there is almost no performance difference and just dramatically more heat. At 1 GHz you processor really isn't the bottleneck anymore, as is the I/O bus, at least on this specific processor in my experience.
I don't really do much high performance tasks on my phone, mostly things like using the internet, navigation, and running emulators. All of this runs fine for me at 500-600 MHz with Froyo so conservative really is the best for me. It's pretty pointless for me to run those tasks at 1 GHz, as there is almost no performance difference and just dramatically more heat. At 1 GHz you processor really isn't the bottleneck anymore, as is the I/O bus, at least on this specific processor in my experience.
- Status