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:
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.
How to remove whats app from greenify? the new update doesn't show any option or may be I am missing something obvious. I don't want whatsapp to be hibernated
Did you try to highlight Whatsapp in the hibernated list and click the menu button? You will see the option to degreenify the selected app. Click that and it is degreenified.
tnsmani said:
Did you try to highlight Whatsapp in the hibernated list and click the menu button? You will see the option to degreenify the selected app. Click that and it is degreenified.
Click to expand...
Click to collapse
In teh latest version when I highlight it then shows 2 options one is X another is zzZ I clicked on X so whats app is no more in hibernated list but I am still not getting messages unless I open whatsapp
which means it still is hibernated.
I got the message saying
"Despite degreenified apps still stay in hibernation until you wake it up by explicitly launching it" so I have opened it its not in the app list but still remains hibernated.
Am I missing something? cant I get whatsapp back out working normally?
Those options are for hibernating (zzZ) and cutting off the wake up path (not X but a scissor). What you should have done is to click the menu button (three vertical dots). Then you would have got the option for degreenifying. What you seem to have done is to cut off the wake up path.
You can try to clear the cache and data of Greenify and see whether Whatsapp works. But it will involve selecting all the apps again to greenify. Otherwise I think that you may have to uninstall and reinstall Whatsapp.
I am not an expert on this so wait for some more comments before attempting to do anything.
Actually new version changed a bit so I could not find those option, anyway Just restarted the phone & seems what app is running now, I can see it in running apps will wait to get a message, hopefully its working now.
sgsI9003 said:
Actually new version changed a bit so I could not find those option, anyway Just restarted the phone & seems what app is running now, I can see it in running apps will wait to get a message, hopefully its working now.
Click to expand...
Click to collapse
IF you are facing similar problem in the future, you could actually backup your WhatsApp conversations (TiB or other backup tools you admire) and uninstall WhatsApp. After uninstalling, reboot, and then reinstall WhatsApp. Launch WhatsApp first and then attempt backup restore for your WhatsApp app.
This is a known problem and proved to some people faced it. Unfortunately however, Greenify has no way to fix this, as this is much more in behalf of WhatsApp's fault. You can search in the old thread if you are interested.
Remove Apps from Auto-Hibernation
1. Open Greenify App
2. Look for the app you want to keep open under the "Pending Manual Hibernation" list.
3. Press AND HOLD the app for a few seconds.
4. When new menu appears across the top, press the "X" button to remove it from the auto-hibernate list.
This is for Greenify App v2.8.1 on Android (Galaxy Note 5 on AT&T Network).
Trying to de-greenify stopwatch/timer app
I have a stopwatch and timer app which does not sound its alert when Greenify is active. If I force stop Greenify I get the alerts. The app does not show on Greenify's list of hibernated apps , even when a timer is in progress, so I can't work out how to de-greenify it.
Any ideas?
itm said:
I have a stopwatch and timer app which does not sound its alert when Greenify is active. If I force stop Greenify I get the alerts. The app does not show on Greenify's list of hibernated apps , even when a timer is in progress, so I can't work out how to de-greenify it.
Any ideas?
Click to expand...
Click to collapse
- if on MM/Nougat remove app from optimize list using ROM interface
- avoid using aggressive/shallow doze (experimental features)
Well, i have observed it with Facebook Messenger and Viber, should be the same issue with other greenified applications
The GCM push works fine, but the problem is, that the notification won't be visible till i actually open or unlock my screen
That said, i can see that the application has been woken by a push( seconds or minutes before i get the notification) but you can't see it till you actually open the phone so the application opens in foreground.
I am almost definitely sure this used to work at KitKat normally
I have tested this using Greenify beta(the latest) with the xposed-alpha 14-05 on OnePlus One
Reptant said:
Well, i have observed it with Facebook Messenger and Viber, should be the same issue with other greenified applications
The GCM push works fine, but the problem is, that the notification won't be visible till i actually open or unlock my screen
That said, i can see that the application has been woken by a push( seconds or minutes before i get the notification) but you can't see it till you actually open the phone so the application opens in foreground.
I am almost definitely sure this used to work at KitKat normally
I have tested this using Greenify beta(the latest) with the xposed-alpha 14-05 on OnePlus One
Click to expand...
Click to collapse
I can confirm this too! @oasisfeng you should definitely look into this issue.I've tried it on my two devices running 5.0.2 and 5.1.1 respectively.The notification doesn't come through until I wakeup the screen.The app is waken up but the notification doesn't arrive until I turn on the screen.
Removing the app from greenified list fixes the issue.
Tapped from my furious dogo
vaisakh7 said:
I can confirm this too! @oasisfeng you should definitely look into this issue.I've tried it on my two devices running 5.0.2 and 5.1.1 respectively.The notification doesn't come through until I wakeup the screen.The app is waken up but the notification doesn't arrive until I turn on the screen.
Removing the app from greenified list fixes the issue.
Tapped from my furious dogo
Click to expand...
Click to collapse
Well sometimes, after a random amount of time it may appear.. But the randomness is what troubles me as well..
@oasisfeng Can confirm this. Unless I turn on the screen manually, I don't hear the notification chime. And yes, it did work fine in KitKat.
Have same issue, no notification with Facebook and Messenger.
I get the when screen turns on, but not instantly...after a while.
Any fix?
Sent from my Samsung Galaxy S5 SM-G906K using TapaTalk
Same here, but also without greenify. I switched to a new ROM and phone. So perhaps it is ROM related.
bongster said:
Same here, but also without greenify. I switched to a new ROM and phone. So perhaps it is ROM related.
Click to expand...
Click to collapse
Hi again, I have managed to get it work again. I degreenified all apps, deselected everything under experimentally features. After a reboot I ticked off my normal feature set. And voila I'm getting gcm messages again! I guess I messed something up by using titanium...
BTW I'm using cm 12.1 optimized on a S4
bongster said:
Hi again, I have managed to get it work again. I degreenified all apps, deselected everything under experimentally features. After a reboot I ticked off my normal feature set. And voila I'm getting gcm messages again! I guess I messed something up by using titanium...
BTW I'm using cm 12.1 optimized on a S4
Click to expand...
Click to collapse
Can you be more precise in what you've done?
For now I've made an app with Tasker that closes Facebook and Messenger and then Greenify all my app list and then locks system, so to not put Facebook and Messenger on Greenify and have push messages, but don't constantly have them on Active Apps last if used.
If you want I can share it.
Sent from my Samsung Galaxy S5 SM-G906K using TapaTalk
PIRATA! said:
Can you be more precise in what you've done?
For now I've made an app with Tasker that closes Facebook and Messenger and then Greenify all my app list and then locks system, so to not put Facebook and Messenger on Greenify and have push messages, but don't constantly have them on Active Apps last if used.
If you want I can share it.
Sent from my Samsung Galaxy S5 SM-G906K using TapaTalk
Click to expand...
Click to collapse
OK. I'll try to explain a bit more precisely.
My issue was, that e.g. whatsapp does not receive messages while greenified. I had to start it manually to see if I got new messages.
This started a few days ago with my new phone. Before the new phone I had no problems with greenify in combination with cm12.1.
Here my steps:
1. Remove all Apps from greenify
2. Remove all options from experimental features
3. Restart the phone
4. Select all apps that I want to greenify
5. Reselect my normal options under experimental options.
That's it
Regards
Unfortunately this didn't work for me. But I tried something else that might be helpful. I use Amplify and decided to disable it temporarily to see if I received the GCM push and the notifications, and yes, it did work flawlessly. I might have stopped a wakelock or a service being of google that might be helpful in this.
same issues, then went to settings security device administrators checked greenify now i get push notifications when screens off
stesteste said:
same issues, then went to settings security device administrators checked greenify now i get push notifications when screens off
Click to expand...
Click to collapse
You mean you turned on the administrator setting?
ottomanrage said:
You mean you turned on the administrator setting?
Click to expand...
Click to collapse
yes just for greenify
blisspop 6.3 .arter97 kernel xposed
Same here :/ It's enabled in security settings
stesteste said:
yes just for greenify
blisspop 6.3 .arter97 kernel xposed
Click to expand...
Click to collapse
Well, it didn't help much. I tried flashing all the ROMs available for S3 and it works, partially, in the latest BlissPop. The thing is that GCM push gets received instantaneously but the notification doesn't get posted. It does though, like after 30 mins or so. But never soon enough.
any news why GCM doesnt work proberly anymore with some apps like WhatsApp ? It used to work so i wonder if this a ROM, App, Xposed or Greenify problem.
About 6-8 weeks ago i had this working with CM12.1 on a GT-I9505 (Galaxy S4) with at that time actual apps, modules and ROM.
Hi,
I'm running greenify (donation version) on a nexus 10 running CM13 release, and I can't get auto hibernation to work.
All i get from greenify are notifications listing apps that can be manually hibernated.
On my other devices (all rooted) auto hibernation works fine. Yes I do have root access turned on in CM13, and greenify has root access.
Any suggestions?
Cheers
[L]
What kind of screen lock method?
[Lemmy] said:
Hi,
I'm running greenify (donation version) on a nexus 10 running CM13 release, and I can't get auto hibernation to work.
All i get from greenify are notifications listing apps that can be manually hibernated.
On my other devices (all rooted) auto hibernation works fine. Yes I do have root access turned on in CM13, and greenify has root access.
Any suggestions?
Cheers
[L]
Click to expand...
Click to collapse
hevesi_j said:
What kind of screen lock method?
Click to expand...
Click to collapse
no idea, how can I tell?
Right now I'm inclined to say "Whatever is the default", since I'm not conscious of making any changes to any settings about screen lock methods.
after some observation time I can see that it's always the amazon apps (amazon video, kindle, amazon app store, amazon music) that are not automatically hibernated.
...the strange part is that they go to sleep with greenify just fine on my other devices, none of which runs cyanogen.
edit: just saw several google apps from the gapps package in the list as well.
same problem as yours automated hibernation not work.
[Lemmy] said:
Hi,
I'm running greenify (donation version) on a nexus 10 running CM13 release, and I can't get auto hibernation to work.
All i get from greenify are notifications listing apps that can be manually hibernated.
On my other devices (all rooted) auto hibernation works fine. Yes I do have root access turned on in CM13, and greenify has root access.
Any suggestions?
Cheers
[L]
Click to expand...
Click to collapse
Are you absolutely sure they don't hibernate after awhile? You probably have the setting "Quick Action Notification" turned on and that is what you are seeing? I have both the Nexus 4 and 7 running CM13 and hibernation works on them just fine, however the notification does show the option of manual hibernation as well. I don't worry about it anymore and let Greenify deal with it.
On a side note, I noticed the beta update yesterday does keep my devices "dozing" better.
colin p said:
Are you absolutely sure they don't hibernate after awhile? You probably have the setting "Quick Action Notification" turned on and that is what you are seeing? I have both the Nexus 4 and 7 running CM13 and hibernation works on them just fine, however the notification does show the option of manual hibernation as well. I don't worry about it anymore and let Greenify deal with it.
On a side note, I noticed the beta update yesterday does keep my devices "dozing" better.
Click to expand...
Click to collapse
*facepalm*
thanks! that's what that was.
Greenify can't auto hibernate apps in Xiaomi Redmi Note 4 running the latest Miui version 9.2.1.0 (details attached in screenshot below).Even after granting all the permissions, Greenify fails to click the force stop button & no apps are hibernated.
This is a major bug and leaves Greenify completely non functional in non rooted phones.
This issue must be fixed ASAP!
Video which shows that Greenify doesn't hibernate apps (CHECK VIDEO FOR COMPLETE INFO) :- https://drive.google.com/file/d/1H3h1118X4WXwmeBDNLL0nHiVEkGyWsjH/view?usp=drivesdk
Screenshot of device details attached below.
Please check and revert.
Thanks
Screenshot Of Device details attached below
KauG said:
Greenify can't auto hibernate apps in Xiaomi Redmi Note 4 running the latest Miui version 9.2.1.0 (details attached in screenshot below).Even after granting all the permissions, Greenify fails to click the force stop button & no apps are hibernated.
This is a major bug and leaves Greenify completely non functional in non rooted phones.
This issue must be fixed ASAP!
Video which shows that Greenify doesn't hibernate apps (CHECK VIDEO FOR COMPLETE INFO) :- https://drive.google.com/file/d/1H3h1118X4WXwmeBDNLL0nHiVEkGyWsjH/view?usp=drivesdk
Screenshot of device details attached below.
Please check and revert.
Thanks
Click to expand...
Click to collapse
Not sure of your expectations or what you are trying to show with the video. Greenify does not remove apps from storage nor immediately reduce their memory footprint (although they may happen over time due to normal LMK behavior). It's singular purpose is to block unwanted background behavior without crushing functionality.
While you may have indeed identified a new 'bug' a single data point (your device) does not necessarily extend to all devices and configs - rooted or otherwise.
Davey126 said:
Not sure of your expectations or what you are trying to show with the video. Greenify does not remove apps from storage nor immediately reduce their memory footprint (although they may happen over time due to normal LMK behavior). It's singular purpose is to block unwanted background behavior without crushing functionality.
While you may have indeed identified a new 'bug' a single data point (your device) does not necessarily extend to all devices and configs - rooted or otherwise.
Click to expand...
Click to collapse
Yes brother.I know that Greenify doesn't remove apps from storage but what I'm trying to show here is that when you click on Hibernate Now, Greenify force closes the apps but in this case it fails to do the same.I am not the sole user facing this issue.
This problem has popped up after the latest miui update.
Thanks again
Kaushik
KauG said:
Yes brother.I know that Greenify doesn't remove apps from storage but what I'm trying to show here is that when you click on Hibernate Now, Greenify force closes the apps but in this case it fails to do the same.I am not the sole user facing this issue.
This problem has popped up after the latest miui update.
Thanks again
Kaushik
Click to expand...
Click to collapse
Appreciate the clarification (might want to shorten and/or annotate the video). So you claim the "problem" is related to the latest miui update but then extend the claim to all unrooted phones and demand Greenify "revert" ... to what?
I do see others raising issues with accessibility based functionality and there may indeed be a link. So far none have stated Greenify flat out does not work, only that automatic hibernation doesn't take place the screen is turned off.
Let's see how this plays out as more reports filter in.
Davey126 said:
Appreciate the clarification (might want to shorten and/or annotate the video). So you claim the "problem" is related to the latest miui update but then extend the claim to all unrooted phones and demand Greenify "revert" ... to what?
I do see others raising issues with accessibility based functionality and there may indeed be a link. So far none have stated Greenify flat out does not work, only that automatic hibernation doesn't take place the screen is turned off.
Let's see how this plays out as more reports filter in.
Click to expand...
Click to collapse
Yes!You are correct.In a nutshell with the latest Miui Update (9.2) , Greenify doesn't hibernate the apps after screen lock even after being granted all the required permissions.
This happens in non-rooted devices
Hope that we will find a fix soon
Thanks a lot!
Kaushik
Turn Off MIUI Optimisation
I had same problem on my Mi Max 2 after MIUI update. To solve it just disable MIUI optimization under developer settings and reboot, Greenify will work again as it used to work before MIUI update.
KauG said:
Yes!You are correct.In a nutshell with the latest Miui Update (9.2) , Greenify doesn't hibernate the apps after screen lock even after being granted all the required permissions.
This happens in non-rooted devices
Hope that we will find a fix soon
Thanks a lot!
Kaushik
Click to expand...
Click to collapse
Check v3.9.5 on Play Store. It seems to have the solution for your issue.
jai220 said:
I had same problem on my Mi Max 2 after MIUI update. To solve it just disable MIUI optimization under developer settings and reboot, Greenify will work again as it used to work before MIUI update.
Click to expand...
Click to collapse
Thanks!
This solved the problem!
tnsmani said:
Check v3.9.5 on Play Store. It seems to have the solution for your issue.
Click to expand...
Click to collapse
Thanks!
This solved the problem!
jai220 said:
I had same problem on my Mi Max 2 after MIUI update. To solve it just disable MIUI optimization under developer settings and reboot, Greenify will work again as it used to work before MIUI update.
Click to expand...
Click to collapse
Are you able to grant special ADB Permissions via Pc brother in non rooted Mi device?
In my case,with usb debugging enabled and all permissions granted,I get an error saying "Neither user 2000 nor......."
Kindly help
Thanks
V 3.9.5 does not work on redmi note 3 (miui9)
I noticed this the hibernate now does not works because Xiaomi change force stop button layout.
Yes Sir correct it doesn't work in note 3
KauG said:
Are you able to grant special ADB Permissions via Pc brother in non rooted Mi device?
In my case,with usb debugging enabled and all permissions granted,I get an error saying "Neither user 2000 nor......."
Kindly help
Thanks
Click to expand...
Click to collapse
Me and others in MIUI forums had the same problem with only USB debugging turned on, this is what solved it:
Turn on the following option:
USB debugging -Debug mode when USB is connected
Install via USB -Allow installing apps via USB
USB debugging (Security Settings)- Allow granting permissions and simulating input via USB debugging
It's very simple
1 . Turn off miui optimisation under developer settings
2 . Turn on " FORCE ALLOW apps on external "under
developer settings.
bit.ly/2JXpR7s
Watch this ,
I think this will surely fix your problem.
I'm on xiaomi redmi note 5 pro (india) with miui 10.0.1
0. I'm having the same issue that greenify is not at all able to click the force stop option in the app page in the settings. This renders greenify completely useless in my device, since hibernation isn't working at all. I've been using greenify from last 5 years, and never faced an issue until now.
akhu5 said:
I'm on xiaomi redmi note 5 pro (india) with miui 10.0.1
0. I'm having the same issue that greenify is not at all able to click the force stop option in the app page in the settings. This renders greenify completely useless in my device, since hibernation isn't working at all. I've been using greenify from last 5 years, and never faced an issue until now.
Click to expand...
Click to collapse
I really don't understand why you are using Greenify to go to an app and click force stop ... Why not just go directly to the MIUI settings and force stop it there ?
Anyway, on all my 4 Xiaomis, with the latest and greatest MIUI 10 8.9.2 Developer ROM as at this date, Greenify works perfectly.
Apps under Hibernation are as expected when viewed from the MIUI Settings, they are already Force Closed (Force Close button greyed out), with the Uninstall button available (not greyed out).
Under MIUI Settings, apps under Shallow Hibernation are not Force Closed, and clicking on the button Force Close will force close it and the button becomes greyed out, and after that, the Uninstall button will be ungreyed and available. When you go back to Greenify, the previously shallow hibernated app that was force closed is now under the section of the normal hibernation, no longer under shallow hibernation.
All fine on my side, MM and Nougat Xiaomis, I don't know about Oreo. I think Greenify is still needed for Xiaomi with Oreo, since Xiaomi seems to walk a different path than the others.
hyborian said:
I really don't understand why you are using Greenify to go to an app and click force stop ... Why not just go directly to the MIUI settings and force stop it there ?
Anyway, on all my 4 Xiaomis, with the latest and greatest MIUI 10 8.9.2 Developer ROM as at this date, Greenify works perfectly.
Apps under Hibernation are as expected when viewed from the MIUI Settings, they are already Force Closed (Force Close button greyed out), with the Uninstall button available (not greyed out).
Under MIUI Settings, apps under Shallow Hibernation are not Force Closed, and clicking on the button Force Close will force close it and the button becomes greyed out, and after that, the Uninstall button will be ungreyed and available. When you go back to Greenify, the previously shallow hibernated app that was force closed is now under the section of the normal hibernation, no longer under shallow hibernation.
All fine on my side, MM and Nougat Xiaomis, I don't know about Oreo. I think Greenify is still needed for Xiaomi with Oreo, since Xiaomi seems to walk a different path than the others.
Click to expand...
Click to collapse
I have over 200 apps in my phone. So there are a lot of apps that need to be 'greenified'. And I've noticed that if you go into developer settings and disable 'miui optimisations', then greenify works perfectly. But for the rest, even if the app is open in the background and you select the option to hibernate it, the force close button is greyed out and nothing happens
akhu5 said:
I have over 200 apps in my phone. So there are a lot of apps that need to be 'greenified'. And I've noticed that if you go into developer settings and disable 'miui optimisations', then greenify works perfectly. But for the rest, even if the app is open in the background and you select the option to hibernate it, the force close button is greyed out and nothing happens
Click to expand...
Click to collapse
Oh, yes, I forgot, of course I have MIUI OPtimizations disabled, always, less problems for me. All rooted too, with Greenify4Magisk, and some module to allow Play Services to be dozed.
Well, if an app cannot be force closed in the MIUI settings, then it is something else preventing it from being closed, and Greenify cannot override it. Gboard (Google Keyboard if used) I think is an example, if I remember. Only a few, and system apps which I would not touch anyway. I don't greenify important user message apps like Messenger or Whatsapp, though, I also Whitelist them from deep doze, just playing safe.
Excluding system apps, I have only a few user apps, less than 40 for sure. All greenified except a few I don't want greenified. As for system apps,
I froze many of them that I will never use and safe to freeze of course, surely stronger than doze or hibernate.
akhu5 said:
I have over 200 apps in my phone. So there are a lot of apps that need to be 'greenified'. And I've noticed that if you go into developer settings and disable 'miui optimisations', then greenify works perfectly. But for the rest, even if the app is open in the background and you select the option to hibernate it, the force close button is greyed out and nothing happens
Click to expand...
Click to collapse
hyborian said:
Excluding system apps, I have only a few user apps, less than 40 for sure. All greenified except a few I don't want greenified. As for system apps, I froze many of them that I will never use and safe to freeze of course, surely stronger than doze or hibernate.
Click to expand...
Click to collapse
Ridiculous and counterproductive greenifying a huge app suite. Focus on those that demonstrate bad behaviors; ignore the rest.