Dan Vybiral
f1e2bc375b
Digging into 'messages still lost after a soft reboot': the loader is sound (well-formed files load fully; a quarantine discards the whole load, never a suffix) and the chat detail applies no time filter — so a conversation missing only its recent messages means the ui_msgs file itself is stale. Two ways that happens silently today: - Persistent ring-write failures. uiWriteMsgsFile failing (full card, FAT damage from hard cuts/card yanks, wedge) was 100% invisible: the small threads file keeps succeeding, so the thread list shows fresh last-message times while messages quietly stop persisting — exactly the reported UX. Now every ring-write outcome is recorded (uiMsgsWriteResult), repeated failures raise an on-screen warning, a failure on the SD store stamps the SD health probe, and the About page gets a 'Chat store' section showing the resolved backend (also exposes the boot-with-unmountable-card trap where history silently goes to internal flash), the msgs file size, and the last save result. - The reboot-time persist had a hole and a corruption hazard. A worker still busy past uiHistWaitWorkerIdle's 9 s cap left _msgs_dirty cleared, so rebootDevice skipped the final sync save entirely; and when the sync save DID overlap a stalled worker write, both truncated the SAME temp file — interleaved garbage, and whichever rename landed last installed a corrupt file the next boot quarantines (total history loss). A still-busy worker now counts as unwritten data, the synchronous writer uses its own temp (last-rename-wins, each candidate internally consistent), a failed last-chance save shows a warning before the reset, and boot reclaims orphaned temps. Builds verified: all five SD-relevant touch envs. Signed-off-by: Dan Vybiral <dan.vybiral@greencode.cz>
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 and Heltec V4 + TFT (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 - Elecrow ThinkNode M9 — env
ThinkNode_M9_companion_radio_touch(beta) - RAK WisMesh Tap V2 (RAK3312) — env
rak_tap_v2_companion_radio_touch(beta)
Architecture
This repo holds only the app: the companion_radio glue, the ui-touch
LVGL UI, the two boards' 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.
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.