- 01-12-2010, 11:18 PM #2
It's not necessary.
- 01-12-2010, 11:29 PM #4
- 01-13-2010, 06:46 AM #6
After reading this and doing some testing with Pandora and Tune Wiki I noticed these processes ended very soon after exiting the program. I was checking this within Running Services. I then did some testing with Shop Savvy and this too closed out from Running Services within a few seconds of backing out of the app.
So as long as I used the back key android was killing the process. The funny thing is Advanced Task Manager was still showing that TuniWiki was running and Shop Savvy was running.
This tells me Advanced Task Manager needs some work especially since it was showing TuneWiki twice when in fact it wasn't running at all.
I went ahead and uninstalled Advanced Task Manager for now which was taking 22k in resources anyhow. I'll see how my droid performs without me ending tasks through the task manager.
Thanks for sharing that article. It was useful.
- 01-13-2010, 10:12 AM #8
- 01-13-2010, 10:18 AM #9
I also uninstalled my ATK a couple days ago, and I'm not seeing any negative results from not killing tasks. I don't know if its running better, but its not running worse, which was the important part. Looks like the article (which was written by someone much more versed in Linux and the like than I am) was spot on.
- 01-13-2010, 11:21 AM #10
- 303 Posts
my 2 cents is that whether I use it or not, i do not see any change in anything. It's so hard to tell what's doing what anyways because the android OS can restart apps that are setup to restart anyways and even tho an app process is still active, it doesn't mean its doing anything, just idle and using up no resources. I've also noticed that after you boot for first time and check the process list, many of my apps are there, even the one's you'd never expect to start at boot such as "Shop savvy" that have no widgets or anything that shoudl be running in background. Ininitially i'd kill all these on boot to give me a clear head What i've found though, is that if I do not use the task killer after boot, and just wait some time, many of those processes that started at boot are killed off, so seems the OS handles the memory fairly well and kills stuff that's not needed and is not priority.
My preference is to have a task killer but i do not OCD and use it all the time, rarely ever anymore. What I like it for is for bugs in certain software, such as the stock browser and beautiful widgets for example, sometimes will need GPS for something and if im inside, will try to find a signal for so long, hurting battery. When these things happen from time to time, i use the task manager to kill them.
- 01-13-2010, 11:27 AM #11
- 01-14-2010, 12:43 AM #12The bending unit
- 423 Posts
- Stock (so far)
I was using Task Killer when I first got my Droid. But noticed allot of screen freezing and alike. I uninstalled, and then tried ATK... same thing (keep in mind, this all occurred with both apps running for about two weeks straight after being installed).
I've been running my Droid without any task killing app for about a month now, and everything seems to be cool as mud. No issues whatsoever. My battery life hasn't changed much either.
Just noticed I hit my 100th. post!
- 01-14-2010, 07:35 AM #13
- 01-14-2010, 08:42 AM #14
- 01-21-2010, 10:00 PM #15
- 133 Posts
I went ahead and got rid of advanced task killer, and have actually noticed a slight improvement in overall performance...but only slight. The only negative I've noticed is that every once in a while the phone will get very sluggish for a minute or two then be fine again. It never did that when ATK was installed.
- 01-21-2010, 11:42 PM #16
Activity | Android Developers Follow the Activity Lifecycle link about 1/4 way down.
The abridged easy to read version.
4 stages of Application life
1. Active - the application currently in use, last to be killed, rarely if ever killed, only killed when the phones needs the resources to remain operating.
2. Paused - application is still active or visible, it maintains all recent application interactions, i.e paused to answer a phone call, text, etc, 2nd to be killed when a device needs additional resources
3. Stopped - application is no longer active or visible, 1st to be killed when the device needs additional resources
4. Killed - a paused or stopped application that has been killed by android because memory and resources were needed elsewhere
- 01-22-2010, 04:56 AM #17
- 01-22-2010, 11:06 AM #18
- 01-22-2010, 01:45 PM #19
I don't use any task managers.
I used to though.
I honestly haven't seen much of a difference, if any. I tried just about every popular task manager and everything still seems the same. As for GPS/WIFI/BLUETOOTH I just have the power widget for that
- 01-22-2010, 08:06 PM #20
This was wonderful information. Thank you, thank you, thank you for the link to that article.
I was using Taskiller primarily for battery optimization and not memory management. It always struck me as odd that when I would review battery usage the program I was using to enhance battery life was responsible for at least 4% of the daily drain.
Thanks for this info and the personal testing many here have done - UNINSTALING my task killer
- 01-22-2010, 11:36 PM #21
I see things a little differently. I posted this over at Droidforums, but will repost it here. Its my opinion, take it or leave it, but being that I use the phone and do see a difference, its not anyone's place to tell me if I am right or wrong.
Without forth ado,
In a perfect world, then applications in the background would not cause issue.
This, is not a perfect world however, and we aren't running regular Linux. Our apps are running in a virtual machine.
An interesting thing I found on wikipedia under Android limitations....
Garbage collection will slow down programs that make too many memory allocations so that Dalvik can keep a pool of free memory. This may noticeably affect responsiveness.
Its been my experience that using a task killer unwisely, hurts performance, breaks features, etc. Knowing what to put on your ignore list for a task killer makes the TK an efficient and quick way to get performance back when a program or program(s) are bogging the phone down. I have mine setup so it ignores my widgets that update, my messaging, email, and calendar apps, and I do NOT have it run in the background or on startup.
When my phone starts to bog down, and lets face it, ALL phones do at some point, I go in, and hit the end all button. It kills off whats not ignored, INCLUDING itself, and I get that fresh dou...erm, boot feeling again
- 01-23-2010, 12:52 AM #22
From personal experience, I have never had a single issue with the OS beginning to slow down or become less responsive, regardless of how much memory I am using. But, I do have Advanced Task Manager installed anyway, because you never know when you might actually need it.
- 01-23-2010, 01:52 AM #23
There is a native system tool to view running apps and kill whatever you want. If one's desire is to optimize battery and memory performance, that can be accomplished by having less apps installed and running in the background. So, I do see the point of not installing or continuously running a task killer. However, I don't see the benefit of using the task killer to force kill running apps when there is a system tool for just that. Is it just because it can be done with one quick click?
- 01-23-2010, 08:57 AM #24
- 01-24-2010, 10:24 AM #25
from a newb standpoint, what are the apps you want to kill and what do you want to leave? Should you leave all of you emails active? Coming from a BB as quite a few are, we are more memory conscience but really I want to save battery. I run through my battery like crazy. While looking at processes, there are some I really don't know how they get started?
Right now I have in ATK:
car home - dont use
corporate calendar - dont use