Hi!
Ever since I updated to .157, I have a lot of FastDormancy related alarms draining my battery. Specifically, I have 53% awake time with 21% screen on time. Most of this is caused by FastDormancyWakeupServer (refer to the attached screenshot). Wakelocks and partial wakelocks are within reasonable bounds.
Since the modem was updated with the .157 OTA, I suspect that some of you might have had the same problem.
Has any of you encountered this before, and how did you solve it?
Related
My phone occasionally fails to go to deep sleep and battery drops 10% per hour ( screen off )
Installed wakelock detector and the top offender was msm_hsic_host kernel wakelock,
in extreme cases it was keeping the device busy at 50% of the time
tried google a lot, lots of people have this issue ( not just S4 ) but there doesn't seem to be a solution to the problem.
anyone else getting this treat ?
any fix?
update: attached screenshots
workaround found?
just following up ...
last night installed "Easy battery saver" and configured it to disconnect data/wifi when screen is off.
8 hours stand-by 4% battery is ( 0.5% per hour !!! ) -> before it was 10% per hour
phone awake 2% -> before it was 50 %
also msm_hsic_host wakelocks are gone.
anyone else getting these wakelocks?
s.illes79 said:
anyone else getting these wakelocks?
Click to expand...
Click to collapse
Yup, on CM10.2. Very annoying and no idea how to solve it
Pfeffernuss said:
Yup, on CM10.2. Very annoying and no idea how to solve it
Click to expand...
Click to collapse
I'm on stock 4.2.2 , I guess there is no point to flush a custom ROM
only workaround so far is to disable 3g/4g data ... when samsung is going to address this? last night got an OTA (1.2mb only) but this bug is not fixed there ...
u not going to believe this:
- I turned off (yes OFF) samsung power saving mode and no longer have the msm_hsic_host wakelocks ... must be a bug
looks like it has been fixed in new FW ( MH8 )
we'll see in long term
This is after the 4.4 update.
I can't figure out the exact cause, but there are several occasions where I have left the phone idle for several hours, only to discover that the phone has not entered deep sleep, having instead been kept awake by Mediaserver the entire time. Unfortunately, I can't get access to the Partial Wakelock stats via BetterBatteryStats, but the time for the PowerManagerService.WakeLocks "container" under the Kernel Wakelock section roughly matches the awake time.
I have done some googling for solutions to this problem and most threads suggest a potential issue with media scanning (e.g. a corrupted .mp3 causing a background process to get stuck in a loop). However, I haven't been able to eliminate the problem with any of the proposed solutions.
However, the last few times this has happened, I have noticed that Bluetooth was enabled and paired with my headset. Also, in each case, the awake time for the Mediaserver process (under battery stats) continues to increment UNTIL I disable Bluetooth, at which point the awake time counter stops incrementing. Also, since I started paying closer attention to this behavior, I have yet to see the same deep sleep (i.e. wakelock) issue while Bluetooth is disabled.
I believe this is enough evidence to prove that the offending wakelock is somehow related to Bluetooth.
Does anyone else see this behavior?
I've seen it on other phones. And adding Bluetooth into the mix may make my advice unhelpful.... But that aside, rebooting after unplugging from charger every time has fixed that issue in the past.
Sent from my XT1058 using Tapatalk
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.
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
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?