OverClocking 101

[Skull One]

Ok I have another newb question.

I set my SetCPU according to your instructions. It was a 1200 mghz kernel and set CPU says its running at max 1200 and min 250.

But I have a CPU Widget on my phone and, sitting here doing nothing, it keeps fluctuating between 250 to 400 to 800, while set cpu keeps saying 1200 250.

Am I doing something wrong?

The Frequency adjusts in real time based on your setting and work load. So SetCPU will show min/max but you can use other programs to read it in real time.

Ok I have a very big problem.

The CPU and Temp Widget I have says my battery is 46 degress celcisu (waaaaay hot) but my SetCPU hasn't changed from 39.0 degrees. My CPU is set to drop if it reaches over 44.9 degrees celsius, but if my SetCPU isn't registering temperature changes then it might be overheating.

Help! Please!

I believe you will have to take SetCPU out of passive mode and tell it to scan the temps every 30 seconds or so for this condition.

 

[DocDoom187]

I believe you will have to take SetCPU out of passive mode and tell it to scan the temps every 30 seconds or so for this condition.

How do I do this? And will this kill my battery?

 

[Skull One]

I believe you will have to take SetCPU out of passive mode and tell it to scan the temps every 30 seconds or so for this condition.

How do I do this? And will this kill my battery?

When you create the widget, the third pull down is "Active Refresh Interval". I doubt it will make more than a 1% difference on battery drain over 24 hours.

 

[DocDoom187]

Thank you so much man!!

 

[TuBitMittens]

I'm wondering what people think of having the profile for screen off(my priority for that is 100) to something like only 250mhz max or even all the way down to 125?? Would this affect the rate at which you receive phone calls, texts, emails etc?????? Some people say they lower their cpu rate as low as their kernel allows for when the screen is off. I'm basically wondering if its not the best idea to do that.
Skull? Anybody?

 

[Skull One]

I'm wondering what people think of having the profile for screen off(my priority for that is 100) to something like only 250mhz max or even all the way down to 125?? Would this affect the rate at which you receive phone calls, texts, emails etc?????? Some people say they lower their cpu rate as low as their kernel allows for when the screen is off. I'm basically wondering if its not the best idea to do that.
Skull? Anybody?

I spent the first 2 months of Froyo 2.2 running with the sleep/standby set at 125/400. For the last two weeks I have been running with sleep/standby in 125/1000. I haven't seen a bit of difference between the two when the phone wakes up for calls, texts or emails. I haven't worried about battery life because I throw the phone on the charger when I go to bed. And rarely drop below 40% battery in the 18 hours it is off the charger.

Eclair 2.1 did have major issues with 125 Mhz for sleep/standby. But I can say beyond all shadow of a doubt Froyo 2.2 fixed that.

 

[aggiechase37]

Question, what would be more effecient: setting setcpu to ondemand and setting processor to 550mhz, or setting it to conservative and clocking to 800 mhz. Seems like everything about this thread has been all about the ondemand setting, but in the hour or so I've had it on conservative and clocked to 800, phone seems pretty snappy. Too early obviously to tell about battery life, but it would seem like the conservative setting would do some good in that department, no?

 

[Skull One]

Question, what would be more effecient: setting setcpu to ondemand and setting processor to 550mhz, or setting it to conservative and clocking to 800 mhz. Seems like everything about this thread has been all about the ondemand setting, but in the hour or so I've had it on conservative and clocked to 800, phone seems pretty snappy. Too early obviously to tell about battery life, but it would seem like the conservative setting would do some good in that department, no?

The reason I haven't covered conservative is due to the major changes between 2.1 and 2.2. And even under 2.2 it has been changing from the first leaks a couple of months ago to today's current builds from ROM makers.

Conservative under 2.1 was much easier to explain and didn't require the user to tweak anything.

Conservative under 2.2 with SetCPU 2.0.2 allows you to set Down Threshold and Frequency Steps under advanced. I haven't benchmarked them to see their overall affects. But I do know this much, don't tweak them properly and you will run your battery out quick, fast and in a hurry.

Once I am sure that there will be no more major changes, I will take the time to pull conservative fully apart and write it up.

 

[TuBitMittens]

I'm wondering what people think of having the profile for screen off(my priority for that is 100) to something like only 250mhz max or even all the way down to 125?? Would this affect the rate at which you receive phone calls, texts, emails etc?????? Some people say they lower their cpu rate as low as their kernel allows for when the screen is off. I'm basically wondering if its not the best idea to do that.
Skull? Anybody?

I spent the first 2 months of Froyo 2.2 running with the sleep/standby set at 125/400. For the last two weeks I have been running with sleep/standby in 125/1000. I haven't seen a bit of difference between the two when the phone wakes up for calls, texts or emails. I haven't worried about battery life because I throw the phone on the charger when I go to bed. And rarely drop below 40% battery in the 18 hours it is off the charger.

Eclair 2.1 did have major issues with 125 Mhz for sleep/standby. But I can say beyond all shadow of a doubt Froyo 2.2 fixed that.

thanks for your feedback. 18 hours....are you a light user???. I get like maybe 13 hours on small use. And I know all the general batt. Saving methods.

 

[Skull One]

I'm wondering what people think of having the profile for screen off(my priority for that is 100) to something like only 250mhz max or even all the way down to 125?? Would this affect the rate at which you receive phone calls, texts, emails etc?????? Some people say they lower their cpu rate as low as their kernel allows for when the screen is off. I'm basically wondering if its not the best idea to do that.
Skull? Anybody?

I spent the first 2 months of Froyo 2.2 running with the sleep/standby set at 125/400. For the last two weeks I have been running with sleep/standby in 125/1000. I haven't seen a bit of difference between the two when the phone wakes up for calls, texts or emails. I haven't worried about battery life because I throw the phone on the charger when I go to bed. And rarely drop below 40% battery in the 18 hours it is off the charger.

Eclair 2.1 did have major issues with 125 Mhz for sleep/standby. But I can say beyond all shadow of a doubt Froyo 2.2 fixed that.

thanks for your feedback. 18 hours....are you a light user???. I get like maybe 13 hours on small use. And I know all the general batt. Saving methods.

That is such a loaded question

I can use a battery up in about 5 hours if I use it every second of that time frame. But generally it is just a phone that can be used as a micro-laptop when needed. In fact if I actually used all the tricks out there, I could probably go 36 to 40 hours on a single charge with my current usage.

 

[JohnnyDepth]

I spent the first 2 months of Froyo 2.2 running with the sleep/standby set at 125/400. For the last two weeks I have been running with sleep/standby in 125/1000. I haven't seen a bit of difference between the two when the phone wakes up for calls, texts or emails. I haven't worried about battery life because I throw the phone on the charger when I go to bed. And rarely drop below 40% battery in the 18 hours it is off the charger.

Eclair 2.1 did have major issues with 125 Mhz for sleep/standby. But I can say beyond all shadow of a doubt Froyo 2.2 fixed that.

thanks for your feedback. 18 hours....are you a light user???. I get like maybe 13 hours on small use. And I know all the general batt. Saving methods.

That is such a loaded question

I can use a battery up in about 5 hours if I use it every second of that time frame. But generally it is just a phone that can be used as a micro-laptop when needed. In fact if I actually used all the tricks out there, I could probably go 36 to 40 hours on a single charge with my current usage.

I just found your thread...Great work!!!
Let me know if there is a donate link, I feel your efforts deserve a lil
sum sumthin!

I've got a few questions I haven't seen answered or asked...

-Moto Droid (1) Bugless Beast v0.4
-I am using Chevy's 7 slot ULV 125-1200 kernel
-I have setCPU 2.0.2 paid version and it does not see the kernel?

When I hit detect I get 250mhz min, and 1200max.
Scaling has to be set from Performance to Ondemand in order
to access the advanced tab...

Once I've done this and change the *sampling* from the default
320000 to 250000 it won't stick. I can change all other values
except for the sampling???


Is something wrong?
I hit apply, set on boot, and it doesn't reflect the change.

Even when I keep the ondemand scaling option running instead of
Performance I can't get 250000 to stay.

 

[Skull One]

I just found your thread...Great work!!!
Let me know if there is a donate link, I feel your efforts deserve a lil
sum sumthin!

I've got a few questions I haven't seen answered or asked...

-Moto Droid (1) Bugless Beast v0.4
-I am using Chevy's 7 slot ULV 125-1200 kernel
-I have setCPU 2.0.2 paid version and it does not see the kernel?

When I hit detect I get 250mhz min, and 1200max.
Scaling has to be set from Performance to Ondemand in order
to access the advanced tab...

Once I've done this and change the *sampling* from the default
320000 to 250000 it won't stick. I can change all other values
except for the sampling???


Is something wrong?
I hit apply, set on boot, and it doesn't reflect the change.

Even when I keep the ondemand scaling option running instead of
Performance I can't get 250000 to stay.

That side effect of not being able to make advanced settings stick is a combo of certain versions of SuperUser and SetCPU. I reverted back to SuperUser 2.1 while using SetCPU 2.0.2 to solve the issue. I have not tried the latest version of SuperUser 2.3.1 to see if it works properly now.

As for SetCPU not picking up the min and max frequencies properly, I have seen it be either a voltage issue or a ROM/Kernel combo issue. The easiest thing to try of course is using a Low Voltage kernel to see if that clears it up. If that doesn't work, then you may have to try other kernels from other makers.

I appreciate the thought, but no donations need. I started this project as a way to learn the ins and outs of the Android OS. It just wouldn't seem right to make a dime off a open source project of this nature.

**********
While catching up on all the threads, found this. http://forum.xda-developers.com/showthread.php?t=682828

Latest version of SuperUser that says it should fix SetCPU issues.

**********
I can now confirm that the latest version of SuperUser works with SetCPU 2.0.2 properly during boot.

 

[rasseyed]

Overclocking and Battery Issue

I currently own an Motorola Droid rooted with sapphire 1.O, and Setcpu managing my o/c processor @ 125/1000. I been very happy with my droid since I updated to Sapphire, and the temperature was never a concern. But yesterday, I left my phone charging not realizing Juice defender was configuring or its setup had accidentally been started. Now normally that would not be a problem but in my workplace I loose connectivity easy, and it looks like it was left waiting/stalling looking for a signal to finish setup. When I got back to my phone was really hot and battery tempature was around 45c or higher and it took a long time to cool down. Now it seems to run hot really easy.. I can get it under control by not overclocking it and runnning my cpu under 600. I'm concerned with the temperature of my battery and temp sensor(I know that this one is an estimated Value). Did I screw something up? Any suggestions?:greendroid:

 

[Skull One]

I currently own an Motorola Droid rooted with sapphire 1.O, and Setcpu managing my o/c processor @ 125/1000. I been very happy with my droid since I updated to Sapphire, and the temperature was never a concern. But yesterday, I left my phone charging not realizing Juice defender was configuring or its setup had accidentally been started. Now normally that would not be a problem but in my workplace I loose connectivity easy, and it looks like it was left waiting/stalling looking for a signal to finish setup. When I got back to my phone was really hot and battery tempature was around 45c or higher and it took a long time to cool down. Now it seems to run hot really easy.. I can get it under control by not overclocking it and runnning my cpu under 600. I'm concerned with the temperature of my battery and temp sensor(I know that this one is an estimated Value). Did I screw something up? Any suggestions?:greendroid:

44C is under even what I consider bad for the battery. I actually would suspect something else is causing the issue and this is simply a coincidence.

 

[rasseyed]

I currently own an Motorola Droid rooted with sapphire 1.O, and Setcpu managing my o/c processor @ 125/1000. I been very happy with my droid since I updated to Sapphire, and the temperature was never a concern. But yesterday, I left my phone charging not realizing Juice defender was configuring or its setup had accidentally been started. Now normally that would not be a problem but in my workplace I loose connectivity easy, and it looks like it was left waiting/stalling looking for a signal to finish setup. When I got back to my phone was really hot and battery tempature was around 45c or higher and it took a long time to cool down. Now it seems to run hot really easy.. I can get it under control by not overclocking it and runnning my cpu under 600. I'm concerned with the temperature of my battery and temp sensor(I know that this one is an estimated Value). Did I screw something up? Any suggestions?:greendroid:

44C is under even what I consider bad for the battery. I actually would suspect something else is causing the issue and this is simply a coincidence.

Any suggestions?