Task manager
- Thread starter xdragon50
- Start date
Here is a link http://www.droidforums.net/forum/droid-applications/65483-task-killers-answer-google-developers.html that may help
Here's something else to read:
Task Killers Per Lifehacker:
Android Task Killers Explained: What They Do and Why You Shouldn't Use Them
How Android Manages Processes
In Android, processes and Applications are two different things. An app can stay "running" in the background without any processes eating up your phone's resources. Android keeps the app in its memory so it launches more quickly and returns to its prior state. When your phone runs out of memory, Android will automatically start killing tasks on its own, starting with ones that you haven't used in awhile.
The problem is that Android uses RAM differently than, say, Windows. On Android, having your RAM nearly full is a good thing. It means that when you relaunch an app you've previously opened, the app launches quickly and returns to its previous state. So while Android actually uses RAM efficiently, most users see that their RAM is full and assume that's what's slowing down their phone. In reality, your CPU—which is only used by apps that are actually active—is almost always the bottleneck.
Why Task Killers Are (Usually) Bad News
Apps like Advanced Task Killer, the most popular task killer in the Market, act on the incorrect assumption that freeing up memory on an Android device is a good thing. When launched, it presents you with a list of "running" apps and the option to kill as many as you want. You can also hit the Menu button to access a more detailed "Services" view, that lists exactly which parts of each application are "running", how much memory they take up, and how much free memory is available on your phone. 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.
What You Should Do Instead
That said, not all apps are created equal. Many of you have used task killers in the past and actually found that after freeing up memory, your phone works a bit better. It's more likely that this is because you've killed a bad app—one that was poorly coded, and (for example) keeps trying to connect to the internet even when it shouldn't. Any performance increase you experience is more likely because you killed the right app, not because you freed up loads of memory (or, in many cases, it's just placebo). Instead of killing all those apps, find out which ones are actually causing the problems. If you really know what you're doing, you may benefit from using a task killer to stop the one or two inefficient-but-loved apps on your phone.
Note, however, that this is still a contested notion. A lot of developers (including ROM builder extraordinaire, Cyanogen) will not even look at your bug reports if you're using a task killer. In this humble blogger's opinion, your best bet is to stay away from regular task killer usage entirely. If you absolutely have to have that one battery-killing app on your phone, though, kill away—just be aware that when you experience a recurring Android bug later on, the task killer may be at fault. Of course, you can just stop using it to determine whether that is or isn't the case.
Task Killers Per Lifehacker:
Android Task Killers Explained: What They Do and Why You Shouldn't Use Them
How Android Manages Processes
In Android, processes and Applications are two different things. An app can stay "running" in the background without any processes eating up your phone's resources. Android keeps the app in its memory so it launches more quickly and returns to its prior state. When your phone runs out of memory, Android will automatically start killing tasks on its own, starting with ones that you haven't used in awhile.
The problem is that Android uses RAM differently than, say, Windows. On Android, having your RAM nearly full is a good thing. It means that when you relaunch an app you've previously opened, the app launches quickly and returns to its previous state. So while Android actually uses RAM efficiently, most users see that their RAM is full and assume that's what's slowing down their phone. In reality, your CPU—which is only used by apps that are actually active—is almost always the bottleneck.
Why Task Killers Are (Usually) Bad News
Apps like Advanced Task Killer, the most popular task killer in the Market, act on the incorrect assumption that freeing up memory on an Android device is a good thing. When launched, it presents you with a list of "running" apps and the option to kill as many as you want. You can also hit the Menu button to access a more detailed "Services" view, that lists exactly which parts of each application are "running", how much memory they take up, and how much free memory is available on your phone. 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.
What You Should Do Instead
That said, not all apps are created equal. Many of you have used task killers in the past and actually found that after freeing up memory, your phone works a bit better. It's more likely that this is because you've killed a bad app—one that was poorly coded, and (for example) keeps trying to connect to the internet even when it shouldn't. Any performance increase you experience is more likely because you killed the right app, not because you freed up loads of memory (or, in many cases, it's just placebo). Instead of killing all those apps, find out which ones are actually causing the problems. If you really know what you're doing, you may benefit from using a task killer to stop the one or two inefficient-but-loved apps on your phone.
Note, however, that this is still a contested notion. A lot of developers (including ROM builder extraordinaire, Cyanogen) will not even look at your bug reports if you're using a task killer. In this humble blogger's opinion, your best bet is to stay away from regular task killer usage entirely. If you absolutely have to have that one battery-killing app on your phone, though, kill away—just be aware that when you experience a recurring Android bug later on, the task killer may be at fault. Of course, you can just stop using it to determine whether that is or isn't the case.
Themsbball
New Member
- Joined
- Feb 23, 2011
- Messages
- 24
- Reaction score
- 0
Does my droid really need a task manager. I heard that android 2.2 doesn't need one.
Thanks
Sent from my DROID2 GLOBAL using DroidForums
Thanks
Sent from my DROID2 GLOBAL using DroidForums
Nope. Using a task manager/killer will cause more problems than they fix. Best to not use one.
Sent from somewhere...
Sent from somewhere...
Themsbball
New Member
- Joined
- Feb 23, 2011
- Messages
- 24
- Reaction score
- 0
Can u explain y please.
Sent from my DROID2 GLOBAL using DroidForums
Sent from my DROID2 GLOBAL using DroidForums
Android has a built in task manager. When you use an 3rd party app its using extra resources to do double duty basically. Also a lot of the task managers kill processes that need to run and the start back up automatically, wasting more battery life. You may also encounter more force closings due to this same factor.
Sent from somewhere...
Sent from somewhere...
- Joined
- Jun 12, 2010
- Messages
- 6,365
- Reaction score
- 35
http://m.lifehacker.com/5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them
This thread has been Thunder struck!
This thread has been Thunder struck!
Themsbball
New Member
- Joined
- Feb 23, 2011
- Messages
- 24
- Reaction score
- 0
Thanks guys but what about the Motorola task manager that came with my droid. Should I use that?
Thanks
Sent from my DROID2 GLOBAL using DroidForums
Thanks
Sent from my DROID2 GLOBAL using DroidForums
You shouldn't use any task manager, period, not even the one provided by motorola, they really don't serve any purpose except to kill your battery life and freeze up your phone with froyo.
Sent from my DROID2 GLOBAL using DroidForums
Sent from my DROID2 GLOBAL using DroidForums
Themsbball
New Member
- Joined
- Feb 23, 2011
- Messages
- 24
- Reaction score
- 0
r u sure
http://www.motorola.com/staticfiles/Support/Experiences/Performance_Manager/US/US.htm
Sent from my DROID2 GLOBAL using DroidForums
http://www.motorola.com/staticfiles/Support/Experiences/Performance_Manager/US/US.htm
Sent from my DROID2 GLOBAL using DroidForums
letsroc1
Member
Im a newbie to the Galaxy S3. Im looking for a task manager that will kill running Apps. I had a Bionic that had one on it preinstall. I take any help that you can give me.
A lot of users have mixed feelings on task managers. Android now does a very good job at memory management. Killing apps and freeing up memory will not increase battery life unless they are using resources like the CPU/Data/GPS in the background, which is either by design, or the app sleeps when not being used.
letsroc1
Member
Thxs for the info.
tgyberg
Silver Member
- Joined
- Dec 18, 2009
- Messages
- 3,961
- Reaction score
- 319
- Location
- Minneapolis, Minnesota
- Current Phone Model
- Pixel 2XL & Pixel C
SystemPanelLite is the best!
Most reactions - Past 7 days
-
35 -
29 -
26 -
16 -
15 -
13 -
9 -
3 -
N
1
