Interactive Troubleshooter

Published: Sep 4, 2026

Android 15 App Permissions Not Saving: Full Fix Guide

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

An interactive root-cause diagnostic tree to resolve Android 15 app permissions not saving and repeated permission prompt loops. Follow structured troubleshooting paths to clear Permission Controller caches, fix Private Space permission isolation, bypass overlay blocks, and apply ADB permission persistence overrides.

Full Diagnostic Tree & Step-by-Step Overview

What specific app permission retention or prompt behavior is your device experiencing on Android 15?

Apps ask for permissions (Camera, Location, Storage) every single time they are launched.
Permissions save initially, but automatically reset or revert after a few hours, days, or reboots.
Permissions fail to save specifically inside Android 15 Private Space or Work Profile.
Permission Manager GUI crashes, toggles freeze, or Package Installer throws continuous error alerts.

When apps repeatedly prompt for permissions upon every launch, what system trigger or screen state occurs during approval?

Permission dialog accepts input, but choice fails to write to system database due to cache lock.
Media or Storage permissions prompt endlessly due to Android 15 Scoped Storage SDK requirements.
A active screen overlay, chat head, or screen filter app is running when tapping 'Allow'.

Clear Permission Controller Storage & Reset System Package State

Solution:

Root Cause: Permission Controller Cache Lock & SQLite Database Corruption

In Android 15, runtime permissions are managed by the com.google.android.permissioncontroller system package and stored in system XML mapping files (/data/system/users/0/runtime-permissions.xml). When this package's internal SQLite database cache becomes locked or corrupted during an OS update, the system accepts user taps on 'Allow' in the UI but fails to commit the grant state to disk. Consequently, the app keeps asking permission on every fresh process spawn.

Step-by-Step Fix:

1Show System Apps in Settings:

Navigate to Settings > Apps > See all apps.

Tap the three-dot menu icon in the upper-right corner and select Show system.

2Locate and Clear Permission Controller Storage:

Scroll down and select Permission Controller (or com.google.android.permissioncontroller).

Tap Force Stop, then tap Storage & cache.

Tap Clear Cache, followed by Clear Storage (or Clear Data).

3Clear Package Installer Cache:

Return to the system apps list, select Package Installer, and tap Storage & cache > Clear Cache.

4Force Reboot Device:

Hold the Power Button + Volume Up for 10 seconds to reboot the device and force Android 15 to rebuild runtime permission database indices.

Reconfigure Granular Media Permissions & Scoped Storage Access

Solution:

Root Cause: Target SDK Mismatch & Scoped Storage Granular Access Enforcement

Android 15 strictly enforces Photo Picker and Granular Media Permissions (READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_AUDIO, and READ_MEDIA_VISUAL_USER_SELECTED). Legacy applications targeting older API levels still request READ_EXTERNAL_STORAGE or WRITE_EXTERNAL_STORAGE. When granted, Android 15's compatibility layer grants a temporary session token rather than a permanent grant, causing the app to prompt for storage access repeatedly upon relaunch.

Step-by-Step Fix:

1Grant All Files Access (For File Managers / Legacy Apps):

Go to Settings > Apps > Special app access.

Tap All files access.

Locate the affected app and toggle Allow access to manage all files to ON.

2Adjust Photo and Video Permissions:

Go to Settings > Apps > See all apps > [Affected App] > Permissions.

Select Photos and videos.

Change selection from Ask every time or Select photos to Allow all.

3Check for App Updates:

Open Google Play Store, search for the app, and update it to a build compiled specifically for Android 15 API 35 standards.

Disable Display Over Apps & Accessibility Overlays Blocking Permission Writes

Solution:

Root Cause: Android 15 Tapjacking Protection & Overlay Input Dropping

To prevent tapjacking malware attacks, Android 15's Window Manager service continuously monitors active touch surfaces. If an app with 'Display over other apps' permission (e.g., messenger chat heads, blue light filters, screen recorders, or sidebars) has an active transparent overlay while the Permission Controller prompt is displayed, Android silently flags the touch event as unverified. The dialog disappears, but the system discards the grant request to protect device security.

Step-by-Step Fix:

1Identify and Disable Screen Overlays:

Go to Settings > Apps > Special app access > Display over other apps.

Temporarily toggle off Allow display over other apps for all listed third-party apps (especially screen filters, messenger bubbles, and gesture tools).

2Disable Active Accessibility Services:

Go to Settings > Accessibility.

Review downloaded accessibility services and temporarily toggle them to Off.

3Re-grant Permission:

Launch the problem application and approve the permission prompt without any overlays running.

4Re-enable Overlays:

Return to Special app access and re-enable required overlay permissions.

Under what operational conditions do saved app permissions silently revert or reset?

Permissions reset automatically after apps remain unused for a few days or weeks.
Permissions reset immediately after device restarts or entering Adaptive Battery saver mode.
Permissions drop across multiple apps following a Google Play System Update or OS patch.

Disable Unused App Permission Auto-Reset & App Hibernation

Solution:

Root Cause: Aggressive App Hibernation & Safety Hub Auto-Revoke Policy

Android 15 features an aggressive App Hibernation system designed to revoke runtime permissions, clear temporary files, and stop background notifications for apps categorized as 'unused'. If an app's background service is flagged by Android's PermissionPolicyService as inactive—or if system clock synchronization shifts—the OS automatically strips sensitive permissions (Location, Camera, Microphone, Contacts) in the background.

Step-by-Step Fix:

1Disable Auto-Reset Per App:

Go to Settings > Apps > See all apps > [Affected App].

Scroll down to the bottom of the App info page.

Toggle off Pause app activity if unused (or Manage app if unused).

2Globally Review Auto-Revoked Permissions:

Navigate to Settings > Security & privacy > Privacy controls > Unused app permissions.

Review the list of hibernated apps and remove critical tools from the auto-revoke queue.

3Disable Auto-Revoke via ADB (Advanced / Global):

Connect your phone to a computer with ADB enabled and run:

bash
     adb shell device_config put privacy auto_revoke_unused_threshold_millis 0

Configure App Battery Usage Limits & OEM Task Killer Exemptions

Solution:

Root Cause: Battery Optimization Daemon Force-Killing State Sync Processes

Aggressive OEM battery management implementations (found on devices from Samsung, Xiaomi, OnePlus, and Pixel) forcibly terminate background framework daemons before PermissionController can flush in-memory permission state transitions to non-volatile storage during device shutdown or low-battery events. When the phone reboots, it restores the last known good XML snapshot, reverting recent permission changes.

Step-by-Step Fix:

1Set App Battery Usage to Unrestricted:

Go to Settings > Apps > See all apps > [Affected App] > App battery usage.

Change setting from Optimized to Unrestricted.

2Exempt Permission Controller from Battery Saver:

Go to Settings > Apps > Special app access > Energy optimization (or Battery optimization).

Switch filter to All apps, locate Permission Controller, and set to Don't optimize.

3Disable Extreme Battery Saver Automations:

Go to Settings > Battery > Battery Saver and ensure schedule triggers do not aggressively freeze background system services.

Repair Mainline Permission Module State & Flush Google Play Services Data

Solution:

Root Cause: Google Play System Update (Project Mainline) Module Mismatch

In Android 15, the Permission Controller is delivered as an updatable Project Mainline apex module (com.google.android.permission). When a background Google Play System Update applies a patch to the Permission module without cleanly migrating local policy manifests, package signature mismatches cause the runtime system to fall back to default restrictive security templates.

Step-by-Step Fix:

1Check for Google Play System Updates:

Go to Settings > Security & privacy > System & updates.

Tap Google Play system update and install any pending updates, then reboot.

2Clear Google Play Services Storage:

Go to Settings > Apps > See all apps > Google Play services > Storage & cache.

Tap Clear Cache, then tap Manage space and select Clear All Data.

3Uninstall Permission Module Updates (Fallback):

In Settings > Apps > See all apps > Permission Controller, tap the three-dot menu icon in the upper right and select Uninstall updates (if available) to restore stable factory module defaults.

In which isolated container or profile configuration is the permission saving failure occurring?

Apps locked inside Android 15 Private Space lose permissions when Private Space locks.
Work Profile apps fail to retain permissions due to IT Administrator / MDM restriction policies.
Permissions fail across multiple guest or secondary user accounts on the same device.

Adjust Android 15 Private Space Auto-Lock & Sandboxed Permission Rules

Solution:

Root Cause: Private Space Security Isolation & User Profile Unloading

Android 15 introduces 'Private Space', which operates as a distinct sandboxed user profile (typically assigned User ID 10+). When Private Space locks, the OS stops the underlying profile process tree to conserve memory and preserve privacy. If an app inside Private Space requests a permission while the space is transitioning to a locked state, the security sandbox aborts file-write operations to the Private Space runtime-permissions.xml container.

Step-by-Step Fix:

1Unlock Private Space First:

Open the App Drawer, scroll to the bottom, tap Private, and authenticate with your PIN/fingerprint.

2Adjust Private Space Auto-Lock Settings:

Go to Settings > Security & privacy > Private Space.

Tap Lock Private Space and change the setting from Every time phone locks to On device restart temporarily while configuring permissions.

3Set Permissions While Unlocked:

Open Settings from *within* the unlocked Private Space profile (or access Private Space App Info directly).

Configure required permissions while Private Space remains actively unlocked.

4Re-lock and Test:

Re-lock Private Space and verify permissions remain persistent across subsequent unlocks.

Override Work Profile MDM Permission Policies & Grant Rules

Solution:

Root Cause: Enterprise Mobility Management (EMM / MDM) Policy Enforcement

Devices with an active Work Profile (managed via Google Workspace, Microsoft Intune, or Knox) inherit DevicePolicyManager runtime permission policies set by network administrators. If the enterprise policy is set to PERMISSION_POLICY_AUTO_DENY or PERMISSION_POLICY_PROMPT without persistent state retention, user runtime selections in the work profile are overridden by policy sync daemons every few minutes.

Step-by-Step Fix:

1Check Work Profile Policy Restrictions:

Go to Settings > Security & privacy > Device admin apps and inspect active work policy agents.

2Grant Permissions via Work Settings Panel:

Open Settings > Work > Apps, select the work app, and configure permissions under the dedicated Work tab.

3Inspect Enterprise Restrictions via ADB:

Verify active DPC restrictions using ADB shell commands:

bash
     adb shell dpm list-owners

4Contact IT Helpdesk:

If enterprise restrictions actively enforce auto-deny, ask your system administrator to update the app's runtime permission policy to Auto-Grant inside the EMM management console.

Resolve Multi-User Profile ID Permission Table Conflicts via ADB

Solution:

Root Cause: Multi-User Profile ID Mismatch in Package Database

When multiple user profiles (Owner User 0, Work User 10, Guest User 11) exist on an Android 15 device, each profile maintains an isolated permission XML mapping file in /data/system/users/[user_id]/runtime-permissions.xml. If an app is installed across multiple user profiles and updated in one profile while suspended in another, the Package Manager service can encounter cross-user ID write lockouts.

Step-by-Step Fix:

1Identify Target App Package Name:

Locate the exact package name (e.g., com.example.app).

2Grant Permission Explicitly Per User ID via ADB:

Connect phone to PC, open terminal, and issue user-specific grant commands:

bash
     # For Primary Owner Profile (User 0)
     adb shell pm grant --user 0 com.example.app android.permission.CAMERA
     adb shell pm grant --user 0 com.example.app android.permission.ACCESS_FINE_LOCATION
     
     # For Secondary / Private Space / Work Profile (Replace 10 with actual User ID)
     adb shell pm grant --user 10 com.example.app android.permission.CAMERA

3Verify Active Grants:

Run adb shell dumpsys package com.example.app to confirm permissions are marked as GRANTED_BY_USER.

What error or system behavior occurs when attempting to modify permissions in Settings?

Settings app crashes or displays 'Package Installer keeps stopping' error popup.
Permission toggles in Settings are greyed out or fail to move when tapped.
System-wide permission failures across all installed apps following an interrupted Android 15 OTA update.

Reset Package Installer & Permission Controller App Binaries

Solution:

Root Cause: Unhandled Exception in System Permission Manager UI

When accessing the Permission Manager settings menu, the OS invokes com.google.android.permissioncontroller alongside com.android.packageinstaller. If corrupted string resources or broken app manifest entries exist in a recently installed APK, parsing those parameters triggers a NullPointerException in the Permission Manager UI, causing the crash screen.

Step-by-Step Fix:

1Force Stop and Reset Settings App:

Go to Settings > Apps > See all apps > Settings > Force Stop.

Tap Storage & cache > Clear Cache.

2Reset App Preferences Globally:

Go to Settings > System > Reset options.

Tap Reset app preferences.

*Note:* This resets all disabled apps, background restriction settings, and default app choices without deleting user personal files.

3Reboot to Safe Mode to Identify Malicious Apps:

Press and hold the Power Button, then press and hold the Restart icon on screen until the Reboot to Safe Mode prompt appears. Tap OK.

If permissions save normally in Safe Mode, uninstall recently downloaded third-party apps that may contain malformed manifests.

Bypass Greyed-Out Toggles via ADB Package Manager Commands

Solution:

Root Cause: Restricted Settings Policy Flag & Restricted Permissions Enforcement

Android 15 automatically greys out permission toggles and enforces a 'Restricted Setting' block for applications sideloaded via web browsers or third-party APK sources (non-Play Store sources) that request high-risk permissions (e.g., Accessibility, Notification Listener, SMS). For complete developer details on Android permission architecture, consult the Android Developer Official Documentation on Permissions.

Step-by-Step Fix:

1Allow Restricted Settings via App Info:

Go to Settings > Apps > See all apps > [Sideloaded App].

Tap the three-dot menu in the upper-right corner and select Allow restricted settings.

Authenticate with your device PIN or fingerprint.

2Manually Force-Grant Permissions via ADB Shell:

Connect device to PC with USB Debugging enabled, open terminal, and run:

bash
     adb shell pm grant <package_name> android.permission.CAMERA
     adb shell pm grant <package_name> android.permission.RECORD_AUDIO
     adb shell pm grant <package_name> android.permission.ACCESS_FINE_LOCATION
     adb shell pm grant <package_name> android.permission.READ_MEDIA_IMAGES

3Verify Grant State:

Relaunch the application; the required permission will be active and saved directly in the system policy engine.

Reset System Permission Tables & Flash Factory Image via Recovery Mode

Solution:

Root Cause: System Partition File System Corruption & Broken Manifest Tables

If an over-the-air (OTA) update to Android 15 is interrupted during the post-install payload execution (system_server package optimization phase), the core system package database (/data/system/packages.xml) can become permanently out of sync with the hardware security module (Keystore/Tee). This corrupts runtime permission state tracking across the entire operating system.

Step-by-Step Fix:

1Reset Permission Table via ADB (Non-Destructive):

Run the following command in ADB Shell to force Android to rebuild permission tables from base APK manifests:

bash
     adb shell pm reset-permissions

2Reboot to Recovery Mode & Wipe Cache:

Turn off the phone completely.

Hold Power + Volume Down until the Fastboot/Recovery screen appears.

Navigate using Volume buttons to select Recovery Mode.

Select Wipe Cache Partition (if available on your OEM software) and reboot.

3Perform Factory Reset (Ultimate Resolution):

If permission tables remain broken system-wide, back up personal files to cloud storage, boot into Recovery Mode, select Wipe data / Factory reset, and set up the device as a fresh Android 15 installation.

Related Diagnostic Guides

Windows Update Error 0x80070002 Missing Files Diagnostic Guide

System Restore Failed 0x80070005 Antivirus Conflict Tree

Windows Photo Viewer Not Showing Thumbnails: Codec Diagnostic

Safe Mode Password Not Working With Microsoft Account Fix

Clipboard History Not Working Windows 11: Sync Service Tree

Subscribe to StepDiag

Embed Guide on Your Website