Related
Hey,
I'm running stock nexus 4. I have been having terrible 8 hour battery life with "Android OS" taking up all the battery in battery status. BetterBatteryStats tells me that "sns_perioidic_wakelock" and "sns_async_ev_wakelock" is using up most of the battery. See attached. Any idea what apps are causing this?
http://i.imgur.com/t1gAr.png
thegreyspot said:
Hey,
I'm running stock nexus 4. I have been having terrible 8 hour battery life with "Android OS" taking up all the battery in battery status. BetterBatteryStats tells me that "sns_perioidic_wakelock" and "sns_async_ev_wakelock" is using up most of the battery. See attached. Any idea what apps are causing this?
Click to expand...
Click to collapse
I'm pretty sure I've seen those wakelocks when making a lot of phone calls. Seems likely related to cell radio use some how, but that's just a guess.
mattb3 said:
I'm pretty sure I've seen those wakelocks when making a lot of phone calls. Seems likely related to cell radio use some how, but that's just a guess.
Click to expand...
Click to collapse
Actually the crazy thing is that i have airplane mode with wifi on most of the day cause I have really bad service. And I only have 100 minutes of talk, so I never talk on the phone.
thegreyspot said:
Actually the crazy thing is that i have airplane mode with wifi on most of the day cause I have really bad service. And I only have 100 minutes of talk, so I never talk on the phone.
Click to expand...
Click to collapse
Just checked mine and those wakelocks are really low today despite several phone calls, I've been on wifi all day though. The right way to figure those wakelocks out is to download the kernel source from one of the devs github and do some searches through the source to see where those wakelocks are logged. You might also search the battery impression thread in general, some smart folks have dissected many kernel wakelocks in there. Seems weird that you would have them in airplane mode.
thegreyspot said:
Actually the crazy thing is that i have airplane mode with wifi on most of the day cause I have really bad service. And I only have 100 minutes of talk, so I never talk on the phone.
Click to expand...
Click to collapse
I have the exact same issue. Wakelocks/Android OS killing my battery (Android OS usually 45% or higher when it should be my screen that is the biggest battery sucker).
I barely use my phone to make phone calls as well. I'd say 1 call every 2 or 3 days.
Same exact wakelocks here. I made 0 phone calls. There is defiantly something up.
I had these two wakelocks too and it turned out to be my live wallpaper that was causing it
http://forum.xda-developers.com/showpost.php?p=35277041&postcount=20
Same wakelocks on my N4....
Solution in my case, delete widget locker....... My Nexy sleeps again:angel:
exact same situation: N4, sns wakelocks killing battery, phone not deep sleeping. culprit? Shake 'n Rotate! app. so add that one to the blacklist as well!
Are any of you running stock kernel and ROM?
Sent from my Nexus 7 using Tapatalk 2
Im Running stock kernal and Rom and i still get sns_periodic_wakelock and sns_async_ev_wakelock Does anyone have any idea what they are or what causes them or how to fix? They seem to be on the whole time my phone is on and they suck battery crazy not as bad as most but my android os is always 2nd battery use to my screen or more depending on how i use it and it sucks cause i know i would have pretty awesome battery life if these were fixed or gone. I appreciate any help!
Apparently you can also add: lightflow vibrate on pickup feature and adding a widget to the lock screen..
PowerManagerService and sns periodic wakelock are my main culprits but I'm not sure these numbers mean there's an issue or not...
I just checked BBS for todays use and I have on 9h use 4h on sns_periodic_wakelock. I have been using DashClock on my lockscreen. I will remove that and post back later to see if that helped.:cyclops:
Hmm can anyone say if this looks problematic?
Sent from my Nexus 4 using xda premium
Yes it does look problematic.
Basically sns_periodic_wakelock kept the device from sleeping for almost three hours.
I have the same issue and don't know what's causing it.
EDIT: Apparently live wallpapers do.
Just writing back to tell you guys how it went. I removed DashClock from my lockscreen and that wakelock seemed to be gone for a few days.
I then later updated the app, and just by updating it, I think it caused the wakelock. This time I'm uninstalling and checking if it comes back again.
Is there a known list of apps suspected of causing this?
dohkoxar said:
Just writing back to tell you guys how it went. I removed DashClock from my lockscreen and that wakelock seemed to be gone for a few days.
I then later updated the app, and just by updating it, I think it caused the wakelock. This time I'm uninstalling and checking if it comes back again.
Click to expand...
Click to collapse
I've had dashclock for the past two days.. Not seeing any wake locks. I have all the extensions from the app enabled.
Sns is related to facebook. If you use Titanium backup, go to apps and you can see a blue icon with a letter f on it that looks like facebook letter and labelled sns. Uninstall that and your lovely nexus 4 will enjoy its sleeeeep....
Edit: The 4.2.2 update seems like it fixed this wakelock from taking over. That's just my personal experience so let me know if yours is different from mine after the update.
I've searched and tried to find a solution to my problem, but I can't find anything. My main kernel wakelocks are sns_async_ev_wakelock and sns_periodic_wakelock and the time they both register is massive. This has been happening for at least a week, or at pretty much the entire time I started monitoring my wakelocks. Does anyone have any idea what these might be attached to? I originally thought they were pertaining to social networking services, so I promptly deleted the Facebook app and for a day it seemed to fix it. But then the wakelocks came back and were even worse.
Have others come across this problem and does anyone know what might be causing it? They've been preventing my phone from going into deep sleep and I would really like to reduce or get rid of them.
Updated info: I have determined that the game Asphalt 7 is at least one app responsible for massive sns wakelocks. As long as the game remains as a "recent app" it will continue to wake the phone up. Angry birds is another game possibly responsible for the wakelock as well as reddit sync. Anyone else that uses these apps regularly us encouraged to report back your findings. Using the phone prompts sns wakelocks, but the amount of time the phone contributes is identical to your talk time, so your phone is triggering a fake wakelock since the device isn't supposed to be in deep sleep while you're on the phone anyways. Right now the only fix I know of for the listed apps is to manually clear them from "recent apps".
Please include the rom and kernel you're using. So far it seems like a new kernel doesn't actually fix the problem when you're on the stock rom. So anyone on CM or PA, do you have this wakelock after having a game like asphalt 7 or angry birds sit in recent apps?
Have you tried a custom kernel like Franco's ? Might be the Qualcomm fixes.
madd0g said:
Have you tried a custom kernel like Franco's ? Might be the Qualcomm fixes.
Click to expand...
Click to collapse
Well I'm getting this on Franco's. I think it has something to do with the phone. [ I mean talking/calling on phone]
@OP,
Do you get this only when you call someone or get a call. In bbs, try a custom ref. setting and monitor for 1 hour where you were not getting/calling anyone and see if it is going down drastically. Also is the msm_hsic wakelock present for you a lot? [The custom kernels like franco, faux and others have fix for this, taken from patch commits done by qualcomm]
What were you doing with your phone in that time, were you making calls, texting, etc?
Sent from my Nexus 4 using xda premium
madd0g said:
Have you tried a custom kernel like Franco's ? Might be the Qualcomm fixes.
Click to expand...
Click to collapse
Currently full stock. And it looks like it's still present even with Franco's kernel
Hrithan2020 said:
Well I'm getting this on Franco's. I think it has something to do with the phone. [ I mean talking/calling on phone]
@OP,
Do you get this only when you call someone or get a call. In bbs, try a custom ref. setting and monitor for 1 hour where you were not getting/calling anyone and see if it is going down drastically. Also is the msm_hsic wakelock present for you a lot? [The custom kernels like franco, faux and others have fix for this, taken from patch commits done by qualcomm]
Click to expand...
Click to collapse
I talk on the phone for maybe an hour every day, so I would be surprised if it was associated with the phone since the wakelock time has been increasing this whole week while my phone time is relatively constant. Although I'm just taking the phone off the charger now and won't use it for calls for the next 2 hours, so I'll report back with what kind of wakelocks I'm getting as well was the apps I've used. As for msm_hsic_host wakelock, it is present but not as prevalent as the sns wakelocks. As you can see from the first picture I'm only getting about 20 minutes for that wakelock compared to the 4 hours of the others. If I remember correctly I ended the day with almost 5 hours for both sns and then an hour and a half for msm_hsic. So sns slowed down a bit and msm_hsic ramped up, but it didn't come close to overtaking sns
steviewevie said:
What were you doing with your phone in that time, were you making calls, texting, etc?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I was using it pretty normally. Had around an hour of talk time (cumulative over the day), texting throughout the day, streaming pandora for a little, checking emails, playing a game for a bit, and on sites like xda, reddit (through apps), and facebook (through chrome).
So far I haven't had any sns wakelocks today (well, nothing compared to what I recently had). The hisc wakelock is dominating now which seems more "normal". I only talked on the phone for a grand total of 3 minutes today so maybe that has something to do with sns. Currently charging it so I'll start getting new stats (the ones I'm posting now were taken a few hours ago), but this time I'll try to use the phone more as well as keep everything else the same. My use today has been streaming pandora, checking emails, reddit, xda, facebook, but no games (maybe that also comes into play). I'll keep updating
I'm getting massive sns kernel wakelocks too. No phone calls.
Xylon + Franco r30
Sent from my Nexus 4 using Tapatalk 2
edgeball said:
I'm getting massive sns kernel wakelocks too. No phone calls.
Xylon + Franco r30
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, yesterday I started getting sns wakelocks after I was on the phone for a while, so that might be part of it. Of course there might have been another reason behind it if you get a lot of wakelocks without the phone. Forgot to get a screenshot
This is the first day since I've been monitoring that this wakelock just went berserk. I made zero calls today. Then, I went back in time to determine what I was doing when it started. At that time, I was using Reddit Sync. Before doing anything, I locked the screen, and a few minutes later checked BBS and determined that the wakelock was still active after locking the screen. Then, I closed Reddit Sync and locked the screen. After a few minutes, I unlocked the screen and checked BBS. Sure enough, the wakelock times had frozen. So, by simply closing Reddit Sync, this wakelock has stopped, at least for now. After restarting this app, locking the screen and unlocking after a few minutes, I notice that the wakelocks were not re-activated. Well, that's my story. Do any of you use this app too?
floepie said:
This is the first day since I've been monitoring that this wakelock just went berserk. I made zero calls today. Then, I went back in time to determine what I was doing when it started. At that time, I was using Reddit Sync. Before doing anything, I locked the screen, and a few minutes later checked BBS and determined that the wakelock was still active after locking the screen. Then, I closed Reddit Sync and locked the screen. After a few minutes, I unlocked the screen and checked BBS. Sure enough, the wakelock times had frozen. So, by simply closing Reddit Sync, this wakelock has stopped, at least for now. After restarting this app, locking the screen and unlocking after a few minutes, I notice that the wakelocks were not re-activated. Well, that's my story. Do any of you use this app too?
Click to expand...
Click to collapse
No, I never used Reddit sync. However, it could be related to a general sync problem
Sent from my Nexus 4 using Tapatalk 2
edgeball said:
No, I never used Reddit sync. However, it could be related to a general sync problem
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Ha. It's not a sync program whatsoever, not in the sense that it syncs anything to the contents of your phone. It does sync in the sense that it keeps track of your "read" articles.
floepie said:
This is the first day since I've been monitoring that this wakelock just went berserk. I made zero calls today. Then, I went back in time to determine what I was doing when it started. At that time, I was using Reddit Sync. Before doing anything, I locked the screen, and a few minutes later checked BBS and determined that the wakelock was still active after locking the screen. Then, I closed Reddit Sync and locked the screen. After a few minutes, I unlocked the screen and checked BBS. Sure enough, the wakelock times had frozen. So, by simply closing Reddit Sync, this wakelock has stopped, at least for now. After restarting this app, locking the screen and unlocking after a few minutes, I notice that the wakelocks were not re-activated. Well, that's my story. Do any of you use this app too?
Click to expand...
Click to collapse
I only use Reddit News. My sns wakelocks for today match the time I was on the phone, almost identically. This has been the case for today and yesterday which leads me to believe that the phone calls are NOT responsible for this runaway wakelock (as others have been saying). I didn't use my Nexus 4 very much this weekend, and the two major functions I used it for were phone calls and checking email sporadically. Others seem to report substantial wakelocks even without calls, so this has to be attributed to some app or setting that we're missing. Although I'm more inclined to think it's a problem with an app (or apps) because limited use seems to result in limited wakelocks, and if it was a system setting then it would be fairly constant. Has anyone gotten low sns wakelocks after not using their phone much in a day (like not using very many apps)? And thanks for the input so far
Async could stand for asynchronous, the CPU functions asynchronously but, I have no clue whether that wake lock is really cpu related.
Sent from my Nexus 4 using xda app-developers app
Ace42 said:
Async could stand for asynchronous, the CPU functions asynchronously but, I have no clue whether that wake lock is really cpu related.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think it might be but I'm not completely sure.I found out last night that the game Asphalt 7 was responsible for a couple hours of wakelocks. However, in the system battery stats it registered as 0s for keeping the phone awake while android os registered the 2 hour jump I saw after playing the game. I played for a few minutes and jumped back to the home screen and didn't touch the game for those 2 hours. I'm not sure why, but having the game in my recent apps triggered those wakelocks, and the second I swiped it out of recent apps the wakelocks stopped. Either the app is bad or maybe the system isn't handling it correctly. I'll be trying other apps to see what the results are.
Sent from my Nexus 4 using xda app-developers app
I use redditsync and also had a 7hour snsw wake lock overnight... Gonna keep an eye on it and hope it was a one off (or an update gets pushed out)
cyberkid2002 said:
I use redditsync and also had a 7hour snsw wake lock overnight... Gonna keep an eye on it and hope it was a one off (or an update gets pushed out)
Click to expand...
Click to collapse
Alright, so that's two people getting wakelocks from redditsync. What happens when you clear redditsync from your recent apps? Does the wakelock continue or does it stop? This definitely sounds like the system isn't handling some of the open/recent apps correctly. No idea what links these apps together though
I am using Franco 62 with stock ROM and it turns out that Angry Birds Seasons can cause these wakelocks as well. Glad I'm not the only one with this issue.
I have never had these wakelocks previously (only the famous msm_hsic_wakelock). Yesterday after I installed a couple of apps (most are just theme-ing apps with no sync) and flashed custom kernel (Franco.r53); and ever since then these two wakelocks are continously appearing in my BBS stats, almost preventing my phone from entering deep sleep AT ALL. So I thought it was the kernel's problem; flashed back stock kernel and the problem still persists.
It's really weird as I previously NEVER had these two wakelocks.
By the way, I'm on stock ROM (rooted, unlocked)
chy1991 said:
I have never had these wakelocks previously (only the famous msm_hsic_wakelock). Yesterday after I installed a couple of apps (most are just theme-ing apps with no sync) and flashed custom kernel (Franco.r53); and ever since then these two wakelocks are continously appearing in my BBS stats, almost preventing my phone from entering deep sleep AT ALL. So I thought it was the kernel's problem; flashed back stock kernel and the problem still persists.
It's really weird as I previously NEVER had these two wakelocks.
Click to expand...
Click to collapse
Thanks for the update. But, it begs the question as to whether you uninstalled the new apps one by one to hone in on a possible culprit?
floepie said:
Thanks for the update. But, it begs the question as to whether you uninstalled the new apps one by one to hone in on a possible culprit?
Click to expand...
Click to collapse
I'm suspecting something else, will update if it's solved.
UPDATE:
This is really weird, I have uninstalled what I installed yesterday and the problem persists, so I decided to try something else (as it was the another differences factor compared to pre-problem).
My WiFi was disconnected in middle of the night and I thought it could be causing it.
I turned my WiFi off, turn it back on and the problem is gone. This is really weird, as I have rebooted many times prior to trying this solution (and even flashed back to Stock Kernel).
Really random or just plain unlucky? I have even reinstalled the apps that I thought are causing the problem, but still fine so far. Gotta leave it overnight again to judge.
Hey guys,
As the title suggests - I'm enquiring about wakelock triggers (reported by WLD (Wakelock detector.))
As you can see, Facebook messenger has triggered my phone awake nearly 400 times in the space of my work day! I know Facebook and its messenger app has its reputation for being a battery hog, but there's no 'actual' wakelock in use!
Anyone know what's going on here? Anyone able to shed insight and or compare with their device?
With the second screenshot, you can see the difference between awake and screen on. I use aeroplane mode when I work, due to not having any signal at all - I just use WiFi.
Thanks in advance guys.
I'd look into something like naptime, power nap, greenify, so that you can basically shut it off when not in use, cause your system is definitely not sleeping.
Someone said there was a 'lite' facebook messenger app on xda, but I don't use it, so I don't know the name off the top of my head.
I have a moto pure running 6.0. Recently I ran into an issue with the google search bar crashing every time i tried a search. I went an uninstalled the google app, rebooted and reinstalled. This resolved the crash with google search but started another issue.
I was having the google app being my number 2 battery user with high CPU pretty much spot on matching the screen time - the device was warm and battery life reduced by 3x from my normal. I installed a CPU monitoring app and noticed that the CPU usage was about 15% continuous for the google search bar googleqicksearchbox:search and googlequicksearchbox together take about 15% and don't stop.
I've tried:
uninstalling the google app, reboot, reinstall
cleared caches for the google app
cleared caches for the google now launcher
uninstalled and reinstalled the google now launcher
Nothing resolved the issue until i did this:
If i remove the google app 4x3 widget the CPU returns to normal - battery returns to normal.
So, it appears to be related to the widget. Does anyone have any other ideas on how to resolve this so i can use the widget? I figure I might be stuck with having to factory reset to resolve.
Google App update constantly listens to audio.
You see it too?
There seems to have been an update on 2/19/16 that broke it, and my own device seems to have picked up the update on 2/26. I noticed that the battery was draining very quickly for the past couple of days, even when idle with the screen off, though it wasn't warm or anything as is usually the case when something goes awry. GSam Battery Stats showed the usual mess of inexplicable Googleness chomping at things, using sensors, and being Googley, but nothing grossly out of the ordinary.
And with the screen on, doing the usual non-intensive things I do, I could watch the battery percentage drop precipitously: 4 percent in a few minutes.
I was using Google Now Launcher, and figured that might be related. I switched to a different launcher, no change. Rebooted for good measure and to make sure Google Now Launcher was definitely not running, no change.
Then I froze the Google App in TiBackup, and the problem went away.
I honed into it being Google App by using top. In a terminal: top -t -b 16. Screenshot: i.imgur.com/19bVXsG.png (no link because I'm too n00b here).
Of note in the screenshot is PID 14272. It's got a lot of threads going, which is not unexpected.
What was unexpected is that some of them were listening to audio. The thread names are abbreviated by top, but one of the threads (14582) is MicrophoneReade which occasionally showed some CPU usage. Another constantly-active thread (14581) is MicroRecognitio, a name which implies TTS. And PID 787, /system/bin/mediaserver, was pretty insistent on using CPU as well with its thread (14584) called AudioIn_2D, verifying that audio was being recorded.
All of this disappeared from top when I froze Google App.
To be clear, I don't use the "OK Google" always-listening function because it drains the battery quickly on my device, but I did have "OK Google" enabled on the home screen. However that shouldn't be happening with another launcher that has no (zero) widgets enabled at all.
So it shouldn't have been listening at all, but it was listening all the time. And this was apparently computationally expensive, and thus hungry for battery.
Samsung Galaxy S5, VZW, running MOAR and Xposed.
My particular issue seems to be related to the 4x3 google now widget. I can use the Google now launcher just fine, till I add that widget then a things go to hell... I really like that widget...
This same thing happened to me on my M9 starting on 2/26. It was getting seriously hot (110-120F) all the time and battery was draining at 33% an hour idle. Navigation was also very choppy and slow. Verizon actually sent me a replacement phone due to the constant over heating and factory resets. Once i got my new one I didn't restore from backup and loaded apps one by one. Sure enough as soon as the NOW widget was added, the phone slowed down and heated up.
With the widget off now for 2 days i am getting my usual 12 hours battery and the temp hasn't gone over 100 F.
Big news from my perspective. Last night I got a Google app update. Today the widget no longer slows down the phone /no more hot phone. Seems like the update fixed it for me... Time will tell.
That's why I don't use that crap! lol. Spies I tell you, spies.
Big news from my perspective. Last night I got a Google app update. Today the widget no longer slows down the phone /no more hot phone. Seems like the update fixed it for me... Time will tell.
Everyday on my battery usage, 2nd biggest user is the system clock, it's been kept awake for over 7 hours, I have no alarms set, I don't even have the clock widget.
Anyone ever seen this? Is it normal, or am I missing something?
markdexter said:
Everyday on my battery usage, 2nd biggest user is the system clock, it's been kept awake for over 7 hours, I have no alarms set, I don't even have the clock widget.
Anyone ever seen this? Is it normal, or am I missing something?
Click to expand...
Click to collapse
I had the same issue. As far as I know, it's a bug in Google Clock. If I recall correctly, there was an Android Police article about it on G+. Haven't noticed it as of lately though so I assumed it was fixed and another version. Make sure it's updated in the Play Store. If it is and you're still having the issue, I just made sure to force close the app every morning after my alarm went off. Issue was gone.