A few days ago, my phone got pretty hot while I slept. But everything seemed fine until last night. I only bring up the heat because that's literally the only thing I can think of that might have caused this problem, even if there were a few days between that event and when the phone started behaving strangely.
Status:
Verizon SGS3. On CM11 nightly from about a week ago with the kernel it came with.
Issues:
I can't boot the phone. It'll quickly show the Cyanogen logo and then shut down again. Even if I'm on the charger, it'll just shut down. The battery will sometimes show 0% and charging, then I'll try it again a couple of minutes later and it'll show 87% and charging.
I did manage to boot the phone a couple times. It lasted long enough until I was able to get to the main screen. After a couple minutes, the power menu started flashing on and off showing the reboot/screenshot/power off menu. Like very quickly. Then the screen started turning on and off rapidly.
One of the times I managed to boot the phone, I was able to do a factory reset from settings. I reset it. The problem persists. I've tried two different batteries. Both batteries work fine in another SGS3 I have, but not in the one that's causing all the problems.
Any ideas?
Related
So over the last few days my phone seems to have settled into some sort of weird pattern with reboots. Although there are outliers, in general it always seems to reboot between 19-24h of uptime and nearly always at like 45 or 50 mins past the hour. It's the most bizarre thing in the world and why I think there's some funky software doing it. I don't have true random reboots, but I can't figure out what it is that is doing this. Very odd.
In all cases my phone is sitting with the screen off (I've NEVER had a reboot while using the phone/screen on) but it doesn't matter what radios are on, WiFi, BT, GPS (can be off or on).
Last time I ran "CatLog" a logging app from Market and had it write to SD logs and a reboot happened but it only by default writes every 200 lines so the last line in the file was probably not the last line in the log. I'm going to try again later and set it to write every line or few lines so I can see the last entry in the log before a reboot. Might shine some light on it.
Just find it very strange since it's a very stable and capable phone for about 18hrs and then it just craps on itself. Very strange.
finally. I too just think it is some weird software or driver bug because I was running EB 1.0.4 FINE for like 3-4 days and loving it... then it started resetting almost hourly. I didn't install any other apps past my initial normal set of apps.
Even CM7, seems like it is fine for a few days, then gets crazy. As long as I put a new nightly rom on it every day, it's good.
I didn't have any issues with stock though and didn't seem to have issues with CM7 for a while until lately.
The leaked GB rom causes lockups immediately out of the gate seemed hourly.
I use CM7 as my main daily driver now but I think you are on to something. We are talking about the Screen of Death right? I don't think mine ever reboots, but gets stuck at the lockscreen where the the display comes up, swiping to unlock vibrates then the phone but doesn't change screens to desktop. The buttons and click/drag widgets work even though you are looking the lockscreen.
I've never had my phone powered off in my pocket or noticed it "rebooting". Mine just has the SoD that seems to follow your pattern idea. They may be related. Stock roms may reset once it locks up, where CM7 just keeps running in its locked state.
I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.
I just hope that update gets here sooner than later.
Sent from my LG-P999 using XDA App
I dunno. The tmobile jingle is pretty loud and I never hear it. CM7 has a silent one so possibly there but I dunno.
I use my phone pretty often and never had the suspicious that it reboots. My phone stays very cool during my usage compared to my nexus and other phones
My uptime was 4 hours since I reset it last. I'll monitor it with results. It'll be hard not to flash but I'll keep track and see how far I can keep it online.
i have not had any reboots or waking up to a dead phone ....with the only fix is a battery pull.... ever since I started.
1) my over night charging / long term charging to 100%... only on the LG charger that it came with. Only short term...maybe. less than an hour and not to a 100% charge on a non LG charger (car charger etc...)
2) I restart my G2x every morning when I take it off the LG charger..(after I take it off..I did it once while on the charger and had an issue... (there is definitely an issue related to when it charges to/ around 100% charge)
Just my 2 cents.
Pattern to my reboots - do yours have a pattern?
Hold Power and volume up simultaneously for about 10 seconds.
I've had my phone since Friday, but the only time I had the rebooting problem was this past Saturday when it rebooted four times within 15 minutes or so. Before the rebooting began, the phone had slowed down to a crawl, so I went ahead and rebooted it. After that, I sat it down and watched it reboot a few times on its own. Luckily my iPhone 4 owning co-worker was completely unaware of this issue since we tease and bicker with each other every day over Android and iOS .
mobilehavoc said:
I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.
Click to expand...
Click to collapse
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.
smashpunks said:
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.
Click to expand...
Click to collapse
What bloat did you remove? I've removed most but not all of it. Can you list it?
mobilehavoc said:
What bloat did you remove? I've removed most but not all of it. Can you list it?
Click to expand...
Click to collapse
Everything other than smart share, tegra zone and qik. Of course have nova and need for speed also.
Oh also have car home froze..
Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).
player911 said:
Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).
Click to expand...
Click to collapse
Yes I know the battery driver is part of the problem as can be seen on CM7 builds but what's odd is my time varies so for a long time it would reboot every 17-20 hours, now all of a sudden it goes to 36 hours before it usually reboots. Looking at logs it doesn't appear to throw any major errors before a reboot which implies that it's a a kernel panic or low-level fault. At this point I've given up on trying to find the issue since it's been repeated over and over that T-Mo and LG are releasing an update. Might as well enjoy the phone and wait for that to come out
Amen. Just keep flashing CM nightlies and you'll never worry about it.
I've been running CM 10 on my phone without issue (besides the whole touchscreen thing that wasn't a big problem for me) for several months.
I went to cm10.1 last week and my phone started having graphical artifacts on occasion (like an overheating gfx card) and eventually started shutting off randomly and restarting with 50% less battery than it had. I did a full wipe and put back on CM10, but it's still doing it, and has gotten progressively worse.
For the past couple of days my phone would work for about an hour, and then shut off and either come back on with 50% less battery, or not at all until I plugged it in for several hours (even if it had just been plugged in all night). Now, my phone has been plugged in for 24 hours and I can't get it to turn on at all. I've held the power button for 30 seconds, held power+down, etc.
When it was on it's last legs I wanted to do S-OFF and then go to stock so I could do the warranty, but the S-OFF process hanged when trying to push the first file.
Any help?
Thanks
slash178 said:
I've been running CM 10 on my phone without issue (besides the whole touchscreen thing that wasn't a big problem for me) for several months.
I went to cm10.1 last week and my phone started having graphical artifacts on occasion (like an overheating gfx card) and eventually started shutting off randomly and restarting with 50% less battery than it had. I did a full wipe and put back on CM10, but it's still doing it, and has gotten progressively worse.
For the past couple of days my phone would work for about an hour, and then shut off and either come back on with 50% less battery, or not at all until I plugged it in for several hours (even if it had just been plugged in all night). Now, my phone has been plugged in for 24 hours and I can't get it to turn on at all. I've held the power button for 30 seconds, held power+down, etc.
When it was on it's last legs I wanted to do S-OFF and then go to stock so I could do the warranty, but the S-OFF process hanged when trying to push the first file.
Any help?
Thanks
Click to expand...
Click to collapse
If it won't power on, screen won't turn on, power led doesn't light up even when plugged in, it's bricked. Sounds like you've got some serious hardware issues.
My s3 started randomly rebooting so I flashed a new more stable Rom.I haven't used the phone since the m7 came out so figured things needed updating. Still kept getting random reboots. Now I have a bigger issue, if the battery dies or the phone is turned off then the phone will completely act dead, no lights when plugged in to any charger, no charge animation, nothing. It will not power on. I've tried every button combination known, nothing works It just will suddenly power on one random time when you hit the power button, could be minutes, hours, even days later.At first I thought it was totally dead. Took the battery out for a day then put it back in and bam booted up like nothing had happened. Well it does this every time it's powered off completely or the battery drains. However you can do a restart a hundred times and it boots fine. I thought maybe flashing firmware would solve it but it hasn't. I'm wondering if this is sds failure? Is there a fix for the Verizon version? I am out of warranty and Samsung wants to charge an arm and a leg for repair.
Things I've done: new oem battery, different roms, Odin firmware (rt66), tested power button.
Thanks!
I bought a used GS6 a few days ago and several times the phone has either randomly rebooted, froze up, black screen, laggy etc. Several times when this has happened it appears as though the phone is still on but there is a black screen. Other times the phone just shuts completely off as far as I can tell. When this happens sometimes I can power down with pwr+vol down and get into the service screen. Other times I can't do anything at all with the phone for several minutes. In all cases when I plug it into the charger and let it charge a while it seems to come back to life.
At first I assumed this was a software problem, but after 3 data factory resets that does not appear to be the case. The problem crops up almost right away after the reset.
Then I noticed these issues always seem to start happening when the battery level gets down to about 65%. This is consistent. I can find no other consistent reason why these problems happen. When the phone is fully charged I don't seem to get these problems.
Any ideas what could be the actual problem (bad battery, bad main board, bad...) and any solutions? Thanks in advance.
I have a HTC 10 (new old stock) that I have been using for 2 months, on stock Oreo.
Everything was fine until last week when suddenly in the middle of reading an email the screen froze, a few seconds later the screen went black and would not boot up. Nothing at all, not even with a hard reset VOL DOWN + POWER or VOL UP + VOL DOWN + POWER. Tried holding it for A LONG TIME like 5 minutes, no luck. The phone had a hard brick and that's it.
Occasionally, after a few hours, I would try to reset it just for the hack of it. Or connect it to a charger (no charging light) Eventually after about 20 hours, it booted up again after I held all three buttons for a few seconds. Then it worked like nothing has happened.
It kept running for several hours, I charged it up to 100%, ran down to about 80%, then the screen froze again and died. Same thing happened, won't boot up at all. But if I wait another day or so, kept trying, it will boot up again.
I know the HTC 10 is known for it's horrible battery drain issue, and I have experienced that myself with another HTC 10, this is not it. The battery is running fine on this one. This is something else.
After doing this for a few iterations, I was able to figure out a pattern.
When the screen froze and the phone dies, it will not boot up no matter what you do. But for some reason something is still going on as the battery is still being consumed, a day or so later, when the battery is completed depleted down to 0%, and as soon as it hits 0%, whatever causes it to not boot unlocks and allow it to boot again, as long as you have it on the charger, the charging light will come up at that time, and as soon as it gets a little bit of juice, it will boot up again normally. Except when it does boot up, the date is reset to December 31, 1969 7PM.
After testing this for two more iterations, I am reasonably sure this is what's going on. Then I did a factory reset.
Once it's factory reset, I did nothing except turned on WIFI and didn't do any further setup except surf the internet a bit on WIFI, and about 10 hours later, it died again. Now I know, if I leave it alone for 20 hours, then plug it in for a few minutes, it will boot up again.
So here are my questions.
(1) The phone appears to have bricked during the 20 hours that is was totally non-responsive. What is happening that's consuming the battery?
(2) Does this seem like a hardware issue or software issue?