file-manager | A java/swing basic File Manager | Application Framework library

It is a very known feature on modern desktop OSs to be able to handle files, allowing the user to open them from the file-manager and other apps, as "file assosiation" configuration.

So far, it wasn't such a convenient thing on Android, for both users and developers, to set an association of a file type.

Up to Android API 30 (Android 11, AKA Android R), you had to use some weird workarounds, especially if the file isn't a known one.

Example for "xyz" :

I am trying to play videos in VLC player via the python module "python-vlc" and the video player disappears immediately after launching.

Here is the code:

I'm trying to use Syncfusion Vue FileManager with NuxtJS.

I try to run the ready code in Kivy cite about MDFileManager component: https://kivymd.readthedocs.io/en/latest/components/file-manager/index.html

However I obtain an error message due to this line "preview=True,"

line 36, in __init__preview=True,

Because when I delete it, I can run the code without any error. But this result is not enough for me. I need to display all images in a path as a list.

I am trying to install the Vue Filemanager to my package.json. However, when I try to install the package using npm install and npm run dev I get this error:

I would like to read Android/data so I can extract documents for backup purposes. Android 11 has changes that prohibit/limit this, but is it still possible? I don't want to use the legacy-approach (if possible).

According to this Manage all files on a storage device which talks about the MANAGE_EXTERNAL_STORAGE permission it seems Google claims it should now be impossible (at least with this method):

Apps that are granted this permission still cannot access the app-specific directories that belong to other apps because these directories appear as subdirectories of Android/data/ on a storage volume.

https://developer.android.com/training/data-storage/manage-all-files https://developer.android.com/about/versions/11/privacy/storage#other-apps-data

Here storage#other-apps-data Google also says that apps can no longer access other apps Android/data

Access to app-specific directories on external storage On Android 11, apps can no longer access files in any other app's dedicated, app-specific directory within external storage.

Here on stackoveflow Thoryia shows us how to ask for the permission.

But can we use it (or any other method) to read those forbidden other app-data folders, Android/data/* ?

The Android app 'Total Commander' does it (on Android 11), and it seems to be using the StorageAccessFramework Intent Intent.ACTION_OPEN_DOCUMENT_TREE to access the files (a guess based on the gui that pops up), but I havn't managed to figure out how to get that working either. Its possible Total Commander use a legacy-approach.

Pr request I've screenshots of Total Comander (TC) here on my OneDrive.

I strongly suspect TC just uses the target-29 access method, I found a list of its permissions here but cannot find which version it targets: Aptoide: TC v3.21

I am using the package https://github.com/alexusmai/laravel-file-manager which comes with either a pre-compiled js file or you may use the vue-component directly through npm from https://github.com/alexusmai/vue-laravel-file-manager.

However, in both variants, the frontend is not modifiable. I am using the Laravel file-manager in my application and I would like to make customization's to the vue files to change the front-end.

What I tried so far:

• copied content of https://github.com/alexusmai/vue-laravel-file-manager/tree/master/src into /resources/assets/js/file-manager

Then I created a file_manager.js like this:

i want to create electron app that have toggle developer tools feature like vscode, from vscode you can check from menu: help > toggle developer tools i'm trying to create the same tools that can accessed from electron menubar/navbar but the program show error below:

There are various storage restrictions on Android 10 and 11, which also includes a new permission (MANAGE_EXTERNAL_STORAGE) to access all files (yet it doesn't allow access to really all files ) while the previous storage permission got reduced to grant access just to media files :

1. Apps can reach the "media" sub folder freely.
2. Apps can never reach "data" sub folder and especially the content.
3. For "obb" folder, if the app was allowed to install apps, it can reach it (to copy files to there). Otherwise it can't.
4. Using USB or root, you could still reach them, and as an end user you can reach them via the built-in file-manager app "Files".

I've noticed an app that somehow overcome this limitation (here) called "X-plore": Once you enter "Android/data" folder, it asks you to grant access to it (directly using SAF, somehow), and when you grant it, you can access everything in all folders of "Android" folder.

This means there might still be a way to reach it, but problem is that I couldn't make a sample that does the same, for some reason.

It seems this app targets API 29 (Android 10), and that it doesn't use the new permission yet, and that it has the flag requestLegacyExternalStorage. I don't know if the same trick they use will work when targeting API 30, but I can say that on my case, running on Pixel 4 with Android 11, it works fine.

So I tried to do the same:

1. I made a sample POC that targets Android API 29, has storage permissions (of all kinds) granted, including the legacy flag.

2. I tried to request access directly to "Android" folder (based on here), which sadly didn't work as it goes to some reason (kept going to DCIM folder, no idea why) :