Can anyone think of a reason why my phone would reset itself ONCE each time I put it on charge after about 10 - 20 minutes? Surely if the battery were overheating then it would continually reboot itself as the phone remains plugged in, but nope; just the once. It doesn't feel particularly warm to the touch when it happens, either. I thought it might be performing some maintenance on itself the first time it happened, but then I released that wasn't likely when it kept happening. Any ideas?
Undesirable said:
Can anyone think of a reason why my phone would reset itself ONCE each time I put it on charge after about 10 - 20 minutes? Surely if the battery were overheating then it would continually reboot itself as the phone remains plugged in, but nope; just the once. It doesn't feel particularly warm to the touch when it happens, either. I thought it might be performing some maintenance on itself the first time it happened, but then I released that wasn't likely when it kept happening. Any ideas?
Click to expand...
Click to collapse
There are two kinds of reboots, the soft one, and the other one .
Do you see the first Motorola Logo and vibration or only the one with the planet when this happens?
If you can provide some logs that would be helpful.
It's a hard reboot with the Motorola logo and single vibration when it happens, and I'll have to look into how to bring up a log of the issue. I'm running stock 5.0.2 on an XT1524.
My wife's phone was doing the same thing (hard reboot with Moto logo and single vibe). It happened mostly at night after she'd gone to sleep, so she barely noticed it. The external speaker stopped working last week as well, so I have a replacement coming tomorrow.
New phone also is hard rebooting. Not as often (I don't think) as the previous, but it's still concerning.
Sent using XDA Free mobile app
One more follow up:
I haven't seen another random reboot since the latest OS update.
YMMV
Sent using XDA Free mobile app
My previous Moto E (first gen) did the same. Only way to fix that was reflash stock firmware via adb.
Same problem here. Always when it getting to ~58%
Sometimes, after reboot Moto E is showing message "Android is upgrading"
Strange, but i can live with this :E
Related
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 got an LG G5 from TMobile about a week ago, and have been having nothing but problems. The first few days seemed okay, but then it started getting really warm, freezing and crashing a lot. I reset the cache and that seemed to help for a day or so, but I just now woke up to a green screen and tiny text on the phone. I couldn't read any of it (don't have a magnifying glass handy) and the phone was unresponsive.
I pulled the battery, now the phone won't even turn on. I can feel it vibrate once when I press the power button, but nothing else. If I plug it in I won't even get the battery charge icon or anything.
Any ideas? I'm thinking of just getting it replaced tomorrow.
It seems to have come back. Not sure what I did, but after many battery removals and plugging / unplugging it finally decided to come alove. Reboot about 10 times and now it's back.
Strange.
It started crashing and freezing again. Ended up getting it replaced at t-mobile.
Treytor said:
It started crashing and freezing again. Ended up getting it replaced at t-mobile.
Click to expand...
Click to collapse
Yeah when the device starts acting up like that it's better to get it replaced fast instead of waiting to see if it resolves itself
Sent from my LG-H820 using XDA-Developers mobile app
Any trouble with your new device as of yet? Did they tell you the cause of the problems?
Guys, I need your help.
So, I just received a call with my phone while driving and after a while? I realize no activity. I check & see that it is stuck on the "your device software can't be checked for corruption"
If I remove the battery, put it back & connect the charger, it charges & shows charge progress.
I can get into the factory reset using hardware keys but I can't get to TWRP.
I removed the sdcard and everything seems to be intact without corruption.
There was this one time it got in for some few minutes then restarted to verification stage.
It doesn't overheat.
Bootloop or just maybe os/recovery failure??
well if it keeps doing it probably but if not idk. so mine i was browsing the internet with firefox then it randomly restarted it did not feel hot so i pulled the battery and restated it and every time it would get stuck at the device software can not be checked for corruption and would stay there for 2-3 min then restart and it would do it again. Thats how mine went into bootloop. i left it on for 1 hour and was able to get it to boot in android for 30 sec but then resarted and could no longer get in to os. i could only get it in fastboot and factory reset(which did nothing).
Mine started randomly rebooting a few weeks ago. I just exchanged mine the other day. I would advise you to try and backup any important data now if you can or get it off the phone. I like my v10 but I'm disappointed in LG for having such a widespread problem like this.
Sent from my LG-H901 using XDA-Developers Legacy app
As nothing worked for me & LG was being difficult, I have dumped the phone for now (will probably resurrect it when the MoBo is available).
I purchased a Huawei Mate 9 four days ago and I'm very glad i did.
Thanks everyone.
Ok I've had the Moto Z for a while and its a great phone. Or it was until a few weeks ago. In the space of a couple of weeks a few official updates were sent to my phone and thinking nothing of it I updated as requested. The last update has seriously messed the phone up.
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
What I've tried to do about it:-
- I've tried running in safe mode, which makes no difference
- I've tried a full reset, which makes no difference
- I even unlocked the bootloader and installed a custom OS (Lineage). Thinking that obviously this will wipe out the new update from Lenovo and the phone would have to work properly again. But no, nothing changes, somehow Lenovo have done something beneath the OS that's causing these problems.
The question:-
Does anyone have any idea what could be causing this or have you at least seen these issues before?
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
apocalypse_bg said:
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
Click to expand...
Click to collapse
The point of my post is obvious, I've got a issue with my phone and want to know if anyone has seen this issue with the Moto Z before and if they have any idea what may fix it. The question is right there near the end:
"Does anyone have any idea what could be causing this or have you at least seen these issues before?"
Click to expand...
Click to collapse
apocalypse_bg said:
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
Click to expand...
Click to collapse
I've tried a different ROM:
- I even unlocked the bootloader and installed a custom OS (Lineage).
Click to expand...
Click to collapse
Honestly don't know how my post was unclear at all, but I've gone and tried to make it even more clear with a quick edit, hope that helps.
I have exactly the same problem. For me it occurred after updating to nougat. So fare I tried nearly everything. Disabling nearly everything to the bare minimum, custom ROMs, resetting, trying to flash only parts of the Android 6 firmware (modem, Bluetooth, DSP) since a complete downgrade is not possible, using all kinds of battery tools with a rooted device, using custom kernels... I always ended up with a constant battery drain of 3 to 8 percent per hour no matter what I did. Same in flight modus. Since under Android 6 the device didn't show this behavior I think that the problem must be somewhere in the firmware beneath the OS level. An the cruel thing is that sometimes without a reason for maybe an hour or two my moto z doesn't drain an works fine so that I do not believe in a hardware problem.
Thanks for the post. Yeah it seems like something has been changed underneath the OS. I know that sometimes memory config gets changed with newer Android operating systems (at least I think so?), but could that cause all these problems?
BTW, do you have all three of the problems I mentioned? Battery drain, sound stops working and charging stops working?
Since in this condition the Moto z is not really usable for me I switched back to my old phone and I am not using it that much as a daily device, I cannot really tell about sound or charging problems. So far I did not notice those problems.
DonnieDio said:
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
Click to expand...
Click to collapse
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
DonnieDio said:
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
Click to expand...
Click to collapse
None of the above ever happended to me
StarStorm said:
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
None of the above ever happended to me
Click to expand...
Click to collapse
I've never seen anything like it before. Its so random as well. I mean yesterday I rebooted and then charged the phone before I left for Football at 4pm. At about 11pm that night I heard the battery low sound (45% of the battery had be used by Android OS..). First thing I thought of was that usually the phone wouldn't still be making sounds by now. Since as I said earlier usually the speaker stops working along with charging within a hour or so of a reboot and this had been over 7 hours without a reboot. So I tried plugging it in and it started to charge. But then when I woke up this morning again the sound was disabled and it won't charge, it just took longer for the problem to occur this time..
How can we stop asking to update to this patch?
I has already disabled this on the developer preferences but still asking every 10 minutes
Any suggest please
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
doug107hk said:
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
Click to expand...
Click to collapse
Yep I've also had that as part of my problem, though it had only happened a few times over the course of the month so I forgot about it with all the other problems I mentioned going on.
Basically my phone would be sitting on, say 40%, and after a reboot it would start up in the single digits.
I recently tried changing to a custom kernel to see if maybe that was causing the problem (I'd already tried changing OS). But all the problems are still there using the new kernel. Think my next step should be to try to go back to a 7.0 Android version. Are there any custom Android ROMs using 7.0?
It is said that the Motorola Manager can rescuer lost data even if the data has been covered on phone , is it true ?
Just curious what came of this. My Z, unrooted, has started running crazy hot and the battery life is not good. 6-10 hours. When I connect it to my Anker PowerDrive 2 in the car, the battery actually discharges faster or I get the slow charge warning.
Hi I have exactly the same problems as the op and tried resetting to no avail.Its driving me nuts.
Short update about the massive battery drain problem: like I wrote above, in the past weeks I tried everything from custom kernels to custom roms, resetting, deleting and so on. Nothing helped. So I went back to stock and didn't use the phone the last weeks. Today I read in an other thread about bluetooth problems that a fix for the not working bluetooth was to activate flight mode, restart the phone and deactivate flight mode. So I activated flight mode, pressed the power button for 10 seconds or so until the phone restarted an deactivated flight mode. And now the absolute strangest thing happened: for the last 5 hours the phone lost 0% battery in standby with wifi and lte on. Since I did all the mentioned things above without any effect I do not understand this at all but right now I think that this could be a (temporally) fix also for the battery drain problem.
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).