Material Файлы

RongVault is an offline Android application for creating, opening, and managing VeraCrypt-compatible file containers. After a container is unlocked, RongVault exposes it through Android's document-provider framework so files can be accessed from the built-in file manager or the system Files app without decrypting the entire container onto device storage.

RongVault is still under development. Keep independent backups of your containers and volume headers. Do not use a test build as your only means of protecting data: a forgotten password, PIM, or key file cannot be recovered.

What it is for Access files in VeraCrypt containers offline on an Android phone or tablet. Create standard or hidden volumes for storing sensitive files. Import and export encrypted volumes on local storage, SD cards, and USB media. Browse and manage files without keeping the whole container as a plaintext directory on device storage. Implemented features Android Storage Access Framework (SAF) selection for local, SD-card, and USB random-access container files. Add, unlock, lock, and remove containers from the app catalog. Removing a catalog entry does not delete the original container file. Standard and hidden volumes, including hidden-volume protection when writing to the outer volume. Password, PIM, and key-file authentication, with optional Android Keystore and biometric protection for saved outer-volume credentials. VeraCrypt non-system containers using the AES, Serpent, or Twofish single-cipher XTS suite; both primary and backup volume headers are recognized. FAT and exFAT read/write operations: create, rename, delete, copy, move, and import/export. NTFS is read-only. An Android DocumentsProvider for unlocked volumes and a foreground service while volumes are unlocked or long file operations are running. Built-in file manager with browsing, search, sorting, hidden-file display, creation, rename, deletion, and copy/move operations inside a volume. Markdown preview for .md, .markdown, and .mkd files, as well as standard Markdown MIME types. It is enabled by default and can be disabled in settings; the source remains available for editing. Cryptography and VeraCrypt compatibility scope RongVault uses the VeraCrypt non-system-container design: XTS mode for encrypted data, a password/PIM/keyfile-protected volume header, and a selected password derivation function (KDF). The current first-release scope is deliberately narrower than desktop VeraCrypt:

Area RongVault 1.0.2 scope Desktop VeraCrypt comparison Data-cipher suites AES, Serpent, and Twofish single-cipher XTS containers can be opened and created. VeraCrypt also offers Camellia, Kuznyechik, and multi-cipher cascades. These cascades and additional ciphers are not supported by RongVault's first release. KDF choices The open/change-credentials flow exposes PBKDF2-HMAC-SHA-512, SHA-256, BLAKE2s, Whirlpool, Streebog, and Argon2id. New volumes created in the current UI use PBKDF2-HMAC-SHA-512. VeraCrypt has broader, desktop-tested configuration coverage. Each RongVault KDF/cipher combination must be considered compatibility-dependent until it is marked verified in the matrix. Volume type Non-system file containers; standard and hidden volumes. VeraCrypt additionally supports system encryption and can work with partitions and whole disks. Filesystems FAT and exFAT read/write; NTFS read-only. VeraCrypt mounts volumes through desktop operating-system drivers and has a different host-filesystem integration model. Platform Android 15+ on arm64-v8a, using SAF and a DocumentsProvider. VeraCrypt has official desktop releases for Windows, macOS, and Linux. The selectable KDF list is not a blanket interoperability guarantee, especially for Argon2id and less-common combinations. See the compatibility matrix for the recorded test status. RongVault is not a replacement for desktop VeraCrypt when system encryption, partitions, full cipher/cascade selection, or desktop-level testing is required.

Limitations Supports VeraCrypt 1.26.29-compatible non-system file containers only; it does not support system encryption, physical partitions, or whole disks. TrueCrypt, LUKS, EncFS, PKCS#11, EMV, cloud drives, network locations, and other non-random-access container sources are not supported. NTFS volumes cannot be written to. Some cipher, KDF, cascade, hidden-volume, SAF-provider, and desktop-VeraCrypt combinations are still being validated. See the compatibility matrix for current coverage. RongVault is not an official VeraCrypt client, is not affiliated with or endorsed by VeraCrypt, and has not received an independent cryptographic or security audit. Relationship with EDS Lite and VeraCrypt EDS Lite RongVault uses EDS Lite 2.0.0.237 as a migration baseline and retains selected historical code and engineering experience from that project. The user interface, AndroidX/Gradle build, SAF storage boundary, Kotlin application layer, and vc_core native container implementation have been progressively rebuilt for this migration.

RongVault is not an official EDS Lite release and does not reproduce all of its features. It deliberately focuses on VeraCrypt non-system file containers on Android rather than the additional formats and legacy path-access modes in EDS Lite.

The EDS Lite README states that it is GPL-2.0-or-later, and its GPLv2 license text is retained with applicable imported files. RongVault distributes the combined work under GPL-3.0-or-later. If an imported file has a GPLv2-only or other license notice, that notice governs the file and its compatibility must be reviewed before combining it with GPLv3-only code.

VeraCrypt RongVault implements interoperability with the public VeraCrypt container format and targets non-system file containers from VeraCrypt 1.26.29. It does not contain the VeraCrypt desktop application and is not an official mobile client, affiliated project, or certified implementation.

Built-in file manager and Material Files The built-in file manager vendors and adapts code, file-operation flows, and Material Design patterns from Material Files 1.7.4. The following changes define the RongVault integration:

File access is routed through RongVault's UnlockedDocumentsProvider, so the file manager sees only the active encrypted-volume session rather than host storage paths. Create, copy, move, delete, and rename operations are bound to the volume session and its foreground-operation protection; normal volume operations do not use a host plaintext temporary directory. Root/Shizuku access, network storage, the FTP server, APK installer, and Material Files credential storage are not initialized or exposed by RongVault. The app integrates the Material Files Markdown viewer. It detects .md, .markdown, and .mkd filenames or Markdown MIME types, renders formatted previews with Markwon (including tables, strikethrough, task lists, and local relative images), resolves relative in-volume links, and lets the user return to the source editor. Markdown rendering is a user setting and is on by default. Material Files is licensed under GPL-3.0-or-later.

GPL is advance permission to copy, modify, and redistribute when its terms are followed, so separate author permission is normally not required. GPL does not grant permission to use project names, trademarks, or claims of official endorsement.

License RongVault is distributed under the GNU General Public License v3.0 or later (GPL-3.0-or-later).