3 ms·

If your friends are teaching you to use advanced task killer, they're teaching you wrong. That shit is snake oil. See these links for more info: http://geekf

If your friends are teaching you to use advanced task killer, they're teaching you wrong. That shit is snake oil. See these links for more info: http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-wi... http://android-developers.blogspot.com/2010/04/multitasking-android-way.html http://android-developers.blogspot.com/2010/04/multitasking-...

slouch 15y ago
i'm not trying to defend a task killer so much as the act of terminating applications. i used to "force stop" apps from the applications menu before i got the killer. that said, low memory situations exist. task killing reduces their load on the system. your links are informative, but i'm not going to let my phone crawl next time it starts to because i shouldn't have to kill apps in a perfect scenario. i used to reboot my phone to reclaim performance, now i use a task killer. from your first link: "can be killed by the system in extreme low memory situations." "and it will often be killed by the system when memory is needed elsewhere." so task killers just accelerate the system's own ability to close applications that aren't being used anymore. also, only two apps that i have offer the ability to close themselves. if i know i am done with the app for the next few hours, my task killer gives me the ability to close the app.
slouch 15y ago
i'm reading the second link now, and it almost seems to contradict the first: "Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations."
- theBobMcCormick 15y ago
  The first link quotes the Android documentation. The second link is written by a core Android OS developer. They do not contradict.

slouch 15y ago

i'm not trying to defend a task killer so much as the act of terminating applications. i used to "force stop" apps from the applications menu before i got the killer. that said, low memory situations exist. task killing reduces their load on the system. your links are informative, but i'm not going to let my phone crawl next time it starts to because i shouldn't have to kill apps in a perfect scenario. i used to reboot my phone to reclaim performance, now i use a task killer. from your first link: "can be killed by the system in extreme low memory situations." "and it will often be killed by the system when memory is needed elsewhere." so task killers just accelerate the system's own ability to close applications that aren't being used anymore. also, only two apps that i have offer the ability to close themselves. if i know i am done with the app for the next few hours, my task killer gives me the ability to close the app.

slouch 15y ago

i'm reading the second link now, and it almost seems to contradict the first: "Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations."

theBobMcCormick 15y ago
The first link quotes the Android documentation. The second link is written by a core Android OS developer. They do not contradict.