Android Storage Permissions Explained — Android 10 to 14

Android's storage permission model has changed dramatically across recent versions, and each update shifts what file managers can and cannot access. If you have ever opened a file manager only to find folders empty, paths inaccessible, or permission dialogs popping up repeatedly, you are experiencing the real-world effects of these policy changes. Here is exactly what changed in each version and how to configure AnExplorer to maintain full filesystem access.

The Short Answer

On Android 11 and above, go to Settings → Apps → AnExplorer → Permissions → Files and media → Allow management of all files. This grants the MANAGE_EXTERNAL_STORAGE permission that restores full browsing capability. Without it, file managers are sandboxed like every other app.

Android Storage Permission Timeline

Android 9 and Below — The Open Era

Before Android 10, storage was simple. Apps requested the READ_EXTERNAL_STORAGE or WRITE_EXTERNAL_STORAGE permission at install or runtime, and once granted, they had complete read/write access to the entire shared storage — every folder, every file type, every path. File managers worked exactly as you would expect a desktop file explorer to work.

This was powerful but created security concerns. Any app with storage permission could read your photos, documents, downloads, and other apps' exported files without restriction.

Android 10 — Scoped Storage Introduced (Optional)

Android 10 introduced scoped storage as a concept but made it opt-in for developers. Apps targeting API 29 could add requestLegacyExternalStorage=true in their manifest to maintain the old behavior. Most file managers used this flag, so users saw no practical difference.

Key changes introduced:

• The concept of "app-specific external storage" (Android/data/[package]/) became formally sandboxed
• MediaStore API became the recommended way to access media files
• The Storage Access Framework (SAF) gained importance for document access
• Direct file path access was technically deprecated but still worked with the legacy flag

Android 11 — Scoped Storage Enforced

Android 11 was the breaking point. The requestLegacyExternalStorage flag stopped working for apps targeting API 30+. Every app was now scoped by default. However, Google recognized that file managers, backup tools, and antivirus apps genuinely need broad access, so they created a new permission:

MANAGE_EXTERNAL_STORAGE — the "All Files Access" permission. This is a special permission that:

• Must be declared in the app manifest
• Requires the user to manually navigate to Settings to grant it (cannot be granted via a simple runtime dialog)
• Must be justified to Google during Play Store review
• Grants access to all of shared storage EXCEPT Android/data/ and Android/obb/ directories

When AnExplorer requests this permission, you see a system screen asking you to toggle "Allow management of all files." This is not a bug or overreach — it is the only way a file manager can function properly on Android 11+.

Android 12 — Minor Refinements

Android 12 did not dramatically change storage permissions but added:

• Nearby device permissions affecting file transfer features
• Slight changes to how the photo picker works
• Better enforcement of package visibility rules (apps cannot see what other apps are installed without declaring queries)

For file manager functionality, Android 12 behaved identically to Android 11.

Android 13 — Granular Media Permissions

Android 13 split the old READ_EXTERNAL_STORAGE into three separate permissions:

• READ_MEDIA_IMAGES — access photos and images
• READ_MEDIA_VIDEO — access video files
• READ_MEDIA_AUDIO — access music and audio files

Apps now request only the media types they actually need. A music player asks for audio only; a photo editor asks for images only. File managers with All Files Access bypass these granular permissions entirely since MANAGE_EXTERNAL_STORAGE already covers everything.

Android 13 also fully blocked third-party access to Android/data/ via the Storage Access Framework. Previously, you could use SAF to grant folder access to Android/data/ — that workaround was closed.

Android 14 — Selected Photos Access

Android 14 introduced the most user-facing change: when an app requests photo access, users can now choose "Select photos and videos" instead of granting access to all media. This means:

• The app only sees the specific files the user picked
• The user can modify their selection later in Settings
• Apps must handle partial access gracefully

For file managers with All Files Access, this does not apply — MANAGE_EXTERNAL_STORAGE still provides full media visibility. But if you have not granted All Files Access, you may find AnExplorer can only see files you have explicitly selected.

Android 14 also introduced:

• Credential-based access for enterprise-managed files
• Photo picker improvements with cloud provider integration
• Stricter restrictions on background file access

How the Storage Access Framework (SAF) Works

When a file manager lacks All Files Access, the Storage Access Framework becomes the fallback mechanism. SAF works through system-level document pickers:

1. The app calls ACTION_OPEN_DOCUMENT_TREE to request access to a folder
2. Android shows a system file picker where you navigate to the desired folder
3. You tap "Use this folder" and confirm with "Allow"
4. The app receives a persistent URI grant for that specific folder and all its contents
5. This grant survives app restarts and phone reboots

SAF grants are powerful but tedious — you must manually grant each folder separately. AnExplorer uses SAF as a fallback when All Files Access is unavailable or when accessing specific protected paths.

SAF Limitations

• Cannot grant access to internal storage root on Android 13+
• Cannot access Android/data/ on Android 13+
• Cannot access Android/obb/ on Android 13+
• Performance is significantly slower than direct file access (operations go through a content provider)
• Some operations (like recursive folder operations) are much slower via SAF

Configuring AnExplorer for Maximum Access

For the best experience across all Android versions:

1. Grant All Files Access: Settings → Apps → AnExplorer → Permissions → Files and media → Allow management of all files
2. Grant notification permission (Android 13+): Required for showing transfer progress
3. Disable battery optimization: Settings → Apps → AnExplorer → Battery → Unrestricted (prevents the OS from killing background operations)
4. Grant SAF access for Android/data (Android 11-12 only): When AnExplorer prompts for folder access to Android/data, tap "Use this folder" → "Allow"

What Remains Inaccessible Without Root

Even with All Files Access granted, certain paths remain blocked by Android's security model:

Troubleshooting Permission Issues

"Permission denied" despite All Files Access being granted

1. Force-stop AnExplorer and reopen it
2. Revoke the permission and re-grant it
3. Check that you granted "All files" and not just "Media only" (some devices show both options)
4. Restart your phone — some permission grants require a reboot to take effect

Permission keeps resetting after a few days

Android 12+ automatically revokes permissions from apps you have not used recently (usually 3 months). To prevent this:

• Settings → Apps → AnExplorer → Permissions → toggle off "Remove permissions if app isn't used"
• Or simply open AnExplorer occasionally to keep it considered "active"

App shows empty folders despite having permission

This usually indicates the app is reading from a cached/stale directory listing. Pull down to refresh, or navigate out and back into the folder. If the issue persists, clear AnExplorer's cache (Settings → Apps → AnExplorer → Storage → Clear Cache).

Related Guides

• Android 14 Storage Changes — detailed breakdown of latest restrictions
• File Manager Not Opening — fix crashes related to permission resets
• Internal vs External Storage — understand Android's storage architecture
• Can't Delete Files — permission-related deletion failures