Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

the settings i used were exactly the same as your screenshot. but i unticked everything later because it was stuttering. i thought that would disable the prog, but i guess not. therefore my soft reset wouldn't boot up the device pass the windows logo. this is probably the cause.

but i will test it once more with more conservative values to see if it stops the stuttering

Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

I did finally get some stutter in wmp and then the phone locked up completely necessitating a soft reset.

Went in and adjusted my values so that each 'step' is about 1/2 the speed of the previous. So it goes 528, 256, 128, 64 (not exactly those numbers).

So far I've had no more issues. Going to be a while before I can tell if it improved battery life though.

Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

i'm setting at 528, 384, 245, 122...
5000ms.

hopefully i don't see any stuttering, but i don't know if this will conserve any battery

Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

I took a look at the WMP issues, looks like the problem is due to the lower priority I get from the power notification queue then using the notifcations from device.exe.

So I could improve performance probably by switching to device.exe, but that would cause it to be uninstallable. So I'll have to take a further look to see if theres a better way to do this.

Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

either way, if you can get the prog to set speed based on program, that would be awesome. if not, then include a section where we can manually input selected programs where it would not allow the speed to override while running

Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

I am trying to wrap my head around this.

Discharge rates
With radio on, backlight on autodim, processor at 528: 157 mA
Radio off, backlight on autodim, processor at 19.2: 157 mA

How is this possible? Using NuePower to monitor discharge rates. I am trying to get my discharge rates as low as possible to maximize battery life. Its so weird. It almost seems like 157 is some artificial low, although I know its not.

Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

Can anyone do a little test on ring delays when the phone is off and underclocked vs. an unmodified Pro?

Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

i noticed that a reboot took about 5 minutes to get to tf3d loading.....radio boot and animation boot was fine, but when it got to the splash screen is when everything seem to hang up, the wait cursor took about 1-3 minutes to appear and when it did it seem to hang again causing an addition 2-3 minutes of boot time. regularly it takes under 25 sec for a full reboot. I had everything according to the picture except on boot was at full 528. Not sure if this has improved battery power consumption or not and all i do have checked is suspend which i placed to 19MHz....but i beleive this is a great thing for these phones and as soon as all the kinks are worked out it has to be a must for every phone. nice work yet again No2

Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

even at these settings, the phone would lock up while streaming on suspended mode. weird.

Re: [4-20] nueDynamicClock - dynamically adjust clock for battery life
 

I'm not sure how accurate that measurement is or if its a timed average. I'm leaning towards an average. Also remember the system is slow at 19.2, so it might take some time for it to update.

i'll take a further look at how suspend should be working and exactly why its locking up. I'm thinking performance profiles (kind of like in desktop windows) in the future...