? for those who don't like task killers

[tjreishus]

I have read a lot about the plus and minus' on task killers all over this site. I havn't used one since I bought my droid in november. I have always suffered from my phone lagging throughout the day, not quite as snappy as when I first restart it, so I decided to check out what apps were active. PRETTY MUCH EVERYTHING! It shocked me. Just for the sake of trial and error I downloaded an auto task killer. I only selected programs that I never use, or only use once in a while. They are set to kill the app when it goes to sleep mode. The past two days the phone has been running faster and better than ever. Most of the apps are apps that I can't get rid of. Messaging, voice dialer, mp3 store, corporate calendar, etc. There are also other apps that I do use every once in a while so I don't want to delete them, but I certainly don't need them using up memory. Apps like shopsavvy, rom manager, radio time, movies. The apps I use every day, I do not kill! I know some people really don't like task killers, but I have to say that my phone runs better now. I now feel that there is a right and wrong way to use a tak killer. Not just a wrong way. I'd love to get some input from others though.

 

[Lock-N-Load]

I kinda think you answered your own question.

I use them, believe in them, never fear them.

 

[OMJ]

I dont use them cause I have no need. I have less than 30 apps on my phone and dont have lag issues at all.

 

[nstallion]

Most of the apps are apps that I can't get rid of. Messaging, voice dialer, mp3 store, corporate calendar, etc.

Actually you can remove these if you have root. Removing the .apk files from /app/ and the data directories from /data/ with Root explorer or terminal emulator should get rid of them.

I'm not sure if any other programs rely on things like Voice dialer though. I would research this before doing it as I don't know the whole process but I know it can be done. In fact most custom ROMs have scripts to remove them.

EDIT: The system apps are located in /system/app/ not /data/app/

 

[bcaroline]

I've been using one since I got my phone, so while I can't say I notice an improvement, I can say that my phone never lags.

 

[El Blacksheep]

Thing is, those apps that you're killing aren't consuming system resources. If anything, you're consuming more resources when your system realizes "Hey, that app I had open in the background is gone! Lets restart it!" and loads it back up.

The improvement you're noticing is likely a placebo effect.

 

[AndroidsOfTara]

FAQ: Why You Shouldn’t Be Using a Task Killer with Android Geek For Me – Android CDMA Sprint Hero

Task killers / managers whatever are great if you've got a misbehaving app and want an easy way to kill it. I use a paid one called Advanced Task Manger for this purpose.

Auto task killers are just bad news.

Verizon techs seem to all be trained to install a task killer no matter what the real problem is.

I also think a good number of people who are interested in task killers are coming from a Windows Mobile device where apparently the OS is too poorly designed to do its own memory management and must rely upon a human for this.

 

[rdsok]

It's pretty funny when any user tries to argue this point one way or the other. If someone is only arguing one side of the discussion, they are ignoring half of the facts in the subject.

The user's that claim that a program in memory isn't using system resources are wrong, no matter how they try to word it differently. If a program is in memory, then it is using system memory which is a resource plain and simple. Just because it may not be using any cpu resources doesn't mean it isn't using other resources. Any program that is using some resources will affect the overall system performance which can result in lags as the OP was talking about.

On the flip side of this argument, you also do not want to always kill all of the processes that are in memory or that also can affect the performance you see when opening an application that isn't currently already in memory.

In short, there is a right way and a wrong way to use a task manager. One issue already mentioned, a misbehaving app, is a good example of the proper use for a task manager. Another ( IMO ) reason would be to kill apps that are seldom used therefore a waste of resources that could be better used by an app that is used more often. A wrong way to use one is to have the task manager kill all apps that are running because that would indeed slow the performance you may see. Any app that is already in memory will open ( re-open ?? ) quicker which results in better performance if it doesn't have to load from the slower flash memory/disk.

 

[growler13]

Just curios to see what task manager programs people are using.

Also heres a quick read about how multitasking works:Giz Explains: How Multitasking Works on a Phone - iPhone - Gizmodo

I've only had my phone for 3 days but my findings are odd. The amount of memory available seems lower after I kill all my apps, and when I have a lot of stuff running it seems higher, but there's a noticeable lag. I'm using Advanced Task Killer by the way.

 

[Lock-N-Load]

Thing is, those apps that you're killing aren't consuming system resources. If anything, you're consuming more resources when your system realizes "Hey, that app I had open in the background is gone! Lets restart it!" and loads it back up.

The improvement you're noticing is likely a placebo effect.

I have never bought into this argument.

using your logic, it technically took "resources" to start them all up on the front side, what's it matter if you ask them to load up on the backside when they are NEEDED! either way, resources get used.

BUT, I also think the "resources used" to start up an app is so laughably negligible if there was some measurable amount when I finally wanted them to run when I asked them to run versus just starting up and running "hoping" they willl get used and hanging around on stand by - so to speak - in case you maybe, might, possibly want them.. they are ready

bah!

 

[takeshi]

I now feel that there is a right and wrong way to use a tak killer.

Of course there is -- that's true of anything.

The anti-task killer meme has been pushed so hard (too far, really IMO) because of OCD Android newbies coming from Blackberries and other devices where you have to constantly keep an eye on various resources. These same people have frequently been causing more problems for themselves.

using your logic, it technically took "resources" to start them all up on the front side, what's it matter if you ask them to load up on the backside when they are NEEDED! either way, resources get used.

BUT, I also think the "resources used" to start up an app is so laughably negligible if there was some measurable amount when I finally wanted them to run when I asked them to run versus just starting up and running "hoping" they willl get used and hanging around on stand by - so to speak - in case you maybe, might, possibly want them.. they are ready

Starting them up once uses negligible resources. Starting them up constantly (because you're auto killing everything) adds up.

 

[craighwk]

I don't care what anyone says, I'm anal about what is running in the background, both on my computer and phone. I use ATK and quite enjoy it. I have obvious things set to ignore, but apps that don't need to run all the time set to kill. I like things nice and tidy.

Haven't had any issues with it at all. In fact, I believe my phone runs better with it. And I think rdsok's post nails it right on the head.

 

[droidpcguru]

I have Taskiller and Autostarts. Taskiller has a "Mini Task Bar", where one touch kills anything not in the ignore list. Autostarts allows you to control which apps start when-VERY handy. With both of these working together, my Droid is MUCH faster, even at boot. I also have a LOT of apps, so having them not sit in memory makes a huge difference. ANY app that sitting in memory(running or not) is using resources. Most of the apps I am "killing" have no need to run unless I am using them. My most used apps are the ones on the ignore list. Also, the slight "lag" experienced by restarting an app that has been killed is FAR LESS than the constant lag caused by having a bunch of said apps sitting in memory all the time.

I've said before and will again.. good memory management or not, any computer will run better with more available system memory. Stick an extra RAM stick in your home PC and see what happens.. same thing. Considering the Droid is a computer for all intents and purposes, this definitely applies here.

 

[droidftw]

When i got my droid the tech installed atk right away

 

[nstallion]

When i got my droid the tech installed atk right away

You have more faith in the knowledge of the average Verizon store employee than I do.

 

[droidftw]

im only 13 and thought it was a verizon app lol

 

[messenger13]

The improvement you're noticing is likely a placebo effect.

No placebo here ... In fact, I can't disagree with this statement strongly enough. When I notice my DROID getting a bit sluggish, I kill the apps and Advanced Take Killer kills itself. At that point, all the sluggishness is GONE.

Or ... we can let the numbers blur the argument. When I first open ATK, more often then not, my DROID has less than 50M of free memory. After I kill the apps and ATK is killed, I reopen it and I have almost double the memory available. I frankly don't understand how anyone can argue with freeing up available memory. More is better. Simple.

Lastly, I would like to point out that 2.1 (ESE81) is much improved in the area of managing apps. My list in ATK is soooooo much shorter now ever since the update.

Having said all of that ... if you don't want to use a task killer, don't. If you do ... feel free as well. And do so without feeling stupid.