Database Info

Best Android Task Manager - Open Processes

Hello All,
I wanted to see what everyone thinks is the best application manger for Android.
Also is anyone familiar with the Getjar free app store?
Thx All,
Force

What do people think of "Advance Task Killer"
It seems to me it shows all tasks, not jsut the open ones.
Regards,
Force

FYI,
Many people say talk killers are not necessary, as that is a windows phenomenon, Linux & android treating background processes differently.
Regards,
Force

I personally use Advanced Task Manager for $0.99. I have read the articles about how Android does not need task Managers because it is built in, but I know from personal experience that without it if there are running programs in the background my phone gets really sluggish especially when I get a phone call and it makes it difficult to answer etc. Take in account, this experience was mainly with the Hero (slower) but I use on my Evo now.

You know people will argue either way, because there is evidence to support both sides of the argument. so with that in mind- i honestly havent had the need for one with my evo, but it you truly are considering one- i actually have a pair to suggest.
one is OS Monitor- free on the market- great app for pinning down process that could be an issue- also supports dmsg repporting- and logcat is built in to- so if your testing something and it goes all wonky you can export the log to view on a pc and send it to the developer too.
the second is AMM- or Auto Memory Manager- free and donate versions on the market. There are pretty much a couple of sliders and you set it how you want android to handle the process. I have had great success with this app on my other device- normal free memory was around 30-35 and using this set aggressively i saw gains of 50mb at most times keeping my freememory to around 75-80mb range.
Hope this helps.

I take both sides. I have task manager installed, but use if ONLY when needed. Aka, I used it when I want to kill the browser after I'm done with it so next time I launch it I won't be seeing old pages.

I like EStrongs Task Manager.

http://www.appbrain.com/app/nextapp.systempanel.r1 is nice, it can kill processes, monitor system stats, uninstall apps and more. There is also a free version.

TREYisRAD said:
http://www.appbrain.com/app/nextapp.systempanel.r1 is nice, it can kill processes, monitor system stats, uninstall apps and more. There is also a free version.
Click to expand...
Click to collapse
i installed that last night, cool app

why someone who know don't explaine exactly how android works and do we need killers and if yes which one is best...
Everyone of us using something but question is that which one is best for our needs.

quick system info pro (free)
I only use the manual task killer widget when memory gets down around 100. Spikes it right back to about 250.
Whats your guys' normal memory range? I see someone on here saying 50 was normal for them but that seems REALLY low to me.

frifox said:
I take both sides. I have task manager installed, but use if ONLY when needed. Aka, I used it when I want to kill the browser after I'm done with it so next time I launch it I won't be seeing old pages.
Click to expand...
Click to collapse
Does the stock Sense browser not have an option to kill the windows by hitting menu? On CM, I do menu, windows, and X them out

[Q] how do you close apps?

so i found out how to force close apps under settings but theres gotta be a better way.
for example lets say i have browser, market, and facebook apps open. all showing under the window selection button. after time i get a ton of windows there and i don't want all of them open. how do i close them selectively without going through all the settings menu crud?
some apps let me close from within, most don't though and leave me stuck with a ton of windows (apps) open.

What you are asking isn't necessary unless an application has malfunctioned. There is no other way to close applications other than using the force close button in settings. Android handles this itself -- if this doesn't satisfy you download a task manager.

I don't think there is a way yet.
What Google needs to do is make those preview windows in the multitasking bar long-pressable for a menu to be able to close them.

modru2004 said:
so i found out how to force close apps under settings but theres gotta be a better way.
for example lets say i have browser, market, and facebook apps open. all showing under the window selection button. after time i get a ton of windows there and i don't want all of them open. how do i close them selectively without going through all the settings menu crud?
some apps let me close from within, most don't though and leave me stuck with a ton of windows (apps) open.
Click to expand...
Click to collapse
There is no need to manually close out apps. Since 2.1, Android has done an excellent job managing memory. It's been written many times (some directly from Google) that micromanaging your apps will actually hurt battery performance. You'll essentially be working against the system as opposed to helping it.

I am not sure if my task manager is working on this device. I use AutoKiller and when I killed task it doesn't appear as though anything closes. Can somebody confirm?

atoy74 said:
There is no need to manually close out apps. Since 2.1, Android has done an excellent job managing memory. It's been written many times (some directly from Google) that micromanaging your apps will actually hurt battery performance. You'll essentially be working against the system as opposed to helping it.
Click to expand...
Click to collapse
id like to point out thats NOT the issue.
the issue is the ton of windows you end up having to sort through unless you close them. its a quality of life thing, i don't like having unused unnecessary windows open that i have to sort through to get to the stuff i am using. its just bad form.

foldog22 said:
I am not sure if my task manager is working on this device. I use AutoKiller and when I killed task it doesn't appear as though anything closes. Can somebody confirm?
Click to expand...
Click to collapse
It will most likely not work until its rewritten. The way 2.2 and now 3.0 allow access is completely different then 2.1 and below. Plus as said about 200 million task there is 0 reason to run a task killer. If you wanna clear them out, even though there is 0 reason, reboot.

Okay, I get the memory management issue, but as the OP pointed out, I've got all sorts of icons in the "task bar area" (bottom right hand corner) that just sit there or keep coming back.
For example, I haven't listened to any music on my Xoom since yesterday morning, yet I've got an icon down there for Music and Rhapsody. Also, there's no way to clear some notifications.
There's got to be a way to at least clear out the notification isn't there?

you tap on the little icon music for example and you will see a little x on the right of it, click that and it closes it from the notification system

There is absolutely no reason to use a task killer or manually kill tasks. 2.2, 2.3, 3.0, etc. handle memory and tasks extremely well. In many cases, task killers will only cost you more battery and more slowdowns than letting tasks just run out and sit in memory. Unless you're seeing rogue or malfunctioning tasks in the background causing slowdowns, there is no need to kill them.
I do wish you could scroll through the recent running apps rather than only being able to access the latest 5, but spam closing background apps doesnt help at all.

arrtoodeetoo said:
I don't think there is a way yet.
What Google needs to do is make those preview windows in the multitasking bar long-pressable for a menu to be able to close them.
Click to expand...
Click to collapse
While I haven't used a task manager since I started learning how android actually works last year when starting to make apps, I can't help but want the same thing in honeycomb for malfunctioning apps. I think google left it out intentionally to discourage task-killing rampages by oblivious users.

Every time I read "you do not need to close apps" I want to scream. first hour of usage I had a second browser installed and it and the stock browser were conflicting with each other... all I wanted to do was a quick close of one of the browsers.
There are always a multitude of good reasons to want to close a background app. I completely understand the technical reasons why an app does not need to be closed, but from a user experience point of view, it should be made simple.

mjpacheco said:
Every time I read "you do not need to close apps" I want to scream. first hour of usage I had a second browser installed and it and the stock browser were conflicting with each other... all I wanted to do was a quick close of one of the browsers.
There are always a multitude of good reasons to want to close a background app. I completely understand the technical reasons why an app does not need to be closed, but from a user experience point of view, it should be made simple.
Click to expand...
Click to collapse
Which is exactly why in my first post I said "...isn't necessary unless an application has malfunctioned" otherwise such a thing is barely necessary. And in your case, the classic "Settings > ....... > Force Close" would have easily sufficed.

So what you are saying is that a method to kill tasks is necessary, just not often. I, for instance, just had the xda app stuck on the splash screen. I killed it and restarted the app and all was good. There is a potential for harm if used over zealously but at times it would be nice if there was a more convenient way to close an app when necessary.
Applications do not always behave as they should so to say there is no need to kill am app is making a naive assumption that every android app is perfect.
Sent from my Xoom using XDA App

martonikaj said:
I do wish you could scroll through the recent running apps rather than only being able to access the latest 5, but spam closing background apps doesnt help at all.
Click to expand...
Click to collapse
Oddly enough, if you turn to portrait, you get a few more. So, technically its not a hard limit on 5, but rather (literally) limited by space on the screen.
Anyone want to place a bet as to what rev we see scrollability?
Sent from my Evo using the XDA App

JanetPanic said:
So what you are saying is that a method to kill tasks is necessary, just not often. I, for instance, just had the xda app stuck on the splash screen. I killed it and restarted the app and all was good. There is a potential for harm if used over zealously but at times it would be nice if there was a more convenient way to close an app when necessary.
Applications do not always behave as they should so to say there is no need to kill am app is making a naive assumption that every android app is perfect.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
If this happens use the built in task killer, settings/applications/running tab.
Sent from my PC36100 using Tapatalk

bwcorvus said:
If this happens use the built in task killer, settings/applications/running tab.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I did and it worked. As I said it would be nice to have a more convenient way of force stopping apps that are not behaving.
Sent from my Xoom using XDA App

Closing apps isn't necessary for two reasons.
1. Android does a good job at managing apps on its own.
2. You have 1GB of RAM to work with.
Sent from my HTC Vision using Tapatalk

Watchdog does a considerable job since it only lets you know when an app is misbehaving. And since being on 2.3 its barely given me any alerts. Perhaps further proving the awesome memory management.
Sent from my Xperia X10 using XDA App

delete please

Task killer

Does transformer need to install any task killer? My transformer runs a little bit laggy after openingtoo many apps behind.

You may get a bunch of different answers/opinions on this. The short answer is no. Android handles memory as it needs it by closing apps as needed. There have been a lot of post on task killers and how they can interfere with the way Android should run. There are also people that use them and have good results. I don't use one and have a few android devices and they all work fine regarding memory.

I use Advanced Task Killer (ATK) myself and only the widget. That one stops all the current apps. I seldom use this function as Android seems to be pretty capable of handling the memory by itself. Only in rare occasions the TF slows down or lags a little, I use it.

Probably you want to try active apps. I dont know if it's working with honey comb but it does quite well identifying what applications are running and cpu usage. Probably it will help.
Sent from my GT-P1000 using Tapatalk

How about minfreemanager? I kind of like that, it seems to be a good compromise between ATK and letting android handle the memory.
Of course, this also depends on the user, always press back instead of homescreen to close the app.

I've not needed a task killer at all yet. Once everyother day I restart it just to be safe, but I have been attributing it to honeycomb "beta" problems and/or the fact that it's not complete yet.
Sent from my Transformer TF101 using XDA Premium App

ELTinos said:
I use Advanced Task Killer (ATK) myself and only the widget. That one stops all the current apps. I seldom use this function as Android seems to be pretty capable of handling the memory by itself. Only in rare occasions the TF slows down or lags a little, I use it.
Click to expand...
Click to collapse
I am also using ATF and wondering why some programs will not kill off even tho i select it to kill. Like logmein, i select it and kill it, a minute later it shows up again ??? Does AFk even work? I noticed that after killing off some apps i see it frees up more memory, but couple of minutes later the same apps will start again....

dazz87 said:
I am also using ATF and wondering why some programs will not kill off even tho i select it to kill. Like logmein, i select it and kill it, a minute later it shows up again ??? Does AFk even work? I noticed that after killing off some apps i see it frees up more memory, but couple of minutes later the same apps will start again....
Click to expand...
Click to collapse
it's because since Froyo, the most a task killer can do is to restart the app / release it from memory. What it means is .. if your program runs a service/ Thread, the program will not be killed but merely restarting the app. That's y some apps that get restarted will show up again. The only way to kill is either you get a super user to do the kill from command shell 'kill -9 PID' or
go to the settings -> Applications and click on stop.
Hope this helps.
Also using task killer is not a good idea. It might drain battery if you use it regularly. if you asked me why? because when you restart the app/ kill the app, the program will load (this actually consuming CPU hence battery) again.
And if you asked again why did google keep those in memory?
it's because it's designed so that when you want to open up again it's faster..
Here is a link that might be helpful.
http://androinica.com/2010/05/googl...-imply-task-killermanager-apps-are-pointless/

I use atk, but like others I only use the widget. It's mostly a compulsive thing; I like to hit it twice and see my available memory shoot up 200 megs. I'm sure HC can handle it but I could swear it reduces lag in some instances; as if some apps or HC interfaces are scaleable to remaining available memory. Probably my imagination, but it hasn't hurt me yet.
Sent from my Transformer TF101 using Tapatalk

Any way to limit 'recent apps' in list? Noobish Honeycomb question.

I guess this is my honeycomb ignorance (still getting used to the features) but when pulling up recent apps with the softkey I really only want apps that are currently running.
Are some of these apps are already "closed" and by choosing a thumbnail from the list I'm re-opening these?
Is there a setting anywhere to "limit" the history I see? Like <5 apps or something?
I have Task Killer pro intalled now to manage the real running apps but the Softkey is handier, if I can just be sure of what its supposed to indicate.
Thanks
Sent from my Transformer TF101 using XDA Premium App

I was wondering this as well. I haven't found any way to do it yet.

I don't know of any way except to manage apps in the settings and then kill "running" apps....but remember; these are apps "in memory" like you'd think in Windows.....they are not sucking resources...
I think that there is an article here somewhere about this list and why you shouldn't use an app killer in Honeycomb....

I'm more interested in changing it to a grid layout, like a speed dial.

yeah I know theyre not in memory but they are wasting screen space. I finished playing chess yesterday, I dont think the game should stay in the recent apps list. Froyo & Gingerbread are much better at managing this.

moo99 said:
yeah I know theyre not in memory but they are wasting screen space. I finished playing chess yesterday, I dont think the game should stay in the recent apps list. Froyo & Gingerbread are much better at managing this.
Click to expand...
Click to collapse
I agree. I just want a cleaner recent apps list. Sometimes it's hard to find what you're looking for.

I guess a workaround would be to longpress the home screen, put a widget there that is linked directly to "manage applications" and then it would only be one press and then zap the offending apps.

You do realize the Recent Apps button on the homescreen is just that, a Recent Apps button. It's not exactly a "running in the background" button.
"I finished playing chess yesterday, I dont think the game should stay in the recent apps list."
Why not? It is a recently played app isn't it? LOL.
And yeah, agree with the other reply, if you want a list of running apps.... don't touch the Recent Apps list button lol.
Stop worrying about what's running in the background. Just enjoy the damn Android.

Im not near my TF now but I use Multitasking Pro on my Galaxy S for that. you can choose to open it by double clicking the home button and see only running apps or recent apps - its configurable in the application settings. i does cost about 2$ i think but it was the best 2$ I've spent

this is called a 'Recent apps' list for a reason...it's 'Recent'..not current running...

Well you could always downgrade to 3.0 if it really bothers you. That only showed 5 apps!

LOL. Its a nuisance, not so much a grievance; but I'm glad I'm not the only one annoyed, perhaps this will get looked at ;-)
Possibly once Honeycomb is more prevalent there will come market apps or enough reportage to have an updte with a setting for it, or a utility that tweaks it. Regardless, I appreciate the feedback. At least now I know its sort of "normal".
Sent from my Transformer TF101 using XDA Premium App

My number one wish is for Google to improve multitasking (and give back control to the user as to which programs are running).
As is, the implementation just isn't very usable if you consider it to be a multitasking device -- it's really closer to single-tasking with a memory of what it did recently and the ability to reopen with a similar state to what it last had.
For example, I use my tab during F1 races for timing and scoring. I have F1.com's timing and scoring app, and I have access to a (non-public) website which provides further real-time info through Adobe Flash in a web browser.
If I switch from the web browser to F1.com's timing and scoring app for more than say 10-15 seconds, then back again, the flash app has to reconnect to the server because the web browser ceased running, even though the browser and the F1.com app were the only programs running and had ample memory / CPU power / a mains power supply connected, ie. no reason to halt the browser.
This isn't the only time I hit this issue, it's just one easy-to-explain example.
I'd much rather I had the ability to exit programs / apps myself when I'm done with them, and to keep programs / apps running in the background when I want them to. It'd make the whole experience much more coherent and logical.

The Flash plugin was designed to suspend when you switched apps. It's not an android issue.
Adding "close programs" to the current implementation would not make it more logical, it would make it more convoluted. It doesn't need it.

knoxploration said:
.I'd much rather I had the ability to exit programs / apps myself when I'm done with them, and to keep programs / apps running in the background when I want them to. It'd make the whole experience much more coherent and logical.
Click to expand...
Click to collapse
The problem is that the vast majority of users won't want to handle this themselves, and would expect the OS to do if for them.
Personally, I'm in favour of having some sort of mechanism whereby you can tell the OS not to kill specific tasks if you so choose, but otherwise task management performs as is.
With specific regard to your example, I think that the OS believes it is always OK to kill the browser, which is why it can be killed so quickly after switching away. For other apps, this doesn't seem to happen - for example, yesterday I was connected to a remote server using Wyse PocketCloud, and I frequently switched away to do something else for 30-60 minutes at a time, yet my remote desktop connection was never dropped or killed.
Regards,
Dave

Me personally don't need and don't like this "recent" app button. Or I need it to have an option either to clear it or not. You know we sometimes need privacy over such things

JCopernicus said:
The Flash plugin was designed to suspend when you switched apps. It's not an android issue.
Adding "close programs" to the current implementation would not make it more logical, it would make it more convoluted. It doesn't need it.
Click to expand...
Click to collapse
Agreed, if flash is left to run in the background it will drain the battery like hell..and other system resources as well.
Sent from my Transformer TF101 using XDA Premium App

...and it should be *my* choice whether that happens. That is where this argument totaly falls on its face. *I* know whether it is vital to me that an app remain open, or can safely be closed. The tablet doesn't.
As long as it remains in the tablet's hands, it will continue to annoy me by leving open apps that I no longer need running, while closing apps that I strongly do need running.

magicpork said:
Agreed, if flash is left to run in the background it will drain the battery like hell..and other system resources as well.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
that's just it....it doesn't.
Revisiting Android Task Killers and Why You Still Don’t Need One
from another forum.
We almost hate to approach the topic of Task Killers on Android after all this time, but with so many new faces here at Droid Life and in Android in general, it’s something that needs to be done. In fact, after seeing the Amazon app of the day and reading through the Twitter conversations we just had with many of you, this thing needs to be posted immediately.
Let’s see if we can’t get you all some better battery life!
First off, please ignore the image up at the top of the post. If this was 2009 and we were all running something less than Android 2.2, that statement plastered on that red banner might be somewhat correct. But since it is 2011 and the majority of people on the planet are running Android 2.2, we need to get you away from the mindset that killing off tasks on your phone is a good thing.
So rather than me blabbering about the inner-workings of Android and how it manages RAM for the 10,000th time, I’m going to just pull from some posts that friends of ours have done that explain this in the plainest of ways.
First up is our boy @cvpcs who you may know from CM and his Sapphire ROM days. He knows Android inside-and-out, so when he goes into memory management which is done by the OS itself, you should listen up:
…What people don’t seem to realize is that android is designed to have a large number of tasks stored in memory at all times. Why? Well basically we are talking about a mobile device. On a mobile device things tend to be slower. The hardware isn’t as robust as say a desktop or a laptop, so in order to get that same “snappy” feeling, there have to be workarounds.
One of these is how android deals with memory. Android will load up your apps and then keep them running until they absolutely HAVE to kill them. This is because that way, if you want to re-open an app, the system already has it loaded and can then just resume it instead of reloading it. This provides a significant performance increase.
What a lot of people don’t realize as well is that android kernels have their own task manager. This means that:
it will be more efficient than any app-based task manager as it is run at the kernel level, and
it should be left up to that task killer to decide when to free up memory
There is only one case where having a task killer is a good idea, and that is when you want to kill ONE SPECIFIC APP. Killing all apps is never a good idea. You don’t know what operations they are performing or if they are necessary.
Whitson Gordon of Lifehacker suggests that you should be more worried about CPU usage than what’s going on with your RAM. We agree:
This set-up implies that the goal of killing these apps is to free up memory. Nowhere on the list does it mention the number of CPU cycles each app is consuming, only the memory you’ll free by killing it. As we’ve learned, full memory is not a bad thing—we want to watch out for the CPU, the resource that actually slows down your phone and drains your battery life.
Thus, killing all but the essential apps (or telling Android to kill apps more aggressively with the “autokill” feature) is generally unnecessary. Furthermore, it’s actually possible that this will worsen your phone’s performance and battery life. Whether you’re manually killing apps all the time or telling the task killer to aggressively remove apps from your memory, you’re actually using CPU cycles when you otherwise wouldn’t—killing apps that aren’t doing anything in the first place.
In fact, some of the processes related to those apps will actually start right back up, further draining your CPU. If they don’t, killing those processes can cause other sorts of problems—alarms don’t go off, you don’t receive text messages, or other related apps may force close without warning. All in all, you’re usually better off letting your phone work as intended—especially if you’re more of a casual user. In these instances, a task killer causes more problems than it solves.
More on how Android has a built-in memory-management system, but also on how killing all tasks is not a good thing (via: NextApp):
Android was designed from the ground up as an operating system (OS) for mobile devices. Its built-in application and memory-management systems were engineered with battery life as one of the most critical concerns.
The Android OS does not work like a desktop operating system. On a desktop OS, like Windows, Mac OS X, or Ubuntu Linux, the user is responsible for closing programs in order to keep a reasonable amount of memory available. On Android, this is not the case. The OS itself automatically removes programs from memory as memory is needed. The OS may also preload applications into memory which it thinks might soon be needed.
Having lots of available empty memory is not a good thing. It takes the same amount of power to hold “nothing” in memory as it does to hold actual data. So, like every other operating system in use today, Android does its best to keep as much important/likely-to-be-used information in memory as possible.
As such, using the task manager feature of SystemPanel to constantly clear memory by killing all apps is strongly NOT RECOMMENDED. This also applies to any other task killer / management program. Generally speaking, you should only “End” applications if you see one which is not working correctly. The “End All” feature can be used if your phone/device is performing poorly and you are uncertain of the cause.
And we could go on for hours with source after source on why task killers do nothing but work against Android, but you probably get the point now don’t you? Ready for a quick recap? OK.
Basically, Android keeps tasks handy because it thinks you’ll want to perform them again in a very short amount of time. If you don’t, it will clear them out for you. It also likes to keep as many things handy as possible so that the overall performance of your device is top notch. If Android were to completely kill off everything that your phone is doing, then it would require more resources to restart all of them and you would likely run into slowness and battery drains. By keeping certain things available to you, your phone is actually running better than it would without. So please, stop killing off tasks and let Android do the work for you.
Your goal for the week is wash your brain of the idea that having little RAM available is a bad thing. The more RAM available, the more Android will find ways to use it up which means your battery will be dead in hours. Instead, let it manage itself, so that you can spend more time playing Angry Birds or reading Droid Life.
All good now?

A simple reboot clears the list of recent apps. And as others have stated, it's not about running apps but something like the "recent documents" list in Windows 7

Task killer vs no task killer?

I use a task killer so im curious why some people say not to use them. What are your opinions?
Sent from my Inspire 4G using xda premium

I personally use them and havent come across suggestions not to, as long as u know what you are "killing" and its not a system process , it should be ok and yes it does free up RAM

I dont use any task killer and Im happy

I personaly would have a task killer one that kills all when idle. and frees up ram due to the fact i like to do cpu hungry tasks often

Ystrem said:
I dont use any task killer and Im happy
Click to expand...
Click to collapse
Same here, kill the task, and then feed the task killer the battery power saved.
I have tried them and found most of them didn't help much.

cnavi said:
Same here, kill the task, and then feed the task killer the battery power saved.
I have tried them and found most of them didn't help much.
Click to expand...
Click to collapse
Same here.
I don't use any of them.I used before but i don't saw too much help.Just task killer use cpu more and load ram.I use now just a shortcut of standard runing services default from android.

Don't use task Killers. Android has its own built in task manager Which works far better than 3rd party task killers. All you doing is making android reload everything again. Then you wonder why this app doesn't update in the background or work properly it is your fault. Your killing off the processes. Ram is essentially useless in android if it's not being used.
If you have lets say most phones have 512-1gig of ram. Your phone will never say you have 512 ram full please free up ram. It gets to a certain memory limit like depending on what it was set to and then end the processes automatically by itself. If there are many processes running android will start swapping out processes to replace for the new one. When your playing a game and say oh i want to browse the web to check on some game codes or whatever you can go right back to the game.
What if you want to listen to your own music as well. You can then go right back to the game in the exact spot left off. But if you go I'm kill the game process off you won't be able to do that. Don't press that Clear ram in that task manager you have either. All process will be killed including google services. Which will be reloaded again as well as system processes. Everytime android needs to reload its using more power meaning worst battery life.
The only time you should use a task manager is when there is a rogue application or a memory leak.

Watchdog
I don't use a Task Killer, but I do like Watchdog. It's more of a system monitor and lets me know if any background apps jump over a particular CPU usage threshold.
---------- Post added at 02:02 PM ---------- Previous post was at 01:55 PM ----------
There is a free, Lite version if you want to give it a try. Amazon had the pay version as their free app o' the day a while back, and I jumped on it.
market.android.com/details?id=com.zomut.watchdoglite&hl=en

I use to use taskkiller but my phone seems to run the same with or without, so I got rid of it.

exileinoblivion7 said:
I use a task killer so im curious why some people say not to use them. What are your opinions?
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
i dont like task killers, if your really desperate for ram and use android, i recommend using the v6 supercharger script made by zeppelinrox. ofcourse the thread can be found here in xda. Iwouldnt recommend task killers for several reasons:
1 they take some ram space themselves
2 they use some cpu thus making ur phone slower
3 they use some cpu thus draining your battery faster
4 they make your boot time on your phone longer because they are being loaded whereas scripts dont have that issue
5 i havent actually seen any propper task manager that has like autokill option and woks properly so you constantly have to press the end tasks button (like on system panel for example) and thats quite boring if your doing it all the time... scripts dont have that issue

Killbynature said:
Don't use task Killers. Android has its own built in task manager Which works far better than 3rd party task killers. All you doing is making android reload everything again. Then you wonder why this app doesn't update in the background or work properly it is your fault. Your killing off the processes. Ram is essentially useless in android if it's not being used.
If you have lets say most phones have 512-1gig of ram. Your phone will never say you have 512 ram full please free up ram. It gets to a certain memory limit like depending on what it was set to and then end the processes automatically by itself. If there are many processes running android will start swapping out processes to replace for the new one. When your playing a game and say oh i want to browse the web to check on some game codes or whatever you can go right back to the game.
The only time you should use a task manager is when there is a rogue application or a memory leak.
Click to expand...
Click to collapse
Great job explaining this man, I've been aware that killing apps just makes them restart. I really only kill apps if they are acting a fool.
And to clear things up I don't have a task killer installed, however I do use the one built into the go launcher app drawer to kill apps that go nuts.
I have used the v6 script before, however I recently downloaded Rom toolbox and it let's you adjust minfrees from there. You guys should check it out
Sent from my Inspire 4G using xda premium

I don't use a task killer. My phone burns less than 1% of battery per hour when idle.
Nexus One on Cyanogenmod 7.1

exileinoblivion7 said:
I have used the v6 script before, however I recently downloaded Rom toolbox and it let's you adjust minfrees from there. You guys should check it out
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
i have a low end phone, as i ran out of cash after buying myself headphones and an itouch, so i couldnt get the phone of my dreams and had to settle for a really cheap samsung galaxy 3 so i dont have a very wide choice of minfrees i can choose from... i got like 256 ram or something, and i dont use swap because i hate partitioning my sdcard...
im so definitly changing my phone in 2012, im either waiting for the nozumi to come out (huge sony ericsson fan ^_^) or im settling for the HTC gigabeats

Task killers are good when you see a rogue app that is draining a ton of your battery life but aren't good when you use the "Kill All" button. As long as their are poorly developed applications, there will be a use for task killers.

some people will tell you not to use task killers because it inhbits Android's normal functioning by interfering with RAm use, causes things to go wrong, running apps don't use battery, blah blah blah. but there are a few problems with these claims.
First, Android's RAM management is not flawless. no Operating system is. fanboys keep claiming it is yet offer no support for whether a 3rd party task killer is better or worse. in fact, they were all claiming this when Froyo was the latest. but then when Gingerbread came out, one of its new features was better RAM management, which fanboys around the internet praised it for, which means there had, in fact, been room for improvement, which they had been denying for quite some time.
second. there are around 500,000 apps on the market. some are flawed, causing RAM leaks and various other malfunctions that ANdroid can't always handle. a task killer is your best, and sometimes only option in this situation, as you might not reasonably have the option of deleting the app permanently.
third, battery life. it may be true that apps simply being running in the background alone doesn't use battery; I'm not sure. yet what fanboys routinely ignore is, many of these apps don't just sit there waiting to be turned on again. some of them turn on so as to collect user data about all sorts of things, then broadcast it to the developer for various uses. this broadcasting uses your phone's radio even when in the background, and that DOES use electricity - from your battery, not to mention data if you have a limited plan. a very large amount of apps do this, which is one major reason why ICS now includes a data management menu that monitors all apps' data usage, as well as a built in app freezer that stops apps from running until you allow them to again.

I use the one that comes stock, and alathough it frees up ram I dont notice any difference in battery drain (1% per hour) or any difference in performance

Falkner09 said:
some people will tell you not to use task killers because it inhbits Android's normal functioning by interfering with RAm use, causes things to go wrong, running apps don't use battery, blah blah blah. but there are a few problems with these claims.
First, Android's RAM management is not flawless. no Operating system is. fanboys keep claiming it is yet offer no support for whether a 3rd party task killer is better or worse. in fact, they were all claiming this when Froyo was the latest. but then when Gingerbread came out, one of its new features was better RAM management, which fanboys around the internet praised it for, which means there had, in fact, been room for improvement, which they had been denying for quite some time.
second. there are around 500,000 apps on the market. some are flawed, causing RAM leaks and various other malfunctions that ANdroid can't always handle. a task killer is your best, and sometimes only option in this situation, as you might not reasonably have the option of deleting the app permanently.
third, battery life. it may be true that apps simply being running in the background alone doesn't use battery; I'm not sure. yet what fanboys routinely ignore is, many of these apps don't just sit there waiting to be turned on again. some of them turn on so as to collect user data about all sorts of things, then broadcast it to the developer for various uses. this broadcasting uses your phone's radio even when in the background, and that DOES use electricity - from your battery, not to mention data if you have a limited plan. a very large amount of apps do this, which is one major reason why ICS now includes a data management menu that monitors all apps' data usage, as well as a built in app freezer that stops apps from running until you allow them to again.
Click to expand...
Click to collapse
Could you please explain what third party task killers do that the Android system manager doesnt do natively?

johnston9234 said:
Could you please explain what third party task killers do that the Android system manager doesnt do natively?
Click to expand...
Click to collapse
From my personal experience it doesn't kill some rogue apps that drain my phone's battery life. Occasionally I use the app "GPS Status" to help find my location faster and if I don't immediately kill the app after my location is locked, the app shoots up to 30-40% on Battery Status.

johnston9234 said:
Could you please explain what third party task killers do that the Android system manager doesnt do natively?
Click to expand...
Click to collapse
work responsively, to start with. every time i've tried to open the application manager on android, I first have to go through all the sub menus to get to it, then sit and wait for it to slooooooooooowly load up the list on installed apps, then running apps, then click on the app, then wait for it to load that particular app's info, THEN I can force close it.
two, they often catch apps running that the default manager doesn't notice, I presume because their developers code them to be hidden somehow.
so yeah, they're occasionally a valid option to use.

I'm happy with or without task killer )
Sent from my GT-S5830 using xda premium