Kaj SchittecatandClaude Opus 5 ecec85e788 Two P4 layout glitches that are really scale bugs (#236, #238)
Both reported on the T-Display P4 by D-Melhede, and neither is P4-specific once
you look: they are hardcoded pixel values in a UI whose text scales.

#236, a Lua app's first line cut in half by the status bar: the app host set its
body offset from a hardcoded 44, commented as matching the AppPage tall bar.
That is only true where STATUSBAR_H is its 22 default. The bar is
SB_TOP_PAD + SB_ROW*2 on the round-corner phone panel and SC(22) everywhere
else, so it grows with the UI scale, and anywhere it exceeded 44 the app drew
under it. The host now asks for the height the bar actually has. The same
mistake was already fixed elsewhere in the file, with a comment saying to
measure with statusBarCurH() rather than assume; the Lua host had not caught up.

That also means this was never only a P4 bug. Any board at Large or Huge scale
had it, which includes the Tanmatsu, whose default has been Large since v29.

#238, the drawer options not fitting: the card is laid out in raw pixels while
the text inside it scales, so the contents outgrew the box. Now scaled with SC(),
which is identity at 100% and therefore changes nothing on a board that was
already correct, and the card is additionally clamped to the sheet's height so a
larger scale cannot push it off screen.

All nine S3 envs and both ESP32-P4 targets green.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 12:50:35 +02:00
2026-09-03 12:52:03 -04:00
2026-08-29 15:57:23 -04:00
2026-08-23 20:32:26 -04:00
2026-08-23 20:32:26 -04:00
2026-08-23 20:32:26 -04:00
2026-08-23 20:32:26 -04:00

WADAMESH

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=1 for 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.

S
Description
No description provided
Readme GPL-3.0
270 MiB
0 Stars 1 Watchers 0 Forks
Languages
C 48.3%
C++ 41.2%
Lua 3.4%
HTML 2.9%
Python 2%
Other 2.1%