• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Task Killer---Yes or No ?

Thank you all for your responses. I do know enough to realize not to kill the important processes that are essential to the phones proper operation. I should have clarified my original post in that aspect. Im just wondering if i really need to use the task killer after using programs that I only use once in a while.....or is it better to just let them stop on there own.
EX: I use google maps....when Im done is it beneficial or not to kill the app as it still shows running after im done with. it. Thanks again everyone
 
Upvote 0
Thank you all for your responses. I do know enough to realize not to kill the important processes that are essential to the phones proper operation. I should have clarified my original post in that aspect. Im just wondering if i really need to use the task killer after using programs that I only use once in a while.....or is it better to just let them stop on there own.
EX: I use google maps....when Im done is it beneficial or not to kill the app as it still shows running after im done with. it. Thanks again everyone

Only if it's still using a lot of CPU or network in the background. This is a great use of System Panel. Just because an APP/service/process is running, or even active, doesn't mean it's using resources. Unless you're about to need every ounce of ram you can get (ie running a 3d game or benchmarking), IGNORE ram usage. You'll get better performance, both speed and battery life, letting android deal with it.
 
Upvote 0
Thank you all for your responses. I do know enough to realize not to kill the important processes that are essential to the phones proper operation. I should have clarified my original post in that aspect. Im just wondering if i really need to use the task killer after using programs that I only use once in a while.....or is it better to just let them stop on there own.
EX: I use google maps....when Im done is it beneficial or not to kill the app as it still shows running after im done with. it. Thanks again everyone

I personally would kill it. Anything that is in there that you yourself have opened should hurt anything by killing. I generally like to keep around 100mb free ram. System panel is the way to go cause it shows if program is using cpu or not. If its not then it hurts nothing to let it go. If your ram gets completely filled then it can slow your system though.
 
Upvote 0
I would also vouch for System Panel. I've never used ATK mainly due to the comments here, since I was a member way before even receiving the phone. So thanks everyone for the great advice (on this issue and others). I've never actually used System Panel to kill an app. Just monitor them really. If I see something on the active list that I don't think should be there, I'll actually go just back to the app and back out of it completely, since that's usually what I forgot to do. I'm not obsessive about my battery life, so I don't mind just going into System Panel to see what percentage I have remaining (as opposed to having a battery widget). I like that it also monitors my battery temp. It never feels hot, but it shows that my battery is typically between 80-90 degrees. Cause for concern? Someone on another thread said his is typically around room temp.
 
  • Like
Reactions: Markus729
Upvote 0
I am trying to make an informed decision about whether or not to use a task killer with the Android OS.

I have read bits and pieces of info in different threads from both sides but cannot find a central forum or thread discussing this, so its hard to figure out the majority opinion.

I would prefer not to use one since its just an extra step every time I use the phone....but if it is beneficial to either processor or battery or both, I will.

Any opinions and/or experiences are welcome. Thanks in advance!!!

I use one to get rid of things that I don't want running anymore, such as City ID, games I'm not playing, IM clients I'm not using, etc. I do agree with someone above, task killers can be beneficial or harmful. People here go on and on about how every time you use a task killer a puppy dies, but it all has to do with how you use it. Make sure that you don't use one that auto-kills, or turn this option off. I use Advanced Task Killer, and only to kill such applications that I mentioned above. I put all of the necessary ones (Messaging, Mail, Sense ____, Talk, Skype, Alarm, and so on) on an ignore list so that I won't accidentally kill them; I always kill the task manager with the others so that there's no chance it'll screw anything up in the background. Yes, I realize this is Linux based and things that aren't actually running aren't using CPU cycles and aren't hurting battery life. Well, unfortunately some programs DO affect things while supposedly idle. And another thing, if you run too many things w/o restarting for awhile, you will get very close to running out of memory. Android is smart, but I'd rather not have it decide for itself what applications it thinks I want running when it starts cleaning up memory for new things.
 
Upvote 0
The article seems to assume that the user is allowing the task killer to kill apps and run in the background or the user is killing tasks constantly.

I don't do either. If I open up a bunch of apps at once (which I do on occasion) I'd rather kill them all than wait for Android to do it for me. Like I said I'm not letting ATK run in the background and I've set it to ignore all essential processes. I probably use the app once every few days or so when I've just been indecisive about what I want to do on it (and thus opened up about 20 apps).

I regularly get 36-48 hours out of my stock battery, which seems to be above the norm for some folks, so I must be doing something right.

Assuming you have it just kill things you start (NOTHING that starts in the background. That will be VERY counterproductive, costing speed/battery), you're avoid MOST of the risks involved. And you might get some (not a lot, but some) battery/speed advantage. It takes some time (a few minutes) for android to shove the processes into the background, so you might lose a little battery in that time.

Here is why it still might hurt...
1. You kill something that you restart later. Instead of being loaded in the ram already, it has to use CPU/battery to reload the app. This also slows down the phone.

2. Let's say that one of the apps started a system service that uses cpu, network, or keeps the phone from sleeping. When the app is done with that service, it will close out that service. However, if you kill that app after it loads the service but before it ends, you can orphan the service, so it will run continuously. This can drain your battery like a sieve.

3. There is some potential to damage/corrupt files used by running apps. Not really a huge risk, but it's there.

Really I'd say what you're doing is GENERALLY harmless, but isn't really doing you any real good. So on a risk reward basis, you'll probably be better off not using Task Killer (or using the TK built into system panel, and only kill stuff thats using proc).
 
Upvote 0
I used to be a big proponent of NOT using a task killer, however, I have found a method that works very well for me, and my battery life.

Whenever I restart/turn on my phone, ATK automatically starts up, and I'll end any task that I don't need (including ATK so it doesn't run in the background). That's it! I've noticed a substantial increase in my battery life since using this method. After leaving work, my battery would usually be about 50%, but now it hovers around 65-70%

Take this for what you will, but if you do decide to give it a shot, let me know how it works.
 
  • Like
Reactions: one11sgt
Upvote 0
no in general, but yes on occasion
here is a good article to read, by one of the android devs
Android Developers Blog: Multitasking the Android Way

that said I too am one of the many using system panel, which has an app killer included in the monitoring app.
that sys pan was mentioned so often should be reason enough to at least look at it.
I have only needed to kill app once, some glitch in barcode scanner/camera stuck my dinc in a bad place, cpu stuck at 998mgz usage for prob an hour or more phone getting warm was what actually brought it to my attention, though it was obvious when I tried to use it, but using sys pan I was able to find the cpu eating app and kill it.
*Though it is tuff not to kill , coming from an winmo Omnia.
 
Upvote 0
Does that affect the phone functioning? I.E: receiving texts and emails. Is it like the X's battery management function which turns of data, gps, wifi etc?

You will still receive evreything just fine. Sleep is anytime the screen is off, pretty much. If you're playing music or streaming something, when the screen is off it is known as "partial wake". Something between awake and sleep modes.

Those of you using ATK, last I used it it didn't distinguish between active and inactive applications. Use System Panel. It will show you which one are actually doing something, how much CPU they're using, and tell you how much CPU time they've used recently. Any that are inactive are fine and you should leave them alone. Inactive means they are cached in RAM for the next time you open that app. This saves battery life because it takes extra power to re-cache them from your flash storage back to RAM.

Someone said this on here, and I totally agree (since Android is based off Linux). Free memory on an Android device is wasted memory. Android (Linux) has awesome memory management. If an app is inactive, leave it alone. Only kill something that is uselessly hogging resources (run amuck).
 
  • Like
Reactions: one11sgt
Upvote 0
You will still receive evreything just fine. Sleep is anytime the screen is off, pretty much. If you're playing music or streaming something, when the screen is off it is known as "partial wake". Something between awake and sleep modes.

Those of you using ATK, last I used it it didn't distinguish between active and inactive applications. Use System Panel. It will show you which one are actually doing something, how much CPU they're using, and tell you how much CPU time they've used recently. Any that are inactive are fine and you should leave them alone. Inactive means they are cached in RAM for the next time you open that app. This saves battery life because it takes extra power to re-cache them from your flash storage back to RAM.

Someone said this on here, and I totally agree (since Android is based off Linux). Free memory on an Android device is wasted memory. Android (Linux) has awesome memory management. If an app is inactive, leave it alone. Only kill something that is uselessly hogging resources (run amuck).

Don't forget only deep down is Android Linux. Apps we run, the UI, and much of what is actively running is Java. As we all know, Java is not perfect.
 
Upvote 0
I called Verizon about another matter and told them the only gripe I had with the DInc is that it killed the battery fast. He recommended that I install ATK.
I was in a local Verizon store and told the dude in there that the battery drained pretty fast and HE TOO recommended that I install ATK.
I was in a BestBuy in the phone department getting an Invisible Shield for my DInc and HE TOO recommended that I install ATK.... SO, I installed ATK.
My experience has been really good! I have it kill non-system apps every 30 minutes with no adverse effects and my battery life has improved about 30% since then.

After reading through this thread though, I have stopped ATK from running in the background and starting automatically, and have purchased/installed System Panel and will see how it compares.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones