Related
@oasisfeng Disclaimer: Apologies in advance -- this is a long one!
I've been experiencing an odd issue, as of late, running the 2.6.1 stable on my Nexus 5 (LP 5.1 / LMY47I, Cataclysm ROM). I'm using Root Mode (donation version), without Xposed.
This issue is slightly difficult to explain. By observing my SuperSU logs, I've noticed that a seemingly random and previously Greenified app will be continually hibernated every 30 minutes or so, each time my device goes idle for a prolonged period (such as while I'm working, or asleep). Curiously, the apps in question will change during each idle period, largely excluding the possibility that this is simply the case of a rogue app. The various apps are usually quite innocuous, and never known to (randomly) wake while my device is in use -- last night's was MX Player, for instance.
(Edit: Upon further observation, it seems that the random app in question is often among the last to have been manually woken/used before entering the next deep sleep period, in case it helps.)
Unfortunately, I've yet to successfully return to my device in time to catch any possible wake-up paths. I do question, however, if the apps are actually being woken in the first place (as opposed to Greenify simply "re-hibernating" apps that are already sleeping), as the issue will seemingly disappear entirely when auto-hibernation is disabled -- according to my SU logs, at least.
The only potential user-side cause that I can think of is that I had previously cut-off the Google Play Services wake-up path for Maps (neither G.P.S. nor any important system apps were ever actually hibernated). I've since re-attached the wake-up path, and de-Greenified Maps. Although that's probably unrelated, it's pretty much the "riskiest" thing I've done with Greenify on this device. I normally just keep a number of seldomly used user apps hibernated, and don't have any known offenders (like Facebook) on my device.
I've since removed and re-added each of my hibernated apps, as well as reinstalled Greenify (and its donation package) several times. I should note, as well, that I have not experienced any noticeable battery drains. Unfortunately, I'm unable to confirm whether or not this occurred before updating to Greenify 2.6.1 stable -- I've simply only observed this behavior since the Play Store rollout.
I've attached an example screenshot of my SuperSU log (taken after a 7 hour idle period), just so you can better visualize the pattern (the actual content of each log is simply the usual force stop message). Apologies for not providing anything more helpful at this time; please let me know if there's anything you'd like to see.
Thank you, for both your time and continued support for this wonderful app.
I am experiencing the same issue as above
"(Edit: Upon further observation, it seems that the random app in question is often among the last to have been manually woken/used before entering the next deep sleep period, in case it helps.)"
this is definitely the case with me. I am quite certain the apps are not actually being woken up every 30 minute period. It feels like greenify is running the command needlessly.
I am in the beta channel and using root mode
@oasisfeng I also experiencing this issue. On BetterBatteryStats, I have partial wakelocks every 30 minutes and it seemed greenify is causing this.
I'm on XtreStoLite 2.1 - LP TouchWiz based ROM running Greenify 2.6.1 on Root mode with Donation Package
It's not an issue, but a protective design, to ensure the apps occasionally woken during the idle period being put back to hibernation again.
First of all, this is not a wake-up periodic timer, that means if your device fell in sleep for more than half a hour, it will never wake up the CPU until other apps wake it. So, it consumes little battery juice, which you could hardly perceive.
I'm planning to add latest wake-up information for all apps including the hibernated ones.
Hi, guys, do you use Tasker for periodic hibernation/wakeup task with Greenify?
I dont. I have tasker installed, but havent set it up to do anything yet. Cheers
oasisfeng said:
Hi, guys, do you use Tasker for periodic hibernation/wakeup task with Greenify?
Click to expand...
Click to collapse
Thanks for your replies! In my case, I haven't been using any hibernation/wake-up tasks (although Tasker is installed).
Regarding your first response, I'm not entirely sure what you mean about the protective design. Apologies if there's any confusion, but if you're suggesting that Greenify simply ensures that woken apps remain hibernated, the puzzling thing is that these particular apps will not wake at all when auto-hibernation is disabled.
Auto hibernation/Manual hibernation
@oasisfeng
I have the same issue as the others above but noted your explanation for the same. I am running stock Lollipop 5.1 in my rooted Nexus 4 with Greenify 2.6.2 beta 3 running in Root mode with donation features.
One more issue which is more serious (in my opinion), is auto hibernation and manual hibernation. Some system apps like Google Services Framework and Google Play Services do not get autohibernated occasionally. Likewise even if the manual shortcut Hibernate+lockscreen is used, these remain running sometimes, even after half an hour of sleep. However, there is no noticeable impact on battery. (I have brought the battery loss down to 0.3 to 0.7% per hour while sleeping, from 6 to 7% without Greenify. Thanks for that) As the others reported, SU logs indicate that every half hour Greenify hibernated these apps though they are present as running continuously when Greenify is opened. My suspicion is that though they are actually hibernated, Greenify does not correctly reflect the status.
This is more of a report than a complaint to keep you and others informed.
tnsmani said:
@oasisfeng
I have the same issue as the others above but noted your explanation for the same. I am running stock Lollipop 5.1 in my rooted Nexus 4 with Greenify 2.6.2 beta 3 running in Root mode with donation features.
One more issue which is more serious (in my opinion), is auto hibernation and manual hibernation. Some system apps like Google Services Framework and Google Play Services do not get autohibernated occasionally. Likewise even if the manual shortcut Hibernate+lockscreen is used, these remain running sometimes, even after half an hour of sleep. However, there is no noticeable impact on battery. (I have brought the battery loss down to 0.3 to 0.7% per hour while sleeping, from 6 to 7% without Greenify. Thanks for that) As the others reported, SU logs indicate that every half hour Greenify hibernated these apps though they are present as running continuously when Greenify is opened. My suspicion is that though they are actually hibernated, Greenify does not correctly reflect the status.
This is more of a report than a complaint to keep you and others informed.
Click to expand...
Click to collapse
jacknicholson said:
Thanks for your replies! In my case, I haven't been using any hibernation/wake-up tasks (although Tasker is installed).
Regarding your first response, I'm not entirely sure what you mean about the protective design. Apologies if there's any confusion, but if you're suggesting that Greenify simply ensures that woken apps remain hibernated, the puzzling thing is that these particular apps will not wake at all when auto-hibernation is disabled.
Click to expand...
Click to collapse
jacknicholson said:
@oasisfeng Disclaimer: Apologies in advance -- this is a long one!
I've been experiencing an odd issue, as of late, running the 2.6.1 stable on my Nexus 5 (LP 5.1 / LMY47I, Cataclysm ROM). I'm using Root Mode (donation version), without Xposed.
This issue is slightly difficult to explain. By observing my SuperSU logs, I've noticed that a seemingly random and previously Greenified app will be continually hibernated every 30 minutes or so, each time my device goes idle for a prolonged period (such as while I'm working, or asleep). Curiously, the apps in question will change during each idle period, largely excluding the possibility that this is simply the case of a rogue app. The various apps are usually quite innocuous, and never known to (randomly) wake while my device is in use -- last night's was MX Player, for instance.
(Edit: Upon further observation, it seems that the random app in question is often among the last to have been manually woken/used before entering the next deep sleep period, in case it helps.)
Unfortunately, I've yet to successfully return to my device in time to catch any possible wake-up paths. I do question, however, if the apps are actually being woken in the first place (as opposed to Greenify simply "re-hibernating" apps that are already sleeping), as the issue will seemingly disappear entirely when auto-hibernation is disabled -- according to my SU logs, at least.
The only potential user-side cause that I can think of is that I had previously cut-off the Google Play Services wake-up path for Maps (neither G.P.S. nor any important system apps were ever actually hibernated). I've since re-attached the wake-up path, and de-Greenified Maps. Although that's probably unrelated, it's pretty much the "riskiest" thing I've done with Greenify on this device. I normally just keep a number of seldomly used user apps hibernated, and don't have any known offenders (like Facebook) on my device.
I've since removed and re-added each of my hibernated apps, as well as reinstalled Greenify (and its donation package) several times. I should note, as well, that I have not experienced any noticeable battery drains. Unfortunately, I'm unable to confirm whether or not this occurred before updating to Greenify 2.6.1 stable -- I've simply only observed this behavior since the Play Store rollout.
I've attached an example screenshot of my SuperSU log (taken after a 7 hour idle period), just so you can better visualize the pattern (the actual content of each log is simply the usual force stop message). Apologies for not providing anything more helpful at this time; please let me know if there's anything you'd like to see.
Thank you, for both your time and continued support for this wonderful app.
Click to expand...
Click to collapse
I have a similar problem
yesterday I was using Wakelock Detector and I found out this:
Today I flashed a new Rom and all I did was configuration stuff and install some basic apps such as facebook, twitter etc. and greenify (not xposed module) greenifying NOT system apps
After 3h it caused screen wakelock during 7 minutes
BTW I amb on stock lollipop 30b
Is greenify incompatible? is supersu broken?
Boopie11 said:
I have a similar problem
yesterday I was using Wakelock Detector and I found out this:
Click to expand...
Click to collapse
First, learn some etiquette. Quote only what is relevant or simply say that you have the same issue as others. Don't go about quoting multiple full posts.
Second, you have opened a separate thread for the same issue. So what is the point of posting the same here?
Third, though your attachments are not visible, your description gives the impression that your issue has no relevance to the posts you have quoted.
The issue appears to have been resolved with version 2.6.2. As always, my thanks go to @oasisfeng -- although if I may ask, did you manage to find the source of the issue, or is this a coincidence?
jacknicholson said:
The issue appears to have been resolved with version 2.6.2. As always, my thanks go to @oasisfeng -- although if I may ask, did you manage to find the source of the issue, or is this a coincidence?
Click to expand...
Click to collapse
Yes, your report is very precious for me to analyze this issue. It was fixed in an earlier beta version before the final release of version 2.6.2. Thanks very much!
oasisfeng said:
Yes, your report is very precious for me to analyze this issue. It was fixed in an earlier beta version before the final release of version 2.6.2. Thanks very much!
Click to expand...
Click to collapse
I was wondering whether Greenify had stopped working, after installing 2.6.2.
Now I know the reason. So this is why I don't see those repeat hibernations.
Thank you, @oasisfeng!
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 to all. my configuration is fritten in my firm.
i noticed some differences between standard and shallow hibernation. i tested telegram and whatsapp on standard... and of course if a person send me a text the apps are NOT WAKING UP till i open them. perfect!
but on shallow hibernation i notice they are waked up and i receive the message, ok maybe not instantly but it could take about 15/30 seconds to receive them.
is it a NORMAL BEHAVIOUR? maybe yes......
this is what i read in the settings​Shallow-hibernated apps will be woken for a brief time periodically in hours and immediately upon HIGH priority GCM push (only if GCM priority is implemented by app developer). They will also keep awake during charging
mmmhh... ok so it should be something similar to the xposed feature ( that require donation package) called "GCM push for greenified apps" ???
i am on nougat and i don't have xposed, but i have the donation package......but i thought that without xposed i would never had the possibiliti to greenify an app ....MANTAINING the possibility to receive push messages... just because for this feature it's needed xposed!!!
so at the end..... could i consider the shallow hibernation an alternative "GCM push for greenified apps" for the persons that can't have xposed? i am just a fraid that this kind of hibernation is not so much effective in terms of battery life, respecting the old/standard one...... but i wait for some users more skilled than me that could explain and reassure me....:laugh:
realista87 said:
hello to all. my configuration is fritten in my firm.
i noticed some differences between standard and shallow hibernation. i tested telegram and whatsapp on standard... and of course if a person send me a text the apps are NOT WAKING UP till i open them. perfect!
but on shallow hibernation i notice they are waked up and i receive the message, ok maybe not instantly but it could take about 15/30 seconds to receive them.
is it a NORMAL BEHAVIOUR? maybe yes......
this is what i read in the settings
Shallow-hibernated apps will be woken for a brief time periodically in hours and immediately upon HIGH priority GCM push (only if GCM priority is implemented by app developer). They will also keep awake during charging
mmmhh... ok so it should be something similar to the xposed feature ( that require donation package) called "GCM push for greenified apps" ???
i am on nougat and i don't have xposed, but i have the donation package......but i thought that without xposed i would never had the possibiliti to greenify an app ....MANTAINING the possibility to receive push messages... just because for this feature it's needed xposed!!!
so at the end..... could i consider the shallow hibernation an alternative "GCM push for greenified apps" for the persons that can't have xposed? i am just a fraid that this kind of hibernation is not so much effective in terms of battery life, respecting the old/standard one...... but i wait for some users more skilled than me that could explain and reassure me....:laugh:
Click to expand...
Click to collapse
- high priority GCM push notifications will display immediately with shallow hibernation or w/Xposed option (Android 6.x and below)
- standard notifications will be delayed until next maintenance window with shallow hibernation; Xposed variant will deliver those immediately
- app developer controls notification priority
- personally I would stick with standard doze/hibernation and call it a day
sorry but i didn't understand your last point. what does it mean "call it a day"?? sorry i'm not a native english....
But seems that you don't rely so much on the new shallow mode.... is there a more precise technical motivation that you could bring on the discussion table... to let me understand why do you prefer the old hibernation method?
realista87 said:
sorry but i didn't understand your last point. what does it mean "call it a day"?? sorry i'm not a native english....
But seems that you don't rely so much on the new shallow mode.... is there a more precise technical motivation that you could bring on the discussion table... to let me understand why do you prefer the old hibernation method?
Click to expand...
Click to collapse
- expression "call it a day" simply means stop further activity (the job is done)
- I do not use shallow/aggressive hibernation as the benefits do not outweigh the side effects; all my devices sleep well with standard doze/hibernation
ok... in fact i notice that with shallow method some apps still continue to wake up the phone, i see the wakelocks on wakelock detector app and betterbatterystats. so at the end it's not clear if shallow hibernation is a REAL OR NOT hibernation... because these 2 apps that wake up, antutu and MYwind ( an app to check balance and options of my operator) are NOT setted to receive any notification... so i don't understand why they still uses alarms.
BUT........ i will continue to use shallow thinking and hoping that i could gain more battery life greenifying MORE APPS.... also the messaging ones. in fact i greenified telegram, WA, alsmost everything and i stil continue to receive notifications.
what i'm saying is that maybe standard hibernation is STRONGER, but it needs to be whitelisted with at least messaging apps and other apps used on average, and my fear is that the benefit gained from the TRUE "old" hibernation could be not surpassed by the smallest NOT whitelisted apps that the shallow ones permits you to set....without break any notification (sorry i'm not a native english, it's my best)
realista87 said:
ok... in fact i notice that with shallow method some apps still continue to wake up the phone, i see the wakelocks on wakelock detector app and betterbatterystats. so at the end it's not clear if shallow hibernation is a REAL OR NOT hibernation... because these 2 apps that wake up, antutu and MYwind ( an app to check balance and options of my operator) are NOT setted to receive any notification... so i don't understand why they still uses alarms.
BUT........ i will continue to use shallow thinking and hoping that i could gain more battery life greenifying MORE APPS.... also the messaging ones. in fact i greenified telegram, WA, alsmost everything and i stil continue to receive notifications.
what i'm saying is that maybe standard hibernation is STRONGER, but it needs to be whitelisted with at least messaging apps and other apps used on average, and my fear is that the benefit gained from the TRUE "old" hibernation could be not surpassed by the smallest NOT whitelisted apps that the shallow ones permits you to set....without break any notification (sorry i'm not a native english, it's my best)
Click to expand...
Click to collapse
I understand what you are saying. Best path is to test both modes to determine which best meets your needs. Good luck.
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...!
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.