Why You Shouldn’t Use a Task Killer On Android

Search This thread

cybervibin

Senior Member
Mar 18, 2012
2,513
1,677
Pallet town
So i saw many posts on which people have asked as to which task killer should be used !
and then i stumble upon this site which provided me the details,
i just complied info

sources-by Chris Hoffman
http://www.howtogeek.com/127388/htg-explains-why-you-shouldnt-use-a-task-killer-on-android/



Android Doesn’t Manage Processes Like Windows


Most Android users are familiar with Windows. On Windows, many programs running at one time – whether they’re windows on your desktop or applications in your system tray – can decrease your computer’s performance. Closing applications when you’re not using them can help speed up your Windows computer.

However, Android isn’t Windows and doesn’t manage processes like Windows does. Unlike on Windows, where there’s an obvious way to close applications, there’s no obvious way to “close” an Android application. This is by design and isn’t a problem. When you leave an Android app, going back to your home screen or switching to another app, the app stays “running” in the background. In most cases, the app will be paused in the background, taking up no CPU or network resources. Some apps will continue using CPU and network resources in the background, of course – for example, music players, file-downloading programs, or apps that sync in the background.

When you go back to an app you were recently using, Android “unpauses” that app and you resume where you left off. This is fast because the app is still stored in your RAM and ready to be used again.

Why Task Killers Are Bad

Proponents of task killers notice that Android is using a lot of RAM – in fact, Android stores a lot of apps in its memory, filling up the RAM! However, that isn’t a bad thing. Apps stored in your RAM can be quickly switched to without Android having to load them from its slower storage.

In summary, you shouldn’t use a task killer – if you have a misbehaving app wasting resources in the background, you should identify it and uninstall it. But don’t just remove apps from your phone or tablet’s RAM – that doesn’t help speed anything up.
Empty RAM is useless. Full RAM is RAM that is being put to good use for caching apps. If Android needs more memory, it will force-quit an app that you haven’t used in a while – this all happens automatically, without installing any task killers.

Task killers think they know better than Android. They run in the background, automatically quitting apps and removing them from Android’s memory. They may also allow you to force-quit apps on your own, but you shouldn’t have to do this.

Task killers aren’t just useless – they can reduce performance. If a task killer removes an app from your RAM and you open that app again, the app will be slower to load as Android is forced to load it from your device’s storage. This will also use more battery power than if you just left the app in your RAM in the first place. Some apps will automatically restart after the task killer quits them, using more CPU and battery resources.

Whether RAM is empty or full, it takes the same amount of battery power – decreasing the amount of apps stored in RAM won’t improve your battery power or offer more CPU cycles.

hope u understood! :D

words of wisdom by fellow-mates
go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.

oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
 
Last edited:

xxkid123

Senior Member
Jun 13, 2012
282
79
I agree with that...to an extent

Auto killing apps is plain stupid, but I do believe in killing certain apps. In a perfect world heavy apps would just be uninstalled, but plenty of useful apps without good replacements are fairly heavy, and it helps to kill them. E.g. after exiting a game I will kill it because its hogging up valuable ram by running in the background, while still using he same resources it uses at the forefront.

I understand that android, and Linux should manage ram well, but more often then not some app is just out there slowing my phone down. Even an hour later of not using that app, it'll still be in the background using up a lot of CPU and ram I don't have (more importantly battery). Android is great at managing smaller apps, but in my experience, it sucks at doing the same for larger apps.

Sent from my Desire HD using xda app-developers app
 

dxppxd

Senior Member
Feb 6, 2012
563
188
I don't use automatic task killers, those that are constantly running, but i do kill unused tasks and apps with no reason to be still running. Google services is a common example. It will launch at boot and keep running peemanently, even if you never launch a google app, google services is running, why?

A lot of apps, mostly the free ones, get revenue by reporting anonymous usage statistics (not so anonymous in some cases). So they stick a running service even if the app is never launched again (sometimes even if it isn't launched in the first place).

To sum up, killing everything is bad, but leaving everything to run free can also decrease performance. This can be observed on an android device that has been running for a long time, versus an android device that's just been reset.
 

Markuzy

Senior Member
Apr 21, 2012
529
120
Singapore
some unused tasks will repeatedly rerun even if killed.

This will further decrease battery life and affect performance as resources are needed to keep restarting it.
The best way is to ignore if it takes a small portion of resources or to uninstall the app. Rooted users may disable the triggers via certain apps.

Sent from my GT-N7000 using Xparent ICS Tapatalk 2
 

cybervibin

Senior Member
Mar 18, 2012
2,513
1,677
Pallet town
some unused tasks will repeatedly rerun even if killed.

This will further decrease battery life and affect performance as resources are needed to keep restarting it.
The best way is to ignore if it takes a small portion of resources or to uninstall the app. Rooted users may disable the triggers via certain apps.

Sent from my GT-N7000 using Xparent ICS Tapatalk 2
use auto run manager
it is the answer to most of every body's problems
 

cybervibin

Senior Member
Mar 18, 2012
2,513
1,677
Pallet town
I don't use automatic task killers, those that are constantly running, but i do kill unused tasks and apps with no reason to be still running. Google services is a common example. It will launch at boot and keep running peemanently, even if you never launch a google app, google services is running, why?

A lot of apps, mostly the free ones, get revenue by reporting anonymous usage statistics (not so anonymous in some cases). So they stick a running service even if the app is never launched again (sometimes even if it isn't launched in the first place).

To sum up, killing everything is bad, but leaving everything to run free can also decrease performance. This can be observed on an android device that has been running for a long time, versus an android device that's just been reset.

use autorun manager, keep it simple :D
 

1ceb0x

Senior Member
Jun 25, 2010
5,662
6,332
The Earth
I don't use automatic task killers, those that are constantly running, but i do kill unused tasks and apps with no reason to be still running. Google services is a common example. It will launch at boot and keep running peemanently, even if you never launch a google app, google services is running, why?

A lot of apps, mostly the free ones, get revenue by reporting anonymous usage statistics (not so anonymous in some cases). So they stick a running service even if the app is never launched again (sometimes even if it isn't launched in the first place).

To sum up, killing everything is bad, but leaving everything to run free can also decrease performance. This can be observed on an android device that has been running for a long time, versus an android device that's just been reset.

let me tell you something about google services...

when you installed your rom, you had to check two options from google services - location and another one.
if you are on stock, those options are available in settings also.

the google services are needed (you are running a google os, right?) because without it, the location feature will not work, the play store will give you headaches and not to mention, google now that needs that service like water.

if you kill that process over and over again you will not gain anything because that service will keep restarting it until you will give up. ah, you will loose a massive amount of battery if you do so
another thing, the google service is a system app. system apps have priority in resources so even if you kill now, as i said, it will restart after a few seconds because some apps that you are running are requesting that service.


as someone said here, yes, even I kill games after I stop playing, BUT, I do it from the task manager built in. Settings - Apps - Running apps etc.
 
  • Like
Reactions: Sagar_Patel

cybervibin

Senior Member
Mar 18, 2012
2,513
1,677
Pallet town
let me tell you something about google services...

when you installed your rom, you had to check two options from google services - location and another one.
if you are on stock, those options are available in settings also.

the google services are needed (you are running a google os, right?) because without it, the location feature will not work, the play store will give you headaches and not to mention, google now that needs that service like water.

if you kill that process over and over again you will not gain anything because that service will keep restarting it until you will give up. ah, you will loose a massive amount of battery if you do so
another thing, the google service is a system app. system apps have priority in resources so even if you kill now, as i said, it will restart after a few seconds because some apps that you are running are requesting that service.


as someone said here, yes, even I kill games after I stop playing, BUT, I do it from the task manager built in. Settings - Apps - Running apps etc.
if u dont want them to restart use, autorun manager :D
 

gamer.11

Senior Member
Dec 11, 2012
508
83
Ernakulam
Normally to kill a process I use the Running Tab in Apps, If any recently opened app which I feel should be closed is open I kill it!Though I leave the google services untouched!

Stopped using Task managers and Battery saving apps long time ago!
Want to really save the juice? Try Under Clocking! and killing the bloatware(saves RAM too!)
 

pendevous

Senior Member
Apr 4, 2011
310
12
Paranaque City
Instead of using a task killer to keep on eating your battery life, simply either delete the app or disable it in your system if it's a system out (eg: default browser, bloatware, etc). :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 39
    So i saw many posts on which people have asked as to which task killer should be used !
    and then i stumble upon this site which provided me the details,
    i just complied info

    sources-by Chris Hoffman
    http://www.howtogeek.com/127388/htg-explains-why-you-shouldnt-use-a-task-killer-on-android/



    Android Doesn’t Manage Processes Like Windows


    Most Android users are familiar with Windows. On Windows, many programs running at one time – whether they’re windows on your desktop or applications in your system tray – can decrease your computer’s performance. Closing applications when you’re not using them can help speed up your Windows computer.

    However, Android isn’t Windows and doesn’t manage processes like Windows does. Unlike on Windows, where there’s an obvious way to close applications, there’s no obvious way to “close” an Android application. This is by design and isn’t a problem. When you leave an Android app, going back to your home screen or switching to another app, the app stays “running” in the background. In most cases, the app will be paused in the background, taking up no CPU or network resources. Some apps will continue using CPU and network resources in the background, of course – for example, music players, file-downloading programs, or apps that sync in the background.

    When you go back to an app you were recently using, Android “unpauses” that app and you resume where you left off. This is fast because the app is still stored in your RAM and ready to be used again.

    Why Task Killers Are Bad

    Proponents of task killers notice that Android is using a lot of RAM – in fact, Android stores a lot of apps in its memory, filling up the RAM! However, that isn’t a bad thing. Apps stored in your RAM can be quickly switched to without Android having to load them from its slower storage.

    In summary, you shouldn’t use a task killer – if you have a misbehaving app wasting resources in the background, you should identify it and uninstall it. But don’t just remove apps from your phone or tablet’s RAM – that doesn’t help speed anything up.
    Empty RAM is useless. Full RAM is RAM that is being put to good use for caching apps. If Android needs more memory, it will force-quit an app that you haven’t used in a while – this all happens automatically, without installing any task killers.

    Task killers think they know better than Android. They run in the background, automatically quitting apps and removing them from Android’s memory. They may also allow you to force-quit apps on your own, but you shouldn’t have to do this.

    Task killers aren’t just useless – they can reduce performance. If a task killer removes an app from your RAM and you open that app again, the app will be slower to load as Android is forced to load it from your device’s storage. This will also use more battery power than if you just left the app in your RAM in the first place. Some apps will automatically restart after the task killer quits them, using more CPU and battery resources.

    Whether RAM is empty or full, it takes the same amount of battery power – decreasing the amount of apps stored in RAM won’t improve your battery power or offer more CPU cycles.

    hope u understood! :D

    words of wisdom by fellow-mates
    go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
    and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.

    oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
    5
    I agree with that...to an extent

    Auto killing apps is plain stupid, but I do believe in killing certain apps. In a perfect world heavy apps would just be uninstalled, but plenty of useful apps without good replacements are fairly heavy, and it helps to kill them. E.g. after exiting a game I will kill it because its hogging up valuable ram by running in the background, while still using he same resources it uses at the forefront.

    I understand that android, and Linux should manage ram well, but more often then not some app is just out there slowing my phone down. Even an hour later of not using that app, it'll still be in the background using up a lot of CPU and ram I don't have (more importantly battery). Android is great at managing smaller apps, but in my experience, it sucks at doing the same for larger apps.

    Sent from my Desire HD using xda app-developers app
    5
    I don't use automatic task killers, those that are constantly running, but i do kill unused tasks and apps with no reason to be still running. Google services is a common example. It will launch at boot and keep running peemanently, even if you never launch a google app, google services is running, why?

    A lot of apps, mostly the free ones, get revenue by reporting anonymous usage statistics (not so anonymous in some cases). So they stick a running service even if the app is never launched again (sometimes even if it isn't launched in the first place).

    To sum up, killing everything is bad, but leaving everything to run free can also decrease performance. This can be observed on an android device that has been running for a long time, versus an android device that's just been reset.
    2
    I don't use automatic task killers, those that are constantly running, but i do kill unused tasks and apps with no reason to be still running. Google services is a common example. It will launch at boot and keep running peemanently, even if you never launch a google app, google services is running, why?

    A lot of apps, mostly the free ones, get revenue by reporting anonymous usage statistics (not so anonymous in some cases). So they stick a running service even if the app is never launched again (sometimes even if it isn't launched in the first place).

    To sum up, killing everything is bad, but leaving everything to run free can also decrease performance. This can be observed on an android device that has been running for a long time, versus an android device that's just been reset.

    use autorun manager, keep it simple :D
    2
    To clarify things a bit: Like already said, Android has its own task-killer. It automatically kills tasks, when theres only few RAM available. It manages the whole life-cycle of every app. The problem is, it is not optimized to a certain amout of RAM, like 256 or 512 mb, which makes it bad and laggy if you have got a phone with low RAM.
    However, task-killers may sometimes seem to make those phones faster, but thats mostly not true, because it(the task killers) messes with the build-in task-killer of Android.

    ---------- Post added at 06:10 PM ---------- Previous post was at 05:49 PM ----------

    The solution is, to tune the values and settings of the default build-in task-killer. That definitly is the best option. A few scripts like the v6-supercharger scripts try to do that, also Roms like the cyanogenmod are tweaked really good.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone