Why You Shouldn’t Use a Task Killer On Android
- Thread starter cybervibin
- Start date
-
- Tags
- task killer
-CALIBAN666-
Senior Member
with a usuable brain a good rom+good kernel and tweaks there is no need for that,just my opinion.
To clarify things a bit: Like already said, Android has its own task-killer. It automatically kills tasks, when theres only few RAM available. It manages the whole life-cycle of every app. The problem is, it is not optimized to a certain amout of RAM, like 256 or 512 mb, which makes it bad and laggy if you have got a phone with low RAM.
However, task-killers may sometimes seem to make those phones faster, but thats mostly not true, because it(the task killers) messes with the build-in task-killer of Android.
---------- Post added at 06:10 PM ---------- Previous post was at 05:49 PM ----------
The solution is, to tune the values and settings of the default build-in task-killer. That definitly is the best option. A few scripts like the v6-supercharger scripts try to do that, also Roms like the cyanogenmod are tweaked really good.
However, task-killers may sometimes seem to make those phones faster, but thats mostly not true, because it(the task killers) messes with the build-in task-killer of Android.
---------- Post added at 06:10 PM ---------- Previous post was at 05:49 PM ----------
The solution is, to tune the values and settings of the default build-in task-killer. That definitly is the best option. A few scripts like the v6-supercharger scripts try to do that, also Roms like the cyanogenmod are tweaked really good.
Not 100% true but if you're on a higher-end device and your swap/cache/data are all on the same NAND chip you'll probably not need a task killer, unlike a lot of handsets they still have a lot of read/writes to the SDCard and that's where a lot of battery consumption comes in, killing apps that don't use a lot of RAM but are churning data constantly through cache/sdcard need killing sometimes just to stop it stalling.
Bashing away at my HTC Desire C
Bashing away at my HTC Desire C
Damn awesome
Thanks a lot for the information!!
But what about greenify, it ain't a task killer, just used to hibernate apps that I do not use much
Not like a traditional task killer, it's different
Correct me if I am wrong
Sent from my Moto G using Tapatalk
Thanks a lot for the information!!
But what about greenify, it ain't a task killer, just used to hibernate apps that I do not use much
Not like a traditional task killer, it's different
Correct me if I am wrong
Sent from my Moto G using Tapatalk
Ugh. Why do people keep repeating this stuff without actually testing it? It's like a religion. "Android's task manager works perfectly already! You don't need swap memory or a task manager!" Have you even tried them?
Android's task management is only as good as the worst app you have on your phone. For instance, apps are required to save their state before they are killed, so, theoretically, they can be restarted and seamlessly continue where they left off. This is great in theory, but is disconnected from reality. If the app developer doesn't bother to write the code to save the state, killing apps starts them over again from the beginning. If the app developer only saves the minimal amount of state (like the URL of the page you're visiting, instead of the entire page), then it has to slowly reload the entire page from the web instead of quickly reloading it from memory. If an app developer includes a service that runs in the background constantly downloading ads or reporting your location or checking whether something is true every 5 seconds, it will slow down your phone. There's nothing wrong with killing poorly-written apps, and it really will make your phone more responsive. (And most apps are poorly-written, so no, you can't always uninstall them and install an alternative.)
Android's task management is only as good as the worst app you have on your phone. For instance, apps are required to save their state before they are killed, so, theoretically, they can be restarted and seamlessly continue where they left off. This is great in theory, but is disconnected from reality. If the app developer doesn't bother to write the code to save the state, killing apps starts them over again from the beginning. If the app developer only saves the minimal amount of state (like the URL of the page you're visiting, instead of the entire page), then it has to slowly reload the entire page from the web instead of quickly reloading it from memory. If an app developer includes a service that runs in the background constantly downloading ads or reporting your location or checking whether something is true every 5 seconds, it will slow down your phone. There's nothing wrong with killing poorly-written apps, and it really will make your phone more responsive. (And most apps are poorly-written, so no, you can't always uninstall them and install an alternative.)
Lollipop task managers
While it might sound good to say you don't need one for Lollipop, a quick internet search will tell you otherwise. Many users (including this one) feel their phones have been bricked by Lollipop. I was constantly fighting to maintain sufficient memory (I often fell below 100MB free) for the phone to be barely useable (not good at this point, just barely usable). A quick check showed that almost every app (closed or open) was consuming very large memory blocks (typically 50MB per app, independent of the app).
In a last ditch effort I did a factory refresh and removed almost every app. The phone now works well again. So, yes, Lollipop has a (very piss poor excuse for a) built in memory manager and many will need a 3rd party manager, will need to constantly manually close apps, to hope that M is better than lollipop or go with LG that resisted the Lollipop 5.1.1 upgrade. Another possibility is to remove most of the apps and only use the bare essentials.
I am a rocket scientist, not an amateur.
While it might sound good to say you don't need one for Lollipop, a quick internet search will tell you otherwise. Many users (including this one) feel their phones have been bricked by Lollipop. I was constantly fighting to maintain sufficient memory (I often fell below 100MB free) for the phone to be barely useable (not good at this point, just barely usable). A quick check showed that almost every app (closed or open) was consuming very large memory blocks (typically 50MB per app, independent of the app).
In a last ditch effort I did a factory refresh and removed almost every app. The phone now works well again. So, yes, Lollipop has a (very piss poor excuse for a) built in memory manager and many will need a 3rd party manager, will need to constantly manually close apps, to hope that M is better than lollipop or go with LG that resisted the Lollipop 5.1.1 upgrade. Another possibility is to remove most of the apps and only use the bare essentials.
I am a rocket scientist, not an amateur.
I notice a considerable improvement in battery power, but at the cost of a loss in performance. However, I use my mobile only occasionally. I am not complaining. Good app.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
39So i saw many posts on which people have asked as to which task killer should be used !
and then i stumble upon this site which provided me the details,
i just complied info
sources-by Chris Hoffman
http://www.howtogeek.com/127388/htg-explains-why-you-shouldnt-use-a-task-killer-on-android/
Android Doesn’t Manage Processes Like Windows
Most Android users are familiar with Windows. On Windows, many programs running at one time – whether they’re windows on your desktop or applications in your system tray – can decrease your computer’s performance. Closing applications when you’re not using them can help speed up your Windows computer.
However, Android isn’t Windows and doesn’t manage processes like Windows does. Unlike on Windows, where there’s an obvious way to close applications, there’s no obvious way to “close” an Android application. This is by design and isn’t a problem. When you leave an Android app, going back to your home screen or switching to another app, the app stays “running” in the background. In most cases, the app will be paused in the background, taking up no CPU or network resources. Some apps will continue using CPU and network resources in the background, of course – for example, music players, file-downloading programs, or apps that sync in the background.
When you go back to an app you were recently using, Android “unpauses” that app and you resume where you left off. This is fast because the app is still stored in your RAM and ready to be used again.
Why Task Killers Are Bad
Proponents of task killers notice that Android is using a lot of RAM – in fact, Android stores a lot of apps in its memory, filling up the RAM! However, that isn’t a bad thing. Apps stored in your RAM can be quickly switched to without Android having to load them from its slower storage.
In summary, you shouldn’t use a task killer – if you have a misbehaving app wasting resources in the background, you should identify it and uninstall it. But don’t just remove apps from your phone or tablet’s RAM – that doesn’t help speed anything up.
Empty RAM is useless. Full RAM is RAM that is being put to good use for caching apps. If Android needs more memory, it will force-quit an app that you haven’t used in a while – this all happens automatically, without installing any task killers.
Task killers think they know better than Android. They run in the background, automatically quitting apps and removing them from Android’s memory. They may also allow you to force-quit apps on your own, but you shouldn’t have to do this.
Task killers aren’t just useless – they can reduce performance. If a task killer removes an app from your RAM and you open that app again, the app will be slower to load as Android is forced to load it from your device’s storage. This will also use more battery power than if you just left the app in your RAM in the first place. Some apps will automatically restart after the task killer quits them, using more CPU and battery resources.
Whether RAM is empty or full, it takes the same amount of battery power – decreasing the amount of apps stored in RAM won’t improve your battery power or offer more CPU cycles.
hope u understood!
words of wisdom by fellow-mates
go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.5I agree with that...to an extent
Auto killing apps is plain stupid, but I do believe in killing certain apps. In a perfect world heavy apps would just be uninstalled, but plenty of useful apps without good replacements are fairly heavy, and it helps to kill them. E.g. after exiting a game I will kill it because its hogging up valuable ram by running in the background, while still using he same resources it uses at the forefront.
I understand that android, and Linux should manage ram well, but more often then not some app is just out there slowing my phone down. Even an hour later of not using that app, it'll still be in the background using up a lot of CPU and ram I don't have (more importantly battery). Android is great at managing smaller apps, but in my experience, it sucks at doing the same for larger apps.
Sent from my Desire HD using xda app-developers app5I don't use automatic task killers, those that are constantly running, but i do kill unused tasks and apps with no reason to be still running. Google services is a common example. It will launch at boot and keep running peemanently, even if you never launch a google app, google services is running, why?
A lot of apps, mostly the free ones, get revenue by reporting anonymous usage statistics (not so anonymous in some cases). So they stick a running service even if the app is never launched again (sometimes even if it isn't launched in the first place).
To sum up, killing everything is bad, but leaving everything to run free can also decrease performance. This can be observed on an android device that has been running for a long time, versus an android device that's just been reset.22To clarify things a bit: Like already said, Android has its own task-killer. It automatically kills tasks, when theres only few RAM available. It manages the whole life-cycle of every app. The problem is, it is not optimized to a certain amout of RAM, like 256 or 512 mb, which makes it bad and laggy if you have got a phone with low RAM.
However, task-killers may sometimes seem to make those phones faster, but thats mostly not true, because it(the task killers) messes with the build-in task-killer of Android.
---------- Post added at 06:10 PM ---------- Previous post was at 05:49 PM ----------
The solution is, to tune the values and settings of the default build-in task-killer. That definitly is the best option. A few scripts like the v6-supercharger scripts try to do that, also Roms like the cyanogenmod are tweaked really good.
New posts
-
-
-
AC8257 CPU Based unit's problems & questions - Couldn't find any info about it- Latest: Oswald Boelcke
