I have been fighting Bluesleep for about a year and losing. Putting in hours of research only revealed that others were fighting it also. A small post in OnePlus 1 lead me to suspect SMARTLOCK. After removing all of the bluetooth devices for unlock the bluesleep went from on all night to 11 minutes. Power loss at night from 91% to 98% battery in the morning.
Hope this works for others. If this fix was already presented I sure missed it in searching for days.
Related
Hello.
I've been searching various forums for a fortnight now to try and diagnose an SII issue I've been having and Google inevitably brings me here. Unfortunately, the numerous threads on battery drain don't match the problem I've had and the solutions haven't helped.
Around two weeks ago I noticed the battery life on my handset was really terrible, draining in hours. I had been using it quite a bit at the time so assumed this was the cause. However, lately it has been draining within around 6-10 hours even when idle, usually dying completely overnight despite a full charge just before then. I don't have a huge number of apps installed - maybe 20, fairly standard ones like Twitter, Facebook, Amazon, no games and no 'battery defender' style apps. It's not rooted (it's 4.0.3) and I can't root it for other reasons.
The battery drain was a nightmare, basically going from power point to power point just to keep it topped up enough to use and it was draining during idle time and deep sleep. I very rarely ever have 3G, GPS or Bluetooth switched on. Wireless is on most of the time and it generally does have a signal in the two places I spend most time (home and work). It also has a strong Vodafone signal since I'm living in a major city centre.
I tried a few things:
1. Uninstalled all but the most-used apps I had. No change.
2. Uninstalled everything it was possible to uninstall. No change.
3. Installed BetterBatteryStats and CPU Spy. BBS plus many hours of searching kernel/partial wakelocks and so on showed nothing that looked odd at all, certainly nothing taking up a lot of time or regularly stirring the phone. CPU Spy showed it did deep sleep when idle.
4. Factory reset. This included no app installations except BBS, disabling the likes of Social Hub, Gaming Hub and all other stock apps I could. No tethering or wifi sharing, no wifi, no 3G, no GPS, no Bluetooth, nothing running. It was basically a handset sitting there doing nothing. BBS showed nothing odd that I could see but the battery still drains in hours. No partial wakelocks and a tiny number of kernel wakelocks taking up next to no time and occurring a handful of times. No change.
5. I charged it before bed, took the battery out and left it until morning. In the morning it was down at 79%. This seemed weird so I bought a brand new genuine Samsung battery and gave that a try. No change in the 6-10 hour drain but taking the battery out overnight showed no drain now.
6. The weirdest of all. I charged it fully before bed, switched it off over night and it was drained completely by morning. That seems crazy to me. I can fully understand poor software or bugs draining a battery but not when a handset is switched off.
I am lucky enough to be able to get a new handset through work but this issue really annoys me. I took very good care of the phone, never installed anything crazy, didn't over charge it, the handset never got warm at any time, I'm careful with Wifi/GPS/Bluetooth/3G and location services, yet I ended up with an effectively useless "mobile" phone.
Is there anything that comes to mind that could have caused this? Point 5 above made me think it was simply a battery issue and maybe it partly was (with two batteries, how unlucky) but point 6 is just crazy. What could cause a handset to drain a battery under these circumstances?
Thanks for any advice!
Take the phone to Samsung Service Centre. No phone should drain that quick when un-rooted and a full wipe has been done
Sounds like tha battery is shot.
Sent from my SPH-L710 using xda app-developers app
same thing happened to me yesterday, heres what i have tried to do so far:
http://forum.xda-developers.com/showthread.php?t=1821094
Um...widgets? Some widgets on stock Samsung ROMs kills your battery - I remember AP mobile news is a huge drainer. Try limiting the number of widgets you put on your homescreens maybe?
Hi...
Try:
01 - Full Wipe
02 - Install a clean ROM
03 - Disable Fast Dormancy ( *#9900*# )
04 - I use the GreenBatterySaver
After post your result !
I sugges too full reflash the stock rom and after count the batter time. If it does not help, it cold be HW error too - maybe it isn't.
I'm trying to figure out what may have changed with my phone here in the last week or so. I installed MOAR rom 3 weeks ago, and it has been running very well. However, thus past week, my phone battery has been draining unusually fast when on idle. I can't figure out why. It seems like an unusual amount of juice is getting used up by cell standby.
It used to be that I could fall asleep at night with my phone unplugged and be maybe 10% worse for wear in the morning, though often not even that much. Last night I fell asleep with 58%, and I woke up 6 hours later with 29%. That was a 29% decrease in 6 hours on standby.
I am hoping someone may have a suggestion or two for me. Any help will be thanked and greatly appreciated.
Under mobile networks network mode, I was set to use global. Not sure if that is best, bit I just switched to LTE/CMDA hoping that might help. Seems like more options should exist here.
I always charge my phone in the evening so it doesn't stay on the charger overnight. It always works out well because the battery only drops about 1% overnight, if that. The last few days, the battery has been dropping 10-15%, and it is being caused by a partial wakelock, NIpWakeLock to be exact (screenshot below). Does anyone know what this is and what can be done? Thanks.
There was a thread in the N5 forum about this a couple of years back. Something to do with location settings. Google nlpwakelock and I'm sure you'll find it.
Hi guys,
I have read countless threads on battery life & wake locks on XDA, Reddit, etc. Trying to find a solution to what I still find the Achilles heel of android, wake locks.
I am running stock on MHC19Q build
Adaptive brightness off
Wifi scanning off
Bluetooth scanning off
Battery Optimization on all apps except for DMService and Google Play Services
Some days I will go 2-3 hours with 30 minutes SOT and my battery only drops 10%. Doze works as it should. I will get through a full day at about 4 hours SOT (6am to 10pm).
On other days (like today) I am unplugged for 3 hours at 80% with 10 min SOT. I have rebooted the device 3 times since unplugging it and my wake locks are still occurring. My signal is perfect green through and through. Bluetooth off and connected to wifi.
I find the issue comes and goes. Some days the phone will start out great, only to have wake locks start occurring mid day. I think Android OS appears to be the issue.
Anyone else encountering wake locks that come and go?
Any help would be greatly appreciated! :victory:
AndroidFS2 said:
Hi guys,
I have read countless threads on battery life & wake locks on XDA, Reddit, etc. Trying to find a solution to what I still find the Achilles heel of android, wake locks.
I am running stock on MHC19Q build
Adaptive brightness off
Wifi scanning off
Bluetooth scanning off
Battery Optimization on all apps except for DMService and Google Play Services
Some days I will go 2-3 hours with 30 minutes SOT and my battery only drops 10%. Doze works as it should. I will get through a full day at about 4 hours SOT (6am to 10pm).
On other days (like today) I am unplugged for 3 hours at 80% with 10 min SOT. I have rebooted the device 3 times since unplugging it and my wake locks are still occurring. My signal is perfect green through and through. Bluetooth off and connected to wifi.
I find the issue comes and goes. Some days the phone will start out great, only to have wake locks start occurring mid day. I think Android OS appears to be the issue.
Anyone else encountering wake locks that come and go?
Any help would be greatly appreciated! :victory:
Click to expand...
Click to collapse
Absolutely same situation. No new application in monthes.
Google play services is usually the battery waster I found when moving around, I tend to place phone down when I can to save juice but you really need to identify your wakelocks first. I'm rooted and use bbs.
Disabling location may help, if rooted and using xposed, amplify may help too.
Google play services get updated when it's pushed out, sometimes it has bugs.
Maybe if you haven't updated any of your apps for months, then possibly one may need updating now.
Hi folks,
A few days ago my never rooted & bootloader still locked OP-direct 8/256 6T took the 9.0.11 OTA, updating from the prior 9.0.7. Each night since then I've had a much higher overnight idle drain than before the update.
For the week or so I had the device prior to the update, I would loose 2-3 % total for an ~8-9 hour downtime. Since the update, I'm losing 10-15% overnight.
Accubattery is installed; it didn't give anything useful but it's limited due to lack of root I think. BBS I don't think runs at all without root.
Of the 370mAh used, only about 15 mAh are accounted for by app usage tracked. The device was in deep sleep for 98% of the time. It doesn't show what else has drained the battery anywhere I can see. Cell standby, wifi, etc.. The phone is kept in a place where wifi is reasonably strong in the house; there's cell service here no problem too.
The device has been rebooted a couple times since the update.
Any thoughts on figuring out why the drain is higher now? I've installed nothing new since day one when I got the device.
Frankenscript said:
Hi folks,
A few days ago my never rooted & bootloader still locked OP-direct 8/256 6T took the 9.0.11 OTA, updating from the prior 9.0.7. Each night since then I've had a much higher overnight idle drain than before the update.
For the week or so I had the device prior to the update, I would loose 2-3 % total for an ~8-9 hour downtime. Since the update, I'm losing 10-15% overnight.
Accubattery is installed; it didn't give anything useful but it's limited due to lack of root I think. BBS I don't think runs at all without root.
Of the 370mAh used, only about 15 mAh are accounted for by app usage tracked. The device was in deep sleep for 98% of the time. It doesn't show what else has drained the battery anywhere I can see. Cell standby, wifi, etc.. The phone is kept in a place where wifi is reasonably strong in the house; there's cell service here no problem too.
The device has been rebooted a couple times since the update.
Any thoughts on figuring out why the drain is higher now? I've installed nothing new since day one when I got the device.
Click to expand...
Click to collapse
Haven't noticed any additional drain on 9.0.11 on mine. Yes, you can run BBS unrooted, you just need to do a couple of adb commands to give the app permissions.
I started using the "deep sleep" mode to turn the phone off at midnight, and back on at 6am, since I don't use it overnight
at all. If I unplug it from the charger at 9pm, at 6am (after it turns off at midnight), the battery shows 99%.
OK thanks. I'll first do some investigating after I get BBS running via ADB commands, and consider the deep sleep option as well if I can sort out why it seems to drain a lot at night.
Normally, on my rooted devices, I would backup, flash the latest version (I'm on latest so no problem), factory reset, then restore the apps/data I care about. But without Titanium backup I'm reluctant to wipe so quickly since backup and restore is more involved. Still trying to avoid rooting this one... but may give in and enjoy the ride.
I didn't get around to messing with this yesterday, but overnight last night I only lost 3%. Not sure why the previous two nights were relative disasters. I'll keep monitoring.
I have heard, that sometimes after an update, it might take a day or two for the phone battery level to stabilize.
I don't root/custom flash anymore. (after I stopped buying bloated carrier branded phones). Stock is "good enough"
for my use, but, I've never had a battery drain on stock, but I've heard that some do.
If it continues, it might not hurt to clear the phone cache.
android has to rebuild its optimization cache after every update. it's normal.
No problems here 6t McLaren all stock, 4g all the time, bt always on
try wipe cache from recovery .
Oh yeah & its quite noticeable after using it for over a week even after wiping Dalvik / Art Cache. @funkwizard
As an update, some nights I lose 3% which is sort of my baseline, and other nights I lose up to 15%, and I have no idea why. Apps are using negligible power. Need to get BBS permissions (I'm unrooted) to track it down I think.
Sent from my ONEPLUS A6013 using Tapatalk
I've been losing about 1% an hour overnight and it's very frustrating, not being able to pinpoint the cause. I am rooted and have better battery stats and gsam battery monitor and all I can tell is that Android system is using a lot of power and there are a lot of wakelocks happening up to 40 or 50 times an hour that seems to be keeping my phone from consistently being in deep sleep
Interesting, and thanks for the reply (thanks button hit!).
Today was my first normal day back to work since getting the phone, and it was a busy day so I didn't use the phone much. It was at about 95% charge when I got to work (topped off in the car, so almost full), and 8.5 hours later it had only lost about 17% power, including about an hour of screen on time due to use during the day. So, 7+ hours of standby and an hour actually on in a few minutes here, a few minutes there, using up 17% of the battery is incredible, best phone I ever had. What I don't understand is why sometimes, not others, it uses almost this much power in 9-10 hours sitting alone, unattended, in an area with decent (2-3 bars) cell signal and very strong wifi. Note when it sits at night it always reports ~95+ % deep sleep (typically 98%), so wakelocks aren't my problem as far as I can tell.
I may go ahead and clear the cache through stock recovery and see if that changes anything. Not sure why it would, really, other than some extra power used to rebuild the cache.
It's a busy week so it may be the weekend before I can do much of anything other than observe...