Quantcast

Android Task Killers are Dead—Here's What You Should Be Doing

By Ryan Whitwam

With recent updates, Android doesn't need task killers the way it used to. Is it finally time to ditch the task killer?

As a general rule, people have a hard time dealing with change. Android, being perhaps the fastest changing mobile OS in history, can leave people in the dust as the platform evolves. Things don't work the same from release to release. Some of this is user-facing, and people can adapt. But some changes are deeper system level alterations that people might not notice at first, and then might not understand why they've changed. The functionality and usefulness of task killers is one such advance. A lot has changed in the underlying Android OS regarding how background processes are managed. 



How task killing became dogma

The solution, at the time, was to use task killer apps.  

Task killers like Advanced Task Manager and Advanced Task Killer became extremely popular in the Android Market because people saw performance and battery life benefits from ending background services. It was the snowball effect from here on out. Every new Android user was told to go get a task killer first thing when buying a new phone. Some carriers even included them on on phones and recommended them to customers. It became Android dogma that you had to kill tasks. 

But starting in Android 2.0, memory management got much, much better. Apps couldn't spawn processes only to leave them forever. The OS would gauge the level of system RAM, and close unneeded background services. Users on phones like the Droid could clearly tell that this was happening. With only 256MB of RAM, some memory-heavy apps would reliably cause the OS to close other apps running in the background. This is why many apps now use persistent notifications. Having that notification running will keep a background process it is connected to from being ended.  

What Froyo changed

When Android 2.2 Froyo was released, users and developers alike noticed something had changed again. Task killers didn't work properly anymore. If a user closed a particular app, it would just show up again. That's because the API for closing other tasks was removed. Now the "end" command has basically become "restart". Only the immediate background app can be closed. Associated services will stay put.

more battery trying to free this memory. The apps will just restart, putting additional strain on the system. The only way to completely end a process now is to find it in the Manage Applications area of the Settings app, then tap the Force Stop button. It's just as destructive as task killing was, but it is more hidden and not accessible via an API.

Google likely changed the API because ending tasks at random can cause system glitches in the worst case. At best, you'll likely notice worse performance from your apps as they try to reconcile their assigned tasks with the fact that you are constantly interrupting them by ending them. 

What you should be doing

Watchdog. We told you all about it a few weeks ago in a Market Roundup. Check that out for the full rundown. 

What Watchdog basically does is poll the CPU to watch for apps that are getting greedy. This is really the holy grail of Android process management. It's quiet, sits in the background, and solves most of your task management needs. You'll be alerted if something goes wrong, and then Watchdog will allow you to restart the offending task. While doing this with an app that isn't misbehaving is a bad idea, you have little choice in cases when an app is legitimately out of control.  

Users with root on their device are able to undertake some additional steps to control tasks on Android. An app we really can't live without on our rooted handsets is called Autostarts. We introduced you to this last month, but we keep finding reasons to recommend it. Killing processes is a bad thing for system stability and battery life (especially under Froyo), but Autostarts lets you keep unneeded apps from starting up in the first place.  

Titanium Backup.  

Also for root users, is an app called AutoKiller. Don't let the name fool you; it isn't an aggressive task killer that's going to make your apps go all wonky. All it does is tweak the Android process manager to be more aggressive in ending background services. This won't end tasks midstream, it just ends unneeded apps a little sooner. You mileage may vary, some users find this helps quite a bit, others not so much. 

Most users that adopt a more modern way of managing (or not managing) their tasks see a big upside. A phone can feel faster, and the battery may last longer. When it comes down to it, killing tasks is just a hassle you don't need to deal with anymore. Everyone on Android 2.0 and higher should rely on Watchdog, or an app like it, to monitor for runaway background processes.  
    
As more Android users are bumped up to Froyo, or just buy new devices, they will find their task killers inoperable. It's important they are steered away from this obsolete method of task management. Tell us about your task killing experiences in the comments.
 
Image credit: Flickr user Johanl