-
-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android 12: Cannot setup storage access framework #639
Comments
Also note the folder exists as I have Solid Explorer and can access them. |
Hooe this gets resolved soon. I'm facing the same issue |
Hopefully this helps as well. |
I also have this error on two Android 12 devices. |
Is the issue accessing Currently it looks like Samsung's latest OneUI update backported some Android 13 changes to Android 12.
Hm will look into that, if Solid Explorer has found a workaround we could do that too. It's possible they are faking access though, or "simulating" it. You can guess some of the content and display it as "access". Can Solid Explorer write to |
Boths. The problems occurs on my Motorola smartphone and Lenovo tablet. |
I have no issues accessing Android/data, only Android/obb. Android/data was accessible right away and I verified by clearing app data and rechecking. Screenshot_20230921-202627_SD Maid SE Solid Explorer can add/edit/delete from both Android/data and Android/obb. |
Android 12 (A11+), NO root(!), MIUI 14, Redme Note 9S, global, stock. |
I followed the recommendations, the result was zero. Documents from system applications in A11+ are excluded. |
Samsung OneUi 3.1 Android 11 same problem. Only "media" folder shows up |
@demetry14 @Pawwwle @KryptoKing93 Hi, please rest assured that we (me and possibly the community with Darken) are currently looking into how other apps got around this. This issue has been present since Samsung's July 2023 Security patch because they brought the restrictions from Android 13 to Android 12. |
…date of the `Files` app Google seems to have backported some Android 14 changes with tighter restrictions on access to `Android/data` The previous `EXTRA_INITIAL_URI` argument trick is no longer working. Also see: https://cs.android.com/android/platform/superproject/main/+/main:packages/apps/DocumentsUI/src/com/android/documentsui/picker/ActionHandler.java;l=84;bpv=1;bpt=0;drc=901f1d6044aade190bb943ccc18d26244132648e;dlc=306a2b606a1f01498d2d83a1d8362962f114e6e8 There are now 3 states to this for Android 12 users: * You have the original "Files" app (API-level 31, e.g. `aml_doc_310851020 (310851020)`) that came with Android 12, then you can just grant access as expected * You have the latest "Files" app (API-level 34 or later, e.g. `14-10492947 (340916000)`), then you can't grant access * You have a version in between those two, then you should be able to grant access after this code change In any case, a possible workaround to this is uninstalling the application updates. You can uninstall the update of the `Files` app, then complete the setup in SD Maid. Updating the `Files` app again won't break the granted permission. * Open device settings * Go to "Apps & notifications" or "Application Manager" * Find the `Files` system app * Tap on the three-dot menu, usually on the top right corner * Choose "Uninstall updates" or `adb uninstall com.google.android.documentsui` Closes #639
TL;DR: Google Play updated the Workaround: Uninstall the update to the See #703 for a detailed explanation. |
…date of the `Files` app Google seems to have backported some Android 14 changes with tighter restrictions on access to `Android/data` The previous `EXTRA_INITIAL_URI` argument trick is no longer working. Also see: https://cs.android.com/android/platform/superproject/main/+/main:packages/apps/DocumentsUI/src/com/android/documentsui/picker/ActionHandler.java;l=84;bpv=1;bpt=0;drc=901f1d6044aade190bb943ccc18d26244132648e;dlc=306a2b606a1f01498d2d83a1d8362962f114e6e8 There are now 3 states to this for Android 12 users: * You have the original "Files" app (API-level 31, e.g. `aml_doc_310851020 (310851020)`) that came with Android 12, then you can just grant access as expected * You have the latest "Files" app (API-level 34 or later, e.g. `14-10492947 (340916000)`), then you can't grant access * You have a version in between those two, then you should be able to grant access after this code change In any case, a possible workaround to this is uninstalling the application updates. You can uninstall the update of the `Files` app, then complete the setup in SD Maid. Updating the `Files` app again won't break the granted permission. * Open device settings * Go to "Apps & notifications" or "Application Manager" * Find the `Files` system app * Tap on the three-dot menu, usually on the top right corner * Choose "Uninstall updates" or `adb uninstall com.google.android.documentsui` Closes #639
Cannot access Android/obb when attempting to setup storage access framework on Android 12. I read that was an issue on Android 13, but I am on a Galaxy S10 and they max out at Android 12.
Click setup > Grant Access > Android > "all you see is media"
Screenshot_20230919-010126_SD Maid SE
Screenshot_20230919-010113_Files
The text was updated successfully, but these errors were encountered: