Repository navigation
Releases
MemoCtrl 0.4.11
What's new
Security
- Saved logins are protected by the phone's secure chip where it has one. On a fresh install (or after clearing MemoCtrl's data), the key that encrypts your access tokens is now created in the phone's StrongBox secure element when the phone has one, and in the normal Android Keystore otherwise. If you already use MemoCtrl nothing changes for you: your existing key keeps working and you stay signed in.
Project
- The Gradle wrapper download is now checked against its published SHA-256 checksum before a build runs.
Full diff: v0.4.10...v0.4.11
SHA-256: 07f8b3f688a1f29a9f4e8205e2771d29592ba992bd479c29acdc989dd967508d MemoCtrl-v0.4.11.apk
MemoCtrl 0.4.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 MemoCtrl 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.
Full diff: v0.4.9...v0.4.10
SHA-256: 0ab0b7c5c0cbca36bcc1f5e5d229ee1de6ff2f9d81e629941739697cfbd95b56 MemoCtrl-v0.4.10.apk
MemoCtrl 0.4.9
What's new
MemoCtrl now needs Android 15 or newer.
Changed
- Needs Android 15 or newer. Android 13 no longer gets security updates and Android 14's end early 2027, so MemoCtrl 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.4.8...v0.4.9
SHA-256: be6d713f459d0c3291bda1dc49aefe2550e7f4bc2c50de77ac05594e18271724 MemoCtrl-v0.4.9.apk
MemoCtrl 0.4.8
What's new
Password managers work on the sign-in screen again.
Fixed
- Password managers can fill the sign-in screen (address, username, password or access token) again. 0.4.7 hid it from every app that reads the screen through accessibility, which also blocked password managers that fill that way; now only the lock screen, the PIN screens and "Forgot PIN?" are hidden from them. Other apps' floating windows are still kept off the sign-in screen, and screen readers such as TalkBack keep working everywhere.
Full diff: v0.4.7...v0.4.8
SHA-256: fa0c32e387cd6a9741800288053cc708abbb45b4c122c71feb0c6104d81043a3 MemoCtrl-v0.4.8.apk
MemoCtrl 0.4.7
What's new
More protection for the PIN screen and for what other apps hand to MemoCtrl. MemoCtrl works exactly as before.
Security
- No floating windows over the PIN screen. While the lock screen, choosing or changing the app PIN, the sign-in screen or a "can't be undone" confirmation (Forgot PIN, sign out, remove, delete) is showing, other apps' floating windows such as chat heads and "draw over other apps" overlays are hidden, so no app can cover or imitate these screens to trick a tap or watch your PIN. They come back as soon as the screen closes, and other screens aren't affected (Android 12+, no prompt).
- The PIN and sign-in screens are hidden from apps that read the screen. On Android 14+, apps that use Android's accessibility features to read other apps' screens can't see the lock, PIN or sign-in screens. Real accessibility tools such as screen readers still work there.
- Shared pictures must really belong to the app sharing them. On Android 15+, Android itself now refuses a share to MemoCtrl when the sending app passes along a picture it isn't allowed to open itself, so another app can't use MemoCtrl to get at files it has no access to. Sharing from your gallery, camera or files app works as before.
- Stricter app shortcuts and links from other apps. On Android 16+, other apps can only open MemoCtrl with the actions it declares (opening the app, sharing to it, the "New memo" shortcut and the widgets), not with made-up requests aimed directly at its screens.
Project
- Checked downloads: every library and plugin the build downloads is now checked against its recorded SHA-256 checksum, and the build stops if one doesn't match.
- README: a "Check a download" note (the APK's SHA-256 in the release notes and
gh attestation verify), the new permission in the permissions table, and how to update the dependency checksums when building from source.
Full diff: v0.4.6...v0.4.7
SHA-256: 77bd29a8e83979f323fbfb664e569f60e64e1d84b92e8e1dda6be1f2d6c9581f MemoCtrl-v0.4.7.apk
MemoCtrl 0.4.6
What's new
A small security fix. MemoCtrl works exactly as before, including plain HTTP to your own Memos server on your home network or over Tailscale.
Security
- A redirect can no longer move an unencrypted connection to another server. Plain HTTP is only used for a Memos server address you chose after the "unencrypted" warning. Until now that check looked only at the address a request started at, so if your server (or something between you and it) answered with a redirect to a different address, MemoCtrl followed it over plain HTTP. Every step of a redirect now has to be an address you allowed for HTTP; otherwise the request stops with the "blocked an unencrypted connection" error. Redirects within your own server, and redirects up to HTTPS, keep working.
Full diff: v0.4.5...v0.4.6
MemoCtrl 0.4.5
What's new
A security and privacy check of the whole app and its repo. MemoCtrl works exactly as before.
Security
- Release builds no longer write debug or info messages to the phone's log, from MemoCtrl or from the libraries it uses. MemoCtrl itself never logged your memos, server address or token, and now nothing from its libraries ends up there either.
- One less entry point for other tools. A receiver that the baseline-profile library adds for adb and app-store tooling is removed. Only the system could use it, but MemoCtrl doesn't need it.
Project
- Build checks: every build now verifies that the Gradle wrapper is an official Gradle release, and checks that no Google Play services, Firebase, ML Kit, Play Core or Tink library has made it into the app.
- Repo: signing keys, keystore settings and Google service files are ignored by git, so they can't be committed by accident.
- README: the permissions table now lists every permission the app has (network state, keeping the phone awake during a sync and setting sync up again after a restart were only mentioned in a sentence), the Privacy section says MemoCtrl is Google-free and has no update check, and the Ctrl series list has every app in the series, including CallCtrl, ClockCtrl, ContactCtrl, DateCtrl, LijnCtrl, MailCtrl, RecorderCtrl and TextCtrl.
Full diff: v0.4.4...v0.4.5
MemoCtrl 0.4.4
What's new
Safer handling of pictures and attachments from the server, and a friendlier GitHub page.
Security
- Pictures in a memo are only loaded from web addresses. A picture in the memo text that points to a file on the phone (a
file:orcontent:address) or any other non-web address is no longer loaded; it shows as a link instead, like pictures from other websites. - Attachment links from the server must be web addresses. An attachment whose external link isn't an
http://orhttps://address is now treated as a normal file on your Memos server, so a memo can never make MemoCtrl open, share or show a file from the phone. - Attachment file names are cleaned in full when an attachment is downloaded to open it in another app, so an odd name sent by the server can't end up outside MemoCtrl's own folder.
- Only MemoCtrl's own attachment files are kept during sync. When syncing, an attachment's saved copy on the phone is only reused, opened or uploaded if it's inside MemoCtrl's private attachments folder. A file address left behind by an older version that points anywhere else is ignored, and the attachment is downloaded from your server again when needed.
Project
- New SECURITY.md: how to report a security problem privately, and the release key's fingerprint.
- New issue forms for bug reports and feature requests, with a reminder to remove server addresses, tokens and personal info.
- README: clearer install steps for people new to GitHub, a new "Is it safe to install?" section with every permission explained, "How MemoCtrl is made", the full Ctrl series list, and the empty Screenshots section removed.
Full diff: v0.4.3...v0.4.4
MemoCtrl 0.4.3
What's new
Fixed
- Bottom sheets no longer show a stray grey box or outline. Sheets that slide up from the bottom had a thin grey rectangle drawn partway down the open sheet, sometimes cutting across the first row, plus a stray rounded outline near the top of the screen. The outline was drawn at the sheet's starting position rather than where the sheet actually is. Sheets are now a plain surface with rounded top corners and no outline; the dimmed background already sets them apart. This fixes every bottom sheet in MemoCtrl:
- the ⋮ menu of a memo (pin, edit, share, copy, archive, delete…)
- choice sheets in Settings (Lock again, Edit gesture) and in the widget setup (tag, number of memos)
- the visibility picker in the editor (Private, Protected, Public)
- Dialogs keep their thin border, and popup menus keep the flat look from 0.4.2. Nothing else about how sheets work has changed.
Full diff: v0.4.2...v0.4.3
MemoCtrl 0.4.2
What's new
Fixed
- Popup menus no longer show a grey box. The tag picker in the editor (the # button: "New tag" and your existing tags) had a grey, square-ish shadow edge around it, most visible in light mode. It's now a flat Signal surface (white in light mode, graphite in dark mode) with 16dp rounded corners, a thin card border and no shadow.
- Menu text and icons follow the theme: menu entries use the normal text colour, icons the grey secondary colour, and disabled entries are greyed out, in both light and dark mode.
- All popup menus in MemoCtrl now share this one style, so any menu added later looks the same. Nothing else about how the menus work has changed.
Full diff: v0.4.1...v0.4.2