I have a Gocryptfs volume containing over 22,000 files, total size 2.6 GiB. There are a dozen top level directories, and most of the files are about three or four directories deep.

When I open that volume in DroidFS, the app freezes in the browser page. It just shows "Location: /" and "N//A" in the top bar and becomes unresponsive. If I wait until the phone blanks its screen, then when I reawaken it, DroidFS has ceased trying to open the volume, and has returned to the home page with the three buttons, and is responsive again.

I enabled the "Keep volume open when the app goes in background" unsafe feature and tried again. About 9 minutes after opening the volume, DroidFS populated the file browser with all the top level directories in the volume, and I could then successfully navigate the folders and view files. However, this only happened twice. On four other attempts, DroidFS remained frozen on a blank page for up to 30 minutes before I used "Force stop" on the app.

Once the volume was successfully open, there was a delay to close it as well. After pressing OK on the "Warning! Are you sure...?" pop-over dialog, DroidFS froze for about 30 seconds with the dialog still visible, then returned to its home page.

Opening and closing a small Gocryptfs volume that contains about a dozen files works fine, with no freezes or delays.

hi , can you please consider adding your app to f-droid , it would have bigger audience and allow us to get auto updates

inside the container, you can create two files or two folders with the same names but with different case

I can create two files
abc.txt
ABC.txt

this is incorrect from the point of view of the file system.

I ask you to ignore the case and consider two files with the same names - completely the same and forbid creating them.

Could you add support for sd card volume write?

Environment

Device

• Android 10, not rooted
• DroidFS 1.4.0 (release from github)
• Folder is managed by syncthing
• Active unsafe features:
  • Allow exporting/decrypting
  • Allow opening files with other applications
  • Allow sharing wfiles via the android share menu
  • Allow saving password hash using fingerprint

File's Source (= where files were encrypted)

• Linux
• GoCryptFS v1.8.0

On the host, the same decrypted files are opened.

Other

Files are synced to the phone from the host using syncthing.
Files are gocryptfs'ed on the host using reverse mode

Problem

Files cannot be viewed/exported from DroidFS

Context

Volume is opened w/o issues, files are listed. The timestamps and dates are valid:

Attempt to open common file format (jpg, txt) from the application itself causes:

The same when file is to be opened using external application: cannot be opened.

Copy of file to the same volume within DroidFS but with a different name leads to a file with a 0-byte size:

Any recipe by the way to build an apk using any ready-to-go docker image with NDK to avoid this build-dependency nightmare? :) That would allow to debug the issue first.

Sorry this is a noob question.
I am not finding the way to export encrypted files out of the volume and make them normal files.
Please help me.
Thank you.

Hello!

The total size of the volume does not fit in the info line. The localized string is only 2 characters longer than the original English, which hardly matters. Here is a screenshot from the screen of Xiaomi Mi 9 Lite phone:
Screen size (inches) | 6.39
Resolution | 1080x2340 pixels
Pixels per inch (PPI) | 403

By the way, there is no logo size issue on this screen (#16).

Hi, the app currently doesn't allow to edit files. Even if we open it with an external app, when we want to save it, we got an error.
Am I doing something wrong ? Or is it just not compatble ?

Thank you for your work, great to see gocryptfs support on android !

It would be nice if you improve the video player to fit landscape orientation.

I create a new volume and add the parent folder to the volume and lose all the sub files and sub folders of parent folder data

Could you add an option that makes it possible to import entire folders (recursively) without having to select every single file?

Android 9
DroidFS version 1.4.4

The app crashes when attempting to delete an image using the trash can icon while viewing that image. Does not crash when deleting via selecting with long press and then pressing the trash can icon.

A significant improvement would be to allow DroidFS to mount volumes under specified directories, such as /mnt/media_rw or in /storage using root permissions or a Magisk module.

I'm trying to open a volume that has been created without obscured file names (created with gocryptfs option: -plaintextnames)
When I can open it with DroidFS it shows as empty.
I suspect this might be because of the missing .diriv file (filename encryption hash)?
Can DroidFS open such volumes? If it's the missing .diriv, is it possible to create an equivalent file for a plain text volume?

Internal viewer don't recognize file extensions with capital letters.

The ascending and descending sorting menu items have a different order of items:
ascending: name, date, size
descending: name, size, date
This is unintuitive.

discussion in another ticket #72

Version 1.5.0 spoils newly added files: after a message about supposedly successful addition to the volume, it displays an error "Unable to load file". Files added to the volume by the 1.4.х application open normally in 1.5.0, but new files are unavailable (for exporting from the volume too).

Both the update installation and the clean installation with the creation of a new volume were tried. 100% error reproduction.

OS: MIUI 11 Andoroid 9

At first I thought some items were not listed but it's because when listing alphabetically, upper case items are shown first, then lower case are shown after (so the order is A..Za..z).
So if you look for something beginning with w, it could be about half way down (if it's upper case) or near the very end (if it's lower case).

It would be more useful (and like every other file listing I know) to sort by letter then case i. e. aA..zZ.

Similarly, folders seem to be included in the list mixed in with files. I realise this may just be personal preference but I am used to seeing folders at the start of the list (some managers have this as an option, most do it automatically in my experience).

Other than these suggestions, thanks for making this great app!

Hello,

as I've noticed, when attempting build if using some NDK version's (Such as the newer rc's, or even the newest stable 22, it'll error out during the compilation process. The latest version of the NDK I was able to get working was 21.3.6528147. Can you mention the reccomended version, maybe that of what you use to compile it? Sometimes this trial & error can get annoying.

Thank you :)

OS: Android 10
Device: OnePlus 6
Platform: ARM64
DroidFS version: 1.5.3

Tried with arm64 and universal apk, it crashes when trying to open a volume ( it worked fine previously).
Crash log attached.
logcat_09-05-2021_12-10-55.txt

Hi , according to https://nuetzlich.net/gocryptfs/comparison/ , securefs seems to be better performing than cryfs , can you look into it please ? https://github.com/netheril96/securefs

Thanks for this app!

I use a gocryptfs in a folder on cloud storage (specifically, Seafile).

On my phone, I have the Seafile app installed, and it created like a "mount" for it, I don't know the exact term, but I can see my Seafile even in a regular file manager, if that makes sense, and I think the files are being downloaded on demand.

When I click on "Open Volume" in DroidFS and click on the folder icon to select a folder, on the left I see my device and the Seafile mount, I can explore it, navigate inside and select it like so:

Once I press "Use this folder", the following two things happen:

1. I get a dialog saying "Warning! DroidFS can't write on removable SD cards. You will only have read-only access to the volumes therein."
2. The volume path is not filled, it's still empty, so I can't even open it for read-only access

Do you think it would be possible to support cloud storage? I think this would open a lot more use-cases for this app.

OS: Android 10
Device: Moto G5+
Platform: ARM64
DroidFS version: 1.5.2

Cannot select a path on removable 8GB exFAT flash drive connected via USB OTG. Attempting to choose the volume path on the flash drive shows "Error: Failed to retrieve the selected path".

Hello,

OS: Kubuntu 21.04
Go Version: 1.16.5
NDK Version: 21.4.7075529
Latest version of Android Studio Stable

when attempting to build DroidFS from any release tag of v1.4.5 & higher, then last command according to readme when being run take a few minutes and displays error:

make[1]: Leaving directory '/home/dhammel/Android/Project/DroidFS/app/libgocryptfs/openssl-1.1.1k'
go: cannot find main module, but found .git/config in /home/dhammel/Android/Project/DroidFS
to create a module there, run:
cd ../.. && go mod init
Done.

it seems as if the go build command, nearly the last step of the build.sh script, seem to cause this error and I can't seem to find out why. libgocrypfs.so, doesn't get built because of this.

I followed all directions of readme, so i have all the needed go modules, libgocrypfs submodule is included, openssl...

Build release tag v1.4.4 or below works, anything higher yields this error.

Hello!

On phones with not very large screens, the logo takes up too much space, pushing the main menu into the scrolling area. For example, a screenshot of the Xiaomi Redmi 5 phone is shown. Characteristics of its screen:
Size | 5.7 inches, 83.8 cm2 (~75.9% screen-to-body ratio)
Resolution | 720 x 1440 pixels, 18:9 ratio (~282 ppi density)

@hardcore-sushi
I have to ask again. Do you plan to add mount in Droidfs for rooted devices, yes or no?

thanks...

OS: Android 10
Device: OnePlus 6
Platform: ARM64
DroidFS version: 1.6.0

This happens only when trying to view images bigger than 5MB, it just shows a black screen. I managed to record some logs when opening one of said images.

logcat_10-22-2021_04-47-44.txt

now you can export files in an unencrypted type from a hidden volume. it's not safe. I ask you to make a backup function when all the data is packed in a zip archive in encrypted form.

that is, it is a simple data packaging in a zip archive with the name: containerName_date_time.zip

you can also implement data recovery from a backup from a zip archive.

gocryptfs v2.2.0 was released 5 days ago.

With it came the ability to use XChaCha20 instead of AES-GCM to boost performance on devices without AES hardware.

Having this as an option in DroidFS would be pretty terrific.

Related: If there is still some interest in supporting cryfs in DroidFS, cryfs from version 0.11.0 uses XChaCha20 as default as well.

Hello,
So I created a volume in the Android/data/sushi.hardcore.droidfs directory on the sd card. The problem is that whenever I try to rename anything, a file or a folder it always shows "Error Failed to rename file/folder". The same thing happens to volumes created inside the internal storage too. This happens in a device running android 5.1.1. I tested the app on another device running android 11, this does not occur on that in either locations. The version I am using is the latest v1.7.0, downloaded from github releases.

Description

If the system language is set to Portuguese (or Brazilian Portuguese), the app crashes when trying to open app settings or open container.

Steps to reproduce

1. Set system language to Portuguese (or Brazilian Portuguese)
2. Open App Settings

now it is possible for the container to remain open when switching to another application. but there is no lock function if the screen is locked or after a certain amount of inactivity.

i don't want to use default file manager from google due to privacy issues pls remove this depedencies

most often you need to run the program and open the container. I ask you to implement the function when, when the program starts, a password entry window opens immediately for a specifically selected one container. it's easier and faster this way.

now, when recording a video, there is no information about how much time has been recorded and there is no information about the size of the file. I ask you to add to the screen the time how much time is recorded and what is the file size.

useful and necessary information on the screen is very good

I ask you to make it possible to open the application settings when the encrypted volume is open. you can't do this now, you need to close the volume and only then you can get into the settings

As the app can use app storage, "hidden volume", Allow the app to bypass the "Permission denied" dialog.

Alternatively, use SAF(Storage Access Framework) to allow restricted access to a specific folder instead of all storage

Hello,

I think it would be nice to have thumbnails for pictures and videos in files browser.
While this kind of files does not always have a talkative filename, for now they are a bit difficult to manage because we have to open each to figure out which one it is.

Thanks and congratulations for this nice project !

after entering the password, you need to click on the open button, but the button is closed by part of the keyboard. I ask you to move the button above so that it is convenient to press open

It would be nice if the app supported the VeraCrypt volume format, seen as it is used quite extensively.

It would be great if this could become a background process that sits in the notification tray. Extra points for a progress bar!

Is it possible to open a SMB server URL with this?

1. Can I Use Other File Explorer?
2. Non Root Yes?
3. What Is Caveats When I Use DroidFS?

v1.7.0 If the dark mode is not switched on, the writing can no longer be read because it then has the same color as the background. No matter what design.
Android 11 Samsung german

Version 1.4.5 from F-Droid.
Device Info:
Android build version: G930W8VLS8CTI1
Android release version: 8.0.0
Android SDK version: 26
Android build ID: R16NW.G930W8VLS8CTI1
Device brand: samsung
Device manufacturer: samsung
Device name: heroltebmc
Device model: SM-G930W8
Device product name: heroltebmc
Device hardware name: samsungexynos8890
ABIs: [arm64-v8a, armeabi-v7a, armeabi]
ABIs (32bit): [armeabi-v7a, armeabi]
ABIs (64bit): [arm64-v8a]
System language: en-US

FATAL EXCEPTION: main
Process: sushi.hardcore.droidfs, PID: 12642
java.lang.RuntimeException: Canvas: trying to draw too large(134468880bytes) bitmap.
	at android.view.DisplayListCanvas.throwIfCannotDraw(DisplayListCanvas.java:229)
	at android.view.RecordingCanvas.drawBitmap(RecordingCanvas.java:97)
	at android.graphics.drawable.BitmapDrawable.draw(BitmapDrawable.java:529)
	at android.widget.ImageView.onDraw(ImageView.java:1367)
	at android.view.View.draw(View.java:20373)
	at android.view.View.updateDisplayListIfDirty(View.java:19318)
	at android.view.View.draw(View.java:20096)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4421)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4207)
	at android.view.View.updateDisplayListIfDirty(View.java:19309)
	at android.view.View.draw(View.java:20096)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4421)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4207)
	at android.view.View.updateDisplayListIfDirty(View.java:19309)
	at android.view.View.draw(View.java:20096)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4421)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4207)
	at android.view.View.updateDisplayListIfDirty(View.java:19309)
	at android.view.View.draw(View.java:20096)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4421)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4207)
	at android.view.View.updateDisplayListIfDirty(View.java:19309)
	at android.view.View.draw(View.java:20096)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4421)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4207)
	at android.view.View.updateDisplayListIfDirty(View.java:19309)
	at android.view.View.draw(View.java:20096)
	at android.view.ViewGroup.drawChild(ViewGroup.java:4421)
	at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4207)
	at android.view.View.draw(View.java:20376)
	at com.android.internal.policy.DecorView.draw(DecorView.java:980)
	at android.view.View.updateDisplayListIfDirty(View.java:19318)
	at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:686)
	at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:692)
	at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:800)
	at android.view.ViewRootImpl.draw(ViewRootImpl.java:3496)
	at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:3283)
	at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2818)
	at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1780)
	at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7827)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:911)
	at android.view.Choreographer.doCallbacks(Choreographer.java:723)
	at android.view.Choreographer.doFrame(Choreographer.java:658)
	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:897)
	at android.os.Handler.handleCallback(Handler.java:789)
	at android.os.Handler.dispatchMessage(Handler.java:98)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6944)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)

mounting to the filesystem would be nice if you have root on your device.

Thanks...