Impressively horrible battery life

[Garwood71]

I too have read a few threads on battery life. Nueclock sounds promising. Google heres I come.

Originally Posted by mstevens

I can't run a WM 6.5 ROM. One of my main reasons for having this device in the first place is to run a medical program that will (currently) only install and run under 6.1 or earlier. There are 6.1 ROMs I could run, but this is a working device that I need to use most of the day every day. I really can't be beta-testing ROMs. I did try nueROM since it was one of the only custom WM 6.1 non-Rhodium ROMs I could find, but it didn't really seem to offer much. Maybe it's crazy to unlock and not change ROMs, but I unlocked in order to try different radios. Does anyone know of an extremely stable, low-cruft WM 6.1 non-Rhodium ROM that offers substantial battery life advantages over stock?

I'm obsessive about fully closing as many processes as possible. Beam Receive, Bluetooth, and WiFi are always off. The phone radio is off any time I'm at home or notice I have no signal. I avoid using GPS because that just seems to make things worse.

I have read all the battery-saving threads and done nearly all of what was recommended (registry edits, disabling polling apps, etc.) but I'm not really comfortable installing cabs unless I know for certain what changes they make. I've certainly enabled all the power-saving features in Diamond Tweak and Schap's Advanced Configurator.

It's hard to find a good old one... you gotta go way back.

Try DREAM's ROM

http://forum.ppcgeeks.com/showthread.php?t=49338

If you can find 0.7, that's even better - I found that version to be most stable of all. I really enjoyed it, it's the ROM I have had on my phone longer than any other.

Also, I know you've said you have switched, but Telus radio.

[kevm14]

Originally Posted by muyoso

There are so many topics already on here that deal with battery life. I get 2 days with light use out of my Touch Pro, about a day if I am browsing and sending emails constantly. It really depends which programs you are running and how much data you use a day. Here is how I have mine set up.

NueDynamicClock - 528 Mhz when in use, 256 Mhz when screen dims, 19.2 Mhz when backlight off, 19.2 Mhz when suspended.

This saves MASSIVE battery life, with absolutely no delay or slowdown with the phone at all. The phone underclocks itself when not in use, and otherwise its running full speed.


Data disconnect - Set to 1 minute

Are you seriously able to answer calls with these settings? My phone would miss many rings when using the NueDynamic clock because it didn't clock back up to full speed when calls came in. And with the data disconnect, I was flat unable to answer most calls, without NueDynamicClock at all. Why is your phone different? I am still on the stock ROM though, with TF3D.

[jmorton10]

Originally Posted by kevm14

Are you seriously able to answer calls with these settings? My phone would miss many rings when using the NueDynamic clock because it didn't clock back up to full speed when calls came in.

Don't feel bad, mine did the exact same thing.

I don't care how good the battery life is if it kills half the functionality of the phone (a lot of people reported similar problems)

~John

[evilpeople]

One thing about the TPs battery life is that it is highly dependent on how strong your signal is. We live in Overland Park (Sprint World Headquarters) and I can easily get two days I don't surf much and don't make too many calls (currently on MightyROM, but I've used several with similar results).

HOWEVER, if I go into a building or area with poor coverage, my battery life can quickly shrink to a few hours. For example, at the Lake of the Ozarks (where coverage is terrible), I'm happy to get 12 hours out of my battery.

[muyoso]

Originally Posted by jmorton10

Don't feel bad, mine did the exact same thing.

I don't care how good the battery life is if it kills half the functionality of the phone (a lot of people reported similar problems)

~John

I assume that you used the latest version of nuedynamicClock? That is your problem, you need to use the initial v1.0 release. In the nueDynamicClock thread, absolutely nobody has had issues with the first release, when everybody including me has had issues with the v1.2 release. Load up the v1.0 release and try it out. And if you are using S2U2 or a similar program like that, and noticing a slowdown, that is why. S2U2 cannot handle the underclock very well.

[muyoso]

Originally Posted by kevm14

Are you seriously able to answer calls with these settings? My phone would miss many rings when using the NueDynamic clock because it didn't clock back up to full speed when calls came in. And with the data disconnect, I was flat unable to answer most calls, without NueDynamicClock at all. Why is your phone different? I am still on the stock ROM though, with TF3D.

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.

Yes, I can answer all calls that come into me, and my battery life is absolutely fantastic. My phone is at 62% right now, and I took it off of the charger yesterday at 9 am. 26 hours of very light use and its still at 62%. I made and received about a dozen calls yesterday, used data for about half an hour and played some games for about half an hour. Took me countless hours to get my phone to where it is now though.

[dahray02]

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.

Yes, I can answer all calls that come into me, and my battery life is absolutely fantastic. My phone is at 62% right now, and I took it off of the charger yesterday at 9 am. 26 hours of very light use and its still at 62%. I made and received about a dozen calls yesterday, used data for about half an hour and played some games for about half an hour. Took me countless hours to get my phone to where it is now though.

wow, impressive

[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.

[therookielot]

haha i bought a battery off of ebay for 5 bucks. i didn't expect much, it sucks, but it worked well the other night when I was on a drunk walk(using gps) to my friend's house and needed a battery after.

When I bought the battery, I also got my credit card number stole and the person who stole it, use it to buy 2 itunes giftcards. I called capital one and told them I didn't "buy music" ---I don't know if the 2 instances are related, but it sure was a coincidence on a shady transaction.