I have been using Greenify for quite some time on a rooted HTC M8 without issue, and I very much like the software and its associated battery savings (I contributed to the donation mode as soon as it appeared). Recently I updated my phone to the LG G4 and was pleased to learn that Greenify would work without root as there is not a reliable root method available for this phone.
My only issue with greenify has been that intermittently (from several times a day to once every couple days) the home screen wallpaper is replaced with the apps property window of one of the apps which is being greenified (see attached screen capture). The phone functions normally otherwise, and when I restart the phone the normal background is back.
Phone Specifics:
Sprint LG G4 LGLS991 (NO ROOT)
Android 5.1
Kernel 3.10.49
Greenify version 2.6.2
Experimental Settings
Working Mode: Non-root
Automated Hibernationn
Greenifying System Apps (limited)n
rest of experimental settings are off
Any advice to resolve this issue would be greatly appreciated
Thank You
Keith Kronemer
I'm sorry I can't offer any help but I have exactly the same issue on an non-rooted, Verizon LG G4 Android 5.1 phone.
I assume I have some settings wrong but I just don't know what they could be.
I have Greenify 2.71 and Greenify (Donation Package) 2.3; if that helps.
Your screen cap (original post above) is exactly what I see, 2 to 3 times per day and, like you, a phone restart returns it to normal operation until next time.
Thanks,
Gerry E.
LG G4 and Greenify
When Greenify locks the screen on my LG G4 I cannot open screen with a double tap, like I was able to in the past, I have to push the power button to be able to use my phone. I have Android 6.0, Greenify 4.1, non-rooted. Tried disabling Auto hibernation for manual, same problem. Have donation package (But can't find icon) . Love Greenify, used to work great but have to fix this problem. Please help.
jamesburgess said:
When Greenify locks the screen on my LG G4 I cannot open screen with a double tap, like I was able to in the past, I have to push the power button to be able to use my phone. I have Android 6.0, Greenify 4.1, non-rooted. Tried disabling Auto hibernation for manual, same problem. Have donation package (But can't find icon) . Love Greenify, used to work great but have to fix this problem. Please help.
Click to expand...
Click to collapse
Repost; responded here: https://forum.xda-developers.com/ap...automate-hibernate-auto-t3738150/post77169643
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.
So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
peste19 said:
So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
Click to expand...
Click to collapse
Do you have experimental mode enabled? I think you need the donation pack as well as root to greenify system apps.
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Has anyone noticed some improvements using greenify with s6?
peste19 said:
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Click to expand...
Click to collapse
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
isangelous said:
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
Click to expand...
Click to collapse
how did you use tasker to enable the hibernation? i am a bit new at this
peste19 said:
how did you use tasker to enable the hibernation? i am a bit new at this
Click to expand...
Click to collapse
I just had a look but unfortunately I don't have the profile anymore to export it for you.
Doing it from scratch would be a bit daunting if you have never used Tasker before.
You basically need to:
1. Set a variable for the display state (ie, on, off and unlocked). %DisplayState
2. Have a task for the screen unlock which sets a variable %NeedToGreenify or similar.
3. Have a task for the when screen off event triggers and %NeedToGreenify is set. This task waits 10 minutes. Then check if the screen is still off - this is what %DisplayState is for (Stop if it is not). Clear %NeedToGreenify. Trigger Hibernate (Greenify is a 3rd Party Plugin). Wait 30 seconds. Turn the screen off "SecureSettings - LockDevice".
I think I may have also used SecureSettings to keep the screen on while the process is running. You will also need to set the task options to "abort existing task" if it is already running.
I think this is how it worked, but it was a while ago :/
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
LG G3 MM (6.0) - Xposed
I found out today that two apps that are not set to hibernate are not functioning when the screen is off (maybe more).
1) Alarm - Didn't go off this morning
2) Security software didn't ding like usual
Just recently moved to MM but assuming this is a Greenify related matter
SyCoREAPER said:
LG G3 MM (6.0) - Xposed
I found out today that two apps that are not set to hibernate are not functioning when the screen is off (maybe more).
1) Alarm - Didn't go off this morning
2) Security software didn't ding like usual
Just recently moved to MM but assuming this is a Greenify related matter
Click to expand...
Click to collapse
Not likely as no one else has reported such behaviour.
Do you use Amplify or PowerNap? If so disable them one by one and see if the issue is resolved. If you don't have them, disable Greenify and check.
tnsmani said:
Not likely as no one else has reported such behaviour.
Do you use Amplify or PowerNap? If so disable them one by one and see if the issue is resolved. If you don't have them, disable Greenify and check.
Click to expand...
Click to collapse
Nope, only Greenify. Full disclaimer, everything worked prior to MM, and I just moved to MM so it may be doze and not greenify. I've tried excluding them in Doze to see if that fixes it.
update for anyone else.
Came across http://www.androidauthority.com/greenify-update-671216/
It appears I missed the whitelist under aggressive doze.
I have the same issue, my alarms aren't working, I'll try disabling amplify and greenify one at a time to see what it is.
On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
mermaidkiller said:
On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
Click to expand...
Click to collapse
Of course it does. The size/activity in this forum plus frequent mentions in respected publications over many years should offer some clues to its integrity. Whether it is working on your device is a different matter.
Greenify does best on rooted devices as unharnessed ROMs can both undo actions and/or misrepresent status. It's quite possible an app placed in hibernation was later woken via internal trigger that Greenify can not suppress on an unrooted device. In the case of Opera (my preferred browser) there is regular syncing of tabs and downloading of *cough* 'news' if you have those features enabled.
I also question info coming out of the "Android Assistant" app. On my device it claimed all apps had zero CPU...including itself. Also did not display system partitions correctly nor properly detect the sensor suite. Granted I only spent a few minutes poking around. Maybe some switches needed to be thrown.
Finally, you probably don't need Greenify on Oreo as Doze does a find job with power management.
planetera said:
Don't I really need Greenify on oreo? Is Doze on Oreo really that good? Can you confirm please? I've been always using Greenify but if I don't need it on Oreo, I'll remove it
Click to expand...
Click to collapse
Well don't take my word for it. Simply remove all apps from Greenify's hibernation list (hopefully there are not many there), observe device behavior over the next few days then make your own decision.
planetera said:
Well, thanks for information. Just made a quick research and everyone says Greenify is trash on Oreo. So I just uninstalled it. Thanks for heads up. Glad I've seen your comment
Click to expand...
Click to collapse
Trash? Err-no. I have it installed on every one of my devices for valid reasons. Needed for generic power management on Doze capable ROMs? Probably not (and as such serving no purpose). Enjoy your device.
planetera said:
ok, but, when Greenify hibernates an app, you don't get notificaton froms this app, but when Android itself hibernates the app, you still get notifications, how does these two compare?
Click to expand...
Click to collapse
It varies by app, developer approach and user settings. Many apps will experience delayed notifications with Doze while other punch right through. Greenify can be configured to permit notifications but only if the app utilizes GCM (Firebase). Aggressive doze, light hibernation, Xposed framework availability and several other variables contribute to notification behavior. If your head is spinning it should! End users should not need to know the contents of the underwear drawer. Best practice is to simply let Android do its thing without 3rd party tools unless one understands their behavior and application. At one time such tools were needed to achieve acceptable app/device performance and battery life. Not so today. Is such a simplistic solution 'optimal' form an enthusiasts point-of-view? Probably not. It is acceptable/reasonable from an end-user perspective? In most cases 'yes' yielding a good balance of performance and battery life with minimal interaction for those who simply want to enjoy their device vs. manage it. Good luck with whatever direction you choose.
Agree one hundred percent!
Greenify on Oreo is an appendage that is best left out in my opinion, since for most, Oreo itself manages the drain admirably. Though I have it installed, it is more by way of habit than necessity. I have experienced Oreo without Greenify and have no complaints.
Greenify is STILL works.
But its benefit on recent Android versions is not as prominent as on earlier versions.
Coz we already have Doze starting from Marshmallow.
It works for me. I have a samsung tab a 9.7 sm-t550 with an aicp 8.1 rom (lineageos based). Therefore it doesn't have the built-in samsung app device maintenance. I've also discovered a little trick to using greenify that I want to share. I use greenify with another app called shutapp. Shutapp is an app that helps you force stop apps running in the background. Except I don't do that. I use it solely for the purpose of having an accurate number of apps running in the background. Then I open the app to see which ones are running. Next I open greenify and hibernate them. I use this method, because I found that when you force stop the apps they will open back up again. Also, I use the widget from shutapp and not the floating bubble which requires extra permissions granted. The widget does the same thing without the extra permissions. This method I discovered has improved my ram and battery life drastically. I can tell because I use status bar mini pro to monitor my ram speed constantly. And finally I do have Xposed with the donation package of greenify, didn't want to leave that out. Not sure if it makes a difference or not, but wanted to be accurate. That's it, hope that works for somebody else, take care.
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
tnsmani said:
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
Click to expand...
Click to collapse
Greenify works just fine on recent Android builds. It is a tool that can be very beneficial when properly used to produce a specific outcome. That said, it is rarely needed on Android 6+ as doze handles most of the heavy lifting. Enjoy using your device vs trying to fix problems you haven't identified.