This is the first beta version of Greenify 2.7. This major version is aimed to improve the over-all user experience in every aspect (if possible).
Beta 8
Fixed the detection for background active app on Android 5.1.1_r9 and 6.0, with new implementation.
Fixed crash on Android 4.0.x.
Simplified the confusing state reason of postponed hibernation.
Beta 7
Fixed crash during auto-hibernation in non-root mode.
Beta 6
Due to a permission change in the newest revision of Android 5.1.1 and 6.0, Greenify has to use the usage stats permission to detect the foreground app and avoid hibernating it. Unfortunately, this new implementation could no longer detect the active background apps (such as music player).
Improved compatibility with Android 6.0.
FIX: Xposed feature settings lost issue on arm64.
Beta 5
Foreground app no longer hibernates even if "state always ignored" is checked.
Reduced the impacts of wake-up cut-off.
FIX: Native processes cleaning.
FIX: Wake-up action in Tasker plug-in on Android 5.x.
FIX: No longer list disabled apps.
Beta 4
Fixed the reboot issue in root mode if core system app is greenfied.
Beta 3
Greenify now cleans up native processes after hibernation, to prevent self-reviving.
Fixed root mode on Android 4.0 & 4.1.
Fixed non-root mode on Android M.
No longer pause auto-hibernation when charging.
Beta 2
Fixed the manual hibernation not working issue when charging. (introduced in beta 1)
Beta 1
Dim the screen when performing auto-hibernation on non-root device.
Auto-hibernation will pause when external power is connected.
"Hibernate and Lock Screen" shortcut does not require device-admin privilege activated, and is now compatible with Smart Lock on Android Lollipop & M. (root-only)
Experimental support for Android M Developer Preview, with new "Shallow Hibernation" - application context and push notification are all preserved in hibernation.
Click to expand...
Click to collapse
About Android M support (experimental)
Since Android M is still in early developer preview stage, anything could change before the final version is out. So is the experimental support in Greenify.
Greenify now takes advantage of App Standby feature in Android M and combine it with the efforts of traditional implementation to create a new "Shallow Hibernation" state for greenified apps. In this state, app won't lose the context before being switched to the background and could also receive GCM push message in hibernation.
Known issues
The "... Lock Screen" shortcut with new implementation is reacting slower than before in some lower end device, due to slow root invocation.
Get beta versions
Opt-in to beta channel or download the apk file.
Please apk file Greenify v2.7 beta 1 ..
http://www13.zippyshare.com/v/HAwp78U6/file.html
Any changes for LP? or for M only?
aeonix_05 said:
Any changes for LP? or for M only?
Click to expand...
Click to collapse
Only the first one is for Android M.
cenzo1996 said:
Please apk file Greenify v2.7 beta 1 ..
Click to expand...
Click to collapse
Link is now provided in OP.
@oasisfeng Thanks for the update. Working fine but the problem that the notifications don't get delivered unless the screen is turned on manually remains on LP. Greenify shows as push received "x" minutes ago but no notification sound or anything related when phone screen is off.
nice
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
Yup, I have that problem too. The toast says hibernated but they actually don't get hibernated.
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
+1 for Samsung Galaxy S6 android 5.0.2 root
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
+1
Sent from my SM-G900F using Tapatalk
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
Same here. S4 with S6 featured ROM.
Gesendet von meinem Nexus 7 WiFi mit Tapatalk
Sony Z1c LP 5.0.2 too . I am back on the last version now.
Gesendet von meinem D5503
ottomanrage said:
@oasisfeng Thanks for the update. Working fine but the problem that the notifications don't get delivered unless the screen is turned on manually remains on LP. Greenify shows as push received "x" minutes ago but no notification sound or anything related when phone screen is off.
Click to expand...
Click to collapse
I'm sorry, I still can't figure out the cause of that issue yet. It seems like only affect some apps in some situations. This combination is not clear in any form.
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
Which Android version and device model? What working mode?
oasisfeng said:
I'm sorry, I still can't figure out the cause of that issue yet. It seems like only affect some apps in some situations. This combination is not clear in any form.
Click to expand...
Click to collapse
Thanks for the reply. For me it's mostly in whatsapp and viber. I have the logs for the GCM push if you need. And it happens everytime. Basically in all situations.
And as for the latest beta update, I have an I9300 running 5.1.1 with boost mode (xposed).
oasisfeng said:
Which Android version and device model? What working mode?
Click to expand...
Click to collapse
android 5.0.2 SAMSUNG GALAXY S6
ottomanrage said:
Thanks for the reply. For me it's mostly in whatsapp and viber. I have the logs for the GCM push if you need. And it happens everytime. Basically in all situations.
And as for the latest beta update, I have an I9300 running 5.1.1 with boost mode (xposed).
Click to expand...
Click to collapse
I have collected many logs in the past months. But both Google Play services and these apps are closed source. Logs are not enough to figure out why they can't post notifications even if push message was received.
Several attempts have been made trying to fix the issue, but still no luck yet.
Maybe they are not prepared to receive push message in hibernation state.
gALEXyS4 said:
I have a slight problem with the newest version: Any app that happens to be awake when I open Greenify just stays awake. At the moment Google App, Google Play Store, ACalendar Plus and Weather don't wanna get closed, they just stay persistently. If I press to hibernate them, I get a toast message that they're hibernated, but they are not... Now I don't know whether it's an error of function or of displaying
Click to expand...
Click to collapse
Have you connected external power to the device? If so, that's because Greenify will not perform auto-hibernation during charging since this version. The incorrect prompt information is the known issue I've listed in the OP. I'll add more clear prompt for this.
all ok with hypernate here
Related
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)
Greenify "greenifies" applications that are in active use, for example Google Maps that I use for navigation and music streaming and player apps like Deezer and Vanilla Music. By "foreground" I mean that the application is currently in use, I don't go back to home screen. I just turn of my screen to save battery. Music playback cuts off after a minute or so and the only solution is to "degreenify" all music player apps. Google Maps will reset shortly when my screen turns off.
Is this how Greenify works?
The latest version with the donation package. [UNOFFICIAL] Xposed for Android 5.1 - API v64 / Alpha 4 / 20150514, HTC One M7. Xposed is enabled in the Greenify settings.
Greenify is designed to not hibernating the currently foreground app. Are you using any 3rd-party lock-screen app? It might interfere the recognition of foreground app.
oasisfeng said:
Greenify is designed to not hibernating the currently foreground app. Are you using any 3rd-party lock-screen app? It might interfere the recognition of foreground app.
Click to expand...
Click to collapse
Not to my knowledge. I'm on CyanogenMod 12.1.
I've experienced similar behavior for quite some time as well, on my Nexus 5 (LP 5.1.1, although I believe the issue goes back to at least 5.0). I am not running a custom lockscreen, nor can I think of anything that would steal the foreground.
Was Greenify compatible with the Unofficial Xposed for Lollipop 5.1 before the today's update?
I only tested a bit, but Greenify seems to be working correctly now :victory:
I'm currently having this same problem with Google music and greenify
Sent from my LG-D851 using Tapatalk
Same problem.
All apps are hibernated after some minutes of screen off.
Before this bug: runtastic and music player active while jogging -> screen off -> all apps beside those too get hibernated
Now: runtastic and music player active -> screen off -> ALL apps get hibernated
Please fix it.
I think it's cm12.1 related.
Tried with Greenify 2.6.2 and 2.7.x all betas.
Still the same.
iamnotkurtcobain said:
Same problem.
All apps are hibernated after some minutes of screen off.
Before this bug: runtastic and music player active while jogging -> screen off -> all apps beside those too get hibernated
Now: runtastic and music player active -> screen off -> ALL apps get hibernated
Please fix it.
I think it's cm12.1 related.
Tried with Greenify 2.6.2 and 2.7.x all betas.
Still the same.
Click to expand...
Click to collapse
Can we use a previous version and it will work?
Sent from my LG-D851 using Tapatalk
Dibsbighead said:
Can we use a previous version and it will work?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Doesn't seem so.
Same problem here after updating my rom yesterday. It must be caused by a CM commit between the 10th and yesterday. Even apps with persistant notifications are being greenified.
an0n981 said:
Same problem here after updating my rom yesterday. It must be caused by a CM commit between the 10th and yesterday. Even apps with persistant notifications are being greenified.
Click to expand...
Click to collapse
Please help @oasisfeng
Greenify isn't usable this way
Very same issue here. the cyanogenmod update is the reason i feel.
At this point greenify is almost unusable.
Was okay till i updated my cm to 20150816 from 20150811...
someone please post a fix if any available at all...
joker_you2007 said:
Very same issue here. the cyanogenmod update is the reason i feel.
At this point greenify is almost unusable.
Was okay till i updated my cm to 20150816 from 20150811...
someone please post a fix if any available at all...
Click to expand...
Click to collapse
It's really unusable at the moment. And I don't wanna downgrade to an older nightly (stagefright issue,...)
Same problem here!
I do not know whether this is related to recent CM updates, but I am also running Greenify on CyanogenMod 12.1 (20150816 nightly on LG D855) and Greenify is hibernating Spotify while it is playing (despite it's ongoing event notification). Both Greenify latest stable and latest beta versions have this issue (I was running stable and then updated to beta while trying to resolve this issue).
There is no need to hibernate Spotify.
Sent from my bacon!!!!!
Saving RAM and preventing Spotify from spawning up Facebook is a reason for me to hibernate it.
NickosD said:
There is no need to hibernate Spotify.
Sent from my bacon!!!!!
Click to expand...
Click to collapse
I also have the problem with greenify hibernating running apps like radio player and strava. Also using Cm12.1, nightly 2608. Was working fine until about a week ago.
The issue has been fixed in version 2.7 beta 8.
Many thanks to @oasisfeng for quick solution!
I get the "app is not installed" error when updating to the newest beta.
The older versions don't have the fix what I'm looking for.
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 XDA Community,
I have recently flashed Cyanogenmod 13 after performing a clean Factory Reset on my OnePlus One. More details at the end of the post. However, Greenify is now unable to cut off wakeup paths of greenified apps, which worked fine before on Cyanogenmod 12.1.
The phone is rooted, Greenify has been granted Superuser rights by SuperSU and is entered as a device administrator under Settings -> Security -> Device Administrators. Greenify - Automated Hibernation under Settings -> Accessiblity was usually set to off, as Greenify shouldn't need that when rooted as far as I'm aware, but I have now turned it on. Still no change. "Draw over other apps" is set to "Yes" for Greenify.
Greenify is running in Boost mode, all Xposed-based features are enabled. Greenify is checked in the Modules section of the Xposed Installer app. Google Play Services and Google Now are permanently on and Greenify shows their status as "Working".
I found the cut off wakeup path feature really useful and would like to use it again.
Could anyone help me with that, please?
Thanks in advance!
Greenify version: 2.8.1 with Donation Package, both from Google Play Store. Legally bought, purchase verification works.
Xposed Framework version: xposed-v82-sdk22-arm
OS: Cyanogenmod 13, cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon to be precise
Device: OnePlus One
@Neehlanfyr
The title of the thread is not correct. Cut off wake-up paths works in 6.0.1. I don't know about its working with CM but in my ROM it is working.
When an app is in "working" state, you will not get the option to cut off wake-up path. It needs to be in "pending hibernation" list for that. And it has to be clicked and not long pressed.
tnsmani said:
@Neehlanfyr
The title of the thread is not correct. Cut off wake-up paths works in 6.0.1. I don't know about its working with CM but in my ROM it is working.
When an app is in "working" state, you will not get the option to cut off wake-up path. It needs to be in "pending hibernation" list for that. And it has to be clicked and not long pressed.
Click to expand...
Click to collapse
Hi tnsmani,
thanks for responding. The thread's title is correct, as I can not cut off wakeup paths on my Android 6.0.1 device. I know very well that it should generally work, but it does not for me, which was my reason for opening this thread. I am looking for a solution that allows me to use this functionality again. To be more precise: I can't cut off the wakeup path of any greenified app, regardless of its condition/status. I forgot to mention that in the opening post, sorry.
The "scissors button" just isn't showing. I have used this feature before on Android 5.1, 5 and 4.4 and if it hasn't been changed radically, I should still know how to use it.
Best regards,
Neehlanfyr
Neehlanfyr said:
Hi tnsmani,
thanks for responding. The thread's title is correct, as I can not cut off wakeup paths on my Android 6.0.1 device. I know very well that it should generally work, but it does not for me, which was my reason for opening this thread. I am looking for a solution that allows me to use this functionality again. To be more precise: I can't cut off the wakeup path of any greenified app, regardless of its condition/status. I forgot to mention that in the opening post, sorry.
The "scissors button" just isn't showing. I have used this feature before on Android 5.1, 5 and 4.4 and if it hasn't been changed radically, I should still know how to use it.
Best regards,
Neehlanfyr
Click to expand...
Click to collapse
Still the title is not correct. It should have been "on CM13" instead of "on Android 6.0.1"
Same problem here
My device is moto g (xt1033) running cm 13(based on Android 6.0.1). To be precise 06-08 nightly. Greenify version is 2.8 beta 3. Xposed version v86 sdk 23. The scissors icon doesn't even show up when I select an app which is listed for hibernation.
Yeshu94 said:
My device is moto g (xt1033) running cm 13(based on Android 6.0.1). To be precise 06-08 nightly. Greenify version is 2.8 beta 3. Xposed version v86 sdk 23. The scissors icon doesn't even show up when I select an app which is listed for hibernation.
Click to expand...
Click to collapse
You can update to the stable 2.9 version and check.
The scissors icon will appear only if a hibernated app is woken up by another app/process.
tnsmani said:
You can update to the stable 2.9 version and check.
The scissors icon will appear only if a hibernated app is woken up by another app/process.
Click to expand...
Click to collapse
It seems that since v2.9 beta4, there is no scissors icon any more. So I have to use beta3 now.
wyc said:
It seems that since v2.9 beta4, there is no scissors icon any more. So I have to use beta3 now.
Click to expand...
Click to collapse
thank you for the info buddy
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.