Kaj SchittecatandClaude Opus 5
a2e18c1811
pisti87 found "Settings → Quick replies" drawing a tofu box, in English as well as Hungarian. It is not a language bug and it is not the beta_62 fallback-chain fix falling short — the glyph simply was not in any font we ship. gen-touch-fonts.sh asked $noto_sans for the symbol set, and Noto Sans does not contain U+2190-2193 or U+2260/2264/2265 (verified directly against the release the script pins). lv_font_conv omits a glyph its source font lacks rather than failing, so those seven characters silently never made it into extras_font_*, in every language, since the fonts were first generated this way. Scope is much wider than the one line reported: 137 uses of → in the touch UI plus arrows in all 13 .lang files. pisti87 happened to open one of them. Fixed by cutting the seven from Montserrat, which has all of them, is already the primary UI face and already the first --font in this script — so no new dependency, no new licence line, and the arrow matches the text beside it. They had to be REMOVED from the Noto Sans symbol list as well: with the codepoint claimed by a later font that cannot supply it, the Montserrat pass produced nothing and the regenerated files came back byte-identical apart from a comment. Noto Sans Symbols 2 was the obvious candidate and does NOT have them either — it errors outright when asked, which is how that was ruled out. Not visually confirmed: I have no way to see the glyph render from here. The regenerated fonts grew ~390 lines per size and lv_font_conv accepted the request (it hard-errors when the source font has none of the symbols, as Symbols 2 did), so the glyphs are in. Worth a look on a device before the beta ships. Reported by pisti87. 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 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.