Firmware Updates over Wi-Fi and from the SD card
Install new firmware without a USB cable. Push it from the PC over Wi-Fi, or drop it on the SD card. Unsigned images are refused, and a broken update rolls back by itself.
The plan of each stretch of work: the goal, the decisions made in the design round, what done means, and what was measured. Generated from docs/milestones/ in the repository.
Each milestone starts with a design round of numbered questions, each with a recommended answer to accept or overrule, then a list of what "done" means, and ends with what was actually measured on the device. They are listed in the order they were done. Generated from docs/milestones/ in the repository: edit those files, not these pages.
Install new firmware without a USB cable. Push it from the PC over Wi-Fi, or drop it on the SD card. Unsigned images are refused, and a broken update rolls back by itself.
The device knows where it is and what time it is without a network: a GNSS Service in the background, a GNSS App with the position and a sky view of the satellites, the clock set from satellites when there's no NTP, and Tracks…
Browse Geminispace from the Cardputer: fetch and read gemtext over TLS, follow links, answer input prompts, keep bookmarks, and save pages to the SD card to read later, offline. A side milestone between M2 and M3, tagged v0.5.0…
The LoRa radio on the Cap works, receive only: a Radio Service owns it and shares the SPI bus with the SD card safely, and a LoRa Scanner App shows what's on the air, either packets (Sniffer) or energy across the band (Sweep).…
The device works on any network, the card can be trusted, and you can see what the system is doing. A side milestone, like G1.
Get at what's on the SD card from the device itself: browse it, look inside the files the firmware writes, copy, move, rename and delete, and keep notes. A side milestone, like G1 and S1; Files and Notes were M3's original second…
A tag is a release, built the same way every time and published where a device can find it.
A public home for the project at roro9stack.net, separate from the blog (stories) and from Gitea (developers): what it is, how to install it, how to use each App, and the docs.
The interface is consistent and uncrowded: the same thing is done the same way on every screen, and the 135 pixels of height go to content.
Reach things from the device that aren't on the Wi-Fi it happens to be on, and keep its traffic private on a network that isn't yours.
The hardware the device already carries and nothing used yet (the motion sensor, the infrared LED, the microphone and speaker) each gets something useful to do.
The device is a MeshCore chat node that listens. A Mesh Service runs in the background on the Radio Service, keeps a node list from the adverts it hears and the messages of the channels you follow, and a Mesh App shows them.…
The device takes part in the mesh. It has its own identity, advertises itself, posts on channels and exchanges Direct Messages with acknowledgements, within the airtime the band allows. Still a chat node: it never relays (Q289)…
The official MeshCore Android app drives the device over BLE: the phone shows the device's nodes, channels and messages, and sends through it. The device stays its own node with its own screens; the phone is a second way in.
Every App is reached from the first screen, however many there are, on a screen that reads at a glance. The Launcher's grid holds 12 tiles (4 × 3) and the firmware lists 13 Apps: Settings sat alone on a fourth row, under the…