Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

Does anybody have issues with push/exchange at 19MHz standby?

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

I've been running 1.3 for a day now and have mine set to only clock down on standby to 19mhz. I could be my imagination but.. it seems like my emails didn't arrive in my inbox until a second or two after I turned the power on.. like the push mail didn't work while the cpu was slowed down.

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

I've had this exact same issue. Push emails seem to arrive later.

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

That explains why my standby battery life seemed insane with 1.3 and 19MHz in standby: push just wasn't working.

But I'm have a problem even at 61mhz now. Something is messed up. Scrolling through TF3D was choppy. It should be at 528mhz when active like that. I have uninstalled and reinstalled several times but something got broken I think...1.0 seems to work ok at 61mhz. Maybe something broke with the service-ness of 1.3.

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

Can anyone who is using 1.3 and is seeing positive results, please tell us what settings you are using? Thanks

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

It's working well for me. But I turned off all push email to save battery life before I even switched to 1.3. Instant email is not a must have for me, so manual checking will do.

My settings:
At boot - 384
After system idle - unchecked
On backlight off - 245.76
On suspend - 19.2
Voltage is auto for all

Using versions 1.0 and 1.2 I was unable to answer an incoming call with the phone at anything less than 81.92 in standby. Now the phone rings just as quickly at 19.2 in standby as it does when its active. Version 1.3 is the best of the bunch for me so far.

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

Thanks!...ill give these settings a try

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

1.0 works the best for me. I can answer the phone at 61mhz in standby, but not 19. 1.3 allowed me to answer calls at 19mhz standby, but as I stated before, it broke my push e-mail and also really started to make the phone act funny, so I am back to 1.0 using 528/256/122/61 with stable results (and the occasional screen corruption on resume).

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

Tried 1.3 and 1.0 in MightyROM 5 (WM6.5). Like on the stock rom, 1.3 broke push, even at 61mhz, and 1.0 seemed to work best. However I decided I didn't want it and tried to uninstall it. That failed. Then I deleted a bunch of Wei registry keys....and now it won't boot. Looks like hard reset time. Yay.

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

hmm, that sucks it breaks push email. I didn't even notice that.

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

I ended up getting it back up to reinstall 1.0, which restored the registry keys. It seems to be working fine now, except I can't get rid of it on MR5. It must have been running at 19mhz. It was AWFUL. Like 10 minutes to get to a state where I could try reinstalling the program (and that was painful to watch).

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

anyone getting problems with bluetooth automatically disconnecting because it's trying to cut the processing speed? it seems like when the phone goes into standby, the bluetooth would cut off. WEIRD

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

Does does this overclock or just underclock?

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

just underclock. It didn't save me any battery power, even though the phone was slower. YMMV

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

So I read all 22 pages of this thread and decide to dl 1.3. After I accept conditions and atart the dl the progress bar shows hardly any progress but there's a check mark indicating that it's done. I go through total comm to unzip and it says there are 0 bytes in the file. I would love to try this out. What gives?

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

try downloading with another browser or the pc

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

Been running 1.3 for a few weeks now without any problems. It does seem to impact battery life overall, so I've kept it going. If it gains me 1 hour a day on the Touch Pro's already short battery life, I'm all about it. :)

Only thing I've noticed that's wierd (and I'm assuming has to do with the cut down clock speeds) is that when I'm at my sisters house (she's on the edge of Sprints coverage) it kicks into roaming a lot when it's suspended and kicks the backlight on. My sister's touch pro did this constantly with the underclocking turned on. Now that it's off she doesn't have the issue.

Re: [5-10] nueDynamicClock 1.3 - more bug fixes
 

Dl'ing through PIE worked. Not used to that since I always use Opera. Man thats a clunky browser. Netflix doesnt like my stock Opera either. Tis strange. Thanks again.