Related
So, yesterday I noticed a sudden battery drain on my nexus 4. After checking battery it showed that AndroidOS takes over about 50% of the battery usage. It also showed that time awake was pretty much the same as the amount of time since I unplugged the phone, even though I kept my phone in sleep mode for the most of the day. After some research I downloaded better battery stats and it showed that from the moment I turn the screen off a process called suspend_backoff runs pretty much the entire time. Eventually I got it down to wifi. If I turn off wifi there are no processes running after the screen is turned off (or if there are they are 30 seconds tops), but the moment I turn wifi on suspend_backoff runs pretty much the entire time screen is off. I tried removing all of my apps, as well as doing factory reset but nothing helps. The moment I turn wifi ON this suspend_backoff consumes pretty much all the time during screen off period. Is anyone experiencing anything like this ? I have 4.2.2 on the phone and I havent' seen this extreme drain until just yesterday.
I experience the samething. Android OS would drain as much as the screen time.
I narrowed it down to the suspend_backoff. But the weird thing is that when i'm at home on my home wifi, suspend_backoff doesn't seem to drain anything at all. But when I'm at school, suspend_backoff kicks in.
Anyone help?
hihihoho said:
I experience the samething. Android OS would drain as much as the screen time.
I narrowed it down to the suspend_backoff. But the weird thing is that when i'm at home on my home wifi, suspend_backoff doesn't seem to drain anything at all. But when I'm at school, suspend_backoff kicks in.
Anyone help?
Click to expand...
Click to collapse
how did you narrow it down? Im having the same problem!
This is caused by a kernel wakelock. A bad mobile connection make battery drain worse... using WLAN nearly fixes this problem.
Thought this problem has got fixed in 4.2.2, at least battery life got improved and the wakelock reduced.
If it is appearing since yesterday, it is triggered by a app often waking the phone up using mobile data (that's why fixed with WLAN) and prevent the phone from getting into deep sleep as fast as it should.
hope i could help.
I use Greenify to hibernate every single user installed apps, then I release them one by one to see which one cause suspend backoff. But suspend backoff still occurs. So I think it's the kernel itself.
AW: Battery drain on nexus 4 since yesterday
hihihoho said:
I use Greenify to hibernate every single user installed apps, then I release them one by one to see which one cause suspend backoff. But suspend backoff still occurs. So I think it's the kernel itself.
Click to expand...
Click to collapse
as i said before, an app needs data, so it starts callung the kernel wakelock... this one causes tje drain, not the app itself
Sent from my Nexus 7 using xda app-developers app
hihihoho said:
I use Greenify to hibernate every single user installed apps, then I release them one by one to see which one cause suspend backoff. But suspend backoff still occurs. So I think it's the kernel itself.
Click to expand...
Click to collapse
Yeah, definitely not user apps. I did full reset on the phone to factory settings, no user apps. Even tried disabling Google Play and Google store after the reset. Still the same. The only thing that gets rid of it is disabling WiFi.
hihihoho said:
I experience the samething. Android OS would drain as much as the screen time.
I narrowed it down to the suspend_backoff. But the weird thing is that when i'm at home on my home wifi, suspend_backoff doesn't seem to drain anything at all. But when I'm at school, suspend_backoff kicks in.
Anyone help?
Click to expand...
Click to collapse
When did you start noticing this ? Has it been for a while or just recently ? I first noticed it yesterday (had the phone for a bit over a month now, didn't see any issues until just yesterday)
hihihoho said:
I use Greenify to hibernate every single user installed apps, then I release them one by one to see which one cause suspend backoff. But suspend backoff still occurs. So I think it's the kernel itself.
Click to expand...
Click to collapse
What is the difference between greenify and limit background apps in developers options?
AW: Battery drain on nexus 4 since yesterday
stop discussing, use search instead... http://forum.xda-developers.com/showthread.php?t=1999368
like i told you 3times now.... it's the wakelock
Sent from my Nexus 7 using xda app-developers app
indoh said:
stop discussing, use search instead... http://forum.xda-developers.com/showthread.php?t=1999368
like i told you 3times now.... it's the wakelock
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah, it's clear that it's the wakelock. What's not clear is why. Also it's not the msm_hsic_host that the forum link you sent refers to. I don't have a problem with msm_hsic, that one barely takes any time during the day (maybe 30 seconds during several hours of standby). The wakelock causing this particular issue is "suspend_backoff" wakelock which supposedly happens when there is a sequence of sleep/wake calls too close together so the system decides to keep it awake. I was unable to find what exactly is causing the issue, even after restoring to the factory settings I kept seeing the same problem.
Anyway, I was able to "resolve" it by installing JuiceGuard app and setting it so it disables wifi when the screen is off. wakelock is gone now and my battery usage is back to normal.
I only get the suspend backoff wake lock when I'm connected to the university Wifi. When I'm at home, everything is fine, no suspend backoff. So my guess is that the Wifi encryption at university is different and causing a succession of close "awake" and cause wake lock.
I did factory reset like 3 times and it still there.
I'll try disable Wifi on Monday and see how it goes.
Same here, when wifi disabled the wakelock doesn't occur.
I have tried almost all of the kernels and non of them seem to help.
hihihoho said:
I only get the suspend backoff wake lock when I'm connected to the university Wifi. When I'm at home, everything is fine, no suspend backoff. So my guess is that the Wifi encryption at university is different and causing a succession of close "awake" and cause wake lock.
I did factory reset like 3 times and it still there.
I'll try disable Wifi on Monday and see how it goes.
Click to expand...
Click to collapse
Interesting... Maybe it is encryption. One thing with my Wifi is that it doesn't use password, but MAC list instead. It may indeed be an issue with different wifi encryption types.
OP do you have maps 6.14 on your phone? Mine kept switching on location reporting for a while and it woke my phone 344 times last night. I've been struggling with the same wake lock issues. I'm going to recharge (again) with maps disabled and see if that helps.
Sent from my Nexus 4 using Tapatalk 2
Check your Google account sync settings... In settings
The clowns may have left you a lovely gift there without telling you or asking any kind of permission.
The latest Maps was giving me horrible battery drain, on WiFi. I'd sleep for six hours with a fully charged phone and wake up with 10% left. it even enabled itself when. I disabled it in settings. I converted it to a user app by moving it to /data/app and greenified it. Seemed to have solved all of my issues with the suspend back off wake lock.
Download greenify
Sent from my Nexus 7 using Tapatalk 2
For some weird reason, I was also having serious battery drain suddenly since yesterday.
Turned out it was maps, and disabling Google network locations hugely increased battery life
Sent from my Nexus 4
Hi guys,
Please bear with me as I've never owned an Android phone before.
I have a Samsung Galaxy S4 I9505 and last week, it started having major battery drain of around 4%-5% per hour of idle screen-off time. This was much more severe than it was in the first two weeks of ownership, which was only about 1% or less an hour. Unfortunately, I have not been able to fix this issue.
I had heard about wake locks in Android, so I downloaded the app Wake Lock Detector and ran it a few days ago. It seemed from the analysis that by far the biggest consumer of my battery was a "com.sec.app.clockpackage". Here is the screenshot I took from the app a few days ago.
tinypic.com/view.php?pic=qzhohx&s=5
I tried googling this and it seems related to the alarm clock???!!! However, I couldn't find anything to help solve my problem. Even after I turned off the alarm clock and deleted all alarms set nothing would solve the problem.
The problem persisted and I decided a few hours ago after having the problem for half a week to factory reset the phone, thinking that I had some rogue application. After resetting the phone, I immediately installed Wake Lock Detector and nothing else.
However, that did not solve the problem. This is another screenshot I took from the app just a while ago.
tinypic.com/view.php?pic=20rx9f&s=5
If you would note, once again com.sec.app.clockpackage is dominating the partial wake lock list.
Could anyone please help me with this - How come a factory reset did not help restore it to how it was when I first bought it, when I didn't have this issue of draining 5% battery per hour? One thing I have noticed is the number of wake locks for com.sec.app.clockpackage is approximately the same in number as com.sec.phone, although that process takes up far less time overall.
Would anyone be able to help me out? I don't know much about these technical things. Many thanks!
jjs82 said:
Hi guys,
Please bear with me as I've never owned an Android phone before.
I have a Samsung Galaxy S4 I9505 and last week, it started having major battery drain of around 4%-5% per hour of idle screen-off time. This was much more severe than it was in the first two weeks of ownership, which was only about 1% or less an hour. Unfortunately, I have not been able to fix this issue.
I had heard about wake locks in Android, so I downloaded the app Wake Lock Detector and ran it a few days ago. It seemed from the analysis that by far the biggest consumer of my battery was a "com.sec.app.clockpackage". Here is the screenshot I took from the app a few days ago.
tinypic.com/view.php?pic=qzhohx&s=5
I tried googling this and it seems related to the alarm clock???!!! However, I couldn't find anything to help solve my problem. Even after I turned off the alarm clock and deleted all alarms set nothing would solve the problem.
The problem persisted and I decided a few hours ago after having the problem for half a week to factory reset the phone, thinking that I had some rogue application. After resetting the phone, I immediately installed Wake Lock Detector and nothing else.
However, that did not solve the problem. This is another screenshot I took from the app just a while ago.
tinypic.com/view.php?pic=20rx9f&s=5
If you would note, once again com.sec.app.clockpackage is dominating the partial wake lock list.
Could anyone please help me with this - How come a factory reset did not help restore it to how it was when I first bought it, when I didn't have this issue of draining 5% battery per hour? One thing I have noticed is the number of wake locks for com.sec.app.clockpackage is approximately the same in number as com.sec.phone, although that process takes up far less time overall.
Would anyone be able to help me out? I don't know much about these technical things. Many thanks!
Click to expand...
Click to collapse
Hi,
I have the same problem. Not with the clock but after 2 weeks it started to have major battery drain. i don't know what to do in order to solve this.
Hi bbbb2004, it seems like no one has been able to help us so far.
However, did you also initially have no problems with the battery and it only started getting worse a few weeks in?
Maybe you could also try Wake Lock Detector to try to find out what the cause is. From the pics I posted, I found out what the cause is on paper, but I have no idea what it actually is...
jjs82 said:
Hi bbbb2004, it seems like no one has been able to help us so far.
However, did you also initially have no problems with the battery and it only started getting worse a few weeks in?
Maybe you could also try Wake Lock Detector to try to find out what the cause is. From the pics I posted, I found out what the cause is on paper, but I have no idea what it actually is...
Click to expand...
Click to collapse
I did try Wake Lock and saw the problem: 1. exchange service 2. com.facebook.katana and third place is facebook messenger. Initially, when i bought the phone i had no problems but after 2 weeks it started to get worse. Interesting thing is that now is going down like 12-15% / hour almost without any usage and the phone gets really hot in the camera area.
Today the phone died while the battery was at 43%. The left corner led was blinking blue and no button was working. The only thing i could do to start was to remove the battery and put it back.
Been quite a while and the problem still hasn't resolved itself. On a daily basis, I can get up to one hour of wake lock from the reading on Wake Lock Detector and GSam battery monitor. (and they show exactly the same time)
I have however gotten a bit closer to trying to solve the issue. The wake lock seems to clock much more faster at my house than when I'm outside. If I'm out all day, I can come back with only around 3-5 minutes of wake lock from com.sec.app.clockpackage. It still accumulates over time, but at a substantially lower rate.
I have no alarms set.
The only thing I can think of is that reception at my house is not superb, and does fluctuate based on the indicator bars shown on the phone. However, I don't think that fluctuating reception can cause a wake lock for com.sec.app.clockpackage, which is something to do with clocks presumably.
Anyone have any other ideas?
jjs82 said:
Been quite a while and the problem still hasn't resolved itself. On a daily basis, I can get up to one hour of wake lock from the reading on Wake Lock Detector and GSam battery monitor. (and they show exactly the same time)
I have however gotten a bit closer to trying to solve the issue. The wake lock seems to clock much more faster at my house than when I'm outside. If I'm out all day, I can come back with only around 3-5 minutes of wake lock from com.sec.app.clockpackage. It still accumulates over time, but at a substantially lower rate.
I have no alarms set.
The only thing I can think of is that reception at my house is not superb, and does fluctuate based on the indicator bars shown on the phone. However, I don't think that fluctuating reception can cause a wake lock for com.sec.app.clockpackage, which is something to do with clocks presumably.
Anyone have any other ideas?
Click to expand...
Click to collapse
Try turning off your email sync and facebook apps. If it still happens, you could try a factory reset or reflashing the firmware. Sometimes its just a bad s/w write and a factory reset could fix that.
Hey guys, I'm having some wakelock issues.
I run greenify on draining apps and have some unused apps/processes frozen, but still have these issues.
So my questions are:
1) Could my battery drain be wifi/3g related? sometime it seems so, sometimes not.
2) Are these immense amounts of wakelocks normal? Audiomix could possibly be because of broken mp3 songs, have them already checked but not deleted. but i didn't even listen to music on this battery cycle.
3) WLD seems to lack some processes. What could cause it to not display the missing ones?
I highly doubt you have an issue here. Your battery doesn't look to be draining much at all. You're at 1 day and 3 hours according to BBS, 1 day and 18 hours according to your phone, and your highest wake lock is less than 30 minutes. That looks like Media, probably from music. That's pretty damn good for 27 hours or more I'd say. There's this misconception that all wake locks are bad. That's not the case. Wake locks are going to happen. Its unavoidable. If you had a wake lock that was at 3 hours or more I'd worry. But you don't, so I don't think you have an issue. Just enjoy your phone.
Never said, that i think they are bad
I just wondered, because 3k+ is quite a high number and i didn't find something i could compare it too. So i didnt know if it was normal or not.
Battery life is ok, but not that great. On the posted cycle, screen on time was just around 2-3 hours. Im getting some drains here and there and havent been able to figure it out yet.
But thanks mate
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.
My battery life had previously been fine. We had that last security update from AT&T and suddenly, my device is awake almost 100% of the time. Android OS is always at the top of my stats and awake time shows at 99%. I used the light version of Wakelock Detector (which doesn't require root) and it's not really showing anything, but I deleted all apps showing the most wakelocks anyway and I'm still at 99% wake time. I even took out my SD card to test that and it hasn't changed anything. I also disabled GPS to test and "awake time" still stayed at max.
I'm on the verge of wiping it, but I have already done that once to resolve other issues and I know there has to be a cause to all of this. Is anyone else experiencing this since the last update? Anything I haven't tried that someone recommends? I have not installed any new apps or anything.
One thing to note is that my drain is only around 1%/hr at idle, but I'm pretty sure the phone still shouldn't be awake almost 100% of the time.
1%/hr drain while idle means 4 days of standby i think you're fine
greyhulk said:
One thing to note is that my drain is only around 1%/hr at idle, but I'm pretty sure the phone still shouldn't be awake almost 100% of the time.
Click to expand...
Click to collapse
percussionking said:
1%/hr drain while idle means 4 days of standby i think you're fine
Click to expand...
Click to collapse
That doesn't change the fact that the phone is awake over 99% of the time. After a wipe, it's no longer going that and my idle drain is less. So, something was clearly wrong.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Yeah, you're right if the behavior is different after resetting the phone. I was wondering if maybe Wakelock Detector might see certain features of the QC820 like AOD as applying a wakelock.