Related
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.
@oasisfeng
I searched a bit and I kept finding conflicting info regarding the interaction between greenify and GCM-Push notifications on Android Marshmallow without xposed. From here the developer states that " GCM push should work for all hibernated apps once their developer adopt the new GCM priority policy required by Android 6.0. No more Xposed framework needed for GCM push!", however all over the google+ community and here at xda it is said that that option works only with xposed installed in fact it can't be enable without having xposed. Therefor is it implemented in the app inherently? or is it still a "project"?
I want only a clarification on this matter to better understand if i have to greenify the social apps or not (I need their notification even if not received ASAP).
You raise a good point. I'd like to know this as well. I had to disable GCM function because of constant random reboots. So far, since disabling, I've not had a reboot but time will tell.
Sent from my Nexus 6 using Tapatalk
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.
Greenify 3.9.5 beta, Android 8.0, htc 10, magisk, xposed systemless
Just wanna make sure it wasn't my issue / permission issue..turned everything on, tried uninstall and reinstall.
Thank you for your developing!
29988122 said:
Greenify 3.9.5 beta, Android 8.0, htc 10, magisk, xposed systemless
Just wanna make sure it wasn't my issue / permission issue..turned everything on, tried uninstall and reinstall.
Thank you for your developing!
Click to expand...
Click to collapse
All three, Enhanced Wake-up Tracker, Wake-up Cut-off and Advanced Wake-up Cut-off, are enabled in mine. But I had to repeatedly enable/disable them initially for them to be enabled.
tnsmani said:
All three, Enhanced Wake-up Tracker, Wake-up Cut-off and Advanced Wake-up Cut-off, are enabled in mine. But I had to repeatedly enable/disable them initially for them to be enabled.
Click to expand...
Click to collapse
That was weird. I clicked so many times under many circumstances but unable to even enable it once.
All it showed was something like "mayyybe your rom is not supported"
I really want to cut off some notorious intent that get triggered via sharing/network state change/media scan...because they significantly slowed my device.
: (
Is there any logcat that I can provide to help @oasisfeng debugging?