Alternative method of accessing data and obb

So I use material files and unable to access Android/data and Android/obb. But today another redditor told me he was able to get it to work with Mixplorer. I kinda figured out how it did this. Here is the recording:

https://user-images.githubusercontent.com/64138578/211184012-80819449-ad81-4890-a3e1-87eca17c2833.mp4

You can see that I can have access to individual dirs in Android/data and Android/obb, but not Android/data and Android/obb,

The problem is that Android blocks RW access to Android/data and Android/obb, but not RW access to Android/data/* and Android/obb/*. So material files can access Android/data/app.revanced.manager.flutter, for example, but not Android/data.

So we just need to ask SAF to give access to Android/data/<package_name> and Android/obb/<package_name>. But how can we get the package names? You can see that Mixplorer asks for the permission for listing the installed apps, thats how it gets the name of installed packages. You can also see I allowed it to query installed packages twice, possibily for Android/data and Android/obb respectively.

I hope Material files can also implement this.

Mixplorer
Download Mixplorer

In the meantime, you could use material files to add another storage to Android/data and Android/obb by asking Mixplorer to grant the permission via SAF.

No repository files or tests are named. Start by tracing the existing SAF permission flow and the installed-app/package-query behavior described in the issue. Done means Material Files can request access to package-specific Android/data and Android/obb directories.