I've been running the Shole's ROM, OCed to 1 GH for 24 hours with no trouble.
SetCPU is the key.
Here's my setup;
CPU Governor is set to ondemand.
Profiles are as follows:
Charging- 250 MH max, 250 MH min
Sleep/Stanby- 250 MH max, 250 MH min
Power < 40%- 550 MH max, 250 MH min
Failsafe Profile- Battery > 50*C- 550 MH max, 250 MH min
Set on Boot is checked.
Problems have been mentioned downclocking to 125 MH. The system sometimes can't wake fast enough for an app/whatever, and bad things happen. If SetCPU was set a certain way and Set on Boot was checked, that could explain the cyclical rebooting.
With the above settings, I get snappy response @ 1000 MH for anything that I'm running, but while my Droid lounges around, it only sips the juice. I'm at 60% battery power remaining after 13 1/2 hours since she was unplugged this morning. I'm usually at 30 or 40 by now. I would say I've been playing with it a tiny bit more than usual today just checking out the speed & responsiveness of different apps. It is definitely a little zippier. Not 81.82% zippier, mind you, but a definite improvement.
If it weren't for SetCPU's ability to do profile management of the CPU speed, the trade off in power usage I would expect from OCing to 1000 MH probably wouldn't be worth it to me.
|