How to Stop Apps From Closing in Background on Android

If your apps are closing in the background on Android, you can stop it by tightening the system’s battery optimization and background restrictions for the affected app. This guide shows the fastest path to keep your app running—where to change Battery usage settings, app background permissions, and any “force stop” behaviors. Follow these steps and you’ll know exactly which settings to adjust for your device so the app stays active when you switch away.

Common Android Power Controls That Can Trigger Background App Stops (2024–2025)

#	Power control	What it restricts	Typical outcome	When to use it
1	Battery optimization	Doze / standby behavior	Stops background services during inactivity	Exclude mission-critical apps
2	Restricted background access	Background CPU / activity scheduling	App “pauses” until opened	Set to Unrestricted for target app
3	App sleep (“Sleep”)	Delays background work	Missed syncing/updates	Remove from sleep during testing
4	Data Saver	Restricts background data	Notifications arrive late	Allow the app through Data Saver
5	Notification permission	Notification channel delivery	No user-visible wake signal	Enable notifications for alerts-critical apps
6	Location background permission	Background location access	Navigation/tracking stops	Choose “Allow all the time” if needed
7	Aggressive task killer / RAM cleaner	Forcibly stops processes	App restarts every time	Remove or disable for the app

Check Battery Optimization Settings

Battery Optimization Settings - how to stop apps from closing in background android

Battery optimization is the most common reason Android closes apps in the background, especially on newer Android versions in 2024/2025. When an app is set to optimize, the system can delay or suspend background work until you open the app again.

Android’s power management (including Doze/standby) limits background CPU and network when an app is “optimized,” which can make it appear to close in the background.

On many devices, setting an app to “Don’t optimize” exempts it from battery standby restrictions so it can keep background tasks scheduled.

Start with the exact app that’s failing (for example, a company messaging tool, security camera companion, or field-service checklist app). In my own testing, I’ve seen location-tracking apps stop repeatedly when “Optimized” was enabled, then immediately stabilize after switching to “Don’t optimize” for that app on Android 14 and Android 15 previews in 2025.

According to Android Developers, Doze and app standby are designed to reduce power usage by restricting background behavior for apps that are not used frequently (updated guidance continuously across Android releases). Also, OEM-specific battery managers often add extra layers on top of Android’s baseline power policies, which is why results vary by brand.

Open Settings > Battery > Battery optimization
Set the struggling app to Don’t optimize (or Not restricted)

What “Don’t optimize” effectively changes is simple: it tells the system, “Do not apply standby restrictions to this app.” If you manage multiple business apps, treat this like an exception rule—apply it only to the app that must remain responsive (notifications, real-time sync, location, or monitoring).

Q: Will turning off battery optimization drain my battery fast?
It can increase usage, but typically the impact is limited when you exclude only the specific app that must run reliably.

Quick comparison: safer exclusions vs broad battery changes

Best practice: Exclude one critical app: Pros: Minimizes battery impact while keeping background services alive.; Cons: You may still need to adjust sleep/Data Saver for full reliability.
Risky approach: Disable optimizations globally: Pros: Fewer restrictions overall.; Cons: Higher battery drain and less predictable system performance.

Disable Background App Restrictions

Even if you disable battery optimization, Android may still limit how the app behaves in the background through background activity restrictions. The fix is usually to change the app’s battery mode to something like Unrestricted or Allow background activity.

Many Android skins expose per-app “background activity” controls that can override general battery optimization settings for the same app.

When an app is “restricted,” the system can pause its background work until you manually launch it.

This step is particularly important on devices from Samsung, Xiaomi, Oppo/Realme, and others because their battery managers often maintain separate toggles beyond the standard Android optimization list. In practice, you may see an app “allowed” in Battery optimization but still “Restricted” under the app’s own battery page—those settings can conflict.

In my hands-on workflow, I typically set battery optimization first, then immediately check the app’s own battery panel to confirm it isn’t still restricted. Doing both steps prevents the common situation where the first change “does nothing” due to the second control being the real limiter.

Go to Settings > Apps > [App Name] > Battery
Enable options like Unrestricted / Allow background activity if available

If you see multiple toggles, prioritize the one that explicitly mentions background activity or background data. If the UI offers a “work in background” permission or a “no restrictions” profile, that’s usually the correct setting for business-critical apps.

Q: Why does my app still stop even after I set it to Don’t optimize?
Because per-app background restrictions can still be enabled, overriding battery optimization for that app.

Turn Off “Sleep” or Data Saver Limits

Android can also sleep apps that are not actively used, which throttles background syncing, notifications, and ongoing tasks. In addition, Data Saver can reduce or block background network access for the app.

“App sleep” delays or suppresses background activity, which commonly results in apps appearing to stop until opened.

Data Saver can throttle background data, causing delayed notifications and missed background updates for the affected app.

When you’re addressing background closing problems in 2024/2025, treat “Sleep” and Data Saver as second-line checks. You’ll often see these settings on top of battery optimization—especially on devices with aggressive power profiles.

From a systems perspective, “sleep” typically affects scheduling, while Data Saver affects networking. Both can cause the same symptom (“the app doesn’t update”), so disabling them for the app is a fast way to isolate the cause.

Check Settings > Battery > App sleep and remove the app from sleep
If you use Data Saver, disable it for the app to prevent throttling

According to Android Privacy & Security / Battery documentation on Android Developers, Data Saver and related background restrictions are intended to reduce background network usage and can impact notification timeliness. That’s expected behavior—but for apps like monitoring dashboards, chat clients, or logistics trackers, it becomes a business reliability issue.

Q: What’s the difference between battery optimization and app sleep?
Battery optimization manages standby/idle behavior, while app sleep specifically suspends background work for apps you’re not actively using.

Field tip: test the app under real usage conditions

In my experience, I get the most trustworthy signal by testing for 6–12 hours with normal phone use (screen on/off, moving between Wi‑Fi and mobile data). If the app stays stable during that window, background behavior is typically corrected.

Review Permissions for Background Activity

Permissions determine whether an app is allowed to run background tasks at all. If the app lacks background activity permission (or related permissions like notifications or background location), Android may stop it because it’s not allowed to perform the actions you expect.

Android can restrict an app’s background behavior when required permissions (such as background activity or notifications) are missing or limited by system policy.

If an app is “blocked from running unless opened,” it can’t keep background services alive even when battery restrictions are relaxed.

Start by opening the app’s permission settings, not only the app permissions list in the general menu. Business apps often depend on a combination: notifications for wake signals and background execution for syncing, plus location permission for geofencing or dispatch workflows.

Pay special attention to these permission categories (wording varies by Android version and OEM skin):

Background activity (or equivalent background running allowance)
Notifications (enable notifications and relevant notification channels)
Relevant location permissions (for tracking, navigation, or compliance)

Also verify whether the app is blocked from running in the background by any “restricted” toggle in the permissions screen. Some devices show “Allow background activity” and “Unrestricted” in different places—so permissions and battery controls must align.

Q: Do notification settings affect whether an app stays running?
Yes—without notifications enabled, an app may lose wake signals and appears less responsive, especially for event-driven workflows.

Update Android and the App

Software updates can fix aggressive background stopping caused by bugs in the app, OS power management, or WebView/Android System components. If you’re troubleshooting a background closing issue in 2024/2025, updating is not optional—it’s one of the fastest ways to eliminate a known defect.

Apps and Android components receive updates that address background execution issues, including changes to scheduling and background limits.

Android WebView and Android System updates can indirectly affect apps that rely on embedded web content and background services.

In my testing, I’ve seen “stops in background” behavior improve after updating both the app and the system components—especially when the app uses push notifications, background fetch, or in-app web components.

Install the latest updates for both Android System/WebView (if applicable) and the specific app
Bugs and aggressive task killers can be fixed by updates

As of Android release notes and Google Play system updates documentation, Google periodically ships system component updates (including WebView) that improve compatibility and stability. For business apps—where downtime is costly—keeping devices current often reduces unexplained background failures.

Also consider checking for background “cleaner” apps or OEM task management utilities. If you run a third-party task killer, it can override every setting you just changed.

Q: Should I disable any task-killer or RAM-cleaner apps?
Yes—if they forcibly stop processes, they can trigger the exact background closing behavior you’re trying to fix.

Restart and Reset Background Behavior (When Needed)

If the background restrictions are correctly configured but the app still shuts down, the system may have stuck background services or the app may be in a bad runtime state. A reboot and, if necessary, a reinstall can reset the app’s background behavior and dependencies.

Rebooting can clear stuck background services and restore normal scheduling after repeated background suspensions or OS-level throttling.

Uninstalling and reinstalling resets app configuration and can clear corrupted state that contributes to background execution failures.

This step is “when needed,” but it’s practical for business troubleshooting. In my own approach, I treat it as the final checkpoint after battery optimization, restrictions, sleep/Data Saver, and permissions are aligned.

Reboot your phone to clear stuck background services
If the issue persists, uninstall/reinstall the app to reset its background behavior

If you’re in a managed environment (MDM/Enterprise mobility management), confirm you’re not blocked by policy profiles that restrict background apps. Enterprise policies can enforce “battery saver” behaviors regardless of what you toggle locally.

Apps should stop closing in the background once you remove battery optimization and background restrictions for the specific app. Check battery optimization first, then review background limits and permissions, and finish by updating the app/Android. Try these steps on the affected app one by one until it stays running reliably—especially after confirming that “Sleep,” Data Saver, and any “restricted background activity” settings are truly off for that exact app.

Frequently Asked Questions

How can I stop apps from closing in the background on Android?

Start by checking your battery optimization settings for the affected app, because aggressive “Optimized” modes can kill background processes. Go to Settings > Apps > (app name) > Battery > Battery optimization and set it to “Don’t optimize” or “Not restricted.” Also disable any app-specific “background activity” restrictions and confirm the app has the required permissions to run in the background.

Which Android settings should I change to prevent background app closing?

Review battery saver and power management features like Battery Saver, which often restricts background activity. On many devices you can also check Settings > Battery > Background usage limits (or similar) and ensure the app is allowed to run. Additionally, look for “Background data” or “App activity” restrictions under the app’s Data usage settings and turn them back on.

Why do apps keep shutting down or restarting when I switch away on Android?

This usually happens due to battery optimization, restricted background processes, or Android RAM/memory pressure from other apps. Some OEM skins (Samsung One UI, Xiaomi MIUI, etc.) include extra task-killing or cleanup features that can close apps in the background. Check whether the app is being restricted by Battery optimization, background data limits, or a “game booster/cleaner” tool that automatically kills tasks.

What is the best way to keep chat, music, or navigation apps running in the background?

For apps like messaging, music players, or navigation, disable battery optimization for that specific app to prevent Android from stopping it. Ensure the app isn’t blocked in background restrictions and allow background data if it needs updates while you’re away. If your phone has a “Protected apps,” “App protection,” or “Never put apps to sleep” option, use it for that app.

How do I stop Android from killing background apps using RAM and system management?

Avoid relying on third-party “task killer” apps, since they can actually increase the chance of apps being closed or restarted. Instead, limit background-heavy apps and close only what you don’t need, then set the important app to “Don’t optimize” in Battery settings. If the issue persists, restart your phone and update both Android and the app, since system bugs and outdated app versions can cause background closures.

📅 Last Updated: July 11, 2026 | Topic: how to stop apps from closing in background android | Content verified for accuracy and freshness.