Develop Bugs

[Q] GPS use forces reboots. Help?

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.

[Q] Time for another "My EVO keeps mysteriously rebooting" thread!

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

[Q] Incredible heats up and reboots

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.

[Q] M7VZW Died twice, after installing cm11. Over heating and battery draining fast.

Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!

ccarr313 said:
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
Click to expand...
Click to collapse
Are you using the stock charger?
Try a different charger on the next phone. Many people have flashed CM11 and don't have those issues so it appears to be your charger that's killing the phones.

Don't think it's the charger. I am seeing more and more threads of people running cm11 a d getting this overheat issues then phone dying. I think it's best that people leaves cm11 alone until it can be fixed. As I have never seen any other Rom act like this.
Sent from my HTC6500LVW using Tapatalk

The only thing i can think of, after resting on it, is that i turned on the DSP manager EQ shortly before it happened each time. Not going to customize the one I am getting today. Just thankful I know enough that I managed to get them both back to s-on / locked / stock RUU before sending them back.....so my warranty will cover them.
And yes, i was using the stock HTC charger that came with the device. Wish i had a meter.

This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.

peteschlabar said:
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
Click to expand...
Click to collapse
Both phones are dead. Will not charge, will not turn on. They only worked for a few hours after the over heating issue started. Battery continued to drain even after being turned off, and after it was drained it would not charge at all. It was lucky i could even get them back to s-on / locked / stock. And the issue continued after going back to stock. Hardware damaged for sure. So no more testing on those. lol

On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.

Fu5ion said:
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Click to expand...
Click to collapse
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao

ccarr313 said:
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
Click to expand...
Click to collapse
They'll let you send as many as you want as long as its under warranty haha. I remember I had to send in the droid bionic 4 times and the droid RAZR twice, both times without any hassle from them. I just had awful luck with those phones, mostly screen-lifting.

Haha. Good to hear. Because I have 10 months of warranty left, and I am a computer modder at heart.....and that has turned me into a custom rom loving phone crazy person. :laugh:

Yeah you've got nothing to worry about there. Just make sure its back to stock. They honestly probably wouldn't say anything if it weren't, but we don't want to give them even more reasons to lock us down more.

I'm having the same issues. I'm on my 4th phone now.
This happened to me on several ROMs. SlimBean 4.3, SlimKat 4.4 now.. and I flashed back to stock while I had a phone that wasn't dead yet.. but it's still happening.
I'm not sure what the deal is. Just happens without rhyme or reason out of the blue one day.
Can anyone recommend flashing anything that might help?
What's responsible for the battery management even if there's no ROM installed? HBoot? Should I re-flash an HBoot to attempt to fix? It's not the ROM, I don't think. If it is, it's something that permanently screws up the phone. I've completely wiped my phone and went to stock. Same issue.

I got my new phone, and s-off'ed / unlocked / flashed cwm recovery, then updated it to 4.3 ota, no issues so far. Scared to put any custom rom after what happened to the last two. But having no issues yet with it, with only a custom recovery and s-off. Have rom manager loaded also, and made a back up since it seems to be running fine now. If anyone isolates this problem and can get a fix going, would make me very happy.

I've noticed that trickster and some of the other CPU performance apps are locking the min CPU speed at the max speed so the phone always stays at top speed. If it stays like that for an extended period of time it will damage the phone. The heat can cause the battery to drain really fast and damage the CPU. If you are on any ROM with a custom kernel I would be on the lookout for this.
Sent from my HTC6500LVW using Tapatalk

I was running CM11 on my nexus Galaxy and I thought my battery was bad. My phone would die after a few hours. I got a new battery and it did the same. I installed slim ROM and now I am getting 10+ hours no problem. Also my phone does not feel like it is going to melt.

Is my HTC 10 defective?

Hey there,
I got my HTC 10 two weeks ago and it's already s-off, unlocked, rooted, twrp and elemental-x kernel installed, and running some xposed modules (greenify, gravity box). I re-branded it from CID H3G to WWE, unfortunately without backing up the stock setup.
From the beginning I've had some random soft reboots which I think are related to the battery's temperature when charging, and the phone is being used for browsing or streaming. The battery reaches up to 44C and the phone feels very warm, both front and back side. The soft reboot itself is strange too, it takes a lot of time until the pin code is asked and after that there's a notification saying that the process system is not responding but it comes up eventually. This is also happening when rebooting manually, both soft and full reboots.
I would like to return it back to stock so I can ask for an RMA, do you think this is the way to go? I'll only be able to go back to the WWE stock, at least I think I can. Do I need to go back to s-on and locked to return it? Your help is highly appreciated! :good:
Thanks in advance!
Greetings from Vienna

http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Maby something for you?
And se if the problem is still there.

Thanks I will give it a try, although I couldn't find the RUU for my region (Austria) and CID H3G (I think it is .771). I'll take the WWE instead and we'll see how far it will take me
greetings from Vienna

hojnol said:
Hey there,
I got my HTC 10 two weeks ago and it's already s-off, unlocked, rooted, twrp and elemental-x kernel installed, and running some xposed modules (greenify, gravity box). I re-branded it from CID H3G to WWE, unfortunately without backing up the stock setup.
From the beginning I've had some random soft reboots which I think are related to the battery's temperature when charging, and the phone is being used for browsing or streaming. The battery reaches up to 44C and the phone feels very warm, both front and back side. The soft reboot itself is strange too, it takes a lot of time until the pin code is asked and after that there's a notification saying that the process system is not responding but it comes up eventually. This is also happening when rebooting manually, both soft and full reboots.
I would like to return it back to stock so I can ask for an RMA, do you think this is the way to go? I'll only be able to go back to the WWE stock, at least I think I can. Do I need to go back to s-on and locked to return it? Your help is highly appreciated! :good:
Thanks in advance!
Greetings from Vienna
Click to expand...
Click to collapse
Try to lighten the load on the phone, clean install a rom.. Stock kernel. Leedroid would be perfect. Install only the apps you need from fresh and see if you have the same issues. Chances are if it's overheating it could just be overloaded. Worse case scenario is the phone itself. Hopefully that's not the case.

dladz said:
Try to lighten the load on the phone, clean install a rom.. Stock kernel. Leedroid would be perfect. Install only the apps you need from fresh and see if you have the same issues. Chances are if it's overheating it could just be overloaded. Worse case scenario is the phone itself. Hopefully that's not the case.
Click to expand...
Click to collapse
It seems that did the trick; I've installed the ICE ROM couple of days ago (LeeDroid will be next in case something goes wrong again) and haven't had any random reboots ever since. I've stopped using the phone when charging and now the temperature does not exceed 41C degrees.
The phone has also stopped stalling after manual reboots, looks pretty good so far!
Thanks a bunch! Have a nice Sunday and greetings from Vienna

dladz said:
Try to lighten the load on the phone, clean install a rom.. Stock kernel. Leedroid would be perfect. Install only the apps you need from fresh and see if you have the same issues. Chances are if it's overheating it could just be overloaded. Worse case scenario is the phone itself. Hopefully that's not the case.
Click to expand...
Click to collapse
Screen on and especially battery charging will heat the phone more than running apps. The case you're using will immensely affect this--aluminum dissipates heat; TPU is a thermal insulator.
CPUs throttle, as does charging when too hot.
44C is a proper temp for a loaded 810/820. If your CPU sustains this temp without down-clocking, it's able to shed heat properly. If you are under constant heavy load, you would notice battery drain before temps I would think.
A hardware issue (heat, power) won't perform a soft reboot, it will reset the hardware, causing a full reboot.
It's likely your ROM and/or apps: bad caching, bad install, bad config. I would RUU before declaring the device defective.

hojnol said:
It seems that did the trick; I've installed the ICE ROM couple of days ago (LeeDroid will be next in case something goes wrong again) and haven't had any random reboots ever since. I've stopped using the phone when charging and now the temperature does not exceed 41C degrees.
The phone has also stopped stalling after manual reboots, looks pretty good so far!
Thanks a bunch! Have a nice Sunday and greetings from Vienna
Click to expand...
Click to collapse
No worries mate, it's an age old problem with android. Sometimes you just need a fresh start.