Related
I was wondering if anyone else is experiencing this phenomenon with mobile data draining battery?
As an experiment yesterday I disabled mobile data and wireless with 9% left and managed to make it the entire day with very light use.
Today I have only wifi enabled and see that I have less than 6% drained in last 4 hours.
So, is there a way to disable mobile data bazed on location or times of day etc? Or maybe even a program that only enables mobile data for 10 minutes every hour or something.
Sent from my SCH-I500 using XDA App
EB01 still has some goofy things that are causing wake locks.
Seems to be different for everyone. Some have it with GPS, I personally have it with auto-rotate, and some have it with WiFi or Mobile Data.
EB16 apparently leaked last night, so we should see something (hopefully) soon.
Oh, well that's good to know. Hopefully it corrects thjs issue and others.
Sent from my SCH-I500 using XDA App
I am having similar issues. hopefully updates will fix it, but with only Wifi enabled, I get up do 2 days of moderate use. With 3g only, much , much less. I had first thought it was because my signal strength isn't great all the time. While that could certainly have something to do with it it's "good to know" that others are having similar issues.
Here's hoping new updates clear up some of the issues!
as an fyi, turning wifi and data off overnight" slept" my phone and it disabled the alarm i had set. wouldn't work again until a reboot.
Samsung Fascinate - EB01/Froyo.
SuperClean 2.4 Voodoo
MTM iOS keyboard
Cyanogen Boot Animation
Warning: I know just enough to be dangerous
So, I'm rooted on VZW with no OTA and suddenly had abnormal battery drain today. Any idea why this may be happening?
Mine is kinda high today as well. I saw something about Google having issues today with email and other applications. This could be related, or phones can't connect to Google so it just keeps on trying.
Sounds nice but don't know if it's true or not.
Sent from my VS980 4G using Tapatalk 4
Install Greenify. Hibernate all the APPs that you don't want notification from first. This app doesn't allow APPs to Wakelock you're phone. Once you find which offending account is the issue you'll be ok. I found that Facebook woke up my phone thousands of times and I have up notifications. Best choice ever ?
This app requires root and free in the app store.
Sent from my VS980 4G using XDA Premium 4 mobile app
Greenify can't touch system apps to my knowledge but yes, it is an excellent solution for rogue apps that take up resources when they shouldn't. :good:
As far as the google services battery drain, I eliminated that by simply turning off google location services. The actual GPS is so quick to lock that I haven't run into a scenario yet where I'd absolutely need to turn it back on.
My location services are off. Doesnt seem to help me much. I also bought donation greenify and greenfied Google Play services and Google Play Store
sent from the galaxy via tapping and talking
With 15:34 for time on, and 1:45 of screen on time, I'm currently at exactly 50% battery. I feel it was something awry with Google Services yesterday and an isolated issue. Location services were off today, but I did nothing with Greenify, yet at least.
nismology said:
Greenify can't touch system apps to my knowledge but yes, it is an excellent solution for rogue apps that take up resources when they shouldn't. :good:
.
Click to expand...
Click to collapse
Donate version is able to greenify system apps.
Sent from my VS980 4G using Tapatalk 4
Yeah I had the same problem, yesterday. I was having Google services use ~60% of battery life. Surprisingly I still got all day battery life.
Sent from my Nexus 7 using Tapatalk 4
heffzilla said:
Donate version is able to greenify system apps.
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
Didn't know that but knowledge is good! :good:
shekinahsmoke said:
My location services are off. Doesnt seem to help me much. I also bought donation greenify and greenfied Google Play services and Google Play Store
sent from the galaxy via tapping and talking
Click to expand...
Click to collapse
How is that working? Considering doing the same as I've already tried removing the sytem app and replacing with Play Services from the play store. That seemed to work for a few days but the nip wake locks are worse than ever right now. Killing the otherwise stellar battery.
iowabowtech said:
How is that working? Considering doing the same as I've already tried removing the sytem app and replacing with Play Services from the play store. That seemed to work for a few days but the nip wake locks are worse than ever right now. Killing the otherwise stellar battery.
Click to expand...
Click to collapse
works great today..... google services error has gone away today and my battery life seems longer. :good:
I just froze google play services and will look at the battery stats later to report the difference. What apps are affected by freezing this though? It seems Hangouts is one.
I don't know why, but all my days are pretty much exactly the same location-wise and some days have huge wakelocks, others don't.
Aside from installing the play store services which seemed to help quite a bit, I've also noticed a nice drop in wakelocks since I went on to Google's Location History dashboard (https://maps.google.com/locationhistory/b/0/dashboard?hl=en) and deleted all my history so maybe it could re-create it.
One thing I've noticed is that on high-wakelock days, my GPS is going nutso. My point markers on that dashboard will have me moving ALL OVER the place, even while I'm just sitting at my desk at work.
This leads me to the conclusion that signal plays a huge role, and I do have bad signal at work (1 bar, and can't get a good GPS lock at my desk).
Also, you can minimize these wakelocks without the use of Greenify by simply turning off Location Reporting and Location Using WiFi and Mobile Networks. This dropped my wakelocks to pretty much 0, immediately. But you'll lose things like weather widget geolocation and some Google Now features. On the other hand, this is a more viable option than freezing services which can cause you to lose push notifications for GMail among other things.
I've been messing with this throughout the day today and the problem is high NIP wakelocks originating from Google Services...specifically the Network Location process. So the fix for me appears to be disabling newtork location while leaving GPS location enabled. This is usally the reverse of how I do things but for this phone, it may be the better solution. Google Now is still working for me, as is maps/navigation. There may be some casualties of disabling newtwork location but I haven't run across them yet. I've always viewed these two options as coarse (network) vs.fine (gps) location. So I'm hoping GPS picks up the slack and I don't lose any functionality. What I could see happening is that it just takes longer for location to be confirmed because network location is faster. I'll take that in lieu of battery drain however.
Still need to run like this for a couple days to see how things go but I was getting hundreds and even thousands of NIP wakelocks in a run cycle prior to disabling network location. I'm now getting zero.
iowabowtech said:
I've been messing with this throughout the day today and the problem is high NIP wakelocks originating from Google Services...specifically the Network Location process. So the fix for me appears to be disabling newtork location while leaving GPS location enabled. This is usally the reverse of how I do things but for this phone, it may be the better solution. Google Now is still working for me, as is maps/navigation. There may be some casualties of disabling newtwork location but I haven't run across them yet. I've always viewed these two options as coarse (network) vs.fine (gps) location. So I'm hoping GPS picks up the slack and I don't lose any functionality. What I could see happening is that it just takes longer for location to be confirmed because network location is faster. I'll take that in lieu of battery drain however.
Still need to run like this for a couple days to see how things go but I was getting hundreds and even thousands of NIP wakelocks in a run cycle prior to disabling network location. I'm now getting zero.
Click to expand...
Click to collapse
I believe disabling network location will disable Google Now location cards, such as weather or places.
cheami said:
I believe disabling network location will disable Google Now location cards, such as weather or places.
Click to expand...
Click to collapse
You are correct, there's the first casualty confirmed. I'm going to run like this for a few days and see what gives. I don't use the cards anyway so no issue there. If anyone knows of other functionality loss, please speak up.
Like some of you have said, I don't rely on Google Now cards, and I don't leave the city I'm in, so for things like weather, I am find with the hourly syncing of my weather app. If I do need GPS/location services, it's not hard to toggle and battery life is incredible. I feel it was just something going rogue the other day. Today, with locaiton off, I've been off the charger for 15:34 with 1:24 screen on time and I'm at 58%. I spent a good portion of today in a sub-basement on airplane mode, with wifi active in the background though. Walking around campus, I used Songza via 4G due to some wifi weak spots. I can't be happier with this phone, as my GNex would have long since been dead, even on airplane mode.
EDIT: Holy ****, 15:34 sounded familiar, checked my post from yesterday, I responded then at the same time off the charger...
Okay so I may have fixed it on my phone.
I forced closed "Google Play Services" and "Google Devices Framework" then rebooted.
Google services was using it 50% of battery consistently through the day and now its down to using 2% of battery. I'll come back at the end of the day with battery stats.
Sent from my Nexus 7 using Tapatalk 4
this night was a pain.... the phone was on 83 and when i wake it was on 76..... google services was draining all my battery, who could fix this?
Hello everyone!
I've been having excessive wakelocks from "wakelockmanager", check out Wakelock Detector stats on the attached image. I'm using CleanROM 1.5 with Galaxy Gear connected all the time. Anyone else experiencing this problem?
Thanks!
XanoZuke said:
Hello everyone!
I've been having excessive wakelocks from "wakelockmanager", check out Wakelock Detector stats on the attached image. I'm using CleanROM 1.5 with Galaxy Gear connected all the time. Anyone else experiencing this problem?
Thanks!
Click to expand...
Click to collapse
I've done some other tests and I only see the wakelocks when I'm connected to the mobile network (with or without data). I use my Verizon Note 3 on GSM/WCDMA.
Sent from my SM-N900V using xda app-developers app
Any follow up on this? Having the same problem all of a sudden
Do you have Android Firewall and/or XPrivacy XPosed module?
I have T-Mobile Note 3 with stock ROM and I noticed this battery drain also when I have both installed. I actually have these wakelocks within 3 hours after rebooting.
- WakelockManagertimeout (runs 808 times)
- WakeLockManager (runs 1107 times)
So maybe it is something that is universal rather than restricted to a particular model (Verizon, T-Mobile, etc.)
I actually just installed xprivacy and rebooted. So far I don't have the wakelock anymore but has it within 6 hours or so after the first reboot... Frigging strange I can't pinpoint what it is even in BBS.
fookea said:
I actually just installed xprivacy and rebooted. So far I don't have the wakelock anymore but has it within 6 hours or so after the first reboot... Frigging strange I can't pinpoint what it is even in BBS.
Click to expand...
Click to collapse
Probably the Android Firewall then. Some networking related process must be running in the background that intercept network request from the application.
However, if OP doesn't have these 2 apps, I am not sure what caused the excessive wakelocks...
Wakelock Detector quit working for me on 4.4.2. It crashes shortly after opening the app and giving it SU permissions.
i don't have Android firewall at all. I did deny some location and wakelock permissions in AppOps and it's better now. I'll post some pictures with the apps i have maybe we can compare them and find the culprit this way.
https://mega.co.nz/#!dIl3mRoa!XK4Yg1Dh-9E-AXgoA5BAIJm9qV-Y6QA2ewGU_JMuDUk
https://mega.co.nz/#!JZFm0RLY!V4Pu8elpJJN8Ufk8_k3qj-P1yoY_zruuv07wV84EM8A
https://mega.co.nz/#!tEUwVT4T!-UQPZdIGhCHgbvRvSe57l2i4ccPegRmUjDtr2OlCXoM
https://mega.co.nz/#!dF9jDDBY!sLRsk5b_Nur22gADlKx6vG7NcJ9T81lU5E0QpQXkOhA
Ignore the obvious ones like facebook and games.
I solved my issue. I ran Catlog and found that the csc was causing me a lot of wake locks. I have ORO CSC and flashed a SIN CSC. Somehow it was constantly trying something in the background. I deleted all the CSC folders except the common one and everything is back to normal. Also my Android OS and Android system are low now. The folders are located in /system/csc. I do advise backing them up in case something goes wrong.
Hope this helps
I tried searching Google for battery drain related to Play Services. Up until my phone had official KitKat, even with CM11, the battery drain from play services was never this horrendous (about 36% battery usage).
The only thing I could find besides version 4.4 was the "fix" for battery drain related to location was that some Sony devices, upon upgrading to KitKat, suffered similar problems with battery.
I've come to the conclusion the RAZR HD/MAXX HD suffer from the same issue.
Downloading BetterBatteryStats I found when GPS was the only way of doing location services, the battery drain is ~1% an hour. When I had high accuracy or battery savings mode, the drain was ~3.5% an hour. This is the EXACT issue that the Xperia devices are suffering from.
So, for all those on KitKat who are experiencing battery drain, try switching to Device Only. This will utilize only GPS satellites to determine location. You will lose location based stuff in Google Now, suck as traffic or weather but your battery will last much longer.
I looked through and didn't see anything about this in any other thread, so I decided to make a new one. Hopefully Google updates Play Services to be a bit more friendly with LTE and WiFi location settings soon (I'm looking at you, I/O).
Sent from my DROID RAZR MAXX HD using XDA Free mobile app
Another potential way around this is possibly using the Greenify app, if you're rooted. You'll also have to donate ($2.99 USD) but it's well worth it if you ask me. I actually used my Amazon Coins to donate that way.
With a donated version, you can hibernate system apps, but you have to be careful because hibernating certain system apps could cause other apps to no longer work (which is easy to fix - just unhibernate them). But, this is different from freezing apps. Freezing an app means you've disabled it. What Greenify does is prevent the phone from starting up apps when the screen is off (wake lock). But, you can launch the app yourself and it will fire up (albeit maybe a little slower since it wasn't pre-loaded) and then when the screen goes back off, Greenify will hibernate the apps again.
This is another way to stop apps from firing up when you're not using your phone. I've noticed Google Play services going nuts one time. A reboot cured it, but I wasn't sure what apps would have been using it. I've since Greenified some regular apps and I haven't seen it happen again.
But, Greenify is definitely something to look at. The non-donation version only allows you to greenify non-system apps, but even for those, it works really well.
You can get it at Google Play or at Amazon App store.
I haven't got issues with battery drain at the moment but I bookmarked this link of reddit and maybe it help you.
Sorry for the English
http://www.reddit.com/r/Android/comments/1zxri4/google_play_services_battery_drain_the_real/
Enviado desde mi RAZR HD mediante Tapatalk
I believe I read that thread, too. It is helpful to understand that Google Now is really what's killing the battery. I've noticed that the battery life is one again incredible on my phone after changing to device only. This allows me to still use navigation if necessary and also allows my weather extension in DashClock to work because the one I installed allows the phone to read GPS location instead of relying on my network location. So for now while I lose traffic updates and weather updates through the Google search app, it's not SO bad. I seriously hope they modify the number of times that Google pings for your location or figure out how to cause less drain on the battery, because I find the location stuff incredibly useful at times.
Sent from my Nexus 7 using XDA Free mobile app
Looking through the time line today saw this thread and remembered this app. Hopefully its helpfull
Hey everyone,
I just wanted to ask for some experiences with the "mobile radio active bug" under 5.1.1. Is there anyone who had this bug on a previous version and recently updated to 5.1.1? What are your experiences? Did it go away, did it improve, didn't it change at all?
To clarify, the mobile radio active bug is a bug specific to Lollipop under various android phones. It's symptoms are (though they might not be related):
- significantly reduced battery life (especially when screen is off)
- unusually high times under the mobile radio active stats in the battery monitor (mra times were almost as high as the run time itself)
- apps establishing internet connections (like whatsapp, facebook, chrome) are by far the top battery consumers (according to the battery stats)
For further information there are bug reports at google regarding these issues:
https://code.google.com/p/android/issues/detail?id=165558 (Report for Android LP)
https://code.google.com/p/android-developer-preview/issues/detail?id=2556 (Report for Android M)
To isolate it from similar bugs encountered with LP:
- it is not a bug that results in sudden drops of battery %
- it is not a bug that won't let you charge your phone
- it is not a bug that keeps the cpu awake (by google services or other apps)
So, what are your experiences?
Thanks in advance
Walli
I had high "mobile radio active" times in both 5.0.2 and 5.1.1, but this never translated into lower battery life for me. It is just a problem with inaccurate stats/reporting. This is confirmed by others in the following discussion: http://forum.xda-developers.com/xperia-zl/general/cm12-1-cell-standby-mobile-radio-active-t3188147
I have it only when i'm on 2g/3g/4g. If wifi active the bug is not present.
It's due bam_dmux_wakelock and a lot of people (with different phones) have it since OTA to 5.1.
here is a good analysis, exactly what happens to me:
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.
Click to expand...
Click to collapse
ltcdata said:
I have it only when i'm on 2g/3g/4g. If wifi active the bug is not present.
It's due bam_dmux_wakelock and a lot of people (with different phones) have it since OTA to 5.1.
here is a good analysis, exactly what happens to me:
Click to expand...
Click to collapse
Hi there,
I did some profiling with my Xperia z3 compact both with mobile data enabled (4G LTE with good signal quality) and without mobile data enabled and measured the power consumption using Trepn-profiler and there is no noticable difference between both. (Note that the state of the mobile data never goes to dormant, but stays idle.) Despite no difference in power consumption, the android power usage screen re-organizes applications with an active radio "on" more to the top. So either the z3 compact is build with a mobile data component which nearly consumes nothing when idle or the android power statistics calculation is incorrect.
Concerning the bam_dmux_wakelock, this is a sperate thing. It stands for bi-directional amplification demultiplexing and although I'm by far an expert on the matter my gut-feeling tells me it is something similair like rx_wlan wakelock. Meaning: you're phone keeps track of the wifi-network you're connected to and it responds to packets which could be addressed to you and creates a wakelock accordingly. If you're on a wifi-network with bad coverage or a lot of other devices on it (eg.: pc, other phones, etc.) this wakelock will show up a lot. I think the same holds true for the bam_dmux_wakelock: it is part of the phone being connected to the mobile network. Bad coverage or a lot of traffic could be the culprit.
So its only relation with the mobile radio "bug" is that this wakelock can only happen when it has a connection to such a network. The fact that the mobile radio is active (and the "bug") has no relation with the frequency of this wakelock. I think it is more due to the qualty and signal strength of the mobile network.
Another possibility: I stated that when the mobile radio is active, it never goes to a suspend state or sleep state. So perhaps that component doesn't need to wake up and hence doesn't require the wakelock. For other phones it could be the case that it wakes up from time to time to check the network status (and consumes a bit of power when switching from suspend/ sleep to idle state) and hence the wakelock shows and power consumption increases.
But on a Xperia Z3 Compact, there is no real power consumption due to the mobile data being on, or I'm lucky to be in an 4G network with top notch signal coverage. The one thing that is not correct at all is that applications with the variable mobile data on is getting pushed towards the top of the standard android power management list.
Kind regards.
the_Walli said:
[...] So, what are your experiences?
Click to expand...
Click to collapse
I currently have this bug on stock Sony 5.1.1
Facebook was my top battery consumer, and I usually don't use it a lot (twice a day). Problem solved with Greenify.
Now Google Play & Google Services are my top consumers (respectively 15% and 13%, 12% for the screen). For both, mobile radio is active about 1h30 on a 2h screen on time.
I just installed MobileActiveRadioFix for Xposed and will see if it brings any improvements !
I've got problem with battery drain when both wireless connections (mobile data and WiFi) are available - then my device cannot enter deep sleep because alarm com.android.internal.telephony.data-reconnect.default is raised every 20s.
This problem is not visible when using WiFi only and I suppose when mobile data only - then there is another alarm com.android.internal.telephony.data-stall but it's less frequent so I does not drain battery so much and it could be natural alarm.
I will do full reflash in a week or two and will see if the problem is gone or it's a bug in firmware.