I've got an old Moto G5+ from my brother, and instead of deleting all his apps and data, I decided to perform a hard reset. That was my biggest mistake. After a hard reset, battery life dropped significantly. The phone tends to lose a lot of charge in standby mode. With 30% left before I go to sleep, the G5+ will be dead in the morning.
I couldn't find out why (no battery-hungry apps in the stats, the issue persists even without user-installed apps) until I've read a post about Wi-Fi affecting battery life from the Moto G5 owner. When Wi-Fi is off, It works fine with no extensive battery drain (I use a 3G/LTE connection instead to surf the web).
I've already tried to:
Calibrate the battery.
Perform another hard reset.
Flash stock firmware. It didn't end well, and I had to use Motorola's Rescue and Smart Assistant, which worked.
Clear cache in recovery mode.
Do one more hard reset in recovery mode.
Turn off Wi-Fi and Bluetooth scanning options in location settings. Too late, I know. But no luck.
I have tried to switch to the Safe mode. That helped to stop the battery drain. But what I need to do next? It doesn't look like a third-party app issue. Maybe I should try to install an older version of the official firmware? I don't want to experiment with custom ROMs (if only an almost 100% stable, but which one to choose?).
Related
Hi Guys,
I upgraded my Exynos Note 3 to Kitkat about 1 month ago, and everything was fine till about 3 days ago when I started experiencing some really bad battery drain. For the last three nights, my phone does not go into deep sleep mode at all. I first noticed this because I usually switch off data and wifi at night. Normally, I'd loose 3% battery overnight, which is good. About two nights ago, I woke up in the morning and I had lost 40% battery (90% down to 50%) overnight! When I checked out the battery stats, "gpsd" had used 80% of the battery.
Since we no longer have batterystats access in Kitkat, I installed the desktop version of WakeLock Detector, enabled USB debugging mode and connected my phone. Phone had basically been awake 97% of the time. Under kernel wakelocks, "l2_hsic" was shown as being the culprit. Now I have searched through various forums online (including xda) to try and find a solution to this. Suggestions vary from home screen replacements (nova launcher) to mobile tracking software (cerberus/findmymobile etc) to generally anything that uses location services. Some even suggest clearing application caches, disabling location services etc. I have tried every suggestion with no change. I uninstalled all mobile tracking apps, turned off location reporting, location history, and eventually location services. I've removed all battery stats apps. I uninstalled all my apps and re-installed them one by one, all with no change. Finally, I backed up my phone and did a factory reset. That seemed to work at first, but after about 3 minutes, "gpsd" was back again, and my phone would not go into deep sleep.
I've done 3 factory resets, and with no google account or samsung account configured, I still get "gpsd" rearing it's ugly head, preventing the phone from going to deep sleep and draining my battery. I'm at wits end.
Anyone know how to fix this? Would appreciate any help!
Anyone!?
OK, so I decided to take out my SIM card, just to see it'd make a difference, and what do you know! "gpsd" no longer takes up CPU time! So this is somehow related to my SIM card? Funny though, coz I'd even tried putting the phone in Airplane mode, but "gpsd" was still taking up CPU time. Does that give anyone an idea as to how this can be fixed?
bump
I'm having exact same issue with my exynos Galaxy S5, shame Samsung.
For the record, my issue fixed itself. Didn't do anything at all. It just went away and never recurred. I'm on the Russian lollipop ROM now, loving it!
Almost a year after the issue fixed "itself"... I have the same problem with my SM-N900 running offical lollipop, Im afraid I cannot wait a year to let the issue fixes itself... and cannot find a solution either.
Anyone that have managed to solve this?
THANKS IN ADVANCE!!
Huge battery drain when tablet is "sleeping" - probably because "bluesleep"
Hello,
I have problem on my N7 with large battery drain.
I had this issue witch Stock ROM, now I tried to root stock ROM (4.4.4) and install Greenify, but battery still dies after 2 days of no usage.
I tried to charge it fully, reboot it, cleared cache and dalvik cache, and put it to "sleep". After one night, 40% of battery was gone.
It seems that my N7 is not going to "deep sleep" for some reason.
So I tried to install numerous of apps to find what app is responsible for this. None was successfull, until I tried BBS.
In attachment, you can find BBS dumpfile. But it seems, there is some "bluesleep" kernel wakelock, which is responsible for all my troubles. Unfortunatelly, I dont know what this process is. Or am I reading dumpfile wrong and some other app/process is responsible for this huge battery drain?
I also attached screenshot from standard android battery statictics, which shows, that "Android OS" is preventing tablet from sleep.
Is there some way to fix this issue? Tablet worked normally for 1.5 year, but in last months is unusable, because it has dead battery everytime I want to use it.
Thanks for advices.
I would imagine bluesleep wakelock is related to bluetooth. Do you have BT on and/or connected to anything using BT?
If so try turning it off and see if it persists.
Yes, I use Bluetooth for my Jawbone UP24 sync. But I have this band only for a week. Extreme battery drain already was there before I have got UP24. In these times I had bluetooth turned off all time. So I dont think this is main reason.
I turned off BT. Lets see what happens in the morning.
UPDATE: You were right. It is bluetooth. When I turn it off, tablet is most time in deep sleep.
So probably rooting and installing greenify worked, but in meantime, I started using UP24 and Bluetooth on tablet.
I will try if situation is better with some AOSP based ROM. I did not wanted to flash another rom (than Stock), but I guess, there is no other way. Even clean Android on Nexus device is not usable with comfort...
After a few weeks of battery problems no matter what ROM (or stock) I used I wiped my device and left it running without restoring any apps. Here's the result:
https://dl.dropboxusercontent.com/u/1623843/Screenshot_20160713-170321.png
So, that's about 35% drain in 6 hours with the screen off and the phone sitting on a shelf. It seems a bit much to me - should it be that bad? If not, is it likely to be the hardware, or could there be some other cause?
Wifi and bluetooth scanning on? Backup in settings turned on? These are first things that come to mind, they tend to get bugged and cause wakelocks not allowing phone to sleep properly
Thanks. Wifi and bluetooth scanning are off (I turned them off some time ago in case they were the cause), but backups are on. I've turned the backups off and will see if that makes any difference.
Turning backups off and aircraft mode on doesn't seem to make much difference.
Install Better Battery Stats and monitor the wakelocks from there over a period of 24hrs and report back here with a screen shot from the kernel and partial.
Here are some from last time I checked it; it was running CM13 at the time, though whatever ROM I choose seems to make little difference:
https://dl.dropboxusercontent.com/u/1623843/tmp/index.html
knirirr said:
Here are some from last time I checked it; it was running CM13 at the time, though whatever ROM I choose seems to make little difference:
https://dl.dropboxusercontent.com/u/1623843/tmp/index.html
Click to expand...
Click to collapse
Nest, Tweetcaster, Pebble and the watchface for your Pebble are high.
When I change ROM or start from fresh, I always format boot, data, system and user data and never restore my backup but only copy what I need (photos, music, apk to be installed, etc.). Its a pain in the ass but at least I'm on a fresh OS and partitions.
therock3181 said:
Nest, Tweetcaster, Pebble and the watchface for your Pebble are high.
When I change ROM or start from fresh, I always format boot, data, system and user data and never restore my backup but only copy what I need (photos, music, apk to be installed, etc.). Its a pain in the ass but at least I'm on a fresh OS and partitions.
Click to expand...
Click to collapse
I've tried wiping as well, and backed up all my apks with Titanium Backup for reinstallation, although it doesn't seem to have helped. Currently I'm getting higher than expected drain without having re-installed those apps.
Initially I thought that Nest was guilty, but removing it had no effect. I removed those other apps as well and there's still a higher power drain than I used to get.
Having left the phone sitting all day with aeroplane mode on and Better Battery Stats installed, here's what I found:
https://dl.dropboxusercontent.com/u/1623843/tmp/Screenshot_20160716-175629.png
https://dl.dropboxusercontent.com/u/1623843/tmp/Screenshot_20160716-175637.png
https://dl.dropboxusercontent.com/u/1623843/tmp/Screenshot_20160716-175644.png
https://dl.dropboxusercontent.com/u/1623843/tmp/Screenshot_20160716-175652.png
Surely losing half the charge in 9.5 hours whilst in deep sleep is not expected behaviour? If it is then no wonder the phone wasn't lasting a day with that base degree of drain plus the drain from actually using it as well.
In nougut i get 1 day 5 hours standby time with 2 hours of screen on time. I don't remember about time in marshmallow but i used to get much more standby time. (Both with wave to wake and other features on except moto voice)
And my cell standby and phone idle usage it very high with nougut. Even if i start using it after full charge without turning screen off even then it shows phone idle usage high.
Can anyone tell me whats the problem?
Is nougut uses much more power in cell radio than marshmallow?
And does nougut uses much more power for wave to wake and other features of moto?
Just to clarify a few things: when did you apply the update? It takes some time to "settle". Did you try a factory reset? This has been known to fix issues. Just asking to determine the troubleshooting you may have already tried
Factory reset and then recalibrate the battery sensor.
I have the same issue, you probably live in area with poor 4g/3g coverage and radio in nougat is way less efficient in low signal situations.
btw to the previous guys, do you have 7.0 update? if not then don't know what are you talking about. Factory reset or some "settiling" jokes won't fix this.
I left mine at 40% last night and woke up to 40%. XT1575 but EU Nougat backup restore.
iks8 said:
I have the same issue, you probably live in area with poor 4g/3g coverage and radio in nougat is way less efficient in low signal situations.
btw to the previous guys, do you have 7.0 update? if not then don't know what are you talking about. Factory reset or some
"settiling" jokes won't fix this.
Click to expand...
Click to collapse
There is this issue. It is one thing that matters me hesitant on taking the update.
But as far as factory reset, it is a good place to always start. I use the term "settle" in quotes for good reasons. Aside from the fact that a user might play around a little more to discover new features, it might take a moment for battery to report correctly. Not really a big thing anymore with modern tech and batteries, but just in case...
I find the biggest thing you can do when going up a version is factory reset and do not let Google restore your apps and data. Hand install what you want and set them up manually. Funky app data is the cause of more standby power use than anything else as apps hold wakelocks when they shouldn't .
Simply uninstalling apps doesn't always fix this as the data gets restored when you reinstall. To me blowing everything away and starting fresh is the best plan on a major update.
Wave to wake in Nougat is a battery killer..
Anyway, maybe you want to check this guide:
https://forum.xda-developers.com/mo...ide-improve-battery-life-performance-t3647155
Take into account that battery stats are buggy, for me everytime I restart my device is a different %. Today i turn it on at 99%, restart it an get 87%, so i keep charging it.
I seem to be losing between 8-10% overnight since clean flashing OPM1. Anyone else seeing this? I can't peg it on a particular app and accubattery reports anywhere from 0.8-1.2% loss with screen off. If I just tap the power button to see accubattery stats, the current drain without going into anything ranges from 54mah to sometimes as high as 150mah. I may try a factory reset to resolve but curious to what others numbers are.
I'm using latest stock 8.1 and find it has the best standby I've ever seen. Either your battery is over year or two and starting to degrade. Or you need to do some spring cleaning when was the last time you backed everything up and wiped internal. You'd be amazed the wonders that does with rogue apps and missfunctioning features after completing wiping and installing fresh copy of stock.
Exodusche said:
I'm using latest stock 8.1 and find it has the best standby I've ever seen. Either your battery is over year or two and starting to degrade. Or you need to do some spring cleaning when was the last time you backed everything up and wiped internal. You'd be amazed the wonders that does with rogue apps and missfunctioning features after completing wiping and installing fresh copy of stock.
Click to expand...
Click to collapse
Just bought a new OEM battery that is reporting 101% capacity so that's not it. Also, clean flashed 8.1 when I loaded it although I restored from my cloud backup. I just factory reset today but honestly, I felt it was worse so I completely blew everything out again, redownloaded 8.1 and flashed again. This time I chose to set up as a new device without using the cloud backup. The only thing I manually backed up and restored was text using a 3rd party app. I am adding my apps back a few at a time but it seems to be a little better as of now but will have to give it a couple days to settle down. Not rooted yet either.
Some are reporting that "mobile data always active" is enabled by default in developer options on 8.1. Have you tried disabling this?
To compare this with op, I got 84% battery health and a drain over night of 4%. Stock 8.1, Nova launcher beta, SuperSU beta, mobile data always active is off. May an app is responsible for your 10% draining ? Any social stuff like fb ???
I turned off mobile data always active and when I clean flashed the second time, I did not put any social media apps on the phone but saw no difference. I ended up putting fb, messenger lite and Instagram back on and they aren't impacting negatively. It's only been 2 days and have only rebooted a couple times.. battery is still reporting 101% capacity. I'll give it a another day or 2 to settle down bc at some points it seems to be very efficient while others it doesn't but that's better than before the 2nd clean flash.
Looking at my accubattery stats, I'm still losing about 1.1% battery per hour with the screen off. I also noticed that so far in the ~7 hours my phone has been off the charger today, it's only been in deep sleep about 51% of the time that the screen has been off. What happened to the built in wakelock detector that was highlighted in https://www.phonearena.com/news/Android-8.1-Oreo-wakelocks-battery-draining-apps_id99715? Does anyone see this actually working or is this yet another "Pixel exclusive". I cannot figure this out so I guess I'll have to download a 3rd party wakelock detector but the reality is, even if I do find the culprit, it's usually not anything that is easily identifiable or fixable. Am I really the only one having this issue??