I just got my moto x 2014 pure edition. I charged it to 100%, did a software update to 5.0, then tested the battery by letting it stream a radio station for about 4 hours. The battery was still over 60% after that. I turned off the streaming radio and left the phone on my desk. An hour later it was shut off. Thinking maybe I turned it off, i turned it back on, then checked the battery status. Still over 60%. I put it back down on my desk. when I picked it up 5 hours later it was shut off again. Is there a power setting I missed that tells the phone to shutoff after a set period of time?
No not that I am aware of. Shouldn't shut down like that.
Sent from my XT1095 using Tapatalk
It was annoying last night - before shutting off it would reboot, causing the bright white light to light up my bedroom - being half asleep I started walking toward the light it thinking my time had come...but then I realized it was just the moto x rebooting itself. I was a bit disappointed.
After rebooting it shut off. I tried to do a factory reset, which seemed to be working but then Andy fell over with a red triangle sticking out of his chest and the message "no command" over him. At least that stopped the phone from rebooting itself and shutting off itself. After I woke up Andy was still prone with the red triangle sticking out of his chest. I shut off the phone and rebooted. It appeared to be back to factory reset because my apex launcher was no longer active, but I discovered that all my apps had been downloaded and my email address was still active.
I did another factory reset which seems to have worked. So far, 4 hours of idle and it has not self-rebooted or shut off.
the problem came back. It got worse, with the phone random booting about every hour. 1.5 hours on the phone with Moto help didn't resolve the issue. Phoned ended up being stuck on the screen with Andy on his back, a red triangle above his chest, and "no command" under him.
So back it goes after just 24 hours.
I've had the same issue with my phone randomly turning itself off. It's rather annoying.
Related
I have this installed [ROM] CyanogenMod-6.1.0-RC1 for Hero CDMA
I was running wifi tethering and installing a game called chess.
I heard my phone vibrate quickly and the screen was black. I tried to turn it back on. But nothing. So I removed the battery and waited a couple minutes. I cant get it to come on.
So I plugged it into a charger and the red/orange LED is on as if it is charging.
The phone will not even attempt to start up
Any ideas?
AcousticBruce said:
I have this installed [ROM] CyanogenMod-6.1.0-RC1 for Hero CDMA
I was running wifi tethering and installing a game called chess.
I heard my phone vibrate quickly and the screen was black. I tried to turn it back on. But nothing. So I removed the battery and waited a couple minutes. I cant get it to come on.
So I plugged it into a charger and the red/orange LED is on as if it is charging.
The phone will not even attempt to start up
Any ideas?
Click to expand...
Click to collapse
Phone just seems dead to me... probably just needs to charge for an hour or so
If it's not charge up and running by now, you'll need a new battery.
Thanksgiving day I had my phone on but was doing things around the house and when I went to check my phone it wouldn't wake. Holding down the power button, nothing, it was dead. I know the battery wasn't drained. So I plugged it into my USB and the light didn't turn on either. I sat staring at the phone for a few seconds to troubleshoot and it suddenly began to boot up and after everything loaded I could confirm it was half charged.
I'm running the same version of Cyanogen as you. Are you using the original battery or 3rd party? Mine is 3rd party.
Have you had other strange occurrences leading up to this? Twice in a week I woke up to find my phone on even though I know I shut it down the night before and not accidentally rebooted.
Since I was able to get my phone to boot back from temporary dead the phone has frozen twice while texting. I didn't battery pull or anything, it just rebooted by itself after a few minutes. I plan on switching back to my old battery to see what happens.
I got my Nexus 7 at I/O this year and I've been happily using it for nearly a month now. I don't know if my device differs in any way from one you can get form google play other than the white back.
Last night I was plugged into my wall charger at around 14% battery and playing SongPop with my girlfriend when my screen just shut off. It was like when you hold the power button on a laptop and BOOM, everything is black. It wouldn't turn back on so I unplugged it and plugged it back in. Got a charging screen so I let it set for a bit.
I came back maybe 15 minutes later and I was at 9% battery, which was odd given I plugged into the wall at 14%. I played with the phone for maybe 30s after boot and it happened again, I saw some weird artifacts on the black screen as it quickly shut off and the speakers played an awful crackly screeching noise. Plugged it in again, came back a bit later, still at 9% and played with the device again, same issue only after a little more time.
I'm currently at work with my N7 plugged into my Galaxy Tab 10.1 charger and charging it from 0 to 16% currently. The device is on but I haven't been touching it (and I don't plan to until it's at 100%).
Has anyone else had this issue?
I cant tell if it's some way I'm touching the device that's causing it to shut down hard, some issue with the battery or charging that is causing a rapid battery drop or even a short in the way I'm holding it when it's plugged into the charger?
I don't really want to deal with ASUS warranty returns already, though I have been unable to find anyone else with the same issue through google, so I turn to you for advice and similar stories.
Mine did the same thing the second day I had it. Now it won't boot. I'm waiting for Google to send me a new one.
Sent from my ADR6400L using Tapatalk 2
Mine did something similar last night. It was at about 6% battery charge and all of a sudden the screen just went black. I went and plugged it in, but it wouldn't power on completely (the screen was on but there was nothing there). I started seeing really thin, small green lines running down the screen. I turned it off and on a couple of times, and finally it booted up. I left it plugged in for awhile, and I just took it out at work to use a bit and everything seems perfectly fine. I wonder if there are some firmware issues with the power management or something. I was all set to put in a return with Google, but it appears to be okay. I'll keep a close eye on it for the next couple of days (I've only had it for a week).
TrevSo said:
Mine did something similar last night. It was at about 6% battery charge and all of a sudden the screen just went black. I went and plugged it in, but it wouldn't power on completely (the screen was on but there was nothing there). I started seeing really thin, small green lines running down the screen. I turned it off and on a couple of times, and finally it booted up. I left it plugged in for awhile, and I just took it out at work to use a bit and everything seems perfectly fine. I wonder if there are some firmware issues with the power management or something. I was all set to put in a return with Google, but it appears to be okay. I'll keep a close eye on it for the next couple of days (I've only had it for a week).
Click to expand...
Click to collapse
After leaving mine off and charging at work to 100% it seems to be working fine. I used it all last night with no issues. I haven't tried wiggling around the usb cable yet in the port to see if that caused any issues.
Firmware issues sounds about right, some sort of low battery safety feature or something? Who knows. I'll update this thread if I continue to experience problems. I'm already past my ability to return to Google so I'm in no rush to warranty to Asus and lose a development tablet.
I own a Moto G 2nd generation running stock lollipop, no modifications, and a couple days ago the battery drained completely kind of quickly (it even turned off when it had 5% left). when i charged it again, it turned on but it charged only up to 1%. i left there for hours and it didn't charge more than it, when i took off the charger it turned on almost imediately so it wasn't a display bug, it really had 1% left. i tried changing chargers and cables but no luck. also when it turned on it displayed the CQATest app which is a Motorola diagnostics app that isn't supposed to show to the end user and it didn't get mobile signal (I didn't have wifi and i didn't check if it was still working). i left it a couple hours turned off to see if the battery drained completely but it didn't fix. after it I left charging the whole night and by the morning it was on the same situation.
When i switched airplane mode on and off, it got mobile signal, but still it had 1% battery and the CQATest app. after it, I took a shower and when i came back the screen was turned on, but completely black. when i turned off and on it remained the same. when i took off the carger it turned off suddenly, and when I put it on again the cellphone turned on imediately even if i didn't press any button. I turned on and off several times throughout the day and only once it turned on, but when it did it kept displaying messages like "the process com.android.whatever has stopped" several times per second, sometimes variating the process. when i turned off and on it went back to the black screen.
So i was willing to factory reset it, and i could access the fastboot menu, but since it only had 0 or 1% battery i couldn't activate recovery mode to do the wipe and reset. On the motorola support for the first generation it says that you can press the power button for 2 minutes to reset, but when i tried it, it kept turning on, then off then on again several times and it didn't reset. i had the debugging mode activated but my computer doesn't even recognize the device so i guess i couldn't try adb. what else can i do?
TL;DR my phone is stuck on a bootloop with 1% battery and can't use adb or recovery mode. how can i reset it?
Delibird Rulez said:
I own a Moto G 2nd generation running stock lollipop, no modifications, and a couple days ago the battery drained completely kind of quickly (it even turned off when it had 5% left). when i charged it again, it turned on but it charged only up to 1%. i left there for hours and it didn't charge more than it, when i took off the charger it turned on almost imediately so it wasn't a display bug, it really had 1% left. i tried changing chargers and cables but no luck. also when it turned on it displayed the CQATest app which is a Motorola diagnostics app that isn't supposed to show to the end user and it didn't get mobile signal (I didn't have wifi and i didn't check if it was still working). i left it a couple hours turned off to see if the battery drained completely but it didn't fix. after it I left charging the whole night and by the morning it was on the same situation.
When i switched airplane mode on and off, it got mobile signal, but still it had 1% battery and the CQATest app. after it, I took a shower and when i came back the screen was turned on, but completely black. when i turned off and on it remained the same. when i took off the carger it turned off suddenly, and when I put it on again the cellphone turned on imediately even if i didn't press any button. I turned on and off several times throughout the day and only once it turned on, but when it did it kept displaying messages like "the process com.android.whatever has stopped" several times per second, sometimes variating the process. when i turned off and on it went back to the black screen.
So i was willing to factory reset it, and i could access the fastboot menu, but since it only had 0 or 1% battery i couldn't activate recovery mode to do the wipe and reset. On the motorola support for the first generation it says that you can press the power button for 2 minutes to reset, but when i tried it, it kept turning on, then off then on again several times and it didn't reset. i had the debugging mode activated but my computer doesn't even recognize the device so i guess i couldn't try adb. what else can i do?
TL;DR my phone is stuck on a bootloop with 1% battery and can't use adb or recovery mode. how can i reset it?
Click to expand...
Click to collapse
google it but forced turn on + reset if I remember correctly is plug in a usb charger and hold power button for 2 minutes + this force turns on and resets / wipes
Just received my OTA upgrade.
Everything went well up to the point were it says - Android is starting. It counts up to 51 and then says Starting Applications and then immediately (shown for half a second) - Shutting Down.
This goes on and on every time I restart the watch.
In addition, it gets so hot that I think it will melt.
Any ideas how to fix that?
super_joe said:
Just received my OTA upgrade.
Everything went well up to the point were it says - Android is starting. It counts up to 51 and then says Starting Applications and then immediately (shown for half a second) - Shutting Down.
This goes on and on every time I restart the watch.
In addition, it gets so hot that I think it will melt.
Any ideas how to fix that?
Click to expand...
Click to collapse
I'm experiencing the same issue. I hope that someone has some ideas on how to fix it.
Let it rest for an hour. Then try again. Works for me.
Sent from my A0001 using XDA Free mobile app
As above. I think it's heat related. I had similar when I was flashing the stock images from scratch. I let it cool down then boot it up again and it was fine after that.
I am sorry, but nothing helped.
Sit and Wait didn't help. Waited over night, same result the other day.
I also wiped the watch from Recovery. For just one time the watch started and demanded more at least 20% power, so I charged it and moved on with the configuration, but all of a sudden the watch turned off.
Since then, after several wiping tries, I had a new behaviour. Watch started with the 4 colored dots, after about 2 min just turned off without showing any other display.
Any other ideas?
super_joe said:
I am sorry, but nothing helped.
Sit and Wait didn't help. Waited over night, same result the other day.
I also wiped the watch from Recovery. For just one time the watch started and demanded more at least 20% power, so I charged it and moved on with the configuration, but all of a sudden the watch turned off.
Since then, after several wiping tries, I had a new behaviour. Watch started with the 4 colored dots, after about 2 min just turned off without showing any other display.
Any other ideas?
Click to expand...
Click to collapse
@super_joe any luck?
The sit and wait method ended up working for me as well.
I too had the same issue. After restarting the watch it kept shutting down. Then as last attempt I kept the watch on charging cradle and charged the watch. While charging the watched booted normally. Then found out battery was at 3%. But oddly before update it was 98%.
Anyways now it's working normally.
there is no consistent way to charge the watch anymore without overheating?
I have the same problem
Same problem here. after running fine with LeeDroidV2. But after the battery died it wouldn't fully start anymore.
Thought it was heat related too so I put it on the A/C fan. Still switches off. Gonna flash stock and will report back
I can't get it to work. It says "Starting Apps" after loading them (38 of 38) and the "shutting down" Just flashed stock 5.1.1. Any ideas?
finally back alive! I don't know what the problem was. When it finally booted without shutting down, the battery was at 2%. Even though it was on the cradle for 2hrs.
The first Moto G started off fine, though fairly constantly laggy (which I blamed on the low/mid specs of the phone.) Then it started getting quite warm while using it, then it started turning off with 5-10% battery left and would not turn back on, even after charging, unless you tried to turn it on 4-5 times. The first few tries, the white LED would just blink with no other sign of life from the phone. Soon after, the camera stopped functioning, so I decided to send it into Motorola for repair/replacement. I couldn't get the phone to factory reset normally, so I factory reset the phone using fastboot. Upon reboot, it took FOREVER to boot back into Android. I honestly thought the phone was bricked it took so long. Once it got booted, I shut it down, boxed it up, and sent it on it's way.
Replacement phone came and all was good again. Camera worked, phone didn't seem laggy this time, and phone charged and discharged like it should. This lasted about a week. The phone started getting warm during use again. The phone shut off at 22% battery and would not charge a single percent on the charger or turn on for at least a half hour. I decided to prep this replacement to go back to Motorola to try again, and again had to factory reset using fastboot. Again, the reboot after factory reset took FOREVER. I wanted to know how long this actually took, so I timed it. I've seen phones that take 5-10 minutes, but this Moto G takes the cake at 20 WHOLE MINUTES.
I am seriously considering jumping ship to something completely different if this is just how this phone is. Very disappointing for it being such a highly rated phone on several websites. Is this normal or did I get 2 lemons in a row?