Database Users

Taskiller...so what's the verdict?

I hear about people using different taskiller apps and now I have been reading that these apps are the cause of some problems and that the phone "knows" when to close apps if it needs the memory.
So what is the verdict??? Are Taskiller apps evil or necessary or do they have any value at all???

I use Taskiller. It's a great app but I have to admit, I wonder about its effectiveness. I tend to 'close all apps' if there are a lot running but I've found that this often causes more problems than it solves. As an example, I use the footprints widget on one of my screens. If I close the footprint app using Taskiller, sometimes it causes the whole touchflo process to terminate unexpectedly. I've also found problems closing processes with Taskiller which are related to the social networking/mapping features. If you know what processes to put in the 'ignore' list then fine, but closing some processes can hinder the phone's overall function.
Sometimes, however, if you want to close an app, there's no way other than to use a task killer. Take Peep for instance. No way to close it other than killing it. So yeh, task killers; generally unnecessary but sometimes handy.

Most applications do not properly handle shutting themselves down on Android. Android itself does not close many applications automatically, so a task manager is needed. How ever the automatic task managers have a tendency to kill system services as well and can cause a lot of problems on the phone.

s0v3r1gn said:
Android itself does not close many applications automatically, so a task manager is needed.
Click to expand...
Click to collapse
I guess that is ultimately the question....is it really needed???

I used taskiller in the beginning but after I stopped using it I think my phone is generally more responsive and better. Why? Because it doesn't have to start apps everytime I change screen or whatever. However I do have taskiller to kill apps that crashes or similar just in case. I do not use it frequently though. Instead I let the phone handle killing apps and whatnot.
So in my opinion taskiller is not needed because the phone takes care of everything that's needed mostly.

advanced task killer screwed up my text messages so i havent bothered with one since. luckily the device is just as as quick and responsive without it. so my vote is 'a' and 'c'

My favorite has been Advanced Task Killer Free. It doesnt cost anything and doesnt get rid of any vital processes that Android needs, especially if youre using SenseUI. Also, I have seen noticeable performance increases afterwards. So yes, I would say it is needed.

I've been using advanced task killer with problems. It seems to do what it suppose to but it also closes the radio for some reason. The rx signal comes back but the evdo doesn't unless I do a reset... I even payed for the advanced task killer thinking it would have more options but only has a hourly function.

Linux has it's own scheduler which handles tasks very efficiently.

no its not needed. i use to use advance task manager and it totally screwed and lagged my phone. not to mention i wasnt getting my sms because of those apps...i stopped using it and my phone functions great. if i feel that the phone is bunddled up with alot of apps i previously opened, i simply reset it (i hardly do resets because the phone functions excellently).
so no to task killers.

I had Taskiller installed, but after initially using it, I found that I wasn't bothered to use it, but it was still there with the icon at the top of the screen.
I read that they can actually slow your system down, so as I wasn't using it, I uninstalled it and maybe it isn't but the system does seem a little more responsive now
Vince

i used advanced taskiller and it kept my phone awake even when locked/lcd off. that murdered my battery. i uninstalled and use task manager now with no issues. it is not as simple as dragging down the notifications bar but my battery life is fine now.

I've definitely found that there is pretty much zero benefit to regularly using a task killer. Other peoples mileage will vary of course, and I'm sure there will be combinations of applications that don't sit too well together and cause issues, but I'm pretty confident than Android handles resource management well enough for most users.
I do wonder how may of those who swear by task killers are also using swapper, as I can well imagine that swapper will cause problems with Androids own resource management.
Regards,
Dave

HAHAHA guess you're not getting a clear cut verdict on task killers from this thread! seems like everyone has their own opinion....
There was an earlier debate on this topic. The thread is here... http://forum.xda-developers.com/showthread.php?t=569709&highlight=task+killer
and the android info is here (must read for understanding task killing) http://forum.xda-developers.com/showthread.php?t=569709&highlight=task+killer

They work well when set up properly. No reason to be closing widgets and programs on your sense ui that you use on a fairly often basis because it will take some time for them to load when you want to view them.
Leave the stuff you use regularly open and close the junk that takes up resources that you don't regularly use. Most of these programs have exception lists for a reason.
People that automatically end all and close sense, or their system dialer files will obviously run into problems and lag when all that stuff restarts at the same time.

Aridon said:
...Most of these programs have exception lists for a reason.
Click to expand...
Click to collapse
Exactly. They are fine if you exclude ALL the necessary components, then just have a few remaining on the main page that you know can be quit. Advanced Task Killer has been fine for me with their 'ignore list'.

i found that since ive stopped using task killer m battery life has improved quite alot
now i leave all the work to the android system

I have had the hero from day one and have had taskiller installed for about as long. I DID use it but do not now... and have no slow downs...
how?.......
custom rom....?
service which frees memory?
no...
Simply press back to exit a program and not home... if you press home the program most likley will not catch the button press and close. click back to exit and the program closes properly.
Press Back ....... this ISNT an iPhone with only 1 button.
nuff said...

I'm going without on this hard reset. On the last go around, even with disabling native sms app and using a 3rd party I was still getting the 100% awake time issue on the sprint hero.
FWIW, On a sprint hero make sure you ignore htiqagent, iqrd and omadm. Killing these will cause a radio reset, and ignore htcsense if you are using sense, which btw you can disable by removing its default setting in settings-apps-manage apps.

I think it is safe to say that I'm pretty ignorant about Android/Linux/etc. Nevertheless, I have Advanced Task Manager and I like to use it. I do use it judiciously, only ending certain programs/apps yet leaving most of that business to Android. And, of course, I use it to end the program itself.
El Mono

Back button does NOT end applications!!!

So, after installing Task Manager and opening it I had 31 applications running in the background! Yup, you read that right, 31!!! I ended them all and started playing around. I would launch and app, hit the back button and then go into Task Manager and there it was, still running. I launched several applications hitting back aftewards and they were all still running. I even tried hitting home aftwards and still running. Oh, and I had some apps running twice!!! WTF!?!? Looks like I found a major flaw in the new 2.1 OS.

This is normal android behaviour.
Apps are only shut down when the phone runs out of memory, however if the app is not doing anyting it will be paused and not use any battery / cpu.
And since the nexus has 512MB RAM it can have a LOT of open applications
If it is a background app (like im) it usually has an exit button in the menu.

Apps always run on android if you don't end them with a task manager.

Ya, normal behavior. The app actually has to intentionally end itself when you press the back button for that to really end it. I wouldn't worry about it, though. Apps in the background tend to use very little RAM and CPU.

Not sure why people are freaking out about apps running in the background... This is normal and Android does an amazing job of freeing up memory by killing apps as NEEDED.

Hmmmm, guess I never looked at it that way. I do notice it gets a little sluggish when all of that is running in the background. I'm just used to my MT3G. I've NEVER seen that many apps running at once.

setzer715 said:
Hmmmm, guess I never looked at it that way. I do notice it gets a little sluggish when all of that is running in the background. I'm just used to my MT3G. I've NEVER seen that many apps running at once.
Click to expand...
Click to collapse
try two and two-thirds the amount of RAM and that would explain how you get so many apps running lol.

david1171 said:
try two and two-thirds the amount of RAM and that would explain how you get so many apps running lol.
Click to expand...
Click to collapse
Ha-ha, good point!!!

From my experience the apps never close it is set to idle and is stored in the phone memory therefore decreasing startup time and allowing for a better multitasking experience but on all other previous android devices there wasn't as much memory so only a few apps could run at a time before the memory would be needed so something would get closed.

You're used to having 37.5% of the ram the Nexus One has
Now here's the question: does having 31 apps open affect battery life?

Paul22000 said:
You're used to having 37.5% of the ram the Nexus One has
Now here's the question: does having 31 apps open affect battery life?
Click to expand...
Click to collapse
It depends on the applications. If they just sit quietly when suspended (in the background) and don't do anything, they will have no impact on battery life (because their threads will never schedule/run). If they continue to do work while in the background, that will have some impact, however, unless they hold a wakelock (something they need the "keep phone from sleeping" permission to do), they will have no contribution to battery consumption while the screen is off and no other apps/services hold wakelocks.
In short, "it depends."
The menu / settings / about phone / battery use panel tries to give you as much information as possible about what apps/services are consuming your battery.

martijnve said:
This is normal android behaviour.
Apps are only shut down when the phone runs out of memory, however if the app is not doing anyting it will be paused and not use any battery / cpu.
And since the nexus has 512MB RAM it can have a LOT of open applications
If it is a background app (like im) it usually has an exit button in the menu.
Click to expand...
Click to collapse
Yes. Traditional multitasking (WinMo, BlackBerry) phone OSes will not close an application (or program, on WinMo) until you tell it to close, or it decides to close itself. This is a resource hog, and results in the freezing up or running painfully slowly that we have come to expect from those devices. The iPhone always runs fast because it ALWAYS closes an app--no multitasking whatsoever--so it never runs out of resources and slows down. It "pauses" the app, then closes it, so when you open it, it resumes right where it left off, as if it were open the whole time. The downside is nothing gets done in the background--which is why awesome apps like Locale or Screebl won't run on iPhone. Android is the best of both worlds. It leaves apps running until it NEEDS to close them. When resources run tight, it pauses apps just like the iPhone, so it stays running fast, but as long as you don't overload the system, you can run background apps. And background services will stay running.
Paul22000 said:
Now here's the question: does having 31 apps open affect battery life?
Click to expand...
Click to collapse
I'm sure it does some, but with that monster of a CPU, and as little power as apps use when they're sitting in the background not doing anything, I'm guessing it is a negligible difference. But that's why I love Advanced Task Manager's auto-end feature.

i lol'd -----------__________----------------

When you have 31 applications running, is there a hardware key that you can press (perhaps with a third party software) to show those which are running, and to switch to anyone of them instantly without resorting back to the application menu? Also, does this same tool let you shut down an active tasks in order to conserver memory and battery life? I understand that a long press of the home key only shows the last 6(?) application launched but not necessarily the currently active tasks.
On my jailbroken iPhone, I'm used to be able to double click the home button to show all active tasks, and there I can switch to or terminate anyone of them. While running an application, I also have the option of long pressing the home button to end it directly so that it does not continue running in the background. If I do a normal home press, the application will continue running in the background, and I'm presented with a screen which lets me jumps to any of the desktop in order to launch new applications.
I hope I can have the same level of convenience here.

All of the applications in the backround are essentially in hibernation - it is part of the way Android manages the RAM. I think it's great.

Task killers...Is it REALLY needed?

Hello guys;
just received my phone yesterday and i have a question regarding open programs
does the back button until home screen close the program or it still run in memory?
some people advise the use of task killers to kill unwanted tasks to save battery
while others say that Linux is handling this automatically and using task killers is no use
some people claims that after they stopped using task killers their battery life was better
i am new the Android as i am an ex WinMo user so please enlighten me
Thanks for huge efforts guys

Yes, they are. Android does a poor job of managing tasks, even to the point it auto starts like everything in your phone and very few of them turn themselves off.
You can manually manage them in applications, running processes, but task killers are so much easier.
I have owned 3, and the one that is easiest to use, that I have never found a bug with is Advanced Task killer (Little green droid icon). The purchased version is expensive, but worth it as it gives you one click widget to kill tasks.
Advanced Taskiller is known for crashing the home screen and stopping vital system services requiring a reboot. I own the full, and I have no use for it.

Okay, let's see how many questions I can answer here....
First of all, using the back button does not close the program. Neither does the home button. Android does handle this natively, but it does so automatically. It doesn't matter how you exit a program, it stays running until it needs to close. Whenever too many apps are running, slowing the system down, it will close the older ones as needed. All automatically. Nice, huh?
Task killers let you do this more aggressively, or manually. You may want to do this if you want your system to be "extra" fast, or to save battery. Most of them have extra features, too, like switching to running apps, or uninstalling them, etc. Beyond that, you don't need it. Some people say that task killers actually drain battery, but in my experience, they help slightly. And they do improve performance slightly too--as long as you are smart about not killing the wrong apps. (HINT--if it's a widget or a background service, never kill it)
So really, it's up to you. Get a free one, or a trial, and try it out, see if it makes things better or worse. Just take into account the learning curve before you give up on it--you have to exclude widgets, background processes, and maybe a couple other apps, too... takes a bit of trial and error to figure out which apps get bugs when you kill them.

It's not necessary but highly recommended. I use Taskiller the paid version. I mainly use it to kill apps that start to have problems and to kill a lot of the apps that boot with the phone.

on G1: i use it every time i reboot, because on boot/startup, some apps open automatically that are not needed (e.g. maps, Documents To Go, alarm, etc.)
clears up a lot of memory
on Nexus One: not sure yet whether that's really necessary considering more RAM available

I use Advanced Task Manager purely because I bought it on my G1 and so thought I might as well. It has a kill-all widget (you can set exclusions of course) but I don't use that. I normally only use it to kill apps that I want to restart or just to monitor what apps are doing what.
I have tried running the phone without using it at all and using its automation feature to kill everything except widgets and background processes every 30 mins. I honestly didn't notice any battery life difference or performance except that abviously apps were slower to open if they'd been killed rather than when they were in the background.
In my opinion and based on anecdotal experiments, task killers are not necessary on the N1 and certainly nothing like as vital as they were on G1

system6 said:
Yes, they are. Android does a poor job of managing tasks, even to the point it auto starts like everything in your phone and very few of them turn themselves off.
Click to expand...
Click to collapse
Bull****. Prove your statement. This isn't Windows we're talking about. Android manages tasks and memory very well, if only people let it... but for some reason people can't understand that Android WILL automatically free memory AS NEEDED. Instead they open a task killer and **GASP** see open programs!! Autostarting certain apps is actually a good thing, since often those are the apps that people tend to use often, so they load very quickly. There is always some free memory with Android, and it never lets it get to a point where that drops to 0.

uansari1 said:
Bull****. Prove your statement. This isn't Windows we're talking about. Android manages tasks and memory very well, if only people let it... but for some reason people can't understand that Android WILL automatically free memory AS NEEDED. Instead they open a task killer and **GASP** see open programs!! Autostarting certain apps is actually a good thing, since often those are the apps that people tend to use often, so they load very quickly. There is always some free memory with Android, and it never lets it get to a point where that drops to 0.
Click to expand...
Click to collapse
+1. I dont use any task killers and have had no problems with speed or battery life.

uansari1 said:
Bull****. Prove your statement. This isn't Windows we're talking about. Android manages tasks and memory very well, if only people let it... but for some reason people can't understand that Android WILL automatically free memory AS NEEDED. Instead they open a task killer and **GASP** see open programs!! Autostarting certain apps is actually a good thing, since often those are the apps that people tend to use often, so they load very quickly. There is always some free memory with Android, and it never lets it get to a point where that drops to 0.
Click to expand...
Click to collapse
This.
I thought a task killer was necessary and went out and spent the dollar something on Advanced Task Killer. It made me feel "good" to know what I control what apps are open. But you know what? Ever since a factory reset, I have not put the Task Killer back on my phone and it's been about a week and a half if not more of letting android control my memory... And like uansari said... Android does a very good job of it.
I have not had to close any apps because of short memory. Android does a great job. Save your money.

Android (and Windows for that matter) has great memory management, but it's mostly a problem of rogue apps that don't sleep properly. I have Advanced Task Manager, and I've noticed with the Nexus One I see more "applications" running (like Launcher) that didn't show up on my G1 (running Enom's 1.6 before I got my N1). I found that I had to block a bunch of apps to keep them from being closed, and I got a couple of weird bugs that seemed to stem from closing apps. One of them was this problem with the audio not be routed properly to my BT or wired headset when connected. I use the task manager much more sparingly now, and only kill apps when they act up.

I really wish we had "Cards" like the Pre, so we could always know exactly what was open. Plus, the ability to "alt-tab" (swipe back and forth) is a million times better than this "hold home button" crap. Sigh. Need better alt tabbing.

while i do not disagree that Android does a ok (yes, ok! just that...) job to manage tasks & processes, I disagree that it opens or keeps open apps that are necessary or frequently used. That's not Android that does it, it's the apps that tell it to do it.
for instance (as i mentioned a few posts up), everytime i boot, it opens "Documents To Go"... an app i most infrequently use, almost never, but like to have in case i have to review a doc or excel sheet on the go.
It doesn't have to open on startup, it is not frequently used, but it still opens on start up.
so yes, i do use task killer, on startup. but i use it sparingly thereafter

shmigao said:
while i do not disagree that Android does a ok (yes, ok! just that...) job to manage tasks & processes, I disagree that it opens or keeps open apps that are necessary or frequently used. That's not Android that does it, it's the apps that tell it to do it.
for instance (as i mentioned a few posts up), everytime i boot, it opens "Documents To Go"... an app i most infrequently use, almost never, but like to have in case i have to review a doc or excel sheet on the go.
It doesn't have to open on startup, it is not frequently used, but it still opens on start up.
so yes, i do use task killer, on startup. but i use it sparingly thereafter
Click to expand...
Click to collapse
That's fine... so Document to Go opens at boot, along with other apps. My point is that as you start opening other apps, and Documents to Go stays latent, it will get closed automatically as other apps demand memory. I'm not directing this specifically at you, shmigao... just responding to a concern a lot of people seem to have. Apps automatically opening at startup is common and don't cause a performance decrease.
I have yet to experience any slowdowns on my N1, and I never use the task killer that's built into Astro.

i use "automatic task killer" free from the market and my phone runs fine. I dont even have to think about it, because it clears memory when phone goes to sleep. I think it was more needed on htc magic than nexus.

uansari1 said:
Bull****. Prove your statement. This isn't Windows we're talking about. Android manages tasks and memory very well, if only people let it... but for some reason people can't understand that Android WILL automatically free memory AS NEEDED. Instead they open a task killer and **GASP** see open programs!! Autostarting certain apps is actually a good thing, since often those are the apps that people tend to use often, so they load very quickly. There is always some free memory with Android, and it never lets it get to a point where that drops to 0.
Click to expand...
Click to collapse
Exactly.
I stopped using task killers on my N1 because it cause more problems and hosed my battery faster. I haven't used it in almost two weeks, and the phone is smooth and the battery lasts a lot longer.
No need for task killers on the N1, IMO.

uansari1 said:
Bull****. Prove your statement. This isn't Windows we're talking about. Android manages tasks and memory very well, if only people let it... but for some reason people can't understand that Android WILL automatically free memory AS NEEDED. Instead they open a task killer and **GASP** see open programs!! Autostarting certain apps is actually a good thing, since often those are the apps that people tend to use often, so they load very quickly. There is always some free memory with Android, and it never lets it get to a point where that drops to 0.
Click to expand...
Click to collapse
HA! Tell me how you really feel....LOL. I have tested my wifes G1 and my old MyTouch and found it gave me about 30% more battery time.
Yes it will auto close programs when it needs the resources, just like a Palm pre, but running processes are just that.....RUNNING.

uansari1 said:
Bull****. Prove your statement. This isn't Windows we're talking about. Android manages tasks and memory very well, if only people let it... but for some reason people can't understand that Android WILL automatically free memory AS NEEDED. Instead they open a task killer and **GASP** see open programs!! Autostarting certain apps is actually a good thing, since often those are the apps that people tend to use often, so they load very quickly. There is always some free memory with Android, and it never lets it get to a point where that drops to 0.
Click to expand...
Click to collapse
I am perfectly happy with android managing my open applications and I have no concerns about RAM. My primary problem is that I am given *no* way to actually close an application if I really want to. An open application could still be polling, syncing, or updating and if I don't want that anymore how can I close it without the application developer explicitly coding an option for me to do so?
(an) Automatic task killer gives me the peace of mind that I can close applications that I use only once in a while and start with a clean slate every time I unlock the device.
I am not one of those users who places every single program there and requires a minimum amount of free ram, but I do have it cleaning up programs that have no business staying resident.

Wouldnt it by wise to use the "ignore" list many of these apps have.
That way you can have your frequenly used apps always able to quick load and the ones that you never use killed off.
I understand that Android has good memory management but I dont see the point of having some apps sitting there when I have no intention of opening them up on a regular basis.

Wow! Such heated debate over something so simple!
This isn't Android 1.0 or 1.5 or even 1.6(pretty darn good at auto closing)... this is Android 2.1 on 1ghz w/512mb RAM! The auto scaling of the CPU and the auto task closing is very, very, very good! There is no need for a task manager unless you want to use it to close something very specific because you want it closed NOW!
But there is no NEED for it, especially on the Nexus One. All it will do, if used regularly, is decrease battery life (yes, decrease, because it takes a lot more CPU power to open up an app than it takes to hold that program in the RAM's cache). As well, it will slow down your Android experience... Hero users found this one out, at least smart ones did, that the best way to keep it zipping along was to not use a task killer, except for media rich apps like youtube, music player, video player.
On a G1 running a Hero ROM, slightly different story in terms of speed, it was beneficial for several reasons; 1. Android 1.5 doesn't have nearly as good auto task management as 2.1. 2. A G1 used almost all of it's RAM to boot up the Hero ROM, and thus the auto settings were no where nearly as agressive as they would need to be.
But we are not talking about a G1 running a Hero ROM... we are talking about a Nexus One running stock Android 2.1...
If the OP, or anyone, wants a task killer, get Astro file manager, and use that. Kill the select few apps that you really want to when you get done, but don't bother getting an auto killer that messes with the already amazing job Android 2.1 and the Nexus One do!

it can be useful... i use it to close certain app that autostart or keep running in the background and use the GPS franticly trying to get a location

Why are so many programs starting on their own?

I downloaded Advanced Task Killer Free, and things like Sprint Navigation, Facebook, Voice Dialer, etc, the list gets 20 programs long after about 15 minutes... this makes no sense.
Can someone who has used Android longer please explain this to me? It seems that this OS needs much more babysitting than even WM, if it's really auto-starting all this crap for no reason.

It seems like all of the applications you described are system apps that were on the phone when you got them. They may be set to automatically run. I know you wont be able to remove any of them without the phone being rooted and having su access - but i may be wrong.
When you close them, it seems like the OS is just automatically reloading them.
Careful when you kill apps, it could cause some unwanted issues.

So many of these programs have nothing to do with day-to-day operation... this is bizarre.
Does Android supposedly have built-in memory-management? IE, you exit the camera app, it eventually FORCE closes it? So far, I haven't noticed that behavior at all. That's what caused so many issues on my old WM HTC devices.

Android does have built-in memory management. It is how the OS was developed.
If you have a program running on your screen, it will use whatever amount of memory it needs in order to run it.
If the program gets pushed into the background, but is still running, it will still use the memory, even though another program is being ran using up even more memory.
Having free memory will not make the phone run any faster. Eventually the program in the background will close if not used. It will also be force closed if the system is in dire need of memory.
Android knows when it is need of memory.

There are several threads already which explain memory use if you search. Since I'm using my phone I won't go into detail but I will say that task killers are not recommended. It's much better to let Android manage the memory and processes.
My personal experience bears this out as I had a lot of strange issues like losing wireless connectivity when I was using a task killer. Now I let Android handle things and my phone runs smooth. Using a Sprint Hero with Fresh 2.1.2 ROM.
-------------------------------------
Sent via the XDA Tapatalk App

Interesting... all my friends who use Android have task managers... Most engadget posts mention that too. Hrm... I guess I'll make sure auto-kill is disabled and just watch and see how the OS holds up.

I just got the phone this morning and was killing apps left and right. I started to get a lot of Force Close errors.
I rebooted the phone which would clear the memory anyways and I'm letting the OS handle everything now - Havent had any problems since.
good luck!

ScrapMaker said:
Interesting... all my friends who use Android have task managers... Most engadget posts mention that too. Hrm... I guess I'll make sure auto-kill is disabled and just watch and see how the OS holds up.
Click to expand...
Click to collapse
Honestly, if you are worried about a particular program running away and have reason to believe it, sure a task manager/task killer can be handy for that one program but historically, giving people task managers on Android causes more problems than it helps. Voice Dialer is your phone app for example and at the CDMA Hero forums, we've seen the phone do some crazy things when we removed it from the phone right after we got root (turns out that thing is hooked to more than just the "making phone calls" feature).
All that said, it's quite informative to google around about android's method of memory management. It's kinda cool!

I had a hero, and it least made it through the day. The Evo is way worse. I have no idea why some things run in the background that I've never used and have no reason to be running in the background. I'm using ATK and Auto Task Manager, which kills app once your phone goes to sleep. You just have to know what apps you shouldn't be killing. As a rule of thumb, I didn't kill any native google or HTC services. I did kill all Sprint services. Following this guide as well:http://www.mobilecrunch.com/2010/06...attery-life-and-what-this-says-about-android/

here is why you don't really need a task killer.
with that, i can say that i do have one but, i don't have any autokill going. i only use it as a last resort to kill things if i have like multiple things producing sound at once.

Honestly I can tell you from experience, that sprint bloat wear will launch on its own all day long. Even if you set ATK or AMM to nuke it, it eventually will cost more batt. in the long run because of the system resources required to launch and kill over and over again. The only way to successfully deal with the issue is to rm the crap, which requires root.

Why did Samsung put in a task manager and a "kill all tasks" button?

So Samsung for whatever reason, decides it's a good idea to include an easy to access task manager with a giant "kill all tasks" button in TouchWiz. It seems like everyone I know, that has a Galaxy S II, has adopted a certain behavior due this. What they do is, every time they put their phone away, they will automatically go to this task manager and kill all tasks, before locking the phone. When I ask them why the hell they're doing that, the answer is usually something like "wasting battery blah blah blah" or "wasting CPU blah blah blah"... NO!
For starters:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
http://www.infoworld.com/t/smartphones/myth-android-devices-need-task-killers-609
http://androinica.com/2010/05/googl...-imply-task-killermanager-apps-are-pointless/
People that are doing this, educate yourself. And Samsung, well done for encouraging this.
Just because a task is in memory, doesn't mean it's doing anything, and certainly doesn't mean it's using up battery. If it's staying in memory, it's because there's no need to release it just yet. If you start it up again, it will already be there, and load up faster. The alternative is, you keep killing it, and every time you run it again, it will have to reinitialize and reload everything. Which option do you think is actually going to cost more battery?
The whole thing with people saying "oh no it's using CPU, i must kill it"... what?! If it's using CPU, it's probably doing something. Why the hell are you killing a process while it's in the middle of doing something? Do you not care about data integrity at all? It could have been in the middle of syncing, or in the middle of a write operation who knows.
If you run other applications and your memory runs low, then Android will close it. And it will close it properly, as opposed to you force killing it, denying it of any chance to clean up.
Obviously there are rare exceptions with dodgy programs. But most of the time, the tasks being killed are system apps, or trustworthy apps, properly written by Google or Samsung.
If you're not a developer, you probably won't understand the whole Android application lifecycle.
http://developer.android.com/reference/android/app/Activity.html
By force closing an application, you're not allowing it to run its onStop() and onDestroy() functions. This is where apps do all the clean up, releasing resources, unregistering things, closing connections etc.
Do you do this on your PC. Open up Windows task manager, and just kill any task that's using CPU. Or hell, just kill all tasks every 2 minutes! Good luck with that.
This has probably been said hundreds of times, but a lot of people i know are getting GSII's and I see them doing this constantly. It's stupid. Do you really think they designed the operating system so that you have to kill everything each time you touch it?
TLDR: Stop "killing all tasks" (unless theres actually something wrong) and well done Samsung for encouraging this. Just stupid.

Damn your right, I never used a task killer on previous android phones, but for some reason I have got into the habit of doing it now. So I'm going to kill that habit. Well noticed

Well according to the user guide (the full one from Samsung's website)... though personally I don't bother killing anything
Use the task manager › ›​
Your device is a multitasking device. It can run more than one application at the same time. However, multitasking may cause hang-ups, freezing, memory problems, or additional power consumption. To avoid these problems, end unnecessary programs using the task manager.​
1 In Idle mode, open the application list and select Task manager → Active applications.
The list of all the applications currently running on your device appears.
2 To close an application, select Exit.​To close all active applications, select Exit all.

i like the placebo effect and stop telling me what i have to do or not to do!
your writing style is to aggressive, stop being aggressive!

For me, it is worth to have the clear memory option because I already faced the glitch or bugs program which cause my phone to run constantly at 1.2ghz and this will cause my phone become extremely hot. I can't see what application is running but for some reason, the cpu gone crazy. It drain battery in no time. With the simple one click button, I can closed the programs without need to restart the phone. Yes, generally I will let the android system to handle the application by itself but I still think it was a good moved by samsung to have task manager if we use it in proper way...
Sent from my GT-I9100 using XDA Premium App

Well it's not all that bad, with 2 cores one core can easily come into a deadlock and the device will continue to function albeit much slower and consuming a lot of power, when this happens in the taskmanager the processes are listed red

Thanks ever so for much for this post I have just got my first Android phone and thought by doing this it would increase the battery life a tad but did kinda think it was a bit daft having a system that required manually killing tasks. Coming from a Windows 6.1 XDA Zest I am still getting my head round an OS that's doesn't require hours on Internet to work out how to do things.

Sad, but true, I was getting onto Android from Symbian, and first thing after I realised that I do not have option of killing all apps, I have installed the task killer and kept using it for like a week, then I've read one of the articles about it, that its wrong, and that Android is not working as Symbian nor Windows, so I realised that I dont need to do that... unninstalled it and not using it at all since

You don't need Task manager / killer if only all android applications are developed by good programmers that implement Android application lifecycle properly.
The problem is not all applications are developed this way. Some application may buggy / in beta stage that still consuming processing time even they are in background.
Task manager is still useful to close nasty program manually. But I do agree, auto-kill is useless and can cause battery drain and system instability.

Yep .. it's mostly services what eats battery. And there is poor control over that. It would be interesting to see what service was active at what time, or even how much battery did it use. All battery discussions are about guessing what is running in the background and how often and how much. We should not guess such things.

As far as I'm concerned an in built task manager is just as important as an in built modem right now. There are far too many unstable applications out there that hang up and Android can never fully deal with them(despite what research may or may not have been done in the past).
I have a few games installed on my S2(namely Pool Break Pro & TNA iMPACT!) that crash quite often and require the use of the task manager to manually end those programs(they are in the task manager highlighted in red when they have stalled).
However, what I will say is that the button to clear memory in the RAM manager really shouldn't be there at all. The task manager alone is more than enough to manually exit necessary apps that crash and stay open for no reason.

I like to have the ability to close programs easily at hand. It gives me better control over "rogue" apps. I only use it for a few programs though, like the Engadget app. It seems to be poorly coded, often using 40-50% CPU when running in the background.
Sent from my GT-I9100 using XDA Premium App

I like it because it lets me close frozen apps quicker..

the_Calen said:
i like the placebo effect and stop telling me what i have to do or not to do!
your writing style is to aggressive, stop being aggressive!
Click to expand...
Click to collapse
Lol yes. Not to be taken too seriously.
Force closing apps with the task manager when somethings wrong with the phone or closing broken apps makes sense. I'm just talking about people that instinctively press the close all apps button every time they use the phone for a second. It's just silly. Basically doing what those automatic task killing apps do.

I use to kill opera everytime i'm done with browsing because even in idle mode the phone gets very hot when opera runs in the backgtound. But after these explanstions i stop force killing every app
Sent from my GT-I9100 using Tapatalk

If a program is badly written and won't stay idle, then kill it.
I am very selective about what I install, and never kill or need to kill anything.
You have 1 GB of ram on this phone. If you want best battery and speed, don't kill anything. loading a running app from ram uses less power than starting from scratch and booting it from nand, then starting it up.
So if apps are well written, don't kill them. If stuff stays around causing drain, kill it individually but find a better app

This thread is spot on... for the most part. Like Pulser said, there are apps when idling/cached, cause detrimental effects like the one I detailed here causing your phone to stay Awake constantly and draining battery:
http://forum.xda-developers.com/showthread.php?t=1094666
ATK isn't the most elegant method, but it allows you to put everything else on ignore and have it actively kill the apps that love to stay cached and cause issues even after you've exited out of them.

Is there a way to "lock" some apps into a memory so they never quit by the android OS except if I would decide to?
Sent from my GT-I9100 using Tapatalk

You have a valid point, but most of the time those apps don't do anything critical that it would hurt to interrupt. I usually prefer to exit them normally, but sometimes I just kill it, like when I forgot the Messages / Internet open. No need to paranoia though, leaving a few open won't kill your battery.

PINki92 said:
Is there a way to "lock" some apps into a memory so they never quit by the android OS except if I would decide to?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
That's exactly what I needed. There are some apps, like SetCPU, TB, Root Explorer, which can be added to SuperUser authorization and it won't get killed by anything unless someone manually kills it. I'd really really like to know how to add an app under SuperUser or anything which will do the job to add the app in to the OS and which can't be killed by any Task Killer or anything.
Besides I also hate those Task Killer apps, they are meaningless unless an user do nothing regularly with his/her phone.
I've no Task Killer installed but once I used the built in Memory Clear feature and next day my schedule app got closed. From then I never touched it. But one thing if RAM usage goes above 400 MB I think sometime its good to clear the memory as it will help to refresh it. But Samsung should had put the Memory Clear feature more precisely.
Regards.
Sent from GT-I9100