Kaj SchittecatandClaude Opus 5
ee15fcb335
#415: a Lua app was covered by the app drawer whenever a message arrived. Reported by jadestarwatcher, reproduced by mysterywavi, both on T-Deck. Mine, from the #393 badge fix. Apps launched from the drawer deliberately leave it alive underneath (appTileCb says so outright), and my badge refresh rebuilt it on every unread-count change, with openAppDrawer() ending in a move_foreground that threw it on top of the running app. The refresh now runs only when nothing is drawn in front of the drawer, tested by sibling order rather than by listing the tools, so a tool added later is covered without anyone remembering to update a list. The status bar is excluded, since it legitimately floats above the drawer at all times and treating it as covering would have stopped the badges refreshing at all. Leaving the signature stale is what makes it self-healing: the check runs again each tick, so the count is right by the time the drawer is back in front, with no need to hook every close path. Scroll position is now preserved across the rebuild too, which my change had also been resetting. #410: on the M9 the accent variants appeared but could not be selected. Also mine, from the #387 work. The picker was handled below m9HandleArrowKey, which takes LEFT and RIGHT for the caret and returns, so the arrows never reached it: the box was drawn and nothing could touch it. Lifted above that call, as its own function rather than a second copy of the logic. #399, requested by @Danie10: an option to advertise a position near you rather than your address. Settings, GPS, cycling exact / 100 m / 250 m / 1 km. The displacement is derived from the node identity, so it is the same offset every time. That is the whole point rather than an implementation detail: a fresh random offset per advert would scatter points around the true position, and averaging a night of them would recover the centre exactly. A fixed displacement instead looks like a node that sits somewhere else, which is what a manually set location already looks like. It applies only to our own adverts; the map and the GPS page keep the real fix, because the aim is to tell other people less, not to lie to yourself. Schema v57. The host test caught the new field the moment it was added, which is what it is for. All nine S3 envs and both ESP32-P4 targets green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A real touchscreen UI for your mesh radio. · open source · GPL-3.0
Touch-UI MeshCore companion-radio firmware for the LilyGo T-Deck / T-Deck Plus, Heltec V4 + TFT and eight other boards (ESP32-S3).
An LVGL touch UI — map, chat, contacts, channels, settings — split out of
meshcomod. The app depends on a
MeshCore fork via PlatformIO lib_deps.
Boards
See DEVICES.md for the full support matrix, install paths and per-board status.
- LilyGo T-Deck / T-Deck Plus — env
LilyGo_TDeck_companion_radio_touch(stable) - Heltec V4 + TFT + CHSC6x touch — env
heltec_v4_tft_companion_radio_usb_tcp_touch(stable) - Tanmatsu (ESP32-P4) — built from
tanmatsu/(ESP-IDF), ships via the Tanmatsu app store — sideload guide for running your own build - Elecrow ThinkNode M9 — env
ThinkNode_M9_companion_radio_touch(beta) — keyboard & d-pad guide - RAK WisMesh Tap V2 (RAK3312) — env
rak_tap_v2_companion_radio_touch(beta) - LilyGo T-Lora Pager — envs
tlora_pager_lr1121_companion_radio_touch/tlora_pager_sx1262_companion_radio_touch(beta) — keyboard shortcuts - Heltec V4-R8 + Expansion Kit V2 — env
heltec_v4_r8_tft_companion_radio_usb_tcp_touch(beta) - LilyGo T-Display P4 — built from
tdisplay_p4/(ESP-IDF); AMOLED by default,WADA_P4_LCD=1for the TFT-LCD SKU (beta) - Attaky Mesh Series — env
attaky_mesh_series_companion_radio_touch(beta)
Architecture
This repo holds only the app: the companion_radio glue, the ui-touch
LVGL UI, each board's glue/variants, and platformio.ini. The MeshCore
core is not vendored here — it's pulled as a library via lib_deps from the
ALLFATHER-BV/meshcomod monorepo
(the same repo as the non-touch firmware), pinned by a lean source-only core-*
git tag. The touch-app files this repo owns (TouchPrefsStore, WifiRuntimeStore,
the transports, …) are dropped from the lib via -DMC_VENDORED_TOUCH_APP so they
aren't compiled twice. The build is byte-identical to the original in-tree
meshcomod firmware.
Lua apps use the on-device SDK described in LUA_APPS.md. For WAV/MP3 playback, including a ready-to-sideload transport test app and exact SD and internal-storage paths, see AUDIO_PLAYBACK_TESTING.md.
Build
PlatformIO pulls the core fork and all libraries automatically:
pio run -e heltec_v4_tft_companion_radio_usb_tcp_touch # Heltec V4 TFT
pio run -e LilyGo_TDeck_companion_radio_touch # LilyGo T-Deck
# or just `pio run` to build both
Flash with the NVS-preserving 4-component chain (bootloader / partitions /
boot_app0 / firmware at 0x0 / 0x8000 / 0xe000 / 0x10000) so saved Wi-Fi
credentials survive — not a merged image, which 0xFF-pads and wipes NVS.
Contributing
Contributions are welcome — see CONTRIBUTING.md. One topic per PR; inbound contributions are accepted under the project's GPL-3.0 license.
License
GPL-3.0-or-later — see LICENSE. wadamesh is copyleft: anyone who distributes a build or a fork must also make their source available under the GPL. This keeps the UI open and concentrates community effort instead of fragmenting it into closed forks.
wadamesh incorporates and depends on MeshCore (MIT, © Scott Powell / rippleradios.com) and other third-party components — see NOTICE for the full list and their licenses. MeshCore-derived files keep their MIT notices; the combined work is distributed under the GPL (MIT is GPL-compatible). The MeshCore fork that wadamesh builds against stays MIT on purpose, so its Wi-Fi/BLE hooks remain upstreamable to MeshCore.