this post was submitted on
1 point (53% like it)
8 up votes 7 down votes
all 11 comments

[–]toastercookie 16 points17 points ago

sorry, this has been archived and can no longer be voted on

How many times do I have to say this?

You. Don't. Need. A. Task. Killer. On. Android.

Just because the task killer shows the process as running does not mean it is taking up any processor or resources at all. The way you describe how it should work is actually how it does work on Android. Apps that need to run in the background (pandora, tethering, etc) will stay running when they aren't visible. These are called processes. If it's not doing something in the background, when you hit home or back out of the app, it's SUSPENDED, and using no resources. Killing it with a task killer is actually bad, because it suspends itself where you left off and if you kill it it won't be able to go back to the suspended state as easily.

Android is built to not need a task killer. If you need proof, I can get links.

[–]rahmad 1 point2 points ago

sorry, this has been archived and can no longer be voted on

ok... then why do task killers have a performance impact?

[–]daggity 0 points1 point ago

sorry, this has been archived and can no longer be voted on

The applications are stored within the ram. Freeing ram speeds the device up slightly, unless you're actively switching between the tasks at hand.

[–]lenolium 0 points1 point ago

sorry, this has been archived and can no longer be voted on

This is something we get from people coming over from windows mobile. Android's process management is actually quite interesting, when designing your app, you have to be prepared to get killed off at any time. Android just keeps chugging along until it runs out of memory and then kills the last thing that was around.

[–]fuckinhell 0 points1 point ago

sorry, this has been archived and can no longer be voted on

I don't like that method.

[–]burntbook 0 points1 point ago

sorry, this has been archived and can no longer be voted on

I somewhat agree but one of my issues is that the music player would continually restart when I plug in my head phones, start playing random music and cut half way into an hour long podcast. I finally found an auto killer that did so with relative ease but for the most part I agree with you.

It would be nice if there was a comprehensive user experience guide that was useful and helped an individual understand what he was supposed to do with the phone. Along with how to optimization without to much redundancy.

So for the most part I agree with you, but unfortunately all of the apps don't do what I want them to do and it is those variable experiences that make it necessary to have a killer. That said, yes, it is very annoying to have all my apps killed at the same time at first, but control is more important to my experience than what you are saying. I am not the average consumer though, because in going through the process to get here it took me several hours to solve a basic issue that was plaguing my otherwise very good experience with Android. Cheers.

[–]BadBoyNDSU 1 point2 points ago

sorry, this has been archived and can no longer be voted on

How about just having quit and min buttons on everything?

[–]kdesu 2 points3 points ago

sorry, this has been archived and can no longer be voted on

This is essentially what the N900 does, and it works beautifully.

[–]dirtysnachez 0 points1 point ago

sorry, this has been archived and can no longer be voted on

ProSwitcher is pretty much perfect in the way it handles iPhone multi-tasking. Wait for Apple to steal the idea and release it in a few years.

[–]hexley 1 point2 points ago

sorry, this has been archived and can no longer be voted on

Didn't they steal it off Palm in the first place?

[–]fuckinhell 0 points1 point ago

sorry, this has been archived and can no longer be voted on

and then patent it.