Repository navigation
Files (com.android.documentsui) crashes and Android stops working properly #290
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.2.0 and all newer
Affected Android/Custom ROM version
Android 14
Affected device model
Xperia 10 VII
How did you install the app?
GitHub releases
Steps to reproduce the bug
Last good working version without bug -> 1.1.0
I install the app and then I convert it to system app by moving it to /product/app/
I do that with all fossify apps and they work fine. I'm root (Magisk) and I have a RW super partiton.
Expected behavior
Files (com.android.documentsui) is opened by apps to grant write permissions and set download / upload / import / export paths.
When Fossify File manager is installed and working (ver 1.1), Files (com.android.documentsui) shows a Fossify File manager icon to click as an option.
Actual behavior
Files (com.android.documentsui) crashes when Fossify file manager version is 1.2 or newer. And all apps that need it don't work properly (no way to choose folder or use a folder already set)
Android stops working properly, no alarms / events / updates for many apps, including system apps. It seems Files (com.android.documentsui) access permissions are denied.
Screenshots/Screen recordings
No response
Additional information
No response
Activity
naveensingh commentedon Oct 17, 2025
This is caused by #213 as mentioned in #213 (comment). I need to think on this, but a choice has to be made here because we can either have #213 or fix this.
Are you able to reproduce this when you do the same with Material Files?
mat999io commentedon Oct 18, 2025
I've using Mixplorer without problem for many years. The icon to select Mixplorer in Files (com.android.documentsui) works in every version (both android and mixplorer). I also have a Termux icon showing in Files (com.android.documentsui).
This is not a minor bug. Android does not work any more. Once Files (com.android.documentsui) stops working, storage access does not work, and the apps are dead (no account sync, nothing automatic triggers itself, no way to save or load anything manually, and many more problems).
It could boot loop in my case because fossify file manager is a system app and there is no way to disable it at boot. It does not at this point, but it could require flashing stock OS to solve.
naveensingh commentedon Oct 18, 2025
That's unrelated to #213. The change from #213 allows Fossify File Manager to handle file picking requests directly similar to the system files app.
mat999io commentedon Oct 18, 2025
Ok, I was pointing that other apps allow file picking inside the Files (com.android.documentsui) interface by showing it's own icon. Just like fossify file manager did in last working version 1.1
To be clear: Just Installing fossify file manager > 1.1 version BREAKS Android. You don't need to open any app, not Files (com.android.documentsui), not fossify file manager, or do anything.
Android stops working because storage permissions for both system and user apps seem to be tied to Files (com.android.documentsui) working properly.
naveensingh commentedon Oct 18, 2025
I'm aware. Does the same happen if you install Material Files?
mat999io commentedon Oct 18, 2025
I've just re flashed and factory reset my phone trying to troubleshoot this. I don't want to experiment with that app.
How is Material Files different from Mixplorer?
naveensingh commentedon Oct 18, 2025
It also handles file picking intents directly like Fossify File Manager.
To workaround this, you only need to remove Fossify File Manager or disable the system file picker. Factory reset should not be needed.
mat999io commentedon Oct 18, 2025
Not really. At first I thought it was a configuration problem so wiping the data partition (factory reset) would solve it. Then I thought it was the system app Files (com.android.documentsui) corrupt so I reflashed system.
Then I realized than even uninstalling fossify file manager some problems persist, bluetooth stopped working, some menu settings take ages to load. Storage settings / permissions get corrupted and there is no solving that.
naveensingh commentedon Oct 18, 2025
In v1.2.0, Fossify File Manager declared it can handle
ACTION_OPEN_DOCUMENT, which is the intent that is used by third-party apps to launch file pickers, and on Android, the system Files app is the default file picker.The existence of
ACTION_OPEN_DOCUMENTin Fossify File Manager's manifest might break file picking, but anything else is a bug/config error in the ROM or a "chain reaction" somehow caused by the broken file picking. I couldn't reproduce any of these problems on a custom ROM running Android 15 with Fossify File Manager installed in the system as a privileged app. The system file picker handles file picking as long as it is installed and enabled.This shouldn't even be happening as per the docs:
That is, the system file picker unconditionally handles all file picking intents regardless of any other app declaring the same capability.
I think more evidence is needed before we can say Fossify File Manager's capability declaration is doing all these things. If you'd like to confirm this, please try the following:
I'm okay with removing support for
ACTION_OPEN_DOCUMENTif it's causing file picker-related problems in some ROMs, but it would be good if you double-check and confirm this.mat999io commentedon Oct 18, 2025
Just to be clear: It's always Files (com.android.documentsui) the one starting the corruption in storage settings / permissions. Both system and user apps fail to access storage, and that causes many problems that cannot be solved (only erasing the data partition). So it does not matter if you uninstalled fossify file manager after android starts to fail.
I use Neo backup, but most system settings cannot be backed up. I don't have TWRP support to create / restore images easily. I could use adb shell (su) + dd, but that creates a 1-1 image of all storage space. It takes ages.
Also take into account that XPeria's Android is almost stock. Pretty similar to Pixel's Android + a few sony apps.
naveensingh commentedon Oct 18, 2025
Is it working properly after the factory reset?
mat999io commentedon Oct 18, 2025
Yes, if you remove fossify file manager as system app or do not install it as user app, wiping the data partition is enough.
But the moment it interferers with Files (com.android.documentsui), it creates permanent problems in Android, requiring to factory reset again. That's why I thought I had a corrupt system partition, but it's just the system storage not working.
naveensingh commentedon Oct 18, 2025
Are you sure that this is caused by Fossify File Manager? Do all the symptoms appear again if you install Fossify File Manager?
mat999io commentedon Oct 19, 2025
Yes, I'm using v1.1, the last version that does not cause the problem. So I tried all the newer versions.
naveensingh commentedon Oct 19, 2025
A new build will be available soon here: https://github.com/FossifyOrg/File-Manager/actions/runs/18629209677/artifacts/4310617391
Please install and confirm if it works properly now.
mat999io commentedon Oct 20, 2025
I tested the debug 1.3.1 version and it works like 1.1.0. It lets Files (com.android.documentsui) to work normally without crashing and it gives apps access permission to folders.
naveensingh commentedon Oct 20, 2025
Thanks for testing!