Related
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.
@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!
I am just wondering if anyone else is having problems with notifications disappearing upon hibernation with xposed 5.1. I have everything set right in experimental settings, I've been using this so for years so I know how to set it properly☺. Just wondering if I am the only one because I am about to loose my mind!! I've tried everything, installing uninstalling downgrading upgrading, I've spent hours on it, just thought I'd ask before giving up. Running in boost mode with donation package. Thanks
Sent from my GT-P5110 using Tapatalk
Shepguessed said:
I am just wondering if anyone else is having problems with notifications disappearing upon hibernation with xposed 5.1.
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
Try the Xposed version of the GB Dev available in the super alpha Xposed thread. Also use beta 3 of Greenify with that. This combination is reported to be working.
Another alternative is to disable deep hibernation in Greenify.
tnsmani said:
Try the Xposed version of the GB Dev available in the super alpha Xposed thread. Also use beta 3 of Greenify with that. This combination is reported to be working.
Another alternative is to disable deep hibernation in Greenify.
Click to expand...
Click to collapse
I am guessing he's using that version of Xposed. But yeah this problem is there.
ottomanrage said:
I am guessing he's using that version of Xposed. But yeah this problem is there.
Click to expand...
Click to collapse
Yes I have tried every possible combo, litterally spent hours on it. I am just wondering if it is my problem only or are other people having this problem? I would love to know!
Sent from my GT-P5110 using Tapatalk
Hi guys. I'm on the same boat.
CM12.1, Greenify 2.6.2b5, xposed super alpha and no notifications kept after auto-hibernate for whatsapp, hangouts and skype.
I've only installed xposed again, and greenify module etc, and notifications only affect Facebook, but just noticed by just noticed that they're snoozing too.
I have the same issue, notifications come in, but then they disappear. I have all the required options checked, using alpha 4 xposed + b5 greenify.
Yes, i have this too. All notifications are gone after re-greenify.
---------- Post added at 07:01 PM ---------- Previous post was at 06:38 PM ----------
I may have accidentally found a solution. deleted beta 5(back up in titanium backup first) , reboot, reinstalled beta 4, reboot, restore beta 5. seems to be working for me now. not quite sure why.
davtse said:
I may have accidentally found a solution. deleted beta 5(back up in titanium backup first) , reboot, reinstalled beta 4, reboot, restore beta 5. seems to be working for me now. not quite sure why.
Click to expand...
Click to collapse
Did you activate the xposed module after b4 installation? When you restored b5 using TiBu, did you choose app, data or app+data? For me, your solution doesn't work.
christiano88 said:
Did you activate the xposed module after b4 installation? When you restored b5 using TiBu, did you choose app, data or app+data? For me, your solution doesn't work.
Click to expand...
Click to collapse
yes activated after b4 installation. after that i just restored app+data for b5. alternatively try to enable notification access for greenify as well. might have been a step i missed but its still working for me.
davtse said:
yes activated after b4 installation. after that i just restored app+data for b5. alternatively try to enable notification access for greenify as well. might have been a step i missed but its still working for me.
Click to expand...
Click to collapse
I do not have Greenify under Notification access.
christiano88 said:
I do not have Greenify under Notification access.
Click to expand...
Click to collapse
weird... i do though. see attached picture. i'm on 5.1.1 slimpop
Beta 6 is up, it doesn't address this issue. I tried reinstalling from scratch, greenify appeared in notification access, but as soon as I activated "Keep notifications" (root non-limited one) under greenify, it disappeared from the notification access. @davtse can you please post a screenshot of your greenify settings?
L.E.: I've pretty much figured it out after reinstalling greenify multiple times and trying with different settings. This is what happens:
- Activating the xposed module makes the "Keep notifications (Limited)" disappear from Greenify options, so I went on and activated it before activating the xposed module and restarting the phone. Also make sure to activate Greenify under notification access option in phone settings.
- Even if "Keep notifications (Limited)" doesn't show anymore, if you managed to activate it before activating the xposed module, it will be kept active.
- If you activate "Keep notifications" (the non-limited one), it will cancel the Limited one, and it won't work, and it also makes Greenify disappear from the notification access menu.
These are my findings.
The good part is that I made it work this way, but the notification light goes away when the app is hibernated with a pending notification. At least, the notification stays.
christiano88 said:
Beta 6 is up, it doesn't address this issue. I tried reinstalling from scratch, greenify appeared in notification access, but as soon as I activated "Keep notifications" (root non-limited one) under greenify, it disappeared from the notification access. @davtse can you please post a screenshot of your greenify settings?
L.E.: I've pretty much figured it out after reinstalling greenify multiple times and trying with different settings. This is what happens:
- Activating the xposed module makes the "Keep notifications (Limited)" disappear from Greenify options, so I went on and activated it before activating the xposed module and restarting the phone. Also make sure to activate Greenify under notification access option in phone settings.
- Even if "Keep notifications (Limited)" doesn't show anymore, if you managed to activate it before activating the xposed module, it will be kept active.
- If you activate "Keep notifications" (the non-limited one), it will cancel the Limited one, and it won't work, and it also makes Greenify disappear from the notification access menu.
These are my findings.
The good part is that I made it work this way, but the notification light goes away when the app is hibernated with a pending notification. At least, the notification stays.
Click to expand...
Click to collapse
Glad to know that i am not alone in this I'll try your method and let you know. I don't know if there are many users in our case but in case @oasisfeng you decide to investigate on it please let us know if we can help with some kind of log or anything else. (keeping notifications after hibernation is a major feature i think)
PS : Irrelevant to the problem, but could somebody tell me difference between the root and beast mode in greenify ? (did some research on it but did not see a clear answer)
Edit : Unfortunately that did not go well at 100%, i mean that for example when i got a messenger message, the app can not go to hibernation but for facebook's notifications (e.g. friend request) after hibernation the notification goes away ... Keeping notifications is one of the best features in Greenify IMO so being broken make me :crying:
mbmb8989 said:
Edit : Unfortunately that did not go well at 100%, i mean that for example when i got a messenger message, the app can not go to hibernation but for facebook's notifications (e.g. friend request) after hibernation the notification goes away ... Keeping notifications is one of the best features in Greenify IMO so being broken make me :crying:
Click to expand...
Click to collapse
Are you sure you did exactly this?
- after installing latest version of Greenify, DO NOT REBOOT, go to settings and activate only "Do not remove notifications (Limited)".
- activate "Greenify" in Notification access from phone settings
- activate the xposed module and reboot the phone
- activate "GCM push for greenified apps".
christiano88 said:
Are you sure you did exactly this?
- after installing latest version of Greenify, DO NOT REBOOT, go to settings and activate only "Do not remove notifications (Limited)".
- activate "Greenify" in Notification access from phone settings
- activate the xposed module and reboot the phone
- activate "GCM push for greenified apps".
Click to expand...
Click to collapse
Actually, i did reboot before activating the xposed module
Just to clarify :
- In the third step, i just activate the xposed module (so i shouldn't activate any greenify feature ?) and reboot the phone ?
- In the fourth step, i activate "GCM push for greenified apps" only or among the other features ?
- Do you recommand Deep Hibernation or should i leave it off for now ?
- Concerning greenify mode, what would be more efficient in our case Boost or Root ?
Thanks again and sorry for being a pain in the arse :laugh: :laugh:
I will try again regarding your next answer and let you know how it went
Yes, you only have to activate the module. No, you can activate other features, for example, I have Deep Hibernation enabled (even though it causes some issues with accounts, and making some apps ask to re-login everytime you use them). So, I don't really recommend Deep Hibernation as it is right now, wait for more updates with fixes for it. Instead, you can check Greenify regularly to cut-off wake paths, which gets you close to having deep hibernation enabled.
Boost is the best tehnically, but I am on Root mode (personal choice).
christiano88 said:
Yes, you only have to activate the module. No, you can activate other features, for example, I have Deep Hibernation enabled (even though it causes some issues with accounts, and making some apps ask to re-login everytime you use them). So, I don't really recommend Deep Hibernation as it is right now, wait for more updates with fixes for it. Instead, you can check Greenify regularly to cut-off wake paths, which gets you close to having deep hibernation enabled.
Boost is the best tehnically, but I am on Root mode (personal choice).
Click to expand...
Click to collapse
Unfortunately that did not work :crying: I will try to go back to a previous stable version ? one you'd recommend ?
mbmb8989 said:
Unfortunately that did not work :crying: I will try to go back to a previous stable version ? one you'd recommend ?
Click to expand...
Click to collapse
Try one more time without activating other modules, just go by my steps only. If it still doesn't work, try same method with beta 5.
christiano88 said:
Try one more time without activating other modules, just go by my steps only. If it still doesn't work, try same method with beta 5.
Click to expand...
Click to collapse
I did try it with beta 3 and it worked but the notification icon is not the original one after hibernating the original app (and its the same custom icon for every app that has a pending notification and goes into hibernation).
I will try it with the beta 5. I hope that op is aware of it
Are we the only ones with this issue :crying:
It's actually working when it comes to manually hibernating the apps but it won't automatically hibernate apps when on sleep no matter how long it was. Any workaround for this or is there something that I've missed? It was working fine when I was still on my rooted KK.
My phone is Xperia z3 Compact (D5833).
dane_xperia said:
It's actually working when it comes to manually hibernating the apps but it won't automatically hibernate apps when on sleep no matter how long it was. Any workaround for this or is there something that I've missed? It was working fine when I was still on my rooted KK.
My phone is Xperia z3 Compact (D5833).
Click to expand...
Click to collapse
I also sometimes have this but only with system apps. Third party apps have no issue.
From observing the SuperSU logs, I find that Greenify fired and closed the apps but when you open Greenify, they will be shown as running the whole time. May be it is an issue with how they are reported when you open Greenify.
I am running Greenify in Boost mode with official Xposed and donation pack on 5.0.1 in a Nexus 4.
tnsmani said:
I also sometimes have this but only with system apps. Third party apps have no issue.
From observing the SuperSU logs, I find that Greenify fired and closed the apps but when you open Greenify, they will be shown as running the whole time. May be it is an issue with how they are reported when you open Greenify.
I am running Greenify in Boost mode with official Xposed and donation pack on 5.0.1 in a Nexus 4.
Click to expand...
Click to collapse
Well in my case, I opened Clash of clans, closed it, then put my phone to sleep for 30mins. I did not remove it from the running services tab/ nor did I hibernate it. I went back to see if it was hibernated automatically but it wasn't and I also checked SuperSU, it did not show anything with regards to greenify.
I have been using Greenify for quite some time on a rooted HTC M8 without issue, and I very much like the software and its associated battery savings (I contributed to the donation mode as soon as it appeared). Recently I updated my phone to the LG G4 and was pleased to learn that Greenify would work without root as there is not a reliable root method available for this phone.
My only issue with greenify has been that intermittently (from several times a day to once every couple days) the home screen wallpaper is replaced with the apps property window of one of the apps which is being greenified (see attached screen capture). The phone functions normally otherwise, and when I restart the phone the normal background is back.
Phone Specifics:
Sprint LG G4 LGLS991 (NO ROOT)
Android 5.1
Kernel 3.10.49
Greenify version 2.6.2
Experimental Settings
Working Mode: Non-root
Automated Hibernationn
Greenifying System Apps (limited)n
rest of experimental settings are off
Any advice to resolve this issue would be greatly appreciated
Thank You
Keith Kronemer
I'm sorry I can't offer any help but I have exactly the same issue on an non-rooted, Verizon LG G4 Android 5.1 phone.
I assume I have some settings wrong but I just don't know what they could be.
I have Greenify 2.71 and Greenify (Donation Package) 2.3; if that helps.
Your screen cap (original post above) is exactly what I see, 2 to 3 times per day and, like you, a phone restart returns it to normal operation until next time.
Thanks,
Gerry E.
LG G4 and Greenify
When Greenify locks the screen on my LG G4 I cannot open screen with a double tap, like I was able to in the past, I have to push the power button to be able to use my phone. I have Android 6.0, Greenify 4.1, non-rooted. Tried disabling Auto hibernation for manual, same problem. Have donation package (But can't find icon) . Love Greenify, used to work great but have to fix this problem. Please help.
jamesburgess said:
When Greenify locks the screen on my LG G4 I cannot open screen with a double tap, like I was able to in the past, I have to push the power button to be able to use my phone. I have Android 6.0, Greenify 4.1, non-rooted. Tried disabling Auto hibernation for manual, same problem. Have donation package (But can't find icon) . Love Greenify, used to work great but have to fix this problem. Please help.
Click to expand...
Click to collapse
Repost; responded here: https://forum.xda-developers.com/ap...automate-hibernate-auto-t3738150/post77169643