Task Killers... The Answer from Google & Developers.

[hemorrdroid]

I only kill ones that I start manually, not ones that auto start themselves. I use agressive, and have it kill when the screen shuts off, that way its not killing something i might want in the background.

[Abe21599]

I do NOT use a taskiller

http://www.droidforums.net/forum/dro...evelopers.html

[Talon8Ya]

I only kill ones that I start manually, not ones that auto start themselves. I use agressive, and have it kill when the screen shuts off, that way its not killing something i might want in the background.

Same here, I only kill apps like the browser and such that do not always shut off. I keep some of my widgets on my ignore list so I don't lose say weather updates and such.

I do not auto kill anything and rarely do I have to manually kill anything.

[aminaked]

There's no need to kill stuff sitting idly in memory. It isn't using CPU/battery. Android keeps stuff in memory so it's available quickly when you need it.

However, if the browser is set to a page that reloads or tracks you with GPS (the google home page) then it would be best to close out those pages...but there's no need to kill the process.

Treat the symptom: kill tasks
Treat the cause: close the browser window that's causing the issue

Treat the symptom: kill tasks
Treat the cause: uninstall problem apps and contact the dev

[JohnnyDepth]

Um, you do know that Autokiller isn't a task killer right?
However, I will read over the opening post, and maybe I missed the memo, lol!

To my understanding Autokiller adds advanced management the native Android OS
already handles. Using Autokiller has made my phone the most snappiest its ever been.

Launcher pro has never had a redraw, and in fact the only issue I have is
with Launcher Pro Plus itself, in that when it landscrape with the keyboard out (from typing a message)
then hitting the home button first the widgets take 2 seconds to switch, but I haven't had a redraw
in ages.

I'm well aware of what AutoKiller is. I found it to be ineffective. It suppose to assist in the handling of task managing thus saving battery. It didn't do any of that for me.

All I can do is share my experience.

I appreciate you sharing your experience.
It does assist the handling of task managing, which among other things
does save battery, but it's not like it was designed to give an extra 100 minutes of talk time. Battery usage depends on personal usage.

I can personally tell you that the native Android OS task management is
highly fallible, and is subject to doing things not conducive to performance.

Once I hit below 30MB (or lower) without using Autokiller my phone
begins to slow to a crawl. Many users also experience this. Since
that time (installing and tweaking AutoKiller) I've zero issues and my phone
flies 24/7 The second I touch the screen to move to a different home screen it is instantaneous. YMMV,

I also use SetCPU and have a plethora of profiles which also aid in extending battery life.

[JohnnyDepth]

When I was at my Verizon store, we complained about battery life. The person conducting a workshop asked if we had Task Manager installed. She enthusiastically proclaimed that she uses it a couple times a day to shut down apps and increase battery life. We downloaded it and have used it and I have to say I did notice an improvement in battery life. Now I read on this forum that what I am doing is not good!

Why did the so-called Verizon Droid expert recommend it if it's not a good idea? Should I leave it installed to kill unresponsive apps, even though I have not experienced an unresponsive app? Am I imagining the improved battery life? Is what I'm doing really going to damage the operating system or apps?

A Task manager in theory should be a good program (think windows)
unfortunately for task managers these are linux based OS's.

Android OS "knows" for the most part what to kill and just because a program "shows up" on the task manager list doesn't mean it is actually running. It keeps a prioritized list of what was already opened (say a browser) and will leave it open for a certain amount of time so in case you
wanted to go back to the browser the previous information will be there.

If after that point you don't go back to that app-Android OS will close it.


A task manager is not needed.
I will beg to differ though (that as you learn,
download MANY apps, and eventually "Root")
...that you use AutoKiller.

If you don't have many apps, nor ever think you will,
don't run live wallpaper, don't have many many contact, don't
have custom ringtones for each...you won't even need Autokiller.

Autokiller (for those of us who have many of those exclusionary
items I just listed) Autokiller is a vital necessity, it really is.

Remember when I said eariler how Android OS prioritizes apps
when they opened, and subsequently when "a certain amount of time"
lapses? Autokiller can fine tune the values associated with when
an app gets killed, according to how much memory your system needs
free memory and other features. It can also uninstall apps by long pressing on them.


I have never had my phone just scream and fly as it does now.
The best part is I have a 1.2Ghz kernel and at 800mhz...It flies
just the same.


I'd like to add that if you open up a slew of apps/programs/services and
you back out of them instead of closing them (if the option is there to exit) I
can assure you that depending on how much free RAM or memory you have at the time
of opening those many apps, you will have performance issues, redraws and a slowing system
until Android deems it necessary to kill of apps. -In our world that revolves around time I don't
want to wait...

Hitting the phone button, my dialpad comes up instantly, it doesn't think, and I have over 100 contacts (not counting FB)
In any app, I hit home and the launcher never redraws and the moment I touch the screen it's ready to go.

[Johnly]

I wish this thread was on every DF page, ha ha
Good information on the OS we use. Thanks.
Task killers are bad, but so are some devs.
People think because it is there, it is good.
NO, they are BAD. DO your research.

[JohnnyDepth]

I wish this thread was on every DF page, ha ha
Good information on the OS we use. Thanks.
Task killers are bad, but so are some devs.
People think because it is there, it is good.
NO, they are BAD. DO your research.

I agree with that!
If I was a developer and created a "task manager"
I'd want to make certain it was downloaded.

The masses out there don't know what these terms mean.
They just want the bigger GeeBee's and the Why-Fys!

This is why I think the Verizon associates prey on that
and even some, don't know what Linux is or why a task manager
wouldn't ever be needed.


I will concede, though that even as efficient as Android OS is...
There are times when an app (an unneeded one) refuses to die.

This is the app developer's written code, and not Android OS's issue.
This is where a one touch kill could be needed should you feel that extra
1, 3, 5 or 10MB would be better spent elsewhere.


You don't go off killing system apps like
acore
phone
anything with a cog in it!

Kill apps like Pandora (it has an exit button) though
Apps that don't piggy back off of the core system apps

You'll be fine, but the extra memory a task manager takes up is to
me a waste.

[droiddadi]

Just another question. From any app if I hit back button instead of hitting home will it kill apps?

I saw redraws sometime when I hit back button from browser pages to go back to home.

[PhoenixGTR]

I use System Panel for it's handy display of info and multi version archival. Only kill apps when they hang and don't display the wait /report /force close dialog.

Sent from my Droid using Tapatalk