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.
Related
Is anyone seeing this copious amounts of this wakelock too? It's part of the Google Search app and its wakelock has now been active for close to 5 hours now just today and seems to be active for most of the day. This is reported by Better Battery Stats and is seems to be confirmed by high energy usage by the built-in batttery settings app, as Google Search hovers in the mid 20s percentage.
floepie said:
Is anyone seeing this copious amounts of this wakelock too? It's part of the Google Search app and its wakelock has now been active for close to 5 hours now just today and seems to be active for most of the day. This is reported by Better Battery Stats and is seems to be confirmed by high energy usage by the built-in batttery settings app, as Google Search hovers in the mid 20s percentage.
Click to expand...
Click to collapse
I got this wakelock overnight after completely disabling location services. My N5 was held awake literally the whole night by this wakelock. This morning I turned back on location reporting and the phone is deep sleeping once again. Very strange. Did you have location service disabled because that seems to be what is causing the wakelock?
I would like to find a solution to this so I can keep location services disabled without completely disabling Google Now for overnight when I can't access a charger.
GoldElocks said:
I got this wakelock overnight after completely disabling location services. My N5 was held awake literally the whole night by this wakelock. This morning I turned back on location reporting and the phone is deep sleeping once again. Very strange. Did you have location service disabled because that seems to be what is causing the wakelock?
I would like to find a solution to this so I can keep location services disabled without completely disabling Google Now for overnight when I can't access a charger.
Click to expand...
Click to collapse
Yeah, I have my location services set to "device only", which I guess is the equivalent to the former GPS only. It could be that the GPS is turning itself off and on continually while it's supposed to be sleeping, and the fact that I'm mainly indoors could explain the hours long wakelock.
I set it to GPS only on the Nexus 5, because that was the most battery friendly on the Nexus 4, but the way services now work, it could be the least battery friendly setting.
this is completely confirmed! my note3 wasnt sleeping at all with the new google search 20hrs of no deep sleep with location off and i turned location on and its been sleeping like a dream for the past hour.. Very weird though
Same issue here with my HTC One. I noticed my battery was tanking at about twice the normal rate today, so I just opened up Wake Lock Detector and saw that on about 5.5 hours of use, Google Search had it awake for 4.5 of them. I've just turned on location services to see if that fixes it.
But, I'm with you. I'd rather find a fix that lets me keep location disabled.
Me too. I have a Galaxy4 S4 with 4.3 stock Samsung ROM. WLD shows huge count of EntriesRefresh_wakelock with almost three hours from 12 por off charge.
Confirmed on the lg g2 on 4.3. I disabled Wi-Fi and mobile network location because of the horrible nlp partial wakelocks only to encounter the entriesRefresh wakelock leech. Keeps awake like 90 of the time. I'm going to go back to enable Wi-Fi and mobile location until this is cleared up.
I am unable to even use Google now.. if I enable Location Report it's burning up and running about 20%.. if I disable Location Reporting it's running 50%.. I like Google Now and don't have any use for the location stuff...
Anyone have any updates? My only other option is going to just be to wipe it and keep Google Now unused so it doesn't run at all..
You can try to greenify Google search which contains this wakelock if you have the paid version of greenify (hibernates system apps). They say it's inadvisable to hibernate system apps, but you can override it. I would do a full backup and try it. They refund your money in 3 days instead of 15 minutes if your not happy. I haven't had a chance to try it yet.
Sent from my LG-D801 using xda app-developers app
Oddly enough I never had this issue on my nexus 5, but my Nexus 7 is absolutely plagued with just hours and hours of this wake lock as soon as I turn location reporting off.
Same issue here, my N7 is going nuts with this.
the7thson said:
Same issue here, my N7 is going nuts with this.
Click to expand...
Click to collapse
This has happened on my N5 before. Force stopping it once I noticed and also rebooting seem to fix it.
I had this wakelock for 2 nights in a row, completely draining the battery BUT
I have location services enabled and GPS is on (I play Ingress all the time and the network loaction gives me a faster lock)
I too noticed this was my top partial wakelock yesterday even though I have location services on. First time I've seen that happen. But it wasn't as aggressive as it was when location services were off.
Sent from my LG-D801 using xda app-developers app
Noticed this keeping my Nexus 5 awake 51%, location services were disabled. My Nexus 7 and Moto X also have them disabled and they were only awake 1%. Google Search is showing 60% of the battery but my device has been mostly idle for 4 days now. I'll see if enabling the services helps otherwise I'm not sure what else to attempt.
ohmimpotence said:
Noticed this keeping my Nexus 5 awake 51%, location services were disabled. My Nexus 7 and Moto X also have them disabled and they were only awake 1%. Google Search is showing 60% of the battery but my device has been mostly idle for 4 days now. I'll see if enabling the services helps otherwise I'm not sure what else to attempt.
Click to expand...
Click to collapse
I got this wakelock this morning.... "entriesrefresh_wakelock"
my location reporting is off
I love my N5 but god......I'm experiencing battery drain frequently (when I'm not on WIFI) with different wakelocks...
Otherwise the battery life is very good, if google can fix it once for all
I had this problem on my Nexus 5 too. I "fixed" it by uninstalling updates for the Google Search app (you can get there by going Settings>Apps and tapping Google Search). However Google will re-update the app frequently so you will have to repeat the process. Here's hoping another update fixes this problem.
Either disabling Location reporting or Locations all together can get rid of this I believe. Tasker can automatically re-enable it when you leave your wifi zone.
Hello,
I am on ParanoidAndroid 4.4 and the battery drain is killing me. I have to charge my phone at least twice a day if I'm outside just because I'm scared of having my phone die on me. I was on stock 4.4.3 up until recently but the sudden wakelocks at random times would kill me so I switched to PA to at least have a few extras like Hover and its even worse now. I'm using ElementalX kernel now because of how amazing the battery life is supposed to be but I am almost crying :'(
I have noticed that if I turn WiFi off, the phone will go to sleep without any problems but turn it on and it'll stay up all night and all day draining the battery 2% every 5 minutes of use. It appears GoogleSearch is the culprit but I'd like some more help on this.
I have uploaded some screenshots if anyone could help me I would really appreciate it.
Thank you.
WakeLockDetector: http://i.imgur.com/oHHRxoE.png
BetterBatteryStats: http://i.imgur.com/C9VEYDx.png (the stats appear to be screwed a little after I turned WiFi off) Logs: http://pastebin.com/vrRpdDdm
Android Battery stats: http://i.imgur.com/hSCfvoa.png and http://i.imgur.com/iVEsVuX.png
EDIT:
I've charged my phone again after disabling Google Now and hibernating WhatsApp and Viber in Greenify. Here are some screenshots. It's still the same
System battery: http://i.imgur.com/qq0I0uc.png
GSam: http://imgur.com/1KIZjJp and http://imgur.com/6JcI1Zs
whisky_ said:
Hello,
I am on ParanoidAndroid 4.4 and the battery drain is killing me. I have to charge my phone at least twice a day if I'm outside just because I'm scared of having my phone die on me. I was on stock 4.4.3 up until recently but the sudden wakelocks at random times would kill me so I switched to PA to at least have a few extras like Hover and its even worse now. I'm using ElementalX kernel now because of how amazing the battery life is supposed to be but I am almost crying :'(
I have noticed that if I turn WiFi off, the phone will go to sleep without any problems but turn it on and it'll stay up all night and all day draining the battery 2% every 5 minutes of use. It appears GoogleSearch is the culprit but I'd like some more help on this.
I have uploaded some screenshots if anyone could help me I would really appreciate it.
Thank you.
WakeLockDetector: http://i.imgur.com/oHHRxoE.png
BetterBatteryStats: http://i.imgur.com/C9VEYDx.png (the stats appear to be screwed a little after I turned WiFi off) Logs: http://pastebin.com/vrRpdDdm
Android Battery stats: http://i.imgur.com/hSCfvoa.png and http://i.imgur.com/iVEsVuX.png
Click to expand...
Click to collapse
Disable Google Now and Greenify it. If it's a system app, I recommend using a minimal gapps package. Like the one from my signature.
If that's still not good enough, Greenify WhatsApp and Viber. We need to see if they are the cause. I suspect something else is the issue, but let's rule out your top 3.
Oh I almost forgot. Thank you for posting a BBS log without being asked.
Aerowinder said:
Disable Google Now and Greenify it. If it's a system app, I recommend using a minimal gapps package. Like the one from my signature.
If that's still not good enough, Greenify WhatsApp and Viber. We need to see if they are the cause. I suspect something else is the issue, but let's rule out your top 3.
Oh I almost forgot. Thank you for posting a BBS log without being asked.
Click to expand...
Click to collapse
Greenify won't allow me to hibernate it since its a System app and asks me to buy the donate package. Also, I'm on ART so Xposed doesn't work for me. Is there a workaround?
whisky_ said:
Greenify won't allow me to hibernate it since its a System app and asks me to buy the donate package. Also, I'm on ART so Xposed doesn't work for me. Is there a workaround?
Click to expand...
Click to collapse
App Ops and nuke it's permissions.
Neither ROM nor kernel will help your battery life.
Lethargy said:
App Ops and nuke it's permissions.
Neither ROM nor kernel will help your battery life.
Click to expand...
Click to collapse
Can't nuke permissions for System apps
whisky_ said:
Can't nuke permissions for System apps
Click to expand...
Click to collapse
Then change it to a user app with Titanium Backup, etc lol. If you installed it from the Play Store it would be a user app, it's installed as a system app if it's flashed in a gapps package. Shouldn't have any problems moving it. You could also Greenify it for free if you did that..
Aerowinder said:
Disable Google Now and Greenify it. If it's a system app, I recommend using a minimal gapps package. Like the one from my signature.
If that's still not good enough, Greenify WhatsApp and Viber. We need to see if they are the cause. I suspect something else is the issue, but let's rule out your top 3.
Oh I almost forgot. Thank you for posting a BBS log without being asked.
Click to expand...
Click to collapse
I've updated my post to add GSam stats for a little while after disabling Google Now and hibernating WhatsApp and Viber. Thanks for your time.
whisky_ said:
I've updated my post to add GSam stats for a little while after disabling Google Now and hibernating WhatsApp and Viber. Thanks for your time.
Click to expand...
Click to collapse
You said you are on PA. You need to wipe system, reflash PA, then flash the Banks minimal gapps in my signature. Then download Google search from play store. Google Now is now user app and can Greenify it. After you do that, send another BBS log.
You will also need Nova launcher or similar. Banks gapps doesn't come with a launcher.
OK guys....look at this I found.
Last night I enabled the new "OK google from any screen" option, in Google settings, OK Google hotword detection.
Then after only after I woke up (didn't charge...I charged before bed) look what I saw....held awake time on Google search, which I've never gotten before.
So a couple hours ago I turned from any screen option off.....no more held awake time on search.
So guys with Google search out of control.....that might be the issue.
Too bad too....I liked that new feature, but Google gone messed it up.....again.
KJ said:
OK guys....look at this I found.
Last night I enabled the new "OK google from any screen" option, in Google settings, OK Google hotword detection.
Then after only after I woke up (didn't charge...I charged before bed) look what I saw....held awake time on Google search, which I've never gotten before.
So a couple hours ago I turned from any screen option off.....no more held awake time on search.
So guys with Google search out of control.....that might be the issue.
Too bad too....I liked that new feature, but Google gone messed it up.....again.
Click to expand...
Click to collapse
Sadly, this is to be expected at this point.
I think like double tap to wake.... If it isn't on the low voltage core, like moto x always listening is, its never gonna be battery friendly. But people wanted....they got it...kinda. Better than having to be on a certain screen anyway. Just now audio in is listening to every sound it hears.
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.
I am running into a Wakelock issue and I am completely stumped. For some reason, my phone refuses to go into deep sleep for hours on end. Better Battery Stats shows that the phone spends the majority of its time with the CPU at its lowest frequency, but refuses to go into deep sleep. The issue started when I clean flashed LinageOS back when I tried 14.1. Since 15.1 has recently released, I tried to have another go, yet the problem remains. I am using a Oneplus 5.
The very weird thing about these Wakelocks is, is that they are completely invisible. Wakelock Detector isn't showing any specific wakelocks (Advanced mode enabled), but does show that the phone isn't entering the deep sleep state. Not even for a single second. Better Battery Stats shows the same thing, with zero seconds spent in Screen off (deep sleep) and all the time spent in Screen off (Awake). No application is listed anywhere that's causing these wakelocks. They aren't visible under partial wakelocks nor kernel wakelocks.
Now this is where things get bizarre. I tried removing all my applications and reinstalling them one by one to find out if it was an app that was causing the issues. Each time I installed an app, I would check whether the phone would go into deep sleep when I wasn't using it. It turns out that the phone stopped going into deep as soon as Whatsapp was installed. Yet Whatsapp would never register more than a few seconds of wakelocks each passing hour.
I'm not sure where to even begin to try and solve this issue. Has anyone else ever experienced these kind of invisible / hidden wakelocks, and if so, how did you manage to fix these issues? Thank you very much in advance for helping me out
Nobody with a similar problem to mine? It's really killing battery life for me
Mushoz said:
Nobody with a similar problem to mine? It's really killing battery life for me
Click to expand...
Click to collapse
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
IanHodgson said:
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
Click to expand...
Click to collapse
No, I still have the same issue unfortunately. Though my issue seems to be slightly different than yours in the sense that Whatsapp is very low in the list. The total minutes of Wakelock is far below the total minutes of awake (screen off). But uninstalling Whatsapp instantly solves the wakelock issue. Out of interest, what phone are you using and what rom?
Mushoz said:
Out of interest, what phone are you using and what rom?
Click to expand...
Click to collapse
Redmi Note 4, Pixel Experience Oreo 8.1
I got here through a google search. I am not sure it's whatsapp causing this (haven't removed it yet) but on a Moto G3 with LOS 15.1 unofficial by Rahul I have the same symptoms.
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.