Related
Ok so for the life of me I cant figure out why my battery is draining so fast its literally draining about 10% an hour if not more. If tried a bunch of different tools to try and monitor it but nothing is really standing out as a main culprit. I recently had my phone replaced and I had them send a new battery just for the heck of it. Also I even tried putting Hyperdrive Roms on my phone and that did not help. So I debating on whether to go back to stock and just root and see what happens again after just removing bloatware.
I tried looking up battery tips but really haven't found anything recently. I only got my phone in May of this year. Any suggestions or links would greatly help I love my phone but cant stand the battery life. I miss my Droid Razr Maxx
SUPERSPORT25 said:
Ok so for the life of me I cant figure out why my battery is draining so fast its literally draining about 10% an hour if not more. If tried a bunch of different tools to try and monitor it but nothing is really standing out as a main culprit. I recently had my phone replaced and I had them send a new battery just for the heck of it. Also I even tried putting Hyperdrive Roms on my phone and that did not help. So I debating on whether to go back to stock and just root and see what happens again after just removing bloatware.
I tried looking up battery tips but really haven't found anything recently. I only got my phone in May of this year. Any suggestions or links would greatly help I love my phone but cant stand the battery life. I miss my Droid Razr Maxx
Click to expand...
Click to collapse
Not sure but I think its a Kit Kat issue. I recall having more battery life on JB than on Kitkat with my S4.
There are lots of things you can do.
System Settings
•WiFi - change sleep policy from ALWAYS (staying on) to either "Only when plugged in" or "never"
•Account Sync - under my Google account(s) I only keep CONTACTS and GMAIL checked...the rest unchecked
•Motions, Smart Features, Gestures, Air - Turn ALL of this crap off!
•Animation Scaling- In Developer Options - I use these settings: Window Animation=OFF/ Transition Animation=0.5x/ Animator Duration=0.5x
In-App Settings
•Play Store - In settings, change Auto-Update Apps to Never...you can do this manually from time to time. If not, it'll just always scan.
•App Ops - This can be a little tedious, but go through your apps (especially under Location) and turn location off on whatever you think doesn't need it! You may want to test out each app to be sure it is functioning properly before you move on to the next app. This makes it much easier to go back and enable it again if you see its needed. Most of the Google apps are gonna need it.
Freeze or Uninstall System Apps
•Check out my thread on which system apps you can remove here
***I recommend using NoBloat to make your changes with:good:
Additional apps & Xposed modules to check out
•Greenify - Hands down my favorite battery saving app. If you don't know it, that's why your battery life sucks! Seriously though, GET IT!
•Greenify Donation (Xposed) - Adds several more features, such as allowing system apps to be greenifiable! Also works well with WakeLock Detector
•WakeLock Detector - Helps determine which apps are waking up your phone while its asleep...allows you to prevent future wakeups.
•Gsam Battery Monitor Pro - Not sure if the free version lets you use the monitoring feature or not, but basically it is like a glorified battery usage graph (like in system settings)
•BootManager - Xposed module allowing you to select which apps are able to run in startup. Not sure how it compares with Greenify, but I just use both
•Prevent Running - Also similar to Greenify. I'm in the process of checking this one out, so don't hold me to it being great.
I took this from @calebcabob
SUPERSPORT25 said:
Ok so for the life of me I cant figure out why my battery is draining so fast its literally draining about 10% an hour if not more. If tried a bunch of different tools to try and monitor it but nothing is really standing out as a main culprit. I recently had my phone replaced and I had them send a new battery just for the heck of it. Also I even tried putting Hyperdrive Roms on my phone and that did not help. So I debating on whether to go back to stock and just root and see what happens again after just removing bloatware.
I tried looking up battery tips but really haven't found anything recently. I only got my phone in May of this year. Any suggestions or links would greatly help I love my phone but cant stand the battery life. I miss my Droid Razr Maxx
Click to expand...
Click to collapse
Post the log from BetterBatteryStats, that tells all.
GrizzlyBarrn said:
There are lots of things you can do.
System Settings
•WiFi - change sleep policy from ALWAYS (staying on) to either "Only when plugged in" or "never"
•Account Sync - under my Google account(s) I only keep CONTACTS and GMAIL checked...the rest unchecked
•Motions, Smart Features, Gestures, Air - Turn ALL of this crap off!
•Animation Scaling- In Developer Options - I use these settings: Window Animation=OFF/ Transition Animation=0.5x/ Animator Duration=0.5x
In-App Settings
•Play Store - In settings, change Auto-Update Apps to Never...you can do this manually from time to time. If not, it'll just always scan.
•App Ops - This can be a little tedious, but go through your apps (especially under Location) and turn location off on whatever you think doesn't need it! You may want to test out each app to be sure it is functioning properly before you move on to the next app. This makes it much easier to go back and enable it again if you see its needed. Most of the Google apps are gonna need it.
Freeze or Uninstall System Apps
•Check out my thread on which system apps you can remove here
***I recommend using NoBloat to make your changes with:good:
Additional apps & Xposed modules to check out
•Greenify - Hands down my favorite battery saving app. If you don't know it, that's why your battery life sucks! Seriously though, GET IT!
•Greenify Donation (Xposed) - Adds several more features, such as allowing system apps to be greenifiable! Also works well with WakeLock Detector
•WakeLock Detector - Helps determine which apps are waking up your phone while its asleep...allows you to prevent future wakeups.
•Gsam Battery Monitor Pro - Not sure if the free version lets you use the monitoring feature or not, but basically it is like a glorified battery usage graph (like in system settings)
•BootManager - Xposed module allowing you to select which apps are able to run in startup. Not sure how it compares with Greenify, but I just use both
•Prevent Running - Also similar to Greenify. I'm in the process of checking this one out, so don't hold me to it being great.
I took this from @calebcabob
Click to expand...
Click to collapse
This is good info thanks. I am doing most of it such as Greenify, etc. Wakelock Detector I have no clue how to use though. I open it up and its like chinese to me any tips on using that? I did not realize the play store is always scanning for updates...interesting. The only thing I see disturbing is that security is the thing I see most used even after shutting the phone off and turning it back on in Usage Timelines. I am rooted and Knox is disabled so im wondering what is causing the high usage on this.
SUPERSPORT25 said:
This is good info thanks. I am doing most of it such as Greenify, etc. Wakelock Detector I have no clue how to use though. I open it up and its like chinese to me any tips on using that? I did not realize the play store is always scanning for updates...interesting. The only thing I see disturbing is that security is the thing I see most used even after shutting the phone off and turning it back on in Usage Timelines. I am rooted and Knox is disabled so im wondering what is causing the high usage on this.
Click to expand...
Click to collapse
WakeLock detector works great for exactly what you're trying to figure out. Check out the WakeLock guide, it'll show you exactly what it's role is. Once you have it installed, you will sometimes see a scissors icon in Greenify when you have something listed under NOT hibernating or pending...click it! You'll see the option for Greenify to "cut-off" the process chain...this prevents further wakeups from what had specifically started up the process. I highly recommend you take a look at gsam battery monitor (I think that's the name), it will also give you details on which processes are killing your battery.
I am not positive but I think you can disable that security process without any issue. You may want to Google that though.
---------- Post added at 03:20 AM ---------- Previous post was at 03:17 AM ----------
SUPERSPORT25 said:
This is good info thanks. I am doing most of it such as Greenify, etc. Wakelock Detector I have no clue how to use though. I open it up and its like chinese to me any tips on using that? I did not realize the play store is always scanning for updates...interesting. The only thing I see disturbing is that security is the thing I see most used even after shutting the phone off and turning it back on in Usage Timelines. I am rooted and Knox is disabled so im wondering what is causing the high usage on this.
Click to expand...
Click to collapse
Short answer...WakeLock only detects, you decide what you need to STOP from there. But there are apps that can utilize WakeLock to detect those battery killers and stop, freeze or remove processes or apps for you...such as Greenify.
Also, I can't stress enough how worth it it is to buy Greenify's experimental features, as it will allow you to get deeper into the whole Greenifying thing!! Hell yes it does:good:
calebcabob said:
WakeLock detector works great for exactly what you're trying to figure out. Check out the WakeLock guide, it'll show you exactly what it's role is. Once you have it installed, you will sometimes see a scissors icon in Greenify when you have something listed under NOT hibernating or pending...click it! You'll see the option for Greenify to "cut-off" the process chain...this prevents further wakeups from what had specifically started up the process. I highly recommend you take a look at gsam battery monitor (I think that's the name), it will also give you details on which processes are killing your battery.
I am not positive but I think you can disable that security process without any issue. You may want to Google that though.
---------- Post added at 03:20 AM ---------- Previous post was at 03:17 AM ----------
Short answer...WakeLock only detects, you decide what you need to STOP from there. But there are apps that can utilize WakeLock to detect those battery killers and stop, freeze or remove processes or apps for you...such as Greenify.
Also, I can't stress enough how worth it it is to buy Greenify's experimental features, as it will allow you to get deeper into the whole Greenifying thing!! Hell yes it does:good:
Click to expand...
Click to collapse
Yes I pretty much have everything that people have suggested including the experimental version of Greenify. I am running Wakelock Detector, GSAM Battery Monitor, Usage Timelines.
However I am still seeing this Security Process running at about 6% and about 82.45 MB. I am not really experiencing any drain when the phone is sleeping.
SUPERSPORT25 said:
Yes I pretty much have everything that people have suggested including the experimental version of Greenify. I am running Wakelock Detector, GSAM Battery Monitor, Usage Timelines.
However I am still seeing this Security Process running at about 6% and about 82.45 MB. I am not really experiencing any drain when the phone is sleeping.
Click to expand...
Click to collapse
Can u post a screenshot of gsam's monitor section? Its the part that has the list of usage...looks similar to the battery monitor screen in Android settings.
Hi all
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
thx
This same problem,
S III, rom > http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
Xposed framework installed
Greenify is device administrator
I have full version
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
If I may make a suggestion?
I started getting the same error message (it started right after I paid for the app). After reading "thousands" of pages I think I may have hit on the answer. Greenify is in "boost" mode, that somehow, even though it uses xposed framework, doesn't need root. So I checked supersu and greenify wasn't listed. Then I changed to "root" method and greenified an app, then supersu asked to allow greenify, thereby now having it listed again in supersu.
I then changed it back to "boost" and so far haven't had that error. Coincidently, Greenify seemed to work ok anyway even with that error.,
edit: well that blows, I started to get the error message again, so disregard what I wrote above. Maybe a fix is coming, or I'll live with manually starting auto-hibernation.
tnsmani said:
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
Click to expand...
Click to collapse
No, I check this 3 times ...
colin p > nothing, still this same problem
anyone has ideas, what else, I can do ?
Just to add additional info, this auto-hibernation error only started after I bought the Donation Package. I don't know if it's something to do with the additional options or not. Before I bought the program, auto-hibernation worked fine.
I have a Nexus 4 (rooted with towel-root) and SuperSu and of course the Xposed framework. I uninstalled/re-installed Greenify, as well as the Donation Package and still the error pops up the first time I open Greenify. I then have to manually start auto- hibernation and it works ok after that, at least it "seems" to as everything is under the hibernated section.
After I re-installed, SuperSu asked to allow Greenify root access, so it is properly listed. I would imagine that if a significant few of us have the issue, a future update will address the error problem.
I would like to try to enable Greenify as root mode. Will the message appear?
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
This is not a definite fix, though in some weird circumstances, it might work
TechnoSparks said:
I would like to try to enable Greenify as root mode. Will the message appear?
The message appears in either root or boost mode on the first time the program is opened after a boot up.
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
Tried your suggestion and still get the "auto-hibernation has stopped" error.
This is not a definite fix, though in some weird circumstances, it might work
Click to expand...
Click to collapse
Unfortunately, no dice. Still get that error, thanks anyway.
By George...
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
colin p said:
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
Click to expand...
Click to collapse
No problem mate. If it really works for a long time, it might be good to report here as I may take your method as a suggestion to other people facing the same problem as well. :good:
romdroid. said:
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
Click to expand...
Click to collapse
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
I had not got this message for quite a long time, but after updating to beta 2, the first time I rebooted and opened Greenify, I got this message. Afterwards, for the whole of today, I haven't got it.
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
gorilla p said:
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
Click to expand...
Click to collapse
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
tnsmani said:
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
Click to expand...
Click to collapse
for me i have to enable it in accessibility after every restart of the phone ....
Anyone found a solution to this? I am getting the same error.
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
HI Oasis - just to reply that I am still getting Auto-hibernation stopped with Greenify v2.5.1
Basically after a while auto-hibernate just seems to stop. I have all my apps waiting to be hibernated even after a few hours of screen off. I do not get the 3rd party message saying auto-hibernation is stopped. I have Accessibilty on and have given Greenify Device Administration rights.
I will get the 3rd party message if I force close Greenify or if I reboot. In those cases Accessibility will have turned itself off. After turning Accessibility back on, the message disappears but I still have apps waiting to be hibernated after seveal hours of screen-off.
After every reboot, I find that Greenify does not seem to ask SuperSU for root access. Even though I've granted Greenify automatic access,the log files for SuperSU never show Greenify as either being granted or denied rights. I know that Greenify is meant to ask for those rights when the screen is off. I guess it might be another app is locking the device when the screen is off before Greenify can ask for access. I've tried removing Device Admin privileges for other apps and remove PIN unlocks but this does not seem to help.
The only way I have managed to get Greenify running again is to uninstall and reinstall, which seems to be the only way when the screen is on that I can get it to request root access via SuperSU. This does mean I cannot use the Xposed installer options, because I would first need to reinstall Greenify, grant it root access via SuperSU, then enable the XPosed module, then reboot. But after reboot SuperSU access seems to be withdrawn and I can't get it to request root unless I uninstall and reinstall.
I'm sure I'm missing something but I'm not sure what. I am not sure if there is a way of forcing Greenify to request SuperSU access even when the screen is on without having to reinstall.
I am rooted with SuperSU 2.4 and Xposed installer, HTC One on Viper 7.02 ROM, Greenify 2.5.1 with donation package.
EDIT: I've found that I can get Greenify to ask for Root Access through Xposed if I first degreenify Facebook, re-greenify Facebook, launch another app which wakes up Facebook (eg Agoda) and then request Greenify to cut-off the wake-up. Seems to be working.
EDIT2: Alas, still having problems. Usually nothing auto-hibernates after charging the phone. Yesterday it was working fine, today I unplugged, started some apps, closed the phone and went for breakfast. 1.5 hours later the apps were still waiting to hibernate. Am completely lost on what to do next.
Dronak said:
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Click to expand...
Click to collapse
I occasionally get this message, generally after an update to Greenify, but just tap on the message and continue on with my day. After exhaustive (I'm rather OCD) research, the general consensus is to forget about it as it is just Greenify's way of letting you know that the auto-hibernation has stopped and needs to be restarted. I have gone without tapping on that message and the service still starts up all by itself.
My advice is to open Greenify after an update (updates have slowed considerably anyway) and just tap on the message and it will be good to go until the next update.
Thanks for the response. I have been tapping on the message when I notice it, but it still seems to appear without updates to Greenify. I've tried checking a little more, though probably not as exhaustively as you did, and I suspect that there's some kind of conflict with Tasker. One of the main things I do with Tasker is alternate between "home" and "work" modes, part of which involves using a screen lock for "work" and turning it off for "home". It seems like when things are working fine at home, I go to work making it switch to work mode, and return home at the end of the day going back into home mode, Greenify complains. Since Greenify only works without a screen lock in non-root mode, I'm guessing this switching may be affecting thing, but I'm not completely sure. I guess I just have to live with it. One thing I've tried doing to mitigate the problem is add a Greenify hibernate action to my Tasker profile for turning mobile data off when the screen goes off. I'm not sure how well it's working, because at work I normally hibernate manually and at home I often don't worry about it, but even if it's not working, I think I get a placebo effect of thinking it's doing *something* so I'm less concerned about checking to see if Greenify has stopped auto-hibernating.
Yes you heard it right ,i have tested this on two phones with xposed install
i have tested this for 5 days
greenify makes eats up your battery so fast and actuall battery wont gets swollen so easily
test it yourself i have tested many times and found greenify the culprit
i dont know how actually works the way it hibernates but after uninstalling you can see significant change in your battery
thanks
Maybe a problem of your setup.
Jasi2169 said:
Yes you heard it right ,i have tested this on two phones with xposed install
i have tested this for 5 days
greenify makes eats up your battery so fast and actuall battery wont gets swollen so easily
test it yourself i have tested many times and found greenify the culprit
i dont know how actually works the way it hibernates but after uninstalling you can see significant change in your battery
thanks
Click to expand...
Click to collapse
When this has happened to me (and it has) I found that greenify and another app were in a war, greenify was forcibly trying to hibernate the app and the app kept forcibly waking up from hibernation causing greenify to hibernate it again (repeat until battery is dead).
muiriddin said:
When this has happened to me (and it has) I found that greenify and another app were in a war, greenify was forcibly trying to hibernate the app and the app kept forcibly waking up from hibernation causing greenify to hibernate it again (repeat until battery is dead).
Click to expand...
Click to collapse
yes and my battery never last for 12 hours with greenify but without greenify it last over 24hours thn i put it for charging
Jasi2169 said:
yes and my battery never last for 12 hours with greenify but without greenify it last over 24hours thn i put it for charging
Click to expand...
Click to collapse
However, the solution was simple, just do not greenify the app causing the war. Then the apps that were greenified would play nice and the other apps are free to go about there business. I do not believe greenify was intended to have all of your apps in the list. Just ugly nasty battery draining, refusing to quit ones like facebook (which I do not even have installed).
u knw i dnt have bloat installd lyk fb messngr or so,i have only wwhtsapp to talk to my gf n frnds nd just sme apps but without greenify im happy cus i dnt have battery prblm then why use greenify no need
if u put battery code in ur build.prop to monitor u will c greenify keeps eatng battery
Unlucky for you. I notice much better battery stats WITH Greenify running. Always have.
Totally noob bs. Must be other problem. Recently tried few days both devices without Greenify. Battery drains so much more and faster. Also unmodded LP Preview on Art on my N7-13 tiny bit more battery life than KK on Dalvik unmodded. However KK modded with X-modules (Greenify extra, Amplify, etc) hours extra battery life.
Verstuurd vanaf mijn Nexus 7 (2013), iPad Mini 2 of Moto G Lte
i think since i have install greenify my battery is draning faster
juliatan said:
Totally noob bs. Must be other problem. Recently tried few days both devices without Greenify. Battery drains so much more and faster. Also unmodded LP Preview on Art on my N7-13 tiny bit more battery life than KK on Dalvik unmodded. However KK modded with X-modules (Greenify extra, Amplify, etc) hours extra battery life.
Verstuurd vanaf mijn Nexus 7 (2013), iPad Mini 2 of Moto G Lte
Click to expand...
Click to collapse
im just saying abt my experience i have edited and build.prop and put the battery codes in it for its logs and what i found i told ,,no bs i have pretty well knowledge abt these stuff brother
i dnt knw it work for other people or not but in my case definitely no even with donated version
if its work for then u lucky
... So much self ego unchecked. Let's not all be modest...
It did after update
Sent from A20
muiriddin said:
However, the solution was simple, just do not greenify the app causing the war. Then the apps that were greenified would play nice and the other apps are free to go about there business. I do not believe greenify was intended to have all of your apps in the list. Just ugly nasty battery draining, refusing to quit ones like facebook (which I do not even have installed).
Click to expand...
Click to collapse
how do i find which app is "causing the war?"
War Detection...
skiier54 said:
how do i find which app is "causing the war?"
Click to expand...
Click to collapse
In my case a set of apps had been updated around the time my battery drain had started. I removed the apps that had been updated and seemed to always be awake from the hibernation list and added them back one at a time (per day in my case) and found that a version of Microsoft's OneDrive was refusing to hibernate properly. Once I removed it from the list my problem went away. Another clue for me was the fact that the problematic version of OneDrive was showing up in the battery usage screen for android when it was greenified when it had never been there before...
A later version of onedrive has fixed the problem and last I tried you could now hibernate that app again...
Another approach is to unhibernate everything and add the apps back to the list one at a time observing the behavior.
muiriddin said:
In my case a set of apps had been updated around the time my battery drain had started. I removed the apps that had been updated and seemed to always be awake from the hibernation list and added them back one at a time (per day in my case) and found that a version of Microsoft's OneDrive was refusing to hibernate properly. Once I removed it from the list my problem went away. Another clue for me was the fact that the problematic version of OneDrive was showing up in the battery usage screen for android when it was greenified when it had never been there before...
A later version of onedrive has fixed the problem and last I tried you could now hibernate that app again...
Another approach is to unhibernate everything and add the apps back to the list one at a time observing the behavior.
Click to expand...
Click to collapse
hm okay that makes sense. one of my apps (peel smart remote) always seemed to be un-hibernated even though i never opened it so i disabled it. lets see what happens
skiier54 said:
how do i find which app is "causing the war?"
Click to expand...
Click to collapse
A way to find out is to lock your device, let it with the screen off for like 5 minutes, unlock it and open Greenify. See if there is any app that's not hibernated. Those that aren't you must remove them from the list to be hibernated.
muiriddin said:
...ones like facebook (which I do not even have installed).
Click to expand...
Click to collapse
I'd like to be able to use the Facebook app, but, wouldn't dream of installing it w/o Greenify.
Android should have built in the default setting that any apps you install do ABSOLUTELY NOTHING unless you actually HAVE THEM OPEN. Checking for updates, giving you notifications, etc. should all come off by default and only go on when a user chooses to specifically turn them on!
@oasisfeng Disclaimer: Apologies in advance -- this is a long one!
I've been experiencing an odd issue, as of late, running the 2.6.1 stable on my Nexus 5 (LP 5.1 / LMY47I, Cataclysm ROM). I'm using Root Mode (donation version), without Xposed.
This issue is slightly difficult to explain. By observing my SuperSU logs, I've noticed that a seemingly random and previously Greenified app will be continually hibernated every 30 minutes or so, each time my device goes idle for a prolonged period (such as while I'm working, or asleep). Curiously, the apps in question will change during each idle period, largely excluding the possibility that this is simply the case of a rogue app. The various apps are usually quite innocuous, and never known to (randomly) wake while my device is in use -- last night's was MX Player, for instance.
(Edit: Upon further observation, it seems that the random app in question is often among the last to have been manually woken/used before entering the next deep sleep period, in case it helps.)
Unfortunately, I've yet to successfully return to my device in time to catch any possible wake-up paths. I do question, however, if the apps are actually being woken in the first place (as opposed to Greenify simply "re-hibernating" apps that are already sleeping), as the issue will seemingly disappear entirely when auto-hibernation is disabled -- according to my SU logs, at least.
The only potential user-side cause that I can think of is that I had previously cut-off the Google Play Services wake-up path for Maps (neither G.P.S. nor any important system apps were ever actually hibernated). I've since re-attached the wake-up path, and de-Greenified Maps. Although that's probably unrelated, it's pretty much the "riskiest" thing I've done with Greenify on this device. I normally just keep a number of seldomly used user apps hibernated, and don't have any known offenders (like Facebook) on my device.
I've since removed and re-added each of my hibernated apps, as well as reinstalled Greenify (and its donation package) several times. I should note, as well, that I have not experienced any noticeable battery drains. Unfortunately, I'm unable to confirm whether or not this occurred before updating to Greenify 2.6.1 stable -- I've simply only observed this behavior since the Play Store rollout.
I've attached an example screenshot of my SuperSU log (taken after a 7 hour idle period), just so you can better visualize the pattern (the actual content of each log is simply the usual force stop message). Apologies for not providing anything more helpful at this time; please let me know if there's anything you'd like to see.
Thank you, for both your time and continued support for this wonderful app.
I am experiencing the same issue as above
"(Edit: Upon further observation, it seems that the random app in question is often among the last to have been manually woken/used before entering the next deep sleep period, in case it helps.)"
this is definitely the case with me. I am quite certain the apps are not actually being woken up every 30 minute period. It feels like greenify is running the command needlessly.
I am in the beta channel and using root mode
@oasisfeng I also experiencing this issue. On BetterBatteryStats, I have partial wakelocks every 30 minutes and it seemed greenify is causing this.
I'm on XtreStoLite 2.1 - LP TouchWiz based ROM running Greenify 2.6.1 on Root mode with Donation Package
It's not an issue, but a protective design, to ensure the apps occasionally woken during the idle period being put back to hibernation again.
First of all, this is not a wake-up periodic timer, that means if your device fell in sleep for more than half a hour, it will never wake up the CPU until other apps wake it. So, it consumes little battery juice, which you could hardly perceive.
I'm planning to add latest wake-up information for all apps including the hibernated ones.
Hi, guys, do you use Tasker for periodic hibernation/wakeup task with Greenify?
I dont. I have tasker installed, but havent set it up to do anything yet. Cheers
oasisfeng said:
Hi, guys, do you use Tasker for periodic hibernation/wakeup task with Greenify?
Click to expand...
Click to collapse
Thanks for your replies! In my case, I haven't been using any hibernation/wake-up tasks (although Tasker is installed).
Regarding your first response, I'm not entirely sure what you mean about the protective design. Apologies if there's any confusion, but if you're suggesting that Greenify simply ensures that woken apps remain hibernated, the puzzling thing is that these particular apps will not wake at all when auto-hibernation is disabled.
Auto hibernation/Manual hibernation
@oasisfeng
I have the same issue as the others above but noted your explanation for the same. I am running stock Lollipop 5.1 in my rooted Nexus 4 with Greenify 2.6.2 beta 3 running in Root mode with donation features.
One more issue which is more serious (in my opinion), is auto hibernation and manual hibernation. Some system apps like Google Services Framework and Google Play Services do not get autohibernated occasionally. Likewise even if the manual shortcut Hibernate+lockscreen is used, these remain running sometimes, even after half an hour of sleep. However, there is no noticeable impact on battery. (I have brought the battery loss down to 0.3 to 0.7% per hour while sleeping, from 6 to 7% without Greenify. Thanks for that) As the others reported, SU logs indicate that every half hour Greenify hibernated these apps though they are present as running continuously when Greenify is opened. My suspicion is that though they are actually hibernated, Greenify does not correctly reflect the status.
This is more of a report than a complaint to keep you and others informed.
tnsmani said:
@oasisfeng
I have the same issue as the others above but noted your explanation for the same. I am running stock Lollipop 5.1 in my rooted Nexus 4 with Greenify 2.6.2 beta 3 running in Root mode with donation features.
One more issue which is more serious (in my opinion), is auto hibernation and manual hibernation. Some system apps like Google Services Framework and Google Play Services do not get autohibernated occasionally. Likewise even if the manual shortcut Hibernate+lockscreen is used, these remain running sometimes, even after half an hour of sleep. However, there is no noticeable impact on battery. (I have brought the battery loss down to 0.3 to 0.7% per hour while sleeping, from 6 to 7% without Greenify. Thanks for that) As the others reported, SU logs indicate that every half hour Greenify hibernated these apps though they are present as running continuously when Greenify is opened. My suspicion is that though they are actually hibernated, Greenify does not correctly reflect the status.
This is more of a report than a complaint to keep you and others informed.
Click to expand...
Click to collapse
jacknicholson said:
Thanks for your replies! In my case, I haven't been using any hibernation/wake-up tasks (although Tasker is installed).
Regarding your first response, I'm not entirely sure what you mean about the protective design. Apologies if there's any confusion, but if you're suggesting that Greenify simply ensures that woken apps remain hibernated, the puzzling thing is that these particular apps will not wake at all when auto-hibernation is disabled.
Click to expand...
Click to collapse
jacknicholson said:
@oasisfeng Disclaimer: Apologies in advance -- this is a long one!
I've been experiencing an odd issue, as of late, running the 2.6.1 stable on my Nexus 5 (LP 5.1 / LMY47I, Cataclysm ROM). I'm using Root Mode (donation version), without Xposed.
This issue is slightly difficult to explain. By observing my SuperSU logs, I've noticed that a seemingly random and previously Greenified app will be continually hibernated every 30 minutes or so, each time my device goes idle for a prolonged period (such as while I'm working, or asleep). Curiously, the apps in question will change during each idle period, largely excluding the possibility that this is simply the case of a rogue app. The various apps are usually quite innocuous, and never known to (randomly) wake while my device is in use -- last night's was MX Player, for instance.
(Edit: Upon further observation, it seems that the random app in question is often among the last to have been manually woken/used before entering the next deep sleep period, in case it helps.)
Unfortunately, I've yet to successfully return to my device in time to catch any possible wake-up paths. I do question, however, if the apps are actually being woken in the first place (as opposed to Greenify simply "re-hibernating" apps that are already sleeping), as the issue will seemingly disappear entirely when auto-hibernation is disabled -- according to my SU logs, at least.
The only potential user-side cause that I can think of is that I had previously cut-off the Google Play Services wake-up path for Maps (neither G.P.S. nor any important system apps were ever actually hibernated). I've since re-attached the wake-up path, and de-Greenified Maps. Although that's probably unrelated, it's pretty much the "riskiest" thing I've done with Greenify on this device. I normally just keep a number of seldomly used user apps hibernated, and don't have any known offenders (like Facebook) on my device.
I've since removed and re-added each of my hibernated apps, as well as reinstalled Greenify (and its donation package) several times. I should note, as well, that I have not experienced any noticeable battery drains. Unfortunately, I'm unable to confirm whether or not this occurred before updating to Greenify 2.6.1 stable -- I've simply only observed this behavior since the Play Store rollout.
I've attached an example screenshot of my SuperSU log (taken after a 7 hour idle period), just so you can better visualize the pattern (the actual content of each log is simply the usual force stop message). Apologies for not providing anything more helpful at this time; please let me know if there's anything you'd like to see.
Thank you, for both your time and continued support for this wonderful app.
Click to expand...
Click to collapse
I have a similar problem
yesterday I was using Wakelock Detector and I found out this:
Today I flashed a new Rom and all I did was configuration stuff and install some basic apps such as facebook, twitter etc. and greenify (not xposed module) greenifying NOT system apps
After 3h it caused screen wakelock during 7 minutes
BTW I amb on stock lollipop 30b
Is greenify incompatible? is supersu broken?
Boopie11 said:
I have a similar problem
yesterday I was using Wakelock Detector and I found out this:
Click to expand...
Click to collapse
First, learn some etiquette. Quote only what is relevant or simply say that you have the same issue as others. Don't go about quoting multiple full posts.
Second, you have opened a separate thread for the same issue. So what is the point of posting the same here?
Third, though your attachments are not visible, your description gives the impression that your issue has no relevance to the posts you have quoted.
The issue appears to have been resolved with version 2.6.2. As always, my thanks go to @oasisfeng -- although if I may ask, did you manage to find the source of the issue, or is this a coincidence?
jacknicholson said:
The issue appears to have been resolved with version 2.6.2. As always, my thanks go to @oasisfeng -- although if I may ask, did you manage to find the source of the issue, or is this a coincidence?
Click to expand...
Click to collapse
Yes, your report is very precious for me to analyze this issue. It was fixed in an earlier beta version before the final release of version 2.6.2. Thanks very much!
oasisfeng said:
Yes, your report is very precious for me to analyze this issue. It was fixed in an earlier beta version before the final release of version 2.6.2. Thanks very much!
Click to expand...
Click to collapse
I was wondering whether Greenify had stopped working, after installing 2.6.2.
Now I know the reason. So this is why I don't see those repeat hibernations.
Thank you, @oasisfeng!
Hey guys,
just stumbled over the two settings ignore background-free and ignore working state.
im wondering if its recommended to check both settings for an app like snapchat (which caused me a huge constant wake lock yesterday)? i can get me an explanation for "ignore working state" but i dont really get behind "ignore background-free". what does it mean? would you enable it for most apps?
or should i just accept that snapchat hung itsself once and that it wont happen that often?
thanks!
xflowy said:
...or should i just accept that snapchat hung itsself once and that it wont happen that often?
Click to expand...
Click to collapse
Yep - a single occurance means nothing. App coughed up a fur ball. Happens.
Leave 'ignore background-free unchecked' unless there's ample evidence that suggests Greenify got it wrong (not likely).
Davey126 said:
Yep - a single occurance means nothing. App coughed up a fur ball. Happens.
Leave 'ignore background-free unchecked' unless there's ample evidence that suggests Greenify got it wrong (not likely).
Click to expand...
Click to collapse
thanks.
but i can still greenify snapchat, right? without enabling the ticks.
xflowy said:
thanks.
but i can still greenify snapchat, right? without enabling the ticks.
Click to expand...
Click to collapse
Sure - but what's the point? The whole purpose of Greenify is to rein in misbehaving apps which usually manifests as unwanted background activity. The only apps that should overtly Greenified on Android 6 and above are demonstrated bad actors. Doze take care of the rest.