auto hibernate when app is closed : eg. FB, music players many other apps & services stay on even no need after closing.
If anybody know how to auto stop these with other apps or tricks, plz let me know!?
Per App Hacking doesn't help..
------
auto start when screen is on : eg. I don't need clean master to stay on when I'm not on wifi and screen is off.
again, any workaround for this?
Greenify is already the greatest app out there, but if it had these features, it would b God of apps IMHO
kennyk09 said:
auto hibernate when app is closed : eg. FB, music players many other apps & services stay on even no need after closing.
If anybody know how to auto stop these with other apps or tricks, plz let me know!?
Per App Hacking doesn't help..
------
auto start when screen is on : eg. I don't need clean master to stay on when I'm not on wifi and screen is off.
again, any workaround for this?
Greenify is already the greatest app out there, but if it had these features, it would b God of apps IMHO
Click to expand...
Click to collapse
I think that you have not understood the working of Greenify correctly. It comes into play for hibernation only after the screen is off. When screen is on, it merely collects info about the apps that are running, closed etc to determine which apps are to be hibernated once screen is off.
Reg. auto hibernation, do you have root and have you enabled it in Device Administrator and Accessibility under Settings? Under which mode are you running Greenify: Root, Boost or Unrooted? And have you enabled Auto hibernation within Greenify and selected the apps to be greenified?
Check the thread title
tnsmani said:
I think that you have not understood the working of Greenify correctly. It comes into play for hibernation only after the screen is off. When screen is on, it merely collects info about the apps that are running, closed etc to determine which apps are to be hibernated once screen is off.
Reg. auto hibernation, do you have root and have you enabled it in Device Administrator and Accessibility under Settings? Under which mode are you running Greenify: Root, Boost or Unrooted? And have you enabled Auto hibernation within Greenify and selected the apps to be greenified?
Click to expand...
Click to collapse
It's a wish list. you don't understand what wish list is?
I fully understand how Greenify works.
Use Tasker and task kill plugin.
And for Greenify create hibernate shortcut and don't forget that it won't hibernate of application is in recent Apps list.
It's easy to kill every app on exit.
Just use LMT(PIE) app , and instead of standard ''home, or back button'' use ''KILLAPP'' button from PIE menu.
In combination with greenify it works fine.
I was think to use only PIE(pie ''kill app process'' on exit), but this is not the same, greenify realy put this apps in hibernation.
So i must use combination of these 2.
Would be great, that greenify do this itself..
Related
Hi
First of all thank you Oasis for creating a tool to fix things that shouldn't be broken to begin with! You are an example for a lot of developers :good:
I've read the first couple of posts on the original thread but I still have a few things that are not clear..
The advice of Oasis himself is too hibernate only those apps that misbehave. He states that hibernating apps will also remove them from the memory, which will come with a performance/cpu usage penalty when you want to use them again.
In the video tutorial however Josh greenifies almost every application that doesn't need push notifications.
So this would mean that when I use an application that doesn't have notifications but I open frequently, for example Nu.nl, a dutch newsapp, it will always have to reload the app from scratch instead of loading it from memory?
So baically the best way to use Greenify would be to NOT just greenify most apps, but to use the analyzer frequently and see what's running in the background and greenify those that don't depend on notifications?
Then newsapps that don't push news, image viewers, file managers, system tools like SD Maid and simple games that don't use internet should be ok not being greenified?
Is there no big list available of apps that misbehave or are safe to keep de-greenified?
Thanks in advance for any help on this.
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
marchrius said:
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
Click to expand...
Click to collapse
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
latino147 said:
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
Click to expand...
Click to collapse
"Disable Service" (and "Autostarts") from play store.
marchrius said:
"Disable Service" (and "Autostarts") from play store.
Click to expand...
Click to collapse
Ah, I believed those were two functions withing Greenify I couldn't find
wtf, FB has 62! services! None of them where active though, until you open the app, then it was 3.
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
The only issue with this second method being that you don't always really know what these services do.
latino147 said:
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
Click to expand...
Click to collapse
Exactly. Take google play services for example. If you greenify it, you'll lose gcm and other functions and that's not advisable at all (in fact greenify hides it). But with disable service (and autostarts/system tuner)you can choose what to disable while still mantaining gcm, location services (when needed), sync etc. I can' remember what I did in system tuner regarding gplay services (I followed some tutorial), but with disable service I disabled analyticsservice (this one will reactivate itself unless you do some tweak with system tuner), refreshenabledstateservice, playlogreportingservice, googlehttpservice, playlogbrokerservice, adrequestbrokerservice, gcmschedulerwakeupservice, advertisingidservice, adsmeasurementservice, locationwearablelistenerservice, nlplocationreceiverservice, geocodeservice, dispatchingservice and playlogservice. A reboot is needed. Haven't lost a single function since weeks (gcm, location, autosync and every google app in general are working 100% fine).
Same story with play store. Apps wake it very often, so greenify it does more harm than good. Instead, you can disable pendingnotificationsservice, contentsyncservice and dailyhygiene (and will still be fully functional).
Of course these are little tips to increase performance and battery life even more. I use greenify for 90% and more of apps that "misbehave" and disable service/autostarts/system tuner for the remaining 10% "misbehaving" apps. However, an app "fixed" with such methods will stay cached while with greenify is completely closed (resulting in more cpu/time/battery consumption when loaded again).
The only issue with this second method being that you don't always really know what these services do.
Click to expand...
Click to collapse
Like I already said, for general purposes you'd better simply greenify the "misbehaving" apps. If you use it/it is woken very often, you can consider these methods.
Yes, it's a "trial and error" thing. Unless you're disabling services with self-explainatory names such as "pushservice".
Never installed Facebook official app but I heard many times that is a notorious hogger and takes many personal datas too, for which you can look for xprivacy xposed module as well.
I'll start experimenting with it today :good:
I often see a few apps running in the background and wonder why they are not Grenified. This happens to me most with YouTube, Google Drive & Titanium Backup. There doesn't seem to be a reason why they should run in the background, thus I'd expect them to be hibernated by Greenify.
I have a rooted LG L7 II device running CM11.
Digdis said:
I often see a few apps running in the background and wonder why they are not Grenified. This happens to me most with YouTube, Google Drive & Titanium Backup. There doesn't seem to be a reason why they should run in the background, thus I'd expect them to be hibernated by Greenify.
I have a rooted LG L7 II device running CM11.
Click to expand...
Click to collapse
Did you Greenify those apps? I had to ask since you didn't specifically say so. Also, is Greenify enabled in Device Administrators and Accessibility settings? And are you running Greenify in Root mode or Boost mode?
tnsmani said:
Did you Greenify those apps? I had to ask since you didn't specifically say so. Also, is Greenify enabled in Device Administrators and Accessibility settings? And are you running Greenify in Root mode or Boost mode?
Click to expand...
Click to collapse
Thanks. Gotta to admit that I didn't Greenify them manually, but waited for Greenify to do it automatically. I now sent them manually to hibernation and will keep track on whether they run in the background as they did before.
However, isn't the whole point behind Greenify that you don't need to do it manually, but let Greenify do that for you? AFAIK, neither of these apps have anything to do in the background, so isn't Greenify supposed to notice that and send them to hibernation?
Digdis said:
Thanks. Gotta to admit that I didn't Greenify them manually, but waited for Greenify to do it automatically. I now sent them manually to hibernation and will keep track on whether they run in the background as they did before.
However, isn't the whole point behind Greenify that you don't need to do it manually, but let Greenify do that for you? AFAIK, neither of these apps have anything to do in the background, so isn't Greenify supposed to notice that and send them to hibernation?
Click to expand...
Click to collapse
Greenify doesn't automatically greenify(!) any app. There are many apps running in the background, some required, some not required. So you make the choice to greenify whatever you choose to, depending on your requirements. This is because if you greenify all the apps running in the background, you will lose some functionality. While you may choose to greenify one particular app because you don't need it to run in the background, I may not agree with you since I may require its functionality. So to each his own. That is the beauty of Greenify, that it allows you to choose.
However, once you greenify a particular app, Greenify takes over and further greenifying that app is automatic.
tnsmani said:
Greenify doesn't automatically greenify(!) any app. There are many apps running in the background, some required, some not required. So you make the choice to greenify whatever you choose to, depending on your requirements. This is because if you greenify all the apps running in the background, you will lose some functionality. While you may choose to greenify one particular app because you don't need it to run in the background, I may not agree with you since I may require its functionality. So to each his own. That is the beauty of Greenify, that it allows you to choose.
However, once you greenify a particular app, Greenify takes over and further greenifying that app is automatic.
Click to expand...
Click to collapse
Thanks for your answer. I did Greenify apps manually in the past, ones that I considered their running in the background as unnecessary (such as a shopping app I had which kept notifying me of new deals). However, I thought that Greenify could somehow identify apps who run in the background without need, and so it would send them to hibernation automatically. Guess I was wrong here.
So I was wondering if there is a way to add this functionality, or if it's already possible and I just didn't see it.
Picking and choosing individual apps to put in auto-hibernation.
Example: I have google play music on greenify and it auto hibernates. Even when I'm listening to music.
So is there a way to deselect it from auto hibernation without completely shutting it off.
StonerSteve420 said:
So I was wondering if there is a way to add this functionality, or if it's already possible and I just didn't see it.
Picking and choosing individual apps to put in auto-hibernation.
Example: I have google play music on greenify and it auto hibernates. Even when I'm listening to music.
So is there a way to deselect it from auto hibernation without completely shutting it off.
Click to expand...
Click to collapse
In Greenify, select the app you want to degreenify. Touch the menu button in Greenify and one of the options will be 'degreenify the selected app'. Select it and that particular app will be degreenified and will no longer be auto-hibernated.
tnsmani said:
In Greenify, select the app you want to degreenify. Touch the menu button in Greenify and one of the options will be 'degreenify the selected app'. Select it and that particular app will be degreenified and will no longer be auto-hibernated.
Click to expand...
Click to collapse
I still would like to be able to greenify it. I use the widget to greenify apps at once and google play music doesn't close all the way when I exit the app that's why I'd still like it being apart of the greenify list just not on auto hibernate
StonerSteve420 said:
I still would like to be able to greenify it. I use the widget to greenify apps at once and google play music doesn't close all the way when I exit the app that's why I'd still like it being apart of the greenify list just not on auto hibernate
Click to expand...
Click to collapse
Either you have all the greenified apps auto hibernate or manually hibernate. You can't have some on auto and some on manual, as far as I know.
tnsmani said:
Either you have all the greenified apps auto hibernate or manually hibernate. You can't have some on auto and some on manual, as far as I know.
Click to expand...
Click to collapse
Yeah that's what I figured. Didn't know where to suggest an idea maybe they can implement this
StonerSteve420 said:
So I was wondering if there is a way to add this functionality, or if it's already possible and I just didn't see it.
Picking and choosing individual apps to put in auto-hibernation.
Example: I have google play music on greenify and it auto hibernates. Even when I'm listening to music.
So is there a way to deselect it from auto hibernation without completely shutting it off.
Click to expand...
Click to collapse
I am not entirely sure, but Greenify has a Tasker plugin. So you could set up a Tasker profile that will hibernate a specific app only when you want it to be hibernated, not in combination with other apps.
Give it a try and - taking your example with Google Play Music - de-greenify GPM completely and try to hibernate it with Tasker.
I want to use greenify to "freeze" a certain apps when are not in foreground, do don't check in the background for location, connect to internet to update, and so on and so forth. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
scandiun said:
I want to use greenify to "freeze" a certain apps when are not in foreground, do don't check in the background for location, connect to internet to update, and so on and so forth. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
Click to expand...
Click to collapse
Look elsewhere. Greenify doesn't "freeze" any app.
tnsmani said:
Look elsewhere. Greenify doesn't "freeze" any app.
Click to expand...
Click to collapse
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
scandiun said:
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
Click to expand...
Click to collapse
My understanding is, when you add apps to the autohibernate list and when you continue to work with one app in the foreground, any other hibernated app will continue to run (if started while you are working or if already running) till the screen is locked. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
tnsmani said:
My understanding is, when you add apps to the autohibernate list and when you continue to work with one app in the foreground, any other hibernated app will continue to run (if started while you are working or if already running) till the screen is locked. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
Click to expand...
Click to collapse
Yes Hibernation Manager and Greenify only work when screen is off. That's enough for me, but do you know if any app that does it also when the screen is on? (App always hibernating unless on foreground)
i was wondering..... some apps like greenify or superfreezZ use accessibility usage to track the app behaviour and auto hibernate them, but since android 9 there is a new command to restrict the background activity of an app and it is RUN_ANY_IN_BACKGROUND
you can simply enable in app info>battery>background restriction set to RESTRICT.
is it a "better" way to hibernate an app and stop all trackers, alarms and services that DRAIN the phone battery? or maybe it's is less powerfull than "force stop" the app?
how does compare DOZE to RUN_ANY_IN_BACKGROUND ? i suppose 1st is a generall switch off for all apps, BUT only on screen off. when you use the phone the "bad" app could continue to do what he wants, wakelocks, call some strange domains to receive or updload datas.... BUT WHAT IF it is restricted by RUN_ANY_IN_BACKGROUND? the app is not force stopped but should be something like hibernated when it's not foreground....?
i found some info here
App Power Management | Android Open Source Project
source.android.com
realista87 said:
i was wondering..... some apps like greenify or superfreezZ use accessibility usage to track the app behaviour and auto hibernate them, but since android 9 there is a new command to restrict the background activity of an app and it is RUN_ANY_IN_BACKGROUND
you can simply enable in app info>battery>background restriction set to RESTRICT.
is it a "better" way to hibernate an app and stop all trackers, alarms and services that DRAIN the phone battery? or maybe it's is less powerfull than "force stop" the app?
how does compare DOZE to RUN_ANY_IN_BACKGROUND ? i suppose 1st is a generall switch off for all apps, BUT only on screen off. when you use the phone the "bad" app could continue to do what he wants, wakelocks, call some strange domains to receive or updload datas.... BUT WHAT IF it is restricted by RUN_ANY_IN_BACKGROUND? the app is not force stopped but should be something like hibernated when it's not foreground....?
i found some info here
App Power Management | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Force Stop = "Hibernate"
Force Stop = App is killed and removed from memory, and (for the most part) not be able to start itself up again. User can. I read you asked the exact same question elsewhere and some talked how apps can restart themselves. Yes, its true BUT its the exceptioopn, not the rule. The only app that ciones to mind at the moment in my past is Google Play. His statement is misleading in practical everyday use. Test it for yourself.
I havent used it, but, RUN_ANY_IN_BACKGROUND explicitly requires the "deny" or "allow" attribute. The app is still in memory and therefore would have some possibility of bringing itself back to life; much more so than a force-stop. Some apps are developed with running a service as a foreground app. Also, RUN_ANY_IN_BACKGROUND is a TESTING feature of android.
ie Force Stop > RUN_ANY_IN_BACKGROUND
I have a hot spot on my home screen (custom launcher allowing scripts) that turns my screen oof and then force-stops all apps that I do not want running in the background.
You want an app to stop consuming battery, then force-stop is the way to go.
"RUN_ANY_IN_BACKGROUND is a TESTING feature of android."
mhhh so u say that not every app will really stop his background behaviour for sure? i thought that the command is quite sure to keep a closed app a "not battery hungry" app, stopping some services, alarms.
basically if u would choose an app to force close apps, would u choose superfreezz (because it s foss) over other alternatives like greenify or brevent?
because i would avoid to install any app for this, IF the command RUN_ANY....... is to consider quite powerfull and acceptable to "stop draining " battery from malicious apps...
realista87 said:
"RUN_ANY_IN_BACKGROUND is a TESTING feature of android."
mhhh so u say that not every app will really stop his background behaviour for sure? i thought that the command is quite sure to keep a closed app a "not battery hungry" app, stopping some services, alarms.
Click to expand...
Click to collapse
If you want to stop it, the a force stop is the way. Its much more "powerful" than what you found.
realista87 said:
basically if u would choose an app to force close apps, would u choose superfreezz (because it s foss) over other alternatives like greenify or brevent?
because i would avoid to install any app for this, IF the command RUN_ANY....... is to consider quite powerfull and acceptable to "stop draining " battery from malicious apps...
Click to expand...
Click to collapse
I explained to you, I use a shell script to get the job done. No need for another app, that also may consume unnecessary battery and memory.