Swiping Apps from Recent Apps on Android: What Happens?

What Happens When You Close Apps on Android?

Many Android users wonder about the fate of applications and their associated data when they are swiped away from the list of currently running apps. The process isn't always what one might intuitively expect.

Understanding Android App Management

The question of what happens when you close an app on Android originates from Android Enthusiast, a section within the Stack Exchange network of question-and-answer websites.

It’s important to understand that Android manages applications differently than desktop operating systems. Android is designed to efficiently handle resources, and simply "closing" an app doesn't necessarily mean it's completely terminated.

The State of a "Closed" App

When you swipe an app from the recent apps list, you are typically not fully killing the application. Instead, you are generally sending it into a suspended state.

In this suspended state, the app no longer actively runs in the foreground, but its processes and data remain in memory. This allows for a faster resumption when you reopen the app, as it doesn't need to be completely reloaded.

Data Retention and Background Processes

Even in a suspended state, some apps may continue to perform limited background tasks. These tasks could include checking for updates, syncing data, or receiving notifications.

Android's system intelligently manages these background processes to minimize battery drain and resource consumption. However, it's possible for suspended apps to still utilize some system resources.

Forcing an App to Stop

If you want to ensure an app is completely terminated, you can go into the Android settings and force stop it. This will remove the app's processes from memory entirely.

However, frequently force-stopping apps can actually negatively impact performance, as the system then needs to expend more energy reloading them each time you launch them.

Key Takeaways

• Swiping an app away doesn't always fully close it.
• Apps typically enter a suspended state, retaining data in memory.
• Background processes may continue even when an app is suspended.
• Force stopping an app completely terminates it, but can impact performance.

Understanding Android's App-Swiping Functionality

An Android Enthusiast reader, Eldarerathis, recently inquired about the app-swipe feature. This functionality, accessible through the home button, presents a list of currently running applications that can be dismissed by swiping.

The Initial Question

Eldarerathis noted the introduction of app-swiping in Ice Cream Sandwich as a native function, not exclusive to custom ROMs like CyanogenMod. He expressed a desire to understand the underlying mechanisms of this feature, as official documentation lacks detailed explanations.

Initial Testing and Observations

To investigate, Eldarerathis conducted tests using the Music app on a CM9 installation. Even after backing out of the app, it remained visible in the recent apps list with an accurate thumbnail.

Further experimentation involved force-stopping the Music app via Settings->Applications. Despite this action, the app persisted in the recent apps list, suggesting the feature isn't directly tied to background processes.

USA Today App Test

A similar test was performed with the USA Today app, yielding comparable results. Force-stopping this application appeared to trigger a relaunch, although the recent apps list's thumbnail didn't immediately reflect this change, likely due to caching.

Core Inquiry: What Happens Upon Swiping?

The central question remains: what occurs at the operating system level when an application is swiped away from the recent apps list? Does the system simply remove the app’s data from RAM and initiate garbage collection, effectively eliminating its saved state?

Delving Deeper into the Process

Essentially, Eldarerathis is seeking clarification on the precise actions taken by Android when an app is removed from the recent applications overview. The behavior observed suggests a more nuanced process than simply terminating a background process.

Understanding this mechanism is crucial for developers and advanced users alike, providing insight into Android’s memory management and application lifecycle handling.

Understanding Android App Management

Insights regarding app behavior when swiped from the recent apps list are provided by Android Enthusiast contributor Austin Mills. The process isn't extensively documented, sparking discussion across various Android forums.

The general understanding, as detailed in forum comments, suggests that swiping an app away mimics repeatedly pressing the back button within the application until it fully exits. Essentially, it functions as a method of application termination.

Regarding the Music app specifically, it's believed to initiate a service. Consequently, while the app's user interface may be closed when swiped away, the service persists in the background. This ensures uninterrupted music playback, even during memory management operations.

Further contributing to the discussion, Eldarerathis shared research uncovering explanations directly from Google employees.

Google Employee Explanations

Research revealed comments from Dianne Hackborn clarifying the effects of removing a task from the recent apps list. Her explanation details two primary actions:

• Killing any existing background or empty processes associated with the application.
• Utilizing a new API to inform any running services about the task's removal, allowing them to respond accordingly.

In a separate blog comment, Hackborn further clarified that removing an app from recent tasks terminates its background processes. However, it doesn't directly halt services. Instead, an API allows services to determine if they should cease operation based on the task removal.

For a complete app termination, a force stop is required. This can be initiated through the app info screen, accessible via a long press on the recent task. A force stop completely kills the application, ending all processes, stopping all services, and removing all associated notifications and alarms.

The app will then be prevented from relaunching until explicitly initiated by the user.

Therefore, swiping an app from the recent list first terminates its background processes and then utilizes the onTaskRemoved function to notify the app of the removal. The app then determines its subsequent actions, meaning there isn't a definitive rule governing its behavior beyond this point.

Do you have additional insights to share? Please contribute in the comments section. For a more comprehensive discussion and further responses from the Stack Exchange community, visit the original discussion thread.