I have a Moto G (Motorola edition) with the latest updates. All stock -- no unlocking, no root.
This morning, a sudden vibrating in my pocket made me look at the phone, and I noticed it was rebooting. I was steady in my pocket, official Moto flip shell closed.
It booted up to the point where my SIM asked for the PIN code. If I hadn't noticed the boot buzz then I would have had a non-functional phone for a long while -- I usually do not look at the phone every couple of minutes.
Anyone recognize this? Any ideas what could have caused the reboot?
The battery was, and still is, sufficiently charged.
sciurius said:
I have a Moto G (Motorola edition) with the latest updates. All stock -- no unlocking, no root.
This morning, a sudden vibrating in my pocket made me look at the phone, and I noticed it was rebooting. I was steady in my pocket, official Moto flip shell closed.
It booted up to the point where my SIM asked for the PIN code. If I hadn't noticed the boot buzz then I would have had a non-functional phone for a long while -- I usually do not look at the phone every couple of minutes.
Anyone recognize this? Any ideas what could have caused the reboot?
The battery was, and still is, sufficiently charged.
Click to expand...
Click to collapse
Had the same issue just a minute a go.. No idea why it rebooted..
I also expierenced this issue at 93% battery so it was pretty full. But i got a sudden drop from 100 to 96 when it was in stand by..
Verstuurd vanaf mijn XT1032 met Tapatalk
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.
Hi all,
I would really appreciate some help with my issue on the HTC One S. I've been looking for a solution for weeks now and still don't have a clue on what it could be happening.
The PROBLEM is this: sometimes my One S turns off suddenly. Next, I turn it on but it is very likely to do the same again in a few minutes. If I am lucky, it turns on and works for a while (which can be from hours to days), but if I'm not, the phone is completely dead (not even responding to charge and no matter how I try to boot it) for hours or even days. Finally, I get it again to life when I see it starts charging the battery (always from zero... even if it died at 80% battery).
I had a video on youtube to show you what it happens. What a pity I can't post it here cause of xda-developers rules!
Do you guys have any idea if this could be a battery issue/software issue or anything else?
Additional information:
-Glass is broken (phone works perfectly) but didn't have this issue for one month since the incident.
-Phone has been working now for 2 weeks (it will do it again... I'm quite sure)
-I dropped the phone into the snow a few days before it started to act like this, but dried it quickly.
Sounds like faulty battery or faulty battery connection. That would require opening up the device and either replacing or reconnecting the battery.
Thanks, it is always good to have a second opinion, two minds always think better than one
Just in case anyone else would like to give his opinion, this are other (maybe) useful symptoms: phone reboots in the middle of the night, or, if already turned off, it turns on (and off again sometimes) by its own. Also, sometimes, just before turning off, screen freezes for 1 or 2 seconds. The phone has its bad and good days (thankfully good days are more frequent as time passes), but, in its bad days, it turns off many many times and sometimes it doesn't even completely reboot, I just see first screen then nothing.
Also I have been using car chargers not from HTC in the same while the phone used to have this behaviour (like the Kindle car charger). Actually, once, while using one I bought on eBay, I got a message saying something like "phone has been disconnected from charger to avoid damage".
What could this mean? Battery fault can make this? I appreciate any similar experience or opinions
Bateries are durable now days, I'm afraid that the snow got into your phone and caused a short circuit on motherboard.
Sent from my HTC One S
my nexus 5 d820 16 gigs would randomly shutdown for no reason, it wouldn't turn on without plugging it in. i was rooted and running cm11, then i tried carbon ROM, then c-ROM. c-ROM started to give me problems so i factory reset and switched to carbon but the problems remained. then i unrooted, thinking that root was the problem but no signs of improvement, so i re-locked the bootloader but still the problem remained. it would sometimes also shut down if i unplug it and would always forget my WiFi connection for some reason. help me please. thanks in advance.
Well sounds like a hardware problem since you already unroofed and relocked boot loader I would say call lg and get a warranty replacement
Sent from my Nexus 5 using Tapatalk
Sorry to bring this post back after a long time.
I had a similar but not exactly the same problem.
2 nights ago I left the phone on the table, and a few minutes later, when I picked it up, it was off (It had about 60% battery left when I put it down).
Then it would not wake up; I kept the power button pressed for like 20 seconds to force a shutdown, and then tried to power up with no luck, so I'm thinking I'm screwed.
I tried again and it powered up to a graphical noise screen as seen in the attached image, but then it showed the boot animation and came back to life.
This morning it shut off by itself while listening to music (Google play), but powered back on right away...
Rooted 4.4.4, stock ROM, Xposed with Greenify, Amplify and wakelock detector (all latest versions). But no changes for a couple weeks before this started happening.
No specific app running (at least in the foreground).
Any one knows where I can find any kind of log or trace about this, if any at all?
Has anyone experienced this as well?
Thanks
Hiya,
I've got this issue for about two or three days now. Quite often, when I take a picture with stock Google camera app, my Nexus turns off instantly. Then, when I try to turn it on again, it often turns off again in about one minute and usually it shows almost empty battery (even though before shutdown it was nearly full).
First it has appeared on stock rooted 4.4.4, the phone tried to boot like 10 times, so I erased cache and dalvik via TWRP, but then it didn't detect SIM card and showed unknown baseband. I solved it by flashing bootloader and radio.
Then, I installed a stock 5.1.1, rooted it again (I thought it would solve the issue), but the same problem with camera occurred.
So, could it be hardware issue? How to debug it?
Thanks for any response.
Sent from my Nexus 5 using Tapatalk
Hi,
Probably not an answer you'll like, but I've experienced similar symptoms on my HTC Sensation with HTC "stock" android on it (phone turning off and then having much less - and sometimes MORE - battery-time left after booting again). I never had an answer as to how to troubleshoot it, nor did I get help (from HTC) to solve the issue until at some point I found that the battery itself wasn't seated properly, and after putting some paper between battery and case to put more pressure on it (which doesn't seem possible with the N5) the issue magically disappeared...
Reference: http://forum.xda-developers.com/showthread.php?t=2090170&page=2 (not my topic btw)
Very recent N5 topic: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-random-shut-off-battery-drops-t3162481
A tip in that topic: "it doesn't happen when connected to power cord". Possibly you can try that to add it to the elimination-process?
Hope you can get it sorted!
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
ZMaissi said:
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
Click to expand...
Click to collapse
Thanks, that is sort of what I was thinking. I suspect the boot partition is corrupt. But, wasn't sure being a new customer with Verizon.
Hey can you link me something about how you downgraded your droid ultra from SU6-7.2 to SU6-7
LOL, just flash SU6-7 (CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml) with RSD-Lite. That's the easiest way.
rfunderburk39 said:
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Click to expand...
Click to collapse
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Mangu said:
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Click to expand...
Click to collapse
In the case of my phone, you could hold the power button in for a long period of time and then release and still nothing, not a flicker. I did not try voice commands, not a bad idea, but I did not want to open the phone due to the fact it was being replaced (further risking a decline on replacement).
On a similar note, the new unit seems to reboot at least once daily.