Allow accessing /Android/data and /Android/obb with root

[Aga-C]

Checklist

• [x] I can reproduce the bug with the latest version.
• [x] I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
• [x] I have read the FAQ and my problem isn't listed.
• [x] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• [x] This issue contains only one bug.
• [x] I have read and understood the contribution guidelines.

Describe the bug Use this folder button is inactive, hence /Android/data and /Android/obb can't be accessed due to missing Storage permission.

To Reproduce Steps to reproduce the behavior:

1. Open the app.
2. Go to /Android/data or /Android/obb.
3. After the confirmation dialog appeared (about allowing the app accessing the selected storage on the next screen), tap OK.

Expected behavior Use this folder button at the bottom of the next screen should be active, and after tapping it, the access to the selected storage should be granted.

Device info (please complete the following information):

• Model: OnePlus 9 Pro
• OS: Android 13
• Version 1.0.0

Additional context

• My phone is not rooted.
• I can access both folders via Total Commander app.

[naveensingh]

The restriction was introduced in Android 11: https://developer.android.com/about/versions/11/privacy/storage#other-apps-data

People found a workaround but it was patched in Android 13. Resorting to workarounds is not a good idea if those directories are supposed to be invisible even to apps with MANAGE_EXTERNAL_STORAGE permission.

I think the current flow is confusing, we should provide the user with clarification. Probably a static text like "Due to system restrictions, this directory is inaccessible."

[naveensingh]

I can access both folders via Total Commander app.

Which version do you have?

[Aga-C]

Which version do you have?

3.42d

[inson1]

https://github.com/SimpleMobileTools/Simple-File-Manager/issues/685

[BioRider17]

I think we should do as material files, and only allow access with root. the work around carried over from simple file manager doesn't work anyway.

[AnotherJavaUser]

I have Android 12 and from MiXplorer I can access Data and OBB. It would be nice to try to replicate your solution, and for Android 13+ just the warning sign.

[gargamel17]

I have Android 12 and from MiXplorer I can access Data and OBB. It would be nice to try to replicate your solution, and for Android 13+ just the warning sign.

Mix is also working fine under 13, without root

[luewolf]

While access to /Android/data or /Android/obb is restricted, access can be granted directly to /Android/data/<PACKAGE_NAME> or /Android/obb/<PACKAGE_NAME> (or at least, that's what I heard).

So to work around the fix to the workaround, the file manager could make it look like it is accessing /Android/data or /Android/obb and displaying their contents when it actually does this:

1. Check which apps are installed on the system.
2. For each app, check whether the directory /Android/data/<PACKAGE_NAME> (if inside /Android/data) or /Android/obb/<PACKAGE_NAME> (if inside /Android/obb) exists. If so, display the directory.
3. When the user clicks on one of the directories, ask for permission to access that directory.

That's probably what Total Commander is doing.

Versions of Android where the old workaround still works should ideally continue to use the current logic.

[MinekPo1]

Note that the old logic is also broken, unsure why exactly, but when trying to grant SAF permissions, Files opens in the user directory instead of /Android/data or /Android/obb. Since these two directories are hidden when attempting to grant SAF permissions, this makes accessing them not possible. This seems to be a bug partially inherited from SMT as SMT file manager opens /Android/data for both /Android/data and /Android/obb.

Might need a separate issue though, as this one is more focused on issues related to Android 13.

[TheShanMan]

I'd like to see this fixed at least for root. Sucks that simple and now fossify have claimed root support but access to the data folder has been broken.

[gargamel17]

I have Android 12 and from MiXplorer I can access Data and OBB. It would be nice to try to replicate your solution, and for Android 13+ just the warning sign.

Mix is also working fine under 13, without root

With android 14 it still works perfectly

[naveensingh]

As leuwolf mentioned above, MiXplorer is also constructing the data, obb folders using the list of installed apps but they are not accessible on Android 11, 12, 13, and 14. I couldn't access the contents of Android/data/any.package.name/* and Android/obb/any.package.name/* because the system SAF dialog (launched by MiXplorer) doesn't show the data and obb folders:

I got the same results with Total Commander.

[naveensingh]

I found this: https://issuetracker.google.com/issues/256669329

[notIkibo]

Android 14, is there really no way to access data or obb?

[tswistak]

Wouldn't it be possible by adding Shizuku support to the app?

[naveensingh]

As a workaround, the app could show a placeholder message like "Due to system restrictions, this folder is not available" when users try to open inaccessible folders like data or obb. There could also be a button to open the same folder in system file manager or a button to "Request access" on older versions where it is possible with SAF permissions.

[naveensingh]

All these SAF workarounds no longer work (even on Android 11) due to Google's mainline updates which also patches the DocumentsUI app (the system file picker). The simple solution I have found on previous versions is to downgrade the DocumentsUI app but on recent Android versions, even that won't help since the preinstalled system version is already patched.

Fossify File Manager will, for now, just offer an option to browse these folders in DocumentsUI. Later, I'll see if I can find the exact DocumentUI version code where they fixed the bug to continue using the workaround when you have a downgraded version.