Arcanum

Releases

• Sep 10, 2026 1.6
  ### New - **The gallery's search finds folders** — Typing in the gallery's search box now matches folder names as well as file names. Search for Camera and the gallery shows what is in that folder, whatever the photographs themselves are called, and the folder appears as a row above the results with its four newest pictures and its count - tap it to see that folder on its own. It matches the folder's own name rather than the whole path, so searching for a parent does not sweep in everything beneath it. (#123) - **Settings can be carried to another phone** — Settings, Backup writes your settings to a file, and reads them back on another phone. It carries the preferences, the way the vault list is arranged and, if you ask for it, the list of vaults itself. It never carries your PIN, panic mode or fingerprint unlock: a PIN in a file is a key, panic mode belongs to the phone it was set up on, and fingerprint unlock is tied to this phone's hardware and cannot leave it. The file can be protected with a password of its own - without one it names your vaults in plain text, and the switch says so. (#63) - **A vault that has lost its file can be pointed at it again** — A vault whose file has been moved, or whose list came from another phone, used to be a dead end: the only way back was to forget it and add it again, losing its name and its settings. It now offers to find the file instead, and keeps everything it had. Its card shows a crossed-out folder while the file is missing, so the list says which vaults need attention. - **The gallery can be limited to the folders you choose** — A vault with photos in several folders showed them all in one stream, with no way to look at one folder at a time. The folder button in the gallery's top bar now opens a list of every folder holding media - four of its newest pictures in a square, its name, and how many files it has - and the gallery shows the ones you tick. Tick nothing and it shows everything, as it always did. The button is coloured while a filter is on, so a gallery showing part of a vault never looks like one that has lost the rest. The choice lasts until the vault is closed. (#123) - **A vault can stay open in the background** — Android closes apps it is not using to reclaim memory, and a vault closed with the app: an import stopped halfway, a file opened in another app stopped working, and coming back meant unlocking again. Settings - Security now holds "Keep vaults open in the background", which keeps Arcanum in memory while a vault is open. It is off by default and it is a best effort rather than a promise - a phone short of memory, or a manufacturer's own battery saver, can still close the app. Auto-lock is unaffected: the app still locks on its schedule, and vaults set to close when you leave or when the screen goes off still do. One thing to know before turning it on with the calculator disguise: while a vault is kept open, Android lists the app in the notification shade's active apps panel under the name Arcanum, and nothing in the app can change that. (#102) - **Markdown notes read like notes** — A .md file in a vault now has two sides, and a button in the corner of the editor turns it over. Written, it is text with its marks visible and a row of them over the keyboard - bold, italic, struck through, code, a link, a heading, a quote, both kinds of list and a checkbox - each of which is a toggle, so pressing one on text that already carries the mark takes it off. Read, it is a page: headings by size with a rule under the first two, lists and nested lists, quotes with a bar down their side, code in a block of its own that scrolls sideways, tables laid out by what is in them rather than in equal columns, and the marks inside a line all doing what they say. Checkboxes are not a picture: tapping one in the reading view edits the file, undo takes it back like any other change, and both sides of the button are the same text - not a copy of it. A note that opens with front matter, the block of properties between two lines of three dashes, is shown as properties instead of a rule and a paragraph, in both modes. A link asks before it takes you out of the app, and shows the whole address while it asks: nothing is fetched from the network to render a file kept in a vault, images included. - **Text files open in the app** — A note, a config file or a script had to be handed to another app to be read, which meant letting that app into the vault. Tapping one now opens it in Arcanum: line numbers down the left, colouring for Markdown, JSON, XML, ini and yaml files, shell scripts and code, undo and redo in the bar, and a switch for the dots and arrows that stand in for spaces and tabs. Nothing is written outside the vault to make this possible. What the editor is most careful about is what you cannot see on screen - the file's encoding, its byte order mark, whether its lines end the Windows way or the Unix way, and whether the last line ends at all. All four come back exactly as they were, a file that ends its lines both ways says so before it is saved, and a file that is not UTF-8 is kept byte for byte: if what you type cannot be stored in its own encoding the save stops and asks, rather than quietly writing question marks where the characters were. Saving writes a second file and renames it over the first, so a save that is interrupted leaves either the old file or the new one and never half of either. Files up to 1 MB open here; a larger one still goes to Open with. How it looks is yours - Settings, Text editor has the font, the size, wrapping, line numbers and colouring, with the editor itself drawn above them, changing as you change them. (#109) - **New folders and new documents from one button** — The plus in the file browser offered Import and New folder. It now offers New..., which asks what to make: a folder, or a text document - .txt, .md, or any extension you type in. The name is checked while it is being typed rather than after: a name already taken in that folder, or one holding a character a filesystem will not accept, is refused before anything is written. On FAT and exFAT that check ignores case, because there Notes.txt and notes.txt are one and the same file. A document you make this way opens in the editor at once, which can be turned off in Settings, Text editor. - **PDFs open inside the app** — A PDF in a vault had to be handed to another app to be read, which meant letting that app into the vault. Tapping one now opens it in Arcanum: pages scroll, pinch zooms, a double tap goes in and back out, and while zoomed a finger moves about the page and on through the document in one gesture. Nothing is decrypted to disk and nothing is read that is not looked at - the document is read a piece at a time from inside the vault, so a large one opens as quickly as a small one. Open with is still in the file's menu for anything you would rather read elsewhere, and it still needs external app access; this does not. A PDF protected by its own password says so rather than failing quietly - Android cannot open those. (#137)

  More…

  - **A hidden volume can be exFAT or ext4** — The hidden volume was always formatted FAT, whatever the outer volume was made with. That put a 4 GB ceiling on any single file kept there, so a video or a disk image would not go in even when the vault around it was 50 GB of exFAT. The wizard now asks for the hidden volume's filesystem the same way it asks for the outer one's, and the two answers are independent: an exFAT vault can hold an ext4 hidden volume, or the other way round. This is about new hidden volumes; one that already exists keeps the filesystem it was made with. - **A hidden volume can go on a USB drive** — Choosing Hidden Volume and then a USB drive used to lead nowhere: the outer volume was created on the drive and the last step failed, because only vaults held in a file had a way to place the hidden volume. They go on a drive now, whole-device or in a partition, the same as VeraCrypt allows on a computer - and hidden-volume protection works there as it does for a file, refusing any write to the outer volume that would reach the hidden one. A vault on a drive has no size to choose, since it fills the whole drive or the partition it was given: the size step shows that number instead of asking for one, and the hidden volume's size is chosen inside it. - **Argon2id, a derivation that costs memory** — VeraCrypt added Argon2id, and Arcanum can now open and create vaults that use it. Unlike the five hashes it stands beside, its cost is memory rather than repetition: an attacker guessing at a stolen header needs hundreds of megabytes for every guess, which is exactly what a graphics card is bad at supplying. How much is set by the PIM - left empty it means 416 MB and a few seconds on a phone, while a PIM of 1 costs 64 MB and needs a password of 20 characters or more. Nothing hunts for it by guessing, because one attempt is that expensive: an unlock that fails offers to try Argon2id, a switch in Settings, Security decides whether that offer appears at all, and a vault that opened with it is remembered for next time. Where the memory is not there, the app says so with the numbers rather than blaming the password, and lets you insist if the shortfall is only the safety margin. Vaults made this way open in VeraCrypt 1.26.20 and newer on a computer, and cannot be opened by anything older. (#177) - **GIFs play** — A GIF opened from the gallery or from Files showed one frozen frame. It now plays, and keeps looping even when the file itself says to run once - the same for an animated WebP. Only the picture you are looking at animates; the ones either side of it wait as a still frame, so a long animation does not fill memory while you swipe past it. Very large files, above 48 MB, still open as a single frame: playing one means holding the whole file in memory. The photo editor bakes what it saves into one still image, so it stays closed for animations rather than quietly flattening one. (#159) - **Skip tracks from the notification** — The playback notification had play and a back button that only jumped to the start of the track. It now has previous and next, and they move through the folder you started playing from - as does a headset, a car or anything else that talks to the media buttons. Shuffle and repeat are handed to the player too, so what the notification offers matches what the app does: turning shuffle on reshuffles from the track you are on, and with repeat off the next button correctly disappears once the shuffled list runs out. (#139) - **See what an operation is doing, and stop an import** — The line that appears while files are moving is now a button. Tapping it opens the whole picture: the file being worked on and how far into it, which item of how many, how fast it is going and how long is left, and anything that was skipped or could not be carried over as it happens rather than in a summary at the end. Copying, moving, deleting and exporting report this way now, not just importing. Where the size of something is not known - a provider that will not declare it, or a folder whose contents are found as the walk goes - no percentage or estimate is shown rather than an invented one, and importing a folder measures it first so it can count properly. An import can also be stopped: the button asks first, and the work pauses while you decide. Stopping keeps the files already in the vault, discards the one half-written, and removes nothing from where it came from. (#158) - **Vaults on USB flash drives** — A vault can now live on a USB flash drive plugged into your phone, created here or opened from one made elsewhere, and a drive prepared here opens in desktop VeraCrypt. Give the vault a partition and the rest of the drive stays ordinary storage - the create wizard has a partition editor for it. Two things are worth knowing before you rely on one: a drive whose whole surface is a vault has no partition table, so Android offers to format it on every connection and accepting that destroys the vault; and pulling a drive without ejecting can lose the last writes, so use Eject and wait for the confirmation. Full details, including what Arcanum does not do about counterfeit drives, are at arcanum.zip/docs/usb-drives (#95) (#131) - **The same file in two places, without a second copy** — A file can now be given a second name somewhere else in the same ext4 vault: three dots on it, Create link, then pick the folder. It is not a copy and not a shortcut - it is the same file, so it takes no extra space, changes to it show in both places, and removing one of the names leaves the other working. Its properties say how many places it is in, and deleting it says so too rather than claiming the file is gone for good. A folder can be linked the same way, though a folder link is a pointer rather than the folder itself, so it stops working if the folder is moved or removed. ext4 vaults only: FAT and exFAT have no such thing, and the entry does not appear there. (#128) ### Improvements - **A backup with no password now warns about hidden volumes** — A settings backup can be written without a password, and then it is a plain text file that names your vaults. If one of those vaults is set to protect a hidden volume, that fact would be in the file too - and the existence of a hidden volume is the one thing a hidden volume is meant to keep to itself. Arcanum now stops and says so before writing such a file, so you can put a password on it or leave the vault list out. - **Restoring a backup no longer switches file access back on** — If a vault had been opened up to other apps on your old phone, restoring its settings used to turn that on again on the new one without asking. That permission is about the apps on the phone you are holding, so it now starts off and is asked for again there. A restored vault already started locked and without fingerprint unlock, for the same reason. - **Arcanum can tell one volume from another** — A vault held in a file is now recognised the way a vault on a USB drive always has been: by a fingerprint of its own header, which needs no password to read. So when you point a vault at a file, Arcanum can say whether it is the volume it was looking for, rather than accepting anything and failing later at the password. If you changed that vault's password on another device its fingerprint changes too, and there is a button that says so. - **The gallery moves rather than jumps** — Photographs that leave the grid - filtered away, deleted, or reordered by a change of sorting - now fade where they stand while the rest slide into the gap, instead of the whole grid rearranging itself between one frame and the next. - **The folder you are moving is marked** — The sheet that asks where to copy or move something lists folders - including the very folder you are moving. It is now green, the way the vault you came from already was, so the thing being moved is not mistaken for a place to move it to. - **A tap opens the vault** — Tapping a vault used to open its settings page, which is a detour when what you wanted was the vault. It now opens the vault: mounted, you go straight in; closed, it asks for the password. Everything else moved into the long-press menu - unmount, rename, select, and the settings page, which is now called Vault Info. A vault on a drive is checked before the password screen opens, rather than after you have typed one in. - **Vaults grouped by where they are kept** — The list is grouped by location out of the box: phone storage, app storage and drives each get a heading, and the vaults under it are drawn as one block of cards, like the settings screens. Under each name is when the vault was last opened, since the heading above already says where it is. - **Vaults on a drive can be renamed** — A vault on a USB drive could not be renamed at all. It can now, and the drive does not have to be connected: the name lives in Arcanum's own list, not on the drive. Because a name can change, Vault Info shows the volume's fingerprint underneath it - the identifier Arcanum actually finds the volume by, so two volumes on one drive stay apart whatever they are called. - **The disguise is no longer offered on arrival** — The offer to turn on the calculator disguise appeared on the first visit to the vault list - the one moment someone is least placed to judge it, having just set a PIN, with no vault yet, for a change that cannot be undone without reinstalling. It is available where it belongs, in Settings, Security. - **The longest settings explanations moved behind a button** — A handful of settings need a paragraph to explain themselves - what Argon2id costs, what turning screenshot protection off exposes, what the share sheet and a media session let other apps see, what the calculator disguise cannot undo. Those paragraphs sat in the list, so a screen of eight settings was mostly prose with the switches lost in it. They are behind an i beside the switch now, which opens the explanation in full, and the row keeps only its name. Short descriptions stay in the row where they always were: a button for a few words is more work than reading them. The i stays live on a setting that can no longer be changed, which is exactly when what it does is worth reading. - **Settings, grouped and easier to read** — The screens inside Settings are laid out the way the main list already was: settings that belong together sit in one card block under a heading, instead of running one after another with nothing to separate them. A switch now shows a tick when it is on, and a padlock when it cannot be moved at all - which is what a greyed switch used to leave you guessing about. About leads with three buttons: the source code, the project's page and, in the F-Droid build, a way to support it that also sits in Settings itself. Nothing moved between screens and nothing was renamed. Two smaller things while there: coming back from What's New or from the donations page now returns where you opened it from rather than always landing on About. - **The settings screen, rearranged** — Settings is laid out the way Android's own is: its sections are grouped into cards, each with a round coloured icon, the arrows on the right are gone since the whole row was always the button, and the title unfolds when the list is pulled back to its top. Nothing moved between sections and nothing was renamed - only the way they are drawn. - **A vault's settings, rearranged** — The vault screen was one long row of items with nothing to say which belonged with which, and four of its actions were hidden behind the three dots in the corner. It is laid out in groups now - access, protection, and managing the vault itself - with the three things you reach for most as buttons under the vault's name, mounting and unmounting among them as one button that knows which it is. Rename, move, forget and delete came out of the menu into the list where they can be seen. What the vault is made of now has its own button in the top corner, instead of being hidden behind a tap on the icon that nothing told you about; it is grey until the vault is open, because the header it reads cannot be decrypted before that. The way back is a round button on every screen. - **Sorting and filtering the Gallery** — The Gallery can be sorted now: by name, date, size, type, or at random. There is a view options button in its top bar, and the All / Photos / Videos filter moved in there with it, which gives the grid back the row the filter chips used to occupy. Your choice is remembered. The month and day headers stay for the date order, where a timeline is what they describe, and step out of the way for the others. The random order reshuffles each time you come back to the Gallery, which is a good way to meet a collection you had forgotten the middle of. (#122) (#151) - **Pinch to zoom a video** — A video can be pinched to zoom and dragged around, the way photos already could. Double tap still seeks ten seconds, and the fullscreen button still turns the screen for videos wider than they are tall. (#151) - **ext4 vaults are much faster to fill** — Adding files to an ext4 vault wrote about twice as much to storage as the files themselves, because the bookkeeping was redone for every single block. It happens once per run of blocks now, so a large import writes about half as much and finishes noticeably sooner. (#155) (#160) (#161) (#162) - **Deleting from an ext4 vault is much lighter on storage** — Removing a file from an ext4 vault rewrote a block of bookkeeping once for every block the file held, so deleting a large file wrote about as much to storage as adding it did. It happens once per run of blocks now: on a phone, clearing twelve files out of a vault took 159 writes, where deleting a single one of them used to take about five thousand. (#165) - **Copying and moving ask where, in one step** — Copying or moving files used to be two steps that did not look like two: Copy put them on a clipboard, and Paste waited in a menu at the top of the screen - unless more than one vault was open, in which case the same button asked where to instead. Now it always asks. Copy or Move opens the list of places at once: the folders of the vault you are in, or the vaults themselves when several are open, with a Copy here or Move here button at the bottom. Paste is gone from the menu, and so is the clipboard behind it. Copying something into the folder it already lives in still makes a numbered duplicate, which is how a file is duplicated. Each vault in that list now carries the icon of where it is kept - a USB drive, the phone, or the app's own storage - so several open vaults can be told apart at a glance. - **A vault shows where it is kept** — Every vault in the list wore the same padlock, which said whether it was open and nothing else. It now carries the icon of where its file lives - a USB drive, the phone's own storage, or ordinary storage - so a list of vaults can be read at a glance, and whether one is open is still said by the colour behind that icon. The same icon appears wherever a vault is offered, including the list that opens when you copy or move something. Closing a vault still shows the lock and the words, but the lock no longer flies across the screen into the list afterwards. - **An ext4 vault says when it was interrupted** — If the app is killed, the battery runs out or a drive is pulled while a file is being written, an ext4 vault is now marked as unfinished, and opening it tells you so once. Nothing is lost and the vault works normally - what is left behind is bookkeeping a filesystem check tidies up, which every write of every operation was interrupted on purpose to establish. A Linux desktop opening the same container sees the same mark and runs its own check without being asked. arcanum.zip/docs/filesystems explains what is and is not promised. (#142) - **The import indicator says how far along it is** — Importing showed a bar that moved on its own and told you nothing: not how much of the file had been written, and not how many files were left. It now names the file being imported and fills the bar as the bytes land - with the percentage beside it when you imported one file, and which of them this is, 3/7, when you imported several. A file whose size the source will not report still gets the old running bar, since a made-up position is worse than none. - **Unlocking a vault is a button now** — Nothing on the unlock screen said how to actually unlock: the only way in was the enter key on the keyboard, which one person reported spending ten minutes looking for. The large lock is the button now - tap it and the vault opens. It shifts gently every few seconds so it reads as something to press, and tapping it with nothing filled in shakes and says what is missing instead of doing nothing at all. The vault's icon above it opens the details of a mounted vault, and the separate row and toolbar icon that used to carry these two jobs are gone. (#120) - **Remove from list is now Forget, and it asks first** — Taking a vault off the list was called Remove, wore a bin icon and happened on a single tap, with nothing said about what that meant. In selection mode it was worse: the same bin removed entries and never touched a file. It is called Forget now, it asks first, and the confirmation says plainly what goes and what stays - the entry and its thumbnails go, the vault file itself is left exactly where it is. Forget also sits in a vault's own menu, not only in selection mode. - **Links in these notes are tappable** — Addresses written in What's New entries, like the documentation links above, can be tapped instead of copied out by hand. - **Adding a vault starts in a folder, not in Recent** — Choosing Internal storage when adding an existing vault opened the system picker on Recent, which is usually empty for a vault file - leaving you to find the picker's own folder drawer before you could look anywhere. It now opens at the folder of a vault you already added, or at internal storage if this is your first. The picker is the system's own screen, so this is a hint rather than a guarantee, but where it is honoured it saves the detour. (#126) ### Security - **Hidden volume protection either holds or the vault does not open** — Unlocking the outer volume with hidden volume protection on, and giving the hidden volume's password, is how you write to the outer volume without destroying the hidden one. If that password did not actually open the hidden volume - a wrong PIM, a keyfile left out, or a hidden volume made with Argon2id, which nothing searches for by guessing - the vault opened anyway with no protection at all, while the app said protection was active. The next thing copied in could overwrite the hidden volume the app had just promised to guard. Now the unlock fails and names both things worth checking, and the hidden volume has its own hash selector for the Argon2id case, with a failed attempt offering to try it. Separately, the guarded area itself started 128 KB too late even when protection did work, which left the hidden volume's first sectors - the ones holding its filesystem - writable; the boundary now comes from the hidden volume's own header, the way VeraCrypt does it. Two smaller gaps of the same shape are closed: unlocking with a fingerprint on a vault set to protect a hidden volume now asks for the password, since the hidden password is deliberately saved nowhere, and turning protection on while leaving its password empty no longer unlocks the vault unprotected. - **What is playing stays inside the app** — A video played from a vault put its file name, and a frame taken from the video itself, on the lock screen and in the notification - where the PIN, the fingerprint, the calculator disguise and screenshot protection do not reach. Music never did that, and now neither does video: what leaves the app is a fixed name and nothing else, whatever the file is called and whatever tags are inside it. If you would rather see the track, the artist and the cover out there like in any other player, there is a new switch for it in Settings, Security - off unless you turn it on. - **A vault you remove stops being remembered** — Removing a vault left things behind. The list of what had been inside it stayed in the app's index, its thumbnails stayed on disk, the saved unlock for your fingerprint stayed with the paths of the keyfiles it used, and Android went on holding a permission that named the vault file. Panic mode cleaned even less: it erased the vault and kept the list of everything that had been in it. All of that goes now, on every path a vault can stop existing, and anything left behind by earlier versions is swept away the next time the app starts. Panic mode's "Clear app settings" also does what it says for the first time - it was saved, shown and never acted on. The one thing it deliberately leaves alone is the calculator disguise: turning that off would leave a calculator icon opening a PIN screen. (#134) - **Coming back to Arcanum asks for the PIN again** — Android shuts apps down in the background to reclaim memory, and some phones do it eagerly. When that happened to Arcanum it came back on the screen you had left it on, already past the calculator, because the app that had been unlocked was gone and the one that took its place had no way to tell. The unlock now belongs to the running app rather than to the screen, so anything that shuts Arcanum down means entering the PIN again. On a phone that is aggressive about background apps you will meet the calculator more often than before, whatever the auto-lock delay is set to. (#150) - **What is in a vault no longer reaches the system log** — While a vault was open, the ext4 part of the app kept a running commentary in Android's log: which file was being opened, by name and by path, and every block read from the volume. Other apps cannot read that log, but a bug report carries it - and a bug report is exactly what you are asked to send when something has gone wrong - and anyone who can plug the phone into a computer with developer options turned on can read it directly. An app built so that nobody can tell what is in a vault should not be narrating it, so the released app now says nothing at all. Debug builds still do, which is where it belongs. It is also a little less work per file. (#174) - **Forgetting a vault clears its media index as well** — Removing a vault from the list used to leave rows behind in the app's own media index: the names and paths of files that had been inside that vault, kept on the device after the vault was gone from the list. They are deleted along with the vault now, as its thumbnails already were. ### Fixes - **The search box behaves the same everywhere** — The three search boxes in the app had drifted apart. The text cursor was painted black, which on a dark theme is a cursor you cannot see, in the gallery inside a vault and in Files; opening the search in the gallery did not put the cursor in the box or raise the keyboard; and pressing back with the box open left the screen instead of closing the search. They are one box now, so they behave the same way. - **The back gesture in the photo viewer** — With the interface hidden, swiping in from the edge of the screen turned the page instead of going back, and there was no way out but the button in the corner. Hiding the interface now leaves the navigation area to the system, so the back gesture is the system's own again - with its arrow, and on a phone with three buttons with its button, which used to disappear along with everything else. The photograph is no smaller for it. - **Photos moved to another folder came back broken** — Moving a folder of photos or videos left the gallery pointing at where they used to be: the grid still showed them, opening one gave a broken image, and only closing and reopening the vault put it right. A move now carries the gallery along with it, inside a vault and between two vaults alike, and thumbnails are kept rather than made again. The same gap worked the other way round for copies - a copied photo did not appear in the gallery until the vault was reopened - and that is fixed with it. - **Renaming a vault could lose it** — Renaming a vault that was added with the file chooser renamed the file on your device, and Android hands out access to such a file by its name: the permission you gave was for the old one, and the renamed file could not be opened again. The vault was intact, but Arcanum could no longer reach it. Renaming a vault now changes its name in Arcanum only, the file keeps the name it has on your device, and the rename dialog says so. If you renamed a vault and lost it this way, the file is unharmed: forget the vault and add it again, and it comes back. - **Coming back to a vault that had closed** — A vault set to close when you leave the app did close, but returning put you back on its screen as though it were still open. The screen of a vault now closes with the vault. - **The size step measures the storage you actually chose** — With the vault's file placed on an SD card, the wizard still read the free space of the built-in storage. A phone whose own storage was nearly full was told there was no room for a vault the card had space for several times over, and the size step would not move on. The figure now comes from the volume the file itself is on, wherever the system picker put it. Two things beside it: the location is called Device or SD card, because that picker reaches both and the old name suggested otherwise; and the note about the 4 GB limit no longer states it as a fact about every card - an app cannot ask Android how a card is formatted, and the one in the report was exFAT, which has no such limit. (#180) - **Choosing where to copy or move files works in a big vault** — The sheet that asks where to put files listed the folders without ever scrolling, so in a folder with many subfolders the list ran off the bottom of the screen and took the confirm button with it - there was no way to copy, move or link anything into such a place. It scrolls now, and the button stays where it is. While there: the magnifier beside the vault's name opens a field that narrows the folders to what you type, which is what was asked for in the report. It filters the folder you are looking at, the way search in the file manager does, and closes again when you step into a folder. (#179) - **A tiny vault made on a computer opens** — VeraCrypt can make very small containers - its own minimum is 292 KB - and Arcanum answered those with "corrupted container". The filesystem driver was refusing any FAT volume under 64 KB as too small to be real, a rule of thumb it applies before looking at the layout itself, and volumes that size are perfectly legal FAT12. They open now, and files can be written to them and read back. Making a vault that small is still not offered here: below 5 MB the FAT formatter cannot pick a type it will accept afterwards. - **The smallest vault is 5 MB** — The size step took any number, and the hidden volume's step named 4 MB as its own minimum - but a volume of about that size could not actually be formatted, and the wizard only said so at the very end, with everything else already set up. Both steps now stop at 5 MB and say so before any work starts. This is about making a vault, not opening one: a smaller vault made by VeraCrypt on a computer opens here and takes files exactly as before. - **Changing a password reaches every vault it should** — Change password and change keyfiles only ever looked at the first header in the container, which is the outer volume's. A hidden volume's own password was answered with "wrong password", so there was no way to change it here at all - where on a desktop VeraCrypt changes whichever of the two volumes the password opens. Both wizards do that now, and they rewrite that volume's backup header along with its working one, so an old password does not survive in a place a header restore could bring it back from. Two more things were out of reach. A vault made with Argon2id could not be opened by either wizard, because the automatic search never tries that derivation - the first step now has a Current hash field for naming it, exactly like the unlock screen. And asking for Argon2id as the new derivation was quietly ignored: the wizard reported success and left the vault on the hash it already had. Changing keyfiles no longer touches the derivation either: it used to write the hash the app had on record, which for a vault this install had never unlocked is SHA-512, so changing a keyfile on a Whirlpool vault turned it into a SHA-512 one without saying so. - **A hidden volume made here opens on Windows** — A hidden volume created in Arcanum recorded its own size as zero in its header. VeraCrypt on Linux and macOS works the geometry out from other fields and never noticed, but the Windows driver takes the volume's length from that one - so a hidden volume made here would not mount in VeraCrypt on Windows at all, and asking Windows to protect it while writing to the outer volume would have guarded nothing. The field is written the way VeraCrypt writes it now. Only the hidden volume's own headers carry it, and nothing can read them without the hidden password; the outer header still records nothing about a hidden volume, since anyone holding the outer password could read that and prove the hidden volume exists. Hidden volumes created before this version keep working everywhere they worked before, and can only be given the field by being recreated. - **An edited photo is the format it claims to be** — Editing a picture and saving it wrote a JPEG whatever the file had been, and left the old name on it: an edited .webp was a JPEG called .webp, and the same went for .heic and .bmp. Little noticed, because most programs look inside a file rather than at its name, but the file was lying about itself and carried that out of the vault on an export. The format now follows what can actually be written: a WebP stays a WebP, and where the original cannot be written back at all - Android has no encoder for HEIC or BMP - the picture is saved as JPEG or PNG and the name changes to match, which the app tells you about. Replacing the original never overwrites a different file that happens to hold that name already. - **An edited photo keeps the date and the place it was taken** — Saving from the editor wrote out the pixels and nothing else, so an edited photo came out with no date taken, no location and no camera in it. Inside the app that stayed invisible, because the date is kept in the index as well, but the file itself was stripped - and the file is what an export, or a fresh scan of the vault, has to go on. The original's EXIF is now carried across: from a JPEG the whole block, camera and exposure included; from a HEIC the date and the place. The orientation is written upright, since the picture is saved already turned; the recorded size follows a crop; and the small preview the camera embedded, which is a picture of the photo before the edit, is dropped. - **HEIC photos show up** — A photo in HEIC, which is what an iPhone and a good many Android cameras save, had no thumbnail in the gallery and opened as a broken picture in the viewer, while the editor opened the very same file without complaint. The decoder Android uses for that format wants the whole file at once and refuses to be fed it a piece at a time, which is how the gallery reads everything else. These are now read whole. - **The editor opens a large photo** — A picture over 16 MB - a big scan, a long-exposure PNG - answered "Cannot decode image" in the editor. It was being asked for in one piece, and a vault hands over no more than 16 MB at a time. It is now read in pieces, like everywhere else in the app. Past 50 MB the editor says the picture is too large, rather than blaming the picture for being unreadable. - **Notifications wait their turn instead of replacing each other** — Two things finishing at once meant one of them was never seen: the second notification replaced the first mid-animation. They queue now, the more serious one goes first, and two of the same thing are one notification rather than two in a row. Errors stay until you dismiss them instead of disappearing after five seconds like a confirmation, and anything that arrives while the app is locked waits until you are back rather than appearing over the calculator. (#135) - **A photo keeps the place it was taken** — A photo carries the place it was taken inside it, and Android strips that out before handing the file to an app that has not been allowed to see it. A photo put into a vault lost its location silently, and for good if you had also asked for the original to be deleted. Arcanum now asks for that permission the first time you import something, after explaining what is about to be asked and why - the system dialog speaks of access to photos and videos, which sounds far broader than what it actually grants. Declining is fine: the import works either way, and only the location is lost. Files arriving through Share go through the same check. (#149) - **Imported files keep their own date** — Until now everything imported into a FAT or exFAT vault was stamped 1 January 2025 - one fixed date for every file, because the vault had no clock to ask. It has one now, and more than that: a file keeps the date it already had, so a vault sorted by date comes out in the order you expect. This applies to what you import from here on. Files already inside a vault keep the date they were given, because their original date is not recorded anywhere to put back. Going the other way, a file exported out of a vault still carries the date it was exported: Android does not let an app set timestamps in shared storage without a broad storage permission, and Arcanum does not ask for one. (#154) - **Swiping follows the order you chose** — Opening a photo and swiping sideways used to walk through files in the order the vault happened to index them, whatever sorting you had picked in the list you opened them from. It now follows that list: the Files browser's order when you open from Files, the Gallery's when you open from the Gallery. (#151) - **A long operation no longer locks the app in the middle of itself** — Auto-lock measured how long it had been since you last touched the screen, and watching a progress bar is not a touch. A vault that took longer to open than the auto-lock delay therefore threw you back to the calculator part way through opening it - and with "unmount on auto-lock" switched on, it tore down the volume it was still setting up. The timer now counts the app working for you as well as your touches: opening a vault, creating one, changing a password or a keyfile, backing up or restoring a header, a long import and playing a video all hold the lock open while they run, and the delay starts counting from the moment the work stops rather than from your last touch before it. Leaving the app in the middle of an operation now waits for it to finish instead of cutting it short. A vault does stay unlocked for as long as an operation runs, which is the deliberate half of the trade. - **A vault does not close itself while it is busy** — Copying a large folder into a vault and then putting the phone down used to be enough to lose the rest of it: switching away, or letting the screen turn off, closed the vault if you had asked it to close on either, and whatever was still being written stopped where it was. Both of those settings now wait for the work to finish before they close anything, and if you come back before it does, the vault simply stays open. Only unmounting a vault yourself, or the panic PIN, stops an operation part way. The vault is still flushed to disk the moment you switch away, so nothing has to wait for the work to finish to be safe. - **Choosing a file no longer locks the app** — Picking files or a folder to import means leaving Arcanum for the system's own file picker, and the minutes spent there counted as time doing nothing at all. On a short auto-lock delay, looking for the right folder was enough to come back to the PIN screen - and the import would then run anyway, behind it, with nothing on screen to say so. Time spent in a picker Arcanum opened is no longer idle time, and a result arriving after the app has locked is refused rather than quietly written into a vault you have been told is closed. A picker left open for more than fifteen minutes stops holding the vault open, on the grounds that nobody spends that long choosing a file. - **Importing over a file that already exists asks first** — Importing a file whose name was already taken in the destination wrote straight over it - no question, no copy kept, and nothing to undo it with. Copying inside a vault has always made a numbered duplicate instead, so the same app treated the same collision two different ways and the silent one was the one that destroyed something. Arcanum now stops at the first name that clashes and asks: keep both, skip it, or replace it. The answer covers the rest of that import, which the question says plainly - a folder of a thousand files should not mean a thousand taps. A folder whose name already exists still merges into the one that is there, the way it always did, and the summary at the end says how many files were left alone. (#157) - **A vault remembers how it was opened** — The options on the unlock screen were forgotten the moment you left it. Read-only did not survive even turning the phone, and unlocking with a fingerprint - which shows no options at all - fell back to the defaults every time: a vault you had opened read-only came back writable, and every unlock paid again for working out which hash the vault uses, which can be the difference between one second and eight. A vault now remembers what its last successful unlock used, and a fingerprint unlock opens it the same way. The hash and cipher are taken from the vault itself rather than from what was typed, so this makes unlocking quicker even if you never touched those settings. Your password, PIM and keyfiles are unchanged in where they live: still only in the fingerprint store, never beside the vault. (#148) - **Dialogs have a background in AMOLED mode** — In AMOLED mode a few dialogs and sheets drew with nothing behind them at all. The confirmation for turning off biometric unlock was see-through, and so were the ones on the change password and change keyfile screens. All of them sit on a proper surface now. - **Links made on a computer are shown as links** — A shortcut made on a computer - what Linux calls a symlink - appeared in an ext4 vault as a tiny damaged file that would not open, and exporting one could hand you a text file containing a path where the real file should have been. They are now shown as links: a link to a file opens the file, a link to a folder goes into the folder, and one pointing at something that is not in the vault says so instead of failing silently. Links written on a computer very often point outside the vault, and there is nothing there to reach - so those are marked rather than left looking broken. (#163) - **Exporting a link says what could not leave the vault** — Outside a vault there is no such thing as a second name for a file, so a link cannot leave as a link - but export used to answer that badly. A link to a folder was written out as an empty file under the folder's name, and so was a link pointing at something that is not in the vault; both were then counted as exported, so the summary said an item had left while what landed outside held nothing. A folder link now leaves as a real copy of the folder it points at, under its own name. A link that leads nowhere is skipped and counted rather than written out empty, and so is a folder link that points back into what is being exported. And when two of the names you exported turn out to be the same file, the summary says so, because outside the vault they are two separate copies taking the space twice. (#167) - **Copying or moving a link keeps it a link** — Copying a link to a folder, or one pointing at something that is no longer in the vault, used to produce a file of zero bytes under the link's name - and if you had cut it rather than copied it, the link itself was deleted afterwards, so what you moved was gone and what arrived was empty. A link is now copied as a link, keeping the same target, dead ones included. Moving anything inside a vault has also become a plain rename: nothing is read or written, so it is instant however large the file is, and a file that has two names keeps both - moving one of them used to quietly make a second separate file holding its own copy. Into another vault, or onto a FAT one, a link cannot be a link at all: copying it takes a copy of what it leads to, and moving it leaves it where it is rather than turning it into a copy, with the summary saying how many items stayed behind. (#168) - **Pasting over something that already exists asks first** — Importing a file whose name was already taken asks what to do - keep both, skip, or replace. Pasting did not ask at all: it wrote straight over whatever held the name, with nothing said before or after, and a folder pasted onto a folder of the same name overwrote the files inside it that clashed, equally silently. The same question is now asked by Paste, by Copy to and Move to, and by the files inside a folder they merge into, with one answer covering the rest of that operation. A folder itself is still not asked about, because it merges into the one that is there rather than replacing it, and copying something into the folder it already lives in still makes a numbered duplicate without asking. (#169) - **An export that could not read a file says so** — If a file could not be read to the end - a damaged vault, a drive pulled mid-export - what had already been written was left outside under the file's own name and counted as exported. Nothing about a half-written file looks half-written, so the summary said the export had gone through and what you had was part of a photo. What did come out is now kept rather than deleted, because an export is how a vault in trouble is rescued, but it is named with .part on the end so it cannot be taken for the whole file, and the summary says how many came out that way instead of showing a tick. (#170) - **An export gets out everything it still can** — If part of a file could not be read - a vault that has been damaged, a drive pulled at the wrong moment - the whole file was refused, including the part that was still perfectly readable. Reading stopped at the first thing it could not make sense of and gave back nothing at all. Now it hands over everything up to that point, which matters because an export is how you get what is left out of a vault that has gone wrong. What comes out short is still named with .part on the end and counted as incomplete, so it cannot be mistaken for the whole file. Copying and importing are unchanged and still refuse: only an export is allowed to settle for part of a file. (#173) - **An interrupted write no longer damages a file that was already there** — If the app is killed, the battery runs out or a drive is pulled while a file is being added to an ext4 vault, losing what was still being written is expected. Losing part of what the file already held is not, and it could happen - a filesystem check settled the interruption by throwing away the file's newest piece, and that piece could include data written before the operation started. The vault's bookkeeping is now written in an order that makes a check settle it the other way, and put the vault right on its own. (#164) - **A badly fragmented ext4 vault keeps taking files** — In an ext4 vault fragmented enough that one file needed thousands of separate pieces - the state a vault reaches after being filled, emptied and refilled many times - a write could be refused as though the vault were full while there was still room in it. The map that records where a file's pieces are had a ceiling it could not grow past. It grows now, the way a Linux ext4 driver does, so what stops a write is running out of space and nothing else. Nothing changed on disk: existing vaults are unaffected, and one grown this way still mounts on a Linux desktop. (#119) - **An ext4 vault made on a computer can be filled to the end** — A vault formatted as ext4 anywhere other than Arcanum - mkfs.ext4 on a Linux desktop, say - refused writes as though it were full while most of it was still empty. On a 260 MB vault it gave up after 76 MB. Formatting a volume leaves the bookkeeping for most of it unwritten, on the understanding that whichever driver first needs the space will fill that part in; Arcanum skipped those parts instead, so everything they covered was out of reach. It fills them in now, the way a Linux ext4 driver does, and the same applied to the record of which files exist, so creating files in such a vault stopped early too. Vaults created by Arcanum were never affected, and nothing about the on-disk format changes: a vault written this way still mounts on a Linux desktop. (#140) - **Folders of an ext4 vault made on a computer accept new files** — A folder that a desktop let grow past a certain size gets a hidden index to speed up name lookups, and Arcanum would not write into one: adding or renaming anything inside it failed, and on a vault made with mkfs.ext4 that was most of the folders with a lot in them. Such a folder is now rebuilt as an ordinary one the first time something is written to it, which takes a moment on a very large folder and happens once. The folder keeps everything in it and still opens on a Linux desktop; only the index is gone, and the desktop's own e2fsck -D puts it back if it is wanted. (#141) - **The path above the file list is no longer see-through** — In the ordinary theme the row of folder names above a vault's contents had no background of its own, so the list scrolled visibly through it. It now takes the colour of the bar it sits under. In AMOLED mode, where it stands on frosted glass, nothing changes. - **The calculator works turned sideways** — Rotating the phone left the calculator unusable: its buttons are circles sized from the width of the screen, so in landscape a row of four was as tall as a quarter of the screen is wide and the bottom three rows sat off the edge, digits included. Landscape now puts the display beside the keypad instead of above it, and the buttons are sized by whichever way the screen runs out first. This is also how it looks on a tablet, where sideways is the usual way round. (#124) - **The filesystem step recommends the right one, and keeps your choice** — The create wizard marked FAT as recommended for every vault it could make: the size above which it was meant to suggest exFAT had been set to two terabytes. It is now 4 GB, which is the number that makes the choice mean anything - a vault smaller than that cannot hold a file FAT would refuse, so exFAT gains nothing there and costs compatibility. Picking a filesystem by hand also sticks now: stepping back to change the size and returning replaced your choice with the recommendation, quietly, which was easy to miss on the way to creating the vault. - **No crash when a large file is picked as a keyfile** — Choosing a big file as a keyfile - a video, a disk image, anything past roughly a hundred megabytes - closed the app on the spot, with no message and nothing written down. The whole file was being loaded into memory even though only its first megabyte can ever matter: that is all VeraCrypt mixes into the password, and everything after it is ignored by every implementation. Arcanum now reads only that first megabyte, and reads it off the main thread, so a keyfile kept in a cloud or network folder no longer freezes the screen while it downloads either. Vaults and keyfiles are unaffected - the bytes that reach the volume are identical. (#136) - **Copy, Move and Paste say what they did** — With one vault open, Copy and Move put the files on a clipboard and the only sign of it was a Paste entry appearing inside the menu at the top - nothing on screen said the copy had landed, so the buttons looked broken. Both now confirm how many items are waiting and where to paste them from. A paste reports its result too: how many arrived, how many failed, and when it correctly did nothing because the files were already in that folder. A failed paste used to look exactly like a successful one. (#129) - **The video menu no longer closes by itself** — Opening the three-dot menu over a video and taking a moment to read it meant losing it: the menu belongs to the player's top bar, and the bar hides itself three seconds after it appears, taking the menu down with it. The bar now stays put while the menu is open, and starts its countdown again once the menu is closed. (#138)
• Aug 7, 2026 1.5.0
  ### New - **Create vaults as ext4** — Vaults can now be formatted as ext4, alongside FAT and exFAT, from the format step when you create one. ext4 does away with FAT's limits - there is no cap on how many files a folder holds, and it fragments far less as a vault fills - and it is a real Linux filesystem, so a vault made here mounts read-write on a Linux desktop with the standard tools, and an ext4 container made on a desktop opens here. It is not readable on Windows or macOS without a separate ext4 driver, so pick ext4 if you work on Linux or stay on the phone, and keep FAT or exFAT for the widest desktop reach. The ext4 support is a clean-room implementation written from the published on-disk format, carrying no third-party filesystem code. (#7) - **Generate keyfiles in the app** — Keyfiles can now be created inside Arcanum instead of having to bring your own file. Pick Generate keyfile from the + button on the vault list for the full options - how many, what size, and extra randomness collected from your touch - or use Generate new keyfile right in the keyfile step while creating a vault or changing its keyfiles. Files are filled with cryptographically secure random data and stay interchangeable with desktop VeraCrypt. A keyfile is only its exact bytes, so back it up like a password: lose it and the vault is gone. (#110) - **Donations** — Support the project in Settings now opens a screen of its own, with GitHub Sponsors and Ko-fi alongside addresses for Bitcoin, Lightning, Ethereum, Monero and Solana - tap one to copy it. Nothing is sent anywhere: the app has no network access, so a payment is always finished in your own wallet or browser. (#66) - **Fullscreen video** — A video wider than it is tall now has a fullscreen button in its own corner. Tapping it turns the screen so the video fills it, carrying on from the same moment, and the way back sits next to the timecode. Videos shot upright already fill the screen, so they do not offer it. Double-tap seeking got tidier too: the -10s and +10s markers now appear over the video rather than below it, a double tap no longer pulls the controls up when they are hidden, and it keeps them up when they are not. ### Improvements - **Save the last mount log for bug reports** — Debug mode can now keep the log of the most recent mount so it can be shared when something goes wrong. Turn on Save last mount log in Settings > Debug, reproduce the mount, then copy the saved log from the same screen. Previously the mount log was visible only live during mounting and could not be captured. - **Rename folders, not just files** — Folders can now be renamed: the same menu that files have is available on folder rows, with Rename and Properties. Previously there was no way to rename a folder at all, which is what led to the move-and-lose-it problem above. A folder with a dot in its name, such as photos.2026, is also handled correctly now - the full name is shown when renaming, and nothing is appended afterwards. (#113) - **Rename and Properties from the grid layout** — The grid layout offered no actions on individual items, so renaming was possible only in the list layout. Press and hold an item to select it and Rename and Properties now appear at the top, in either layout.

  More…

  - **Interface polish** — Progress and completion screens now look and behave the same everywhere - a few of them were missing their animation or their haptic entirely, which made a long operation look like a stalled one. What's New groups entries by kind, new features first and fixes last, rather than listing them in the order they happened to be written. And the password steps no longer leave an empty band of background sitting above the keyboard. - **Video thumbnails that actually show something** — A video's thumbnail was always its very first frame, so anything opening on black, on a white slate, or on a plain title card showed up in the gallery as an empty square - and every such video looked identical. Arcanum now uses the cover image stored in the file when there is one, and otherwise checks whether the first frame is a solid fill and reaches a little further into the video when it is. Videos that already had a usable first frame keep it. Existing thumbnails are regenerated once, the next time you open the gallery. (#111) - **Open a file in another app without decrypting it to disk** — Open with is now an item in each file's menu, and it no longer works by writing a decrypted copy into the cache first. The other app is handed the file straight out of the mounted vault instead, so nothing plaintext ever reaches storage, and a large video opens immediately rather than after a long wait - it used to be read into memory in full, which could fail outright on a big file. Because this route exposes the vault to the other app, it asks first if External app access is off for that vault, and you can turn it back off in the vault's settings. Any decrypted copies left behind by the old version are wiped the next time you open a vault. (#103) - **Expand Volume has been removed** — Expanding grew the encrypted container but not the filesystem inside it, and neither Arcanum nor desktop VeraCrypt can grow a FAT or exFAT filesystem - VeraCrypt warns about exactly this before expanding, and only finishes the job for NTFS, which Arcanum does not use. The added space was therefore never usable on the phone, so the action has been withdrawn rather than left looking like it worked. To get more room, create a larger vault and move your files into it, or expand the container on a desktop and extend the filesystem there. Vaults expanded by an earlier version are unaffected and keep working. - **Smoother playback progress** — The video seek bar and the audio waveform advanced in five visible steps a second, because that is how often playback position was sampled. Both now move continuously. - **Album art for music files** — Music files in the file browser now show their embedded cover art instead of a generic icon, in both the list and grid layouts. Tracks without artwork keep the icon. Opus files are also counted as music on the Storage screen now, rather than as ordinary files. - **Music files are marked as music** — A track showing its cover art now carries a small note over it, the way a video carries a play triangle, so artwork is not mistaken for a photo at a glance. ### Security - **Hardened biometric app unlock** — The fingerprint prompt that unlocks the app is now tied to a hardware-backed Keystore operation, so only a genuine biometric match can pass it. Before, the unlock relied on the prompt's success signal alone, which on a rooted or instrumented device could be driven directly to reveal the vault list (each vault stayed separately encrypted, so no vault contents were exposed). App unlock now works the same way per-vault unlock already did. (#89) - **Keyfiles never touch storage any more** — Whenever you used a keyfile - creating a vault, changing a password or keyfile, backing up or restoring a header, expanding a vault - Arcanum first copied it into its own cache folder unencrypted, and relied on deleting it afterwards. That copy is gone: keyfiles are now read straight into memory, used, and wiped, exactly as they already were when mounting. Unlocking a vault was never affected. (#116) ### Fixes - **Correct location for vaults added from the Downloads or Videos picker** — Adding an existing vault while the file picker was showing Downloads, Videos, or any section other than the device's own storage showed a meaningless location like Internal/1000000123 instead of the real folder. The vault's location now resolves correctly no matter which picker section you chose the file from. - **Open FAT32 vaults created by other apps** — Some apps (for example AndroidCrypt) format small containers as FAT32 even when they hold too few clusters to qualify as FAT32 under the spec. Arcanum's bundled filesystem rejected these with a mount failure, even though the password was correct and the same vault opened fine in desktop VeraCrypt. Arcanum now honors the on-disk FAT32 layout and mounts these vaults. - **Clear message when a storage location is read-only** — Some storage providers, such as certain network or SMB shares, let an app read a vault file but not write to it. Mounting such a vault read-write failed with a generic error. Arcanum now recognizes this and shows a clear message that the location is read-only and to mount it read-only instead, rather than an unhelpful failure, and read-only mounts of the same vaults keep working. - **No crash playing media on 32-bit devices** — On 32-bit ARM devices, playing an audio or video file from a vault could crash the app. Decryption performed unaligned 64-bit memory accesses that 32-bit CPUs reject, triggered when playback read from a position that was not sector-aligned. Reads are now aligned before decryption, so media plays without crashing. (#92) - **Keyfile vaults with very long passwords now match VeraCrypt** — When a keyfile was combined with a password longer than 64 bytes, Arcanum mixed them differently than VeraCrypt does. A vault created here that way could not be opened in desktop VeraCrypt, and VeraCrypt vaults created that way could not be opened here. The limit counts bytes rather than characters, so a password in a non-Latin alphabet crossed it at around 33 characters. Arcanum now matches VeraCrypt exactly. Vaults made by earlier versions still open - Arcanum detects the old format and retries automatically - and changing the password, or backing up, restoring or expanding such a vault, rewrites it in the correct format. Note that vaults created from now on with a keyfile and a password this long will not open in Arcanum versions older than this one. (#112) - **Moving a file or folder to where it already is no longer deletes it** — Selecting Move on an item and then pasting it into the same folder made it disappear. Arcanum copied the item onto itself and then removed the original, so nothing was left. Pasting an item into the folder it already sits in now simply does nothing, and pasting a folder into itself or into one of its own subfolders is refused instead of destroying it. Copying an item into its own folder now makes a numbered duplicate, the way other file managers do. (#113) - **Import errors now say what actually went wrong** — Every failed import claimed "Not enough space in the vault" no matter the cause, and a vault that genuinely was full was not even recognised as such - so the one problem the message named was the one it could never detect. Imports now report the real reason. One case worth knowing about: the top level of a vault formatted as FAT can hold a limited number of entries, fixed when the vault is created, and long filenames use up several each - so it can fill up after a hundred or so files while the vault itself is nearly empty. Arcanum now says so and points you at a subfolder, which has no such limit. Apps writing into a mounted vault from outside also get a proper out-of-space error instead of a generic failure. (#114) - **New vaults hold far more files at the top level** — Vaults were being formatted in a way that capped the top level at a few hundred files, no matter how much room was left inside - after that, importing failed however small the file was. New vaults are now formatted the way desktop VeraCrypt does it, so the top level grows as needed and that limit is gone. Space is used more efficiently too: small files waste much less room than before. This applies to vaults created from now on. Existing vaults keep the old layout, so if you have hit the limit in one, moving files into subfolders will get you going again, or recreate the vault to be rid of it. (#115) - **Storage no longer shows free space that isn't there** — The Storage screen took a vault's size from the volume header rather than from the filesystem inside it. Those are the same number until a vault is expanded, after which the header grows but the filesystem does not - so an expanded vault could report gigabytes free while refusing to accept a single file. Sizes now come from the filesystem, and where a vault's volume is larger than the filesystem in it, the screen says so instead of leaving two screens quietly disagreeing. - **Clean icons in the storage chart** — The icons drifting through the ring on a vault's Storage screen were drawn with visible streaks and distortion, and some came out looking nothing like the icon they were meant to be. They are now drawn from a single crisp copy of each icon, and they are also kept clear of the edges of their slice, so a thin slice no longer trims them down to a sliver. - **Runs on devices with 16 KB memory pages** — The encrypted-database library shipped with Arcanum was built for 4 KB memory pages. On a device using the 16 KB page size that newer Android versions support, it could not be loaded at all, and the app died on startup as soon as it touched its database. It has been replaced with a build that handles both. Your data is untouched - the database format is identical and existing vaults open as before. (#45) - **Storage figures keep up with changes** — The Storage screen worked its numbers out once and then held them, so importing or deleting files left it showing the old breakdown until the vault was unmounted and mounted again. It now updates as files change, and recounts whenever the tab is opened.