* pager: keep encoder focus inside the chat message list, remap composer nav The rotary encoder's plain turn stepped LVGL's focus group directly, which only ever contains the currently-materialized bubbles (the message list is virtualized; loading more history is scroll-driven, not focus-driven). So turning past the first/last *loaded* bubble escaped the list onto the header/composer even with plenty of un-loaded history in that direction. A turn at that edge now scrolls the list instead when more messages exist (reusing the existing free-scroll helper), which triggers virtualization to load the next batch; focus only leaves the list at the true oldest/newest message. Fast turning folds into a pending target so it doesn't escape mid-load, and the render's focus re-aim now runs synchronously so the transient auto-focus LVGL assigns a deleted row's neighbor never paints. Also removes the two touch-only jump-to-oldest/latest arrows on this board (no touchscreen to tap them) and remaps the chat's key bindings now that plain turns stay in the list: - Orange/Alt tap: jump to the newest message + focus the composer (was Backspace's job). - Backspace tap: jump to the first unread message below the "NEW ----" divider, or the newest message if nothing's unread. - Composer row edges: Send+NEXT reaches the channel-settings gear (falls back to the newest bubble in a DM, which has no gear); the quick-reply chip+PREV goes straight to the newest bubble. TLORA_PAGER_SHORTCUTS.md documents the new chat-screen behavior. Signed-off-by: Tesso M Costa <tesso.martins@gmail.com> * fix scroll --------- Signed-off-by: Tesso M Costa <tesso.martins@gmail.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.