Database Info

[Q] G-Maps excessive wakelocks?

Hoping a BBS (Better Battery Stats) expert can advise… I’ve noticed that last couple of weeks that under BBS Alarms, that “com.google.android.apps.maps” is generating about 70-80 wakeups per hour for the first few hours after removing device from charger… then stabilizers to about 40-50 wakeups per hour thereafter (see attached screen-shot). Phone is going into Deep Sleep… and under “Partial Wakelocks” it seems to tie to “SignalCollector.ScannerThread” process (after 11 hrs since full charge it shows 12min 55s of wakelock time). So averaging just over 1min per hour of wakelock. But as stated, after 11 hrs since full charge, I’m up to around 600 alarm wakeups.
What I’ve tried: (1) clearing Maps data and cache; (2) uninstalling Maps and reinstalling
Under “Settings… Location Services”, I have “Google Location Service” and “GPS satellites” checked… and “Location and Google Search” has always been unchecked
GPS works fantastic, just wondering if ROM is making too many calls to G-Maps? Anything else I can try to reduce the number of Alarm wakeups? Running SkyICS 4.2F6 Update 2.4B. Honestly, couldn’t be happier with this ROM and it’s performance… best I’ve run on my i727. Just would like to understand what’s happening with G-maps and these wakelocks? Thx.

I've been monitoring wakelocks for a while now with SKYICS and I had a similar issue with gallery. I eventually froze it with TiBu and am using quickpic instead. Maps shouldn't be causing wakelocks and definitely not 40-50 an hour. Try starting again with 2.4A after formatting etc etc.

sandman97289 said:
I've been monitoring wakelocks for a while now with SKYICS and I had a similar issue with gallery. I eventually froze it with TiBu and am using quickpic instead. Maps shouldn't be causing wakelocks and definitely not 40-50 an hour. Try starting again with 2.4A after formatting etc etc.
Click to expand...
Click to collapse
Thanks for the reply... I think this would be my last resort. By reflashing 2.4A, it will rewrite my systemUI and framework-res files... I've added custom PNGs to both, so I'd have to redo all of these plus all the add-on zips (although I may have to!). Any other suggestions regarding the maps wakelocks? (BTW, tracked again today when I took phone off charger... got 65 wakeups in first 51 minutes (com.google.android.apps.maps)... and Partial Wakelocks on BBS shows the process culprit as "SignalCollector.ScannerThread" (2m 1s for these).

DoctorQMM said:
Hoping a BBS (Better Battery Stats) expert can advise… I’ve noticed that last couple of weeks that under BBS Alarms, that “com.google.android.apps.maps” is generating about 70-80 wakeups per hour for the first few hours after removing device from charger… then stabilizers to about 40-50 wakeups per hour thereafter (see attached screen-shot). Phone is going into Deep Sleep… and under “Partial Wakelocks” it seems to tie to “SignalCollector.ScannerThread” process (after 11 hrs since full charge it shows 12min 55s of wakelock time). So averaging just over 1min per hour of wakelock. But as stated, after 11 hrs since full charge, I’m up to around 600 alarm wakeups.
What I’ve tried: (1) clearing Maps data and cache; (2) uninstalling Maps and reinstalling
Under “Settings… Location Services”, I have “Google Location Service” and “GPS satellites” checked… and “Location and Google Search” has always been unchecked
GPS works fantastic, just wondering if ROM is making too many calls to G-Maps? Anything else I can try to reduce the number of Alarm wakeups? Running SkyICS 4.2F6 Update 2.4B. Honestly, couldn’t be happier with this ROM and it’s performance… best I’ve run on my i727. Just would like to understand what’s happening with G-maps and these wakelocks? Thx.
Click to expand...
Click to collapse
I would clear maps cache and turn off google location service and try that

My approach to the problem:
1. Install MapQuest, OSMAnd and Waze
2. Clear Google Maps cache and data
3. Uninstall Google Maps
4. Problem solved

Bruno2123 said:
I would clear maps cache and turn off google location service and try that
Click to expand...
Click to collapse
Thanks for reply... I already tried clearing map data and cache... wakelock issue returned. But did not turn off "Google Location Service".. so will try that next. My concern of course is by turning off Google Location Service, will that degrade the accuracy/performance of G-Maps when I need it?
If this doesn't work, I'll try T.J. Bender's recommendation (thanks for that). No one else is experiencing these high BBS wakeups with G-Maps? Started when I flashed 2.2B or 2.3B, can't recall which.

DoctorQMM said:
Thanks for reply... I already tried clearing map data and cache... wakelock issue returned. But did not turn off "Google Location Service".. so will try that next. My concern of course is by turning off Google Location Service, will that degrade the accuracy/performance of G-Maps when I need it?
If this doesn't work, I'll try T.J. Bender's recommendation (thanks for that). No one else is experiencing these high BBS wakeups with G-Maps? Started when I flashed 2.2B or 2.3B, can't recall which.
Click to expand...
Click to collapse
You can keep clearing it till it stops doing it after you close maps i know it seems kinda pointless but it will work. With the gps fixes on skyics it helps connect you to multiple satellites so you dont need google location service even with it clicked off and the right fix you can get gps locked on in seconds with accuracy under 5 meters you just have to have to find the right fix for you if it doesnt already do that.

[Q] wlan_rx_wake keeps device awake!

Dear all,
I have been noticing the last few days (since I did a wipe + factory reset) that my TF700 (running latest JB) is draining ~3% of battery/h when completely idle (almost as much as my phone, which is on 3G and wifi!) when connected to Wifi. After installing Better Battery Stats, I see they report 90% of kernel wake lock time due to "wlan_rx_wake", which is not normal.This is (I think) consistent with the fact that I always see the arrows of "download" and "upload" blinking on top of the wifi icon...
I've googled around and it looks like a problem with dynamic IP and Ipv6, but I am worried that an app is actually doing this, because when I first got the tablet (a couple of weeks ago) this was not happening. However, I was getting 2 random reboots per day and I suspected that disabling the ASUS apps was causing it, so I did a complete wipe and I flashed the firmware. I think this problem started since then, but I cannot be 100% sure.
I've tried to check if there is any application that is actually using up the network, but the data usage seems reasonable (just a few KB for the system)...
Is anybody else experiencing this? Any proposed hints/solutions/workarounds?
Thanks!

DjKarras said:
Dear all,
I have been noticing the last few days (since I did a wipe + factory reset) that my TF700 (running latest JB) is draining ~3% of battery/h when completely idle (almost as much as my phone, which is on 3G and wifi!) when connected to Wifi. After installing Better Battery Stats, I see they report 90% of kernel wake lock time due to "wlan_rx_wake", which is not normal.This is (I think) consistent with the fact that I always see the arrows of "download" and "upload" blinking on top of the wifi icon...
I've googled around and it looks like a problem with dynamic IP and Ipv6, but I am worried that an app is actually doing this, because when I first got the tablet (a couple of weeks ago) this was not happening. However, I was getting 2 random reboots per day and I suspected that disabling the ASUS apps was causing it, so I did a complete wipe and I flashed the firmware. I think this problem started since then, but I cannot be 100% sure.
I've tried to check if there is any application that is actually using up the network, but the data usage seems reasonable (just a few KB for the system)...
Is anybody else experiencing this? Any proposed hints/solutions/workarounds?
Thanks!
Click to expand...
Click to collapse
You might try to disable some of the the ASUS bloatware, maybe one by one, to see if it isn't one of them causing the wakelock.

okantomi said:
You might try to disable some of the the ASUS bloatware, maybe one by one, to see if it isn't one of them causing the wakelock.
Click to expand...
Click to collapse
Thanks! OK, I'll try this... Maybe I just root and remove the bloatware...

DjKarras said:
Thanks! OK, I'll try this... Maybe I just root and remove the bloatware...
Click to expand...
Click to collapse
So, one update: at home, where I have a wifi with WPA2-PSK, the wlan_rx_wake goes down to 1% (as per BBS), so now the tablet is at a little less than 1%/hour, which is something more reasonable.
At work, where we have an enterprise network with TTLS authentication and so on, the wlan_rx_wake is around 70-80%. It then looks to be related to this, maybe: http://code.google.com/p/android/issues/detail?id=29804
I'll try to post a logcat tomorrow, will it be useful?

Yes, thanks for the update, and for looking into this. I hope there will be a fix now that the issue has been identified.

okantomi said:
Yes, thanks for the update, and for looking into this. I hope there will be a fix now that the issue has been identified.
Click to expand...
Click to collapse
So I'm JB and my tablet is still not rooted. That means no logcat access I'll need to wait until the weekend, I will root the tablet and then on Monday I do a test at work. BTW, I confirm that with the work network I get ~3% batt/hour with 90% wlan_rx_wake...

DjKarras said:
So I'm JB and my tablet is still not rooted. That means no logcat access I'll need to wait until the weekend, I will root the tablet and then on Monday I do a test at work. BTW, I confirm that with the work network I get ~3% batt/hour with 90% wlan_rx_wake...
Click to expand...
Click to collapse
So I did further tests, and I see that the AlarmManager is scheduling a lot of wake ups, for example
Code:
12-07 11:52:18.444 D/AlarmManager( 412): Triggered Alarm 414a0c90 ELAPSED_REALTIME_WAKEUP IntentSender{419d1c18: PendingIntentRecord{41a69780 android broadcastIntent}}
12-07 11:52:19.174 D/AlarmManager( 412): Added alarm Alarm{41b34b20 type 2 android} type:ELAPSED_REALTIME_WAKEUP when: After 0h:14m:24.0s
12-07 11:52:19.214 D/WifiNative-p2p0( 412): SetWifiConnected false
12-07 11:52:19.214 I/WifiStateBroadcastReceiver(11952): connecting or connected to Wifi
12-07 11:52:19.224 D/WifiNative-p2p0( 412): SetWifiConnected true
12-07 11:52:19.224 D/ConnectivityService( 412): ConnectivityChange for WIFI: CONNECTED/CONNECTED
I see a lot of these SetWifiConnected false... I attach the full log for a couple of hours. Anything suspicious?
Thanks!

DjKarras said:
So I did further tests, and I see that the AlarmManager is scheduling a lot of wake ups, for example
Code:
12-07 11:52:18.444 D/AlarmManager( 412): Triggered Alarm 414a0c90 ELAPSED_REALTIME_WAKEUP IntentSender{419d1c18: PendingIntentRecord{41a69780 android broadcastIntent}}
12-07 11:52:19.174 D/AlarmManager( 412): Added alarm Alarm{41b34b20 type 2 android} type:ELAPSED_REALTIME_WAKEUP when: After 0h:14m:24.0s
12-07 11:52:19.214 D/WifiNative-p2p0( 412): SetWifiConnected false
12-07 11:52:19.214 I/WifiStateBroadcastReceiver(11952): connecting or connected to Wifi
12-07 11:52:19.224 D/WifiNative-p2p0( 412): SetWifiConnected true
12-07 11:52:19.224 D/ConnectivityService( 412): ConnectivityChange for WIFI: CONNECTED/CONNECTED
I see a lot of these SetWifiConnected false... I attach the full log for a couple of hours. Anything suspicious?
Thanks!
Click to expand...
Click to collapse
Hi,
a further update on the matter. I used Shark to capture traffic incoming to the tablet, and I see that mainly there are som DHCPv6Client SOLICIT requests. It looks like IPv6 is not being treated well by the tablet (or maybe it's the routers?). I attach the pcap file from Shark, and I would like to ask for your advice on how to go further towards solving the problem. Is there somebody in the forum that can help with this problem? Can I disable IPv6 (I have not been able to find where)? Is there any further debugging I can do?
Many thanks,
Albert

I have the same problem. Google maps causes it for me. I run on clemsyn and cleanrom and stock before. I did factory reset, full wipe, new google accounts etc. Nothing helps.
The tablet consumes the dock and tablet battery in about 2 days of very very mild usage.
I have to know how to stop it.
I even applied all the battery save options and disable the automatic sync. The problem was before and with the new rom, but only appeared last week.

usern ameisval idandnot said:
I have the same problem. Google maps causes it for me.
I have to know how to stop it.
Click to expand...
Click to collapse
Easy. Just disable Google Maps. I did, when it kept reappearing in my running apps list on its own.

But I need it so much

usern ameisval idandnot said:
But I need it so much
Click to expand...
Click to collapse
I find Gmaps pretty useless, as you need a constant Inet connection . Pretty much only use Navfree these days. If I need satimagery, I use Google Earth or the Maps website. And paper maps
Try checking if 'Google Location Service" is enabled under settings --> Location Services. I can't check the maps app (obviously ) but there might also be a similar setting there. (There was a bug with it, that much I do remember. One where it remained on and kept eating battery, even with Maps not running. May very well be the same thing.)

I will test if that helps. Until then I will drop some bread on the streets to find my way back.

@ ShadowLea
It worked. Google maps still uses 80% of all apps but it just used 3% of the battery in 24h.
Thanks

However, I don't thing this has anything to be with the original post, hasn't it? It looks like a different issue...

DjKarras said:
However, I don't thing this has anything to be with the original post, hasn't it? It looks like a different issue...
Click to expand...
Click to collapse
Don't know. Have you checked it? From the name of the process i'd say something is keeping the wifi awake, and that's exactly what location service does.
Might also be the 'keep WiFi during sleep" setting.

It doesn't say so it battery usage (it's just keep awake, no app is waking the tablet up) and Battery Plus tells me it's a Kernel Wakelock. In addition, this only happens on certain wireless network. I think some packets on the network are keeping the tablet to sleep for a long time, and there are similar reports around.
I think I have been able to isolate the issue quite well with the Shark sniffer, but I just don't know how to follow further

[Q] Battery life worse at home

Just got my N5 last week and I'm having some battery issues.
Battery life seems to be just fine when I'm at work (after 8 hours, it's only down to 85% or so, with minimal use). However, when I'm at home, the battery drops off rapidly. It was down to 25% after just 6 hours, also with just minimal use.
What gives? I haven't changed any settings. It looks like my signal is weaker at the office (2 bars) vs. home (5 bars). At both locations I leave WiFi on and can connect to the local network.
I checked battery settings now (at home) and Google Play Services is using 30%. Not sure what it was at when I was at work.
Any ideas?

jarros said:
Just got my N5 last week and I'm having some battery issues.
Battery life seems to be just fine when I'm at work (after 8 hours, it's only down to 85% or so, with minimal use). However, when I'm at home, the battery drops off rapidly. It was down to 25% after just 6 hours, also with just minimal use.
What gives? I haven't changed any settings. It looks like my signal is weaker at the office (2 bars) vs. home (5 bars). At both locations I leave WiFi on and can connect to the local network.
I checked battery settings now (at home) and Google Play Services is using 30%. Not sure what it was at when I was at work.
Any ideas?
Click to expand...
Click to collapse
I don't know this for a fact, but I was having a similar thing happen to me. I disabled Google Now (for testing purposes) and my "Google Play Services" on the battery list had lowered. The Google Play Services was not what was using most of my battery but it went down significantly. Do you have that enabled? If so, maybe try disabling that feature and testing it to see if it helps. Having that enabled will pull your location constantly and something small like there being more businesses or things to visit around your home it may try and pull info more than when you're at work.
Also, surely you had the right of mind to make sure GPS itself is disabled in your OS? Are either of the routers you use, at work or home, dual band as opposed to single? Have you tried restarting your phone when you get to work initially to make sure it connects to a closer cellular tower?

FourPointedFreak said:
I don't know this for a fact, but I was having a similar thing happen to me. I disabled Google Now (for testing purposes) and my "Google Play Services" on the battery list had lowered. The Google Play Services was not what was using most of my battery but it went down significantly. Do you have that enabled? If so, maybe try disabling that feature and testing it to see if it helps. Having that enabled will pull your location constantly and something small like there being more businesses or things to visit around your home it may try and pull info more than when you're at work.
Also, surely you had the right of mind to make sure GPS itself is disabled in your OS? Are either of the routers you use, at work or home, dual band as opposed to single? Have you tried restarting your phone when you get to work initially to make sure it connects to a closer cellular tower?
Click to expand...
Click to collapse
Thanks for the quick response. I had Google Now running, so I'll try disabling it and see if it helps with the battery. Google Play Services is still running at 30% under battery settings (and Android OS at 18%, Screen 17% - same as before).
Maybe it is something to do with the router? I'm pretty sure my home wifi router is single band (Linksys WRT160N). Would single band greatly decrease the battery life? I have no idea what we use at work. Something Cisco, I'm pretty sure, but don't know how old it is.

jarros said:
Thanks for the quick response. I had Google Now running, so I'll try disabling it and see if it helps with the battery. Google Play Services is still running at 30% under battery settings (and Android OS at 18%, Screen 17% - same as before).
Maybe it is something to do with the router? I'm pretty sure my home wifi router is single band (Linksys WRT160N). Would single band greatly decrease the battery life? I have no idea what we use at work. Something Cisco, I'm pretty sure, but don't know how old it is.
Click to expand...
Click to collapse
Well the biggest thing is dual band provides a signal over a greater length than single band. So if something like Google Now is running and you're connected to a dual band router, it'll suck more power and info at greater distances. That's all I was referring to Plus with dual band routers you will get a better speed depending on your internet provider so typically people do more because their phone responds faster.
Try it for a few days without Google Now enabled and it should make a difference, at least a little.

The other thing to keep an eye on is your Mediaserver process. Some apps will keep it open, which keeps an ongoing wakelock. So even if your device is "sleeping" (you're not using it) it's actually awake and chewing up battery. I have a couple of games that I have noticed this with and am now in the habit of closing the app out instead of just switching apps.
Predictably mediaserver shouldn't be anymore than a few % through the day, but it's kind of random how much it affects the battery.

jarros said:
Just got my N5 last week and I'm having some battery issues.
Battery life seems to be just fine when I'm at work (after 8 hours, it's only down to 85% or so, with minimal use). However, when I'm at home, the battery drops off rapidly. It was down to 25% after just 6 hours, also with just minimal use.
What gives? I haven't changed any settings. It looks like my signal is weaker at the office (2 bars) vs. home (5 bars). At both locations I leave WiFi on and can connect to the local network.
I checked battery settings now (at home) and Google Play Services is using 30%. Not sure what it was at when I was at work.
Any ideas?
Click to expand...
Click to collapse
Everything is a shot in the dark without a BetterBatteryStats log. Head over to the app section and grab the beta.
It could be the router. You say you can connect to the wifi at work and at home, but do you?
Please attach a BBS log to your next reply. Give us at least 2-4 hours of data to interpret.

Aerowinder said:
Everything is a shot in the dark without a BetterBatteryStats log. Head over to the app section and grab the beta.
It could be the router. You say you can connect to the wifi at work and at home, but do you?
Please attach a BBS log to your next reply. Give us at least 2-4 hours of data to interpret.
Click to expand...
Click to collapse
Thanks for the help. I installed BetterBatteryStats and have attached the two log files. Hopefully you can read it, it looks a bit garbled when I open it with notepad.
It looks like the top kernels at home are:
bam_dmux_wakelock (): 1 h 42 m 37 s (6157 s) Cntc/wc/ec)1291/12/0 45.7%
wlan_rx_wake (): 1 h 10 m 9 s (4209 s) Cntc/wc/ec)3140/628/3139 31.3%
PowerManagerService.WakeLocks (): 1 h 6 m 10 s (3970 s) Cntc/wc/ec)12000/289/0 29.5%
wlan_ctrl_wake (): 45 m 20 s (2720 s) Cntc/wc/ec)2053/56/2053 20.2%
radio-interface (): 32 m 46 s (1966 s) Cntc/wc/ec)1972/7/0 14.6%
wlan_wd_wake (): 26 m 26 s (1586 s) Cntc/wc/ec)12433/230/0 11.8%
While at work they are:
PowerManagerService.WakeLocks (): 15 m 25 s (925 s) Cntc/wc/ec)665/59/0 6.5%
wlan_ctrl_wake (): 11 m 2 s (662 s) Cntc/wc/ec)189/88/190 4.6%
wlan_rx_wake (): 3 m 53 s (233 s) Cntc/wc/ec)204/30/203 1.6%
wlan_wd_wake (): 2 m 57 s (177 s) Cntc/wc/ec)2477/60/0 1.2%
Again, I don't change any of the settings on my phone when I go to work. I connect to and access the wifi network at both locations (both show the up/down arrows by the WiFi button in the menu).
Any thoughts on what this means? It's time to do some googling...

jarros said:
Thanks for the help. I installed BetterBatteryStats and have attached the two log files. Hopefully you can read it, it looks a bit garbled when I open it with notepad.
It looks like the top kernels at home are:
bam_dmux_wakelock (): 1 h 42 m 37 s (6157 s) Cntc/wc/ec)1291/12/0 45.7%
wlan_rx_wake (): 1 h 10 m 9 s (4209 s) Cntc/wc/ec)3140/628/3139 31.3%
PowerManagerService.WakeLocks (): 1 h 6 m 10 s (3970 s) Cntc/wc/ec)12000/289/0 29.5%
wlan_ctrl_wake (): 45 m 20 s (2720 s) Cntc/wc/ec)2053/56/2053 20.2%
radio-interface (): 32 m 46 s (1966 s) Cntc/wc/ec)1972/7/0 14.6%
wlan_wd_wake (): 26 m 26 s (1586 s) Cntc/wc/ec)12433/230/0 11.8%
While at work they are:
PowerManagerService.WakeLocks (): 15 m 25 s (925 s) Cntc/wc/ec)665/59/0 6.5%
wlan_ctrl_wake (): 11 m 2 s (662 s) Cntc/wc/ec)189/88/190 4.6%
wlan_rx_wake (): 3 m 53 s (233 s) Cntc/wc/ec)204/30/203 1.6%
wlan_wd_wake (): 2 m 57 s (177 s) Cntc/wc/ec)2477/60/0 1.2%
Again, I don't change any of the settings on my phone when I go to work. I connect to and access the wifi network at both locations (both show the up/down arrows by the WiFi button in the menu).
Any thoughts on what this means? It's time to do some googling...
Click to expand...
Click to collapse
There are no partial wakelocks. Make sure your BBS is the latest beta, and enable root access through advanced settings.

Aerowinder said:
There are no partial wakelocks. Make sure your BBS is the latest beta, and enable root access through advanced settings.
Click to expand...
Click to collapse
OK, enabled root access. Here's another log from the past 3hrs (minimal use, just a few sms and checked email once or twice).
Top wakelocks:
GCM_CONN_ALARM (Google Play services): 8 m (480 s) Count:687 26.8%
Checkin Service (Google Play services): 6 m 16 s (376 s) Count:2782 21.0%
ConnectivityService (0): 5 m 10 s (310 s) Count:348 17.3%
And alarms:
com.google.android.gms (): Wakeups: 189
Alarms: 69, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 90, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR
Alarms: 22, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION

jarros said:
OK, enabled root access. Here's another log from the past 3hrs (minimal use, just a few sms and checked email once or twice).
Top wakelocks:
GCM_CONN_ALARM (Google Play services): 8 m (480 s) Count:687 26.8%
Checkin Service (Google Play services): 6 m 16 s (376 s) Count:2782 21.0%
ConnectivityService (0): 5 m 10 s (310 s) Count:348 17.3%
And alarms:
com.google.android.gms (): Wakeups: 189
Alarms: 69, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 90, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR
Alarms: 22, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION
Click to expand...
Click to collapse
Set location services to device only. Then pull an overnight log (not using the device - use BBS custom ref point), and we will go from there

Aerowinder said:
Set location services to device only. Then pull an overnight log (not using the device - use BBS custom ref point), and we will go from there
Click to expand...
Click to collapse
OK, it appears to be MUCH better after setting location to "Device Only". 87% after 2hrs idle instead of 70% before. :good: Still not quite as good as when I'm at work (where both the wifi and cell signal are weaker). I've attached a log file from the past two hours.

Aerowinder said:
Set location services to device only. Then pull an overnight log (not using the device - use BBS custom ref point), and we will go from there
Click to expand...
Click to collapse
Hi Aerowinder, could u help have a look at my BBS log and see if there's something weird? Thx. Google play services seem to eat a lot of battery from my Nexus 5, especially when it's on wifi.

Phantom_11 said:
Hi Aerowinder, could u help have a look at my BBS log and see if there's something weird? Thx. Google play services seem to eat a lot of battery from my Nexus 5, especially when it's on wifi.
Click to expand...
Click to collapse
Same advice I gave to jarros.

Aerowinder said:
Same advice I gave to jarros.
Click to expand...
Click to collapse
Thx, buddy

Aerowinder said:
Set location services to device only. Then pull an overnight log (not using the device - use BBS custom ref point), and we will go from there
Click to expand...
Click to collapse
I thought I had this issue resolved, but since yesterday it has come back with a vengeance. (any way to check what system changes took place?)
I've attached a BBS log from the past 3 hours.
Here's what I've done so far:
Turned off system backup (which really helped cut down data usage and save battery)
Turned off Google Now
Location services are set to Device Only
Google play store: turned off auto-update apps AND Notifications
In the last 2 days data usage for Android OS went up from almost zero (and I had great battery life at the time) to 17.5mb (ALL BACKGROUND), and I have no idea why.
This morning I tried uninstalling Viber, and I turned off facebook notifications, but neither of those helped.
Any ideas?

jarros said:
I thought I had this issue resolved, but since yesterday it has come back with a vengeance. (any way to check what system changes took place?)
I've attached a BBS log from the past 3 hours.
Here's what I've done so far:
Turned off system backup (which really helped cut down data usage and save battery)
Turned off Google Now
Location services are set to Device Only
Google play store: turned off auto-update apps AND Notifications
In the last 2 days data usage for Android OS went up from almost zero (and I had great battery life at the time) to 17.5mb (ALL BACKGROUND), and I have no idea why.
This morning I tried uninstalling Viber, and I turned off facebook notifications, but neither of those helped.
Any ideas?
Click to expand...
Click to collapse
Does it persist through a reboot?

Aerowinder said:
Does it persist through a reboot?
Click to expand...
Click to collapse
Unfortunately yes... I'm getting really tired of this. What's the next step? Full factory reset and reinstall all my apps?

Go into your router settings and change your Beacon Interval to 150 (default 100), and DTM to 7 (from 1)
Reboot router, reboot phone.

Wakelock called bam_dmux_wakelock

Hello there, this is almost my first post around here (I hope the first one in the right place)
I had heavy battery draining a couple of days ago and they went away after wipe data and cache. Now I have reinstalled everything I had, I looking to solve an issue that also have before wipes related to battery draining. In BetterBatteryStats shows a wakelock called bam_dmux_wakelock that wakes my phone one time per two seconds. It only appears when phone is using mobile network for the internet (I mean, the way I could make a call and surf the internet only if I'm using wifi).
I've been writing a thread on reddit the last days about that.
The post it's on the MotoG subreddit and it's called "Any solution to idle battery draining?" (I would post the url, but I'm not still able)
Here is a copy of the (I think) more relevant part:
I found some things about the wakelock bam_dmux_wakelock that means nothing to me, but maybe somebody could tell me more about them.
I think is related to Qualcomm hardware, because if you browse to the MotoG kernel you'll found the next folder: kernel/arch/arm/mach-msm, and a fast look for around the web shows that is qualcomm related.
Inside that folder there is two files: bam_dmux.c and inside include folder bam_dmux.h Another file called bam_dmux.txt is in kernel/Documentation/devicetree/bindings/arm/msm, but it isn't in the online kernel repository: link
The content of that file is the following:
Qualcomm BAM Data Multiplexer Driver
Required properties: - compatible : should be "qcom,bam_dmux" - reg : the location and size of the BAM hardware - interrupts : the BAM hardware to apps processor interrupt line
Optional properties: -qcom,satellite-mode: the hardware needs to be configured in satellite mode -qcom,rx-ring-size: the size of the receive ring buffer pool, default is 32
Example:
qcom,[email protected] {
compatible = "qcom,bam_dmux";
reg = <0xfc834000 0x7000>;
interrupts = <0 29 1>;
qcom,satellite-mode;
qcom,rx-ring-size = <64>;
};
BAM seems to mean Bus Access Manager, and of course I don't have a clue about what that means.
In addition I look for files on my MotoG with the string bam_dmux in its name, and two folders came out: /d/bam_dmux and /d/ipc_loggin/bam_dmux In the first one there is three files: * stats * tbl * ul_pkt_cnt
In the second one there is only one file where it keeps the log_cont.
Click to expand...
Click to collapse
In the post in reddit theres links to the log and others contents.
Any idea how could I stop that? Thank you in advance.
P.d.: sorry for my english, maybe there is some glitch in the post

You probably have an app that is causing this. I would factory reset and install one app at a time until I found the one causing the problem. Then just uninstall that app.
For example I found the BBC weather app caused a wakelock which showed up in 'android OS'. Took a while for me to figure out which app caused it.
Does wakelock detector show any user apps with high wakeup triggers. If so you may find one of them is the cause.

Broadband Access Multiplexor.
There's another thread on XDA (going back a year or two) trying to diagnose causes for high incidence of this wakelock, which came to the conclusion it is caused by some other app trying to keep a mobile data server connection open. Your pattern of repeated every couple of seconds wakelock suggests something is trying to sync / ping a server and is failing to do so, but won't give up.
A look at what is showing up as using a lot of mobile date might help in diagnosing the problem app, and also checking what your sync settings are. Try disabling autosync for a while to see if it continues to show up.
Google+ auto backup of photos is something I would expect to cause a high incidence of this wakelock if you you the camera regularly.

Well, it looks like k9-mail and telegram were eating muy battery.
Thank you!

elfio said:
Well, it looks like k9-mail and telegram were eating muy battery.
Thank you!
Click to expand...
Click to collapse
Have been using K9 as well on my XT1032 but I did not have battery drain.
So I can not confirm that K9 will be causing this.
Or did you maybe have setup in your configuration that K9 had to check your mail every 5 minutes.

I had two accounts with IMAP push and refresh idle conection every 60 minutes, and another three with IMAP but without push and check every 6 hours or so.
Now I only have one of the two first ones and draining have decreased, but still there is a bit.
I'm using mainly WiFi (no wakelocks) since right now have a lot of work and I cannot spend enough time with this.

Mickeyvdb said:
Have been using K9 as well on my XT1032 but I did not have battery drain.
So I can not confirm that K9 will be causing this.
Or did you maybe have setup in your configuration that K9 had to check your mail every 5 minutes.
Click to expand...
Click to collapse
I've reconfigured all my accounts with IMAP, two of them with push and anotherone with sync every 24 hours . Now I'll check if still is making some wakelocks. Also I've switched the telegram client: from unofficial to the official one.
I hope it solves my issue with K9 because I really love that email client.
Let's see

Any idea why the wakelock only appears using mobile data and no wifi?

elfio said:
Any idea why the wakelock only appears using mobile data and no wifi?
Click to expand...
Click to collapse
No but I also have this annoying problem. And I don't have k9 or telegram installed.
@elfio: in your case wakelock is caused by k9 when using data right?
So the only way to find out is to uninstall one app at the time and re-install it and test? I have root is there any more sophisticated method to find out app in question?

frojnd said:
No but I also have this annoying problem. And I don't have k9 or telegram installed.
@elfio: in your case wakelock is caused by k9 when using data right?
So the only way to find out is to uninstall one app at the time and re-install it and test? I have root is there any more sophisticated method to find out app in question?
Click to expand...
Click to collapse
K9-mail is not the only app causing this wakelock, but after I disabled the push imap it the wakelock went down a lot. Now I have a power consume around 0.6~1%/hour with 2G on and screen off. I think this is a great consume, and there is still some wakelock and I don't know wich app it is causing it.
I have no rooted the phone and I don't know how it could be solved this issue. I hope the next update solves it.
Anything I can help you, just tell me
I've uploaded a screenshot of my batterystats after a few hours of normal use. I hope you find it useful.

Battery Drain

Has anyone else noticed heavy standby drain from Android System?
I spent a couple of hours digging through to find the culprit and it looks like it's actually Qualcomm's IZat location services. Even though you can disable it in the location settings it is still set to scan and report back to Qualcomm's servers via a couple of config files in /etc.
Instead of changing the config files and forgetting which ones I changed I simply disabled the service in location settings then disabled the package that IZat uses and rebooted.
I am already seeing an decrease in battery usage and I have been able to still use GPS.
You can either freeze the app with Titanium Backup or whatever you choose. I did it through adb which I believe is even possible to do without root.
com.qualcomm.location
Code:
adb shell pm disable com.qualcomm.location
I hope this helps someone else out that was having the same issue. I did not get a screen shoot of my battery usage before disabling the service but I have included one with it disabled.
I was losing 15% overnight with a kernel wakelock for the entire night that showed up as LocationManagerServiceEx through GSam

for users with no root:
Code:
adb shell pm hide com.qualcomm.location
I'm going to poke around and try and find the files in /etc you mentioned.. would rather tackle the actual problem in the config files than disable izat entirely. good find though. I'm currently trying to find the source of my Google Play services drain (may be related to pushbullet). you mentioned that it was showing up in your Android system drain so not sure if it'll help with my specific issue but if it does I'll report back.

autoprime said:
for users with no root:
Code:
adb shell pm hide com.qualcomm.location
What is the command to unhide it? I would like to try it but also want to reverse it. Thanks
Click to expand...
Click to collapse

hobbs said:
autoprime said:
for users with no root:
What is the command to unhide it? I would like to try it but also want to reverse it. Thanks
Click to expand...
Click to collapse
adb shell pm unhide com.qualcomm.location
Click to expand...
Click to collapse

autoprime said:
for users with no root:
I'm going to poke around and try and find the files in /etc you mentioned.. would rather tackle the actual problem in the config files than disable izat entirely. good find though. I'm currently trying to find the source of my Google Play services drain (may be related to pushbullet). you mentioned that it was showing up in your Android system drain so not sure if it'll help with my specific issue but if it does I'll report back.
Click to expand...
Click to collapse
I think they were lowi.conf and xtwifi.conf there might have been more but I can't remember at this time.
As for finding what is draining I learned recently (and quickly) how helpful dumpsys is.

KAsp3rd said:
I think they were lowi.conf and xtwifi.conf there might have been more but I can't remember at this time.
As for finding what is draining I learned recently (and quickly) how helpful dumpsys is.
Click to expand...
Click to collapse
ahh thank you. I got sidetracked when trying to pinpoint my drain and never went through all the files. I will check out those 2 files as well as grep around through the rest.
and thanks for the dumpsys tip... never actually used it. I went the easy route and reinstalled BetterBatteryStats. Within 20 minutes a partial waklock stood out... "CmaSystemUpdateService"
A quick google lead me to this reddit: https://www.reddit.com/r/Nexus/comments/4jmw74/cmasystemupdateservice_wakelock/
Made sense... I had blocked OTA updates using the same method Nexus devices use.. as the tmo g5 gets its updates the same way.. instead of using LG's own updater like most of the other variants. As soon as re-enabled "SystemUpdateService" in Google Play Services the wakelock stopped and battery was fine. I'm not sure what needs to be done to stop the wakelock while still blocking OTA updates... more research must be done.

autoprime said:
ahh thank you. I got sidetracked when trying to pinpoint my drain and never went through all the files. I will check out those 2 files as well as grep around through the rest.
and thanks for the dumpsys tip... never actually used it. I went the easy route and reinstalled BetterBatteryStats. Within 20 minutes a partial waklock stood out... "CmaSystemUpdateService"
A quick google lead me to this reddit: https://www.reddit.com/r/Nexus/comments/4jmw74/cmasystemupdateservice_wakelock/
Made sense... I had blocked OTA updates using the same method Nexus devices use.. as the tmo g5 gets its updates the same way.. instead of using LG's own updater like most of the other variants. As soon as re-enabled "SystemUpdateService" in Google Play Services the wakelock stopped and battery was fine. I'm not sure what needs to be done to stop the wakelock while still blocking OTA updates... more research must be done.
Click to expand...
Click to collapse
I had the same drain after disabling updated on my tmo g5. I used app MyAndroidTools to fix it. After you disable system updates open the app and grant root. Open the menu and click on service, broadcast receiver and activity options. In each on goto system then find Google play services and disable anything that says system update then go back and do the same for Google play services framework. After disabling for all three categories restart and your wavelock will be gone. Also you can disable the OTA using this method as well. Seems like when using adb it only disables some of the services but not all which is why it keeps searching for updates. Hope this helps.

I too have this irritating wakelock which prevents the phone from reaching deep sleep (it shows up as LocationManagerServiceEx in betterbatterystats).
When I freeze the com.qualcomm.location app however, GPS actually DOES NOT work the way it is supposed to. Interestingly, it results in the GPS behaving just like the 10A GPS bug--GPS is achieved, but then cuts in and out all the time, making nav near useless. The 10D update fixed this. So maybe the implementation was buggy in the 10a firmware.
Still would be nice to have a more permanent fix for this wakelock issue. I'm not getting the cmasystemupdateservice issue.

autoprime said:
ahh thank you. I got sidetracked when trying to pinpoint my drain and never went through all the files. I will check out those 2 files as well as grep around through the rest.
and thanks for the dumpsys tip... never actually used it. I went the easy route and reinstalled BetterBatteryStats. Within 20 minutes a partial waklock stood out... "CmaSystemUpdateService"
A quick google lead me to this reddit: https://www.reddit.com/r/Nexus/comments/4jmw74/cmasystemupdateservice_wakelock/
Made sense... I had blocked OTA updates using the same method Nexus devices use.. as the tmo g5 gets its updates the same way.. instead of using LG's own updater like most of the other variants. As soon as re-enabled "SystemUpdateService" in Google Play Services the wakelock stopped and battery was fine. I'm not sure what needs to be done to stop the wakelock while still blocking OTA updates... more research must be done.
Click to expand...
Click to collapse
Hi @autoprime,
For some reason, out of the blue, I received the Nougat update notification today. I plan on staying on MM until I retire the device.
I had previously knocked out the OTA update receivers using 3c system tuner, just disabling the receiver elements that matched the 3 ones you listed in your all in one thread.
When I looked at the running receivers, one of them that was still on for some reason (update.systemupdateserviceactivereceiver). I can toggle it off, but it doesn't stick with a reboot. Under services, update.systemupdateservice was still active.
I decided to go the ADB route. I stopped the services using your ADB commands. This fixed the OTA. But then just as you mentioned, the CmaSystemUpdateService wakelock came in.
Did your research come up with any new ways to stop the OTA notification?

jeffsga88 said:
I had the same drain after disabling updated on my tmo g5. I used app MyAndroidTools to fix it. After you disable system updates open the app and grant root. Open the menu and click on service, broadcast receiver and activity options. In each on goto system then find Google play services and disable anything that says system update then go back and do the same for Google play services framework. After disabling for all three categories restart and your wavelock will be gone. Also you can disable the OTA using this method as well. Seems like when using adb it only disables some of the services but not all which is why it keeps searching for updates. Hope this helps.
Click to expand...
Click to collapse
Just saw this post just now. Do you have a more detailed list of what you disabled?

waylo said:
Just saw this post just now. Do you have a more detailed list of what you disabled?
Click to expand...
Click to collapse
Using the app My Android Tools is the easiest way I found. Then do like I said before and go into each category and click on Google play services and search for systemupdate, disable anything the comes up. Then go into Google services framework and search for same thing and disable anything that comes up. I've included some screenshots, hopefully that helps. Maybe when I have more time I'll write each thing down and post list but don't have time right now.

KAsp3rd said:
Has anyone else noticed heavy standby drain from Android System?
I spent a couple of hours digging through to find the culprit and it looks like it's actually Qualcomm's IZat location services. Even though you can disable it in the location settings it is still set to scan and report back to Qualcomm's servers via a couple of config files in /etc.
Instead of changing the config files and forgetting which ones I changed I simply disabled the service in location settings then disabled the package that IZat uses and rebooted.
I am already seeing an decrease in battery usage and I have been able to still use GPS.
You can either freeze the app with Titanium Backup or whatever you choose. I did it through adb which I believe is even possible to do without root.
com.qualcomm.location
Code:
adb shell pm disable com.qualcomm.location
I hope this helps someone else out that was having the same issue. I did not get a screen shoot of my battery usage before disabling the service but I have included one with it disabled.
I was losing 15% overnight with a kernel wakelock for the entire night that showed up as LocationManagerServiceEx through GSam
Click to expand...
Click to collapse
I'm on a unrooted G4 running Nougat but saw this thread and decide to try it, but when I use the above command I get the following error, see grab below, any ideas? thanks