My EVO overheated

carholic

Member
May 16, 2010
6
0
0
I took it out of my pocket and tried to turn off the ringer but the screen went dead. I put it in my sports bag and 5 minutes later, someone called and it rang. I picked it up but the screen was still dead and I could not answer the call. I put it back in my bag and one hour later, I took it out of the bag. It was too hot to even touch and screen was still dead. I could not restart it so I had to remove the battery. Everything was so hot. I let everything cool down and then installed the battery again. It rebooted and then everything was fine, but baattery was then about 20 % and drained fast for the next hour. I te=ried to charge it in the car but it seemd to charge very slowly.I took it home and charged it for 3 hours before it was fully charged again.

Hope it does not happen again. Still don't know what happened.
 
Sounds like Android locked up into a loop that drew high CPU usage... Sounds like the same issues I had with my Hero.... I really REALLY hope this isn't a common issue with the Evo... I think HTC needs to have a seriously long debug session to their Sense UI to make the code more efficient & eliminate weird lockup up issues.

My guess is that the Sense UI software gets all worked up when the CPU is occupied with voice data connections which have top priority & sends the interface into a weird loop if certain actual android code is executed & things dont happen as fast as HTC's software demands em. This is a software flaw on HTC's part with Sense UI because I've never heard of this similar issue with stock android & stock android phones I've used & owned. Seeing as how all 3 Hero's with 2.1 Sense ui I've owned had the SAME EXACT ISSUE in addition to your evo with 2.1 sense, the only common denominator is Sense UI & I've heard this same issue from others with the Hero. I don't know jack about android programming, but I know LOTS about CPU assembly language & it seams that the Sense UI software is sending an interrupt that is being ignored when the CPU is taking too long getting back to answering Sense UI's request & then Sense ui gets pissed & goes on to a different subroutine while the CPU tries to answer the interrupt while Sense ui has already moved on. This would send the CPU into high mode to answer the interrupt, but sense is moved on & is stuck in a loop because the CPU finally caught up & wants to answer sense ui's interrupt now but since sense moved on it doesnt respond to the interrupt answer. My guess is that since the evo is faster in processing, Sense doesnt have the issue of being ignored & the issue isn't that big of an issue 99% of the time, but it still should be fixed because OBVIOUSLY it can still be an issue in certain circumstances evidenced by your situation.
 
Last edited:
Interesting stuff guys.

My EVO just got stuck in a looping boot sequence and the lower back of the phone was getting really hot.

I popped the battery out, let it cool down, then rebooted the phone. This just happened 5 mins ago.

I think it IS the Sense UI, as I was jumping back and forth through loading themes... looking at one layout... loading up another... and so on. I did about 9 different theme changes, then BOOM.... screen locked reset loop started.
 
Can't we Turn Sense off? I remember seeing this somewhere...

I haven't even Tried being this is my First Android with Sense on it...
I'm happy enjoying the Sense UI Experience

Can anyone comment on how to Turn Sense off?
 
This has happened to me once (and only once). It's happened on rare occasions on other devices, too. One of my Treos used to go into a loop where it would ring forever; that was really annoying when I was on my motorcycle and couldn't take it out of my pocket to turn it off.

Not making excuses, because whether it's in Sense or in Android itself it needs to be found and fixed, but the truth is that ALL software has bugs. Even the stuff controlling NASA missions and cruise missiles. Android and Sense don't seem to be too bad compared to some other systems.
 
So my phone was overheating whenever it had trouble getting a signal for internet (at least from what I could tell.) Then it began to restart whenever it wanted and eventually even started freezing up randomly and I had to physically remove the battery to restart it. I finally was able to exchange it for a new one at Best Buy the other day (I was within the 30 days of my purchase and was put on a waiting list for a phone.) My new phone still gets pretty warm at times but so far no restarting or freezing yet. I have noticed that sometimes it gets hot even when I’m not connected to the internet.

Is this just an issue for all the phones or is it a defect because I find it way too coincidental that both phones I’ve gotten had this problem, and if this is a common thing wouldn’t the constant overheating start to fry some internals? Have we gotten any definitive word from HTC or Sprint like they did with the screen leakage issue?
 

Trending Posts

Forum statistics

Threads
962,007
Messages
6,988,692
Members
3,164,756
Latest member
dustsansee