Automatic Task Killer |
How to properly set up and use a task killer (Oh, yes, I went there!) sums up what I was thinking in these seven bullet points.
Just be selective on what you kill and do not kill everything. If you run into issues with a program double check if it is being killed by a task killer. If it is uncheck the program and see if the program still has issues.
Recommended Reading:
The Definitive RSS Guide for Bloggers
Google Official Google Reader Blog
- Any application that has the manufacturer or carriers name in it should never be killed.
- Any application that has the word android. (yes the period is there on purpose) should never be killed.
- Any application that keeps time should never be killed.
- Any application that has a widget that updates should never be killed.
- Any application that is not installed on /data (this is where user apps go) should never be killed.
- If you can't figure out exactly what an application is, it should never be killed.
- Home replacements, whether from the Market or your manufacturer never should be killed. This also means Sense, Blur, and Touchwiz. They also have dependencies that should stay alive, refer to numbers 1, 5 and 6 above. Of course if you're a tinkerer, and know which parts of the system you don't need running on your particular installation, feel free to experiment. And share your results.
Just be selective on what you kill and do not kill everything. If you run into issues with a program double check if it is being killed by a task killer. If it is uncheck the program and see if the program still has issues.
Recommended Reading:
The Definitive RSS Guide for Bloggers
Google Official Google Reader Blog
No comments:
Post a Comment