Hot topics

Why clearing recent apps is a waste of time and task killers don't work

androidpit samsung galaxy tab s 2
© nextpit

The second of these two statements is pretty much accepted as common knowledge by anyone even passingly familiar with how app caches and RAM work in Android, but the first statement is not as commonly understood. This is why the developer of Greenify, a great app you can use to hibernate apps that have a tendency to stay up past their bedtime, decided to clear things up.

androidpit samsung galaxy tab s 2
It may be tempting to ''close all'' but you won't really get the performance boost you want. © ANDROIDPIT

To give you the super simple explanation (which we've covered in greater depth before), when you launch an app it gets stored in random access memory. When you close it, it stays in your RAM so that if you launch it again it will launch must faster. When you force close or swipe away an app in the recent apps list, you effectively clear out that cached app and the next time you launch it, it will be like you're doing it from a fresh boot. This means it takes longer and requires more system resources.

AndroidPIT performance monitoring 1
Depending on how into your RAM and CPU usage you are, there's lots of tools available. © NextPit/Pavel Petrov

Now, when you have a recent apps list that's 20 apps long then it makes perfect sense to clear away the ''one-off'' apps that you opened once and probably won't open again in the near future. This clears up RAM for other tasks and, on a practical level, you probably don't need those apps stored in memory anyway. In this instance, swiping away unused apps can be a useful way to free up some additional RAM for other tasks. But clearing all of your recent apps creates slow down later on.

speedup7
Some RAM managers only clear out the least used apps in your recent apps list. © ANDROIDPIT

The same thing goes for task killers and RAM boosters, which simply kill everything: cached apps and background processes. The same problem arises when you launch the app again. If you've cleared it from memory it takes longer to launch, and if you've killed background processes they usually just start up again after a short period of time. So for freeing up RAM in the short term these are perfectly fine, but as a general remedy for improving performance they are nothing more than a panacea.

AndroidPIT Process Stats RAM Usage
The Android OS gives you all kinds of data that lets you assess how demadning your apps are. © NextPit

If you know how these tools work then using them is fine, but most people don't quite get the mechanics of how caches work and why they are actually a good thing. Take Android L's ART (Android Run Time), for example: by pre-compiling apps once and keeping them stored in RAM, you'll notice significant increases in app launches and responsiveness. This is a good thing, and there are several reasons why Google is making ART the default runtime in the next version of Android.

This is also why the dev behind Greenify, Oasis Feng, decided to illuminate us with the following pearls of wisdom:

Swiping away apps from recent tasks frequently is not a good practice, since it reduces the efficiency of process cache mechanism in Android, thus impact the performance of your device.

Swiping away apps from recent tasks kills the process of those apps, thus prevent them from being cached in memory. When you launch them later, it takes longer time and much more CPU cycles to create the process and re-initialize the app runtime.

Clearing recent tasks does free much memory, at the expense of later performance and battery consumption for launching those apps again. So if you have a device with 2G RAM, it gains no benefits in practice.

Coming from a developer involved with an app that is very well recognized for managing your apps, background processes and processor consumption, you can assume he knows what he's talking about. So, the moral of the story is this: clearing everything from the recent apps list is a waste of time unless you seriously need every inch of RAM available right there and then. Clearing out apps you're not going to switch between regularly however, is perfectly fine. So, your frequently used apps can stay and everything else can be killed with fire. Simple.

Via: Reddit Source: XDA Developers

  Editor's choice Best smart home control center Best price-performance ratio Best sound Best sound supplement Best display
Product
Product image Amazon Echo Dot (5. Gen) 2022 Product Image Amazon Echo Hub Product Image Amazon Echo (4.Gen) Product Image Amazon Echo Studio Product Image Amazon Echo Sub Product Image Amazon Echo Show 10 (3rd. Gen) Product Image
Review
Review: Amazon Echo Dot (5. Gen) 2022
Review: Amazon Echo Hub
Not yet tested
Review: Amazon Echo Studio
Not yet tested
Not yet tested
Price Compariosn
Go to comment (8)
Kris Carlon

Kris Carlon
Senior Editor

Kris is a former AndroidPIT Editor who came to the team via a lengthy period spent traveling and relying on technology to keep him in touch with the outside world. He can usually be found juggling three phones at once and poring over G+ posts, Reddit and RSS feeds.

Liked this article? Share now!
Recommended articles
Latest articles
Push notification Next article
8 comments
Write new comment:
All changes will be saved. No drafts are saved when editing
Write new comment:
All changes will be saved. No drafts are saved when editing

  • 3
    Nelson Branco Sep 23, 2014 Link to comment

    (Aboute ART runtime)
    Quote:
    ..."Take Android L's ART (Android Run Time), for example: by pre-compiling apps once and keeping them stored in RAM, you'll notice significant increases in app launches and responsiveness.." >>> I am confused here.
    Is this part of the article correct? After compiled with dex2oat (.dex files to ELF), aren't the apps stored at the storage space? Aren't the apps stored in RAM only after launch?

    I though that w/ ART apps launch faster because of replacing Just In Time (JIT/dalvik) compilation with Ahead Of Time (AOT/ART) compilation, being the bytecode already compiled, running the app from the ELF executable.
    Can someone enlighten me on this? Thanks


  • Barry Dugger 4
    Barry Dugger Sep 22, 2014 Link to comment

    iOS users don't have interchangeable batteries either. Besides, they're not problems really, we are just trying to make our phones even faster. Mine's fine if I don't do anything. It's a game to see what I can do with my phone.
    Also the darn screens on iOS phones were soooo small until now-I needed a bigger screen. A hazard of being old. Sigh.


  • 2
    Hans Meiser Sep 22, 2014 Link to comment

    Problems iOS-Users don't have.


  • Barry Dugger 4
    Barry Dugger Sep 21, 2014 Link to comment

    Greenify gave me nothing but grief on my Galaxy Round. SD Maid seems to work really well, but it is really designed for rooted phones.


  • Junaid Q. 17
    Junaid Q. Sep 20, 2014 Link to comment

    greenify is best


  • 10
    Byron Garay Sep 20, 2014 Link to comment

    And thats exactly what I always do, very good article, Helpful!

    Dan C.Moni Mihailov


  • 12
    Paco Inurreta Sep 20, 2014 Link to comment

    I got used to clear-everything-after-using when I had my iPhone 4S and to this day I have been doing the same with my Galaxy S4. I read about this the other day (yesterday?) and I have been forcing myself not to close them anymore but is damn hard... Its just something I automatically do.

    Moni Mihailov


  • flooney 37
    flooney Sep 20, 2014 Link to comment

    True Story!

    Monty SiladhielMoni Mihailov

Write new comment:
All changes will be saved. No drafts are saved when editing