I charged my Nexus 5 to 100% just before I went to bed, turned off radios, WiFi, location and data, I just woke up and the battery went down to 64% this is unacceptable, and this is only happening after I flashed android 5.1 Factory Images, never happened when I was on 5.0.1
Could this be because when flashing the FI, when I hit flash-all command only flashed boot loader and radios and then it gave me an error so I hit flash-all command again and same thing happened, after flashing the boot loader and radio gave the error, this happened 3 times after I restart my laptop, hit the flash-all command and it flashed the whole thing, after this I did a restore using adb
Any ideas if any of these can be the reason of the battery draining? Should I go back to 5.0.1 ? Can a reset fix this issue?
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Register an account on XDA for full access.
Stand by
Good luck
Enabling airplane mode does not mean you won't lose any juice. But the fall -36% during the night is not normal.
Anyways, it seems that we won't see you soon
Which wakelocks do you have on gsam battery monitor or bbs?
XDA Visitor said:
I charged my Nexus 5 to 100% just before I went to bed, turned off radios, WiFi, location and data, I just woke up and the battery went down to 64% this is unacceptable, and this is only happening after I flashed android 5.1 Factory Images, never happened when I was on 5.0.1
Could this be because when flashing the FI, when I hit flash-all command only flashed boot loader and radios and then it gave me an error so I hit flash-all command again and same thing happened, after flashing the boot loader and radio gave the error, this happened 3 times after I restart my laptop, hit the flash-all command and it flashed the whole thing, after this I did a restore using adb
Any ideas if any of these can be the reason of the battery draining? Should I go back to 5.0.1 ? Can a reset fix this issue?
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Related
OK so I bought a phone off craigslist as a replacement for my gf, really unstable running the stock 2.3 firmware, did a factory reset, seemed to be stable afterwards but the battery meter constantly reads 100%, so I flashed it to 2.3 stock with ODIN, problem was still present, put clockwork mod on it, wiped battery stats, still was there. Installed a PAC MAN rom, still there, flashed back to stock 4.1 firmware, problem still present, and finally put the dirty unicorn ROM on it and its still stuck.
So I found a post saying to charge up all the way, delete the batterystats.bin file reboot in recovery wipe cache partition and davlik cache, power off and keep plugged in, disconnect charger reconnect and leave powered off but charging, then turn on, did that and leaving on till it powers itself off and its still stuck at 100%
Oddly when the phone is turned off upon first showing it does display the correct battery for about 15 seconds and then reverts to 100%
What is going on here, how do I fix this
rodimus_prime said:
OK so I bought a phone off craigslist as a replacement for my gf, really unstable running the stock 2.3 firmware, did a factory reset, seemed to be stable afterwards but the battery meter constantly reads 100%, so I flashed it to 2.3 stock with ODIN, problem was still present, put clockwork mod on it, wiped battery stats, still was there. Installed a PAC MAN rom, still there, flashed back to stock 4.1 firmware, problem still present, and finally put the dirty unicorn ROM on it and its still stuck.
So I found a post saying to charge up all the way, delete the batterystats.bin file reboot in recovery wipe cache partition and davlik cache, power off and keep plugged in, disconnect charger reconnect and leave powered off but charging, then turn on, did that and leaving on till it powers itself off and its still stuck at 100%
Oddly when the phone is turned off upon first showing it does display the correct battery for about 15 seconds and then reverts to 100%
What is going on here, how do I fix this
Click to expand...
Click to collapse
u would need to try an oem battery and cable to see if it corrects the issue, if not then its probably the charging port, reading this post might help http://forum.xda-developers.com/showthread.php?t=2493751
An OEM battery really isnt a possiblity as no places sell it locally (sure I can order it online but this is a time sensitive project) and I really dont want to dump any further money into this project if its not going to work
Battery was getting tired, so I ordered a replacement -- and installed it yesterday afternoon..
The phone worked normally -- until this morning.
I noticed a notification from my text app that it couldn't connect and that I should check my settings.
I went to settings and began by refreshing the PRL. During that process the phone froze and then went dead.
Totally dead.
So, I opened it up again to check the battery terminal connection -- and I believe it WAS loose -- so I reconnected it and checked it. Phone goes on!
But it only goes to the splash screen and then repeats. No boot animation.
It will go to the bootloader, but not boot the system nor recovery from there.
Using the fastboot commands, I re-flashed bootloader, radio, boot, system, (From 5.1 stock image) TWRP recovery and erased the cache.
Still stuck at the Google splash screen.
Anyone care to point me in a better direction?
Must be expiration time for Nexus 5 batteries from the initial run. I had to replace mine today as well. Try reflashing the cache and not erasing it after. I made that mistake a month or so ago and kept bootlooping.
I was charging my phone overnight. In the morning I realized it didn't charge, I tried to turn it on and it gets stuck on the HTC screen.
I was running Viper One 3.21, I tried rebooting, entered recovery, tried to reinstal a nandroid, got stuck on the screen again.
Tried reinstalling ViperOne same problem.
Here's what I know:
Fastboot will NOT work, while I can get to fastboot, any time I reboot the phone it gets stuck.
I can't get to RUU (because it wont go past the HTC screen).
adb sideload will not work
I've let the battery drain, fully charged it; no change.
I tried wiping and doing a factory reset but it just gets stuck on the reboot, I also noticed on the File manager within TWRP that my phone was never wiped.
Any ideas?
SS823 said:
I was charging my phone overnight. In the morning I realized it didn't charge, I tried to turn it on and it gets stuck on the HTC screen.
I was running Viper One 3.21, I tried rebooting, entered recovery, tried to reinstal a nandroid, got stuck on the screen again.
Tried reinstalling ViperOne same problem.
Here's what I know:
Fastboot will NOT work, while I can get to fastboot, any time I reboot the phone it gets stuck.
I can't get to RUU (because it wont go past the HTC screen).
adb sideload will not work
I've let the battery drain, fully charged it; no change.
I tried wiping and doing a factory reset but it just gets stuck on the reboot, I also noticed on the File manager within TWRP that my phone was never wiped.
Any ideas?
Click to expand...
Click to collapse
Sorta sounds like one of the bricked ones where the entire emmc goes write protected. If you can't get fastboot or ruu mode and have no warranty left I can take a look at it for you. I'm in PA so it wouldn't take long to mail it here.
Not sure how it got bricked, it has been over a month since I flashed anything.
I am able to use adb sideload, but any file I use it says is corrupted.
Could I partition part of the drive and try to instal from there?
What part of PA are you in?
SS823 said:
Not sure how it got bricked, it has been over a month since I flashed anything.
I am able to use adb sideload, but any file I use it says is corrupted.
Could I partition part of the drive and try to instal from there?
What part of PA are you in?
Click to expand...
Click to collapse
I am down in the York/Harrisburg/Lancaster area. You don't want to partition emmc manually.
I have a weird battery drain. As you can see Phone dropped 90 from 100. Then an endless bootloop started. I wasn't able to get to fastboot, recovery. Phone was restarting over and over again. I tried pressing power+vol down button for 120 seconds, and almost everything. Anyway 12 hours later i plugged My Phone and now everything looks Fine. But i am sure that it will gonna happen again. Because its My 3rd or 4th time with this problem. Wiped cache, dalvik, factory reset, flashed stock rom 5.1. It happens again. Flashed marshmallow rom. Happens. Downgraded to kitkat via firmware method. Happens. I hope that someone could help me.
So, all was working fine till I flashed CM13 on my N8000 for the third or fourth time. When I booted my battery just drained from 70% to 0 at the drop of a hat. I left it charging for 20 minutes so I could turn it on and finish setting it up again and when I did so, it was on 1% and it suddenly dropped to 0 and went off again. I booted into TWRP and again showing that the battery was at 1% and suddenly battery stats disappear on TWRP (probably meaning it was on 0). So I tried reinstalling CM13 but it didn`t work. It optimized all the 49 apps (from OpenGAPPs) and when it got to the home screen, boom, 1->0 and then dies. I`ve searched the internet for this issue and couldn`t find anything. I tried reseting my battery stats but I couldn`t do it either. Some random dude said it was located in data/system/batterystats.bin or something and when I get to these folders they`re empty already. That`s it. I hope anyone can help me because I`m like super screwed. Thanks!
Don't mess with battery stats bin.
In recovery. Format. Data system cache.
Boot to download flash stock rom via Odin .
Sent from my SM-N920C using XDA-Developers mobile app
JJEgan said:
Don't mess with battery stats bin.
In recovery. Format. Data system cache.
Boot to download flash stock rom via Odin .
Sent from my SM-N920C using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, this is what went down later that day. Thanks for the help and concern though.
http://forum.xda-developers.com/galaxy-note-10-1/help/n8000-insane-bug-t3444875