Underclocking on 2.2 Saphire 0.7.0 via SetCPU

[mscalero]

I am very happy with the speed of Froyo on my Droid. I recently purchased SetCPU but I wasn't too sure how to use it.

I think my Droid is fast enough, I don't want to overclock, I want to underclock it when the screen is dark and it's idle, to gain some extra battery life. Does anyone have a good metric they would like to share on how they set their droid to conserve battery life?

I am worried to set the CPU too slow, that I might miss calls, or eBuddy won't update, or K-9 can't check every hour if I don't touch my phone for 3 hours or so (rare though).

Anyone have a good schema to share? And how much more battery life did this schema get you, before SetCPU?

 

[Lancer033]

mine is set to run at 250 w/ the screen off and battery life has improved a lot even though i have it running @ 1100 normally

 

[mscalero]

Thanks. So you're only condition is 250 min / 250 max when screen is dark?

 

[dubge]

You can miss calls and things if it is set too low?

Can anyone confirm this? This is the first time I have read that and want to make sure I have mine setup correctly

 

[Brett]

i don't think calls will be missed. the keywords "i dont think" because i have never experienced it myself. i used to have it set at 250-250 when i first rooted my phone and had droidmod on it back in the old days haha.

now i have my phone set at 250-550 when sleeping, or whatever is closes to 550 depending on the kernel im using. if you set it at 250-550 give or take, might be the best options for you. it will go somewhere in between there, not always at 500 or 250. kind of distributes it as necessary.

thats just my preference, others might say different but the way i see it is that i have had my droid overclocked since last december and have not had a problem since then

 

[thebizz]

I set mine to 125-400 when asleep I need more kernels with the 125 slot 250-300 slot kernels murder my battery while asleep I lost 20% with one kernel in an hour while my phone was sleeping. And that's with autokiller set to aggressive

 

[ebruot]

Android 2.1 and earlier i think had a problem with the 125 setting. The phone wouldn't ramp up fast enough for you to be able to answer the phone. I think it was only on some phones or roms because i never had any problems. Supposedly 2.2 has remedied the problem from what i've read.

 

[dagostin]

125 def has had and still has issues in some cases. More prone to freezes and waking up say from a phone call can be slower and more difficult in my experience. stick with 250 up. to be honest, droid already scales the cpu even without setcpu. So when idle it will mostly be running at lower frequencies. I would just leave it alone.

 

[mscalero]

So would you say 250 min - 250 max while the screen is dark is fair? This should extend battery life?

Also, what is the OnDemand setting when the screen is awake? Should it be 250min - 550max? I am on 2.2 via Sapphire 0.7.0