Path issue in OTG USB drive (gocryptfs volume)

[sa-anon-00]

OS: Android 15
Device: Samsung A14
Platform: ARM64
DroidFS version: 2.2.0

Trying to mount an existing Gocrypt volume from a usb drive connected through OTG throws a "Droidfs doesn't have write access to this path. Please try another location" error.

Same thing happens when trying to create a new volume on the same usb drive.

I believe it's the same issue as this now closed one: older issue

Attached droidfs logcat:
DroidFS_2026-01-30_10_29_46.log

Attached screenshots:

[hardcore-sushi]

Thanks for the bug report. What does happen if you manually enter

/mnt/media_rw/070A-459A/Encrypted

as the volume path?

[sa-anon-00]

Thanks for the bug report. What does happen if you manually enter

/mnt/media_rw/070A-459A/Encrypted

as the volume path?

Thank you for the quick response.

Entering that volume path works as intended 👍

[hardcore-sushi]

Great. I'll apply a fix then.

[sa-anon-00]

Great. I'll apply a fix then.

Thank you so much. I'd be more than happy to test the .apk if you want me to whenever that fix gets implemented 😀

[hardcore-sushi]

I had forgotten, but the fix has actually already been implemented in #330.

[sa-anon-00]

I had forgotten, but the fix has actually already been implemented in #330.

Oh my bad I didn't realize it's the same issue.

The link for the debug .apk on there with the fix seems to be deleted :( . Any chance I can get another link? (if it's no trouble of course).

[hardcore-sushi]

The fix will be included in the next app release.

[thomas725]

Hi there! I'm trying to mount a gocryptfs container from an external exfat disk on a Pixel 7 Pro cheetah phone, running LinageOS 23.2-20260217-nightly.
Sadly, on my device the suggested workaround to manually replace the file-picker resolved path "/storage/6A0E-BAAD/DroidFS" with "/mnt/media_rw/6A0E-BAAD/DroidFS" didn't solve the issue, same error with both paths (missing write-permissions..?) Mounting the volume via a root-shell in Termux (with gocryptfs build like this guide described: termux/termux-packages#11891 ) works, but I can only access that mount within the root shell itself.

UPDATE: I think I didn't manage to use the workaround the first go round while the termux gocryptfs instance still had the volume mount open. closing all that cleanly and retrying with droidfs now does look like it worked after all also on my device! ;)

[user46637]

Broken on Android 16

The inability to be able to mount USB drives on graphene operating system is not fixed using /mnt/media_rw/

I can confirm a lot of other open source apps work perfectly with USB drives. There seems to be a fundamental problem with the way that your code is working in Android 16.. must be fundamentally incorrect?

Take a look at how the file management is being undertaken in this application that works no issues.

https://apt.izzysoft.de/fdroid/index/apk/org.fossify.filemanager

As it stands your application is non-functional. Cannot be used with the latest version of Android 16.

---

Version 2.2.0

sushi.hardcore.droidfs
versionCode 374

targetSdk 34
minSdk 21

[AxolSky]

Changing the path to /mnt/media_rw/... does not seem to help on Google Pixel 10 Pro with up-to-date Android 16. It changes the error message from not having write access to not recognizing the encrypted drive. I unlocks okay in Cryptomator 1.19.2 (Linux).

from the logcat:
hiddenapi: Accessing hidden method Landroid/os/storage/StorageVolume; -> getPath()Ljava/lang/String; (runtime_flags=0, domain=platform, api=max-target-q,test-api) from Lsushi/hardcore/droidfs/util/Wiper; (domain=app, TargetSdkVersion=34) using reflection: denied

I don't see much else that could give a hint.

Version 2.2.0