How to Disable an App on Android: Step-by-Step Guide

Want to disable an app on Android fast? This step-by-step guide shows exactly how to disable an app—so it stops running in the background and no longer appears as active. If you need the quickest path to regain control of notifications, permissions, and background activity, follow these directions.

Disable an App from Settings

App Settings - how to disable an app on android

Disabling an app from the Settings app is the most direct method when the Disable button is available for that app. On most phones, Android treats “disable” as a way to stop the app from running and effectively remove it from your app list, while still keeping the app installed so you can re-enable it later.

“Disabling an app stops it from running and removes it from the launcher (app list) in many cases.”

“If an app can’t be disabled, Android typically limits options to notification control or background restrictions via App info.”

Step-by-step: disable from App info

Open your phone’s Settings.
Go to Apps (or Apps & notifications, depending on the device).
Search for and select the app you want to disable.
Tap Disable and confirm.

From my experience using this on multiple Android devices, the exact wording can vary by manufacturer (Samsung, Google Pixel, Xiaomi, etc.), but the flow is consistently anchored in App info. If you see Disable (rather than only Uninstall), you’re usually dealing with a system component or a preinstalled app that can be turned off without requiring root access.

Q: What happens when you disable an app on Android?
It stops the app from running and removes it from your app list for many system/preinstalled apps, while preserving the ability to re-enable it later from the same App info screen.

Quick decision rules before you tap Disable

If Disable is visible: use it.
If Disable is missing but Uninstall exists: uninstall instead.
If neither is available: switch to notification controls or background restriction steps below.

Q: Will disabling an app delete my data?
Usually no—it typically prevents the app from running; however, some devices may also reset certain app behaviors depending on the app type. If you’re concerned, check Storage/usage details in App info before disabling.

Q: Can I re-enable a disabled app?
Yes. Go back to Settings > Apps > [App Name] and tap **Enable**.

Disable a Preinstalled/System App

Disabling a preinstalled or system app is often possible, but Android may restrict what’s safe to turn off. The core tradeoff is control vs. risk: you can reduce clutter or background activity, but disabling a critical system component can degrade features.

“Some system apps can be disabled for users, while others may be protected by Android or the device manufacturer.”

“Android’s package management behavior varies by app type—system, updated system, or user-installed—affecting whether Disable is offered.”

What to expect on system apps

Many system apps show Disable in the App info page.
Some will show Uninstall updates (if they’re updateable system apps) instead of disable.
Some core components won’t be disable-able at all.

Be careful with core functionality

Examples of areas that can break if disabled incorrectly include:

System UI dependencies (may affect status bar or navigation)
Keyboard/assistive services
Package installer components
Network and permissions brokers

In my testing, I’ve found that disabling “adjacent” helper apps (like companion services for preinstalled tools you never use) is usually safer than touching core services. If you’re unsure, start by disabling the app you don’t need, observe for 24–48 hours, then re-enable if anything changes.

Q: Can I safely disable any preinstalled app?
No. Preinstalled apps range from harmless extras to tightly coupled components; if Disable causes missing features, re-enable immediately from the same App info page.

A quick safety framework (practical, not theoretical)

Use this operational approach:

Disable first only one app at a time.
Test key workflows (calls, messaging, Wi‑Fi/Bluetooth, banking apps).
Document what changed (e.g., notifications, background syncing, widgets).
Re-enable if you see side effects.

Turn Off App Notifications (Alternative to Disabling)

Turning off notifications is the best “low-risk alternative” when you don’t need an app’s alerts but want to keep it installed and stable. It prevents interruptions without risking feature breakage that can happen if you disable certain system-linked apps.

“Notification channels exist on Android 8.0+ (API 26), enabling per-category notification control inside a single app.”

“You can mute or toggle notification categories through the app’s notifications settings in Settings > Apps.”

Step-by-step: mute notifications in App info

Open Settings > Apps.
Select the app.
Tap Notifications (or App notifications).
Turn off the notification categories you don’t want.

On Android 8.0+ devices, apps often expose multiple channels (e.g., “News,” “Promotions,” “Reminders”), which makes fine-grained control possible without disabling the entire app. According to Android Developers, notification channels were introduced in Android 8.0 (API 26) to standardize how users control notification categories. (Android Developers, API 26 / Notification Channels)

Q: Is turning off notifications the same as disabling an app?
No. It keeps the app installed (and potentially running in the background depending on restrictions), but stops it from alerting you.

Pros/cons: disable vs. notifications vs. background restriction

Below is a quick comparison to choose the safest lever for your goal:

Disable
✅ Strongest “stop running” effect (when available)
✅ Reduces background execution
❌ Higher risk of feature side effects for system-linked apps
Turn off notifications
✅ Lowest risk (keeps app functionality)
✅ Immediate reduction in interruptions
❌ Doesn’t guarantee background activity is eliminated
Restrict background activity
✅ Can reduce battery drain and background work
✅ Works even when Disable isn’t available
❌ May delay sync, messages, or background updates

Data snapshot: how apps typically deliver alerts

This table summarizes how Android notification control often maps to app alert types and what you can toggle.

📊 DATA

Common Android Notification Channels and Where to Disable Them (Android 8–14)

#	Notification type (channel)	Typical purpose	Best action	Impact on interruptions
1	Promotions & offers	Marketing pushes	Turn off category	Very high
2	News updates	Content refresh alerts	Mute channel	High
3	Reminders	Scheduled nudges	Disable only if nonessential	Medium–High
4	System alerts (app-specific)	Status changes	Keep on if you need sync signals	Depends
5	Messages / DMs	Direct communication	Disable only for unused accounts	Can be critical
6	Updates for apps you don’t use	Install/upgrade reminders	Turn off if you never act	High
7	Quiet hours / batches	Scheduled delivery mode	Use OS quiet scheduling	Very high

Stop an App and Prevent Background Activity

Stopping and restricting background activity is the right move when disabling is unavailable or when you only want to reduce resource use. This approach targets immediate CPU/network activity first (Force stop), then controls ongoing background work through battery management policies.

“Force stop immediately halts an app’s processes and background activity until you open it again.”

“Android introduced Doze mode (Android 6.0) to defer background work when the device is idle.”

Step-by-step: Force stop and battery restriction

Go to Settings > Apps and select the app.
Tap Force stop (immediate halt).
Open Battery settings for that app (or Battery usage).
Choose a stricter background option such as Restricted (wording varies by manufacturer).

In practical terms, I use Force stop when an app misbehaves (spins on network, repeatedly wakes the phone, or drains battery during a specific task). Then I switch to a battery restriction so it doesn’t quickly resume background work.

Q: Does Force stop permanently disable the app?
No. It stops the app right now; the app can start again when you open it or when the system decides to run it under allowed conditions.

Why background controls matter

According to Android Developers, Doze mode is designed to reduce background activity during idle periods and was introduced in Android 6.0 (2015). (Android Developers / Doze Mode) This is a key reason why two users can experience very different “battery drain” outcomes based on whether an app is allowed to keep running.

Also, Android’s background execution limits have evolved over releases. According to Android Developers, background start and execution rules tightened substantially from Android 8.0 (API 26) onward. (Android Developers / Background Execution Limits)

Practical “battery-first” checklist

If the app is a nuisance but you still need core functions, start with notifications off.
If the app wakes frequently, do Force stop + Restricted battery.
If it still misbehaves, consider uninstalling (for user apps) or switching to a lighter alternative app.

Re-Enable or Uninstall the App

Re-enabling or uninstalling is how you regain control if disabling didn’t produce the outcome you expected. Android gives you a safety net: most disabled apps can be re-enabled from the same App info page, while user apps can be uninstalled entirely.

“Disabled apps can be re-enabled from the app’s App info screen, restoring the app’s normal availability.”

“Uninstall removes a user-installed app, while Disable pauses it without removing the package.”

How to undo changes

Go back to Settings > Apps.
Select the app.
If it was disabled, tap Enable.

When to uninstall instead of disabling

For apps you installed yourself: Uninstall often makes sense.
For preinstalled/system apps: try Disable first (and re-enable if needed).

Q: What’s the difference between Enable and Uninstall?
Enable returns a disabled app to an active state, while Uninstall permanently removes the app from your device (for user-installed apps).

From my on-device workflow, I treat uninstall as “commitment,” while disable is “reversible experimentation.” If the app is tied to reminders, login status, or background sync, disable is safer than uninstall until you’ve confirmed no critical features rely on it.

Troubleshooting When Disable Won’t Work

When Disable isn’t available or doesn’t produce the expected behavior, the best approach is to confirm the app type and use the correct control surface (notifications or background limits). In many cases, the app is either protected as a critical component or only allows changes to notifications and data usage.

“If an app can’t be disabled, Android still provides control via notification settings and background/battery restrictions.”

“Restarting the device can help clear stale app state when UI actions (like disable) don’t apply immediately.”

Troubleshooting steps that work in the real world

Confirm the app category:
If it’s a system app and the UI doesn’t show Disable, you may only have notifications or background limits.
Check for recent changes:
After a system update or app update, the available toggles can change. Re-check App info.
Restart:
If disabling appears to fail, reboot the phone and try again.
Validate behavior:
After forcing restrictions, watch for changes over a few hours (battery stats and notification behavior update on their own schedule).

Q: Why is the Disable button missing?
It’s usually because the app is protected (critical) or your Android version/device manufacturer doesn’t allow disabling that specific package.

Quick “issue-to-fix” mapping

Disable missing → Use Notifications off + Battery restriction
App still runs → Use Force stop + Restricted battery
Notifications still arrive → Disable the specific notification channels/categories, not just the main toggle
Everything feels broken → Re-enable immediately from App info, then narrow scope (one change at a time)

Disabling an app on Android is straightforward when Settings > Apps > [App Name] > Disable is available, and it’s often the most direct way to stop an app from running—especially for many preinstalled tools. When Disable isn’t offered or feels risky, you can still achieve the practical outcome using notification controls, Force stop, and battery background restrictions, then undo changes anytime by re-enabling from App info or uninstalling user-installed apps. Follow the steps above, make one change at a time, and validate results over the next day for the most reliable outcome—particularly on Android 8.0+ devices where notification channels and background limits can materially affect behavior.

Frequently Asked Questions

How can I disable an app on Android without uninstalling it?

Open **Settings > Apps** (or **Apps & notifications**), then select the app you want to disable. Tap **Disable** (or **Turn off**) to stop the app from running and receiving background activity. If you don’t see Disable, some apps may only allow **Uninstall updates** or **Force stop** instead.

What’s the difference between disabling and uninstalling an app on Android?

**Uninstalling** removes the app completely (or removes updates for system apps if you can’t fully remove them). **Disabling** keeps the app installed but turns it off, which prevents it from launching and reduces background behavior. For preinstalled or system apps, disabling is often the safest option because it restores the app if you later re-enable it.

Why can’t I disable certain apps on my Android phone?

Some apps can’t be disabled because they’re required for system functions or your device’s core features. You may also only have the option to **Force stop**, **Uninstall updates**, or **Clear data** depending on whether it’s a system app or a user-installed one. In those cases, the best workaround is to restrict the app’s permissions and background activity rather than disabling it.

How do I disable an app from the app settings screen on Android 13/14?

Go to **Settings > Apps**, find the app, and open its details page. Choose **Disable** to turn it off, or use **Storage & cache** to **Clear cache** if you’re troubleshooting issues. If the app is still running, check **Battery** settings for **Background restrictions** and ensure **Notifications** are turned off.

Which method is best for disabling an app that keeps showing notifications or running in the background?

Use **Disable** first if available, since it fully stops the app from operating. If disable isn’t an option, turn off **Notifications** for the app, then restrict **Background activity** under **Battery** or **Mobile data** settings. You can also **Force stop** the app and review app permissions to reduce how it behaves after restarts.

📅 Last Updated: July 13, 2026 | Topic: how to disable an app on android | Content verified for accuracy and freshness.