Quote:
Originally Posted by big3etr
I don't have any of these heat issues. I charge my phone with a couple diffent things. I use the wall charger from my Mogul (charges from 11pm to 5am), the USB cable from my Mogul (charges on my work computer from 730am to 4pm) and a USB cable from my digital camera (charges from my home computer peridoically when I'm home between 5pm and 11pm). I talk ALOT on the phone. most of the time while it's charging. I use BT alot. I don't know if any of you with heating issues use BT or not. I do alot of playing with the phone, internet, and texting.
|
When you say you talk "ALOT," do you mean that you talk for more the 1+ hour at a time? The problem we are having, mostly, is that extended, non-stop use, causes the phone to stop charging.
You clearly do not use the phone much, if your USB cable is enough to charge your phone all day. USB only outputs 500mA, if you're lucky. It's already been shown to use MORE than 1A a lot of the time.
I think the problem with people's experiences/takes on the issues, especially in the polls here, is that there is no consistancy between data and usage. I tried to make an "advanced" poll, so people could to a multiple-choice poll, and we could get a good idea of just how many people are really experiencing these problems. All the other polls are far too basic, and people's answers are not necessarily true to their comments.
For example, on the poll I had going, someone posted that their screen had lowered sensitivity around the edges of their screen, yet they voted that their device was flawless. I think our fight is hopeless, because there are far too many fanboys who will defend the phone, regardless of any condition. People will actively cool their phones, open the keyboard, etc, instead of making HTC or Sprint do something about this.
I am truly convinced that every since Touch Pro ever made (CDMA,) suffers from this same problem. People find tricks/workarounds to solve the issues, or are just lucky, and don't trigger the problem. I don't see how this could be a device-to-device defect. I would bet it's a design defect, or a software design problem.