Hi, I just bought a Mi Band 2 and I noticed a moderate battery drain due to a bluesleep wakelock (together with a ttyhs0) preventing the cpu from going into deep sleep. When bluetooth is on there is always a bluesleep entry on kernel wakelocks, but for a limited time (10-15% of total).
Is there anything I can do? I'm on latest stock ROM, no root. I tried uninstalling every suspicious app. I didn't do a factory reset, but if it's something kernel related I doubt it could resolve something...
Thank you
Related
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...
A few weeks ago, my S4 started to have terrible battery life. BetterBatteryStats tells me that my phone is usually 1-2 hours longer active than I'm actually using it, and that it's caused by the kernel wakelocks in the screenshot. Sometimes there are wifi-related wakelocks too, even though wifi is always turned off.
Is there a known cause for these wakelocks? I couldn't find an explanation. Also, could flashing a new kernel help? I thought about doing that anyway.
Thanks!
Screenshot 1
Screenshot 2
If it really is kernel related, then yes.
Better Battery Stats shows Doze-Wakelock as my worst offender of Kernel wakelocks at 75% with the next offender, power manager service at a measly 13%. I have reset, reflashed, uninstalled, reinstalled, wiped cache, wiped dalvik, yet the wakelock persists and I can not find anything about it on any thread. I currently use greenify, power nap, amplify, and force doze on Stang5.0litre rom. However I have noticed the wakelock on Echoe and stock rom. It persists with Force Doze off (I don't use Greenify's Aggresive doze.) If anyone has any info on this wakelock, please inform me.
link77709 said:
Better Battery Stats shows Doze-Wakelock as my worst offender of Kernel wakelocks at 75% with the next offender, power manager service at a measly 13%. I have reset, reflashed, uninstalled, reinstalled, wiped cache, wiped dalvik, yet the wakelock persists and I can not find anything about it on any thread. I currently use greenify, power nap, amplify, and force doze on Stang5.0litre rom. However I have noticed the wakelock on Echoe and stock rom. It persists with Force Doze off (I don't use Greenify's Aggresive doze.) If anyone has any info on this wakelock, please inform me.
Click to expand...
Click to collapse
I'm also on the Stang rom and i just noticed it after gsam showed my phone being held awake for over an hour during 2 and a half hours of standby. Seemed to start when i turned on the AOD but i can't be sure.
Omegeddon said:
I'm also on the Stang rom and i just noticed it after gsam showed my phone being held awake for over an hour during 2 and a half hours of standby. Seemed to start when i turned on the AOD but can't be sure.
Click to expand...
Click to collapse
Do you use any if the apps I mentioned above. Ive noticed the wakelock isnt as prominent if the phone is left stationary. So I feel as though it might be greenify or force doze trying to force doze, but android system noticing the motion and not letting it do so, creating a loop and constant conflict. But as I said i can not find anything about this on xda or Google.
Omegeddon said:
I'm also on the Stang rom and i just noticed it after gsam showed my phone being held awake for over an hour during 2 and a half hours of standby. Seemed to start when i turned on the AOD but i can't be sure.
Click to expand...
Click to collapse
Turned the aod off this morning. Definitely the culprit. However noticed 4 random reboots while the phone was inactive. The problem goes away when i turn aod back on. Currently investigating this new problem.
Freezing always on display in titanium Backup after disabling it fixed the random reboot issue. Currently enjoying no doze-wakelock in bbs with a great increase of deep sleep time.
The only one i use is greenify.
It happened a few weeks ago and has not improved. After the most recent update, I'm getting anywhere from 15 - 50% battery usage from Play Services.; my usual play services battery usage is 1 - 3%. I'm on the latest version, and apparently it's affecting devices from all different manufacturers. It's not heating my phone up and it still says it's deep sleeping, which leads me to believe it's messing with hardware - constantly scanning wifi or bluetooth or something. CPU usage isn't any higher than normal. If I leave my phone unlugged while I sleep, it'll drain 25+% battery over 8hrs while it claims it was in deep sleep the whole time.
I can't roll back or remove play services (I'm rooted and on Oreo), I'm about to try clean flashing my ROM with no gapps, and installing an older version of play services. I don't know what to do, I'm just wondering if anyone here has had the issue or found a way to stop it.
edit: I ended up clean flashing my ROM with the latest opengapps and it seems to have stopped killing my battery.
I had a massive battery drain issue due to 7000000.ssusb wakelocks. My phone is rooted and i updated "disable_host_mode" file to "Y". Since then the battery drain decreased by a half. But still there is 9-10% battery drain in the period of 6-7 hours of idle period. BBS, showed there is around 98% Awake (Screen Off), I am quite not sure what is causing this, but I am certain that 7000000.ssusb is not causing this. I have attached the following screenshots of BBS.
I just wonder what might be the reason for this. I have -
1. Turned off wifi, data and location.
2. Put phone in Airplane mode
Can anybody point me to right direction? Thanks
Friend of mine has the very same issue. I suspect a HW defect, but he's lazy to go to a service center, so I can't confirm (yet)..
We tried rooting/unrooting, several reflashes of stock ROM, factory resets with/without apps restore etc., result is always the same - pretty much no deep sleep.
_mysiak_ said:
Friend of mine has the very same issue. I suspect a HW defect, but he's lazy to go to a service center, so I can't confirm (yet)..
We tried rooting/unrooting, several reflashes of stock ROM, factory resets with/without apps restore etc., result is always the same - pretty much no deep sleep.
Click to expand...
Click to collapse
Yup it is a hardware issue. I fixed it by changing charging port
You could try install a custom kernel and use the boeffla wakelock blocker to block 700000.ssusb. I guess you are on Oreo?