Kaj SchittecatandClaude Opus 4.8
dd7ba1f9f9
Root cause of the reported "SD writes fail after a few hours of uptime": when the segment table is full (s_seg_count == k_ui_seg_max), segBuildJob still emits a CREATE-append, but segCommitJob only tables a create while s_seg_count < the cap. The new segment file is written but never recorded, the durability watermark (s_seg_flushed_seq) never advances, so the same append re-arms every flush cycle (permanent write-spin). As the ring evicts the frozen records the target first_seq shifts, so a new orphan seg_*.bin is written each cycle until the card fills and every SD write fails; records evicted before they are credited are lost. It surfaces only after hours because s_seg_count creeps from its ~20 steady state (5000/256) up to the 24 cap slowly, via delete-driven fragmentation and step-1-append starving step-2 retirement. Fix: at the cap, defer the create-append instead of emitting an untableable one. segBuildJob skips step 1 (before the gather/watermark advance, so the watermark is never moved past un-written records) and falls through to step 2, which retires the oldest segment first. At the cap the oldest 256 records have aged out of the ring (24*256 > 5000), so that segment is fully evicted -> compact_dirty -> unlinked, freeing a slot with no live-record loss; the deferred records are the newest (above the watermark, evicted last) and land next cycle. saveMsgsToStorage's early "armed == 0 -> durable" return is guarded with segMoreWorkPending so a deferred append is reported as a failure, not a false success. Below the cap: no-op. Builds green on T-Deck + Heltec V4 TFT. Needs a multi-hour on-device soak to confirm against the original repro. Co-Authored-By: Claude Opus 4.8 <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 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.