Quote:
Originally Posted by lipidfats
I remember him saying they made some changes... that's mainly why I haven't hard reset yet (that and because I didn't have low volume issues and that seemed to be the fix for peeps). I didn't know what changes they made, but when i started putting on apps and whatnot i started to wonder if any changes they made would be reverted if i hard reset the phone. Someone should contact him since almost everyone did the hard reset fix when they received their phone. Now i'm probably not going to hard reset for a while....... lol
My pro doesn't heat up for no reason*
|
I have not done a hard reset but still experience the heat issue, and have from day one (it's something I've learned to live with while I reasearch WHY it gets hot)
Quote:
Originally Posted by ScrapMaker
Sounds like you have a magical Touch Pro. Most of us can't get the phone to charge at all, with use like that, (or much, much less.) So congratulations on your find. Hopefully all the rest of us can get our hands on one like that.
I wish someone would write a test program that takes a TP, with battery at 100%, and then runs calculations, and measures battery % vs time vs heat vs voltage. Then we could compare apples to apples--rather than one objective review after another.
|
What kind of calculations do you want it to run? My battery log prog will keep a complete log of power draw, voltage, and battery temperature. and system events. I modified it to let the unit go to sleep, but my original version keept it in full power mode with the screen off. I could dump in a routine to do some heavy calculations the entire time and put in the option to enable or disable that feature. I have run some of my calculation intensive software while logging, and never see over 230mA of battery draw, (i.e. the application processor/WinMo side seems quite efficent) Where I have seen the heavy battery draw is with the transmitter. Which is why I am conviced that the issue lies in the radio ROM. (Since LG uses the RFT61xx series transmitters on many of their handsets (eg vx8300/8350) without major reported issues)