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.
Related
I've been playing with random ROMs recently and have noticed my 'roids acting up.
Upon install of a new kernel/ROM, I bypass the Android/Google services setup pages that show up on initial boot. That gives me the baseline battery drain. It's only when I start to use Google services (like the Market) that it requires me to activate via a Google acct. After the activation, I see the increased battery drain.
Specifically, my battery discharge increases ~2.7x (idle) after I provide my Google account information to access the Market. After I provide the account creds, the GMail app starts working and I receive notifications of new emails.
I've got a theory that the GMail app or another Google app is polling/pulling instead of using the GMail/Google service to push the data and that this is using additional CPU.
Is this theory correct? Has anyone else seen this behavior?
P.S. My service provider, Verizon, uses a NAT (IP 10.xxx). I can't see how any external service can push anything through a NAT unless it has special access through the NAT. Can Google?
P.S.S. I know I can disable background data and auto-sync via Settings--> Accounts & Sync. It seems to fix the problem but I can't pin it down specifically to an app/service.
- Samsung Droid Charge
- Verizon Wireless 4G
- kernel 2.6.32.9 imnuts at virtualbox 1
- Humble 1.51 EE4 Android Froyo (currently)
Any help?
Anyone? I've received no responses and this seems like a question that could affect a large number of Android users.
Hi!
2 things I've done recently seem to have "removed" Google services from my battery usage when idle.
1.Using Titanium Backup/Menu/Market Tools/Market Auto Updates/Deselect all and Save auto Updates configuration.
2.Go Maps/More/Location History and then press the back button and go Menu/Settings /Location reporting/Location Reporting-Do not update your location+disable Location history+sign out of Latitude.The first 2 I've always done but signing out of Latitude seemed to make the difference.(Disable both Check ins).
There are obviously the other usual battery saving settings but these 2 got rid of Google Services.
HTH.
Galaxy S
Darky JW1 Base
Semaphore 2.2.0 Kernel
Modem ZSJPG
If you have no other regular apps working the background, google services as gmail or gtalk or contacts sync or calendar will surely increase battery usage, but it should be in the dimension of 2.7 times.
Battery life
Battery now down to 26% from full with 2d 1h 48m on battery.Google services has gone from 80%+ to 2%.Couple of screenshots attached.This Google services thing is not the only answer to battery life problems but there's always something running in the background doing the damage.HTH.
I've noticed that when I've got my EVO active on WiFi there's some significant network traffic between it and Google even when the device seems idle. I also have a cell phone repeater in my basement that shows activity when I so much as hit the power button to unlock the phone. Feels like there's stuff going on with some of those apps that maybe excessive and, yeah, that could impact battery drain. It certainly can't be good for it.
it is indeed.
Launcher?
Changed from TW Launcher to Go at about the same time as fiddling with Google Services above.Could it be that this has also made a difference.It has been a big improvement whatever it is.
Phone:Galaxy S I9000
Modem:XXJVQ
Romarky JW1 Base
Kernel:Semaphore 2.4.0
Launcher:Go
Theme:Honeycomb
[Q] Wifi & network location unavailable after switching location off & on again
Hi there,
I found this strange but reproduceable bug on my N5's location services and was wondering if it's the same for you.
Turn off location via settings or quick settings
Turn it back on
You'll be asked to accept Google location terms
Switch to battery saving mode (only wifi & network, no GPS)
After these steps, my N5 cannot find it's location via Wifi & mobile network anymore. In Maps it might still show the blue dot but moving around it won't update. When using any other app which will try to get a fresh location it's a no go. Like Google+, try and make a post with location, no joy.
I have to reboot to get it working again.
Did you agree to those Google terms? If not that's the reason...
cawith said:
Did you agree to those Google terms? If not that's the reason...
Click to expand...
Click to collapse
I agreed to those of course. If you cancel that it will turn back to device (GPS) only
Sander M said:
I agreed to those of course. If you cancel that it will turn back to device (GPS) only
Click to expand...
Click to collapse
Strange. Are you running stock ROM? I had no problem doing the thing you described.
cawith said:
Strange. Are you running stock ROM? I had no problem doing the thing you described.
Click to expand...
Click to collapse
Just got it 2 weeks ago, all is stock, locked and original.
Did you try any other app besides Maps? That sometimes uses last known location and shows blue icon.
Sander M said:
Just got it 2 weeks ago, all is stock, locked and original.
Did you try any other app besides Maps? That sometimes uses last known location and shows blue icon.
Click to expand...
Click to collapse
You're right, mine also won't find my position without GPS. However a reboot fixes it for me.
Somewhat glad to see others having this bug too. Indeed a reboot fixes it right up so it's not a huge deal.
Under normal circumstances I would't change this setting ever, but when I just got my N5 I wanted to test the GPS only feature. After turning it back to Battery saver I noticed and started investigating what caused it.
Thanks for testing mate!
Sander M said:
Somewhat glad to see others having this bug too. Indeed a reboot fixes it right up so it's not a huge deal.
Under normal circumstances I would't change this setting ever, but when I just got my N5 I wanted to test the GPS only feature. After turning it back to Battery saver I noticed and started investigating what caused it.
Thanks for testing mate!
Click to expand...
Click to collapse
No problem. I'm glad also to be aware of it now, so that I can avoid standing somewhere I need and it won't find it
Anyone else willing to try this? The N5 from a friend of mine did not show this behavior. And another did. Weird bug.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
I have the problem on my 16 GB black nexus 5 with stock Rom and no root. I tested with dalvik and art but the problem exist. I have found 3 solutions:
1- reboot phone (temporary solution)
2- stop Google Play Services (temporary solution)
3- uninstall updates of Google Play Services use with stock/no update (permanent solution)
one more thing; when I can't get a location fix with network/wireless GPS mode on Google Maps or any other application, I can see a circle on " Yandex Navigation" that shows my location.
but more interesting thing is I can see a circle that shows my location on Yandex Navigation when my GPS is completely off.
I think this problem is about Google Play Services or Google Location Services. I hope someone find a solution.
ymeksur said:
I have the problem on my 16 GB black nexus 5 with stock Rom and no root. I tested with dalvik and art but the problem exist. I have found 3 solutions:
1- reboot phone (temporary solution)
2- stop Google Play Services (temporary solution)
3- uninstall updates of Google Play Services use with stock/no update (permanent solution)
one more thing; when I can't get a location fix with network/wireless GPS mode on Google Maps or any other application, I can see a circle on " Yandex Navigation" that shows my location.
but more interesting thing is I can see a circle that shows my location on Yandex Navigation when my GPS is completely off.
I think this problem is about Google Play Services or Google Location Services. I hope someone find a solution.
Click to expand...
Click to collapse
Thanks for your (rigorous :good tests.
Reboot was the one I used to fix it, didn't know about the others you found.
In a strange way glad to see it's a software bug, which means it's fixable. I guess the friend I mentioned has not updated the Play services ever, that would explain why he is not affected.
happens to me as well on a Nexus 7 (2013). I've found that battery drains faster even when in deep sleep
Me and my colleague also have this issue...
Completely wiped and factory reset to stock, same prob.
Reboot solves it until you turn location services off and on again, or go from "device only" mode to "battery saving".
A quicker way then reboot (reboot actually does the same as this step) is go to settings, apps, running, Google Services (you might have 2), there STOP the GoogleLocationService (it will stop and reload the service)
Location should work again in battery saving mode...
Thanks for that one Foggy79!
Reboot or restarting the google play services takes much longer (especially when you have to disable ADM first) then your trick of only stopping the only location service.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Sander M said:
Thanks for that one Foggy79!
Reboot or restarting the google play services takes much longer (especially when you have to disable ADM first) then your trick of only stopping the only location service.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
No problem.
I just reproduced the issue on an other colleague's N5, that makes 3 ppl here in the office, can't be coincidence.
If the GoogleLocationService could restart automatically when you turn on "Location" and agree the terms, that would be great...
Foggy79 said:
No problem.
I just reproduced the issue on an other colleague's N5, that makes 3 ppl here in the office, can't be coincidence.
If the GoogleLocationService could restart automatically when you turn on "Location" and agree the terms, that would be great...
Click to expand...
Click to collapse
It appears the issue is fixed for me.
I have Google Play services 4.3.24 so it might be fixed behind our backs.
Now when you turn the location off and on again, the GoogleLocationService is automaticly restarted also
Fixed for me as well with the new Google Play Services!
The new version now indeed restarts the LocationService again.
I'm glad Google also reads XDA (j/k)
Now if they can get GoogleLocationsManager and NlpLocationsReciever to stop running when Locations Services are turned off completely, that'd be great.
Sent from my Nexus 5 using Tapatalk
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.
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
Hi, so the simplest way of stating my problem is when my device is either unlocked (AKA browsing apps and whatnot with the screen on), or locked (sleeping), notifications are slow to arrive. Right now I've been testing with Skype, and Gmail, both of which are inconsistent. My OPO does not currently have a SIM card (haven't setup the plan yet), and I've tried with both LTE and Radio off (using *#*#4636#*#* on the phone info page)
Info about my OPO/Setup:
Flashed CyanogenMod 12.1 as stated in the Sultan thread before flashing Sultanxda Rom
Using Sultanxda Unofficial CyanogenMod 12.1 Sep 14, 2015 (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-12-1-t3120259)
Using AK v.020 CAF Kernel (http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t3189886)
Using StyloKing v1 Synapse profile for CAF (http://forum.xda-developers.com/one...ad-oneplus-t3163211/post62600798#post62600798)
Using build.prop mods (http://forum.xda-developers.com/oneplus-one/general/build-prop-tweaks-device-t3168207)
Using TK Gapps Pico (http://forum.xda-developers.com/android/software/tk-gapps-t3116347)
Using Oxygen OS Modem ONLY (http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516)
Using Xposed for Lolipop (http://forum.xda-developers.com/showthread.php?t=3034811)
Using Greenify and Amplify with settings from both of these threads (http://forum.xda-developers.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588 & http://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884)
My OPO does not currently have a SIM card (haven't setup the plan yet)
Things I've tried:
With both LTE and Radio off (using *#*#4636#*#* on the phone info page)
Older Skype versions
Push Notification Fixer (https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer&hl=en)
Disabling Amplify by disabling the module in Xposed, and rebooting
Double checked that Greenify isn't touching Skype or anything related
I also have a Samsung Galaxy S3 that is using the stock ROM (Android 4.1.2) with root permission and a custom recovery. That is the device I've been using to test with. If I send a Skype or Gmail message from my OPO to the Galaxy, it takes 2-3 seconds EVERY TIME consistently.
If I send a Skype or Gmail message from the Galaxy to the OPO, sometimes I'll get the message within 3-5 seconds, other times it takes 1 minute+ and even a few messages don't arrive until I unlock the device and open Skype or Gmail.
When I leave Skype open, and lock my OPO, it seems to get the messages very quickly almost every time.
Also, it appears that when my phone sleeps for a certain period of time, seems inconsistent, the WiFi will disconnect - and I DO have keep WiFi on while phone is sleeping.
I've run out of ideas short of trying a full wipe and different rom/kernel/who knows what at this point...=\
Any/all help is greatly appreciated. Thanks.
Edit/Update: Found this post (http://forum.cyanogenmod.org/topic/107023-cm12121-wifi-connectivity-issuesdrops-workaround-included/) on another forum, and that seems to have fixed it for me. Doing further testing, but so far positive results.
The delayed response is most probablye due to the Greenify/Amplify tweaks that you've made. Remove everything related to Gmail, Skype, Google Play Services from Greenify & Amplify and then test. Add back the tweaks one by one and find the culprit.
I've already tried that. Fully disabling Amplify, and double checking that I've touched nothing close to Skype or Gmail or Google Services in Greenify's settings.
As I put in the edit in my first post, I found out going to /system/etc/wifi/WCNSS_qcom_cfg.ini and changing the line
Code:
McastBcastFilter=3
to
Code:
McastBcastFilter=0
appears to have solved the issue for me.
But when I did that, I also noticed something else, and I wish I hadn't unplugged my device (AKA wiping battery data so I could show a clear screenshot of what I mean), because I saw when I was looking at the battery usage chart, all day long while I had McastBcastFilter=3, my WiFi signal was turning on and off CONSTANTLY throughout the day, and sometimes for decently long periods. Now that I've changed McastBcastFilter=0, my WiFi signal shows that it's on 24/7 in my battery screen.
I'm worried that this is going to cost me a fair bit more battery, but at the same time I need my notifications.
I found another setting in that file with this comment:
Code:
# Enable suspend or not
# 1: Enable standby, 2: Enable Deep sleep, 3: Enable Mcast/Bcast Filter
gEnableSuspend=3
Before I made any changes to this file, it was set to 3, which makes sense with the McastBcastFilter changes I made. But attempting to get some more battery life so my WiFi goes into some sort of partial power save mode for battery longevity, I'm going to try my OPO with Enable Deep Sleep on all day. We'll see how the battery fairs and if notifications are still delayed or not.
Edit: I was able to get the data from my secondary battery app so screenshots for all!
This is what my Wifi/Battery was like before I changed McastBcastFilter at all:
Code:
imgur.com/ZXmFYhI
This is after I changed it from 3 to 0:
Code:
imgur.com/H5ZlXc2
And this is what it's been like since I rebooted last night with gEnableSuspend=2 (AKA Deep Sleep):
Code:
imgur.com/2O6GuVE
Obviously when the WiFi is off, I'm not getting my notifications. >=\
(Gave the URLs CODE tags so I could link the images...)
Well so far I haven't seem to have come across any issues with leaving BcastMcast at 0 and using Deep Sleep for WiFi. I'm still getting all my notifications, and as far as I can tell the battery life is give or take about the same. Possibly a little more battery drain than with BcastMcast on, but I haven't done any sleep tests yet, just initial observations with using OPO in a daily setting.