• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Evo Rebooting on its own

It is definitely the overheating of the battery. Basically I can not play a game for too long because it will reboot every time after it reaches over 104 degrees. Should I take it to the Sprint to have it checked, or is this something that happens to all the phones. Can anyone else do a test and see if it happens to you?
 
It is definitely the overheating of the battery. Basically I can not play a game for too long because it will reboot every time after it reaches over 104 degrees. Should I take it to the Sprint to have it checked, or is this something that happens to all the phones. Can anyone else do a test and see if it happens to you?

Read back in this very thread. We have been trying to nail down the cause, but there are varying reports. Some phones reboot only when the GPS is on. Others reboot when they are in a weak signal area, requiring the phone to emit higher power which = higher current drain from the battery. Others reboot for no friggin reason that they could determine. It's not one set cause.
 
It is definitely the overheating of the battery. Basically I can not play a game for too long because it will reboot every time after it reaches over 104 degrees. Should I take it to the Sprint to have it checked, or is this something that happens to all the phones. Can anyone else do a test and see if it happens to you?

I think it's reasonable for any portable electronics device to have a thermal protection circuit - bad things happen if a battery is allowed to overheat - potentially, very bad.

The question I would have is - in your personal case - what's driving the CPU so very hard (the large SoC processor is the main heat generator) that you would experience this sort of condition?

It might be helpful (no guarantees, I'm just following the engineering side of my nose) if you could also please share:
  • How much time are we talking for too long?
  • A particular game, all games or a class of games? And if some class of games is the answer, can you give a brief description of the genre (I'm not a gamer)?
  • Were you also playing media or anything while the game was running the phone into that regime, or this is null question because the game includes some lively sound already?
  • Ambient environment - phone's being used in a reasonable environment?
  • When the temp hits 104 or so - or - after you've played the game a while, is the touchscreen equally warm or are there hotspots? If hotspots, I'm attaching a link to pictures of your Evo's internals so you can refer to a specific functional block.

HTC Evo 4G Teardown - Page 2 - iFixit

Refer to Step 13 - for the accompanying picture, the bottom of the phone is at the right of photo and that circuit view is what lays underneath the touch screen. The Snapdragon is outlined in yellow.

Sorry to ask 80 questions, I'm hoping additional info can help narrow to a specific direction, in your personal case.
 
I for one do not believe it is the battery over heating. I have used my EVO with multiple apps running, browsing the Internet, using the GPS, streaming Pandora and texting and never had a reboot. The only time mine has rebooted is the combination of the GPS and talking on the phone and this has been consistent. It's been doing this for months and that is the only combination that has triggered a reboot.
 
I for one do not believe it is the battery over heating. I have used my EVO with multiple apps running, browsing the Internet, using the GPS, streaming Pandora and texting and never had a reboot. The only time mine has rebooted is the combination of the GPS and talking on the phone and this has been consistent. It's been doing this for months and that is the only combination that has triggered a reboot.

For your use case, yes?

I think we have multiple paths to failure.

Have you tried the GPSCLRX fix?
 
For your use case, yes?

I think we have multiple paths to failure.

Have you tried the GPSCLRX fix?

I called support today and was told that using this method has worked in some cases but it also has caused problems in functionality in some 25 other areas. I asked what areas it has caused problems and was told that was HTC proprietary information and could not be disclosed. The rep offered to give me the code but said the account would be noted and that if I had future problems in one of these areas there would be no support from Sprint or HTC.

Sounds fishy to me but I declined to accept the code until I could get some more feedback. Thanks in advance for any information that can be added to this.
 
I called support today and was told that using this method has worked in some cases but it also has caused problems in functionality in some 25 other areas. I asked what areas it has caused problems and was told that was HTC proprietary information and could not be disclosed. The rep offered to give me the code but said the account would be noted and that if I had future problems in one of these areas there would be no support from Sprint or HTC.

Sounds fishy to me but I declined to accept the code until I could get some more feedback. Thanks in advance for any information that can be added to this.

WOW.

I'm astounded.

Presuming that this is Sprint telling you this, I'd suggest you confirm this with HTC.

I was out for a while, maybe I missed it, but I hadn't seen such info before.

And given that this is repeated about a bazillion times on Sprint's forums with no record I found (I looked the other day when this was alleged) of Sprint correcting the info - and they do correct bad info on their own forums.

Sounds extremely fishy.

Firmware tend to be highly deterministic.
 
I been working with the HTC techs and they called me today and said that they put out a new update for this problem So every please update your phone and lets see if they got it right
 
I been working with the HTC techs and they called me today and said that they put out a new update for this problem So every please update your phone and lets see if they got it right


which update would this be?

damn phone just rebooted twice this morning in the matter of minutes when trying to reply to a text.

this crap is getting old very fast lol
 
I cannot stress the importance of this:

When your phone updates, if all goes well, you're in heaven. If an update goes bad, you're in hell.

I strongly advise performing a backup, then doing the update, then clearing your caches with a hard reset, then a restore - instructions at http://androidforums.com/evo-4g-support-troubleshooting/141369-how-fix-froyo.html

ESPECIALLY when they're claiming to fix stability issues.

I've seen it too many times, have had mine since launch+2_days
 
Installing on my phone as we speak. I will report back if my phone reboots, i can go to specific websites and play games that make it reboot.
 
Welcome to the forums.

Just a hint - on any maintenance upgrade, clear your browser cache.

Lots of update/browser problems vaporize with that step.

If your game accesses any video/animated help screens and you end up in outer space instead, you'll have to reboot your phone (usually just power off/on) - and yes, clear the browser cache, it's not unusual to see these things tie together. (And that's on the game devs, not Android, ok.)
 
Thank you for the warm welcome. As sad as it is to say this update was of no help to my problem, i barely got into the browser when my phone rebooted itself, its done it several times since. Guess a new phone is due,seems its the only fix.
 
I'm also surprised at the lack of anyone reporting that Sprint has "reprovisioned" their phones.

At least one user here, Rangergrrl, had patiently tried all the right stuff including numerous factory resets. Being persistent, she found just the right tech at Sprint - who performed this task, and her problems disappeared.

Maybe somebuddy knowledgeable can tell us what "reprovisioning" is - all I know is that it's a software/firmware something, and solved a problem that a factory reset could not.

Saved her from unnecessarily trading in good hardware.

Just tossing this one out there for you.


Sorry all I haven't been on much in the past while...because my phone has been running flawlessly! Anyway what EarlyMon says is true. I did all the guides all the steps to no avail until I talked to the right Sprint rep and then no problems since. I did start to have some random reboots about 1.5 months ago. I couldn't track down what was going on and had ordered some spare batteries for a trip...needless to say with the new batteries my phone is no longer rebooting. If I put the stock one back in..reboots start happening again..and if that stock battery gets put into the other EVO in the house it starts rebooting as well.
 
So far with the new update my phone hasnt rebooted but I only have made 3 calls with a gps program on and one hour long call with it off.. Guess we will see
 
EarlyMon

Downloaded alogcat and found this to be in red, alot, any help would be greatly appreciated...

E/lights ( 98):write ok string=0,len=1
" 3

Thanks for your time
 
Welcome to the forums!

We see that error come and go (mostly stay) on a lot of users phones and haven't correlated it to any failure mechanisms.

As near as any of us have been able to gather, it's tied to some control of the LEDs.

Basically, it appears to be saying that some routine is returning "a nothing" instead of some coordinated response as expected.

I always suspected the Flashlight app because this one didn't seem to show up and really dominate until we all upgraded to Froyo (Flashlight came with Froyo, btw) - but - that's just a best guess.

In any case - this is what a software guy would call a nuisance error. It's absolutely wrong, so it's an error in red in syslog, but it doesn't hurt anything or tie to anything hurt.
 
There have been many discussions about the EVO rebooting under various circumstances. I have experienced this multiple times on my EVO as well (hardware version 3). It appears that I've resolved 2 of the conditions that have caused these reboots.

In the first condition, my phone would reboot every time I'd turn off and exit my Toyota Venza. Obviously this is a bluetooth issue. However, since it used to work without a problem, it can't be solely a hardware issue. The fix for this turned out to be fairly well publicized by Vlingo. While the problem is associated with the use of Vlingo, it appears it isn't caused by Vlingo. Vlingo brings out a flaw in Android 2.2 which is documented by Google and appears to be have been fixed in Android v2.2.1, which of course we don't have on the EVO. In Vlingo, under the Advanced Settings, there is an option to "listen over bluetooth." If this option is checked, my EVO will reboot every single time I turn my Toyota Venza off and the phone disconnects from the Toyota bluetooth. Every time. If you turn off this setting in Vlingo, the problem goes away.

The second condition appeared much more randomly but over time I figured out a pattern. While driving, if I received a call that I answered over bluetooth, at some point into the conversation the phone would immediately reboot. It wasn't immediately, as I could regularly complete short phone calls without issue. The reboot would occur several minutes into the phone call. However, on some occasions, I could carry on long conversations without it rebooting also. Over time, I determined that I had to be running Google Navigation in order to experience the reboot problem. I don't think this is related to the Google Navigation software, but rather, I'd guess it is related to the use of the GPS itself. Once I suspected that, I could reproduce that every time I was using the GPS and received a call over bluetooth, several minutes into the call the phone would reboot. This one was a little tougher to solve.

There is a great app for Android called Tasker. I have no connection to app at all other than being a satisfied customer. Tasker lets you do some amazing customization and "macros" on your phone. To solve the reboot problem above, I used Tasker and did the following. I monitored the offhook status of the phone. When the phone goes offhook, I disable the GPS and close Google Navigation. When the phone offhook condition clears, I then restart the GPS and open Google Navigation. Google Navigation picks up where I left off. Since I've set this up in Tasker, I've had no reboots at all.

Perhaps someone at Sprint, HTC or Google can use this to get this reboot problem solved.
 
I never had the reboot issue. Even when paired to a bluetooth device. But I'm glad HTC has resolved the issue. Just goes to show that HTC is much better than other cellphone manufacturers out there. Cheers to them!
 
hmm.. I don't have any reboot issues either.

I have no idea what vlingo is but my evo is on android 2.2.1. I am not on the latest software from sprint yet either. I'm still on the 3.30 from hardware version 4. have you gotten the latest update to software 3.70 with the blockbuster app and swype? I decided to hold off for a bit. I don't think they will announce 2.2.1 as the major portion of the update as it is still froyo..

your second reboot issue sounds like a memory issue and not gps to be honest. but is probably fixed by killing gps due to the amount of system ram it takes up.

I would suggest installing system panel lite from the market so you can see your memory usage. you may find an app or 2 you never really use that holds some system memory even when not in use or not even applied to one of your home screens. you can then decide you may be able to uninstall something you never use. with system panel lite you can view what apps are holding memory (even when inactive) and kill any or all inactive or active apps. the paid version will give you the ability to monitor apps that are running for battery drain issues.

you may consider using this to also kill things like market and web browser as these will hold memory for recently viewed pages.

the only reboot issue I know of on the evo is when the memory is tapped out and you try to use the phone for something...
 
Back
Top Bottom