Hi,
I'm using a Nexus 6P with stock MM 6.0.1 + root + xposed and using the paid version of greenify (currently testing v2.8b10)
(1) I'm trying to figure out how shallow hibernation works, what is the philosophy behind it compared to "normal" hibernation because it seems to me that the apps that I hibernate are more often awaken under shallow than normal hibernation, that their service seems to still be running in the background.
(2) In the description of shallow hibernation, it says that shallow-hibernated apps will be woken for a brief period of time periodically: Why and what does this mean exactly? by periodical wakeups are we not loosing the whole purpose of hibernation?
(3) Also with shallow hibernation, it seems impossible to cut some unwanted wake-up paths because greenify doesn't indicate which path has awaken an app. While in normal hibernation, greenify specify which "action" has awaken an app against your will so you can cut this specific wake-up path (for instance I have a stupid app that is being awaken everytime I make a phone call - but I need this app only when I manually launch it)
Search a little bit and you will find your answer
Sent from my bacon!!!!!
NickosD said:
Search a little bit and you will find your answer
Sent from my bacon!!!!!
Click to expand...
Click to collapse
Great! Thank you for you useful answer!!!
I did search through the Greenify forum before posting, and couldn't find any satisfactory answers to my questions. Also I've been a satisfied paid user of Greenify since its creation, so I believe I'm experienced with it and I understand how it works.... until the emergence of Shallow hibernation which is pretty new to me since I only upgraded to MM about 1-2 month ago.
Navigating through various threads, I actually found out that many people are questionning the behavior of Shallow hibernation, and answers that I found were either unclear or contradictory. I believe a lot of people could benefit from a thread dedicated to Shallow hibernation... if smart people could contribute to it with better answers than just "Search"
It's already been answered
Sent from my bacon!!!!!
Surfinette said:
Great! Thank you for you useful answer!!!
I did search through the Greenify forum before posting, and couldn't find any satisfactory answers to my questions. Also I've been a satisfied paid user of Greenify since its creation, so I believe I'm experienced with it and I understand how it works.... until the emergence of Shallow hibernation which is pretty new to me since I only upgraded to MM about 1-2 month ago.
Navigating through various threads, I actually found out that many people are questionning the behavior of Shallow hibernation, and answers that I found were either unclear or contradictory. I believe a lot of people could benefit from a thread dedicated to Shallow hibernation... if smart people could contribute to it with better answers than just "Search"
Click to expand...
Click to collapse
If you had searched properly instead of being sarcastic, you would have found the answer. A mere search for "shallow hibernation" on Greenify gives atleast the following answers.
http://forum.xda-developers.com/showpost.php?p=65021192&postcount=8
and
http://forum.xda-developers.com/showpost.php?p=65005722&postcount=2
Likewise for the other queries.
Sorry for lacking clearly communication. I'll write separate posts to explain the new features in 2.8, including Shallow Hibernation and Aggressive Doze.
tnsmani said:
If you had searched properly instead of being sarcastic, you would have found the answer. A mere search for "shallow hibernation" on Greenify gives atleast the following answers.
http://forum.xda-developers.com/showpost.php?p=65021192&postcount=8
and
http://forum.xda-developers.com/showpost.php?p=65005722&postcount=2
Likewise for the other queries.
Click to expand...
Click to collapse
I was being sarcastic because I was upset that the guy thought I didn't search before posting, and also didn't bother to help (I didn't force him to answer me)... because I did search a lot, and because I saw many people looking for answers and finding different answers that didn't always match... and also because the behavior of shallow hibernation on my phone doesn't always match the expected behavior (according to the answers I found in this forum). My search has led me to believe that a thread dedicated to shallow hibernation might prove useful to some people
I thank you because at least you are being constructive by providing some links, but those links I had read before posting, and for instance your second link relates to an explanation of shallow hibernation which ends by the poster saying "This is my understanding but I don't know if I am 100% correct."... This is typically why I'm looking for more answers!
For instance, I don't understand why an app that I don't use often is always hibernating in "normal" hibernation mode while it is often awake in shallow hibernation and doesn't hibernate automatically if I don't force its hibernation manually, and why there is no indication of its wakeup path when in shallow hibernation...
oasisfeng said:
Sorry for lacking clearly communication. I'll write separate posts to explain the new features in 2.8, including Shallow Hibernation and Aggressive Doze.
Click to expand...
Click to collapse
You don't have to be sorry, you are a great dev. I've been following your work since the very start and advertizing greenify to all my android friends.
It's just that new features can get sometimes more challenging to get use to
Surfinette said:
.............
For instance, I don't understand why an app that I don't use often is always hibernating in "normal" hibernation mode while it is often awake in shallow hibernation and doesn't hibernate automatically if I don't force its hibernation manually, and why there is no indication of its wakeup path when in shallow hibernation...
Click to expand...
Click to collapse
In normal hibernation the app is held in check by Greenify and hence there are no running or background services. In shallow hibernation, as the Dev explained in the first post quoted by me, the context of the app is preserved so that when you invoke it, it need not start afresh.
You have to make the choice here, whether to use shallow hibernation or normal hibernation depending on your type of usage. There is no point in saying that the app doesn't fully hibernate in shallow hibernation because that is the intended behaviour.
Anyway the Dev has promised a writeup explaining the features and I am sure we are thankful for that. That will clear up all these back and forths.
I am also having trouble understanding. Let's say I do a shallow hibernation on Whatsapp. it will be waken up by any new message using GCM push, but won't drain the battery otherwise? So in this case it would be a great idea, am I correct?
ppaasseeii said:
I am also having trouble understanding. Let's say I do a shallow hibernation on Whatsapp. it will be waken up by any new message using GCM push, but won't drain the battery otherwise? So in this case it would be a great idea, am I correct?
Click to expand...
Click to collapse
Does WhatsApp have major wake issues anyway to drain battery? Why are you Greenifying it in the first place?
dmo580 said:
Does WhatsApp have major wake issues anyway to drain battery? Why are you Greenifying it in the first place?
Click to expand...
Click to collapse
No it's nothing major, it's a a few wakelocks an hour. I usually don't greenify it because you don't get messages if you do (unless with Xposed). I'm just trying to understand what this shallow hibernation does.
ppaasseeii said:
No it's nothing major, it's a a few wakelocks an hour. I usually don't greenify it because you don't get messages if you do (unless with Xposed). I'm just trying to understand what this shallow hibernation does.
Click to expand...
Click to collapse
Let me try to explain it with an example.
Suppose Chrome is chosen for hibernation and you open it and browse to a particular page and then dismiss/close it, Chrome will be hibernated after the screen is off. If it is normal hibernation, then when you open it again, you will be presented with the start page of Chrome and not the last page which you had open. If it is shallow hibernated, you will be presented the last page you had open.
In addition, in normal hibernation, Chrome's processes will be completely stopped and it will be removed from memory. So when you start it again, it starts afresh.
In shallow hibernation, Chrome will be allowed to remain in memory but its background processes will be stopped. So when you open it again, it starts from where it was before. Since such apps remain in memory, shallow hibernation is not advisable for devices with low memory.
I don't know if I was able to clear your doubts or confused you further.
Hi, I just wanted to say that I am experiencing strange behavior when using shallow hibernation. Instagram cannot open once the shallow hibernation is turned on and also the phone stutters every few seconds. Turned the shallow hibernation off and now all is good.
Hello, as i understand shallow hibernation is not working on my phone. Applications appear in the status "after a few minutes you hibernate" and if i play hibernate, run it. As have the time off screen, when i look greenify applications are hibernated. Any idea why it does not work properly?
Excuse my bad English.
I'm on cm 13 6.0.1, the aggressive doze works fine. Have greenify 2.9 beta 2 with xposed and donate version
Thanks very much
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Swallow keeps them more time awake. Read again the description. It's working as it suppose to work.
Sent from my A0001 using Tapatalk
NickosD said:
Swallow keeps them more time awake. Read again the description. It's working as it suppose to work.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I read the description, but says that the application retains the status? when I have the screen off and turn on to open an app starts from the beginning and not where he had left. This is correct? Sorry for the insistence, but that part did not stay clear.
Thanks for your time
It's been hibernated until it will be woken again, from the user or by itself.
Sent from my A0001 using Tapatalk
NickosD said:
It's been hibernated until it will be woken again, from the user or by itself.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Greenify's implementation is NOT to allow an app to start/run by itself. A hibernated app has to be explicitly started by you. It won't run by itself.
---------- Post added at 01:50 PM ---------- Previous post was at 01:47 PM ----------
elpipo87 said:
I read the description, but says that the application retains the status? when I have the screen off and turn on to open an app starts from the beginning and not where he had left. This is correct? Sorry for the insistence, but that part did not stay clear.
Thanks for your time
Click to expand...
Click to collapse
In shallow hibernation, a hibernated app will start from where it was before whereas in normal hibernation, such an app will start from scratch.
Please read my previous post a few posts above (post #13).
It seems like GCM is not received when the app is hibernated either in the normal or shallow mode (which makes sense as all background services should be prohibited).
I know I will get GCM messages in the normal mode + donation package. Will the donation package also solve this issue in the shallow mode?
Thanks.
Related
Hi! My App (KLWP, see official thread) is currently using content providers to fetch presets from Play Store downloaded skin packs, problem is that some user are reporting that templates are not loaded correctly and i can find in their logs the following statement:
Code:
I/DeepHyber( 1382): Refuse content request for hibernated app: glassatlas.kustom.waveandanchor/org.kustom.api.Provider
So:
Is "DeepHyber" tag is from this app/mod?
Any idea on how i can prevent the provider being stopped?
Thanks!
frankmonza said:
Hi! My App (KLWP, see official thread) is currently using content providers to fetch presets from Play Store downloaded skin packs, problem is that some user are reporting that templates are not loaded correctly and i can find in their logs the following statement:
Code:
I/DeepHyber( 1382): Refuse content request for hibernated app: glassatlas.kustom.waveandanchor/org.kustom.api.Provider
So:
Is "DeepHyber" tag is from this app/mod?
Any idea on how i can prevent the provider being stopped?
Thanks!
Click to expand...
Click to collapse
I think that only the Dev can answer that properly.
There is Deep Hibernation in Greenify. So may be that tag is from Greenify. The users seem to have hibernated your app and also enabled Deep Hibernation in Greenify. They can ungreenify your app which will solve the issue.
So over to you @oasisfeng .
tnsmani said:
I think that only the Dev can answer that properly.
There is Deep Hibernation in Greenify. So may be that tag is from Greenify. The users seem to have hibernated your app and also enabled Deep Hibernation in Greenify. They can ungreenify your app which will solve the issue.
So over to you @oasisfeng .
Click to expand...
Click to collapse
Thanks, so, yes, disabling Greenify works (just got the confirmation from an user, so its almost certainly caused by it) while ungreenifying probably doesn't help because you would need to disable it on all the "skin" apps because they all have their own provider.
My problem currently is that i can either detect greenify in the app and ask the user to disable it or i need to find a way around this to avoid it disabling the providers i need (otherwise i will keep getting requests from users saying that they cannot load presets without knowing why).
If you tell the users to disable Greenify completely, they are going to lose its functionality completely. Better tell them to ungreenify your app and any others that need content providers till you and @oasisfeng find a solution, so that the users have both apps functioning, albeit Greenify less fully.
As an experiment, you can tell the users to disable Deep Hibernation alone (in Greenify) instead of completely diabling Greenify.
tnsmani said:
If you tell the users to disable Greenify completely, they are going to lose its functionality completely. Better tell them to ungreenify your app and any others that need content providers till you and @oasisfeng find a solution, so that the users have both apps functioning, albeit Greenify less fully.
As an experiment, you can tell the users to disable Deep Hibernation alone (in Greenify) instead of completely diabling Greenify.
Click to expand...
Click to collapse
I cannot ask them to "ungreenify" 10/20/30 apps, too much work, disabling deep hibernation works (and i am asking to disable just that, i did not express myself correctly). But this is a minor issue i am not taking any action yet, just got 3/4 reports so its not that urgent, there is time to find a better solution
Deep Hibernation is a new *experimental* feature in Greenify, which blocks any attempts to launch the process of hibernated apps, including content provider.
In theory, this feature only affects hibernated app. But in a side effect, all newly installed apps on Android are in "hibernated" state initially, this behavior, in my understand, caused the trouble for your app.
My apologizes! I'm working on this issue and planned to fix it in the next version. Before that, please advise the users to manually "wake up" the newly installed app once either by launching any of its activities or by temporarily deactivating "Deep Hibernation" for a short while. Once the app is launched once and not explicitly greenified by user, it will not be affected by Deep Hibernation any more.
oasisfeng said:
Deep Hibernation is a new *experimental* feature in Greenify, which blocks any attempts to launch the process of hibernated apps, including content provider.
In theory, this feature only affects hibernated app. But in a side effect, all newly installed apps on Android are in "hibernated" state initially, this behavior, in my understand, caused the trouble for your app.
My apologizes! I'm working on this issue and planned to fix it in the next version. Before that, please advise the users to manually "wake up" the newly installed app once either by launching any of its activities or by temporarily deactivating "Deep Hibernation" for a short while. Once the app is launched once and not explicitly greenified by user, it will not be affected by Deep Hibernation any more.
Click to expand...
Click to collapse
Thanks for the reply! No worries, the most complex thing was finding the issue (most users have no idea of what logcat is and i was just getting an empty cursor from the provider so had no log anywhere within the app).
Anyway, the problem here is that skin packs do not have any activity, they just have a content provider, so the user cannot launch the activity and also a reboot won't fix the issue, so, unless they disable this feature the content won't be loaded.
What about disabling this feature for content providers entirely by default?
frankmonza said:
Thanks for the reply! No worries, the most complex thing was finding the issue (most users have no idea of what logcat is and i was just getting an empty cursor from the provider so had no log anywhere within the app).
Anyway, the problem here is that skin packs do not have any activity, they just have a content provider, so the user cannot launch the activity and also a reboot won't fix the issue, so, unless they disable this feature the content won't be loaded.
What about disabling this feature for content providers entirely by default?
Click to expand...
Click to collapse
Deep Hibernation was initially launched without the blocking of content providers. But apps like Amazon Appstore use content provider (of the Appstore app) heavily within all apps distributed by them (most app developers are not aware of this injected nasty behavior), causing wake-ups constantly. As requested by users of Greenify, content provider is added to the blocking target.
If the skin pack has only resources, I'd suggest the more efficient direct resource loading via PackageManager.getResourcesForApplication() instead of content provider, unless code within the skin pack is also needed to run.
oasisfeng said:
Deep Hibernation was initially launched without the blocking of content providers. But apps like Amazon Appstore use content provider (of the Appstore app) heavily within all apps distributed by them (most app developers are not aware of this injected nasty behavior), causing wake-ups constantly. As requested by users of Greenify, content provider is added to the blocking target.
If the skin pack has only resources, I'd suggest the more efficient direct resource loading via PackageManager.getResourcesForApplication() instead of content provider, unless code within the skin pack is also needed to run.
Click to expand...
Click to collapse
The provider does caching and other stuff so i cannot use "PackageManager.getResourcesForApplication()" which also has issues with paid app since on those assets go into the private area.
Only options i see are:
Detect greenify and ask the user to disable the feature with a popup
Greenify "greenlists" providers with "android:name" -> org.kustom.api.Provider
Greenify provides a way to disable this feature via a broadcast
Thoughts?
frankmonza said:
The provider does caching and other stuff so i cannot use "PackageManager.getResourcesForApplication()" which also has issues with paid app since on those assets go into the private area.
Only options i see are:
Detect greenify and ask the user to disable the feature with a popup
Greenify "greenlists" providers with "android:name" -> org.kustom.api.Provider
Greenify provides a way to disable this feature via a broadcast
Thoughts?
Click to expand...
Click to collapse
This issue will be fixed in the implementation of Deep Hibernation in the next version of Greenify. After that, everything will be back to what it used to be.
oasisfeng said:
This issue will be fixed in the implementation of Deep Hibernation in the next version of Greenify. After that, everything will be back to what it used to be.
Click to expand...
Click to collapse
Cool, thanks
Just curious, what are you going to change?
oasisfeng said:
This issue will be fixed in the implementation of Deep Hibernation in the next version of Greenify. After that, everything will be back to what it used to be.
Click to expand...
Click to collapse
Deep Hibernation would no longer treat newly installed apps as hibernated.
oasisfeng said:
This issue will be fixed in the implementation of Deep Hibernation in the next version of Greenify. After that, everything will be back to what it used to be.
Click to expand...
Click to collapse
Not sure if next version has been released yet but my users are still reporting the issue. If it has been released Is there any way to detect if the deep hibernation feature is enabled from another app? I mean, i can show a dialog if the provider returns 0 entries but that would be an hack since it might be something else.
oasisfeng said:
Deep Hibernation would no longer treat newly installed apps as hibernated.
Click to expand...
Click to collapse
Hi @oasisfeng did you check this issue? I will add a popup to ask the users to remove Greenify deep hibernation from next version when provider returns zero results but i'd prefer it to be solved on Greenify end, any ideas?
Hi all, I'm considering on buying the donation package of Greenify to try out the GCM Push notifications on hibernated apps but I´m not sure about it so can you please guys tell me if it's works properly and if it has any impact on the battery life?
Also, I would like to ask about the feature called "Shallow Hibernation" because I don't know what's exactly it does and the description doesn't tells much for me.
Thanks
Mr.YatekomoSan said:
Hi all, I'm considering on buying the donation package of Greenify to try out the GCM Push notifications on hibernated apps but I´m not sure about it so can you please guys tell me if it's works properly and if it has any impact on the battery life?
Also, I would like to ask about the feature called "Shallow Hibernation" because I don't know what's exactly it does and the description doesn't tells much for me.
Thanks
Click to expand...
Click to collapse
GCM Push notifications will work OK if the apps pushing notifications are developed keeping in mind Google's recommendations. Further for apps not using GCM viz. Facebook and WhatsApp etc it will have no effect.
On shallow hibernation: Till now, if you restart a hibernated app, it will have to start from the beginning and not from the background (like from 'recents'). This will consume more battery and that is why the Dev advised not to hibernate frequently used apps.
Now in shallow hibernation, the app will be kept in memory but it will not be allowed to function in the background (like syncing etc). When this app is opened again, it will start as if from 'recents' and not from the beginning. This will save more battery. This is my understanding but I don't know if I am 100% correct.
Mr.Jay said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser:
Click to expand...
Click to collapse
Where da link doe ??
I use Greenify with shallow hibernation.
I noticed that various apps like Facebook, Messenger, Whatsapp and Tapatalk sometimes are offline when I try to use (to refresh a page, to check a status or a message, etc.). After minutes and casually they return online. I'm sure that it is not a connection problem, and if I substitute shallow hibernation with normal hibernation this problem does not exists. So I think that it is a shallow hibernation bug. This happens with all the last versions of Greenify, beta and stable.
Do you have any feedback?
My system is a rooted Samsung Galaxy S5 stock 6.0.1.
rogxd said:
I use Greenify with shallow hibernation.
I noticed that various apps like Facebook, Messenger, Whatsapp and Tapatalk sometimes are offline when I try to use (to refresh a page, to check a status or a message, etc.). After minutes and casually they return online. I'm sure that it is not a connection problem, and if I substitute shallow hibernation with normal hibernation this problem does not exists. So I think that it is a shallow hibernation bug. This happens with all the last versions of Greenify, beta and stable.
Do you have any feedback?
My system is a rooted Samsung Galaxy S5 stock 6.0.1.
Click to expand...
Click to collapse
I experience something similar with Youtube, Maps and Firefox which i greenified: sometimes, when i resume them from hibernation, they can't go online. The connection is ok and other apps can connect but not those ones. Try to hibernate them again manually with the greenify button, then reopen them and see if they can connect.
Did you also disable any broadcast receiver for the problematic apps?
Are you still experiencing this problem after one year?
i'm on a sony stock 6.0.1 rom
Real question why use shallow hibernation? What problem/behavior are you attempting to address? Although native to Android 6+ it seems this mode is automatically utilized by normal/regular/standard doze as needed. I don't see a benefit to using it globally but obviously individual situations vary.
Additional background: https://greenify.uservoice.com/knowledgebase/articles/828357
Davey126 said:
Real question why use shallow hibernation? What problem/behavior are you attempting to address? Although native to Android 6+ it seems this mode is automatically utilized by normal/regular/standard doze as needed. I don't see a benefit to using it globally but obviously individual situations vary.
Additional background: https://greenify.uservoice.com/knowledgebase/articles/828357
Click to expand...
Click to collapse
I'm answering this a month later but would like to point out that for me Shallow Hibernation is amazing.
I have a device with plenty of memory for my usage, so I don't need the app to be wiped out of memory every time, just to be set as inactive.
For example, I found that Spotify is a great candidate for Shallow Hibernation.
Whenever I'm listening music on my computer, my phone has a tendency to stay awake because of Spotify Connect.
However if I shallow hibernate it, it won't keep the phone awake but still be kept in memory for me to use whenever I want. The same things goes for Maps, Youtube, and some games.
I’ve put an “Hibernate and Sleep” shortcut at homescreen and works really great.
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 settingsShallow-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...!