External Storage. Error: Directory '/' not found.

[Francewhoa]

About that Encdroid app at https://play.google.com/store/apps/details?id=org.mrpdaemon.android.encdroid

I love it. It's easy to use. Small. And it's more secure because the code is open source for review.

This ticket is to report a bug. Storing a EncFS volume on external storage return this error message: Directory '/' not found

Steps to reproduce

1. Navigate to "Settings" > "Enable external SD card" CHECKED
2. Navigate to "Settings" > "External SD card preferences" > "External SD location" Try various option for the path. Such as with or without dash "/". Examples: /2R43-5574/ed /2R43-5574/ed/ 2R43-5574/ed 2R43-5574/ /2R43-5574/ /2R43-5574
3. Where 2R43-5574 is the external storage volume unique name, and ed is a folder name. The default value after a fresh install is /mnt/external1 But that value returns the same error message.
4. Navigate back to the app homepage. Tap "Create Volume". Tap "External SD" option Follow instructions on screen.
5. When you create a volume on external storage the app returns the following error message Directory '/' not found
6. Tap "CREATE VOLUME" button. Follow instructions on screen. After entering the password. After tapping "OK" button. The following error message is display: Directory '/' not found

I'm able to open that external storage using other apps. I double check the volume name. It's correct. Creating a volume on internal storage works. But not on external storage.

Using

• App version: 2.1.1
• App URL: https://play.google.com/store/apps/details?id=org.mrpdaemon.android.encdroid
• App updated: December 4, 2014
• OS: Android 7.1.1
• ROM: LineageOS 14.1
• Device: Samsung Galaxy S5
• Rooted: Yes
• Removable storage media: Flashdrive connected to the device via its USB port

Any volunteer for a patch? We would be happy to contribute testing and documentation.

Cheers,

Francois

[Francewhoa]

According to markuskreusch creating volume on external storage could be done with the Storage Access Framework. Assuming access is provided by the OS. Read more at https://github.com/cryptomator/cryptomator-android/issues/50#issuecomment-291153051

Developer documentation about Storage Access Framework (SAF) at https://developer.android.com/guide/topics/providers/document-provider.html