Kaj SchittecatandClaude Opus 5
eafcd23f40
Four things the merges needed. The POI menu from #549 was not in the popup registry. Every modal in this file registers its closer there, and one that does not cannot be dismissed by Back or by the screen-lock teardown: it stays on screen while the page behind it changes. That is the same failure #553 describes for Known Regions, which #550 fixes in the same slice. Czech had no POI string. It was added after #549 was opened, so thirteen language files got the row and the fourteenth did not. Auto keyboard backlight never switched off when the screen timeout is Never. #550 changed Auto to follow the screen timeout instead of a fixed three-second window, which is right, except that Never then means lit forever. Auto is the default mode, so a device left on a desk would burn its keyboard backlight until the battery gave out, where the old window at least ended. The Never case is bounded to a minute; mode On is still there for a permanently lit keyboard. Compact chat rows have vertical padding on the T-Deck Pro and Max (#563). Compact mode leans on the alternating row tint to show where a message ends and e-paper has no tint, so messages ran together, worst when one wrapped. Not fixed here: #562, the Pro terminal drawing black on black. The console already special-cases e-ink, the Pro's palette is white paper and black ink, LovyanGFX treats equal fore and back as transparent rather than a filled block, and consoleBegin gets the display before anything renders. The remaining suspect is the pre-LVGL boot screen, which fills black on purpose because "our pre-LVGL screens are always dark" and inks the whole panel on e-paper. That needs the device to confirm, and guessing at an e-paper fix is how a regression ships. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Submitting an app to the WADAMESH store
Apps are small Lua programs that appear in the device's Apps drawer and are
downloaded over Wi-Fi from firmware.wadamesh.com/apps/. Snake, RF Monitor and
Airtime all ship this way — they are ordinary submissions, not special cases, so
reading their source is the fastest way to see what an app looks like.
Every submission is reviewed and safety-checked before it is added. What that means in practice is spelled out under Review below. It is not a formality and it is not a judgement of you — an app runs on other people's radios, so somebody has to read it first.
What an app is
One Lua file plus a small manifest. Apps talk to the firmware through the wada.*
API — wada.ui (widgets, colours, a text prompt), wada.sys, wada.store
(persistence), wada.timer, and on the larger boards wada.fs, wada.net,
wada.crypto and the writable half of wada.mesh. Supported boards also expose
asynchronous WAV/MP3 playback through wada.audio; plain filenames come from the
app sandbox on internal flash, SD, or SD_MMC. Physical-SD directory metadata
is available through wada.sd, which can also find and delete Windows malware on the
card (the firmware decides what counts, so it cannot delete anything else), and
direct card playback uses an explicit sd:/... path. There is no general-purpose filesystem or network access; the API
is the whole surface, which is what makes reviewing tractable. It is documented at
wadamesh.com/sdk.html.
Two numbers worth knowing before you start: every callback runs under a
100,000 Lua instruction budget, and Lua here is built with 32-bit numbers,
so its floats are single precision. If you are logging coordinates, use the
lat_e6 / lon_e6 integers rather than lat / lon.
Apps run on every board that has the Apps drawer, from the 2 MB-PSRAM Heltec
V4 to the 800×480 Tanmatsu. Do not hard-code pixel sizes — read the screen from
the API and lay out relative to it, the way snake.lua computes its grid.
Layout
deploy/apps/<id>/<ver>/<id>.json manifest
deploy/apps/<id>/<ver>/<id>.lua the app
<id> is lowercase, no spaces, and is the filename stem everywhere. <ver> is
major.minor.
The manifest is one line:
{"id":"snake","name":"Snake","ver":"1.0","desc":"The classic, in Lua. Swipe to steer.","icon":"game"}
desc is what people read in the store listing before installing, so make it say
what the app does. One sentence.
icon is optional and picks the drawer tile's glyph by NAME — an app cannot
ship its own artwork, so anything unrecognised falls back to the generic app
symbol. Choose from: gps / compass / map, radio, signal, chart,
list, message, person, group, bell, star, search, settings,
battery, game.
Version directories are immutable. Once 1.0/ is published it is never edited
— a change ships as 1.1/. Devices cache by version, so editing in place means
some users silently run different code from others under the same version number.
Submitting
- Fork
ALLFATHER-BV/wadameshand branch offmain. - Add your
deploy/apps/<id>/<ver>/directory with the two files. - Add or update your app's row in
deploy/apps/apps.json(the store catalog). Add"seed": falseto that row if your app should be downloadable but not compiled into the firmware. Apps in the catalog are baked into the image as built-ins for boards that cannot reach the Store, and that is flash spent on the boards with the least of it. A large app, or one that needs hardware those boards do not have, is better left to the Store. - Open a pull request. In the description, say what the app does, which boards
you tested it on, and anything it persists via
wada.store.
Please open the PR even if you are unsure about the code — a rough app that works
is easier to review than a perfect one that never gets sent. If you would rather
not use git at all, open an issue with the .lua file attached and say so; we
would rather have the app than the paperwork.
You keep authorship: merging the PR preserves your commits, and the store listing is generated from your manifest. The repository is GPL-3.0, so your app is published under that licence too — do not submit code you are not free to license that way.
Review
Two passes. The first is ordinary code review: does it work, does it fit the screen on a small board, does the description match the behaviour.
The second is the safety check, and it exists because an app ships to other people's devices. We read every submission for:
- Identity and keys — an app must not read, log, transmit or persist the node identity, private key, channel secrets or contact keys. This is the one that gets a submission rejected outright rather than sent back for changes.
- Flash wear and stalls — no writes in a tight loop and none on a per-packet path. Frequent small writes to internal flash trigger garbage collection, which on ESP32 suspends the flash cache and stalls both CPU cores; we have shipped two firmware bugs of exactly this shape. Persist on a user action or a slow timer, not on every frame.
- Blocking the UI — no busy-waits and no long synchronous work. The UI and the mesh share a loop; an app that blocks it drops packets as well as frames.
- Memory — bounded allocations, and nothing that assumes 8 MB of PSRAM. The V4 has 2 MB and is the floor.
- Radio behaviour — an app may read counters and statistics. Transmitting, or changing radio parameters, needs a clear reason and an explicit user action.
- Probing —
wada.mesh.discover()costs a transmission from the user and a reply from every node that hears it, so it spends other people's airtime as well as theirs. The firmware enforces 15 seconds between probes, but a survey app is still expected to probe on a cadence a person chose and to stop when it is not on screen. Probing in a loop for no stated reason gets sent back. - Where data goes — anything leaving the device has to be something the user asked for and can see.
If something needs changing we will say what and why on the PR, and we would rather help you land it than close it. If we reject an app we will tell you the reason plainly.
Testing before you send it
Try it on real hardware, not just one screen size. If you only have one board, say so in the PR — that is useful information, not a disqualification, and it tells the reviewer what still needs checking.