Impressively horrible battery life

[muyoso]

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.

[YouMayLose]

with Silence9 rom no other tweaks (other than the sprint 1.11 radio) I can go all day and not have to charge my phone till next morning with light use... and by light use I mean 60 to 80 text messages check email once or twice and play on net for maybe 20 to 30 minutes...

[dkranes]

Hmmm...personally I would call your text use moderate, but I agree the rest is very light. How is your signal where you usually use your phone. It seems that being in a poor signal area really kills the battery quickly.

Maybe that's why some folks here report battery life at a day or two and others get only 6-10 hours. I am, unfortunately, in the latter camp. Poor signal and poor battery life. All the tweaking I've done has definitely helped, but it's no match for my old BBerry 8830. I would say on its best day my TP has about 1/3 of the battery life of my old BBerry.

One thing I absolutely LOVED about the BBerry was the ability to schedule the phone to shut down completely and start back up. I had it set to shut off at midnight and then turn on again at 7am M-F and shut down at 3am and start up at 10am on weekends. Why does WinMo not have a setting or app to take care of this? Seems like a HUGE oversight. This alone could reduce the need to charge the phone so much. Frankly I am shocked that this is not included in WinMo 6.5 so far. Perhaps the official release will give us some more goodies (a la Win7 beta versus Win7 release candidate which includes virtual XP mode), but I doubt it.

[bruceo]

Originally Posted by jmorton10

2 days??????

Sorry, but I find that VERY hard to believe. I have three TP's, all running Mighty 4.16 with the same battery tweaks as everybody else, & I don't think I could get two days out of a battery if the phone was in standby with the screen off the whole time.......

I deal with it by having a fully charged spare 1500 Seidio battery in my pocket at all times, & plugging my phone into a ProClip that charges it whenever I am in my truck.

I also have a charging cradle on my desk at work that charges the phone & a spare batt simultaneously.

~John

Yeah I agree. These guys that chime in on battery threads and say days of use are full of crap. No freaking way unless the phone was turned off. Actually HTC Winmo devices are so bad with power management that I would even bet you cant get a battery to last for 24 hours even if you turned the phone totally off.

[ESsprint]

its been 30 hours since i charged my phone. I am on sprint tp and i have been as i am now using it to post this message. running might rom r3born. so go whine about people lying cuz i am loving reading about it at the park right now... oh im at 50% battery right now.

[kevm14]

Originally Posted by muyoso

Again I assume you as well used the most recent nueDynamicClock? Try the v1.0 version. It is stable and works flawlessly. And are you using any sort of S2U2 program on the phone? If you are, that is why you cannot answer most calls, because it doesn't play nice with nuedynamicClock.

Tried 1.0. Seems to work very well! The only issue I really had was boot-up was slow. It was a tad slower to answer the phone but not useless like 1.2 was. I am running 528/256/122/62 or whatever. We'll see what happens tomorrow at work. This could be great.

But I still don't understand the data disconnect one...I could never answer a phone call properly with that one.

[ESsprint]

forgot to mention. i run with wi-fi on most of the time. Not sure if that helps.

[zepsamsung]

I don't recommend all this flashing roms, if it messes up your phone, don't do a claim!!!
I had the same issue and Sprint replaced it under my 30 days or call tech support and explain the issue to them, they should send a new one.

[muyoso]

Originally Posted by bruceo

Yeah I agree. These guys that chime in on battery threads and say days of use are full of crap. No freaking way unless the phone was turned off. Actually HTC Winmo devices are so bad with power management that I would even bet you cant get a battery to last for 24 hours even if you turned the phone totally off.

There are two options.

1) You are not willing to put in the time to customize your device to the point where battery lasts long enough

or

2) You want everything to autoupdate, want data to be constantly used, want to have several programs running when you arent even using your phone and on top of all that you want excellent battery life


You cannot have it all. If you spend a little time, and battery life is your priority, you can EASILY get 40-50 hours out of a charge. If you aren't willing to put in the time to customize your device, don't come on here and claim everyone who is willing is a liar.

[muyoso]

Originally Posted by kevm14

Tried 1.0. Seems to work very well! The only issue I really had was boot-up was slow. It was a tad slower to answer the phone but not useless like 1.2 was. I am running 528/256/122/62 or whatever. We'll see what happens tomorrow at work. This could be great.

But I still don't understand the data disconnect one...I could never answer a phone call properly with that one.

Yea, starting the phone is a little bit annoying. I meant to try and fix this for while. I think that if you change your screen dimming time and making it a little longer it might work well. Testing it now. BTW, i nuedynamicclock at 528/256/19.2/19.2.


EDIT: Went ahead and just disabled the "After system is idle for" setting in nuedynamicclock. I don't think it will make that much of a difference on battery life. It boots up completely normally now.