has anyone else had their phone shutdown while it was sleeping in their pockets? It never happened before this outage. I have been keeping by mobile data turned off, ans it seems that when I lose WiFi and it can't jump to mobile data it just shuts my phone down. Is this bug affecting anyone else or is it just my device?
Sent from my HTC Rezound using XDA App
shut down victim
Hi, I am unsure if my shutdowns were the same as your circumstances but i thought i would let you know I had the random shutdown problem as well. I had my phone for about 3 days, it shut down once in my pocket and pretty much every night after that; there was no reboot after the shutdown...it was off when I woke up in the morning (not the best when trying to arrive to work on time). I actually returned the phone for a new one and have not had a problem since. Not sure if this helps, but at least you know you aren't alone
Related
i swear i have the worst luck. haven't even had the phone a day and already i went to check the time and the phone was off and wouldn't turn back on, had to pull the battery. now just a few min ago i felt a vibration in my pocket so i took the phone out and it was starting back up "starting services". it must have rebooted in my pocket.
if i go back into the sprint store for this they are not going to be happy to see me again after all the strings they pulled to get me into this phone after being well out of my 30 days with my 3d.
Edit: i just went to sprint and they tested the battery and said it was bad. maybe that's why it was charging so slow? hooked up to the charger the phone died while using it. that seems way too slow right?
Edit again. The new battery didn't fix my problem.
Ask for a new back cover. There have been numerous post about how some back covers are not a tight enough fit allowing the battery to break contact which results in a reboot. Sprint appears to be aware of this as there are reports of stores having spare back covers to give to people who request them.
mine had the updated cover with the rubber/foam inside. the phone was faulty, they replaced it and it looks like the problem is solved.
last night when i got the phone and i put it on the charger i started using it and it sucked the 15% of battery out when on the charger. i started charing at 7pm and by 2 am it was only at 50%. pretty sure some thing was wrong with the phone. this new one charged up in about an hour.
Mine does the same at random times of the day.... went to sprint and they told me it was a software bug... that sound right to you guys?
Sent from my MB855 using XDA App
mercNstein said:
Mine does the same at random times of the day.... went to sprint and they told me it was a software bug... that sound right to you guys?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Mine has been fine since it was replaced.
Sent from my MB855 using Tapatalk
I've had my phone reboot first thing in the morning when I first turn it on. When it happens, it reboots twice and then no problem thereafter. It's done this three mornings so far, rebooting twice each time. It's happened both before and after rooting. I wonder if it has to do with being fully charged and reboots until its no longer fully charged. Luckily it's not every morning and it's easy to live with until the update is released. I know we have the leak, but I'm waiting for the official update.
DualSportDad said:
Mine has been fine since it was replaced.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
ok cool ill look to replace mine then.
I had the same issue with reboots when I first started it up after it activated it would restart few times. Then today I had 60% battery life left and I powered off the phone and started it up again it said I had 3% battery left. Not sure whats going on. Also I am having bluetooth headset issues. My top of the line motorola finiti constantly loses connection and has to regain it. I have also experienced the call audio issues on several occasions. Unfortunately for me I was given this phone by Sprint and can't return it for another device. My only recourse is to wait till Motorola comes out with a firmware update.
Everything has been fine with my G for weeks. Then today, I heard the boot animation and pulled it out of my pocket to see it rebooting. I thought I had bumped the button, so no big deal. Waited for it to boot, then unlocked it and checked mail.
I set it on the couch next to me, then a few minutes later, I reached over to turn it on and it wouldn't turn on. I held the power button several times for extended periods. I finally held power and volume down and it rebooted.
Kind of alarming, since I haven't changed anything. No new apps, no hacking, rooting, modding. It's stock and I haven't changed anything about it in the last week.
Anyone else experience anything like this?
I've had the problem of random reboots and it being stuck on the yellow god screen I'm guessing download mode so your not alone. I'm sure it's a software glitch mentioned by someone earlier hopefully with the jellybeaner it gets worked out
Sent from my LG-E970 using xda premium
Yes im having this issue too, it happens on any stock rom i run. even stock roms that have been debloated like Savvy, ive tried proper custom roms but they give me a blue screen external modem crash screen more often than the random switch off i have with a stock rom. However the switch off has happened to me twice today. its happened overnight before causing me to be late for work and ive missed many phone calls.
Im sick of this issue and am currently in the midst of speaking to the seller off ebay for warranty return (it was bought new unlocked unopened from an ebay store)
Problem: Phone shuts off and often upon restart the battery displays low to no power when it was at full charge before shut down.
Isolating the Problem
Will only shut down if mobile network is turn on and has been in use
Will not shut down if left plugged into a power source
If issue occurs you can recover by rebooting the phone while plugged into a power source
Using a wi-fi connection will not replicate the problem
Is not an issue with third party as issue is replicated with "Safe Mode" on
Backstory:
My phone is rooted and had/has [ROM] Official Thunderbolt ICS running. At the time I did not have OTA Killer flashed so when the recent OTA came out it tried to install and in my ignorance/stupidity I accepted. It obviously didn't work and I went back to the forum and found out why.
A friend of mine has a Thunderbolt completely stock and this same issue has been happening to him. From what Verizon's TS has said this is a known issue that is hit-and-miss and they replace your phone until you find one that works (took him 3 times). That's all well and good except my phone is rooted and they'll charge me $300 for the replacement.
(Finally) The Question:
Does anybody else have the know-how to fix this problem? I can give whatever specs you would like and am fairly good at keeping a log of what I did/what happened. (necessary for IT and troubleshooting)
Replace your battery. The battery you have is bad.
Sent from my Infected Rezound using Tapatalk 2
Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.
I have two V60s on A11 and noticed for the past two nights one of them will reboot while charging. Only way I notice is because I have to use my PIN in morning to login in instead of fingerprint and one app indicates a restart. This is a replacement V60 that I have had for two days.
Any thoughts?
Are you sure that it's a reboot? I noticed that if I leave my phone idle for a couple of hours (not sure how many, maybe 4 or more?), some kind of security kicks in requiring that I enter my pattern instead of using the fingerprint reader. Pretty sure this has happened both on Android 10 and Android 11. I don't commonly leave my phone idle for 4+ hours during the day, but it has happened just enough for me to notice it. And it definitely wasn't a case of the phone just randomly rebooting itself on me in the middle of the day. THAT, I would have noticed.
Positive it is a reboot. I actually saw it happen this morning. Phone will just shut off and T-Mobile reboot splash screen comes on. I think it is not related to fingerprint reader bug as I have disabled the fingerprint reader on my lock screen/AOD.
Actually been noticing it happens now even when the phone is not charging. I wish there was a way to see which app is causing the problem or get some kind of log to know what is going on.
Hmmm, other than trying to isolate which app is causing the problem, I'd probably suggest a factory reset.
I actually removed all apps and left with factory defaults and it still rebooted during a charge. I have sent the phone back and awaiting a replacement. (This one was the 2nd year promise replacement for a dying G8)
I had to ship the phone back and get a replacement. Everything I tried did not work to stop reboot while charging.
My LG started to freeze, then reboot several times a day, while in use as well as overnight. Sometimes boot loops directly after the logo, so not OS or app related, also without SIM or SD. I had the battery changed (still in warranty), but that behavior continued. So I got a replacement phone yesterday, since it was obviously a hardware issue (I guess it is a RAM failure).