Team - I am running the latest version of greenify posted on the playstore. I've followed guides for enabling agressive doze on android 6.0 on my moto x pure (non root) -- including adbing to the device to grant permissions on the app. It seems to be working most of the time. The device seems to go to sleep and i've seen a great increase in battery. However, seemingly randomly i'll notice battery draining fast. When i look at my usage its google play services keeping the device awake 100% of the time. If i reboot the phone, google play services stops doing that and all is well for awhile, till it repeats. I've been unable to find the cause of this. I imagine i'm missing some information that we might need to track this down. thanks in advance!
tange1 said:
Team - I am running the latest version of greenify posted on the playstore. I've followed guides for enabling agressive doze on android 6.0 on my moto x pure (non root) -- including adbing to the device to grant permissions on the app. It seems to be working most of the time. The device seems to go to sleep and i've seen a great increase in battery. However, seemingly randomly i'll notice battery draining fast. When i look at my usage its google play services keeping the device awake 100% of the time. If i reboot the phone, google play services stops doing that and all is well for awhile, till it repeats. I've been unable to find the cause of this. I imagine i'm missing some information that we might need to track this down. thanks in advance!
Click to expand...
Click to collapse
That may not have anything to do with Greenify unless you have greenified Play Services. If you have, remove it from hibernation.
Usually Play Services will go berserk upon updating itself in the background. What you can try is clear it's data and cache and reboot. If you have TWRP, do it in recovery. If not, do it in Settings>Apps.
tnsmani said:
That may not have anything to do with Greenify unless you have greenified Play Services. If you have, remove it from hibernation.
Usually Play Services will go berserk upon updating itself in the background. What you can try is clear it's data and cache and reboot. If you have TWRP, do it in recovery. If not, do it in Settings>Apps.
Click to expand...
Click to collapse
Thanks for the info. Here's what i've done:
I removed greenify, performed the actions you suggested and left greenify off for about 12 hours. No issues with google play services and keep awake. I reinstalled greenify and everything was good for a number of hours. Unfortunately the play services keep awake started again about 3.5 hours ago. The phone has a solid 'awake' bar in battery settings and play services is the culprit with 3.5 hours awake. While i dont blame greenify, there's some sort of correlation of events here that I can't explain.
tange1 said:
Thanks for the info. Here's what i've done:
I removed greenify, performed the actions you suggested and left greenify off for about 12 hours. No issues with google play services and keep awake. I reinstalled greenify and everything was good for a number of hours. Unfortunately the play services keep awake started again about 3.5 hours ago. The phone has a solid 'awake' bar in battery settings and play services is the culprit with 3.5 hours awake. While i dont blame greenify, there's some sort of correlation of events here that I can't explain.
Click to expand...
Click to collapse
Do you have Xposed? If so, install AppOpsXposed and untick the "Keep Awake" function of Play Services. Another thing you can try is uninstalling the update to the Play Services, reboot and then manually update it and again reboot.
If it is still not arrested, Google is your friend.
Unfortunately I've the same problem on my OnePlus 2 with stock ROM. I've installed Greenify two days ago, and enabled aggressive doze with amazing results! Last night I enabled Doze on the Go (using ADB) and since unplugging my phone this morning there is this constant wakelock of Google Play Services. Disabling Doze on the Go as well as reinstalling Greenify didn't help. Looking forward to a solution!
This is a known problem. Sometimes it's worse and sometimes less, but Google Play Services is a known offender in this manner. And Google processes in general. Part of the reason for this is that Google often wakes up your device, periodically, to track your location (horrible, yes, and it continued to happen for me even when all Google location options I could find, as well as GPS, were turned off).
Solutions that have reportedly worked for some people in the past (try one at a time or all of them) - they don't require root:
-Make sure you do not Greenify/freeze/hibernate Google Play Services, or similar processes, as this may make the issue worse.
-Clear cache and data of Google Play Services.
-Manually update Google Play Services to latest APK version available from your device, downloaded from the web. Make sure you select the right version for you. http://www.apkmirror.com/apk/google-inc/google-play-services
-Try turning off as many Google background features as you can, such as location tracking/history, etc.
I guess some of these steps may only work after the next reboot, so reboot the device when you're done.
But as I said, this process is a known big offender. The above may not work, or may work temporarily. The stronger and more permanent solutions require root (you don't really need to try the above options if you do these). The more of them you do, the less 'keep awake' you should experience:
-Install Xposed Installer app and install Xposed Framework, so you can use the modules mentioned below...
-Use AppOpsXposed module (or CM Privacy Guard if you have it) to deny keep awake permission to Google Play Services, and other Google background apps.
-This is a big one: Install Amplify (Xposed module) from the Play Store, and it will automatically take care of limiting Google wakelocks. That's it. If you pay for the pro version, then you can additionally tweak and limit all wakelocks, alarms and services on your device (pretty cool and useful, but more involved, so for advanced users).
Cultar said:
..............
-This is a big one: Install Amplify (Xposed module) from the Play Store, and it will automatically take care of limiting Google wakelocks. That's it. If you pay for the pro version, then you can additionally tweak and limit all wakelocks, alarms and services on your device (pretty cool and useful, but more involved, so for advanced users).
Click to expand...
Click to collapse
The unpaid version of Amplify will block a maximum of a couple of wakelocks related to location. Only the pro version is capable of blocking other wakelocks and alarms including those of Play Services. But as you said, it is not automatic and you will have to set it up.
Any updates on this?
Google play services is awful
MSK1 said:
Any updates on this?
Google play services is awful
Click to expand...
Click to collapse
Not a Greenify issue. Some devices/ROMs/configs seem more susceptible to GPS runaway. Clearing GPS cache+data on occasion followed by an immediate reboot has proven helpful for some. Good luck.
Related
For a few days now I've noticed a massive battery drain of Google maps, up to 60 per cent of the battery use, without evening opening the app (must have been running in the background). I have temporarily disabled the app on my phone, but am I the only person with this problem?
stevennekens said:
For a few days now I've noticed a massive battery drain of Google maps, up to 60 per cent of the battery use, without evening opening the app (must have been running in the background). I have temporarily disabled the app on my phone, but am I the only person with this problem?
Click to expand...
Click to collapse
Make sure the "Location reporting" (in Google Maps settings) is disabled if you don't want the battery drain. Moreover, Google Now activates the Location reporting so you might have to disable Google Now as well...
P.s: this post should be in Q&A section, doesn't it ?
vakbrain said:
Make sure the "Location reporting" (in Google Maps settings) is disabled if you don't want the battery drain. Moreover, Google Now activates the Location reporting so you might have to disable Google Now as well...
P.s: this post should be in Q&A section, doesn't it ?
Click to expand...
Click to collapse
I have google now disabled all the time, and the location reporting was unchecked too.. Besides that, even if that had been activated, it shouldn't have taken 60% of my total battery (I had about 70% of my total battery left when I noticed it today), should it?
(...and yes, this one should be in the Q&A section, hadn't thought about that when I posted it though...)
I had the same issue. I turned all location reporting off and turned off Google now, also made sure GPS was off. All that helped a fair amount but Maps still kept running in the background even though I'd never used the app. In the end I used an app called Greenify to hibernate maps and a bunch of other background apps and it made a world of difference. Use wakelock detector to see which apps are causing wakelocks and disable any you don't need running.
Wyman Gibuil
use an extension car battery so it can add battery life even for month, just make sure you will get the same voltage
Its coz of google location services bug that HTC phones are having after the update.
If you are interested about it: http://www.androidpolice.com/2013/0...ssues-for-htc-owners-google-working-on-a-fix/
In short:
Only location service thats working if you have this bug, is gps. Rest of locations services (wifi, mobile newtwork etc.) wont work.
Who couses it? - latest updates for google services.
How to fix it? - atm google is working on fix. There is some type of user fixes you can try. (see post).
Hope it explains your drain. I have this bu and i get this unusual drain from maps too.
Hi
First of all thank you Oasis for creating a tool to fix things that shouldn't be broken to begin with! You are an example for a lot of developers :good:
I've read the first couple of posts on the original thread but I still have a few things that are not clear..
The advice of Oasis himself is too hibernate only those apps that misbehave. He states that hibernating apps will also remove them from the memory, which will come with a performance/cpu usage penalty when you want to use them again.
In the video tutorial however Josh greenifies almost every application that doesn't need push notifications.
So this would mean that when I use an application that doesn't have notifications but I open frequently, for example Nu.nl, a dutch newsapp, it will always have to reload the app from scratch instead of loading it from memory?
So baically the best way to use Greenify would be to NOT just greenify most apps, but to use the analyzer frequently and see what's running in the background and greenify those that don't depend on notifications?
Then newsapps that don't push news, image viewers, file managers, system tools like SD Maid and simple games that don't use internet should be ok not being greenified?
Is there no big list available of apps that misbehave or are safe to keep de-greenified?
Thanks in advance for any help on this.
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
marchrius said:
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
Click to expand...
Click to collapse
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
latino147 said:
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
Click to expand...
Click to collapse
"Disable Service" (and "Autostarts") from play store.
marchrius said:
"Disable Service" (and "Autostarts") from play store.
Click to expand...
Click to collapse
Ah, I believed those were two functions withing Greenify I couldn't find
wtf, FB has 62! services! None of them where active though, until you open the app, then it was 3.
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
The only issue with this second method being that you don't always really know what these services do.
latino147 said:
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
Click to expand...
Click to collapse
Exactly. Take google play services for example. If you greenify it, you'll lose gcm and other functions and that's not advisable at all (in fact greenify hides it). But with disable service (and autostarts/system tuner)you can choose what to disable while still mantaining gcm, location services (when needed), sync etc. I can' remember what I did in system tuner regarding gplay services (I followed some tutorial), but with disable service I disabled analyticsservice (this one will reactivate itself unless you do some tweak with system tuner), refreshenabledstateservice, playlogreportingservice, googlehttpservice, playlogbrokerservice, adrequestbrokerservice, gcmschedulerwakeupservice, advertisingidservice, adsmeasurementservice, locationwearablelistenerservice, nlplocationreceiverservice, geocodeservice, dispatchingservice and playlogservice. A reboot is needed. Haven't lost a single function since weeks (gcm, location, autosync and every google app in general are working 100% fine).
Same story with play store. Apps wake it very often, so greenify it does more harm than good. Instead, you can disable pendingnotificationsservice, contentsyncservice and dailyhygiene (and will still be fully functional).
Of course these are little tips to increase performance and battery life even more. I use greenify for 90% and more of apps that "misbehave" and disable service/autostarts/system tuner for the remaining 10% "misbehaving" apps. However, an app "fixed" with such methods will stay cached while with greenify is completely closed (resulting in more cpu/time/battery consumption when loaded again).
The only issue with this second method being that you don't always really know what these services do.
Click to expand...
Click to collapse
Like I already said, for general purposes you'd better simply greenify the "misbehaving" apps. If you use it/it is woken very often, you can consider these methods.
Yes, it's a "trial and error" thing. Unless you're disabling services with self-explainatory names such as "pushservice".
Never installed Facebook official app but I heard many times that is a notorious hogger and takes many personal datas too, for which you can look for xprivacy xposed module as well.
I'll start experimenting with it today :good:
With my phone largely idle, Google Play Services is consuming 40-50% of the power and seems to be stopping the phone sleeping. The net_scheduler wakelock is the biggest culprit causing up to around 800,000 wakelocks in a day. It got to the point where I couldn't get through a day of minimal usage without recharging during the afternoon. I don't use Google+, I have turned off location services and disabled Google books, movies, games, search and google+ apps. I still have sync enabled for Google apps data, calendar, chrome, contacts, gmail and internet but I have disabled sync for drive, Fit data, people and picasa which I don't use anyway.
The problem was worse when I was using Exchange Services to sync with my work email and calendar. Turning off email sync helped a bit but Google Play Services activity still seemed to ramp up and stay high when I had a calendar appointment in Outlook, even with the sync period set to manual. So I have now removed the Exchange account completely.
I am aware that Exchange Services seems to be a common problem, something to do with the version of the Exchange server? Anyway that is not within my control. The serious battery drain started maybe 4 weeks ago and Exchange Services was responsible for most of it. Having eliminated that, its now Google Play, which also seems to be a common problem but usually NlpWakeLock? My phone is currently showing it has been kept awake 1h51m by Google Play Services since this morning, and 1h39m of that is net_scheduler (435409 wakelocks). GSam battery monitor shows almost continuous background activity even when I am not using the phone. The highest battery usage per app is by Google Play Services at 27%, the next highest is Kernel at 9%.
The battery drain seems to be worse when I am at work, where the signal is poor and I am on wifi but that has always been the case. I also use wifi at home. I turn off mobile data while at work to try and reduce battery usage. Other than changes to reduce battery drain I haven't changed anything on my phone for ages and I haven't updated or installed anything new, although I think Google Play automatically updated itself a few weeks ago.
What is net_scheduler and how do I stop it or Google Play killing my battery?
stock Samsung Galaxy S3 LTE, not rooted, on T-mobile
Android 4.3
New battery less than a year ago.
Someone please answer your... I am having the same issue and it is riculous. On one plus oxygen.
I am having the exact same problem. 28929 wakelocks for *net_scheduler*
Thank you in advance for anyone's help!
Custom Samsung Note 3 Rom 4.4.2
Me too, pls help us to solve this problem. Thanks.
its my problem too , fk my battery ! plz help ...
Same problem. Recently, battery has been draining crazy fast in standby. Wakelock detector shows this net scheduler causing 263,000 wakelocks over only 4 hours standby and lost about 25% battery doing nothing. Android 4.3 on sony xperia sp.
Using OS monitor app, Android system and google services framework are consuming 60% cpu power when phone is just idle.
Google are a bunch of idiots.
---------- Post added at 02:02 PM ---------- Previous post was at 01:38 PM ----------
To fix, find Google Services Framework and clear data and cache. Instantly fixed the problem. CPU usage by Android system and Google framework dropped to 0 and wakelocks have stopped increasing.
I highly recommend the app OS monitor, let's you put a permanent notification which shows top 3 things consuming cpu power.
Before Clearing Framework (this was non-stop, even restarting didn't help)
After
problem has returned, google, you suck.
Hi, I have the same issue like you. I disabled some services of google play services and I was thinking that that was the reason of wakelock *net_scheduler*, but it isn't, because I flashed new ROM with all services enabled but *net_scheduler* is draining my battery again. Its strange that is showing it randomly, I mean some day I don't have that wakelock and the next day I have it. Really strange.
If anyone knows more about it please answer.
Hey,
I have the same issue. Since the last GPS update wont even last a day. I found also that the GPS are responsible and in my case its also the *net_scheduler* service. It is pretty active. I already tried a few things from here: http://forum.xda-developers.com/showthread.php?t=2357417
But so far nothing helped. It drains the battery really fast, yesterday my battery went from 50% to 30% in 20 min. That sucks.
If someone found a fix please post it here
Tried uninstalling google play services update, everything fine. Then updated it via play store and within a few minutes of update noticed phone was getting hot and laggy again. Same issue, something is going on with google play services causing massive wakelocks and high cpu usage. Currently at 1.4 million net_scheduler wakelocks in past 18 hours. Had to recharge twice even though phone barely used.
For no obvious reason, since yesterday I don't appear to be having the problem with Google Play Services any more. I haven't done anything to the phone, I am in the same location, nothing has changed on my end as far as I know unless I have inadvertently done or not done something that I normally do or don't do. In any case the problem appears to have gone away, or maybe it is just dormant waiting to drain my battery when I least expect it...
Something broken on the Google servers that they have now fixed?
Yep its fixed itself, there was an update on 18th June. The version with problems was 7.5.71 now its 7.5.74
Used my phone without google play services for a day and it actually doesn't affect much. You can still use play store, chrome but most other google apps won't work. Snaptube can be used as youtube replacement. If you can live without hangouts,gmail etc I'd recommend just removing it completely, save any future headaches.
Hmmm... I still have Google Play Services 7.5.71. Strangely Google Play Store says it has no connection, even though I am on wifi and other apps can connect fine. Maybe that's why it hasn't been able to hammer my battery?
What is the relationship, if any, between GP Services and GP Store?
spencetj said:
Hmmm... I still have Google Play Services 7.5.71. Strangely Google Play Store says it has no connection, even though I am on wifi and other apps can connect fine. Maybe that's why it hasn't been able to hammer my battery?
What is the relationship, if any, between GP Services and GP Store?
Click to expand...
Click to collapse
I got the no connection on play store after clearing google framework cache. Had to reboot phone to fix it. Could be why the issue has stopped for you as I noticed it did too after clearing framework at first.
Completely uninstall google play services, it will reset to factory default. Re-enable it and launch a google app such as youtube. It will prompt you to update and bring you to google play services page on play store where latest version will be downloaded.
Google Play Services updated itself over the weekend to 7.5.74, lets hope this one fixes the battery drain for me. I never get any option to update or not, the only reason I know it updated is because I have an app that automatically backup up any app that gets installed, so I can revert to the previous version if an update causes problems. I did try reverting GPS but installation of the previous version failed.
Anyway, is there any way to stop Google services updating automatically? I can't find anything in the settings. I have Play Store set not to update automatically but that doesn't seem to make any difference. When google play services updates I don't get redirected to the Play store, it just installs the update without asking me.
Follow these hints next time.
Anyone else still having this issue? It's issuing a lot of wakelocks for me (Marshmallow/TouchWiz Note 4)
Coldblackice said:
Anyone else still having this issue? It's issuing a lot of wakelocks for me (Marshmallow/TouchWiz Note 4)
Click to expand...
Click to collapse
Yep same for me (TW MM Note 4). Amplify shows *net_scheduler* to be by far biggest wakelock, which is what brought me to this thread. Google Play Services now at at v9.4.52. Hmmm.
wakelock
it is google play services which drains battery very drasticly
arctophile said:
Yep same for me (TW MM Note 4). Amplify shows *net_scheduler* to be by far biggest wakelock, which is what brought me to this thread. Google Play Services now at at v9.4.52. Hmmm.
Click to expand...
Click to collapse
Started happening to me yesterday - battery was great until this
Hi,
For some reason SystemUpdateService is absolutely destroying my battery (phone awake 98% of the time) because it's not running and Android is constantly trying to run checks against it.
The service is under both of the following apps:
Google Play Services
Google Play Services Framework
If I use the DisableService app I can kick them back into action again... but whenever I restart my phone, they're disabled again. Also, sometimes they randomly switch off again at random.
Any idea how to keep these services running please?
Many thanks
Hi,
I am using the latest Greenify version (donation package) v2.6.2 in order to hybernate some apps causing wakelocks when my phone is in stand-by mode. I was also trying to hybernate all the google apps, such as google play store or google play services, which worked out perfectly by cutting off some reactivation paths.
In order to update my apps weekly or monthly I wanted to take these apps from the greenify list, which was successful at first glance. However, I am now facing problems in regreenifying them, especially when it comes to the google play services. I have no idea why, but this times greenify always tells me that it fails to hybernate google play services for no apparent reason. Also it does not show me the scissors tool to cut off the wakelock paths.
Has anybody of you experienced the same problems? Is there any solution for my problem? Thank you for your help!
If you use beta 5, that's why:
Beta 5
Foreground app no longer hibernates even if "state always ignored" is checked.
Reduced the impacts of wake-up cut-off.
FIX: Native processes cleaning.
FIX: Wake-up action in Tasker plug-in on Android 5.x.
FIX: No longer list disabled apps.
Click to expand...
Click to collapse
MihaiSG said:
If you use beta 5, that's why:
Click to expand...
Click to collapse
Actually not, I am using version 2.6.2 according to the application.
I have seen problems after I hibernate an app called " Google App" similar issues
Still the same problem. Reinstallation of greenify and Xposed didn't work out, unfortunately. Did they change something inside of greenify without a new version?