-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help DROID Incredible random restart/reboot problem
- Thread starter OhScar
- Start date
-
- Tags
- htc droid incredible
I had mine replaced last month for that. According to the store rep it's the screen overheating and was a problem on early run phones.
zerocool79346
Android Expert
Seems to be extremely common with AMOLEDs for sure, that rep knew what he was talking about. The problem now is, Verizon doesn't fix the issue (I think because they don't spend enough time on the phone after they get them back to see the problem occur), so quite a few of their "certified like new" Incs have this problem. I managed to get 2 in a matter of 5 days that had it before I got an SLCD that works like a charm.
I was worried about that with my replacement (always a risk with intermittent problems with subtle causes), but do far so good.
Had mine since day one it was released as well. Had a few random reboots even then. Then I cracked my glass and AMOLED - and I didn't have a warranty - doh! Replaced the AMOLED screen and glass and it was o.k. for a little bit then I quickly had crazy reboot issues, plus delays on voice calls, issues with the proximity sensor, programs crashing and force closing, overheating, you name it. Almost wanted to chuck the phone in the trash and pay full price for something else. Before giving up I rooted my phone and it's been working perfectly ever since. Go figure?
stehl16917
Lurker
I've had my Dinc since June last year. Would have a reboot every once in a great while. In the last couple months it has gotten progressively worse. Can't go more than 5 min. on google maps navigator with the stand alone gps on without it rebooting. Try to video record my daughters basketball game, and it reboots. Run radiotime app for more than 15 min. and it reboots. Seems like anything that tasks the processor too much causes it. Haven't noticed any correlation to signal strength when it occurs. Never happens when just using the phone or tethering it to my PC. Verizon sent me a replacement. Haven't got it out yet.
Will let you know how things work out
Will let you know how things work out
Crazy reboots here too. Had phone since summer 2010. This just started about a week or two ago. I had one episode of the infinite rebooting, which I was able to stop by removing the battery and leaving it out for a while before cranking it back up. This happened again yesterday, only this time I lost all my contacts (fortunately I was able to re-sync w/ my Outlook and get them back), and several apps I had installed no longer work. It also changed all my ringtones and notification sounds. The rebooting is still happening a lot today, but it doesn't always keep rebooting over and over. This is NOT fun.
BlackBombBird
Lurker
I hope that this will help someone. This is my experience, with all the usual disclaimers like YMMV.
I have identified two repeatable scenarios that will crash my Droid Incredible.
The short:
My phone will crash and repeatedly reboot when the temperature reaches about 38-40 degrees C.
My phone (not just the browser) will crash when I use the browser to go to 511.org
The long:
This is how I arrived at these conclusions. A few observations first:
1) The phone rebooting itself is usually an indication that a fatal hardware error has
occurred. As in, some illegal area of memory was accessed, some instruction in the
CPU was invalid, some high priority interrupt from one of the components, etc.. The
phone reboots itself to protect from further catastrophe, because after any of these
things happen, all bets are off.
2) I have found that certain apps that run in the background, which incidentally start
without you wanting them to, and restart when you've manually killed them, and still
start even though you've told them you didn't want them to start up with the phone,
and oh, by the way CANNOT BE UNINSTALLED, will use enough of the CPU to increase
your baseline temperature closer to the failure point. Yes, I'm talking about you, SKYPE
MOBILE! After reading what I just typed, this might be a big DUH fact. Oh well, guess
I'm just venting.
3) I went through all the pain of factory reset and restore. Twice. No resolution whatsoever.
For the heat issue:
* I downloaded an app that would tell me the battery temperature, which for lack of being
able to read a temperature diode on the CPU itself, was a good enough indicator of chip
temperature. For this I chose "Temp + CPU v2" by SanelS because it was free and simple,
and also showed CPU frequency and busy percent. No plug here, just use whatever you
think is useful to you.
* I plugged the phone charger in, and proceeded to use several apps to warm up the phone.
I played Angry Birds, used the GPS, used Latitude and whatever else I could think of. I
switched back and forth between these apps and the home screen so I could see the
temperature rising. When the temperature got to about 37 degrees C, I knew I was close.
A few more birds out of the slingshot, and BOOM! Phone crash. Again and again until I
removed the battery and allowed the phone to cool.
* Next experiment was to get a block of Blue Ice, remove the back cover of the phone
with the battery still in, and place the phone directly on the Blue Ice so that the battery
was in contact. The charger was plugged in. I proceeded to do everything I did before
to get the CPU going and the battery/CPU/phone hot. The temp came down below 20
degrees C and stayed there. I was able to stay in operation for hours with no crashes.
* I then removed the phone from the Blue Ice and snapped the cover back on, repeating
the first experiment. 30 minutes later, BOOM again. Repeated phone crash.
This is as controlled of an experiment as I could come up with to prove that the issue
is heat. I have worked with integrated circuits for 20 years now, and my best guess as
to why some people see this heat issue is because there is a variation in the process by
which chips are created. Basically, all chips, especially CPUs, have limits as to how fast
they can run. If a chip runs at 1GHz, that means that one clock cycle is 1 nanosecond.
A signal must make its way from one place to the next within this nanosecond of time.
If it doesn't make it, this is an unrecoverable scenario in which a hard system reset occurs.
There are three contributing factors as to whether the signal will make it:
1) Voltage. A chip can run faster with higher voltages (but within a margin that would
not destroy the device). You overclockers are well aware of this. I'm pretty sure that
all the smartphones have voltage regulators that bring down the voltage from either
the battery or charger such that the voltage to the components in the phone will never
droop, so this should never be an issue.
2) Temperature. The hotter a chip runs, the harder it is for the internal signals to make
it to their destinations in time.
3) Process. There is a variation in how the silicon of each chip behaves. This has the
effect of some chips failing at lower voltages and/or higher temperatures than another
exact copy of the device. Each chip is supposed to be screened at the factory or
"guaranteed" by design that it will work with certain given operating temperatures and
voltages. Some chips end up being closer to the edge than others as to when they'll
fail (the distribution is a bell curve). Qualcomm, did you EFF up here with the operating
specs?
My wife and I each got Droid Incredibles at the same time. I installed the temperature
monitor on both devices and ran similar experiments. No problem with my wife's phone,
lucky her.
For the 511.org issue:
* Holding the temperature down again with the Blue Ice, simply browsing to 511.org
crashes the phone, although not repeatedly. The same failure occurs when the
temperature is not held down. I find this one more perplexing as I am not a software
guy. I would expect maybe a browser crash, but not the whole phone crashing. Anyone
want to chime in here with theories?
So what to do? I am frustrated with this and have spent countless hours Googling for
solutions that will not void my warranty. Of course, saying that, I'm going to return the
phone to Verizon for a replacement and play my luck. I'll run the same tests on the
new phone and return that one too if I see the same thing. I guess the point of all this
is that the heat factor is DEFINITELY a problem and it is in itself, I believe, a reason to
return the phone.
good luck to all of you, I hope that this post has armed you with more justifications to
get in Verizon's (and HTC's) faces about this issue. I envision an army of us with blocks
of blue ice walking into HTC headquarters with our phones and chargers.
I have identified two repeatable scenarios that will crash my Droid Incredible.
The short:
My phone will crash and repeatedly reboot when the temperature reaches about 38-40 degrees C.
My phone (not just the browser) will crash when I use the browser to go to 511.org
The long:
This is how I arrived at these conclusions. A few observations first:
1) The phone rebooting itself is usually an indication that a fatal hardware error has
occurred. As in, some illegal area of memory was accessed, some instruction in the
CPU was invalid, some high priority interrupt from one of the components, etc.. The
phone reboots itself to protect from further catastrophe, because after any of these
things happen, all bets are off.
2) I have found that certain apps that run in the background, which incidentally start
without you wanting them to, and restart when you've manually killed them, and still
start even though you've told them you didn't want them to start up with the phone,
and oh, by the way CANNOT BE UNINSTALLED, will use enough of the CPU to increase
your baseline temperature closer to the failure point. Yes, I'm talking about you, SKYPE
MOBILE! After reading what I just typed, this might be a big DUH fact. Oh well, guess
I'm just venting.
3) I went through all the pain of factory reset and restore. Twice. No resolution whatsoever.
For the heat issue:
* I downloaded an app that would tell me the battery temperature, which for lack of being
able to read a temperature diode on the CPU itself, was a good enough indicator of chip
temperature. For this I chose "Temp + CPU v2" by SanelS because it was free and simple,
and also showed CPU frequency and busy percent. No plug here, just use whatever you
think is useful to you.
* I plugged the phone charger in, and proceeded to use several apps to warm up the phone.
I played Angry Birds, used the GPS, used Latitude and whatever else I could think of. I
switched back and forth between these apps and the home screen so I could see the
temperature rising. When the temperature got to about 37 degrees C, I knew I was close.
A few more birds out of the slingshot, and BOOM! Phone crash. Again and again until I
removed the battery and allowed the phone to cool.
* Next experiment was to get a block of Blue Ice, remove the back cover of the phone
with the battery still in, and place the phone directly on the Blue Ice so that the battery
was in contact. The charger was plugged in. I proceeded to do everything I did before
to get the CPU going and the battery/CPU/phone hot. The temp came down below 20
degrees C and stayed there. I was able to stay in operation for hours with no crashes.
* I then removed the phone from the Blue Ice and snapped the cover back on, repeating
the first experiment. 30 minutes later, BOOM again. Repeated phone crash.
This is as controlled of an experiment as I could come up with to prove that the issue
is heat. I have worked with integrated circuits for 20 years now, and my best guess as
to why some people see this heat issue is because there is a variation in the process by
which chips are created. Basically, all chips, especially CPUs, have limits as to how fast
they can run. If a chip runs at 1GHz, that means that one clock cycle is 1 nanosecond.
A signal must make its way from one place to the next within this nanosecond of time.
If it doesn't make it, this is an unrecoverable scenario in which a hard system reset occurs.
There are three contributing factors as to whether the signal will make it:
1) Voltage. A chip can run faster with higher voltages (but within a margin that would
not destroy the device). You overclockers are well aware of this. I'm pretty sure that
all the smartphones have voltage regulators that bring down the voltage from either
the battery or charger such that the voltage to the components in the phone will never
droop, so this should never be an issue.
2) Temperature. The hotter a chip runs, the harder it is for the internal signals to make
it to their destinations in time.
3) Process. There is a variation in how the silicon of each chip behaves. This has the
effect of some chips failing at lower voltages and/or higher temperatures than another
exact copy of the device. Each chip is supposed to be screened at the factory or
"guaranteed" by design that it will work with certain given operating temperatures and
voltages. Some chips end up being closer to the edge than others as to when they'll
fail (the distribution is a bell curve). Qualcomm, did you EFF up here with the operating
specs?
My wife and I each got Droid Incredibles at the same time. I installed the temperature
monitor on both devices and ran similar experiments. No problem with my wife's phone,
lucky her.
For the 511.org issue:
* Holding the temperature down again with the Blue Ice, simply browsing to 511.org
crashes the phone, although not repeatedly. The same failure occurs when the
temperature is not held down. I find this one more perplexing as I am not a software
guy. I would expect maybe a browser crash, but not the whole phone crashing. Anyone
want to chime in here with theories?
So what to do? I am frustrated with this and have spent countless hours Googling for
solutions that will not void my warranty. Of course, saying that, I'm going to return the
phone to Verizon for a replacement and play my luck. I'll run the same tests on the
new phone and return that one too if I see the same thing. I guess the point of all this
is that the heat factor is DEFINITELY a problem and it is in itself, I believe, a reason to
return the phone.
good luck to all of you, I hope that this post has armed you with more justifications to
get in Verizon's (and HTC's) faces about this issue. I envision an army of us with blocks
of blue ice walking into HTC headquarters with our phones and chargers.
So it has been almost 4 months since I found this post and contributed my thoughts on what I believed the problem may have been. I just want to give an update in case anyone else has been going through the same nonsense. Long story short; I really don't think it's a heat issue although excessive heat may be a contributing factor.
I am on my THIRD HTC incredible. I have had the phone replaced via warranty with a factory 'refurbished' incredible twice. This last replacement I just received less than an hour ago. I also received a new battery from Verizon because the CSR thought it might have been a bad battery issue. I put in the battery, turned the phone on, programmed the phone. The phone rebooted. I opened a web browser, went to lastpass.com and the phone rebooted itself. After the reboot I tried the same exact thing... boom. reboot. This is on a completely stock from the factory, Incredible. I think this is solid evidence that there is an ongoing issue with this hardware model and not a "bad app". This also disproves heat as being the culprit as the phone was room temperature.
I just got off the phone with the CSR for the third time. They agreed to send me a brand new Incredible (my FOURTH!) -->(not refurbished) overnight with Saturday shipping.
I really do like this phone... when it's working. I truly hope the replacement they send me does not have the same issue.
I am on my THIRD HTC incredible. I have had the phone replaced via warranty with a factory 'refurbished' incredible twice. This last replacement I just received less than an hour ago. I also received a new battery from Verizon because the CSR thought it might have been a bad battery issue. I put in the battery, turned the phone on, programmed the phone. The phone rebooted. I opened a web browser, went to lastpass.com and the phone rebooted itself. After the reboot I tried the same exact thing... boom. reboot. This is on a completely stock from the factory, Incredible. I think this is solid evidence that there is an ongoing issue with this hardware model and not a "bad app". This also disproves heat as being the culprit as the phone was room temperature.
I just got off the phone with the CSR for the third time. They agreed to send me a brand new Incredible (my FOURTH!) -->(not refurbished) overnight with Saturday shipping.
I really do like this phone... when it's working. I truly hope the replacement they send me does not have the same issue.
ned4spd8874
Android Enthusiast
Rooting my phone seems to have fixed the problem. Well, for the most part. It's only rebooted on me maybe 2 times since rooting a couple months ago. I can live with random reboots every month or so.
Nick The Great
Well-Known Member
I got a new replacement Inc and it's been good. I have the same apps, go to the same sites, and maintain the same charging regimen.
I still worry about this from time to time though.
I still worry about this from time to time though.
When I first started having this issue I also rooted. I installed cyanogen 6(? I think that was the latest release at the time) and everything seemed to be good for at least a few days. After a while I started have the same problem.
I suppose everyone's threshold for aggravation is different, but I'm at my wits end. I bought an Android 'smart' phone to use the 'smart' features like the browser, maps, and other applications. It's almost guaranteed that when I need to use the device to look up some information whether it's navigation, financial, or work related it never fails to fail. that, to me, is extremely frustrating.
Hopefully this is just an issue with a particular batch of incredibles. My wife also owns one and has had it for a couple of months without this issue. Than again, she rarely uses 3G data, navigation or third party applications.
After I receive the new one tomorrow I'll report back with any more problems.
ByteCrawler
Lurker
This thread appears to be dead. Has anyone found a solution to this? Some of what I'm experiencing sounds like what everyone else here has seen. But the difference is that my phone only reboots randomly (and often) in only one place - the airport in Calgary. I travel a lot and have never had a problem with reboots. In Calgary, the phone will reboot randomly but on average every 5 minutes or so; more often if I use anything data related. The only way to stop it is to turn off 3G, Wireless, and all location services. Then at least I can make calls. I think 3G might be enough, but I haven't had the time or inclination to sit around the airport and experiment.
My DINC which worked for several months with no issues has started rebooting as well. Usually when I try to use google maps. My GPS is always on but when I access maps I will find that it has no GPS tracking signal. Checking with a third party GPS status app I find no sats are detected. Eventually while waiting for a GPS lock the phone starts going into a deathloop and reboots 4 or 5 times before starting then it usually reboots again within a few min of any use. Eventually it calms down. The death loops almost always happen when i try to use the GPS, after getting a GPS lock and settling things down again the GPS maps works fine and the phone becomes stable. Every time I have had this issue it was while the phone was trying to lock on GPS but could not.
Nick The Great
Well-Known Member
My Dinc first started the Death Loop while in GPS Nav. In all fairness, I did have it setting in the sun on a 90 degree summer day. So it could have been heat related.
But after that fateful day, it'd do it just when browsing the web. MY new one doesn't have that problem. Though I haven't really used it all that much as GPS Navigator. Kinda afraid to!
But after that fateful day, it'd do it just when browsing the web. MY new one doesn't have that problem. Though I haven't really used it all that much as GPS Navigator. Kinda afraid to!
cgrella
Lurker
My first death loop was also while running a GPS tester app (as I mentioned in my above post), but during the winter. All occurrences since have been while web browsing, texting ... the simplest things. I'm still having problems. All the steps I mentioned above simply mitigate the problem, they don't really solve it. And since my post, I've tried formatting the SD card then immediately the phone storage then immediately a factory reset, and then NOT reinstalling any of my apps, just using the web browser and texting... The phone still heats up and shuts down (and not necessarily in that order, but always together). And I never use GPS on this phone anymore, or anything else that's going to be resource-intensive, because I know it's going to blow after about 5 minutes, and I'm pulling it apart and putting the battery in the freezer again.
Again, my phone is completely stock, unrooted, and not a refurb.
There is a design flaw with this phone, and it is degenerative. Once your DINC starts death-looping, it's going to be more prone to doing it more often. I've been waiting this out for awhile in the hopes that a software update would come down the pike and fix it, or someone would figure out the "golden pill" solution, or HTC would issue a recall, but I'm tired of paying for a phone that basically doesn't work.
I had to ask my wife for my old TomTom back so I would have some kind of GPS in the car again. This is ridiculous.
And I have a friend with a Motorola Droid 2 who is having the same problem!?! So is it an Android problem? Should I just get an iPhone already??
Again, my phone is completely stock, unrooted, and not a refurb.
There is a design flaw with this phone, and it is degenerative. Once your DINC starts death-looping, it's going to be more prone to doing it more often. I've been waiting this out for awhile in the hopes that a software update would come down the pike and fix it, or someone would figure out the "golden pill" solution, or HTC would issue a recall, but I'm tired of paying for a phone that basically doesn't work.
I had to ask my wife for my old TomTom back so I would have some kind of GPS in the car again. This is ridiculous.
And I have a friend with a Motorola Droid 2 who is having the same problem!?! So is it an Android problem? Should I just get an iPhone already??
Agree with all above.
I don't know what exactly happened to trigger this, but my random reboots are suddenly a big issue. Once phone started doing it's first loop about 1 month ago, it's been getting worse and worse.
Even my girlfriend commented last night, "It's rebooted 3x in last 15 minutes, that's unacceptable."
The BIG difference is now the boot loops. During my first 8 months or so, I would have just random restart here and there, no loops. No biggie. Now I'm getting boot loops almost everyday if I use phone long enough. This was never an issue before.
No rhyme or reason for restarts. Won't add much that hasn't already been said above. Hot or cold, mainly hot though. GPS, etc. etc.. I'm completely stock, cut down to basic apps, wiped phone multiple times. Even now. I wipe 2 days ago, and still looping.
I can stand occassional restarts, but constant battery pulls?
Big problem.
I don't know what exactly happened to trigger this, but my random reboots are suddenly a big issue. Once phone started doing it's first loop about 1 month ago, it's been getting worse and worse.
Even my girlfriend commented last night, "It's rebooted 3x in last 15 minutes, that's unacceptable."
The BIG difference is now the boot loops. During my first 8 months or so, I would have just random restart here and there, no loops. No biggie. Now I'm getting boot loops almost everyday if I use phone long enough. This was never an issue before.
No rhyme or reason for restarts. Won't add much that hasn't already been said above. Hot or cold, mainly hot though. GPS, etc. etc.. I'm completely stock, cut down to basic apps, wiped phone multiple times. Even now. I wipe 2 days ago, and still looping.
I can stand occassional restarts, but constant battery pulls?
Big problem.
GARY24NASCAR
Lurker
Unfortunately, I am another victim of this constant reboot loop. Usually occurs when GPS navigation is on or Pandora app. Sometimes with nothing extra running I'll notice it occurring on it's own.
No task killers. No much for other apps to try and keep processor working less...doesn't matter.
This thread needs to keep open. I will be heading to the Verizon store this week. The features I like about the phone I am afraid to use because of this problem. I usually just yank the battery and, naturally, the cycle stops. All ready tried factory reset with no luck. It does appear that some chip is over used and over heating but just my 2 cents.
Should have gotten the Droid X or Iphone. I don't have time for fighting Verizon or go through 5 phones. Actually, I am out of warranty (bought in July 10 with no extended warranty). I hate when encountering these types of situations where the company (Verizon in this case) refuses to admit a defect or flaw in a product they sell. They should own up to the issue, do a recall, provide comporable replacements...then take their losses to HTC and bill them. Rediculous! Customer service and employee run around of "We don't know of any issues with that type of problem you are describing" is unacceptable.
No task killers. No much for other apps to try and keep processor working less...doesn't matter.
This thread needs to keep open. I will be heading to the Verizon store this week. The features I like about the phone I am afraid to use because of this problem. I usually just yank the battery and, naturally, the cycle stops. All ready tried factory reset with no luck. It does appear that some chip is over used and over heating but just my 2 cents.
Should have gotten the Droid X or Iphone. I don't have time for fighting Verizon or go through 5 phones. Actually, I am out of warranty (bought in July 10 with no extended warranty). I hate when encountering these types of situations where the company (Verizon in this case) refuses to admit a defect or flaw in a product they sell. They should own up to the issue, do a recall, provide comporable replacements...then take their losses to HTC and bill them. Rediculous! Customer service and employee run around of "We don't know of any issues with that type of problem you are describing" is unacceptable.
BlackBombBird
Lurker
This is a follow-up to my last post. I did end up going to the Verizon store about a month ago, rebooting phone in hand. I started to show the salesperson the "511.org" reboot problem. He watched it happen and immediately said "I'm going to give you a warranty replacement."
"Don't you want to see the other way it reboots?" I said.
"Nope."
"Have you seen the overheating problem before with the Droid Incredibles?"
"Yup."
From there, I had replacement phone in hand in a few days, and have had this new one for about a month. I am happy to report that I have no problems with the overheating reboot whatsoever. The 511.org reboot still happens, but it's not a problem if I simply don't go to that page. I have installed Temp+CPU v2 and watched the battery temperature exceed 50 degrees C and keep on working. No other apps have crashed the phone.
So, I don't know what the lesson is here, except that you should definitely keep trying with Verizon until you get one that works. One other note is that the refurb replacement I received has a green "void" sticker over one of the corner screws inside the case, whereas the defective one had a red one. Don't know if that really means anything.
Good luck!
"Don't you want to see the other way it reboots?" I said.
"Nope."
"Have you seen the overheating problem before with the Droid Incredibles?"
"Yup."
From there, I had replacement phone in hand in a few days, and have had this new one for about a month. I am happy to report that I have no problems with the overheating reboot whatsoever. The 511.org reboot still happens, but it's not a problem if I simply don't go to that page. I have installed Temp+CPU v2 and watched the battery temperature exceed 50 degrees C and keep on working. No other apps have crashed the phone.
So, I don't know what the lesson is here, except that you should definitely keep trying with Verizon until you get one that works. One other note is that the refurb replacement I received has a green "void" sticker over one of the corner screws inside the case, whereas the defective one had a red one. Don't know if that really means anything.
Good luck!
BlackBombBird
Lurker
All:
Please see my post and subsequent follow-up in this thread:
http://androidforums.com/incredible...232398-repeatedly-restarting.html#post2292617
I hope it will be of some help to you.
BBB
Please see my post and subsequent follow-up in this thread:
http://androidforums.com/incredible...232398-repeatedly-restarting.html#post2292617
I hope it will be of some help to you.
BBB
Nick The Great
Well-Known Member
I saw this from the other thread. Interesting 'test' results though.
I had similar issues and got a replacement phone. Long story short, the guy at the store offered to factory reset it, and it got into a hot loop of death on the spot. So luckily I got a brand new one on the spot.
This was over the summer, and he hadn't ever heard of this before. And he personally had a DInc.
I had similar issues and got a replacement phone. Long story short, the guy at the store offered to factory reset it, and it got into a hot loop of death on the spot. So luckily I got a brand new one on the spot.
This was over the summer, and he hadn't ever heard of this before. And he personally had a DInc.
cgrella
Lurker
Took my rebooting phone into the Verizon Store, described the problem and they shipped me out a replacement, which works just fine.
The new phone looks nearly identical. The only thing different is that my if I held my old phone horizontally and looked across it I could see a grid of tiny dots across the surface. On my new phone, I don't. On my co-workers phones (which have never had this problem) theirs don't have the grid either.
So maybe the hardware profile was altered at one point and the old ones have the issue? I don't know.
My new phone gets just as warm as my old one did, it just keeps working instead of shutting down. I don't think the bad phones are overheating, I just think they get to a state where they can't handle normal operating temperatures anymore.
Bottom line, if your phone is rebooting like this, take it back to the store! I wish I'd done it sooner. All these threads nearly scared me out of doing that. At last, my Incredible is incredible again!
The new phone looks nearly identical. The only thing different is that my if I held my old phone horizontally and looked across it I could see a grid of tiny dots across the surface. On my new phone, I don't. On my co-workers phones (which have never had this problem) theirs don't have the grid either.
So maybe the hardware profile was altered at one point and the old ones have the issue? I don't know.
My new phone gets just as warm as my old one did, it just keeps working instead of shutting down. I don't think the bad phones are overheating, I just think they get to a state where they can't handle normal operating temperatures anymore.
Bottom line, if your phone is rebooting like this, take it back to the store! I wish I'd done it sooner. All these threads nearly scared me out of doing that. At last, my Incredible is incredible again!
Another here with the random reboot & continuous reboot problem on the HTC Incredible. Purchased mine when they first came out and from day 1 it had the random reboot problem. It would reboot even just sitting on the desk not being used. At first the reboot was every now and then, but eventually got up to having a dozen or more (noticed) each day. Last week it fell into the continuous reboot loop with the only way to stop it was pull the battery. Then sometimes it would recover, but would fall into the reboot loop within an hour. Took phone into the Verizon Store while it was in the loop and they did a factory reset (I already had tried that, but procedures