Repository navigation
Releases
TrueCtrl 0.17.0
What's new
This release encrypts some of what the app stores on the phone. An older version cannot read it afterwards, so export or back up anything you need before you update (details below). Built and checked by CI only: nothing in this release had been run on a phone when it was published.
Security
- Encryption at rest for what TrueCtrl keeps about your servers. These files are now stored encrypted on the phone: the offline copies for each server (
cache/overview-<server>.json,storage-,datasets-,protection-andsharing-<server>.json: system details, alerts, pools, disks, dataset names, snapshot and backup tasks, shares and connected SMB sessions) and the notes the background checks keep for each server (notify/<server>.jsonanddisk-health/<server>.json: which alerts, failures and disk problems were already notified, when the last check ran). They're sealed with AES-256-GCM under a random 256-bit data key. That key is stored indata.keyin the app's private storage, itself encrypted by a key in the Android Keystore that can't be exported (made in the StrongBox security chip when the phone has one). It needs no PIN or fingerprint, so background checks keep working while the phone or the app is locked. It has nothing to do with the app lock, and the key that encrypts your saved sign-ins is not touched. - What this protects, and what it doesn't: a copy of the app's files taken off the phone (a backup image, a forensic copy, another app that got hold of the files) no longer shows your guests, storage and check history in readable form. It does not protect against something that controls TrueCtrl while it runs: the data key is in the app's memory then.
- Moving over is automatic and can't lose anything that matters. The first time the updated app starts, each existing file is sealed in the background: the sealed copy is written next to it and synced to storage, read back, decrypted and compared byte for byte, and only then moved over the original in one step. If anything fails, or the app is stopped halfway, the original file stays in use and it's tried again at the next start. New saves are sealed from then on. Files of both kinds are read, so nothing changes on screen.
- If the key is ever lost (the Keystore key is gone, or a sealed file is damaged), a sealed file can't be opened. Because everything in these files comes from your TrueNAS, TrueCtrl then treats it as "nothing saved": the file is deleted and the data is read from the server again at the next refresh. For the background check that means it starts fresh, so a warning that is still true can be notified once more. Nothing is asked and nothing on your server changes. The
data.keyfile itself is never replaced; while it can't be read, TrueCtrl goes on saving ordinary files exactly as before this change. The same happens on a phone whose Keystore doesn't work at all. - Not encrypted, on purpose:
- The list of servers (name, address, user name, certificate fingerprint) and which server is open: plain settings that are read at once on the main thread when the app starts, before anything can be drawn. Sealing them would put the secure hardware in that path and slow every start down, or show the set-up screen for a moment while the key loads. API keys, passwords and the ntfy access token in the same file were already encrypted and are not touched.
- The push registration with ntfy (the push address and the secret token that proves a message comes from ntfy): read at once, on the main thread, every time ntfy hands over a message. If it couldn't be read, push would stop until TrueNAS's alert service is set up again, so it stays as it was.
- Settings (theme, notification and disk-health choices, the ntfy server and topic for disk warnings, app lock choices) and the small note that the app lock is off: not content, and the note has to be readable at once at start.
- The app lock's vault: already encrypted, not touched.
- The method list TrueCtrl remembers between reconnects: only ever in memory, never on storage.
- WorkManager's own database (Android's schedule of the background checks): a database of the library, not TrueCtrl's content.
- No going back to an older version with these files: TrueCtrl 0.16.0 and older can't read sealed files. If you install an older version over this one, it finds nothing it can read and starts without the offline copies and with a fresh background check (it reads everything from the server again); it does not crash on them as far as the code shows, but that was not tried. There is nothing to export first: your servers and sign-ins are stored as before and are not affected.
- What you might notice: nothing, apart from the points above. The first Keystore use happens in the background, so on phones with a slow security chip the last known state can appear a moment later after a cold start.
Full diff: v0.16.0...v0.17.0
SHA-256: 3f5c4555ba57891a050ca3738a812e60ecff8b7c036cf479bd4630e1bc87a41a TrueCtrl-v0.17.0.apk
TrueCtrl 0.16.0
What's new
Built and checked by CI only: nothing in this release had been run on a phone when it was published.
Removed
- Home-screen widgets: the TrueNAS pools and TrueNAS alerts widgets are gone. After updating, Android removes them from your home screen (or shows them as unavailable; remove them by hand). The Overview in the app still shows pool health and usage, alerts and what needs attention.
- Quick Settings tile: the TrueNAS tile is gone.
- Their saved data: the summary the widgets and the tile kept for each server (server name, pool names, health and alert counts, in a file called
health.json) is deleted the first time the updated app starts, and is no longer written after each refresh and background check. Notifications and background checks themselves are not affected.
Performance
- Faster start without the app lock: at start TrueCtrl read its settings store on the main thread, before the first screen, to know whether the app lock was on. It now keeps a small note that the lock is off and reads that instead. When there is no such note (the first start after this update, or when the lock may be on) the setting is read exactly as before, so the app still never shows unlocked for a moment. With a PIN set nothing changes: the PIN vault already answered at once.
- Faster reconnects: every time TrueCtrl came back on screen it downloaded the full method documentation of 24 parts of the TrueNAS API (
core.get_methods) to know what your sign-in may do. That list is now remembered while the app runs and reused as long as TrueNAS reports exactly the same version and your user the same roles and shell permission; otherwise it's read again. It's kept in memory only, never on storage, and the Retry button always reads it again. - One request less per reconnect: the check of the address (
GET /api/versions) is done on the first connect and whenever the connection can't be opened, instead of before every reconnect. The first connect to a server, setting up a server and the error messages are unchanged. - Pinned certificates: the secure connection setup for a server with a pinned (self-signed) certificate is no longer done on the main thread at start.
- App catalog: the search and category filter is no longer worked out again on every redraw, the app icon on an app's page is decoded at the size it's shown instead of up to 1280 pixels, and images reuse one download client instead of building a new one each.
Full diff: v0.15.0...v0.16.0
SHA-256: fb7fdafb8cad85ad0a48f6c9afd55185790f0fb3cdae5e7ce3239d13decf7459 TrueCtrl-v0.16.0.apk
TrueCtrl 0.15.0
What's new
New
- Update all apps: System › Apps shows Update all apps when apps have a newer version. It lists them with the version you have and the new one, all ticked; untick the ones to leave alone, then tap Update (the ticked ones) or Update all, and confirm. TrueCtrl updates them one after another and shows each upgrade's own progress (pulling images and so on), what's waiting, done or failed, and a summary at the end. A failed app doesn't stop the others. You can leave the screen meanwhile; Stop after this app lets the running update finish and skips the rest. It needs the APPS_WRITE role, as single upgrades do.
- Search and copy in app logs: the live log of an app's container now has a search button that shows only the lines containing your text, highlighted, with how many match, and a copy button that copies the log (or only the matching lines). Logs are kept out of clipboard previews, as they can contain tokens or addresses.
- Disk health warnings (Settings › Notifications › Disk health, off until you turn them on): a separate background check, every 15 minutes to once a day, of pool status, the state and read/write/checksum errors of every disk in your pools, SMART self-test results (TrueNAS 25.04) and TrueNAS's disk alerts (SMART, disk temperature, pool status). Each new problem is notified once, problems already there when you turn it on included, and the notification goes away once it's fixed. Check disks now runs it at once, and each server shows when it was last checked and how many problems it found.
- Disk warnings to your ntfy server (optional, off by default): new disk warnings can also be posted to a topic on your own ntfy server, for your other devices. Enter the server, the topic and, if needed, an access token (stored encrypted, only sent over HTTPS), and tap Save and send a test. A self-signed certificate is shown with its fingerprint and pinned once you trust it.
Changed
- Longer app logs: the log screen now keeps the last 5,000 lines instead of 2,000, says when older lines were dropped, and cuts single lines longer than 4,000 characters.
- With Disk health on, the general background check no longer notifies pool status and SMART alerts itself, so you don't get them twice.
Full diff: v0.14.11...v0.15.0
SHA-256: 58323cc01c32c8c750505c7547210cae5ef7a87d6cb2cd042cdd3727406f16b6 TrueCtrl-v0.15.0.apk
TrueCtrl 0.14.11
What's new
A security and privacy check-up. Nothing works differently, and you don't need to sign in again.
Security
- Sign-ins in the phone's security chip: on phones with StrongBox (a separate security chip, such as Titan M on Pixels), the key that encrypts your saved API keys and passwords is now made inside that chip, and falls back to the normal Android Keystore on phones without one. This applies when the key is first made (a new install, or after clearing TrueCtrl's data); sign-ins you already saved stay encrypted with the key they have.
- Checked build tools: the build now also checks the SHA-256 of the Gradle build tool it downloads, as it already did for every library.
Performance
- Reading a saved sign-in no longer opens the Android Keystore again each time, so background checks and the widgets connect a little sooner.
Full diff: v0.14.10...v0.14.11
SHA-256: 9d6acd14ce4908c8daac3e4051043da44058fee95088a0de275dd1075978d665 TrueCtrl-v0.14.11.apk
TrueCtrl 0.14.10
What's new
Changed
- Slightly smaller download. The bundled JetBrains Mono font (numbers, readouts and labels) no longer carries the Cyrillic, Vietnamese and maths-alphabet letters TrueCtrl never shows itself, which takes about 0.1 MB off the download and 0.2 MB off the installed app. Everything looks the same; if a name or a log line shown in that font uses one of those scripts, those letters are now drawn with your phone's own font.
- One font file for Space Grotesk instead of four. Regular, Medium, SemiBold and Bold now all come from one variable font file, which takes about another 0.15 MB off the download. Text should look the same as before.
Full diff: v0.14.9...v0.14.10
SHA-256: 4a0ed67ef794f67d50196e56845eceb0fa21f4e3ded64ea9a30eda5f608fd2d4 TrueCtrl-v0.14.10.apk
TrueCtrl 0.14.9
What's new
Changed
- Needs Android 15 or newer. Android 13 no longer gets security updates and Android 14's updates end in early 2027, so TrueCtrl now supports Android 15, 16 and 17 only. On older phones the version you have keeps working, but it won't get updates.
Full diff: v0.14.8...v0.14.9
SHA-256: c94870b1e486b0f8fc6b36bf7587cfb972c95ee53e67fddb812239df87654467 TrueCtrl-v0.14.9.apk
TrueCtrl 0.14.8
What's new
Fixed
- Password managers can fill your sign-in and secret fields again. Since 0.14.7 the server sign-in (API key, password, one-time password), the dataset passphrase and secret fields in app install forms had been hidden from every accessibility service that isn't a screen reader, which also kept password managers that fill through accessibility from filling them. Only the lock and PIN screens are hidden from those apps now. Other apps' floating windows stay hidden over all of these screens, as in 0.14.7.
Full diff: v0.14.7...v0.14.8
SHA-256: b4f1bf5ac1b028e891a908d2347890b96e8d03994c492ddbc950046900279d58 TrueCtrl-v0.14.8.apk
TrueCtrl 0.14.7
What's new
A security update. Nothing changes in how TrueCtrl works.
Security
- No other app's floating window over the PIN, key and confirmation screens. While the lock screen, PIN entry or change, "Forgot PIN?", the server sign-in (API key, password, one-time password), the dataset passphrase, an app install form with secret fields or a confirmation (like deleting a dataset) is showing, Android hides other apps' floating windows (chat heads, screen filters, overlays), so none can cover the screen or trick you into tapping the wrong button. They come back as soon as that screen closes and work as usual everywhere else, including in the shell. This uses Android's "hide other apps' floating windows" permission, which is granted at install without a prompt.
- PIN, key and passphrase screens are hidden from apps that misuse accessibility (Android 14 and newer). Real accessibility tools such as TalkBack still read them; other apps with accessibility access can't see the PIN pad, the API key, password or one-time password fields, or a dataset passphrase.
- Stricter intent matching (Android 16 and newer). Other apps can only start TrueCtrl through the actions it declares. The launcher, the widgets, the Quick Settings tile and push from ntfy work as before.
Project
- Verified dependencies: every library and plugin the build downloads is now checked against SHA-256 checksums in the repo, and the build stops if anything doesn't match.
- Provable releases: from this release on, the release notes list the APK's SHA-256, and each APK has a signed build provenance attestation from GitHub. The README's "Is it safe to install?" section shows how to check both.
Full diff: v0.14.6...v0.14.7
SHA-256: 4df9d60e426506f67f2e0f9af0c40c93773895187d7e7db14f340b90c93f03c5 TrueCtrl-v0.14.7.apk
TrueCtrl 0.14.6
What's new
Security
- Widgets and the Quick Settings tile no longer show your server while TrueCtrl is locked. With the app lock on, the TrueNAS pools and alerts widgets and the TrueNAS tile used to keep showing the server name, pool health and usage, and the number of alerts on the home screen and in Quick Settings, even while TrueCtrl itself asked for the PIN. Now, while the app lock is locked, they only say that TrueCtrl is locked. That also applies as soon as your Lock again time has run out while you were away, even before you open TrueCtrl again. They show the last check again the moment you unlock, and tapping them still opens TrueCtrl.
- Background checks and notifications work exactly as before while TrueCtrl is locked.
Project
- Build checks: every build now verifies that the APK is signed with TrueCtrl's own release key, so a build signed with any other key can never be published as an update.
- README: the App lock section now says that widgets and the tile only say "TrueCtrl is locked" while the app is locked.
Full diff: v0.14.5...v0.14.6
TrueCtrl 0.14.5
What's new
A privacy and security check-up: one permission fewer and a stricter build.
Privacy
- One permission fewer: TrueCtrl no longer asks for "run foreground service". A background library added it for long-running work that TrueCtrl never starts, so it was never used. Your list of permissions in Android's app info is now one shorter.
- Release builds no longer write debug and info messages to the phone's log, including any from the libraries TrueCtrl uses. TrueCtrl's own code never logged anything.
Project
- Stricter builds: every build now checks that the Gradle wrapper is the official one, and checks that no Google library (Play services, Firebase, ML Kit) has slipped in through a dependency.
- README: a full permissions table with what each permission is for, a note that the shell uses a locked-down web view that only loads the terminal built into the app, the ntfy link under Privacy, and the Ctrl series list with all 28 apps.
Full diff: v0.14.4...v0.14.5