Related
Hello!
I received my nexus on Monday and so far I've only noticed one problem: there's a mysterious "Google services" process draining my battery. Just from leaving the phone unplugged over night the battery is already half drained. Looking at the battery stats I get this data, which I really can't understand. With this wake and cpu times, it makes no sense at all that this is draining the battert, does it? What's going on?
http://imgur.com/oEP13
http://imgur.com/2ucaL
Edit: Don't know how to use thumbnail so I'm just gonna put the raw links
I have the exact same thing google services has taken 43% but battery life had been ok not great not bad but just ok
I've had that.
Fixed by disabling location history.
Are you using Google currents. When the nexus 7 came out many had issues with drain when they had Google currents installed. For me it didn't even master if I had it synced. I uninstalled it and problem solved. Since I don't have mine yet that's the only thing I can recommend.
sent from my perfect 32GB Nexus 7
Disabled Google Currents (can't be uninstalled) and unchecked Location Reporting and Location History from the maps app. Will report later this night
Thanks.
hallucynogenyc said:
Disabled Google Currents (can't be uninstalled) and unchecked Location Reporting and Location History from the maps app. Will report later this night
Thanks.
Click to expand...
Click to collapse
Any news?
None. I've moved to the wierd wakelock thread to discuss the battery problems btw
Sent from my Nexus 4 using Tapatalk 2
not fully related, but on my N7, I was getting crazy battery drain from google wallet after updating it. Reverting wallet back to the stock version that came on the N7 fixed it. (even stranger was that I never setup wallet for NFC to begin with, and I keep NFC off)
disable sync from your gg account. gg services include gg book, magazine, music, map, chorme, gmail...
Having the same issue. Didn't start draining till about 4 hours off the charger...
I am also having this issue. Google Service is the number 1 battery eater. Right now it is at 56%.
Did anyone find the cure?
I'm having this problem. Cleared all data, installed a new kernel etc. A ton of Google stuff disabled, currents included. Only sync I have to both my connected Google accounts are gmail to my knowledge.
Help!!
Disable Location Services, especially the Wifi one.
ace7196 said:
Disable Location Services, especially the Wifi one.
Click to expand...
Click to collapse
Both are off and have been off.
Also having the same problem - after doing a quick search, seems to be affecting a lot of people. Has anyone found a solution?
I am NOT rooted, completely stock. Had phone about a week, and today was the first day I noticed significant battery drain (down to <10% in 8 hours) under very minimal use at work (sat in desk drawer most of the day)
Sorry, can't post direct link to image since i'm under 10 posts. Remove the space in "www" and "https"
ht tps://w ww.dropbox.com/s/xxedstxoozx4bwv/2013-02-07%2018.38.05.png
chopstxnrice said:
Also having the same problem - after doing a quick search, seems to be affecting a lot of people. Has anyone found a solution?
I am NOT rooted, completely stock. Had phone about a week, and today was the first day I noticed significant battery drain (down to <10% in 8 hours) under very minimal use at work (sat in desk drawer most of the day)
Sorry, can't post direct link to image since i'm under 10 posts. Remove the space in "www" and "https"
ht tps://w ww.dropbox.com/s/xxedstxoozx4bwv/2013-02-07%2018.38.05.png
Click to expand...
Click to collapse
I have the same problem, I dont know when it started, I think after updating from 4.1.2 to 4.2.x. Anyone found a solution?
I'm just now having the same issue here even after trying turning off those different things. There doesn't seen to be anything definitive out there online when I searched. It's probably something Google will have to fix, or will fix hopefully.
Same here. I went through all of the google settings and switched off everything (Contacts and Calendar were the only things I left ticked). Nothing seems to work...
I uninstalled Maps entirely and made sure none of Google's features were enabled but for some reason, Google Services is still eating its way through my battery.
and its not only on nexus.iam suffering the same drain with my xperia T too
I noticed this after the Google Services Update which includes a lot of new API's.
Sent from my Nexus 4 using xda app-developers app
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....
In the past few days out of nowhere I've noticed a massive amount of battery life attributed to Google Services. I checked on better battery stats and the wakelocks are coming from process: NLPWakeLock.
I've searched on the net and several forums, and I'm getting very mixed info. The majority of the info points to Google Now as being the culprit, and that it's somehow related to 4.3. I actually really like Google Now and would hate to disable it. It's odd because I've had the phone a few weeks and Google Now was always enabled, but only now these wakelocks are starting to show up.
Does anyone have any further info on this? Could it be something else? I've already frozen so many things in TiBu I'm losing track!
TIA!
I'd like to just confirm in case anyone else was having this issue - it was in fact Google now.
siciliano777 said:
I'd like to just confirm in case anyone else was having this issue - it was in fact Google now.
Click to expand...
Click to collapse
So did you just freeze Now? I'm having the exact same issue -- was working fine until just recently (I think 3 days or so ago) when I started getting many wakelocks from NLPCollectorWakeLock and NLPWakeLock. I also like using Now and don't want to disable it if I can avoid it. I did find a thread in the G2 forums with a possible solution: http://forum.xda-developers.com/showthread.php?t=2453850
Basically, he deleted GooglePlayServices using Titanium, then reinstalled directly from the market and found that fixed his issue. So I just deleted it (phone auto rebooted after doing so), then got a notification saying Maps request an update of Play Services which I got from the market. Rebooting now, will keep an eye on the wakelocks and let you know how it goes.
I didn't freeze it, I just turned it off within Google now settings. I'd like to keep it on too, but it def helped battery life.
Let me know if that method you used works.
Thanks!
So after updating facebook and messenger (facebook) I've found huge wakelocks in bbs. Anyone else having this issue? It's related to some kind of bug reporting?
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
*job*/com.facebook.orca/com.facebook.bugreporter.scheduler.LollipopService (com.facebook.orca.Messenger): 37 m 20 s Count:10 22.2%
*job*/com.facebook.katana/com.facebook.bugreporter.scheduler.LollipopService (com.facebook.katana.Facebook): 30 m 2 s Count:6 17.8%
Same here........I'm locking it down using the Amplify Xposed module.
Prey521 said:
Same here!
Click to expand...
Click to collapse
It's causing massive wake time if left alone for a few hours. I went ahead and limited the wakelocks in amplify. Set it to allow them every 10th hour on trial. We'll see if that causes any problem.
I noticed this too. I watch battery like a hawk but this is the first time Facebook had shown much drain in the last few months. This was build still 59.0.0.3.313
Looks like tonight's build still has the issue.
I recommend reporting in the Facebook app itself.
Sent from my A0001 using Tapatalk
dmo580 said:
I noticed this too. I watch battery like a hawk but this is the first time Facebook had shown much drain in the last few months. This was build still 59.0.0.3.313
Looks like tonight's build still has the issue.
I recommend reporting in the Facebook app itself.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I've disabled them both in amplify. I don't feel I want battery every spent on uploading any form of reports. I've also limited facebook wakelocks apart from this to every 15th minute. It's spending too much battery on something irrelevant.
Reported it already.
Even my fiancee's Galaxy S5 (which can usually get through to the end of the day with 65+% battery left) was saying that her battery has been draining very quickly.
So I know Facebook in general gets a bad reputation, but as someone who watches wakelocks on a daily basis and the battery page, this is really the first instance of Facebook misbehaving in at least 2-3 years.
Anyway, is this something like you guys are seeing? https://imgur.com/a/rpO0j
The background drain isn't TOO Terrible. It's around ~2.5% / hour screen off on LTE (honestly that's what I got on a OnePlus One on Lollipop anyway), while the screen on drain was around 25% / hr
BTW, are you using Facebook/Messenger beta? I'm only in the Facebook beta program, so I don't see any issues for Messenger on my side yet.
are you using Facebook/Messenger beta?
Not using betas. I can't agree regarding facebook and battery life. It'd suppose to use cgm but still it had a heap of timers going off and the app is ever high in wakelock detector. I've had enough and now limited most of its alarms and wakelocks in amplify to no more often than every 15 mins. This has lowered facebooks position in the wakelock list to a much more acceptable level. No problems arise either apart from not getting notifications as expected but that's been a problem for years over multiple handsets.
I can even confirm it, the same wakelocks and drain have been appearing on my OnePlus One too.
I use amplify and prevent wakelocks to everything pertaining to Facebook to 86400s. That's once per day and haven't had any detrimental effects from the app. All still works as it should.
TigerSoul925 said:
Not using betas. I can't agree regarding facebook and battery life. It'd suppose to use cgm but still it had a heap of timers going off and the app is ever high in wakelock detector. I've had enough and now limited most of its alarms and wakelocks in amplify to no more often than every 15 mins. This has lowered facebooks position in the wakelock list to a much more acceptable level. No problems arise either apart from not getting notifications as expected but that's been a problem for years over multiple handsets.
Click to expand...
Click to collapse
What version of Facebook are you on?
BTW Facebook does use GCM. IT only uses MQTT when you are actively in the Messenger app. I'm not entirely certain what's going on here. The wakelock is com.facebook.bugreporter.scheduler.LollipopService so it seems to be bug reporting related and not notification related.
dmo580 said:
What version of Facebook are you on?
BTW Facebook does use GCM. IT only uses MQTT when you are actively in the Messenger app. I'm not entirely certain what's going on here. The wakelock is com.facebook.bugreporter.scheduler.LollipopService so it seems to be bug reporting related and not notification related.
Click to expand...
Click to collapse
Oh! Funny thing is, I've limited the mqtt stuff and I've had zero issues getting messages right away when screen is on or off in messenger but thanks to the mods facebook stuff is now farther down on the list of wakelocks rather than high. If those mqtts were only used when active, why use wakelocks for it at all? And why do they creep up in count when the screen is off? 60.0.0.2.76
Sent from my Nexus 6P using Tapatalk
TigerSoul925 said:
Oh! Funny thing is, I've limited the mqtt stuff and I've had zero issues getting messages right away when screen is on or off in messenger but thanks to the mods facebook stuff is now farther down on the list of wakelocks rather than high. If those mqtts were only used when active, why use wakelocks for it at all? And why do they creep up in count when the screen is off? 60.0.0.2.76
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
MQTT is only used when the app is in the foreground meaning its being actively used and screen on. Therefore it shouldn't cause wakelocks. I'm guessing MQTT is used because GCM can see delayed notifications sometimes. MQTT is probably better suited for real time chat.
What wakelock are you seeing? Is it the one I posted earlier? If so I'm not sure if that sure it has anything to do with the actual chatting and communication portion of the app. The wakelock has to do with a bugreporter, which is misbehaving when your screen is off.
I think I know the answer, but no way to help this without root right?
I can confirm, same problem on Nexus 5x (not rooted) latest version of Facebook... Updated this morning, caused wakelocks, uninstalled, problem solved. Shame I have to uninstall it to fix...
I have 60.0.0.5 now... Facebook simply minimizes itself automatically now. Anyone else seeing this behavior? I have greenify on Facebook as well as amplify to limit some wakelock. Might be the cause...
I am seeing this issue as well with com.facebook.bugreporter.scheduler.LollipopService causing massive drain.
I just have Messenger 53.0.0.17.308.
Since I do not want to install Xposed + Amplify to address the issue, is there a way to block this Job? I am digging into MyAndroidTools, but I can't find anything like that in Messenger services or Activities.
EDIT: According to BetterBatteryStats, it's a Service, but I can't find it.
EDIT2: By changing display mode in MyAdroidTools, I was able to find the service, the normal display name is Lollipop Service. However, if disabled, the app does not work properly, closes as soon it's opened.
same here guys!nexus 5 with cm13. huge wakelock with facebook and messenger. I tryed to greenify it but it doesn't work and after few minutes they come back again. I have to hybernate them with SDMaid app and it works well, but of course once hybernate i can't use them anymore until i dishybernate. Any solution?i don't use xposed..:crying:
Confirm this wakelock on 1+1 with CM 13.
Hi,
Is anyone having sensor battery drain issue with WhatsApp?
This during my sleep where the sensor is on 100%.
Not sure how to turn it off.
I excluded WhatsApp in the whitelist for battery monitor.
Wondering if anyone have similar issue.
Yes. I posted this to another thread and got no responses. I wound up uninstalling. There is no reason for this. Their support was useless
Kill the whatsup? Do you really need to get updates while sleeping? Are there any settings, how often program updates? Any program that misbehaves like this gets deleted from my phone: either it's broken/not working properly or it's the way it works, not sure which is worse.
I have this drain, too. BBS says Sensor: invensense Accelerometer(1), wakeup=false, Time: xxh xxm. In another thread someone suggests that this drain is related to the usage of whatsapp web. I use wa web a lot, but the drain continues even if I don't use it and even when I kill and restart whatsapp. Why does wa need the Acceleromter?
edit:
With the latest WA version (2.17.190) the high battery drain doesn't occur anymore. It seems the problem is solved.
blue-spiderfire said:
I have this drain, too. BBS says Sensor: invensense Accelerometer(1), wakeup=false, Time: xxh xxm. In another thread someone suggests that this drain is related to the usage of whatsapp web. I use wa web a lot, but the drain continues even if I don't use it and even when I kill and restart whatsapp. Why does wa need the Acceleromter?
edit:
With the latest WA version (2.17.190) the high battery drain doesn't occur anymore. It seems the problem is solved.
Click to expand...
Click to collapse
Isn't the case for me. I have OnePlus 3T, with the WA version you mentioned above, and I still have this issue.
Bump. Anyone get anything useful from their support?
No help from Whatsapp support. Uninstalled and reinstalled, same issue. Reset the phone, the issue still persists. I need Whatsapp for my daily work so can't afford to remove it. I hope GSAM/BBS are reporting it correctly. Will have to wait for another update and keeping fingers crossed they solve this bug.
Anything off this? The problem still persist, the app uses the acelerometer like crazy in my moto x style.
I stop caring and just use the phone as it is.
Still getting 6 hrs of sot.
Some apps are using the sensor and I bet if we disable them the battery life will improve.
I dont see the drain anymore. Did you update Whatsapp?
I'm getting the drain atm... phone was at 88% last night.. got up this am and it was 55% and WhatsApp was using 23% above everything else..
I have the same issue...is there anyway to deny permission to whatsapp for sensor usage?
Anyone managed to solve this one? It's really annoying. Thinking about it, the only (reasonable) reason for Whatsapp to use acceletometer would be the camera, right? Since I never use Whatsapp's camera I just disabled the camera service for whatsapp and blocked Whatsapp from using phone's camera in the Privacy Guard settings, will see if that changes anything - so far this seems to be working.
I have the same problem
Still having the same problem...
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
Still having the same problem
Put whatsapp to sleep, go to Apps->Special access--> Optimize Battery usage and enable Whatsapp here. Then go to device maintenance, remove it from 'unmonitored apps' if present and add to 'always sleeping' apps. Try this for a day and check BBS for wakelocks. Also you might want to check partial wakelocks when 'screen off' and not 'since charged'. You may miss messages for a day or two but its worth the effort
linom said:
Put whatsapp to sleep, go to Apps->Special access--> Optimize Battery usage and enable Whatsapp here. Then go to device maintenance, remove it from 'unmonitored apps' if present and add to 'always sleeping' apps. Try this for a day and check BBS for wakelocks. Also you might want to check partial wakelocks when 'screen off' and not 'since charged'. You may miss messages for a day or two but its worth the effort
Click to expand...
Click to collapse
But this is happening me on a Oneplus 3T... I dont have that option
airiartev said:
But this is happening me on a Oneplus 3T... I dont have that option
Click to expand...
Click to collapse
Then why dont you post on that forum? You may not get answers here.
What did you use to make it all black?
The same problem.
It's look like WA collect my activity data.
Any way to (may be utility) to deny WA use acceleration sensor?