1. dpham00's Avatar
    My Verizon moto g is on 4.4.2 and when I woke up, the phone was dead. It had almost a full charge last night before I went to bed. Would not even turn on. I plugged it in for a while and turned it on. According to battery monitor widget, it went from 91% to 0% in 1 minute and from 8% to 100 % in a minute.













    dpham00, Android Central Moderator
    Sent from my Verizon Samsung Galaxy Note 3
    06-09-2014 12:13 AM
  2. B. Diddy's Avatar
    06-09-2014 12:42 AM
  3. Macktion's Avatar
    Wow! And I thought I had battery problems on some of my devices! On my moto g I did a factory reset and the problems went away, but it was only a modest issue: -15%/hr while idle.

    Swyped from my Yoga 8
    06-09-2014 01:29 AM
  4. mtvictor's Avatar
    Try to discharge to 0% and then charge completely

    That happened to me once, from 90% to 0%

    Posted via Android Central App
    dpham00 likes this.
    06-09-2014 07:17 PM
  5. dpham00's Avatar
    Should not happen ever though... I called moto support, the guy told me to go into recovery and told me to do a factory data reset. Didn't even offer to help me backup data. I don't think it makes a difference but why not, if it happens again, then I will push them harder.

    Also I said that I logged the battery stats, but honestly the guy seemed more interested in getting me off the phone.

    dpham00, Android Central Moderator
    Sent from my Verizon Samsung Galaxy Note 3
    06-09-2014 11:52 PM
  6. neu smurph's Avatar
    Well reported issue - apparently fixed in 4.4.3.

    https://forums.motorola.com/posts/7a7b068df1
    06-09-2014 11:58 PM
  7. dpham00's Avatar
    Well reported issue - apparently fixed in 4.4.3.

    https://forums.motorola.com/posts/7a7b068df1
    I realize that, but the tech support seemed clueless to the problem. Also, 4.4.3 isn't available to me yet.

    dpham00, Android Central Moderator
    Sent from my Verizon Samsung Galaxy Note 3
    06-10-2014 08:12 AM
  8. Ry's Avatar
    I realize that, but the tech support seemed clueless to the problem. Also, 4.4.3 isn't available to me yet.

    dpham00, Android Central Moderator
    Sent from my Verizon Samsung Galaxy Note 3
    That level of tech support doesn't go that deep.
    06-10-2014 11:23 AM
  9. dpham00's Avatar
    That level of tech support doesn't go that deep.
    Sure but at the same token when I said I had logs, he didn't say, Sure send it to me and I can take a look or something.

    dpham00, Android Central Moderator
    Sent from my Verizon Samsung Galaxy Note 3
    06-10-2014 12:18 PM
  10. Inundated's Avatar
    Had this happen this morning for the first time. (I got my G months ago.)

    Thankfully, I'd read about it, knew what was happening...I ended up unplugging and replugging my phone, and it's back up to 100%. Got there almost instantly.
    07-03-2014 06:50 AM
  11. Inundated's Avatar
    Happened again the other day...hoping 4.4.4 fixes it...whenever that finally makes it to the Verizon Moto G...
    07-16-2014 09:41 AM
  12. scipper77's Avatar
    I know you said this is a known issue but this happened a few years ago to my wife's thunderbolt. It was a bad battery. We ordered new batteries and we were back in business. I have no idea your phone had a removable battery but the thread title drew me in.

    Posted via Android Central App
    07-16-2014 09:48 AM
  13. Inundated's Avatar
    This is not a bad battery issue. It's a KitKat 4.4.2 bug...reportedly fixed in 4.4.3. That version is being skipped due to an SSL bug, and 4.4.4 will (hopefully) come out for the Moto G versions that never got 4.4.3...
    07-16-2014 04:05 PM

Similar Threads

  1. Odin fails to write CWM6 <ID:0/004> FAIL! (Auth)
    By TH3_FRB in forum Samsung Galaxy S3 Rooting, ROMs, & Hacks
    Replies: 6
    Last Post: 06-13-2014, 09:10 AM
  2. Replies: 6
    Last Post: 06-09-2014, 07:38 PM
  3. Have calls default to Bluetooth headset?
    By jlprest in forum Samsung Galaxy Gear
    Replies: 0
    Last Post: 06-08-2014, 10:42 PM
  4. Replies: 0
    Last Post: 06-08-2014, 10:22 PM
LINK TO POST COPIED TO CLIPBOARD