[OnePlus 3 Guides, News, & Discussion] Asiier:
I cannot Greenify or Doze neither WhatsApp or Snapchat because my GF will get mad because I wouldn't receive her messages...

For the best idle you should not use Shallow since it will wake up the device and no, don't enable aggressive doze on Greenify ( Although this doesn't substitute Shallow hibernation, both can be enabled)

Use Naptime or ForceDoze enable Aggressive Doze and disable motion capture for longer time on deepsleep.

Then try ForceDoze, for some reason I have no problem using it or I might got used to it.

I know!! The only bad thing is that cannot be configured further.

For example I don't want Snapchat to be woken up until I open it, but I want Instagram to be woken

It's either both or non

Aggressive Doze ( Not the one from Greenify) + Shallow hibernation it's fine

*Explantion for Shallow hibernation*

Apps will no longer be killed in shallow hibernation, with interaction context preserved for snappier task switching, while all the background behaviors are still strictly prohibited during hibernation.

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.

If enabled, shallow hibernation replaces the classic hibernation mechanism throughout Greenify.

What this means?

Basically what Greenify does is kills the app more or less like Force Close. This prevent the app to be woken unless you open the app which is really good for our battery.

Although, if they are some background services, the app might be woken up again.

Examples: Facebook, unless we use Deep Hibernation it will be woken up sooner or later

If you have enable certain app to read Notifications or have Accessibility access they will instantly woken up because this.

For this, you shouldn't enable all app on reading Notifications etc...

What does Shallow hibernation is to store the apps on your RAM, like Android would do but they are hibernating and not killed so can be woken up.

The advantages of this?

Apps can be reopen a bit faster and you will receive notifications from this app, since every X time they will be slightly woken up for listening to GCM pushes (notifications)

This will only work with apps that implement this.

Problems:

They will consume more battery, not only when they are woken but a little bit while idling.

It cannot be configured, neither the X seconds when the apps are woken nor the apps that are woken.

As I said before, we might don't want that certain app will be woken but we wait it to be Greenified.

I think it's a really promising feature and I'm sure that with more time and development all the problem will be solved.

I personally use it. Apps will no longer be killed in shallow hibernation, with interaction context preserved for snappier task switching, while all the background behaviors are still strictly prohibited during hibernation.

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.

If enabled, shallow hibernation replaces the classic hibernation mechanism throughout Greenify.