How to Enable and Manage Android’s Auto‑Reset App Permissions for Better Privacy

Many Android users discover that an app suddenly stops working after a system update or after they reinstall it. The usual culprit is a lingering permission that the app no longer needs—or that you no longer want it to have. Starting with Android 11, Google introduced an auto‑reset permission system that automatically revokes dangerous permissions from apps you haven’t used for three months. This guide shows you how to enable the feature, verify which apps were affected, and safely manage any side‑effects.

Why Android Auto‑Reset Permissions Matter

Android categorises permissions into normal (granted at install) and dangerous (e.g., location, microphone, camera). Dangerous permissions give apps access to personal data or hardware that can be abused. If you install a weather app once and never open it again, its location permission remains active forever—unless you manually revoke it.

The auto‑reset feature works like a privacy‑clean‑up timer: after 90 days of inactivity, Android revokes all dangerous permissions for that app. When you open the app again, it will ask for the permissions it truly needs, giving you a chance to reconsider.

Before You Start

• Android version: Auto‑reset is built into Android 11 and later. If your device runs Android 10 or older, the feature is unavailable.
• Backup your data: Revoking permissions does not delete app data, but some apps (e.g., banking apps) may refuse to start until you re‑grant access. Make sure you remember any critical credentials.
• Charge your phone: The process is quick, but it’s best to have at least 30 % battery or be plugged in.
• Wi‑Fi connection: Not required for the reset itself, but you’ll likely need the internet to re‑grant permissions later.

Enabling Auto‑Reset Permissions

Once enabled, Android will run a background job each night to evaluate app usage. No further action is required unless you want to manually reset a specific app.

How to Manually Reset Permissions for a Single App

Sometimes you may want to reset permissions immediately—perhaps after selling a device or before handing it to a friend. Here’s how:

When you open the app again, Android will present fresh permission dialogs, just as it would after a fresh install.

Checking Which Apps Have Been Auto‑Reset

Android does not provide a single list of reset apps, but you can infer the status by looking at the permission state of each app.

For a quicker overview, you can use the ADB command adb shell pm list permissions -g -d on a PC, but the on‑device method works for anyone without a computer.

Common Pitfalls and How to Fix Them

1. Apps Crash Immediately After Reset

Some apps assume the permission is always present and do not handle the denial gracefully. If an app crashes on launch:

• Open the app’s Permissions screen (Settings → Apps → App name → Permissions).
• Re‑grant the permission the app requests (usually shown in a pop‑up when you try again).
• If the app still misbehaves, look for an in‑app setting that lets you reset the app’s data, or uninstall and reinstall the app.

2. Auto‑Reset Not Triggering After 90 Days

Reasons this can happen:

• Battery optimization: Some OEMs disable background jobs for power‑saving. Open Settings → Battery → Battery optimization, find PackageInstaller and set it to Not optimized.
• Work profile: Apps installed in a corporate work profile are excluded from auto‑reset. You’ll need to manage permissions manually inside the work profile.
• App usage tracking disabled: If you turned off Usage access for Settings, Android can’t determine inactivity. Re‑enable it via Settings → Apps → Special app access → Usage access → Settings → Allow.

3. Permission Reset on a Device with Multiple Users

Android treats each user (including guest) separately. Enabling auto‑reset for the primary user does not affect secondary users. Switch to the other user and repeat the enabling steps if needed.

Advanced: Using ADB to Verify Auto‑Reset Status

For power users who already have adb installed, you can query the reset timestamp directly:

adb shell dumpsys package | grep -i "autoReset"

This command lists packages with a pending auto‑reset and the time remaining. It’s useful when you want to confirm that a particular app is scheduled for reset without waiting for the nightly job.

When Not to Use Auto‑Reset

• Critical security apps: Banking, password managers, and two‑factor authentication apps often need constant access to sensors (camera for QR codes, microphone for voice verification). Revoking permissions may interrupt their workflow.
• Accessibility services: Apps that provide screen readers or custom keyboards rely on accessibility permissions that are not covered by auto‑reset, but they may still be affected by other power‑saving settings.
• Devices used as kiosks: If you lock a device to a single app (e.g., a point‑of‑sale terminal), you likely want all permissions to stay granted permanently.

In these scenarios, keep auto‑reset enabled but monitor the affected apps and re‑grant permissions promptly.

Alternative Approaches

If you prefer more granular control, consider using a third‑party permission manager such as AppOpsX (requires root) or the built‑in Permission manager to manually deny permissions you never use. The advantage of the native auto‑reset is that it works without root and respects the system’s usage statistics, making it a low‑maintenance solution.

Quick Checklist

• Device runs Android 11+.
• Enable auto‑reset via Settings → Privacy → Permission manager.
• Verify the switch is on and note the 90‑day schedule.
• Periodically review permissions in each category to spot any unexpected denials.
• If an app misbehaves, re‑grant the needed permission or reinstall the app.
• Check battery‑optimization and usage‑access settings if resets don’t happen.

By following this guide, you’ll let Android do the heavy lifting of cleaning up unused permissions while staying in control of the few apps that truly need access. The result is a quieter, more private device that respects your data without constant manual tweaking.