I know that the battery life issue after 5.1 has been addressed in these forums, but I want to make a specific thread about this problem in particular that many other are experiencing too and it doesn't seem to be addressed in here, at least not recently (There's a thread from 2012 that doesn't give much info).
So the thing is that ever since updating to 5.1, my battery doesn't last nearly as long as it used to. I'm using a couple of apps to try to diagnose the problem and I've found a this particular wakelock: bam_dmux_wakelock is what's keeping my phone awake. I also noticed that Google Play Services is what's using more energy than it used to. This wakelock is only present when using mobile data, although when using wifi the wlan wakelock family is also present, but those wakelock are not as long as the bam_dmux_wakelock, but they do keep the phone awake for a considerable amount of time.
Booting in safe mode does not help. Restricting mobile data access to Google Play Store and Google Play Services makes no difference either. I did some Googling and learned that I can disable some Google Services that were always running: BackupTransportService (I have backup disabled), WearableService (No idea why this was running since I've never even turned on bluetooth since I updated to 5.1, let alone pair my device with any wearable device), AnalyticsService and DeviceConnectionServiceBroker.
No dice. Wakelock is still keeping the phone awake.
There' still 5 other services that I'm not sure I should disable: GMSCoreStatsService (No idea what this does), GoogleLocationService and GoogleLocationManagerService (I don't why these are running since location has been disabled for weeks), PendingIntentCallbackService (No idea what this does), ConfigFetchService (No idea) an GCM Service (I think this is important, it has to do with push notification).
If you have more info on these services, please let me know. I don't want to mess with anything I don't know. I've stopped the location services but they come right back up. No idea why.
So, summing up, this is what I know:
- The bam_dmux_wakelock is responsabile for keeping my phone awake
- It only appears when in mobile data (not in WIFI)
- Google Play Services is what's using more energy than before
- Disabling sync does not help
- I've made two factory resets (from settings and from recovery), nothing.
- Restricting mobile data access to Google Play Store and GP Services makes no difference
- Disabling running services doesn't help either.
Is anybody else experiencing this and did you find a solution? I'm getting real sick of this, and I'm considering flashing a custom ROM for the first time in my life.
Related
After installing the latest edition of Google Maps, I noticed that it was using between 13-18% of my battery (after approx. 9 hours off the charger). I never opened Maps or Navigation, and when looking at its battery use, it's "stay awake" time was 0s.
I do have Google location services enabled, but as I said, I never used the Maps app or any other application that would require the use of standalone GPS services. And I always keep standalone (and VZW) location services off unless navigating. This was never a problem on older versions of Google Maps - is anyone else having this problem?
I also noticed my battery life was incrementally worse with this happening, which makes sense seeing as Google Maps ranks third behind Cell Standby and Screen on my battery usage log.
Any information or advice would be much appreciated!
minnysota said:
After installing the latest edition of Google Maps, I noticed that it was using between 13-18% of my battery (after approx. 9 hours off the charger). I never opened Maps or Navigation, and when looking at its battery use, it's "stay awake" time was 0s.
I do have Google location services enabled, but as I said, I never used the Maps app or any other application that would require the use of standalone GPS services. And I always keep standalone (and VZW) location services off unless navigating. This was never a problem on older versions of Google Maps - is anyone else having this problem?
I also noticed my battery life was incrementally worse with this happening, which makes sense seeing as Google Maps ranks third behind Cell Standby and Screen on my battery usage log.
Any information or advice would be much appreciated!
Click to expand...
Click to collapse
All apps that use Location Services at all will show up as "Maps" in battery stats, so it can be really tricky to figure out which app is actually causing the problem. It's most likely an updated third-party app that has location permissions. Have you updated any other apps recently?
Recently, this happened to me with 1Weather - their update had some bug that caused the LocationServices service to run continuously, which led to Maps taking up the majority of my battery without using it. Uninstalled, and that fixed the problem.
scorchedsky said:
All apps that use Location Services at all will show up as "Maps" in battery stats, so it can be really tricky to figure out which app is actually causing the problem. It's most likely an updated third-party app that has location permissions. Have you updated any other apps recently?
Recently, this happened to me with 1Weather - their update had some bug that caused the LocationServices service to run continuously, which led to Maps taking up the majority of my battery without using it. Uninstalled, and that fixed the problem.
Click to expand...
Click to collapse
That's interesting. The only apps I have that could have had location settings turned on were Facebook (chat), Flixster and Chrome. I turned off the location in Facebook chat, and the Flixster app says it uses network location only, so that shouldn't be an issue, right?
Also, I left location on for Chrome seeing as that would be the main benefit to keeping Google location services on.
I'll report back, hopefully the culprit was Facebook chat.
As a side not, uninstalling the Google Maps updates seems to have solved the problem, but I'd rather have the most up-to-date version of Maps.
If anyone else has any thoughts, I would really appreciate hearing them!
I froze maps and Google now and went from almost constant awake times overnight to nothing. Was losing 20% overnight sometimes. I don't use Google now and un freeze maps when I need navigation.
Sent from my SCH-I535 using Tapatalk 2
scorchedsky said:
All apps that use Location Services at all will show up as "Maps" in battery stats, so it can be really tricky to figure out which app is actually causing the problem. It's most likely an updated third-party app that has location permissions. Have you updated any other apps recently?
Recently, this happened to me with 1Weather - their update had some bug that caused the LocationServices service to run continuously, which led to Maps taking up the majority of my battery without using it. Uninstalled, and that fixed the problem.
Click to expand...
Click to collapse
Thanks for the info on this, I've been wondering what's up with the maps battery usage.
I was searching around for solutions to help me with my massive battery drain in CM10 A4 for these 2 days and I realised little emphasis had been put on "wakelocks" in our i9003 forums; so I thought some discussion here would be nice to help all of us, especially relatively new people like me.
A detailed explanation can be found in ahalford's thread; and also in the XDA wiki. Below is just what I managed to sort out for our device, specifically CM10 A4 (not sure about applicability in other ROMs).
Wakelocks are identifiable via BetterBatteryStats and I would like to mention a few of them that I could identify (and if possible, solve). My purpose here is just to share some info that I managed to find and if possible provide some guide based on my own experience.
In CM10 A4, I uninstalled:
Google Search
Google Maps
News & weather
Google Backup Transport
CM Wallpapers
Android Live Wallpapers and its associated LWPs
Spare Parts
GTalk
Movie Studio
Certificate Installer
Wakelocks identified:
1. RILJ
Easiest way to solve: Flash the fixed kernel by loSconosciuto. Personally tested it on CM10A4, and SlimBean v3.1; both worked. Just screen off/on and the signals will return.
Alternatively, put the phone to Airplane Mode (I left my WiFi on), reboot. Then leave it to screen off for some minutes, and turn off the Airplane Mode. The signal bars may not return as of yet; so just DC and reconnect the WiFi. Signal bars return, RILJ stopped. :victory:
2. GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice UNSOLVED
Attempts: Removed GTalk (but problem persisted); Auto-Sync off; and disabled location settings.
Also worth to mention it occurred only when WiFi was on; didn't test it on mobile data (I don't have one).
Attempts of freezing apps: (Still investigating)
Search Application Provider
Network Location
com.android.backupconfirm
Google xxxx Sync (Contacts, Calendar, etc)
* Others recommended to sign out from Google account, and re-add (but I have no experience on this).
* Also somebody was talking about disabling GTalk-related services in Google Framework Services using Autorun Manager (or similar); but it didn't work for me.
3. AudioOut_2
Perhaps not a wakelock. If the time matches time of you opening any games/app that produce sound; it should be normal and should stop after exiting application.
* Saw a thread that this may happen if the app did not exit properly (e.g. here)
Any input/discussion would be greatly appreciated.
Will update more whenever I have time! Thanks!
cheeyeen said:
2. GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice[/B]
Solution: Removed GTalk (but problem persisted). Stopped it by freezing a few apps via TitaniumBackup but the exact way to do it is still unknown, currently trying to rule out the below one by one.
Click to expand...
Click to collapse
I think for 2nd wakeclocks you have to turnoff Auto-sync from setting.Double check your setting.Though there is not perticular button to turnoff Autosync in CM10 you have to use widgets to turnoff autosync.
And go to Play store settings disable all tick.That may be solve second one.
nicsptl said:
I think for 2nd wakeclocks you have to turnoff Auto-sync from setting.Double check your setting.Though there is not perticular button to turnoff Autosync in CM10 you have to use widgets to turnoff autosync.
And go to Play store settings disable all tick.That may be solve second one.
Click to expand...
Click to collapse
Thanks. Actually it was solved, but I forgot to mention that. I just didn't know how it went solving lol :laugh: And yeah, Auto Sync off via power buttons in notification drawer and verified from the account settings.
Hi, recently I have observed almost 3GB of Google Play Services usage.
I am reading in many threads that this issue is caused by OTA updates constantly downloading. The only solution reported is to download some application to disable it. However, apparently this causes a wake lock? Also, this is reported in version 4.3. I am on Cataclysm ROM on 4.4, so not sure if the solution would be applicable in this case.
Any help is appreciated.
Thx!
If you're running a custom ROM, it wouldn't be OTA downloading. If you have high accuracy on for your location settings, something might be trying to access GPS and syncing data.
Sent from my Nexus 7 using xda app-developers app
I had enormous data usage with google play store and android services while i was stock, i tried to find the culprit but i couldn't so im at a custom rom until we get an update. I don't have a problem on my custom rom right now (liquidsmooth) they still don't pull back tho, always at the top of my data usage list, google needs to look into that.
So for Google Play Services I have made it only to download in the background, so connected to WIFI.
I believe that this has disabled Push notifications, as Facebook Messenger no longer alerts me to a message.
Any other input would be greatly appreciated.
Thx!
I've looked around a bunch and it seems like a lot of people are having a problem with terrible battery drain after the last two android updates. I'm on Verizon, unrooted, stock GS3. Ever since the update to 4.4 I've been hit with Google Services or Google Play Services running non-stop. My phone battery will discharge from 100% to critical in less the 4 hours without any use. The usual tricks of killing the process, restarting the phone and factory resetting have not worked. This has gotten ridiculous. Has anyone come up with any way to fix the sticking processes? Any kind of update at all? I'm extremely frustrated. I've had this phone for 2 years with no battery drain problems. Then I took the first 4.4 update and I started getting problems. Now with the newest update its much worse. Nothing will stop Google Services from running constantly. I can't wait to get an upgrade at this point.
bbuck002 said:
I've looked around a bunch and it seems like a lot of people are having a problem with terrible battery drain after the last two android updates. I'm on Verizon, unrooted, stock GS3. Ever since the update to 4.4 I've been hit with Google Services or Google Play Services running non-stop. My phone battery will discharge from 100% to critical in less the 4 hours without any use. The usual tricks of killing the process, restarting the phone and factory resetting have not worked. This has gotten ridiculous. Has anyone come up with any way to fix the sticking processes? Any kind of update at all? I'm extremely frustrated. I've had this phone for 2 years with no battery drain problems. Then I took the first 4.4 update and I started getting problems. Now with the newest update its much worse. Nothing will stop Google Services from running constantly. I can't wait to get an upgrade at this point.
Click to expand...
Click to collapse
From what I've read on not just here, but for other phones...the usual culprit is location services via google now. The best way to test this is to turn off google now (which will just give you the standard pre jb google search) and see if that calms things down. If you want google now...try turning off location reporting in google''s location settings. Additionally, turn off syncing to things under the google account that you don't necessary need to sync constantly.
dvschnk said:
From what I've read on not just here, but for other phones...the usual culprit is location services via google now. The best way to test this is to turn off google now (which will just give you the standard pre jb google search) and see if that calms things down. If you want google now...try turning off location reporting in google''s location settings. Additionally, turn off syncing to things under the google account that you don't necessary need to sync constantly.
Click to expand...
Click to collapse
I kept reading more forum posts yesterday, and I am fairly confident that I found the correct answer for my phone. I've never had a problem before with the location services draining my battery. The culprit is the "OK Google" voice detection constantly listening. Ever since I turned that off, my battery usage has returned to normal. Immediately I noticed a difference in the phone's performance and the battery percentage didn't drain while I was watching it. This makes sense too with the timing of the update and my battery drain. KitKat brought this feature to the GS3 and that is precisely when my battery started to be sucked dry. Whereas before, Google services was listed as 40-60% of my battery usage, it's now down to 15%. The good thing with turning this off is I never used the feature, unlike location services that are baked into everything and actually useful to me. Thanks for the help.
Ever since the 5.1 OTA (Or Google Services 7.0.99, I'm not sure), I've been experiencing bad battery life.
I downloaded Better Battery Stats and Wakelock Detector to try to find the culprit and this is what I've found.
- Connected to my wifi at home my Nexus 5 sleeps just fine.
- At work (wifi) I'm having a lot of wlan_rx and wlan_wd wakelocks and high awaken times due to this.
- When on mobile data it all gets worse: I'm getting hundreds of instances of RILJ wakelock in a matter of minutes, and sometimes Gmail often appears first on the list with high wakelock counts and times. Google+ and Keep also make frequent appearances I'm Wakelock Detector
- BBS ALWAYS shows bam_dmux_wakelock as the main culprit and sometimes sensor_ind (on mobile data), but I don't know what to make of that, since WD shows other things (RILJ etc).
Regarding RILJ: almost everything I've found online says that it has something to do with network location and that turning off location history removes it, but I rarely have location services on (GPS or network location) and location history is off anyway. I've tried disabled NetworkLocationService and every other service regarding location using disable service to no avail. It doesn't seem to happen when the phone is in 2G only.
Gmail frequently shows up in WD with high counts and times, I've seen Keep and Google+ in there too, first on lists. I've disabled them both for now.
In the battery stats the activity bars doesn't seem to be all that different from the screen on bars, but both WD and BBS show high awake times (sometimes as high as +20%). This is when on mobile data or connected to the wifi at work (wifi at home is just fine).
I tried downgrading to 5.0.1 (there now), installing Google Services 7.3.29, disabling a bunch of services, but nothing helps.
Google Services shows up as using more energy than anything else, sometimes even more than the screen, but only when mobile data is enable, it doesn't use energy when on wifi. There's no high data traffic as some people is experiencing with 7.X versions. The wlan wakelocks are awful at work though. So there are like several, independent problems.
I'd appreciate any insight on this matter. I don't seem to be the only one experiencing this.
I'm leaving a few screen shots. I'll post BBS screenshot by the end of the day.
Did you solve this? Nobody seems to know what really is RILJ.. If I restrict it to "7200" (2 hours) at Amplify it's safe to receive calls/sms ???
Luckzzz said:
Did you solve this? Nobody seems to know what really is RILJ.. If I restrict it to "7200" (2 hours) at Amplify it's safe to receive calls/sms ???
Click to expand...
Click to collapse
Easy way to find out is to test it. Restrict and then phone/text yourself from another phone. Test periodically until you're comfortable with the results.
I've having troubles with this from some months ago now. It dissapeared at some time, but it's back again.
Anyway, in my case, the problem happen when i'm connected to a WIFI network, with mobile data activated. If I deactivate it, everything is just fine. Don't really know what is causing this, but at least I discovered my problem.
Hope this help someone else.
Cheers