Related
hi everyone, recently i discovered huge battery drain on my note. when i fully charge it the battery drops from 100 to 80 percent in about 9 hours of standby. in order to find the culprit i installed better battery stats and let it run over night. i found out that something called networklocationlocator keeps my device from going into deep sleep (see attached screenshot).
does anyone know which app is behind this service? i think that its google now but i am not quite sure and dont want to uninstall it since its a really good app.
thanks in advance
Sent from my Note
probably when you go to settings and then location services, switch all off, switch back on only when you need it.
It would be interesting what is triggering your phone to seek location, could be a buggy app running silently updating every so often. I think the logs could tell you that. But not sure. I set location of in many apps in app settings cause I feel they dont need it.
I know that switching apps is buggy, It could be google maps running silently in background. Got to settings, apps running and stop those. Might need to stop as well in cached running.
I guess with root, and something like pdroid or lbe you can block apps requesting location services, also an option
Sent with a grin (^.^)
baz77 said:
probably when you go to settings and then location services, switch all off, switch back on only when you need it.
It would be interesting what is triggering your phone to seek location, could be a buggy app running silently updating every so often. I think the logs could tell you that. But not sure. I set location of in many apps in app settings cause I feel they dont need it.
I know that switching apps is buggy, It could be google maps running silently in background. Got to settings, apps running and stop those. Might need to stop as well in cached running.
I guess with root, and something like pdroid or lbe you can block apps requesting location services, also an option
Sent with a grin (^.^)
Click to expand...
Click to collapse
This is a 'bug' with google maps that has persisted for at least over a year now and it affects a lot of devices. Users have been complaining for the longest time and it seems like it's falling on deaf ears at google. It's a shame! There is NO acceptable 'fix' - turning off google locations services will get rid of this problem but again, as i said, that's not acceptable!
jknolls said:
This is a 'bug' with google maps that has persisted for at least over a year now and it affects a lot of devices. Users have been complaining for the longest time and it seems like it's falling on deaf ears at google. It's a shame! There is NO acceptable 'fix' - turning off google locations services will get rid of this problem but again, as i said, that's not acceptable!
Click to expand...
Click to collapse
I dont think its a bug affecting all roms. Nor that it has been there for over a year.
You've probably seen a ton of complaints on the bad battery life after KitKat upgrade. Google Services is seen at 90+% in battery stats, and the battery is discharging very quickly.
Factory reset is reported to cure the problem. Many are disabling Google Location services. There's also a workaround suggested by Sony, to disable backup and interest-based ads, or uninstall the latest Google Services.
[edit Jul-1-2014]
New Google Play Services 5.0 is now out, and its APK can be downloaded and installed just by searching for it in Google. It's reported to cure the problem for some, temporarily or permanently. It's recommended to try it first, before going with the suggestion below.
[previous post contents starting here]
However, there's no need to resort to the above, a much "lighter" solution may work. I've attempted it on my father's ZR and it worked.
Thanks to grim_ripper for mentioning steps that I forgot.
What needs to be done:
1. Go to Settings / Security / Device Administrators, disable Android Device Manager, if enabled.
2. Go to Settings / Apps, disable Google Play Services. It'll ask you to uninstall all updates, agree to it. After disabling it, some of other phone services might crash. Don't mind it.
3. This step might not be required according to the feedback from grim_ripper, however I'll list it "just in case": press "Clear data", or "Control data usage" and then "Clear all data". Make sure that in the Google Play Services app page, it's listed as disabled and has 0kB data usage.
4. Re-enable Google Play Services. Hangouts will immediately ask for its upgrade, get into Google Play Store and upgrade it.
5. Reboot the phone. You should see no crashes at this point.
6. In case you want Android Device Manager to function - go to Settings / Security / Device Administrators and enable it.
That's it, Google Play Services battery usage will be back to normal, and battery life seems even improved over JellyBean.
[edit Jul-13-2014]
The fix might stick for some, and some will find the battery drain coming back after several days. I'm over a month with it, and everything is still fine. However, the results are mixed.
Jack_R1 said:
You've probably seen a ton of complaints on the bad battery life after KitKat upgrade. Google Services is seen at 90+% in battery stats, and the battery is discharging very quickly.
Factory reset is reported to cure the problem. Many are disabling Google Location services. There's also a workaround suggested by Sony, to disable backup and interest-based ads, or uninstall the latest Google Services.
However, there's no need to resort to the above, a much "lighter" solution may work. I've attempted it on my father's ZR and it worked.
What needs to be done:
1. Go to Settings / Apps, disable Google Play Services. It'll ask you to uninstall all updates, agree to it. After disabling it, some of other phone services might crash. Don't mind it.
2. Press "Clear data", or "Control data usage" and then "Clear all data". Make sure that in the app page, it's listed as disabled and has 0kB data usage.
3. Re-enable Google Play Services. Hangouts will immediately ask for its upgrade, get into Google Play Store and upgrade it.
4. Reboot the phone. You should see no crashes at this point.
That's it, Google Play Services battery usage will be back to normal, and battery life seems even improved over JellyBean.
Click to expand...
Click to collapse
I confirm that this works, I didn't even clear data.Just disabled android device manager, uninstall google play services, enabled android device manager, re-install play services and finally reboot
Thank you, I completely forgot about Android Device Manager blocking the app disable. With your permission, I'll update the instructions.
I have just tried that thing you posted, will see how the results are in a few days.
One thing I noticed after upgrading to KK is night time for about 8 hours the battery drains 10% while in JB 4.3 it drains about 20% or more.
But the usage draining is similar to JB in KK. Will see if this thing works. Don't like to go to barebones CM11 cause I will be missing on the many features of the phone.
Let's see
It s working here too!
At first, I didn't even thought I had a problem but I looked in the processes and saw this f... Google service running.
Now my batterie last even better than when I was on 4.3.
Thanks
Jack_R1 said:
Thank you, I completely forgot about Android Device Manager blocking the app disable. With your permission, I'll update the instructions.
Click to expand...
Click to collapse
No Problem. I found out that this method only works as long as you don't reboot the phone after the fix, otherwise you'll need to do the whole process again. Mine went well until I waited till my battery was fully discharged before charging, hence forcing a reboot which play services started misbehaving again
I just realized a new battery drain problem, the Xperia social services keeps draining my problem
grim_ripper said:
I just realized a new battery drain problem, the Xperia social services keeps draining my problem
Click to expand...
Click to collapse
Oh yes, I have all these disabled. Perhaps this is why I had to restart the phone a couple of times already (changing SIM cards back and forth), and the original Google Services problem didn't come back.
Jack_R1 said:
You've probably seen a ton of complaints on the bad battery life after KitKat upgrade. Google Services is seen at 90+% in battery stats, and the battery is discharging very quickly.
Factory reset is reported to cure the problem. Many are disabling Google Location services. There's also a workaround suggested by Sony, to disable backup and interest-based ads, or uninstall the latest Google Services.
However, there's no need to resort to the above, a much "lighter" solution may work. I've attempted it on my father's ZR and it worked.
Thanks to grim_ripper for mentioning steps that I forgot.
What needs to be done:
1. Go to Settings / Security / Device Administrators, disable Android Device Manager, if enabled.
2. Go to Settings / Apps, disable Google Play Services. It'll ask you to uninstall all updates, agree to it. After disabling it, some of other phone services might crash. Don't mind it.
3. This step might not be required according to the feedback from grim_ripper, however I'll list it "just in case": press "Clear data", or "Control data usage" and then "Clear all data". Make sure that in the Google Play Services app page, it's listed as disabled and has 0kB data usage.
4. Re-enable Google Play Services. Hangouts will immediately ask for its upgrade, get into Google Play Store and upgrade it.
5. Reboot the phone. You should see no crashes at this point.
6. In case you want Android Device Manager to function - go to Settings / Security / Device Administrators and enable it.
That's it, Google Play Services battery usage will be back to normal, and battery life seems even improved over JellyBean.
Click to expand...
Click to collapse
I confirm that it works. At least for a week or so - after that the GogglePlayServices problem appeared again....
Dont helps in my case too.
At first it seems that it works, but after a day the google services are again over 75 prozent or so.
Thinking of going back to 4.3 or hoping that a fix will come soon.
Is it necessary to factory reset after update to kit kat to encounter the battery drain problem?
I had these problems and the only save cure is to disable the location services. Some times you would think a solution helps but stucked with an empty Phone suddely is a bad thing.
Sent from my C5503 using XDA Premium 4 mobile app
Is something known of a fix from Google for the google services?
I ask cause since yesterday evening the akku works normal in my case. Dont see the google services as first in line of accu consumption like before. Seems that everything works fine again.
Lemmi1 said:
Is something known of a fix from Google for the google services?
I ask cause since yesterday evening the akku works normal in my case. Dont see the google services as first in line of accu consumption like before. Seems that everything works fine again.
Click to expand...
Click to collapse
After I disabled the location service I see the android system in the second line. And the google services almost at the bottom line. The battery usage still not very good.
Been through several reboots by now, everything enabled, location is used, the problem didn't return, on both mine and my father's phones.
The only thing worth noting is my phone configuration - not rooted, STAMINA mode disabled, Low battery mode disabled, Queue background data disabled, Location-based WiFi enabled.
Waiting patiently for the next Sony update.
OK, the method seems to be obvious.
Does it need to be repeated after every reboot?
I also do not understand why installing the latest Google Play (after removing it the way it is written here) is not bringing the problem back .
Thanks anyway.
By the looks of it, the issue might be caused by user data being present already in Google Services since before the KitKat upgrade, but this is some type of data that's not necessarily present once it's deleted. Maybe some sort of duplication / overloading of data from multiple places, and this changes the order of loading.
one word: AMAZING
after this all the lagging of UI and keyboard is removed.
I was intending to install CM11, but after this fix I think I will stay with stock ROM
Ok this worked well for a couple of days including the UI lag fix but now Play services is destroying my battery again. I'm fed up with my ZR (Bluetooth issues and all) Just ordered a Nexus 5 yay!
Sent from my C5502 using Tapatalk 2
New Google Play Services 5.0 is out, if it didn't reach you yet - you can install it. It stops the battery drain.
Hi all,
I just installed cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip and I have a big problem with SystemUpdateService which is always on and draining my battery. The phone will not go in deep sleep, it will just stay awake.
I tried all of the following:
1. Installed Disable Service and went on to disable SystemUpdateService, but it was already disabled.
2. Installed Autorun Manager and went on to disable com.google.android.gsf.update.SystemUpdateService$Receiver. but it was already disabled
3. I copied FOTAkill.apk in the System folder with RS Root Explorer and restarted, but the problem kept persisting
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Does anybody know what else I could do?
keeekeeess said:
Hi all,
I just installed cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip and I have a big problem with SystemUpdateService which is always on and draining my battery. The phone will not go in deep sleep, it will just stay awake.
I tried all of the following:
1. Installed Disable Service and went on to disable SystemUpdateService, but it was already disabled.
2. Installed Autorun Manager and went on to disable com.google.android.gsf.update.SystemUpdateService$Receiver. but it was already disabled
3. I copied FOTAkill.apk in the System folder with RS Root Explorer and restarted, but the problem kept persisting
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Does anybody know what else I could do?
Click to expand...
Click to collapse
I installed (cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip) on my device
and i am not found this problem?
try wakelock detector to see what's keeping it awake http://forum.xda-developers.com/showthread.php?t=2179651
Starting today, I got this issue as well on a Nexus 4 device running the M7 snapshot with hellscore kernel. The first 2 steps you took didn't work for me too. Didn't know about #3 this far.
keeekeeess said:
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Click to expand...
Click to collapse
Doesn't sound pretty, but how did you do this? Still better than running out of battery halfway through the day, I'd guess.
pryerlee: WLD says exactly that - Google Play Services -> SystemUpdateService, for me currently 4h23m, being 100% of the time - plus it says "x2" (what's that precisely?)
not sure if this will help but read tho the post http://forum.xda-developers.com/showthread.php?t=2388243 http://forum.xda-developers.com/showthread.php?t=2378962
it is not work this servicein with lock screen!!
(i speek arabic good but english not good)
Sent from my GT-I9000 using XDA Free mobile app
pryerlee: Couldn't make anything out of those.
Just linking the other way round as well, maybe it'll help - the issue popped up on CM forums too: http ://forum.cyanogenmod. com/topic/96459-systemupdateservice-wakelock-on-cm11-m7-massive-battery-drain/
(sry for destroying the link, I'm blocked from posting it.)
pryerlee said:
not sure if this will help but read tho the post http://forum.xda-developers.com/showthread.php?t=2388243 http://forum.xda-developers.com/showthread.php?t=2378962
Click to expand...
Click to collapse
I did all of the options, the service is closed yet it was still running.
I compromised and installed Paranoid Android 4.4.2 and the problem is no more.
So just trying stuff without any deeper thoughts, I just did two things, locked the phone afterwards and now the wakelock seems to be gone:
1. I enabled SystemUpdateService using Disable Service App, which had already been disabled when we first looked.
2. I looked into the CM update function, where - having selected all stable releases - nothing was showing and refreshing didn't work. Got the idea to look into Disable Service App again, and found that UpdateCheckService of CyanogenMod-Updater was disabled. Enabled it, refreshed CM updater, got a list of stable releases.
My beginner's guess would be #1 did it - but why was #2 even an issue in the first place?
Running CM 11 M7 Snapshot 6/9/14 msm8960 on Motorola Atrix HD MB886. Have seen something similar.
Details:
- Have not seen this issue for weeks of running this ROM until now.
- This seems to have started a few (2?) days ago after an update. Google Play Music, Maps, Search, Drive, Sheets, and Docs all received updates in the past week.
- Typically, based on the configuration and usage of my phone, when the screen on is off the phone is in Deep Sleep (percentage in high 90s).
- At some point after some app or service is run, the phone stops going into deep sleep.
- Better Battery Stats shows SystemUpdateService as having partial wakelock for about the same percentage of time that the phone should be in deep sleep (high 90s).
- SystemUpdateServices does not seem to be hogging battery even considering that it might be folded into another category, but the wakelock causes the phone to use battery more than twice as fast as in deep sleep.
- A restart clears it up until the SystemUpdateService is invoked again by... whatever... seems to be something I do manually - still chasing it.
IronTechmonkey,
confirming your descriptions, up to the point where you describe that a reboot clears the issue up until a certain unknown event some time after boot. This is clearly not the case for me.
Instead, I was just able to reproduce the behaviour I described above. The wakelock remained gone since my last post, then I had to reboot for another reason, and it was there again basically from the first second (100% awake time since boot). Looking into Disable Service, SystemUpdateService was unchecked / disabled - again I checked / enabled it, and the wakelock stopped immediately.
Silkeyway said:
IronTechmonkey,
confirming your descriptions, up to the point where you describe that a reboot clears the issue up until a certain unknown event some time after boot. This is clearly not the case for me.
Instead, I was just able to reproduce the behaviour I described above. The wakelock remained gone since my last post, then I had to reboot for another reason, and it was there again basically from the first second (100% awake time since boot). Looking into Disable Service, SystemUpdateService was unchecked / disabled - again I checked / enabled it, and the wakelock stopped immediately.
Click to expand...
Click to collapse
I've been able to consistently replicate the problem 100% by running the Google Play app when the phone has a data connection.
If I run the Google Play app when the phone has no data connection the problem does not occur until the next time the phone has a data connection, whether or not Google Play is running.
I do have all auto-updating disabled in google and elsewhere which makes this easier to chase.
See if it happens when your phone has no data connection, with apps and google things set not to autoupdate.
As for the temporary fix: Like you said: Disable Service app, System Apps list, Google Play Services, SystemUpdateService enable/disable.
I'll try with those conditions asap. No time just now.
However, doesn't this all raise the question why SystemUpdateService is disabled? Shouldn't this default to enabled?
Or to put it differently: Is enabling SystemUpdateService a workaround, or is it being disabled the issue?
I also had the wakelock on my P990.
systemupdateservice was disabled in gooogle service framework, but it was still active as receiver and actice receiver in google play services - disabling it there solved the wakelock for me.
Silkeyway said:
I'll try with those conditions asap. No time just now.
However, doesn't this all raise the question why SystemUpdateService is disabled? Shouldn't this default to enabled?
Or to put it differently: Is enabling SystemUpdateService a workaround, or is it being disabled the issue?
Click to expand...
Click to collapse
Now that I've tested during a work day I'm seeing the problem occur more pervasively as some of you are
- It starts any time I go on line.
- Reboot sometimes but not always fixes
- Toggling using Disable Service app no longer works reliably
- Must stop Google Services Framework to fix issue until next time I go on line
= Royal PITA!
As for your question; It is not uncommon in the world of computers (and phones) to have to toggle a setting on/off or off/on to get the setting to stick, especially when something deeper in the system is turning it on and off without a flag letting the user know.
Just summarizing what was found on the CM forums where I tried to link previously:
Seemingly permanent workaround: http://forum.xda-developers.com/showpost.php?p=53739230&postcount=5031
Related fix, merged into nightly since Jun 29: http://review.cyanogenmod.org/#/c/66894/
Haven't tried that workaround, had no time to go for the nightly... hopefully the fix will already be included in the M8 stable release(?).
Silkeyway said:
... hopefully the fix will already be included in the M8 stable release(?).
Click to expand...
Click to collapse
Indeed hoping the same, and it looks like M8 and the nightly to which you refer will not yet be using the KK bootloader (great for my old Moto AtrixHD MB886 w/JB bootloader). Found that same XDA post referring to Autorun Manager which looks like a good temporary fix - working good so far. Does not hold setting through restart but still more effective than others..
I've the same issue here since 2/3 days on my 9001 running CyanogenMod 11.0 by ADC-Team - Release 8, maybe it was some app update occurred recently... I didn't have any issue with the same rom before.
---------- Post added at 10:29 AM ---------- Previous post was at 10:00 AM ----------
I can confirm that downgrading Google Play Services to version 4.3.25 is a working workaround.
http://forum.xda-developers.com/showpost.php?p=53851739&postcount=3026
Silkeyway said:
Just summarizing what was found on the CM forums where I tried to link previously:
Seemingly permanent workaround: http://forum.xda-developers.com/showpost.php?p=53739230&postcount=5031
Related fix, merged into nightly since Jun 29: http://review.cyanogenmod.org/#/c/66894/
Haven't tried that workaround, had no time to go for the nightly... hopefully the fix will already be included in the M8 stable release(?).
Click to expand...
Click to collapse
Hey everyone,
i can confirm the issue for CM11 M7 and it all started with the recent update to Google Play Services 5 v84.
The workaround mentioned before works very well until a reboot ... lets hope the best for CM11 M8!
Best workaround I've found:
"Finally I was able to block the SystemUpdateService wakelock, using this app:
https://play.google.com/store/apps/d...com.rs.autorun
go to settings, enable the option to show system entries
find google play services and disable:
SystemUpdateService$Receiver
SystemUpdateService$ActiveReceiver
SystemUpdateService$SecretCodeReceiver
done... no more wakelock and it didn't break anything, syncs all work ok
I know this app doesn't look the best, but I tried others like "Android Tuner Free", "Disable Services", "Gemini App Manager", etc, but they allowed me to only disable the main service and didn't show the other receivers that had to be disabled."
As the other user said, this is all caused by the Google Play Services update that has being rolling out this last week. The solution above is reboot proof (At least for me). Thanks to the user who posted it.
Anyone have this wake lock?
It's called
wake:com.google.android.gms/.auth.be.proximity.authorization.userpresence.UserPresenceService
pham818 said:
Anyone have this wake lock? I have it on stock rom and firekat rom.
It's called
wake:com.google.android.gms/.auth.be.proximity.authorization.userpresence.UserPresenceService
Click to expand...
Click to collapse
I also have this high count wakelock on my Note 4 running stock Kit Kat 4.4.4. I cannot figure out how to get rid of it. I tried disabling services that I think are causing it but no luck so far.
Upon researching, I'm finding it has to with Android Wear detection, but I cannot find any process or service that is related to it under Application Manager.
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
MrBrady said:
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
Click to expand...
Click to collapse
you just in reality not really said nor showed us your problem. ok, battery drain.. i have that. my battery drains when i use my phone.. understand? give us some more info, screenshots, etc.
simms22 said:
you just in reality not really said nor showed us your problem. ok, battery drain.. i have that. my battery drains when i use my phone.. understand? give us some more info, screenshots, etc.
Click to expand...
Click to collapse
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
MrBrady said:
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
Click to expand...
Click to collapse
Looks similar to an issue I had, turned out it was an issue that Google play services was having trouble with system update feature. It started when I switch from stock to Pure Nexus rom the rom, and many others, does something to disable the update button in the settings app but in some cases Google Play Services holds a wakelock for it for some reason or another. The way I fixed it was wiping Google play services and uninstalling its updates and letting it start fresh. Also if you have the app "GasBuddy" installed it causes a bluetooth wakelock, it only shows up in kernel wakelocks as "bluesleep," looking for beacons at gas stations to send you ads.
StykerB said:
Looks similar to an issue I had, turned out it was an issue that Google play services was having trouble with system update feature. It started when I switch from stock to Pure Nexus rom the rom, and many others, does something to disable the update button in the settings app but in some cases Google Play Services holds a wakelock for it for some reason or another. The way I fixed it was wiping Google play services and uninstalling its updates and letting it start fresh. Also if you have the app "GasBuddy" installed it causes a bluetooth wakelock, it only shows up in kernel wakelocks as "bluesleep," looking for beacons at gas stations to send you ads.
Click to expand...
Click to collapse
Thanks for the tip. No Gasbuddy installed. A few weeks back I had FiveStars installed (a purchasing points app) and it caused a huge Bluetooth wakelock. But that was removed a while ago and didn't affect Google Play Services.
MrBrady said:
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
Click to expand...
Click to collapse
looks like its google play services updating itself or something. that happens every once in a while. best thing to do is to leave it alone for a day or two and it should "fix" itself after. but in a day or two, check your battery again just to make sure.
simms22 said:
looks like its google play services updating itself or something. that happens every once in a while. best thing to do is to leave it alone for a day or two and it should "fix" itself after. but in a day or two, check your battery again just to make sure.
Click to expand...
Click to collapse
Yeah, I think you're right.
Sent from my Nexus 6 using XDA Labs
MrBrady said:
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
Click to expand...
Click to collapse
There is an app in the playstore called 'Disable services.
You can disable the services you don't use/need.
In case anyone has this same issue, I think I found the problem and solution. The latest version of Google Play Services causes a massive wakelock on ROMs that are blocking system update checks.
Using the DisableService app I enabled the update service and the wakelock has disappeared.
Sent from my Nexus 6 using XDA Labs
MrBrady said:
In case anyone has this same issue, I think I found the problem and solution. The latest version of Google Play Services causes a massive wakelock on ROMs that are blocking system update checks.
Using the DisableService app I enabled the update service and the wakelock has disappeared.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I've noticed the GPS wakelock using GPS on my N5, my wife's N5X, and a buddy's 6P as well. Did you enable systemupdateservice in only Google Play Services or both GPS and Google Services Framework? Both were disabled for me... Thanks in advance!
kornball said:
I've noticed the GPS wakelock using GPS on my N5, my wife's N5X, and a buddy's 6P as well. Did you enable systemupdateservice in only Google Play Services or both GPS and Google Services Framework? Both were disabled for me... Thanks in advance!
Click to expand...
Click to collapse
Just Google Play Services. I didn't think of looking in GS Framework.
Sent from my Nexus 6 using XDA Labs