Related
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.
rhinolow said:
So I went back to 4.0.1 and was getting a steady three bars on my phone
Went to 4.0.2 and am getting a steady 2 bars on 4g
Unlocked, and rooted on 4.0.2, and was getting really sporadic signal behavior, including signal loss
All these readings are from the same location in my home.
Then I went back to 4.0.1 and tested all three conditions and got the same results.
I'm no programmer so I can't say why unlocking/rooting would make a difference, but I believe it's making enough of a difference at this point that I'm going to stay stock and locked at 4.0.2 for now.
You guys that are having a lot of problems, are you unlocked or rooted?
Click to expand...
Click to collapse
Now that it's been a few days..... I want others to chime in on this report (no one answered this question in the original thread).
I was having a ton of issues, thought that VZW did something to make it slightly better (which I still believe they did), but stilll... I have issues, although not as bad as the second 12 hours of ownership.
I had made the call to tech support and was then going to return the phone.... when I got home I brought the device back to stock carrier 4.0.1 ROM floating around). Problems were almost completely gone!?! An hour later, the update came and I was worried about the upgrade screwing the radio that was acting better (not that it was perfect by any means!!). So..... after a little thought, I figured I could always go back to 4.0.1 and/or return it. I let the update do it's thing.
There seems to be zero difference between 4.0.1 and 4.0.2, when it comes to the radio.
I was still scared to do much..... I didn't install any apps while I watched the phone for a few hours. Then only Google's apps... the next day the rest of my apps (w/small exceptions, detailed below). Everything ran smoothly.... including the radio. Now it isn't nearly as good as the DX radio in my last phone, BUT..... at least I wasn't constantly with -120dbm and was able to use the phone, as a phone!
So.... I figured after another day that VZW must have fixed something.
Cool, right? Not sure..... I am stock, unlocked, and unrooted. I am afraid to root the phone..... I can't fathom how root could cause a radio issue, but am wondering how many others might have issue with and without root.
Now.... I am still seeing issues, but not nearly as bad. I'll root the phone tonight to see what happens, but would like others input.
Stock Verizon Nexus here and where I normally get full 4g I get maybe 2-3 3g bars. Most of the time I get zero signal where I at least get 3g.
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
droid2andyou said:
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
Click to expand...
Click to collapse
Great article. Sure as heck opened my eyes up. Thanks.
Root doesn't touch the radio. All it does it give you admin right over the phone.
-Galaxy Nexus
-Asus Transformer
player911 said:
Root doesn't touch the radio. All it does it give you admin right over the phone.
-Galaxy Nexus
-Asus Transformer
Click to expand...
Click to collapse
Exactly right it must have just been the cell towers by the ops area
I'm currently having issues now before and after root
droid2andyou said:
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
Click to expand...
Click to collapse
Just read that earlier today. Lots of great info inside.
The story continues
So, just to follow up. I did return my device for a new GNEX and have not had the same issues. I have been reluctant to root my new phone, but I still don't see any reason why the two would be related. I think I had a bad device. I think there are a substantial number of people that are getting DOA devices, but it doesn't appear to a majority. I'll report back if/when I decide to root and flash anything to my new device.
abendx said:
Now that it's been a few days..... I want others to chime in on this report (no one answered this question in the original thread).
I was having a ton of issues, thought that VZW did something to make it slightly better (which I still believe they did), but stilll... I have issues, although not as bad as the second 12 hours of ownership.
I had made the call to tech support and was then going to return the phone.... when I got home I brought the device back to stock carrier 4.0.1 ROM floating around). Problems were almost completely gone!?! An hour later, the update came and I was worried about the upgrade screwing the radio that was acting better (not that it was perfect by any means!!). So..... after a little thought, I figured I could always go back to 4.0.1 and/or return it. I let the update do it's thing.
There seems to be zero difference between 4.0.1 and 4.0.2, when it comes to the radio.
I was still scared to do much..... I didn't install any apps while I watched the phone for a few hours. Then only Google's apps... the next day the rest of my apps (w/small exceptions, detailed below). Everything ran smoothly.... including the radio. Now it isn't nearly as good as the DX radio in my last phone, BUT..... at least I wasn't constantly with -120dbm and was able to use the phone, as a phone!
So.... I figured after another day that VZW must have fixed something.
Cool, right? Not sure..... I am stock, unlocked, and unrooted. I am afraid to root the phone..... I can't fathom how root could cause a radio issue, but am wondering how many others might have issue with and without root.
Now.... I am still seeing issues, but not nearly as bad. I'll root the phone tonight to see what happens, but would like others input.
Click to expand...
Click to collapse
I'm getting ready to upgrade from my beloved Galaxy S4. I'm considering the One M9 and would love to hear opinions from current owners.
I saw another thread titled similarly, but that person didn't mention some of my chief concerns.
My biggest concern is I MUST have a rooted phone. The S4 was a bit of a pain because it was locked down so much, but the amazing people here on XDA always came through and eventually worked up root methods that idiots like me can follow. Other than the root issue, I have loved the S4.
My phone before the S4 was an HTC Incredible, which was awesome. And with a Verizon recently locking up the S6 with updates to block rooting, I thought HTC might be my ticket once again. Then when I came here to do some research, it seems Verizon has similarly locked down the One M9.
So how difficult is it to root the M9?
I saw something about sending the phone off to a gentleman who could unlock the bootloader. That would be an option for me since I don't have to have the phone immediately. If I do that, does that solve the root difficulty permanently?
On top of all that, how is the One M9 as a phone? Is Sense still similar to previous versions, etc.?
I'd love to read your thoughts!
Buckhunter206 said:
I'm getting ready to upgrade from my beloved Galaxy S4. I'm considering the One M9 and would love to hear opinions from current owners.
I saw another thread titled similarly, but that person didn't mention some of my chief concerns.
My biggest concern is I MUST have a rooted phone. The S4 was a bit of a pain because it was locked down so much, but the amazing people here on XDA always came through and eventually worked up root methods that idiots like me can follow. Other than the root issue, I have loved the S4.
My phone before the S4 was an HTC Incredible, which was awesome. And with a Verizon recently locking up the S6 with updates to block rooting, I thought HTC might be my ticket once again. Then when I came here to do some research, it seems Verizon has similarly locked down the One M9.
So how difficult is it to root the M9?
I saw something about sending the phone off to a gentleman who could unlock the bootloader. That would be an option for me since I don't have to have the phone immediately. If I do that, does that solve the root difficulty permanently?
On top of all that, how is the One M9 as a phone? Is Sense still similar to previous versions, etc.?
I'd love to read your thoughts!
Click to expand...
Click to collapse
Well, first of all, this question has been asked several times here and there are a handful of responsive threads that answer some of your questions.
1. It's very easy to root the M9, if you have access to one of the individuals in the java card thread. I drove a few miles west on the PA turnpike to hook-up with @dottat after acquiring my M9 and had a rooted, bootloader-unlocked handset within minutes of our meet-up. I had someone else waiting in the wings for me to mail it to him, but this was more convenient. If you aren't near anyone on that thread's map, you'll have to send the handset out. Yes, that's harder than the "gool ol' days" with many of the exploits available on xda and elsewhere, but that's life now.
2. As a phone it's great. If you happen to get another call from someone else with advance calling it is to telephone audio what FM is to AM.
3. The camera is very good. No OIS, but with 21 megapixels, it's pretty darn good. The front facing camera, an ultrapixel camera, is excellent for selfies, if you're into that sort of thing (I'm most assuredly not).
4. The processing speed is very quick with the multi-core processor.
5. Sense 7 is much more unobtrusive than prior Sense versions. I like it very much. I had even flashed a Sense 7 ROM on my M8 because I preferred it to Sense 6.
6. The device can get hot, especially in a sunlit care when dashboard mounted with BT audio and GPS in use. Very hot. The solution is run it naked and on a charger, otherwise your battery will die before you arrive anywhere. Overheating is less prevalent out of sunlight.
Hope that helps.
Just How Hot?
Thanks for the great feedback! I didn't know about the heat issue.
Here's another question: I use my phone at LOT for tethering. I keep it plugged in because the battery drain is so intense while doing so, but if the screen is on for any amount of time even the S4 gets HOT to the point of shutting down.
I'm not saying that's a flaw in the phone ... that's a lot of computing/work for such a small device, but ... do you think the M9 would be unworkable for my intense tethering?
Buckhunter206 said:
Thanks for the great feedback! I didn't know about the heat issue.
Here's another question: I use my phone at LOT for tethering. I keep it plugged in because the battery drain is so intense while doing so, but if the screen is on for any amount of time even the S4 gets HOT to the point of shutting down.
I'm not saying that's a flaw in the phone ... that's a lot of computing/work for such a small device, but ... do you think the M9 would be unworkable for my intense tethering?
Click to expand...
Click to collapse
I don't think tethering alone would do. Direct sunshine and GPS seem to be the main drivers
Sent from my Nexus 6 using Tapatalk
The heat is a luck of the draw thing too. My phone is caseless mounted to the dash and charging any time I'm driving. At a minimum it is playing music and has the GPS active. A lot of times it is running waze/google maps or Ingress. While it will get hot to the touch, I have never seen the actual overheat warning. I think the highest I've seen is ~118°F battery temp. I don't usually check the CPU temp.
Took the Plunge
Thanks again for the feedback, guys. I went ahead and ordered an M9 last night.
Will be sending it off to get bootloader unlocked as soon as it arrives.
Don't know what I'd do without XDA!
I just got a VS986 to use with a GSM carrier etc. Anyway I updated it to the lastest MM 24c and not sure if its the phone or the software as I did not test 13B that it came with.
At times its a little sluggish in say the Pokemon Go app once open for a few minuets. And also it has random freezing to the point that the phone will actually just reboot as it cannot recover from it. And battery life is not so great, not sure but that could be the actual battery itself.
Keep in mind this phone is a 2nd line and it mostly just sits so noticing the issues is a big concern considering I barely use it.
So im guessing its just best to go back to 13B, and still possible from 24c correct?
Thanks!
hyelton said:
I just got a VS986 to use with a GSM carrier etc. Anyway I updated it to the lastest MM 24c and not sure if its the phone or the software as I did not test 13B that it came with.
At times its a little sluggish in say the Pokemon Go app once open for a few minuets. And also it has random freezing to the point that the phone will actually just reboot as it cannot recover from it. And battery life is not so great, not sure but that could be the actual battery itself.
Keep in mind this phone is a 2nd line and it mostly just sits so noticing the issues is a big concern considering I barely use it.
So im guessing its just best to go back to 13B, and still possible from 24c correct?
Thanks!
Click to expand...
Click to collapse
A vs986? I was under the impression that the vs986 was CDMA for verizon. But you mention GSM? AT&T uses GSM. But anyway onto your problem. Your problem sounds like the phone may be overheating which is a known problem for the earilier G4's. The best way to know for certain is take out your battery and look at the sticker under the battery for the Serial number. Look at the first 3 digits and reply back with what they are. examples 506,508,509,510 etc etc etc. If the number is below 511 EXPECT THE PHONE TO DIE!..... Originally 510 was supposed to be on the safe side. But I have a 510 that did the bootloop just 6 monthes after buying it brand new... I may have gotten a faulty one though. But for certain anything 508 or lower to my knowledge is GUARANTEED TO DIE. So make backups if you haven't already. As for going back to 13B you can try but I don't think it will make a difference when it comes to the phone shutting down. About the only reported benefit of downgrading is battery life. I personally liked MM much better. Just my opinion though.
phonepie said:
A vs986? I was under the impression that the vs986 was CDMA for verizon. But you mention GSM? AT&T uses GSM. But anyway onto your problem. Your problem sounds like the phone may be overheating which is a known problem for the earilier G4's. The best way to know for certain is take out your battery and look at the sticker under the battery for the Serial number. Look at the first 3 digits and reply back with what they are. examples 506,508,509,510 etc etc etc. If the number is below 511 EXPECT THE PHONE TO DIE!..... Originally 510 was supposed to be on the safe side. But I have a 510 that did the bootloop just 6 monthes after buying it brand new... I may have gotten a faulty one though. But for certain anything 508 or lower to my knowledge is GUARANTEED TO DIE. So make backups if you haven't already. As for going back to 13B you can try but I don't think it will make a difference when it comes to the phone shutting down. About the only reported benefit of downgrading is battery life. I personally liked MM much better. Just my opinion though.
Click to expand...
Click to collapse
Yeah I know all about the bootloop issues, (I run the G4 back to stock guide) But I haven't owned a G4 since November. I have desided to return it yeah it had overheating issues, but the random reboot issues occured when phone was not being used. Running 13B was AWFUL it would go into what I thought was the forever bootloop for about 10 min and then randomly bootup haha. MM was not so bad besides the random reboots for no reason.
Yes I was using the VS986, The Verizon Variants are factory unlocked works perfectly fine with a GSM carrier. The 4 I bought back in November worked just fine as well. With no the exception with the MM update the annoying invalid sim icon is now gone.
I ordered an HTC One M9 to see how well it goes and once again went with the Verizon variant due to being cheaper and factory unlocked.
The last phone I had was a Galaxy S2 and rooting and installing a new ROM was quite simple. They even had directions+tools to revert back to stock... What's the deal now?
What is dm-verity and how do I figure out if the ROM I want to install has it.. disabled? enabled?
I have no more warranty so I'm not worried about triggering knox.
This latest update has basically fried my battery... the battery discharges in about 3-4 hours using youtube red with airplane mode enabled, and the battery is also quite warm (at least 100 degrees F!)
I just want to be able to disable/enable services I want.
I'm on SM-G925T on 6.0.1/G925TUVS4EPH2, specifically. How do I find compatible ROMs and roots? I don't want to brick anything.
I understand this is a long shot since I see so many other posts with no replies but, I'm kind of desperate. I'm actually worried my phone might explode because of how warm it gets now.
I just got the phone about two days ago, did all the 8000 updates via OTA (phone came with 5.0.2) and landed on the 6.01 EPH2 that you're on and my battery life has been absolutely horrible as well. I'm thinking about returning the phone over it. Idk what to do.
xy34 said:
The last phone I had was a Galaxy S2 and rooting and installing a new ROM was quite simple. They even had directions+tools to revert back to stock... What's the deal now?
What is dm-verity and how do I figure out if the ROM I want to install has it.. disabled? enabled?
I have no more warranty so I'm not worried about triggering knox.
This latest update has basically fried my battery... the battery discharges in about 3-4 hours using youtube red with airplane mode enabled, and the battery is also quite warm (at least 100 degrees F!)
I just want to be able to disable/enable services I want.
I'm on SM-G925T on 6.0.1/G925TUVS4EPH2, specifically. How do I find compatible ROMs and roots? I don't want to brick anything.
I understand this is a long shot since I see so many other posts with no replies but, I'm kind of desperate. I'm actually worried my phone might explode because of how warm it gets now.
Click to expand...
Click to collapse
Thus device has been horrile for me too...
I have been trying to find folks who could actually communicate and help a little too..
Had a galaxy 3 in 2010 and a s4 in 2014, both were easy... bootloop, flash again.. not much risks..
Here we cant even remove the batteries and a lot of rhinfs that can make it stuck....
I do have root and twrp recovery btw..
If you want help getting those, just install telegram and search for user DSN .
I can help faster there and also link up to a few rom threads where people are quite active incase for help
I've been modding and ROMing for what seems like almost 10 years, the ROM development on this phone is horrible, I blame Samsung for this, too many variants, had the S6 on 4 networks and S6 edge on 4 networks, Hopefully Google makes a really nice new phone or I'm going to the other side.
I guess it's starting to make more sense now. Samsung obviously tried to squash custom build efforts by releasing so many different variants. It's a bit reassuring that people are having the same problems as I am...
To the person who just got the phone - RETURN IT!
Ironically, after I did a lot of browsing on this site during my morning commute, the phone started behaving better. It's still slow (not in my OP but it's definitely freezing whereas this wasn't an issue before) but the battery life is back to normal-ish levels and it hasn't warmed up on me. Maybe just keep browsing this site? LOL
Thanks, Samsung... I used to love the Galaxy line but this is some real Apple-esque **** (y'know, the whole updating the phone before the next generation gets released and having it run slow as **** thing.) Just Google the issue and there's lots of claims. I remember reading a reddit post where an Apple employee or cell phone repair store employee was saying that he'd have an influx of customers just before a new phone release.
It's all speculation but I wouldn't be surprised. They (Samsung) just did it after S7 got released. Too bad I'm stuck paying $30/month for this phone for the next two years. Never should have updated! It was perfect before all this.
That was me. Return it for what though? There's not much else in the price range that I was able to put down for a down payment that tmobile offers.....I put 276 down and the phone cost 499 total. The G5 is also 499 but I see nothing but complaints about it.......the S7 and S7 Edge they wanted close to 450 down and I just couldn't afford that so I went with the S6 Edge. What else is there?
carnivalrejectq said:
That was me. Return it for what though? There's not much else in the price range that I was able to put down for a down payment that tmobile offers.....I put 276 down and the phone cost 499 total. The G5 is also 499 but I see nothing but complaints about it.......the S7 and S7 Edge they wanted close to 450 down and I just couldn't afford that so I went with the S6 Edge. What else is there?
Click to expand...
Click to collapse
Look into the LG G4, maybe. Same era as the S6 but it's got a removable battery and external storage and I think it's easier to install custom software and root, but hopefully you won't need to if it runs well. Do your own research, yknow! Don't blindly follow anyone's advice, obviously. Let me know what you decide.