I have been having a nagging problem w/ my DInc ever since I was stock w/ 2.1.
When I use the GPS w/ Google maps, my phone will randomly reboot.
I've tried various kernels, various 2.2 ROMS, tried underclocking / managing temperatures and continue to be plagued w/ this issue.
My current setup is:
Rooted, S-Off, Virtous ROM 2.6, Adrynalyne's Virtuous Custom Kernel, 2.15.00.07.28 radio
It is rock solid with GPS off. As soon as I enable GPS and start navigating somewhere, it's only a matter of time before it reboots. Sometimes it reboots after 1 minute - other times 20 minutes. No rhyme or reason to the length of time before reboot.
I've been hoping that the latest kernels, radio, etc would alleviate this problem, but I'm about at my wits end and ready to just un-root, go back to stock, and try my luck w/ a replacement from VZW.
Anybody have any troubleshooting tips that I can try before I go the replacement route?
UPDATE: Took phone into VZW while it was doing a reboot. They immediately put in a refurb order for me. Replacement phone has been absolutely rock solid for a few days now. Thanks for your help in convincing me it was a hardware issue.
Idea
margelef said:
Anybody have any troubleshooting tips that I can try before I go the replacement route?
Click to expand...
Click to collapse
What's the temperature of your phone at the point it reboots (or comes out of its reboot).
jdmba said:
What's the temperature of your phone at the point it reboots (or comes out of its reboot).
Click to expand...
Click to collapse
Good question, I've never actually recorded the temperature after the reboot (I obviously can't know what the temp was *before* the reboot)
I have, however, used SetCPU with a profile that should underclock (and throw an event notification) if the phone gets above around 43 degrees celsius. I've never actually gotten that notification, though. So either the phone isn't actually getting that hot, or it's rebooting before SetCPU can kick in and pop up the notification.
I'll GPS on the way home tonight and after the inevitable reboot, I'll take a look at what the temperature reading is.
...
Great. Of course, my question was one of experience and not randomness. I am expecting to hear something back from you along the lines of 43c+. If you are at 47c or 48c then its a no brainer.
Bad radios (not the 2.15.xxx software; the physical hardware) are a documented issue with early early early DINC's. They are faulty and they start trying REAL HARD to get their signal, at which point the DINC overheats and reboots.
I returned my first DINC (I am on #3) as it would superheat to 43c (without being in actual use ... temp would just climb and climb) and then enter a reboot loop.
jdmba said:
Bad radios (not the 2.15.xxx software; the physical hardware) are a documented issue with early early early DINC's. They are faulty and they start trying REAL HARD to get their signal, at which point the DINC overheats and reboots.
I returned my first DINC (I am on #3) as it would superheat to 43c (without being in actual use ... temp would just climb and climb) and then enter a reboot loop.
Click to expand...
Click to collapse
Other than having SetCPU do an "Audible Alert" if it hits a certain temperature, is there any sort of diagnostic logging that I can do to help monitor the temperature?
I have used System Panel to show CPU/usage history, but I have not noticed a spike in the CPU right before the reboots in the history view.
This is a release-day unit, so it would have been in the first batch of DIncs. You reference a documented issue on the early batch of phones...do you have a link to something that I can reference if I take this to VZW for a replacement?
Not any more
At the time when this was big news you could find postings, but no admissions from VZW if that's what you want. I think you overestimate the amount of difficulty VZW is going to give you. Sure, a level 1 tech may get very very very annoying by asking you if you pulled the battery and if you are running "advanced task killer" (I guarantee the latter actually), but you should just come up with the answer you know they want, until they agree to pass you up the chain. At the second level, they don't ask those questions (case in point: when I went to return DINC # 2 because it was shipped to me with a pre-blown speaker; the tier 1 rep actually asked me if I pulled the battery and did a reboot. Tier 2 rep apologized when I told him that).
Anyway, if you have one of these bad initial batch phones (as I did), I doubt any software solution is going to help you. In fact, it will hurt. If your phone has a faulty radio or is overheating after a few minutes of GPS, you probably want to know that, rather than mask it.
Turn off your protections, run the GPS, and see if you are hitting 43c+ (I believe 48c is the absolute highest level the Incredible will actually go before shutting down to save itself). If you are getting that hot, you simply have a bad phone.
EDIT: Whoops - missed your question. I use BATTERY INDICATOR (Free) from the market to show my battery strength as a number. It also shows the temperature when you slide down the top menu bar:
http://www.appbrain.com/app/com.darshancomputing.BatteryIndicator
Well, took all of 5 minutes of gps'ing before my phone started rebooting. It rebooted, I opened System Panel and the temperature was 35.7. Then it rebooted again. I shut off gps, went into System Panel and temp was 36.1. With the gps now off, the reboots stopped.
Hmmmm
Honestly, I have to turn the reigns over to someone else. I am still thinking bad radio (search out Incredible random reboot) as the source regardless of heat, but heat would have been the easier answer. My first DINC would also reboot randomly at the office (where it is sufficiently cool all the time).
It's assuredly hardware failure.
In my case, it wasn't related to temperature. Anything that taxed the radio or cpu triggered a reboot and/or boot loop. Even batch operations in Titanium Backup would render the phone unusable.
najaboy said:
It's assuredly hardware failure.
Click to expand...
Click to collapse
You are probably correct.
I reverted back to unrooted stock 2.1 last night. Did not install ANY applications whatsoever. This morning, used Google Navigation on my way to work and the phone rebooted about 3 minutes into my drive.
What's interesting now is that my phone is telling me that it's up to date and there are no updates available. I wonder if VZW has pulled the 2.2 OTA because of the battery drain issues. It'll be interesting to see when I go into VZW for a replacement phone if they make me go through the 2.2 upgrade or if they'll just swap out the phone.
Related
Mine just started to after lunch today. I've had it on the desk and saw it restart about 3 times in less than a 15 minute window.
How do I know this just started and it hasn't been going on in my pocket? Well over the weekend I would have heard it reset (since it's not on silent/vibrate like it is at work). It also significantly drains the battery more if you are constantly soft resetting it/turning it off and on.
So is anyone else having this issue? I need to figure out if it was just a freak occurrence or if something is wrong with it.
I did NOT root it, running everything stock - I did some updates on some apps I have installed but no new programs installed in a couple of days - again this just started happening today in the last couple of hours.
And besides email and messaging, I'm not running anything in the background like Pandora or eBuddy, so I don't think it's a program causing it to reset.
Edit:
Not sure if this is the best category for the thread, but I could not find any threads similar to this besides the battery issue in general. Apologies if this thread already exists somewhere.
No uncalled for restarts here. Open the back, pull the battery, check the contacts? Is it plugged in when it does this? Try padding the battery with a folded piece of paper between the door and battery to ensure a snug fit. If it still does that, time to go to a store.
@Jye75
Thanks, I have pulled out and looked at the battery. I have that Seido case they were slangin' at Best Buy on it, I don't think there's an issue with the contacts.
One weird thing is during one of the automatic restarts, the phone made the start up sound. I had the phone on vibrate and the start up before that (and after when I manually restarted it) did not have a tone. Very odd... perhaps it's possessed.
Odd indeed... drop by a Sprint store, would be my next move.
It happened to me two times today since I did the full root last night. The last time it happened, I clicked on a input field and it restarted...
I had the issue when I turned off "enable always on mobile data"...turning it back on stopped the resets.
forum.xda-developers.com/showthread.php?t=701540 <-- no one said much in my thread about it
Probably just a kernel panic. I would not worry about it too much. It's happened to me on my Hero, and on my Evo.
For comparison purposes, how often does OS X Kernel Panic? How often does Windows BSOD?
Android is rather new technology in comparison. Yes, it runs Linux, which is rather mature at this point, but it's built with a lot of new technology, which may not be as mature as the stock kernel itself.
/two cents.
heed316 said:
I had the issue when I turned off "enable always on mobile data"...turning it back on stopped the resets.
forum.xda-developers.com/showthread.php?t=701540 <-- no one said much in my thread about it
Click to expand...
Click to collapse
Thanks, I realized that was one of the few things I've changed at the end of the weekend. Sweet!
blakejohnson86 said:
Probably just a kernel panic. I would not worry about it too much. It's happened to me on my Hero, and on my Evo.
For comparison purposes, how often does OS X Kernel Panic? How often does Windows BSOD?
Android is rather new technology in comparison. Yes, it runs Linux, which is rather mature at this point, but it's built with a lot of new technology, which may not be as mature as the stock kernel itself.
/two cents.
Click to expand...
Click to collapse
It reset about 8-10 times in less than 2 hours. More than half of that time the phone was in my pocket and not in use. I hardly got a signal inside of Walmart so it's not like I was using it that much in there.
I have set the data to be always on and hopefully this will help...
I appreciate all the help guys!
pekosROB said:
Thanks, I realized that was one of the few things I've changed at the end of the weekend. Sweet!
It reset about 8-10 times in less than 2 hours. More than half of that time the phone was in my pocket and not in use. I hardly got a signal inside of Walmart so it's not like I was using it that much in there.
I have set the data to be always on and hopefully this will help...
I appreciate all the help guys!
Click to expand...
Click to collapse
I had the same exact thing happen to me beginning this past weekend. It was driving me insane since it was rebooting every 30 minutes or so. I noticed it started happening more so when I did not have good signal. In any case I came to the conclusion it was all the tinkering (root part 1 and custom ROM) I've done with the phone so I wiped it last night and started from scratch (root part 1 and 2 and custom ROM). No reboots yet, but seeing your post concerns me since it's not the first post I've read regarding this issue. I'll keep you posted if mine keeps doing it. I really hope it's not a real issue, getting a replacement does not seem like it will be an easy process at the moment with them constantly selling out.
marcosowns said:
I had the same exact thing happen to me beginning this past weekend. It was driving me insane since it was rebooting every 30 minutes or so. I noticed it started happening more so when I did not have good signal. In any case I came to the conclusion it was all the tinkering (root part 1 and custom ROM) I've done with the phone so I wiped it last night and started from scratch (root part 1 and 2 and custom ROM). No reboots yet, but seeing your post concerns me since it's not the first post I've read regarding this issue. I'll keep you posted if mine keeps doing it. I really hope it's not a real issue, getting a replacement does not seem like it will be an easy process at the moment with them constantly selling out.
Click to expand...
Click to collapse
Thanks for the input. Your concern about the difficulty in getting a replaced unit due to them selling out is EXACTLY why I'm trying to figure out if this is a software glitch.
I'm also glad you pointed out that it tended to happen when the signal was ****ty. Last night I enabled the data always on (it was on by default and I turned it off earlier in the weekend) and I haven't had a reset yet this morning. Of course I've also been in good coverage areas. When it kept resetting like mad last night it was inside of Wal-Mart, and they have some serious shielding on their building or something since I rarely get a full or even half signal in there regardless of carrier or phone in past experience. A lot of friends on Altell/Verizon beg to differ with me though.
I'm thinking if they're connected, the fact that a weak data signal contributes to the device rebooting is really odd; the only time I can think of why a phone should reboot on its own is the OS crashes (or some app takes up ALL the available RAM, freezing it, then crashing it) or it overheats (but would seem to turn off rather than reboot). I had a BB Curve that did this at one point so I had to clear the cache all the time.
Edit:
Actually, I realized when it started to happen it was at work where I have excellent reception. Hmmm... well at least it hasn't reset on its own this morning so far (so far meaning 30 minutes).
pekosROB said:
Thanks for the input. Your concern about the difficulty in getting a replaced unit due to them selling out is EXACTLY why I'm trying to figure out if this is a software glitch.
I'm also glad you pointed out that it tended to happen when the signal was ****ty. Last night I enabled the data always on (it was on by default and I turned it off earlier in the weekend) and I haven't had a reset yet this morning. Of course I've also been in good coverage areas. When it kept resetting like mad last night it was inside of Wal-Mart, and they have some serious shielding on their building or something since I rarely get a full or even half signal in there regardless of carrier or phone in past experience. A lot of friends on Altell/Verizon beg to differ with me though.
I'm thinking if they're connected, the fact that a weak data signal contributes to the device rebooting is really odd; the only time I can think of why a phone should reboot on its own is the OS crashes (or some app takes up ALL the available RAM, freezing it, then crashing it) or it overheats (but would seem to turn off rather than reboot). I had a BB Curve that did this at one point so I had to clear the cache all the time.
Edit:
Actually, I realized when it started to happen it was at work where I have excellent reception. Hmmm... well at least it hasn't reset on its own this morning so far (so far meaning 30 minutes).
Click to expand...
Click to collapse
Well for what it's worth, mine was also doing it in good signal areas as well. It just seemed a lot more pronounced when I was getting bad signal. Anywho I reread your original post that you are running stock software so let's see if it keeps occuring for both of us regardless of the differences in software we are running. I also still have "Enable data always on" off.
marcosowns said:
Well for what it's worth, mine was also doing it in good signal areas as well. It just seemed a lot more pronounced when I was getting bad signal. Anywho I reread your original post that you are running stock software so let's see if it keeps occuring for both of us regardless of the differences in software we are running. I also still have "Enable data always on" off.
Click to expand...
Click to collapse
Sounds like a plan. Still no problems so far with data always on.
FWIW I also did the battery trick by switching the phone to CDMA auto from GSM auto. Supposedly you have to do it everytime you boot your phone, and it's supposed to help with battery life. Thread here:
http://forum.xda-developers.com/showthread.php?t=700601
It has to have something to do with turning off always on mobile data. It goes away when it's on, but then comes back when you turn it off. I just did rooted and unlocked nand protection on my phone last night and turned off always on mobile data and haven't had any reboots yet. Then again, it took a little while for it to start resetting last time so we'll see I guess. Could just be some glitch in the software that putting a new rom on has fixed...
It has to have something to do with turning off always on mobile data. It goes away when it's on, but then comes back when you turn it off. I just did rooted and unlocked nand protection on my phone last night and turned off always on mobile data and haven't had any reboots yet.
Click to expand...
Click to collapse
Mine had been the complete opposite, I have had data off, and when I turned it on yesterday it started reseting, I turned data back off last night and have had no more problems...
-------------------------------------
Sent via the XDA Tapatalk App
I had this happen to me while I was trying to talk on the phone and use google navigation at the same time while running the Overclocking widget to throttle my cpu to 285mhz when the screen was off. Whenever I turned off the screen my phone would reboot.
My guess is that there some issue there where the cpu cant keep up with the heavy usage, locks up and forces a reboot...
I've since gotten rid of the OC widget, rooted my phone and installed a custom rom. I've not had it happen since, of course I havent tried talking and using google nav yet.
I've also noticed that advanced task killer caused the htc sense launcher to reboot (force killed) every once in a while... I've gotten rid of that too...
happend to me while talking on the phone twice, it was weird i could hear him still talking the entire time it was rebooting, up untill the OS actually launched...Im gunna try and kill set cpu, how many other people have this running while its rebooting???
widjit said:
happend to me while talking on the phone twice, it was weird i could hear him still talking the entire time it was rebooting, up untill the OS actually launched...Im gunna try and kill set cpu, how many other people have this running while its rebooting???
Click to expand...
Click to collapse
This happened to me today, in-call. My phone has reset 6 times since then off-call.
Alright un-installed setcpu and it still resets. I'm now trying to shim my battery to see if its a loose connection. I gotta figure this out its driving me crazy...
UPDATE: still hapining with battery shined, tried both data sync on and off, installed setcpu, all to no avail... maybe I will try a hard reset... I remember on my kaiser this started hapinin and it was a bad nand flash, but I'm running stock with unrevoked... so if anyone has any ideas I'm wide open.
-------------------------------------
Sent via the XDA Tapatalk App
widjit said:
Alright un-installed setcpu and it still resets. I'm now trying to shim my battery to see if its a loose connection. I gotta figure this out its driving me crazy...
UPDATE: still hapining with battery shined, tried both data sync on and off, installed setcpu, all to no avail... maybe I will try a hard reset... I remember on my kaiser this started hapinin and it was a bad nand flash, but I'm running stock with unrevoked... so if anyone has any ideas I'm wide open.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Running Toast's root has stopped it for me as of today. If that actually had any effect, I have no idea...but no resets yet with always on mobile data on and off. Maybe flashing the rom again helped...
heed316 said:
Running Toast's root has stopped it for me as of today. If that actually had any effect, I have no idea...but no resets yet with always on mobile data on and off. Maybe flashing the rom again helped...
Click to expand...
Click to collapse
Me too, I'm totally stuck on part 2 though...
widjit said:
Alright un-installed setcpu and it still resets. I'm now trying to shim my battery to see if its a loose connection. I gotta figure this out its driving me crazy...
UPDATE: still hapining with battery shined, tried both data sync on and off, installed setcpu, all to no avail... maybe I will try a hard reset... I remember on my kaiser this started hapinin and it was a bad nand flash, but I'm running stock with unrevoked... so if anyone has any ideas I'm wide open.
Click to expand...
Click to collapse
Wow dude I'm sorry to hear you're having that much trouble. I'm on step 2 of part 2 of Toast's root method but running into major issues. Since I did step 1 (and before that I enabled data always on again) I haven't had a reset issue.
For the record, my Hardware version 2.
Do you guys think this is a widespread or isolated issue? I'm surprised it hasn't happened more or less, in other words I figured there would be either a lot or hardly any comments about it. This medium sized number is interesting.
You know em, you love em, random semi-reproducible problems!
I have been playing with my phone and enjoying the freedom of root access every since the original 2.2 OTA root method was posted (the downgrade unrevoked method). Its been great, but I started to have an annoying reboot issue that popped up every now and then. At first it was annoying, but now it is getting worse.
It SEEMS like it is temperature related. It started happening while the phone was charging, 4g was on, and wireless tethering (pre8) was running. First the connection between my computer and the phone would drop, then I'd reconnect, surf for another 5 mins or so, and the phone would reboot. Battery temp was reporting ~44C. After I let the phone cool down everything was fine.
I found that if I didn't have the phone on the charger or if I put the phone (battery side down) on top of a cool metal surface, the problem would not arise.
But then it started happening more often and under circumstances where it had previously not had any problems. Things like turning off my alarm, answering a call, playing alchemy. Under those cases, the battery was sometimes warm, but usually cool.
Last night it entered a reboot loop, where it just returned to the white HTC EVO screen over and over and over. It eventually turned off and the green light began to flash. I could not boot it up until I removed the battery and cooled both the phone and battery down. It was charging with a file downloading over 3g.
The problem is defiantly getting worse.
--------------------
I know that people are going to fire at me to wipe and reinstall (like in all the other threads) but that is the craziest part: I have. Many times. When it started to happen I thought it was the ROM, so I would change ROMS when it happened, but now I realize the problem is independent of the ROM in use.
I have used (and hit rebooting issues while the batter is hot and cold)
Stock (rooted) 2.1 and 2.2
Ava V5, V6, and V7
Fresh 3.2 (and a previous version, I don't recall which)
BakedSnack 1.6 and 1.7
Evo Zone 8.29
Vaelpak 1.3 and (I believe) 1.2
A couple of Virus' ROMs
I have used the stock 2.1, 2.2, and 3.2 HTC kernels and King's #s 6, 8, and 5, all with the same problems.
I even nandroided to backups that I had previously NOT had the issue with, only to immediately reboot. It really looks like software is not the issue, but I'm not sure.
As you may gather from this, it has been an on going issue for quite some time. I always do a full wipe (all caches, dalvik, et all) between ROMS. I'm out of ideas, do I need to S-ON and OTA then return this bad boy to sprint? Any ideas?
EDIT
Forgot to add, I am using ClockWork recovery, and flashing ROMs manually (through recovery, not a ROM manager app)
Quick bump for interest and posible solution. I'm pretty sure it's a hardware issue, but I just want to be sure.
Even though I'm always going on about how clockwork always works fine for me, and wipes everything correctly, I'll be the guy here to suggest trying to flash with amon ra a few times. If you still run into issues, I'd say that your battery is borked. But before returning the whole thing, maybe pick up a cheap extra battery off of ebay, and see how it works with that?
Just so I am clear on what to do, if I want to return the phone for service, I need to run the S-ON tool from unrevoked, then accept the OTA and I should be good to take it in, right?
Yes flash s-on then run RUU
i am having exactly the same issue
i've been on cm6 for over a month and it started about 2-3 weeks ago, at first i thought it was the temperature too but recently it started rebooting at completly random moments. I flashed baked snack yesterday and put a new battery in, same thing, random reboot
i flashed deoxed newest update with no mods today to see if that would fix the issue, 3 minutes after i did, i was signing in to my google account - reboot
turned the phone on, and 1 minute later reboot and loops....
any ideas?
using RA recovery btw, wiped everything before i flashed.
It's the HARDWARE
Guys,
Just thought I'd share a little of my experience with this phenomenon.
I had a HW003 Nova since the release of the Evo. I started experiencing random reboots every so often about a month or so later.
These progressed regardless of what version of Android, or which rom, or which kernel, bootloader, OTA update, S-ON, S-OFF, Bone stock or rooted.
After barely managing to get the phone back to it's factory state, I replaced it no questions asked on my second visit to Sprint repair center.
My refurbished replacement (Also HW003) was fine for a whole 5mins before it started doing the exact same thing. I gave it back to the technician, and put in the order for my second replacement. As per the advice of the technician, if my next replacement has any problems at all, I'm supposed to call Sprint customer service directly in hopes of a longstanding solution (read: Ask for a brand new phone)
Not trolling or starting ****, because I love my Evo, but let's be realistic.
These phones are built like garbage. At least the original crop of them is.
They use some good parts, but they are manufactured in a cheap manner.
Probably in cheap factories using cheap labor, and cheap materials.
While not every Evo is junk (my girlfriend hasn't had any problems with her's in over 3 months) you have to figure that one out of every few thousand is probably going to have some kind of defect, be it light leakage, bad screen grounding, broken USB connector, or even the infamous nonsensical, irrational, arbitrary reboot/power-cycle.
Sounds like what was happening to me too. I just took it to repair center and after a couple trips they replaced it. First they put a new battery in, said they couldn't reproduce the reboot but in three minutes I did. After that they ordered a new one.
In the beginning it was so random and appeared to be a heating issue too, then it just got worse and worse. Seemed like I could use the phone without issues if I wasn't taxing the phone too much but it progressively got worse and got to the point of it being maddening. Then it was hanging on splash screen and boot looping. Uprooted and took her in. Sounds like thats your best bet. I tried different ROMs, stock, etc etc.
Just take it in after doing what you need to do. Good luck.
SWYPED from my SUPASONIC
I have been having this problem for what seems like a few weeks now, but it has gotten worse over the past week or so. I rooted my Inc and have flashed a few roms to test them out ( got most from Rom Manager as I was told those are pretty reliable ). I have this issue that seems to be pretty constant now, I will be using my phone, like downloading an app from the market or listening to music and I will pop into google maps to get directions or see where my latitude friends and family are, and poof! my phone reboots, then it goes into a boot loop and doesn't usually fix itself until I pull the battery. I do notice that the battery gets pretty hot at the same time. If I pull the battery and keep it out till it cools, it will usually fix the issue for a short time... but then it happens again ( no matter what rom I am running) Someone told me the radio may be causing this, anything to that ?
I am currently running Redemptive R-EVO-lution 1.6
Ver 2.2
Baseband Ver.
2.15.00.07.28
Kernel Ver.
2.6.32.15-gb7b01d1
htc-kernel(at)and18-2#1
Build Number
3.21.605.1 CL231334 release-keys
Browser Ver.
Webkit 3.1
Pri ver.
1.28_002
Prl
52011
Eri Ver.
5
Any suggestions or help, would be great.
Thanks!
Steve
I don't know a whole lot about android but I do know most devices have builtin failsafes when it comes to batteries. So, your battery may be the issue here and not the device itself. If you know someone else with an incredible then try to trade batteries for a day. If the problem doesn't repeat, or even starts happening on the other device then you know you have a defective battery.
Other than that, you'll have to wait for someone more knowledgeable than I to give you their thoughts. Good luck.
Sent from my SCH-I500 using Tapatalk
Install something to view your battery heat you may be over heating it
Sent from my Incredible using XDA App
will do
Is there an app you'd recommend for the battery app heat ?
pulling info will heat the phone...use setcpu it checks for battery temp and displas it on the widget... do you have GPS on? any downloads over 3g tend to heat the phone a bit too..as does anything that uses the GPS....
check your phone usage and see if anything looks out of whack, maybe an app that is drawing a lot of battery etc...
you can flash back to the stock rooted 2.2 and see if that does the same thing....i'm running the desire rom with adrynalyne SSUV kernel and phone is steady at 95*
Installed setcpu... will keep an eye on that for the next 24 hours and see what happens. Do you have any recommendations on profile settings in setcpu ? Thanks again for the help.
-Steve
I was having the exact same issues, and thought it was heat for the longest time as well.
Digging around online, I found that my issue was related to the phone switching towers on a low signal. It seems that there may have been a bad batch of phones in there with this problem - because I found a LOT of examples when I looked for them.
Anyway, I had it replaced by Verizon and it's been great ever since. It hasn't rebooted on me once. Maybe you are having the same issue.
The actual answer
All deference to the prior posters, but SetCPU has nothing to do with it.
I had this as well on my first Incredible (I am on #3). As the above poster indicated, there IS a problem with the earlier batches of Incredibles. They were built with faulty hardware radios. As they struggle to compensate to find a signal, they heat. Once they hit a point, they reboot. Mine would go into a reboot loop between 4-13 times before actually booting, and it would virtually never go into custom recovery (at least not unless it was off for a while).
You do not need a new kernel, you do not need SetCPU, you do not need a battery checker ... you need to call Verizon, tell them your phone gets super hot even with no use, and enters a reboot loop. They will send you a refurb (I received a refurb with a pre-blown speaker) and you will enter refurb-hell until you get one that works.
I really appreciate your input, I put setcpu on my DInc. and have it set to drop the CPU to 600 if the battery temp hits 100, has been like that all day and so far, it hasn't rebooted once. If the problem continues, I will have to goto verizon and play the refurb game, but i HATE the refurb game and like so many of us, I NEVER win the first few times I play.
11RJB, what did you look up specifically to find out about the bad batch of phones??
Thanks again guys/girls
11RJB said:
I was having the exact same issues, and thought it was heat for the longest time as well.
Digging around online, I found that my issue was related to the phone switching towers on a low signal. It seems that there may have been a bad batch of phones in there with this problem - because I found a LOT of examples when I looked for them.
Anyway, I had it replaced by Verizon and it's been great ever since. It hasn't rebooted on me once. Maybe you are having the same issue.
Click to expand...
Click to collapse
Did you revert the phone back to stock and unrooted?
You are few to do with your phone as you see fit but please understand you are now throwing a software band aid over a known hardware problem.
respect your suggestion
jdmba said:
You are few to do with your phone as you see fit but please understand you are now throwing a software band aid over a known hardware problem.
Click to expand...
Click to collapse
If I did choose to bring the phone back to verizon, I would need to unroot it and put it back to stock 2.2 with sence, right ? Is the OTA rom out there anywhere ? I am not trying to argue with you, just trying to avoid dealing with the nards at the verizon store... LOL
-Steve
Yes
There are so many threads out on XDA on unrooting an Incredible for warranty return that I weep a little bit. A little searching will bring them up. I too did NOT want to enter refurb hell, but when the phone would become unusable for hours (usually later in the day) because of the heat, I had little choice.
So you had to go through a few exchanges to get a good unit, right?
Now on my 3rd DInc: ( still playing the refurb game.... this sux
Sent from my ADR6300 using Tapatalk
rockinr6 said:
I have this issue that seems to be pretty constant now, I will be using my phone, like downloading an app from the market or listening to music and I will pop into google maps to get directions or see where my latitude friends and family are, and poof! my phone reboots, then it goes into a boot loop and doesn't usually fix itself until I pull the battery. I do notice that the battery gets pretty hot at the same time. If I pull the battery and keep it out till it cools, it will usually fix the issue for a short time... but then it happens again ( no matter what rom I am running) Someone told me the radio may be causing this, anything to that ?
Click to expand...
Click to collapse
Even though I don't own an Incredible, I have the exact same issue with my Desire. I was thinking of going for an Incredible S. Anybody experienced any such issues with Incredible S? I bought my Desire around Q3 of 2010.
I seem to be having an issue with my phone overheating and rebooting. It seems to happen consistently when using navigation or when playing games (I'm hooked on Gem Miner). Always at an inopportune time. To me this seems like a result of bad hardware or something but is it possible that rooting and installing ROMs like CM7 or Kingdom Stock Sense?
I bought my phone at Best Buy and ended up getting the warranty, so assuming I can revert the phone back to stock, I should be able to get this covered under warranty. Right?
My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
TheWhiteBandito said:
My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible
Click to expand...
Click to collapse
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...
k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Hot enough that it's shutting down. I couldn't tell ya specifically.
k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Its higher than 119F. Mine hit 122F the other day and didn't reboot, unless the safety shut off didn't kick in on mine. Don't think it is much higher than that though before it does.
I had heard it shuts down at 119 but my phone hasn't ever gotten that hot. I've only managed to get it up to about 114, that was multitasking and charging, overclocked to 1113.
When it reboots, do you get 5 vibrations and then the indicator flashes green until you pull the battery? If so, you are starting to have serious problems.
This thread helped me recover my Incredible..
http://forum.xda-developers.com/showthread.php?t=982454
I had mine at 120F the other day loading a new rom and no shut off
Sent from my Incredible using XDA Premium App
Mine gets hot when using wireless tether.
jetsaredim said:
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...
Click to expand...
Click to collapse
I'm leaning toward a hardware issue. The reason I say that is because I'm using CM7.0.3 and Chad's Incredikernal and when I use navigation I also connect my car charger and have never had a heat issue nor any reboots. I drove from SC to FL back in Feb and had navigation running the whole time.
Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?
jetsaredim said:
Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?
Click to expand...
Click to collapse
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.
fLaWx said:
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.
Click to expand...
Click to collapse
I assume you're not completely an expert in this matter, but let me see if I get this right... I have to go back to having CWM on my phone so I can apply the S-ON zip and then re-run the stock recovery to get back to complete 100% stock. Sound right? I wouldn't even consider it if I didn't think there was a slight chance that I'd get flagged on the warranty review for having S-OFF set. I don't want them to have any reason to deny my getting a new phone.
Hi - long time lurker, barely ever post, but I'm gonna chime in here.
My DInc also reboots, and it is warm to the touch when it does happen. Don't know how hot though sry. I've been rooted since November, but haven't installed a Custom Rom, just removed bloat, and added some other useful tools. The biggest change I've made was changing the fonts. I don't over/under clock either (it runs just fine for me). My reboots seem to be increasing in number. At first it would be once a month, then a few times a week, and now a couple times a day.
Sometimes, my phone will reboot just once, and then continue to work. Sometimes 2-3x in a row, and then continue to work or not. Sometimes, it just vibrates 5x quickly, and then is locked (LED flashes), and the only way to recover is to pull the battery and start over.
Seems to happen MOSTLY around certain times of day - 4:30-6pm when I'm on my way home from work (no, not using my phone, but it happens anyway), and around lunchtime (again, not using it, or if I am it's barely). Other times it happens too - but really randomly. I'm ruling out different apps that might be triggering it, but don't think that's the issue.
QUESTION - if it is heat related, and the phone is supposed to go into shut-down mode at 119*, but seems to be different temps for everybody, could it be the thermostat? Could it be registering a false temp reading and think it needs to shut down? Has anyone explored this?
I'm not an engineer, or even a programmer, but I like to play one on TV. Thx
Oh - I forgot to add this:
There have been times when it would reboot, and I've placed my phone and battery (removed from phone) on the vents of an airconditioner, or even sitting on a frozen ice pack (the kind for a cooler) and it would still happen afterwards. To the touch, my phone would be cold, not freezing, but cold. Seriously lower temp than what it was when it was very warm to the touch...
I'm definitely with you on the first scenario. I just brought it to my local Best Buy where I bought it (with warranty) and they sent it off and gave me a loaner DInc to use till mine's repaired. They said, if they can't repair it, they'll give me a DInc2 as a replacement since the Dinc1 is "backordered" (aka not being carried).
jetsaredim - I was able to get a replacement DInc sent to me overnight (free!). My first replacement had a faulty USB port, so I couldn't charge my phone. I have 'another' DInc being sent to me now. Other than the faulty USB port, I haven't had any overheating issues so far (knock on wood).
First phone manufactured in June 2010
First replacement phone, manufactured in April 2010, and remanufactured June 2011 (via ##7764726)
I just got my replacement Incredible today. I just tested my original phone again by watching 15 minutes of video on youtube and BANG!!!!!!!!!! It rebooted as usual. Screen and battery get very warm. The reboots seem to happen when watching videos online or offline, playing games for 10 to 15 minutes, browsing the web for 15 to 20 minutes, using Google Maps with or without charging at the same time, and charging and talking on the phone at the same time. Well, I'm sending back the original and hoping that the replacement doesn't fail me. Glad that I swapped it just before the manufacturer warranty was up.
Have had the Dinc since week one. 100% stock - have not rooted (yet) and stock battery - in the past month it has 'overheated" and rebooted twice. Never happened before. Both times while using navigation and charging. Could it simply be the battery? It's not holding a charge like it used to too which also makes me wonder about the battery.
I've read 10 pages on this subforum, random talks about updates, LTE fixes, etc...I've yet to find a single thread giving an official fix for random rebooting? I get this at least 4x a day...regardless of charging or not, SD card installed or not, all the latest updates are installed. I can't be the only one and if so, why isn't this a Sticky issue at the beginning?
I and few have others have the unpleasant experience with rebooting. But it was a little relief that this issue is not just with my Note4.
Laughter is the key to happiness
I had this problem with the early 6.01 stock roms, but it eventually calmed down. Now I get a reboot about once a week. I just assumed the first couple 6.01 stock roms were buggy.
I suppose lots of hardware issues could also cause it.
I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc
m5james said:
I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc
Click to expand...
Click to collapse
So, what rom is the phone running?
Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?
m5james said:
Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?
Click to expand...
Click to collapse
What version of stock? If it's old, some of the early 6.01 roms were pretty buggy. The current stock rom is QC1, which just began to roll out this week. Make sure you are on the most current rom.
Last update I received was this week which turned out to only be a security patch.
So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.
So I hope I don't jinx myself, but I think a new battery has solved my issue...with some extra steps Let me explain.
Bought the phone used, it'd reset about 3-4x a day...being charged, being used, whatever. It'd reboot anywhere from 80% down to 40%, no rhyme or reason. Sometimes it simply wouldn't allow me to turn it back on, the light would flash blue while dimming in and out, but wouldn't power up the screen. Plugging it back in and it'd be at 30%-45% no matter what. I downloaded an app called Battery Calibration from Meza (sp?) that had a little Android logo with a % on his chest. Resetting may or may not have completely solved the problem had it not soft reset when trying to get battery stats to refresh themselves. It's my understanding that if it reset, it rewrote a battery stat upon reboot, making this step useless.
I got two new batteries from eBay (http://www.ebay.com/itm/112344168032?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT), I charged one in the phone and one on an external charger. Even after running with the new battery, it still reboot once and shutoff around 43% reported on the phone itself. Once plugged in and phone still off, it said it was at 15%. I swapped in the other new and charged battery, powered on the phone, plugged it in until it read 100%. I fired up the Battery Calibration app, unplugged the phone as directed and then to force the battery to drain faster, I let YouTube play uninterrupted for about 4hrs. NOT A SINGLE REBOOT!! For the first time with this phone, it actually stayed on and dipped below the 30%'s and gave me a warning when the battery was getting low (yellow icon) and getting critically low (red icon) before it finally powered itself off at 1%. The phone is now charged on the factory fast charger, this time playing Pandora with the screen off and uninterrupted as well...it's currently sitting at around 57% last I checked.
Once it's fully charged, I'll run it like any normal user (texting, music, etc) without being plugged in and if all works well, it won't reboot.
Hopefully this helps someone with the same issue and is a $8 fix since I bought two batteries.
poit said:
So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.
Click to expand...
Click to collapse
I reset the phone the day I got it.
if your phone often reboot many times in a day, make sure that you don't use Ram kernel V6 or v7 for your Rom, V5 is only version that not make your phone randomly reboot. I try Ram kernel v6 and v7 in Note 7 port rom, note 5 port rom and stock either, and this kernel version always make my phone reboot many many times, unless i flashed v5 or stock kernel, the problem had gone.
I had this problem. I replaced the battery with an official Samsung battery I ordered from Sprint, and the problem went away. Simple as that. No reboots ever since.
Purchased a new battery from Amazon, Samsung OEM, problem solved. Put back old battery guess what it started again but only when battery reached 70% of the original charge. So it must be the battery memory problem.
Sent from my SM-N910P using Tapatalk
Four batteries later and this still happens. Can this be addressed via rooting and then undervolting? I remember phones of the past where people would overclock for speed and undervolt for battery life, but one way too high or too low and you'd either get random rebooting or freezing. This is so god damn annoying!!!!!!