[Greenify] themadproducer:
Stupifier,

I am not going to try to convince you nor do I have the time to make you understand exactly why I came to these conclusions, but I can offer you this advise based on tons of experience:

Just run Greenify in Auto Hibernation mode. Your 2 main concerns should be to stop misbehaving power hungry apps from screwing around when the screen is off and in standby....and to keep certain apps from hogging RAM when you rarely use them and/or if they keep re-spawning. Although the modern Android OS manages ram effectively, low memory devices will benefit if certain UN WANTED apps just stay out of the way until the rare time when you NEED them...especially if they stubbornly keep re-spawning.

If you use an "AutoStarts" type of app to restrict certain apps from loading into ram during boot...then you could let Greenify take over this job...except that initially the apps would load...but then after Greenify kicks in, the apps would be removed from ram. Greenify is 99% more likely to keep those apps dormant. Sometimes even when you use an AutoStarts app or an APP KILLER, stubborn apps will still get triggered back into ram. (eg Maps) Greenify uses a better method of subduing these apps.

Another use for Greenify is if you have a really poorly written apps that is busy even when the screen is on. I haven't seen many examples of that.

I sometimes use a MANUAL SHORTCUT to Hibernate apps on command, but it's more for just testing....because most of the problem apps are already hibernated.

Something that has come in handy for me is certain apps can only be exited by clicking my menu button and then choosing EXIT. I find that to be a hassle. For those apps, I create a Tasker TASK which is set to Hibernate that specific app (eg Navigation), I then place that Tasker Task shortcut into an OVERLAYS profile. When I run Navigation, I get a floating Tasker Shortcut, that when clicked, it hibernates my maps, thus fully exiting it and removing it from ram.

Your original list with answers in BLUE below....

1. Trigger Hibernation only when Screen Off at set intervals.

Not necessary, redundant, just use auto hibernate as detailed above.

2. Trigger Hibernation at set intervals regardless of Screen Status.

Not Necessary, too obsessive, not real gain...probably more of a battery drainer itself.

3. Trigger Hibernation based on power-hungry app open/close status.

Tasker will have issues detecting whether certain apps are open or closed if they use a SERVICE as well as a PROCESS. An example is PowerAmp. Tasker has a difficult time with this app. It thinks it's always alive because PA keeps a Service alive. (might be an option in PA though)

4. Trigger Hibernation based on Time-Of-Day....for example, when I know I'm not using phone (sleeping).

NOPE...once your screen turns off, and 3 mins later, greenify kicks in, then all apps will stay hibernated. WAIT, what if you get a notification from an app, then the screen will turn on, and then when it turns off, Greenify will kick in again 3mins later.

5. Any other ideas?

Gave you some above already. Hope they are helpful.

But my favorite trick is the Overlays + Tasker Hibernate floating button which appears when certain said apps are in the foreground.

Good Luck:D:good:

---------- Post added at 05:29 PM ---------- Previous post was at 05:20 PM ----------

Always experiment and please let us know if you get positive results or new and better ideas....BUT.....greenifying apps every 5 mins is counter productive. Imagine filling your gas tank to full, parking your car in your garage and not using it ever, but every 5 min, you check the fuel level. There is no point to it.

Once is enough per screen off. If it wasn't enough, then this app would not deserve it's merit. It would be a very disrespected app since in essense, it would not be doing what it claims to be able to do. Just saying. ;)