Quote:
Originally Posted by dkranes
Thanks for the good info in this thread guys!
I am using the latest version of nueDynamicClock without the issues others are reporting. I'm on Copper 6.5 ROM. However my settings are to downclock the cpu permanently to 384 when in use and then go to 122 when on backlight or suspend. I notice that if I set the cpu lower than 122 on backlight or suspend I have trouble answering incoming calls. Always wondered how folks got away with setting it to 19.2 and still be able to answer incoming calls.
Looks like I may have to downgrade my downclocking softare to 1.0, LMAO. I will try that. But for the record, with cpu underclocked to 384 and other settings above I have finally gotten to a point where I'm OK with the battery life. Unfortunately my workplace as well as my home are both in not so great signal areas so the battery problem is something I will likely have to live with.
EDIT: the phone seems to run fine at 384 versus 528...I really don't see a difference, but then I'm not a truly heavy user.
|
With my experience with nuedynamicClock v1.2, it would freeze for almost a minute when coming back from suspend when it was set to 19.2 Mhz, which would make answering calls impossible. v1.0 has none of those issues. It works flawlessly, but does not have program specific CPU clock control.