Tiny Journal (M5Stack Cardputer)
V. 2026.11.14
Write on the go with your Cardputer.
Tiny Journal is a distraction-light journalling and notes app for the M5Stack Cardputer. Write on its own keyboard, or pair a Bluetooth keyboard when you have a little more space. Your notes are ordinary UTF-8 text files on the SD card, so you can take them elsewhere whenever you like.
There are templates, audio notes, a choice of text sizes and colours, optional Google Drive backup, and plain-text network printing. You don't need Wi-Fi or a Google account to write.
Getting started
- Fit a FAT32 microSD card and start Tiny Journal.
- Set the date and time under Settings → Date & time before making dated notes. The saved clock is a software clock, so check it after a power-off.
- Start typing. On a fresh card, the app creates the journal folders and a blank note. Later starts reopen your last document.
- Press Esc (
Fn + backtick on the Cardputer) to open the Main menu.
- Use Writing menu → Text documents to create a blank note, a daily entry, a note from a template, or open an existing document.
Notes save when you leave or switch documents, and after an idle period if idle autosave is enabled. The default is five seconds. A failed save keeps the unsaved indication; don't switch off until you've dealt with the error. Sudden power loss can still lose recent changes, so keep a separate backup of your SD card.
A copy of this guide is installed as /journal/README.txt. Choose Read user guide in the Main menu to read it on the Cardputer. The reader does not edit your note. Up/Down (or ;/.) changes page; Enter or Esc returns. The app refreshes its own guide on upgrade; keep personal notes in the document folders. A pre-existing, unrecognised README is preserved and the guide is put in /journal/Tiny-Journal-README.txt instead.
Keys and navigation
On the built-in keyboard:
| Keys | What they do |
| --- | --- |
| Fn + ; / . / , / / | Up / down / left / right in the editor |
| Opt + , / / | Jump to the previous / next word |
| Opt + ; / . | Page up / down |
| Opt + Del | Delete the previous word |
| Fn + Del | Delete the next character |
| Opt + Tab | Record an audio note |
| Ctrl + Space | Change layout in the editor or Bluetooth settings |
| Ctrl + Z / Y | Undo / redo |
| Ctrl + F | Find text; search is case-sensitive and wraps forward |
| Fn + backtick | Esc: open the menu or return to the editor |
In ordinary menus, ; and . move the selection, Enter selects and Del goes back. Long lists have a scrollbar. A selected item that is too wide scrolls sideways; the rest of the screen stays still.
An external keyboard supports arrows, Page Up/Down, Home/End, Ctrl+Home/End, Ctrl+Left/Right, Ctrl+Backspace/Delete, and the editing shortcuts above. Escape opens or backs out of menus. Ctrl+Space also changes layout in external-keyboard menus.
The document and audio browsers accept W/S or ;/. for navigation. Enter opens a document or plays a recording. In the document browser, d renames the selected document. In the audio browser, d deletes the selected recording and Shift+D requests deletion of the listed recordings (the browser lists up to 64). The storage tools can delete all recordings. Bulk deletion requires confirmation.
Make it comfortable
Under Settings → Appearance, choose green, amber or white on black, or black on white.
Editor text cycles through Standard, Medium 1.4×, Large 2×, and Extra large (the original cataracts mode). Menu text has its own Standard / Medium / Large setting. The small help text at the bottom stays small.
Under Settings → Editor behaviour, choose anchored or classic cursor scrolling and idle autosave: Off, 1, 2, 5 or 10 seconds.
Undo/redo history is limited to 32 KiB; individual snapshots over 16 KiB are not kept. Documents have a 128 KiB limit and a limit on wrapped lines and available memory. Files that are too large are refused rather than partly loaded. Splitting a long document into smaller notes helps.
Bluetooth keyboards and layouts
Go to Settings → Sync & connectivity → Bluetooth keyboard. Put the keyboard into pairing mode, select Scan / pair keyboard, then choose it from the list. Follow any passkey or confirmation prompts on the screen. Select an unused pairing channel on multi-device keyboards if you want to keep their other pairings.
This is Bluetooth Low Energy HID support. The ESP32-S3 does not support Classic Bluetooth keyboards. A keyboard being wireless does not necessarily mean it supports BLE; compatibility depends on its connection mode and HID reports. The ProtoArc XK01 TP has been the target for local testing, but there is no guarantee for every keyboard or every key.
Available layouts are US, UK, German, French, Spanish and Russian. Select Layout and press Enter, or use Ctrl+Space. Caps Lock, AltGr and common dead-key combinations are supported. Latin and Cyrillic text are supported; CJK input methods, Arabic shaping and full emoji editing are not.
Bluetooth settings also include:
- Bluetooth On/Off: manual Off is remembered across restarts. Saved bonds are kept.
- Power-on connect On/Off: independently controls automatic connection to a remembered keyboard. Turning this off does not disconnect a working keyboard.
- Forget saved keyboard: removes the saved pairing.
Automatic connection gets three attempts. If all three fail, Bluetooth shuts down for that attempt cycle. It can try again on the next boot if Bluetooth and power-on connection are enabled. A dropped working connection starts another bounded reconnect cycle. With automatic connection disabled, use Scan / pair keyboard when you want to connect.
Audio notes
Press Opt+Tab, or use Writing menu → Audio notes → Record new note. Any key stops recording. Use the audio browser to play recordings back.
Recordings are WAV files in /journal/audio. The app also recognises /journal/audio/export for files placed there; there is no separate automatic export step. Interrupted recordings may be recovered from .wav.part files on the next normal boot.
Moving files over USB
Choose Enter USB storage mode in the Main menu. The app saves first, restarts into storage mode, and makes the SD card available to the computer.
Eject the disk on the computer before pressing a Cardputer key to leave storage mode. While the computer owns the card, the journal does not edit it. An empty removable device can appear during normal journal use; the card becomes available only in storage mode.
USB serial reboot requests are ignored during storage mode. Leave storage mode before uploading firmware. If discovery fails, check the cable supports data and that the computer sees the Cardputer; the storage screen alone is not proof of a successful connection.
Wi-Fi and Google Drive
Wi-Fi setup is under Settings → Sync & connectivity → WiFi setup. Scan, choose a network, enter its password and save it.
Google Drive is optional upload backup, not two-way synchronisation. It uploads notes and WAV files from both audio folders. It does not download edits made in Drive. Changed files update their tracked remote copy; unchanged files are skipped. Duplicate files created by older firmware are not automatically removed.
For Drive, you need your own Google OAuth client, a refresh token and a destination folder ID. Put these four lines in /journal/config/gdrive.cfg:
YOUR_REFRESH_TOKEN
YOUR_CLIENT_ID
YOUR_CLIENT_SECRET
YOUR_DRIVE_FOLDER_ID
This takes more setup than Wi-Fi alone. You can skip it and use USB instead. When configured, choose Settings → Sync & connectivity → Sync now.
Connections to Google verify TLS certificates. The clock must be valid; the app requests network time when needed and stops if it cannot establish a verified connection. It does not fall back to an insecure connection.
Credentials are plain text on the SD card. TLS protects their connection to Google, not a lost card. Don't share your config files or include them in bug reports. Keep /journal/config/drive with your backups: its remote IDs and hashes are what let later uploads update existing files safely. A missing or inaccessible remote file reports an error rather than silently creating another copy.
Network receipt printing
Use Settings → Sync & connectivity → Network printer setup. Enter your printer's own address and port (usually 9100), set its paper columns, then send a test receipt. Wi-Fi credentials must already be configured.
The printer needs to accept plain-text ESC/POS over TCP. USB-only and Bluetooth-only printers are not supported by this feature. Set the address for your own network; no personal printer address is built into the firmware.
Print current note saves first and sends a snapshot. Optional Print on Enter sends completed logical lines as you type. Completed receipts feed and cut by default; switch cutting off for a printer without a cutter. Live lines do not cut. Later edits cannot change paper already printed.
The stream selects CP437, including UK £ and common Latin accents. Unsupported characters become ?; printer text support is narrower than the editor's language support. Print jobs are limited to a total 32 KiB queue. A send error may leave a partly printed receipt, so check the printer before retrying. “Job sent” means the data was sent, not that paper definitely came out.
Raw network printing is unencrypted. Use it on your trusted local network and keep the printer port off the public internet.
SD folders, templates and backups
/journal/
README.txt
config/
wifi.cfg
gdrive.cfg
theme.cfg
btkeyboard.cfg
printer.cfg
rtc.txt
lastfile.txt
CONFIG-README.txt
drive/
templates/
daily/
notes/
meetings/
projects/
travel/
misc/
archive/
audio/
export/
Older root-level config files are migrated into config when possible. Wi-Fi configuration is two lines: SSID, then password. Printer configuration is JSON; use its menu unless you want to edit it yourself.
Templates live in /journal/templates and support {{DATE}}, {{TIME}} and {{DATE_LONG}}. Use the supplied templates as examples for creating your own. Up to 32 templates are listed; each file must fit the document limit. Keep metadata lines below 512 bytes and the leading metadata header below 4 KiB. Oversized templates are refused.
A checked save writes and verifies a temporary file, keeps the prior revision as .bak, then installs the new file. Boot recovery handles interrupted replacements. The .bak is normally one revision old, not a full history. Back up the entire journal folder, including config and Drive tracking, somewhere separate from the SD card.
Settings → Storage & SD tools includes deletion and reset tools. Read each confirmation carefully: deleting notes or resetting the journal is a fresh start, not a backup operation. Unrelated files outside the journal are preserved.
Building from source
Tested hardware is the original M5Stack Cardputer (ESP32-S3) with a FAT32 microSD card. Other Cardputer variants have not been validated in this release.
Use Arduino IDE 2.x and these tested dependencies:
| Component | Version |
| --- | --- |
| M5Stack ESP32 board package | 3.2.2 |
| M5Cardputer | 1.1.1 |
| M5Unified | 0.3.0 |
| M5GFX | 0.3.0 |
| NimBLE-Arduino | 2.5.1 |
| ArduinoJson | 7.4.3 |
The M5Stack board index is https://static-cdn.m5stack.com/resource/arduino/package_m5stack_index.json.
git clone https://github.com/joejee90/Tiny-Journal.git Tiny_Journal
cd Tiny_Journal
Open Tiny_Journal.ino, keeping all the accompanying .h and .inl files in the same sketch folder. Select M5Cardputer, 8 MB flash, Huge APP (3 MB), USB-OTG/TinyUSB, USB CDC On Boot enabled, and USB-OTG CDC upload. Keep Erase All Flash disabled when retaining settings and bonds. Verify, select the port and upload.
Board package 3.3.10 was compared on the test Cardputer and produced invalid microphone capture. This release therefore uses 3.2.2. That result is specific to the tested hardware and library combination; “latest” is not the tested configuration here.
For Arduino CLI, tools/setup-review-build.sh installs the pinned dependencies into a separate sibling toolchain and builds the sketch. tools/build.sh uses already-installed dependencies. tools/test.sh runs the host regression checks. Python 3 and a C++17 compiler are needed for the checks. tools/generate-guide.py --check verifies that the embedded guide matches this README.
See VALIDATION.md for checks performed and remaining hardware acceptance work, and NETWORK-AND-PRINTING.md for network details. Some behaviour, especially Google account sync and keyboard compatibility, still needs testing with the actual account or hardware involved.
Changes in V. 2026.11.14
- Added Medium 1.4× editor text, separate menu sizes and the two-pixel editor margin from TenoTrash's PR #4.
- Added menu scrollbars, scrolling long selections, buffered row-only animation and small help text.
- Expanded BLE keyboard/report handling, layouts, pairing controls and bounded reconnection.
- Added undo/redo, search and bounded document loading.
- Added checked saves, interrupted-save/recording recovery and stronger storage transitions.
- Repaired USB interface registration and protected storage mode from serial-triggered reboots.
- Added verified Google TLS and remote-file tracking for safer upload retries.
- Added configurable network receipt printing, live lines and optional cutting.
- Added this on-device guide and the release-review safety fixes documented in validation.
Licence
This project uses the same basic licence terms as the Cardputer Camera Companion project:
- You may clone, fork, and modify the source code for your own personal, non-commercial use.
- You may not sell:
- compiled binaries of this firmware, or
- devices with this firmware pre-installed,
without explicit permission from the author.
- You may share forks and modified versions non-commercially, as long as:
- this licence notice (or an equivalent) is kept, and
- it is clear that your fork is unofficial and not supported by the original author.
- The software is provided “as is”, without any warranty of any kind. You use it entirely at your own risk.
In particular:
- The Wi-Fi and Google Drive sync features are experimental.
- There is no guarantee against bugs, crashes, or data loss.
- The author accepts no responsibility for:
- lost or corrupted notes,
- damaged SD cards,
- failed or partial syncs,
- or any other problems arising from use of this firmware.
If you want to use Tiny Journal (or any substantial part of its code) in a commercial context, please contact the author first.