My android device is rooted with xposed framework installed and greenify xposed module enabled. What Greenify settings i can enable to make it perform at its best?
Peter770 said:
My android device is rooted with xposed framework installed and greenify xposed module enabled. What Greenify settings i can enable to make it perform at its best?
Click to expand...
Click to collapse
There is no right answer as every device and work flow is unique. That said, Aggressive Doze, Doze on the Go and Wakeup Timer Coalescing are popular choices with limited side effects. If you miss notifications or find your device lagging for a few seconds after wake disable Aggressive Doze. Resist the temptation to add every app/service to Greenify's action list; only target apps that demonstrate bad behaviors. If running Android 6+ doze will take care of most background activity w/o help from Greenify. It's a tool to address specific problems.
What is the difference between the three hibernation modes: default, normal hibernation, deep hibernation (by island)?
Peter770 said:
What is the difference between the three hibernation modes: default, normal hibernation, deep hibernation (by island)?
Click to expand...
Click to collapse
Default is whatever you set as the default in Greenify settings. Normal is what Android uses by default and is adequate for the vast majority of work flows. Deep requires an add on product (Island) and seems to be a solution looking for a problem. You could have discovered all this by searching the thread or reading documentation.
Peter770 said:
What is the difference between the three hibernation modes: default, normal hibernation, deep hibernation (by island)?
Click to expand...
Click to collapse
I absolutely concur to @Davey126's correct statement and recommendation, and I'm unable to add anything substantial. However, I like to share my settings (please refer to attached screenshots), and if interested and required I'll provide information, which of my applications are not greenified.
Regarding your question, at least from my point of view all settings are pretty well explained within Greenify but it's also worth to study the threads by @oasisfeng that are pinned to this Greenify forum.
Thanks, for the screenshots. It was helpful.
I have problem with some apps, like Nine email client, which won't hibernate. Why is that?
Peter770 said:
I have problem with some apps, like Nine email client, which won't hibernate. Why is that?
Click to expand...
Click to collapse
They might be woken up by other apps. If so, you can cut off the links using wakeup tracker option in Greenify's settings.
'Wake-up tracking and cut-off' option is enabled.
Peter770 said:
'Wake-up tracking and cut-off' option is enabled.
Click to expand...
Click to collapse
Merely enabling the option is not enough. You have to manually cut off the trigger. When an app which you greenified wakes up automatically and is shown in Greenify as pending hibernation, if you long press the app, it will show some info like which app or process triggered it and whether it is critical etc. Then you can click the three dot menu button at top right and choose to cut off the trigger using the scissor icon or to ignore its running state. Then it will remain hibernated. Be careful while choosing the options since it may have unwanted side effects. Unless you are sure that you don't absolutely want that app to run in the background and be woken only upon your choosing to open it, don't meddle with the options.
EDIT: I am rusty with Greenify since I haven't installed it for my daily driver and hence the instructions are from memory. There may be some slight differences with what I stated and the actual behaviour.
I don't see these Greenify options but my device is running android 4.4.2 and that might be the reason.
Peter770 said:
I don't see these Greenify options but my device is running android 4.4.2 and that might be the reason.
Click to expand...
Click to collapse
Sorry, I have no idea since I never ran Greenify before MM and that was looong ago.
DB126 said:
Default is whatever you set as the default in Greenify settings. Normal is what Android uses by default and is adequate for the vast majority of work flows. Deep requires an add on product (Island) and seems to be a solution looking for a problem. You could have discovered all this by searching the thread or reading documentation.
Click to expand...
Click to collapse
True man, but i am looking for that documentation for a few days (cause i like to read...); so i ended up here... still... no documentation...
So please, if you are kind, give me a link to Greenify documentation.!
Thanks.!
Robotu said:
True man, but i am looking for that documentation for a few days (cause i like to read...); so i ended up here... still... no documentation...
So please, if you are kind, give me a link to Greenify documentation.!
Thanks.!
Click to expand...
Click to collapse
Greenify is obsolete; power management approaches of the past are no longer relevant. Looking forward is a better time investment. Greenify documentation exists somewhere but I'm not going hunting. Good luck, mate.
DB126 said:
Greenify is obsolete; power management approaches of the past are no longer relevant. Looking forward is a better time investment. Greenify documentation exists somewhere but I'm not going hunting. Good luck, mate.
Click to expand...
Click to collapse
Very true, though it took me a few days to convince myself..., just to remember why i freezed it few years ago...
Thanks...!
Related
Hi,
for my basic understanding of Greenify I would like to know:
I ran Greenify 2.7 in root mode, currently without Xposed. This because I want to read more about Xposed first before installing.
It normally should hibernate the configured Apps automatically if I understand right.
In what time intervalls does Greenify check if such a App has been woken up and therefore hibernated again?
I watch the battery comsumption with 3C Tools and see, that the saving effect takes place only if I check manually every hour or so. Doing so, Greenify hibernates woken up Apps well and the battery saving effect is really good. But during the night I can see that the hibernation does not take place and I have 20% less capacity.
Sorry, if this question has already been discussued elsewhere. I have seearched here already, but being not sure, to find the right answers.
Edit: Now I Installed Version 2.8 Beta 8 and watch the behaviour.
Regards, Onurbi
onurbi said:
Hi,
for my basic understanding of Greenify I would like to know:
I ran Greenify 2.7 in root mode, currently without Xposed. This because I want to read more about Xposed first before installing.
It normally should hibernate the configured Apps automatically if I understand right.
In what time intervalls does Greenify check if such a App has been woken up and therefore hibernated again?
I watch the battery comsumption with 3C Tools and see, that the saving effect takes place only if I check manually every hour or so. Doing so, Greenify hibernates woken up Apps well and the battery saving effect is really good. But during the night I can see that the hibernation does not take place and I have 20% less capacity.
Sorry, if this question has already been discussued elsewhere. I have seearched here already, but being not sure, to find the right answers.
Edit: Now I Installed Version 2.8 Beta 8 and watch the behaviour.
Regards, Onurbi
Click to expand...
Click to collapse
Have you enabled Greenify in Device>Settings>Security>Device Administrator?
Do you have the donation pack?
Which version of android and what phone?
Normally, Greenify watches for apps waking up and hibernates them. There is no fixed interval for checking.
From your description I would guess that only manual hibernation is working and not automatic hibernation.
Thank you for your answer!
tnsmani said:
Have you enabled Greenify in Device>Settings>Security>Device Administrator?
Click to expand...
Click to collapse
Yes, there is a "Greenify Automator". This entry is there since Version 2.7 has been installed. It is ok for 2.8 Beta 8 also?
Do you have the donation pack?
Click to expand...
Click to collapse
Yes, I have.
Which version of android and what phone?
Click to expand...
Click to collapse
5.0.1 ,64 Bit, rooted, Huawei P8 Lite (ALE-21)
Normally, Greenify watches for apps waking up and hibernates them. There is no fixed interval for checking.
Click to expand...
Click to collapse
Ok. I could imagine, that a timer controlled action like I do it, would help.
When Greenify is not in "root" mode, it does an automated "Stop" of the Apps. With root mode it reports, that the found Apps are hibernated. When Greenify does this only once and another App will be waked up later, this now again running App will drain the battery anyway. That's not particular senseful I find. Therefore my question about regular checks.
From your description I would guess that only manual hibernation is working and not automatic hibernation.
Click to expand...
Click to collapse
I think so as well. But the Settings tell me that automatic hibernation is active (in German)!
The last 2 hours suddenly a process has been started named SUPL20Services. It will be reported by the 3C Toolbox analyser. This process caught my eyes several times already. The only context I found googling has to to with GPS. But when I disable GPS, this process comes up anyway. I tried to identify the parent process of it with "ps -t", but to no avail. There is no.
In this case Greenify can do nothing I believe.
Regards, Onurbi
onurbi said:
Thank you for your answer!
When Greenify is not in "root" mode, it does an automated "Stop" of the Apps. With root mode it reports, that the found Apps are hibernated. When Greenify does this only once and another App will be waked up later, this now again running App will drain the battery anyway. That's not particular senseful I find. Therefore my question about regular checks.
Click to expand...
Click to collapse
When an app is hibernated, it can not wake up again unless you specifically open it or another app/process wakes it up. So a hibernated app continuing to run does not happen unless you permit it.
If you find that a hibernated app is woken up again (not specifically by you), long press the app's name in Greenify and you will get a scissors icon on top. Clicking that icon will pop up a dialogue box which will tell you what woke up that app and if you don't want it to be woken up, click the appropriate button in the dialogue box.
If you find that a hibernated app is woken up again (not specifically by you), long press the app's name in Greenify and you will get a scissors icon on top. Clicking that icon will pop up a dialogue box which will tell you what woke up that app and if you don't want it to be woken up, click the appropriate button in the dialogue box.
Click to expand...
Click to collapse
Yes I understand this.
I think I tried this in the past and Google Services has been reported what has woken up, in this case, Hangouts. Hangouts is very "aggessive" I found and will very often be active again.
I'll have a look at the scissors next time a app will be active.
onurbi said:
Yes I understand this.
I think I tried this in the past and Google Services has been reported what has woken up, in this case, Hangouts. Hangouts is very "aggessive" I found and will very often be active again.
I'll have a look at the scissors next time a app will be active.
Click to expand...
Click to collapse
A word of caution: some apps require such wakeups to function properly. So if after using the scissors, you find that the app is not functioning correctly, you can again long press it and then click the three dot menu at top right in Greenify. You will get an option to reattach whatever you had cut earlier.
tnsmani said:
A word of caution: some apps require such wakeups to function properly. So if after using the scissors, you find that the app is not functioning correctly, you can again long press it and then click the three dot menu at top right in Greenify. You will get an option to reattach whatever you had cut earlier.
Click to expand...
Click to collapse
Thanx, I'll have a look at ths fact!
I lost magnify icon....im usin greenify 2.7.1 final stable with donation. Why??
Thankss
Can someone help?
hawkdown77 said:
I lost magnify icon....im usin greenify 2.7.1 final stable with donation. Why??
Thankss
Click to expand...
Click to collapse
Which magnify icon are you talking about?
tnsmani said:
Which magnify icon are you talking about?
Click to expand...
Click to collapse
When we are inside greenify, in up right corner there was a magnify icon to choice APP that we want to freenify. Now this icon disappear
hawkdown77 said:
When we are inside greenify, in up right corner there was a magnify icon to choice APP that we want to freenify. Now this icon disappear
Click to expand...
Click to collapse
I am on 2.8 beta9. There is no such icon. I have never used such an icon in Greenify and so I am not sure whether it was available in any version.
I am not saying that you are wrong but just that I don't remember. I also don't think that it is of much use unless you have hundreds of apps.
hawkdown77 said:
When we are inside greenify, in up right corner there was a magnify icon to choice APP that we want to freenify. Now this icon disappear
Click to expand...
Click to collapse
Due to restriction enforced by newer Android system, that selector could no longer work, thus was removed long ago.
oasisfeng said:
Due to restriction enforced by newer Android system, that selector could no longer work, thus was removed long ago.
Click to expand...
Click to collapse
But there some apps that i can not choose because it not show in the list of apps. How can i proceed to greenify them?
Hello @oasisfeng
Ive been using of greenify since the beggining ive rooted my device and now that MM is out which im also using since it was released on my nexus 5 device i still used greenify
Right now i have to uninstall it for one particular reason. It doesnt sync in notifications anymore.
I do know that "doze" limits notifications but opens background sync up in a short time for every minute or hours of interval. I do know greenify forces apps to go to "app standby" mode or forces apps to defer background process without exiting them on 6.0+ this means that the general "wait time" for push notifications are also deffered.
I do know there is a "wake up service" for greenify that intends to wake up device services again when hibernated from time to time but to be honest i think it is inefficient.
So haveyou tried creating an alarm that cuts the hibernation off for a small second to quickly sync in background process and push notifications from apps such as xda labs or messenger? You can do it by creating an alarm with a code of setandallowwhileidle()
Hope you read this and ill be waiting for your feedback, in the meantime ill be uninstalling greenify also its donate package and wait for further improvements
Cheers!
Instant messaging apps should generally be excluded from Greenify unless it supports GCM "high priority" push on Android 6.0+. This is the recommended solution mentioned in the app description and FAQ.
Do you mean the Greenify did sync in notifications in the past but not now? Can you give me a specific version number of Greenify that worked for you?
If I understand correctly, you want to wake-up apps periodically. It has been discussed actively in the early time. That derived a large set of functionality requirements, such as interval settings, settings per app, black-out duration, conditional wake-up, and etc. Even the worse, the longer interval, the less timely notification while the shorter interval, the more battery consumption. It is hard to balance, compared to the real right solution - GCM push. In summary, this idea introduced too much complexity.
As always, if you want to achieve that purpose, I'd suggest using Tasker together with the "wake-up" plug-in function provided by Greenify. Why do you think it is inefficient?
BTW, the solution of setAndAllowWhileIdle() is not the answer you may expect. If you are a developer and have read the documents, you should know this API is strictly limited and it also defeats the purpose of Greenify.
oasisfeng said:
Instant messaging apps should generally be excluded from Greenify unless it supports GCM "high priority" push on Android 6.0+. This is the recommended solution mentioned in the app description and FAQ.
Do you mean the Greenify did sync in notifications in the past but not now? Can you give me a specific version number of Greenify that worked for you?
If I understand correctly, you want to wake-up apps periodically. It has been discussed actively in the early time. That derived a large set of functionality requirements, such as interval settings, settings per app, black-out duration, conditional wake-up, and etc. Even the worse, the longer interval, the less timely notification while the shorter interval, the more battery consumption. It is hard to balance, compared to the real right solution - GCM push. In summary, this idea introduced too much complexity.
As always, if you want to achieve that purpose, I'd suggest using Tasker together with the "wake-up" plug-in function provided by Greenify. Why do you think it is inefficient?
BTW, the solution of setAndAllowWhileIdle() is not the answer you may expect. If you are a developer and have read the documents, you should know this API is strictly limited and it also defeats the purpose of Greenify.
Click to expand...
Click to collapse
I havent tried testing whileidle() to be honest i just read it multiple times on google sources and the likes.
For your suggestion on tasker i would not recommend it. There has been an endless discussion on tasker if it was battery friendly or not and i know for a fact that it is not. The problem with tasker is its constant background monitoring which depends on your "trigger" and "event" so yep i wouldnt use tasker to automate things anytime soon.
And yes. Waking up apps periodically is the thing that i would like to propose though it might contradict M's doze mode. So overall just now im with you that its not a good solution for messaging apps.
I dont remember it was years ago way back when im using kitkat and a non-famous brand phone locally made here in our country, but as far as i remember messenger really still doesnt tickle a notification update.
So bottomline right now theres no solution for messaging apps other than leaving it as it is right? The problem is that those messaging apps have the highest background drain so i guess i had to adjust myself using messenger lol
phantom146 said:
I havent tried testing whileidle() to be honest i just read it multiple times on google sources and the likes.
For your suggestion on tasker i would not recommend it. There has been an endless discussion on tasker if it was battery friendly or not and i know for a fact that it is not. The problem with tasker is its constant background monitoring which depends on your "trigger" and "event" so yep i wouldnt use tasker to automate things anytime soon.
And yes. Waking up apps periodically is the thing that i would like to propose though it might contradict M's doze mode. So overall just now im with you that its not a good solution for messaging apps.
I dont remember it was years ago way back when im using kitkat and a non-famous brand phone locally made here in our country, but as far as i remember messenger really still doesnt tickle a notification update.
So bottomline right now theres no solution for messaging apps other than leaving it as it is right? The problem is that those messaging apps have the highest background drain so i guess i had to adjust myself using messenger lol
Click to expand...
Click to collapse
IM app without GCM push is such a pain, since it usually tries its best to improve the real-time notifications, at the cost of power consumption. In my experience, even a 5 minutes interval wake-up is far from enough for a IM app, but already increases the power consumption a bit.
oasisfeng said:
IM app without GCM push is such a pain, since it usually tries its best to improve the real-time notifications, at the cost of power consumption. In my experience, even a 5 minutes interval wake-up is far from enough for a IM app, but already increases the power consumption a bit.
Click to expand...
Click to collapse
Agreed and again facebook and messenger is to blame for the poorly written codes and the messy services they all have.
Right now my issue is solved and im glad for such a quick and concise response. Ill be waiting for the future beta releases and in the meantime if you need my help for an upcoming feature on M count me in, and ill also throw down "possible suggestions" for you and maybe give you some codes for it
Cheers bud
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.
I been having huge RAM consumption with UC web browser, the app has a continuous foreground activity. Now, this is only app that keeps running on background and draining my battery. Is there anyway to force UCbrowser to hibernate using the shortcut hibernate icon? I mean instead of manually open the Greenify, the hibernation icon on my desktop shortcut should do the job.
I know that Greenify does not hibernate an app with constant foreground activity but UCbrowser is way too aggressive. Ironically, i don't want to uninstall UC because i like the browser functionality but only for browsing the web not its constant background activity.
I already turn off all of its in-app notifications such as Facebook, updates, news, ads, and even the "system" notification which i found inside the UC.
I hope someone can help me dealing this problem.
MrBrowseGierza said:
I been having huge RAM consumption with UC web browser, the app has a continuous foreground activity. Now, this is only app that keeps running on background and draining my battery. Is there anyway to force UCbrowser to hibernate using the shortcut hibernate icon? I mean instead of manually open the Greenify, the hibernation icon on my desktop shortcut should do the job.
I know that Greenify does not hibernate an app with constant foreground activity but UCbrowser is way too aggressive. Ironically, i don't want to uninstall UC because i like the browser functionality but only for browsing the web not its constant background activity.
I already turn off all of its in-app notifications such as Facebook, updates, news, ads, and even the "system" notification which i found inside the UC.
I hope someone can help me dealing this problem.
Click to expand...
Click to collapse
There are many fine browsers with great feature/functionality that do not exhibit insidious UC behaviors. That said, recent Greenify builds permit ignoring foreground activity. Highlight the UC entry in your watch list and open the overflow (3-dot) menu for options.
@MrBrowseGierza: Personally, I absolutely concur with @Davey126's statement. I use the following two browsers, FOSS Browser and Firefox Klar, but I'm aware that their functionalities do not necessarily serve everybody's requirement. Especially Firefox Klar only carries a very bare minimum and is clearly focused on privacy, and as usual you must first familiarise yourself with their user interfaces. But for those two, I can clearly promise a very decent battery usage. Another personal option could be Fennec.
Anyhow, what I don't understand really: Gratefully, you were able to clearly identify a source, the root for heavy battery drainage but you only want to fight the symptoms and not cure the buddy. I don't know if this is the right way?
EDIT: Without haven't ever UC Browser installed and no own personal look into it, I checked Exodus Privacy just for fun, and I know for sure I wouldn't install or use it: https://reports.exodus-privacy.eu.org/reports/14541/
Davey126 said:
There are many fine browsers with great feature/functionality that do not exhibit insidious UC behaviors. That said, recent Greenify builds permit ignoring foreground activity. Highlight the UC entry in your watch list and open the overflow (3-dot) menu for options.
Click to expand...
Click to collapse
that's really manual way to greenify UC, I guess UC developers see-through this that's why they took advantage with this not hibernating apps with foreground activity.
I really hope greenify can fix this flaw.
MrBrowseGierza said:
that's really manual way to greenify UC, I guess UC developers see-through this that's why they took advantage with this not hibernating apps with foreground activity.
I really hope greenify can fix this flaw.
Click to expand...
Click to collapse
Flaw?? Hardly. Intentional actions that should serve as a red flag. A few comments:
- method I referenced is fully automated
- hibernated apps can be restarted unless 'wake-up' paths are severed
- there can only be one active 'foreground' app; everything else is background
- there is no "flaw" for Greenify to address
Davey126 said:
Flaw?? Hardly. Intentional actions that should serve as a red flag. A few comments:
- method I referenced is fully automated
- hibernated apps can be restarted unless 'wake-up' paths are severed
- there can only be one active 'foreground' app; everything else is background
- there is no "flaw" for Greenify to address
Click to expand...
Click to collapse
:good:
MrBrowseGierza said:
that's really manual way to greenify UC, I guess UC developers see-through this that's why they took advantage with this not hibernating apps with foreground activity.
I really hope greenify can fix this flaw.
Click to expand...
Click to collapse
In my opinion, UC Browser is intentionally coded the way that it permanently collects and transmits data of its users, and in turn obviously for the burdon of battery capacity or RAM/CPU. Just a few ideas are linked:
https://en.wikipedia.org/wiki/UC_Browser (see paragraph "Security & Privacy)
https://citizenlab.ca/2015/05/a-chatty-squirrel-privacy-and-security-issues-with-uc-browser/
http://androroot.com/2017/08/is-really-uc-browser-is-safe-risk-and.html
A web-search provides additionaly information.
MrBrowseGierza said:
that's really manual way to greenify UC, I guess UC developers see-through this that's why they took advantage with this not hibernating apps with foreground activity.
I really hope greenify can fix this flaw.
Click to expand...
Click to collapse
What Davey126 meant is that you can control UC browser by following the steps mentioned by him.
Disable password for device
2ISAB said:
Disable password for device
Click to expand...
Click to collapse
???
tnsmani said:
???
Click to expand...
Click to collapse
Sometimes, having a password setup on the device, prevents greenify from auto hibernating. It's a one in ten shot...
2ISAB said:
Sometimes, having a password setup on the device, prevents greenify from auto hibernating. It's a one in ten shot...
Click to expand...
Click to collapse
Urban legend; have never heard/seen this. Knowing what happens when Greenify attempts to initiate post screen-off hibernation on an unrooted device (via accessibility) strongly suggests the presence of a lockscreen password is not in play.
Davey126 said:
Urban legend; have never heard/seen this. Knowing what happens when Greenify attempts to initiate post screen-off hibernation on an unrooted device (via accessibility) strongly suggests the presence of a lockscreen password is not in play.
Click to expand...
Click to collapse
It deactivates auto when screen off (greenify) as soon as a password is setup on a urooted N7. fyi
I remember how much of a pain it was searching forums for a simple solution.
OP doesn't mention Android version...
2ISAB said:
It deactivates auto when screen off (greenify) as soon as a password is setup on a urooted N7. fyi
I remember how much of a pain it was searching forums for a simple solution.
OP doesn't mention Android version...
Click to expand...
Click to collapse
Interesting. There have been random public reports of Automatic Hibernation becoming disabled - either spontaneously (GUI slider doesn't stick) or after a period of time. It always seems isolated with no correlation to device, rom, etc. It feels like a permissions issue, although none are required for basic use.
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
devsk said:
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
Click to expand...
Click to collapse
Did you try the shallow hibernation or normal hibernation?
devsk said:
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
Click to expand...
Click to collapse
Yes, Greenify is working on many (tens of) thousands of devices. Likely YOUR device, rom or kernel is aggressively clearing memory due to limited resources. What are you using?
tnsmani said:
Did you try the shallow hibernation or normal hibernation?
Click to expand...
Click to collapse
I tried both but app restarts instead of resuming.
Yes, Greenify is working on many (tens of) thousands of devices.
Click to expand...
Click to collapse
What's your definition of working? It runs and does something or works as in if an app is hibernated and started, it resumes. If its the latter, its clearly not working...
devsk said:
I tried both but app restarts instead of resuming.
What's your definition of working? It runs and does something or works as in if an app is hibernated and started, it resumes. If its the latter, its clearly not working...
Click to expand...
Click to collapse
Not going to engage on this level. Greenify stands on its own merrits.
If not happy with the results nor willing to share device/rom/config info that might help with 'problem' determination then it probably ain't the right tool.
Davey126 said:
Not going to engage on this level. Greenify stands on its own merrits.
If not happy with the results nor willing to share device/rom/config info that might help with 'problem' determination then it probably ain't the right tool.
Click to expand...
Click to collapse
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
devsk said:
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
Click to expand...
Click to collapse
Just for interest, I'd downloaded and installed Andoku. Greenified Andoku. Played a few minutes and stopped within the game. Closed Andoku. Ensured Andoku was hibernated. Opened Andoku and was able to resume my game exactly at the point where I'd closed Andoku.
Just for completeness although most likely unimportant in this matter: Andoku had no internet access granted in AFWall+.
Personal conclusion: Greenify (currently on v4.6.3) works exactly and perfectly as advertised!
Personal remark: I concur with @Davey126. Unless you provide sufficient information about device, ROM, kernel and "configuration" (e.g. Magisk, Xposed, XprivacyLua, tools that restrict permissions, services, broadcast receiver etc.) most likely nobody is able to support you.
devsk said:
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
Click to expand...
Click to collapse
Android hibernation is not the same as Windows hibernation. Resumability is not assured - especially on a resource constrained or highly 'tuned' ROM. You should probably read up on how it works and the primary objective of Greenify which is to suspend unwanted background activity. In that respect it shares many characteristics with doze.
Oswald Boelcke said:
Just for interest, I'd downloaded and installed Andoku. Greenified Andoku. Played a few minutes and stopped within the game. Closed Andoku. Ensured Andoku was hibernated. Opened Andoku and was able to resume my game exactly at the point where I'd closed Andoku.
Click to expand...
Click to collapse
Did you use the pause/resume feature of the Andoku game or did you just click the game to start it again, and it resumed where you left off? Typically, if you resume using the game's feature, you have to click through 3 times to resume your game. If the app is resuming from where it left off, its 1 click just to start the game.
If you resumed the app as if you switched to it using app switcher, then something definitely is broken on my end.
Just for completeness although most likely unimportant in this matter: Andoku had no internet access granted in AFWall+.
Click to expand...
Click to collapse
I do the same.
Oswald Boelcke said:
Unless you provide sufficient information about device, ROM, kernel and "configuration" (e.g. Magisk, Xposed, XprivacyLua, tools that restrict permissions, services, broadcast receiver etc.) most likely nobody is able to support you.
Click to expand...
Click to collapse
I am stock Pixel 3 XL with Magisk 18.1 root. Nothing else. I have given all perms needed by greenify.
Android hibernation is not the same as Windows hibernation.
Click to expand...
Click to collapse
I think this is where likely the disconnect is. I started using greenify several years ago (I have been here on these forums for a while, I keep that dated forum reference in my signature for remembering how far android and this community has come). If I recall correctly, I used to be able to resume apps, just by clicking or switching to them. Now, I notice a different behaviour: the app restarts from scratch. That's all. Obviously, I preferred the app to not start but resume like I was just switching to it.
I don't know if this is relevant in this case, but doesn't Greenify in non-root mode just force stop apps? I believe this to be the case because I can see it happening; i.e., when hibernation is triggered, for each app hibernated the app info screen briefly appears and the warning dialog about force stopping an app flashes on screen momentarily.
olliebean said:
I don't know if this is relevant in this case, but doesn't Greenify in non-root mode just force stop apps? I believe this to be the case because I can see it happening; i.e., when hibernation is triggered, for each app hibernated the app info screen briefly appears and the warning dialog about force stopping an app flashes on screen momentarily.
Click to expand...
Click to collapse
Correct. The equivalent happens on rooted devices just in a more efficient and largely transparent manner. If the ROM later opts to recover some/all of the resources consumed by the 'hibernated' app standard Android memory mgmt rules apply. In most cases that means only critical pointers are retained which may or may not contain sufficient information to resume from the point the app was in when last in the foreground.
Davey126 said:
Correct. The equivalent happens on rooted devices just in a more efficient and largely transparent manner. If the ROM later opts to recover some/all of the resources consumed by the 'hibernated' app standard Android memory mgmt rules apply. In most cases that means only critical pointers are retained which may or may not contain sufficient information to resume from the point the app was in when last in the foreground.
Click to expand...
Click to collapse
But AIUI, force stopping an app is essentially killing the app process. So for the app to start afresh when next launched, rather than resuming from where it was left, would be expected behaviour.
Is Greenifying an app functionally better than disabling Background Activity from the app's Battery Usage page (a new setting in Oreo)? IWHT the latter achieves the same result but without killing the app.
I am running root mode. So, let's not talk about non-root mode.
If a hibernated app is going to restart from scratch instead of resume, I might as well just clear all apps (that I fed to Greenify) on screen off with 5 min delay using tasker/automate. Why bother with anything else?
The point of Greenify was to be able to resume the app after hibernate as if you just switched to it. This used to work, I have tested it in the past. Not anymore though.
olliebean said:
But AIUI, force stopping an app is essentially killing the app process. So for the app to start afresh when next launched, rather than resuming from where it was left, would be expected behaviour.
Is Greenifying an app functionally better than disabling Background Activity from the app's Battery Usage page (a new setting in Oreo)? IWHT the latter achieves the same result but without killing the app.
Click to expand...
Click to collapse
Well, no ... but this is not the place for that discussion. Not going to get into Android 101 or validating speculation around various actions.
---------- Post added at 05:18 PM ---------- Previous post was at 04:52 PM ----------
devsk said:
I am running root mode. So, let's not talk about non-root mode.
If a hibernated app is going to restart from scratch instead of resume, I might as well just clear all apps (that I fed to Greenify) on screen off with 5 min delay using tasker/automate. Why bother with anything else?
The point of Greenify was to be able to resume the app after hibernate as if you just switched to it. This used to work, I have tested it in the past. Not anymore though.
Click to expand...
Click to collapse
Sorry it is not working with your device/kernel/ROM/root solution. Could be an adverse interaction with the doze mechanisms in Android 9, aggressive memory management settings (eg: VM, LMK), resource mapping of the app(s) you are trying to hibernate, etc. I have not see a lot of feedback from Pie users as doze generally addresses rogue background activity and corresponding power drain. So the behavior may be different on that platform. I use Greenify on a variety of devices for other reasons for which it continues to work well. Just another tool in shop; appropriate selection is the key to success. Good luck.