I have a doubt from starting about what exactly does a task killer do and Greenify do.
I know that greenify force stops the applications which we list to be hibernated. Thought they are force stopped, the memory on the ram is not cleared if we notice, so the application opens quickly when reopened. But how is the ram not cleared even after force stopped?
Also what does a task killer do?? does it not force stop the application. Does it follow another procedure to kill the app which makes it more battery consuming?
One more thing which is more confusing is, what does clearing recent apps from the phone swiping does? From my observation it actually does the same as Greenify.
Can somebody please explain me all this.
Related
Seems like many applications spring back up after "killing" them though the Android task manager or any of the task managers available in market. Is annoying the hell out of me. If im not using the app I dont want it to.run in the background..
I understand that messaging applications need to run in background but not all.
How do you guys make sure
that any application which you close "remains" closed until the next time you open it?
Thank me if I helped you..
~n0tr1x on t989~
You might try Gemini app manager to disable auto start apps
Sent from MARVEL using Tapatalk 2 Beta-4
Easy Task Killer can help too..
use Easy Battery Saver too along with it!
Thanks.for your replies guys. However.i believe the main question here is,.how.to.stop these background app processes from running until the next time I start them manually.
Problem with task managers is that they stop these apps after a certain interval. Once they do, the.apps restart after 2-5 seconds. And.remain there till the next interval of the task killer is reached. This in turn take up more memory a compared to keep the running.. In addition, these apps run in the background on their own taking up a junk of memory/processor space..
Thanks again for your replies. Please correct me.if my understanding is wrong and you are feel otherwise.
Thank me if I helped you..
~n0tr1x on t989~
Those "apps" that you say keep opening are actually the processes running in the background. I know of many apps that keep re-enabling their processes after killing them. (IE: Facebook, some Google stuff, and a couple games that run in real-time)
Best solution: try to go into the app's settings and see if there is an option to disable anything that would require a background service to run, IE: sync, updates... If not, then just stop killing that app. Ignore it in the list or set a task killer to ignore it. If the app keeps re-opening, you killing it all the time is only doing bad because it puts more stress on the operating system because it has to take the time to reinitialize the app/service. If you are really that anal about background running apps, set android to limit a lower amount of background apps to run.
Like asdot suggested above use Gemini App Manager to disable the apps autostart permissions. If an app is set to automatically start after a certain intent is broadcast by the system (ie, at boot, or at a change in connectivity, etc.) you can use Gemini to stop that app from automatically starting. You can stop an app from automatically running in the first place instead if trying to kill it after it has started.
Hello!
I installed ES task manager today on my new Nexus 7 and I was shocked to see that several apps are consuming 20mb+ of RAM when I don't even have them open, such as Titanium Backup, Facebook Messenger, PIE Controls, Auto Hide Softkeys. Even apps like YouTube, Gallery, Chrome, Currents and Hangouts seem to be running and using RAM and I have never opened any of these applications before. The actual app switcher shows that I have no apps open, yet ES Task Manager reports that 25% of my CPU is being used. All in all, an almost fresh install of Android idling is consuming 1GB of ram and 1/4th of my CPU time.
I have Googled this issue and discovered that many people are annoyed at developers who have background services, and sometimes even refuse to use an app that has such background services, but I haven't been able to discover why these background services use so much RAM (or even why titanium needs a background service), and I would really like to be able to just kill Chrome, Youtube, Currents etc because I never use these, but of course when I kill them in ES Task Manager they re-open within several minutes.
Can anybody shed some light on what's going on here? From what I can gather after searching around the forums, some people advocate the use of task killers, and some people also say killing all these services and apps just makes battery life even worse.
Edit: google+ is using 20mb of ram and I never even use it-- why!
If you are rooted you can use apps like Greenify to pause them temporarily until you run them. You can also use apps like Clean Master that will kill all task on every screen off. Ultimately you can remove these apps that are taking up a lot of ram as the best solution.
youngnex said:
If you are rooted you can use apps like Greenify to pause them temporarily until you run them. You can also use apps like Clean Master that will kill all task on every screen off. Ultimately you can remove these apps that are taking up a lot of ram as the best solution.
Click to expand...
Click to collapse
Wow, didn't know something like greenify existed, thank you!
hi there
as you know , mi a3 and other android one devices won't force stop apps when we close them from resen apps !
for that problem i use Kaspersky Battery Life , but to avoid installing any third party apps , is there any module or trick to force stop them in recent apps menu ?
Simple apps with no background service will close when they are cleared from recents. Those with background service need to be force stopped, but depending on their configuration, they might just start back again. Constant killing and relaunching of apps wastes your CPU cycles and battery, there is no reason to kill all apps at once. The proper way is to either disable their services, broadcast receivers, hibernate them (Greenify) or uninstall/disable them.
My background apps are killed way too often. Is it possible to change that behaviour? Even music apps are killed while I'm playing music.
I have tried several custom roms and kernels but nothing seems to change the settings. Is either able to change RAM management settings?
I have also tried several apps that claim to be able to change RAM management settings without success.
Disabling battery optimisation doesn't help.
I have uninstalled unused apps and disabled autostart (boot completed receiver) for non-essential apps to reduce RAM usage.
When I use a RAM monitor it will show RAM usage at ~75% when apps are killed.
My old phone (Note 4) only had 3 GB ram but could still keep more apps in memory.
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
ChazzMatt said:
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
Click to expand...
Click to collapse
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Telorast said:
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Click to expand...
Click to collapse
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Worth a try. Installed Greenify and added most apps with ignore background-free.
Telorast said:
Worth a try. Installed Greenify and added most apps with ignore background-free.
Click to expand...
Click to collapse
I even hibernate alleged background free apps, just in case.
ChazzMatt said:
Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Click to expand...
Click to collapse
VERY TRUE!
This always infuriated me, not just on phones, PCs too, all the way back to the DOS days. An obsession with running in the background, as if it's particularly clever. :cyclops:
I've also found that turning off battery optimization for apps I don't want killed helps. I've had the same experience with music and podcast apps getting killed in the background and turning off their battery optimization usually fixes it.
There are some simple things to try that do not require any special apk's. One is to look in the apps section of the "Developer options" sub-menu. The default settings work well in most instances. Perhaps you accidently enabled closing of apps when a background limit has been reached or have ticked force closure of apps on exit.
Another place to look is in the "Power saving exclusions" sub-menu in the Battery settings. Music makes some boring forms of exercise less tiresome and provides additional motivation for activities that are challenging but fun (mountain biking). The music should not stop, but it might for default settings. Enabling a power saving exclusion for your music app will keep it running.
ChazzMatt said:
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Click to expand...
Click to collapse
Been using Greenify for a bit now and doesn't seem to help much. It shows a bunch of hibernated apps but multitasking is still nearly impossible.
I had assumed the problem was related to the Mem Free settings rather than actual free memory but no one here has mentioned it. Is that because no one else thinks it's the problem or maybe I have misunderstood what those settings do?
I thought apps were free to use as much memory as they want until certain thresholds on total memory usage were met, then the system would ask or force apps to release memory.
Apps that let you edit those settings usually shows several thresholds where the system gets progressively more aggressive at freeing memory as memory is running out. But they all look hopelessly out of date so maybe it works completely differently today?
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.