Hi,
I recently installed Greenify on my Pocophone F1 /MIUI 10.3 on which I have already Tasker.
For Tasker, I have removed all battery restrictions so it is never optimized and it is fine. If I stop it manually, then for I don't know which reason accessibility and notification services get disabled so I have to enable them again.
The problem since I installed Greenify is that although Tasker is not part of the apps to hibernate, after some time when the screen is off, the same services get disabled on Tasker, exactly as if Tasker was forced to stop. So I am wondering why Greenify acts like this and how to prevent it? Isn't there any kind of whitelist?
I have not changed any default setting in Greenify.
Any idea what is happenning?
Thx.
Related
I often see a few apps running in the background and wonder why they are not Grenified. This happens to me most with YouTube, Google Drive & Titanium Backup. There doesn't seem to be a reason why they should run in the background, thus I'd expect them to be hibernated by Greenify.
I have a rooted LG L7 II device running CM11.
Digdis said:
I often see a few apps running in the background and wonder why they are not Grenified. This happens to me most with YouTube, Google Drive & Titanium Backup. There doesn't seem to be a reason why they should run in the background, thus I'd expect them to be hibernated by Greenify.
I have a rooted LG L7 II device running CM11.
Click to expand...
Click to collapse
Did you Greenify those apps? I had to ask since you didn't specifically say so. Also, is Greenify enabled in Device Administrators and Accessibility settings? And are you running Greenify in Root mode or Boost mode?
tnsmani said:
Did you Greenify those apps? I had to ask since you didn't specifically say so. Also, is Greenify enabled in Device Administrators and Accessibility settings? And are you running Greenify in Root mode or Boost mode?
Click to expand...
Click to collapse
Thanks. Gotta to admit that I didn't Greenify them manually, but waited for Greenify to do it automatically. I now sent them manually to hibernation and will keep track on whether they run in the background as they did before.
However, isn't the whole point behind Greenify that you don't need to do it manually, but let Greenify do that for you? AFAIK, neither of these apps have anything to do in the background, so isn't Greenify supposed to notice that and send them to hibernation?
Digdis said:
Thanks. Gotta to admit that I didn't Greenify them manually, but waited for Greenify to do it automatically. I now sent them manually to hibernation and will keep track on whether they run in the background as they did before.
However, isn't the whole point behind Greenify that you don't need to do it manually, but let Greenify do that for you? AFAIK, neither of these apps have anything to do in the background, so isn't Greenify supposed to notice that and send them to hibernation?
Click to expand...
Click to collapse
Greenify doesn't automatically greenify(!) any app. There are many apps running in the background, some required, some not required. So you make the choice to greenify whatever you choose to, depending on your requirements. This is because if you greenify all the apps running in the background, you will lose some functionality. While you may choose to greenify one particular app because you don't need it to run in the background, I may not agree with you since I may require its functionality. So to each his own. That is the beauty of Greenify, that it allows you to choose.
However, once you greenify a particular app, Greenify takes over and further greenifying that app is automatic.
tnsmani said:
Greenify doesn't automatically greenify(!) any app. There are many apps running in the background, some required, some not required. So you make the choice to greenify whatever you choose to, depending on your requirements. This is because if you greenify all the apps running in the background, you will lose some functionality. While you may choose to greenify one particular app because you don't need it to run in the background, I may not agree with you since I may require its functionality. So to each his own. That is the beauty of Greenify, that it allows you to choose.
However, once you greenify a particular app, Greenify takes over and further greenifying that app is automatic.
Click to expand...
Click to collapse
Thanks for your answer. I did Greenify apps manually in the past, ones that I considered their running in the background as unnecessary (such as a shopping app I had which kept notifying me of new deals). However, I thought that Greenify could somehow identify apps who run in the background without need, and so it would send them to hibernation automatically. Guess I was wrong here.
auto hibernate when app is closed : eg. FB, music players many other apps & services stay on even no need after closing.
If anybody know how to auto stop these with other apps or tricks, plz let me know!?
Per App Hacking doesn't help..
------
auto start when screen is on : eg. I don't need clean master to stay on when I'm not on wifi and screen is off.
again, any workaround for this?
Greenify is already the greatest app out there, but if it had these features, it would b God of apps IMHO
kennyk09 said:
auto hibernate when app is closed : eg. FB, music players many other apps & services stay on even no need after closing.
If anybody know how to auto stop these with other apps or tricks, plz let me know!?
Per App Hacking doesn't help..
------
auto start when screen is on : eg. I don't need clean master to stay on when I'm not on wifi and screen is off.
again, any workaround for this?
Greenify is already the greatest app out there, but if it had these features, it would b God of apps IMHO
Click to expand...
Click to collapse
I think that you have not understood the working of Greenify correctly. It comes into play for hibernation only after the screen is off. When screen is on, it merely collects info about the apps that are running, closed etc to determine which apps are to be hibernated once screen is off.
Reg. auto hibernation, do you have root and have you enabled it in Device Administrator and Accessibility under Settings? Under which mode are you running Greenify: Root, Boost or Unrooted? And have you enabled Auto hibernation within Greenify and selected the apps to be greenified?
Check the thread title
tnsmani said:
I think that you have not understood the working of Greenify correctly. It comes into play for hibernation only after the screen is off. When screen is on, it merely collects info about the apps that are running, closed etc to determine which apps are to be hibernated once screen is off.
Reg. auto hibernation, do you have root and have you enabled it in Device Administrator and Accessibility under Settings? Under which mode are you running Greenify: Root, Boost or Unrooted? And have you enabled Auto hibernation within Greenify and selected the apps to be greenified?
Click to expand...
Click to collapse
It's a wish list. you don't understand what wish list is?
I fully understand how Greenify works.
Use Tasker and task kill plugin.
And for Greenify create hibernate shortcut and don't forget that it won't hibernate of application is in recent Apps list.
It's easy to kill every app on exit.
Just use LMT(PIE) app , and instead of standard ''home, or back button'' use ''KILLAPP'' button from PIE menu.
In combination with greenify it works fine.
I was think to use only PIE(pie ''kill app process'' on exit), but this is not the same, greenify realy put this apps in hibernation.
So i must use combination of these 2.
Would be great, that greenify do this itself..
Hi,
I noticed that Greenify has it's own persistent service (Wake-up Monitor) that occupies RAM.
I don't have auto hibernation enabled or anything like that, but it's still running.
These services are exactly why I ended up using Greenify in the first place... Is this a bug?
Thanks.
Hi, Greenify keeps losing access to the accessibility service for some reason. It happens after a few minutes of using the phone, not even a reboot is required to get it unticked again. Then when I try to hibernate+lock screen again, it says that it requires the service for automation to work.
Phone: Huawei Mate 7
System: KitKat 4.4.4
Greenify: latest version
Root? No (Greenify set on non-root mode)
Accessibility activated for Greenify? Yes but keeps getting unticked all the time and asks me to enable automation again and again!
Greenify device administrator? Yes
Donation package? Yes.
Anyone?
Have you noticed any clue on when and what caused the stop of accessibility service?
If you device memory is running low, it may be killed by Android system for more memory for foreground app, especially when playing large game.
oasisfeng said:
Have you noticed any clue on when and what caused the stop of accessibility service?
If you device memory is running low, it may be killed by Android system for more memory for foreground app, especially when playing large game.
Click to expand...
Click to collapse
No it does it all the time, after a few minutes usually. If I lock the screen within a minute or two, it works fine, it later than that, the hibernation service is normally turned off already.
Other Info
Any other updates on this issue? I was running Greenify on my Galaxy S5 with no issues. I just changed over to an S6 Edge and now I'm getting the same problem with Greenify losing its Accessibility permissions. No rhyme or reason for when it happens. I'm not running any big applications or games. I have a few other apps that need Accessibility authorization and those never seem to lose their access like Greenify does.
Same Problem on my new Galaxy S6 edge. Any help to solve the problem would be greatly appreciated.
This can solved by removing Greenify from Protected Apps or in the case of non Huawei phones by disabling battery optimisation for greenify or the app in question.
On my phone gets it often after I kill the any application with /long press/back button. Rooted, CM13
this happen as well with OOS 3.2.1 on OnePlus 3
if you decide to clear recents and the memory as well, it will straight away losing the accesibility access..
Is there an established reason for this?! Reinstalling and add power-saving exception doesn't seem to being helpful.
Issue started after update to android 8. On previous versions never had a tiny problem.
Sent from taptalk
I have greenify installed on xiaomi redmi note 4 snapdragon (mido) on lineageOS 13 with xposed(v87) module enabled and donation apk installed. There is a weird error happening with greenify installed. Whenever I open shareit app to send something, it freezes as soon as it tries to discover greenify on app tab. There after it stops responding until it Force closes/crashes.
This problem is specific to greenify v3.6.x and upto 3.5.2 everything works smooth. Following features as enabled-
1. xposed module
2. aggressive doze
3. wake up tracing and cut off
4. automated hibernation
5. xposed settings - doze on go, wake up coalescing, telephony wake up, dont remove notification, block app state abuse, GCM push.
Please consider looking into it as shareit is really useful app and i dont seem to use it.
Although on nougat shareit and greenify behaves properly.
souravipc53 said:
I have greenify installed on xiaomi redmi note 4 snapdragon (mido) on lineageOS 13 with xposed(v87) module enabled and donation apk installed. There is a weird error happening with greenify installed. Whenever I open shareit app to send something, it freezes as soon as it tries to discover greenify on app tab. There after it stops responding until it Force closes/crashes.
This problem is specific to greenify v3.6.x and upto 3.5.2 everything works smooth. Following features as enabled-
1. xposed module
2. aggressive doze
3. wake up tracing and cut off
4. automated hibernation
5. xposed settings - doze on go, wake up coalescing, telephony wake up, dont remove notification, block app state abuse, GCM push.
Please consider looking into it as shareit is really useful app and i dont seem to use it.
Although on nougat shareit and greenify behaves properly.
Click to expand...
Click to collapse
Try disabling aggressive doze. It buys little/nothing in battery savings while introducing a host of other issues. May or may not fix your specific issue but easy enough to try. Toss in a reboot after twiddling the setting to insure a clean test.