Database Info

Google play services wakelock after update 6.1.74

After updating to latest version of Google Play Services I have started to notice some sort of partial wakelocks. After 6hrs use I've got 44mins wakelock by google play services. Has anyone else noticed such behaviour? I have tried Purity Rom, Cm and Carbon just incase if there's difference, but I've encountered the same wakelock always. Here's what wakelock detector shows

http://forum.xda-developers.com/showthread.php?t=2785128

Lethargy said:
http://forum.xda-developers.com/showthread.php?t=2785128
Click to expand...
Click to collapse
Edit:thanks!

wakelocks are how your phone works, they are supposed to be. an occasional incident might happen, and a process will get "stuck", which could keep a wakelock active. tell me, your wakelock, is it draining battery faster than usual? a reboot will usually fix these kinds of incidences. but you say you flashed roms since, and still the same.. so my next question is which apps are you using that is using this wakelock?

simms22 said:
wakelocks are how your phone works, they are supposed to be. an occasional incident might happen, and a process will get "stuck", which could keep a wakelock active. tell me, your wakelock, is it draining battery faster than usual? a reboot will usually fix these kinds of incidences. but you say you flashed roms since, and still the same.. so my next question is which apps are you using that is using this wakelock?
Click to expand...
Click to collapse
Afaik I don't use any apps that trigger these wakelocks I've experienced. The only solution I've found so far is to disable services called "Configfetchservice" and "userpresenceservice". I've got these wakelocks no matter what ROM or even if I had disabled all Google stuff (sync, location, device manager and so on). Always after a day I have about an hour of Google play services wakelocks by userpresenceservice and configfetchservice. Never had this before. I'm sure it has something to do with latest google play services versions. I know wakelocks are very important part in smartphones but these kind of wakelocks are everything else but wanted.

rockknee said:
Afaik I don't use any apps that trigger these wakelocks I've experienced. The only solution I've found so far is to disable services called "Configfetchservice" and "userpresenceservice". I've got these wakelocks no matter what ROM or even if I had disabled all Google stuff (sync, location, device manager and so on). Always after a day I have about an hour of Google play services wakelocks by userpresenceservice and configfetchservice. Never had this before. I'm sure it has something to do with latest google play services versions. I know wakelocks are very important part in smartphones but these kind of wakelocks are everything else but wanted.
Click to expand...
Click to collapse
so you are saying that these wakelocks exist for you.. one very important question to an answer you havent mentioned at all, are these wakelocks causing battery drain?

simms22 said:
so you are saying that these wakelocks exist for you.. one very important question to an answer you havent mentioned at all, are these wakelocks causing battery drain?
Click to expand...
Click to collapse
Not really shocking drain but noticable it is, which is nothing exceptional. It does these wakes during deepsleep every now and then. And of course when device is not used much and there is google play services on top 3 consuming elements at settings-> battery that's not the way it should be. Now I'm going to enable those services again and look for the logcat if I could find out to which app it is related to.

rockknee said:
Not really shocking drain but noticable it is, which is nothing exceptional. It does these wakes during deepsleep every now and then. And of course when device is not used much and there is google play services on top 3 consuming elements at settings-> battery that's not the way it should be. Now I'm going to enable those services again and look for the logcat if I could find out to which app it is related to.
Click to expand...
Click to collapse
if its draining some battery, but nothing in large amounts, i wouldnt really worry about it. as sometimes these wakelocks appear, then disappear a week or two later.

simms22 said:
if its draining some battery, but nothing in large amounts, i wouldnt really worry about it. as sometimes these wakelocks appear, then disappear a week or two later.
Click to expand...
Click to collapse
I guess you're right. I'll just keep those services enabled for a week or so and see wheter it goes away or gets nasty and drains my battery in couple hours.

rockknee said:
I guess you're right. I'll just keep those services enabled for a week or so and see wheter it goes away or gets nasty and drains my battery in couple hours.
Click to expand...
Click to collapse
a while back, these kinds of things drove me crazy. then one day i just decided not to think about them anymore, and have been better off since. sure, every once in a while(rare, usually location oriented) a wakelock will appear that will drain lots of battery, but ill just use the disable services app to kill that wakelock for a week or two, then ill switch it back and all will be normal.

Anyone else having lots of wakelocks after flashing new kernels?

Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks

KodRoute said:
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.

Lethargy said:
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Click to expand...
Click to collapse
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?

KodRoute said:
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
Click to expand...
Click to collapse
The CPU throttles at 65C by default (some kernels change this or give you an option to change it), and shuts down at 105C. 47C is hardly anything.

Kernel wakelocks draining battery, anybody else? Help needed

Hello all,
My phab 2 Pro is draining its battery too fast with the screen off. Using Battery Historian I've been able to pinpoint it down to something keeping the phone awake when it should be sleeping. The problem is it happens randomly and I haven't been able to "connect" it to a specific app or setting.
The "kernel wakeup reason" that Battery Historian shows as the (I think so anyway) culprit is "Abort:Wakeup IRQ -1169425744 (null) pending". The number after "IRQ -" changes from log to log.
Something else that keeps popping up on the "Userspace wakelock" line with short bursts is "RILJ". This is precisely during the period that the phone is "awake" but the screen is off. So maybe the RILJ and the IRQ thing have something to do with each other?
Steps I took:
Full factory reset
Uninstalled ALL apps that can be uninstalled.
Disabled ALL apps that can be disabled, apart from things that have to stay like keyboard.
Switched of any Location setting that can be switched off
Switched of all syncing that can be switched off
Enabled developer options (to be able to pull the bugreport.txt off the device using adb)
Engaged airplane mode
But even with all of these steps, which leaves the phone totally unusable (but I have another daily driver) this weird kernel wakelock still happens frequently, draining the battery very fast. Going from 38% down to 9% in just 6 hours, with the screen off(!) is plainly unacceptable.
Are there other users out there experiencing the same? I know of one guy who posted lasted year, but maybe there are more out there?
Can anybody help with this? I have no idea what to do now I more or less now where the problem lies. I'm no coder and don't know anybody at Lenovo...
Regards,
Sander

Is not normal what happens to you, but as a remote solution ... try to get into the applications that are working, and look at google services, there is one that spends a bestiality, it is called fileakintentoperation $ external that application next to the others Spend a lot of ram, I ended up blocking the services of google play and play store, and I assure you that the battery lasts for more than two days

rogerbcn said:
Is not normal what happens to you, but as a remote solution ... try to get into the applications that are working, and look at google services, there is one that spends a bestiality, it is called fileakintentoperation $ external that application next to the others Spend a lot of ram, I ended up blocking the services of google play and play store, and I assure you that the battery lasts for more than two days
Click to expand...
Click to collapse
Hi Rogerbcn,
thanks for replying.
Could you type the name of the app/service again? Google doesn't return anything on "fileakintentoperation" .
I already have the Google play and Play Store apps disabled, unfortunately, that didn't help.
Regards,
Sander

Is just below, where are the services of google play, and is also a service, but after reading that you have disconnected and you also have disconnected play store, gives me your battery or is badly calibrated or is to change, Take it to the sat of lenovo and assert your guarantee that for that we have spent 500 dollars / euros,regards

[rogerbcn] is probably correct and that you may have a defective battery. I use greenify and it seems to extend battery life about 23% for app hibernation.
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en

I resolved with task killer (kil 1 sec. After lockscreen)
edit: not resolved... anyone has other experience?

Seems to be resolved.
I used greenify, with doze go (adb solution)

Battery drain (Google account manager)

Let me start off by saying I was so happy with this phone and its battery life but the past couple of days I've seen it drain more than usual. Upon checking I see that Google account manager is responsible for this.
Anyone have an idea what caused this? and how to fix it?

i noticed the same on my chinese mate 9 however the % is below 40 still, from what I can see on my case is the google photos app causing all the noise I had disable synching over cellular data but haven't seen any improvement so far. I did that 2 days ago

Same here on my P10.
How many Google Accounts do you guys have linked? I currently have 4.

Raylow said:
Same here on my P10.
How many Google Accounts do you guys have linked? I currently have 4.
Click to expand...
Click to collapse
I have 2 on mine.

Raylow said:
Same here on my P10.
How many Google Accounts do you guys have linked? I currently have 4.
Click to expand...
Click to collapse
2 account

Thx for your replies guys!
Meanwhile I accidentally found out that this might be the process what is on other phones the Google Play Services.
I tapped on the Google Account Manager entry and scrolled down to the bottom of the next view and there it is..
Still I haven't seen the "Googl Account Manager" process ever before I assume that Huawei handles or at least displays the processes differently than others (at least Samsung) do.
For me it's a good thing since I see way more processes sucking battery than my SGS7 showed me.
Remembering the battery drain on my SGS7 the Google Play Services had pretty similar battery drain like the "mother process" Google Account Manager has on my P10.
So I think that's it
What do you guys think?

I have the same problem, lot's of times it's a Google calendar fail sync or Google fit fail sync because the system close it and when Google account has do a sync that's impossible because the apps are closed so I'm testing to not force closing Google apps. I will tell you my results
Sent from my HUAWEI MHA-L29 using XDA Labs

Use gsam battery monitor
I'm currently doing troubleshooting to find out why this is

virtyx said:
Use gsam battery monitor
I'm currently doing troubleshooting to find out why this is
Click to expand...
Click to collapse
Mine is the damn android OS. its using 33% average. no idea why latest update too

leo72793 said:
Mine is the damn android OS. its using 33% average. no idea why latest update too
Click to expand...
Click to collapse
its normal for android OS or android system to use battery
android OS is in respect to the kernel however.

virtyx said:
its normal for android OS or android system to use battery
android OS is in respect to the kernel however.
Click to expand...
Click to collapse
Still shouldn't use that much. Literally it's the most used one. One hour of screen use today and I'm down 25%
My Huawei watch is the only thing connected. No autosync no nothing. Used it minimally. My note 5 after last update and a reset lost maybe 6% all day. Android OS n kernel aren't an option. It's not on 7.0 tho

Does anyone have a solution for this? It is horrible since a few weeks (no update in the meantime, no other apps installed): Google Play Services (Google Account Manager) are very active, device gets hot, reboot helps for a short time, but almost every day I have a huge battery drain. Before the last weeks, this was not a problem at all, battery usage was super.
L29, B156

Hielko said:
Does anyone have a solution for this? It is horrible since a few weeks (no update in the meantime, no other apps installed): Google Play Services (Google Account Manager) are very active, device gets hot, reboot helps for a short time, but almost every day I have a huge battery drain. Before the last weeks, this was not a problem at all, battery usage was super.
L29, B156
Click to expand...
Click to collapse
Do you have developer options enabled?
I've had the same problem, after diasabling developer options it seems to be somewhat better but not really cured.
I also enabled in settings the automatic memory and data cleanup as I've found that cleaning all app caches helped for a short period of time.

I fixed my by doing factory reset. Now everything is back to normal.
Also before I had a problem that whatsapp didn't show messages if I didn't open up the app. This issue also got fixed the same time.

I'm suddenly having high consumption by media server - have no idea what it means and the phone is quite hot.

zayidhs said:
I'm suddenly having high consumption by media server - have no idea what it means and the phone is quite hot.
Click to expand...
Click to collapse
mediaserver can be due to listening or streaming music, or indexing music.
its fairly normal, however if your rooted you can disable it in an init.d script.
stop mediaserver works.
or
su -c pm disable mediaserver

virtyx said:
mediaserver can be due to listening or streaming music, or indexing music.
its fairly normal, however if your rooted you can disable it in an init.d script.
stop mediaserver works.
or
su -c pm disable mediaserver
Click to expand...
Click to collapse
Thanks, I've been listening to music all day. I'm not rooted so I guess I'll have to keep on with it.
Shut down for a while then restarted the phone and it's no more getting hot.

CandyAndy said:
I fixed my by doing factory reset. Now everything is back to normal.
Also before I had a problem that whatsapp didn't show messages if I didn't open up the app. This issue also got fixed the same time.
Click to expand...
Click to collapse
ive still got issues with android os using the most power. i only get 6-7 hours max screen time. i use my huawei watch via BT. latest update for the USA 183

Seems to be getting worse. Now I'm slated max 27 hours. WTF

in reality battery life never gets better. The constant discharge, and charge rates only put wear and tear on the battery. It would great to have the ability to swap batteries on the fly.
Sent from my MHA-L29 using Tapatalk

Insanely high alarms by "com.google.android.location.ALARM_WAKEUP_ACTIVITY _DETECTION"

Insanely high alarms by "com.google.android.location.ALARM_WAKEUP_ACTIVITY _DETECTION"
Hi there, I've been using OOS 9.0.2 and I got some excessive wakelocks by *walarm*:com.google.android.location.ALARM_WAKEUP_ACTIVITY_DETECTION which happens about every 60 seconds. I'm not sure if this is normal or what the culprit could be as the location services are deactivated all the time, yet it occurs. Any idea what it could be? Can it be related to Android Wear?

UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.

Macusercom said:
UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.
Click to expand...
Click to collapse
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods

spartan268 said:
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods
Click to expand...
Click to collapse
I wish I could say I simply used a wakelock detector or something like that. I loaded my apps to a secondary device and disabled them one by one. I wasn't sure whether Greenify would prevent it but it did. So greenifying different apps and see if it changes was how I figured it out.
My battery consumption during standby went significantly down. Even though alarms are just the triggers and not the wakelocks, triggering the Network Location Provider every 60 seconds prevents the device from deep sleeping and was a main cause of the standby issues. I suggest to check it for yourself with BetterBatteryStats.
My ALARM_WAKEUP_ACTIVITY_DETECTION exceeded 1000 alarms by the end of the day. While I still get a few Android Wear wakelocks if my smartwatch is not connected. They make up at least 150 too. What I'm trying to say is that I don't say you should have no alarms anymore, but even 150 seem normal for Google Play Services. But over 500 or 1000 definitely isn't normal.

I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.

oksagi said:
I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.
Click to expand...
Click to collapse
That's my point. Even with light doze active apps still have a maintenance window and Sleep as Android seems to have permanently used sensors via Play Services. Once greenified it stops using it completely and I went from 1.2%/h idle drain to under 0.7%/h or less. I'm just trying to help people who have the same issue as I do. If no app seems to use any sensor, location etc. you don't need Greenify of course. But it can help with some apps.