Compare commits

...
237 Commits
Author SHA1 Message Date
Kaj SchittecatandClaude Opus 4.8 ae02fb6238 release: beta_45 infra — T-LoRa Pager + T-Display P4 in the flasher matrix
- release.sh: add both T-LoRa Pager envs (LR1121 + SX1262) to the PIO build set.
- gen-flasher-meta.py: add pager (×2) + T-Display P4 manifests; P4 carries
  chipFamily ESP32-P4 (per-board now, not hardcoded S3).
- site: LilyGo T-LoRa Pager board card (both radio variants) with the
  partially-supported badge; the P4 card already landed last cut.
- release-notes/beta_45.txt (leads with @codemonkeybr's pager port).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-15 20:32:31 +02:00
Kaj SchittecatandClaude Opus 4.8 fd0b952620 fix: R8 I2C freeze (shared-bus wedge) + Tanmatsu Wi-Fi settings unreachable
- Heltec V4-R8: the CHSC6x touch ran on a 2nd I2C controller (Wire1) bound to the
  SAME pads (17/18) as the board Wire (RTC + sensors), driven from two cores — a
  classic SDA-stuck-low wedge = the tester's random hard-freezes-needing-reset.
  Touch now shares the one board Wire (V4CAP_WIRE selector), so arduino-esp32's
  per-instance TwoWire mutex serialises all access, the proven T-Deck pattern.
- Wi-Fi settings: the join/details/hidden sheet floats on the base layer above the
  settings page; navMaybeRebuild only recognised the settings sheet + chat + top
  layer as focus roots, so on no-touch/keypad-nav boards (Tanmatsu) its SSID/
  password fields + Join button were never collected into the focus group and
  couldn't be selected. Add s_wifi_sheet as a nav focus root (priority over the
  settings sheet beneath it).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-15 20:27:20 +02:00
Kaj SchittecatandClaude Opus 4.8 f029dcc744 site: per-board support-level badges + T-Display P4 board box
Every flasher board card now carries a support badge with a hover popover:
Heltec V4 + TFT and the T-Deck are 'Fully supported' (the two primary dev
boards); ThinkNode M9, RAK Tap V2, Heltec V4-R8, Tanmatsu and the new
T-Display P4 are 'Partially supported' — the popover spells out that the
core (LoRa mesh communication, chat, phone-app link) works while the rest
is still settling. New T-Display P4 card wired to the beta channel
(manifest-tdisplay-p4.json), same new-board pattern as the M9/RAK cards.

NOTICE: extend the ES8311 attribution to cover the P4's P4Audio.cpp
(esp-bsp-derived register sequence, re-based onto Arduino Wire).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-15 19:24:55 +02:00
Kaj Schittecat be0a49255c Merge PR #149: LilyGo T-LoRa Pager port (LR1121 + SX1262) by @codemonkeybr
Full keyboard+encoder-driven board port: TCA8418 QWERTY matrix, rotary encoder
focus-nav, ST7796 display, ES8311 notification sound, both radio variants.
Hardware-verified by the author against a live mesh.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

# Conflicts:
#	src/ui-touch/UITask.cpp
2026-07-15 19:16:51 +02:00
Kaj SchittecatandClaude Opus 4.8 2353c56adc p4: T-Display P4 port — web VNC/remote, time-sync hardening, brightness + sound
LilyGo T-Display P4 (ESP32-P4 + factory ESP-AT C6) reaches POC: LoRa mesh, Wi-Fi
companion (TCP:5000), GPS, SD, battery gauge, chat persistence, and now:

- Web VNC/REMOTE/terminal via a first-byte router on the single ESP-AT listener
  (HTTP verbs -> WS server, '<' frames -> phone companion; both live at once).
  C6Server gains a _begun gate so never-listening instances stay inert.
- VNC freeze fixed: bounded one-CIPSEND-chunk drains under the WS client mutex
  (a whole-band blocking write starved the main loop), fast-drop of stalled
  mirror clients, SEND-OK wait 8s->4s.
- Wi-Fi robustness: CWJAP? miss-streak tolerance, CIPSERVER liveness verify +
  re-arm (a re-association silently killed the listener until reboot).
- Time sync: HTTP-Date fallback when SNTP is blocked; ClockFloorRTC gains a
  MAX_PLAUSIBLE_EPOCH guard (all boards) after a garbage-future hardware RTC
  read (2043) latched the ratchet.
- Brightness: RM69A10 DCS 0x51 driven live (CC slider + persisted pref).
- Sound: ES8311 + NS4150B notification chimes (P4Audio, esp-bsp-derived
  register sequence on Wire1), full HAS_UI_SOUND surface + CC Screen/Sound
  sliders; ccVolumeReleaseCb's hardcoded tanBeep -> uiSoundPreview.
- tdisplay_p4/: IDF project (build.sh, c6_at AT-over-SDIO driver, sdkconfigs,
  fetch-deps.sh vendoring, .gitignore for local payloads).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-15 19:13:23 +02:00
Tesso M Costa 0adcd26b78 Revert "pager: hide the touch-only chat jump-to-oldest/latest arrows"
This reverts commit 53a60dfbb2.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 21:52:21 -06:00
Tesso M Costa 53a60dfbb2 pager: hide the touch-only chat jump-to-oldest/latest arrows
Both floating jump arrows in the open-chat view are touch-only
affordances with no purpose on the T-LoRa Pager (no touchscreen), so
skip creating them on that board and leave the pointers null like
every other consumer already expects. The pager's existing
Backspace-tap "jump to latest" shortcut no longer depends on the
button object itself -- it checks chatVirtAwayFromBottom() directly
and calls chatVirtJumpToLatest(), the same virtualization-aware jump
the button's own click handler used.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 17:54:55 -06:00
Tesso M Costa e5cd766f73 pager: move Home-jump to Alt+Backspace, works everywhere including mid-edit
Alt+Shift previously did double duty: toggle Caps Lock while editing a
field, or jump Home otherwise. Splitting these apart -- Alt+Backspace is
now the dedicated Home-jump gesture, and unlike Alt+Shift it isn't
context-dependent: it works whether or not a field is being edited, so
it's reachable from anywhere without first backing out of what you're
typing. Alt+Shift outside a field is now a no-op instead.

PagerKeyboard.cpp suppresses a Backspace press entirely while Alt is
held (no '\b' ring-push, no hold-to-back/hold-to-unlock tracking) and
reports it as a one-shot chord instead, mirroring the existing Alt+Shift
chord plumbing. Also closes the accent/@-mention popups first, since
those live on lv_layer_top() outside the tab content the Home jump
switches away from.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 12:15:29 -06:00
Tesso M Costa 5c97d02fbe Merge remote-tracking branch 'origin/main' into tlora-pager-port-lr1121
Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>

# Conflicts:
#	NOTICE
#	platformio.ini
#	src/ui-touch/UITask.cpp
#	src/ui-touch/device_caps.h
2026-07-14 10:45:53 -06:00
Tesso M Costa 01833d0365 docs: track T-LoRa Pager port tracker in git
Previously kept local-only (see f18929b/cca9a44), moving pager tracker
docs under gitignored dev-docs/. This one now ships in the repo instead,
per explicit request -- keep it current alongside pager code changes.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 09:44:42 -06:00
Tesso M Costa a95f976262 docs: note keyboard alternatives for the encoder's turn/click/hold gestures
Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 09:43:26 -06:00
Tesso M Costa 2540e230c6 docs: document the @-mention picker's encoder navigation
Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 09:29:38 -06:00
Tesso M Costa 6073b6fa4e ui: app-drawer tiles use their own accent tint for keyboard/encoder focus
App tiles previously fell through to navFocusCb's generic white
reverse-video fill when focused via keyboard/encoder nav, instead of
the accent-tinted LV_STATE_PRESSED look they already show on a touch
press -- a solid white block over a small rounded icon chip reads as a
glitch, not a highlight, and looked inconsistent with the touch-driven
boards. Tiles now opt into the same accent tint for both states.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 09:29:06 -06:00
Tesso M Costa 57802eba3d pager: make the @-mention contact picker encoder/keyboard-navigable
Typing "@partial" in a composer popped up a touch-only contact list
(NAV_SKIP_FLAG cells, same as the accent-variant box before it got the
same treatment) -- on this board's no-touch input model there was no
way to actually pick a name from it. Mirrors the accent box's pager nav
(rotary encoder walks the highlighted cell, Enter/click confirms,
Backspace cancels without touching the typed text), but grabs the
encoder the instant the list appears rather than requiring an explicit
Fn+Space arm: unlike the accent box (which pops up after almost every
letter typed and must not steal focus from ongoing typing), the mention
list only shows once the user has deliberately typed "@partial" looking
for someone to pick, so there's no ongoing typing to protect.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 09:28:29 -06:00
Tesso M Costa b16206bf7d pager: Fn+Shift toggles Caps Lock only while editing a field, else jumps Home
The Fn(Alt)+Shift chord previously toggled Caps Lock unconditionally,
even with no text field focused to see the change reflected in --
reported as surprising and purposeless outside of typing. PagerKeyboard
now only reports the chord (pagerKeyboardConsumeAltShiftChord()); the UI
decides the effect: Caps Lock toggle while actually editing a field,
otherwise a direct jump to the Home screen (mirrors the "ta" derivation
handleHwKey() already uses to tell bound-but-unfocused fields apart from
one actually being edited).

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 08:46:55 -06:00
Tesso M Costa c4c28d493d pager: rotary encoder short click opens the message action menu
A focused chat bubble already opened its Ack/Mention/Copy/Info/Block
action menu on Enter (navEnterBubble), but the encoder's short click
only sent a plain ENTER, which a bubble doesn't otherwise react to.
Mirrors handleHwKey()'s Enter branch so both inputs agree.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 08:46:18 -06:00
Tesso M Costa 8e7d6ae902 docs: add T-LoRa Pager keyboard & rotary encoder shortcut guide
User-facing reference for MeshCore users new to this board's touch-less
input model: keyboard layout, Shift/Caps, accent-variant picker, sliders,
map panning, keyboard backlight, and a full gesture quick-reference.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-14 08:27:05 -06:00
Kaj SchittecatandClaude Opus 4.8 a87ebe1e81 site: tidy the per-board download link — two-line 'Download .bin' + version caption
The first cut used an inline-flex link that wrapped and scattered the icon, text
and version across the narrow card. Restructure as a clean teal 'Download .bin'
row with the version as a small muted caption underneath; drop the double spacing
(the .board flex gap already separates it from Connect).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14 12:11:27 +02:00
Kaj SchittecatandClaude Opus 4.8 69ffe71bfe site: standalone flasher — per-board "download the .bin" links (find them where Connect is)
Community feedback: the only .bin download was buried in the Launcher path, so
people couldn't find a download at all. Add a compact "or download the .bin" link
to every standalone board card, right under its Connect button. Each follows the
Stable/Beta toggle (beta-only boards stay pinned to latest-beta) and shows the
exact version that feed serves (both channel tags fetched once so every link is
accurate). Downloads the full merged image — the same build Connect flashes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14 12:03:43 +02:00
Kaj SchittecatandClaude Opus 4.8 e617bf306c site: Launcher flasher page — Stable/Beta toggle + "you're downloading version X" box
Community feedback (gubbinsgalore): on the Launcher install page there was no way
to tell which version the "Download .bin" gives you (it's the version-less
wadamesh-tdeck.bin), and the Stable/Beta channel toggle only existed on the
Standalone page — so Launcher users were pinned to stable and couldn't grab a
beta app image.

- Add the same Stable/Beta toggle to the Launcher page (the existing wmSetChannel
  JS already drives dl-tdeck + keeps both toggles in sync).
- Add a version box under the download, auto-filled from version.json and updating
  with the toggle: "You're downloading version <tag> · <channel>".

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14 11:49:31 +02:00
Kaj SchittecatandClaude Opus 4.8 687eb3865c touch: add Heltec WiFi LoRa 32 V4-R8 board (8 MB octal PSRAM + Expansion Kit V2 SD)
The V4-R8 uses an ESP32-S3R8 (8 MB OCTAL PSRAM) which claims GPIO33-37, so
Heltec moved every control signal off them and the Expansion Kit V2 rebuilt the
display/touch/SD block onto a hardware-SPI bus:
  Vext 36->40 (active-LOW) . GPS_EN 34->42 . LED 35->46 . ADC_Ctrl removed
  TFT (LovyanGFX HW-SPI): MOSI=15 SCK=16 MISO=45 CS=47 DC=48 RST=21 BL=44
  touch (CHSC6x, shares board I2C 17/18) . micro-SD (shared TFT SPI, CS=3)

The build defines HELTEC_LORA_V4_TFT too, so it reuses all the V4 touch-UI code;
HELTEC_LORA_V4_R8 gates only the deltas. 8 MB enables the on-device web browser
(CAP_WEB_BROWSER) and the SD card (CAP_SD). Also wires the board into the release
+ web-flasher pipeline (release.sh, gen-flasher-meta.py, the flasher picker).

UNTESTED — no V4-R8 hardware yet. Pin sources: Meshtastic heltec_v4_r8 variant,
Heltec V4-R8 pinmap, and the Expansion_board_V2.03 schematic. All three touch
envs build clean; V4/T-Deck unregressed. On-device TODO: CHSC6x shared-Wire on
17/18, SD_CS=3, and the V2 PAM8904 buzzer.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14 11:27:40 +02:00
Tesso M Costa 9881bb0038 pager: WASD pans the Map tab, move slider nudge to Q/E
Reuses mapNudge() (previously Tanmatsu's Ctrl+Arrow-only helper, now
shared) so W/A/S/D pan the map north/west/south/east on this board's
touch-less Map tab. Frees up D from the slider-nudge binding, which
moves to Q/E so the two gestures don't collide when a slider (e.g. the
map zoom bar) is focused while WASD panning is in play.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-13 13:15:16 -06:00
Tesso M Costa 4b0c2e9de1 pager: add tlora_pager_sx1262_companion_radio_touch env
Milestone 10: serve pager units sold with SX1262 instead of LR1121.
Same board JSON, same variant dir, same NSS/RESET/BUSY/DIO1/SCLK/MISO/
MOSI pins as the LR1121 env -- confirmed against trail-mate's own
working SX1262 pager reference that it's the same physical radio slot,
just a different chip populated. RADIO_CLASS/WRAPPER_CLASS swap to the
core fork's CustomSX1262/CustomSX1262Wrapper, the exact same generic
classes the T-Deck already uses, so radio_init() just calls
radio.std_init(nullptr) -- no new radio C++ code needed, only build
flags.

TCXO voltage and the DIO2-as-RF-switch setting are NOT copied from the
T-Deck wholesale: trail-mate's reference for this exact PCB uses
RadioLib's own 1.6V TCXO default with no override, so
SX126X_DIO3_TCXO_VOLTAGE is left undefined here too (std_init() already
retries at 0.0f on an SPI-cmd failure). SX126X_DIO2_AS_RF_SWITCH=true
and SX126X_CURRENT_LIMIT=140 ARE carried over from the T-Deck, but
because both are tied to the shared LORA_TX_POWER=22 target (RadioLib's
default 60mA current limit silently caps real TX power below 22dBm on
any board, not something T-Deck-specific), not board-specific analog
circuitry.

Also fixes a real bug found compiling this for the first time:
target.h only ever included the LR1121 wrapper (vendored locally in
this variant dir), never the core lib's CustomSX1262Wrapper -- unlike
T-Deck/Heltec V4's own target.h, which already include it. RADIO_CLASS/
WRAPPER_CLASS resolved to nothing and every radio_driver.* call site in
MyMesh.cpp failed to compile.

Hardware-verified: flashed a real SX1262 unit via the documented
out-of-box recipe (full erase + merged image), boot log confirmed
radio init succeeded alongside the rest of the board, and a live
mesh test confirmed send/receive on the public channel, a custom
channel, and DM.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-13 11:34:43 -06:00
Tesso M Costa 43f040ec0a pager: make the accent-variant popup reachable via Fn+Space + encoder
The accent-variant popup (issue #22) that appears above the field when
typing a letter with accented variants was touch-only -- its cells are
NAV_SKIP_FLAG, deliberately excluded from the keyboard/encoder focus
group. On the pager (no touch at all) this made the popup pure visual
noise: it would appear and just sit there unreachable.

Added a small parallel nav path scoped to this board: Fn (Alt) held +
Space jumps into the popup (instead of typing a space or the usual
double-tap-cycle-layout action); the rotary encoder then walks the
highlighted variant; the encoder's own click confirms (reusing the
existing accentBoxCellCb via a synthesized CLICKED event, rather than
duplicating its delete-base-letter + insert-variant logic); Backspace
cancels without deleting the base letter. Everything else is swallowed
while active so a stray keypress can't leak into the message mid-pick.
Focus never actually leaves the text field throughout -- the popup's
cells stay outside the normal nav group the whole time -- so nothing
extra is needed to "return" focus after a pick or cancel.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-13 10:45:31 -06:00
Kaj SchittecatandClaude Opus 4.8 c22c76b704 docs: add Web browser section + screenshots to the site docs
New "Web browser" section in deploy/site/docs.html (and a TOC entry)
covering the on-device text browser and tappable chat links
("Open in web" / "Create QR"), with three new device screenshots
(app_web, app_web_links, app_web_qr). Existing screenshots unchanged.

Also render the reader page inline in the DOC_CAPTURE tour: the reader
paints from the UI-update poll, which doesn't run while the tour blocks
the loop, so the tour now drives the fetch-wait + render itself before
capturing the Web app.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-13 18:08:43 +02:00
Tesso M Costa 79df5281e4 pager: real Shift-hold, Alt+Shift chord for Caps Lock
The Shift/Caps key previously toggled Caps Lock on every bare press --
a deliberate design choice reused from a working reference build, but
not conventional keyboard behavior. Changed to: held alone, it's a
momentary Shift (uppercases letters typed while held, same as a real
Shift key); held Alt then a Shift press instead chords into a toggle
for persistent Caps Lock. kCapsPos renamed kShiftPos to match its new
primary role -- zero other call sites reference it, and s_caps itself
is unchanged (still just "is Caps Lock engaged", only the trigger
changed).

Alt (row2,col0) and Shift (row2,col8) share a matrix row, so holding
all three of Alt+Shift+O or Alt+Shift+L at once phantom-ghosts a
'q'/'a' (diode-less-matrix 3-key rectangle, no software fix possible)
-- documented in the matrix-legend comment; harmless in practice since
the intended gesture is hold-Alt-tap-Shift-release-both, not holding
all three down together.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-13 09:57:39 -06:00
Kaj SchittecatandClaude Opus 4.8 308be40b96 touch: beta_44 — on-device text web browser + tappable chat links + French keyboard fix
- New "Web" app: on-device HTTPS text browser (strip HTML to readable text,
  tappable links, back/fwd/refresh, no proxy). Gated to 8 MB boards via
  CAP_WEB_BROWSER; hidden on the 2 MB V4 (can't do the TLS handshake).
- Tappable URLs in chat -> Open in web (8 MB) / Create QR (all boards).
- Drawn vector globe icon for the Web tile.
- Fix: French AZERTY on-screen keyboard lost its spacebar/OK/kbd-switch row
  (a stray "" mid-map terminated the LVGL button map early). Restored.
- V4 web fetch resilience (192->96->48->24 KB buffer fallback).
- Home signal box: "tap for details" cue back at the top.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-13 17:26:05 +02:00
Kaj SchittecatandClaude Opus 4.8 8a2825e7fd docs: cache-bust the map screenshot URL past the Cloudflare edge
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-12 17:25:40 +02:00
Kaj SchittecatandClaude Opus 4.8 5f40653e58 docs: restore the previous (better) map screenshot
The DOC_CAPTURE tour re-captured the map from the live device, which showed a
less representative view. Keep the earlier curated map shot (tiles + markers).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-12 17:23:44 +02:00
Kaj SchittecatandClaude Opus 4.8 d787d77365 docs: web control panel + Remote/VNC guide, refreshed device shots
- New "Remote & web app" docs section covering the browser control panel
  (Chats / Contacts / Discovered / Settings / Terminal), Screen mirror (VNC)
  and Remote UI, with a 7-shot phone gallery of the real web app.
- Refreshed all device screenshots via the DOC_CAPTURE tour (now also
  captures the Remote screen) and added the MQTT bridge settings page.
- New automated web-capture harness (scripts/doc/web-demo/): extracts the
  real page from firmware, serves it with mock data, screenshots via Playwright.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-12 17:18:20 +02:00
Kaj SchittecatandClaude Opus 4.8 831959ea5c touch: beta_43 - web control panel becomes a full remote app + V4 map-tile fix
The browser control panel gains full Chats / Contacts / Discovered / Settings
tabs (search, sort, filter, per-contact actions, notifications + live refresh,
ACK/repeats, add-from-discovered, live radio settings, quick-command picker).

Heltec V4 map tiles: fixed the "only the top renders" bug on the 2 MB-PSRAM
board with a persistent tile-buffer pool + viewport culling (no more per-render
128 KB churn/fragmentation). Adds an opt-in "Tile debug overlay" (Map options).

Also: V4 physical-keyboard input in remote/VNC, clearer remote-access screen,
complete Terminal help on device + web, WADAMESH header + status icons.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-12 16:29:08 +02:00
Kaj SchittecatandClaude Opus 4.8 4df391a283 touch: beta_42 - REMOTE fits the Heltec V4 + keyboard-less exit
Remote mode showed a black screen on 2 MB-PSRAM boards (Heltec V4): the
mirror ring/shadow were too big to allocate. Size the ring to one frame
and drop the remote render to 400x240 so the whole footprint is smaller
than VNC's (which already worked). Add a touch-and-hold (3 s) exit for
keyboard-less touch boards and an Exit button on the web page.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-11 23:34:30 +02:00
Kaj SchittecatandClaude Opus 4.8 3f375f2fe4 touch: beta_41 - VNC + REMOTE web mirror (experimental)
Stream the live LVGL UI to a phone/desktop browser over the WS companion
server (VNC app) plus a headless REMOTE mode that renders the UI at a
browser-friendly resolution. Non-blocking per-client TX buffering, a
core-0 stream task guarded by a recursive mutex, an on-page Rotate
orientation toggle, and a small 480x288 render upscaled in the browser.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-11 22:32:25 +02:00
Kaj Schittecat 9da367d0bc chore: refresh Mesh America catalog for beta_40 2026-07-11 12:28:49 +02:00
Kaj SchittecatandClaude Opus 4.8 01a5238662 touch: beta_40 stable — Tanmatsu About version fix + comprehensive release notes
- Tanmatsu (ESP32-P4) now bakes FIRMWARE_VERSION="wadamesh <tag>" like the S3
  release path, and the app-store publish passes the exact beta tag into the IDF
  build — so the About page shows the real beta number instead of the MeshCore
  default "v1.16.0-touch".
- beta_40 stable release notes: rolls up beta_36 through beta_40.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-11 12:27:00 +02:00
Tesso M Costa 1514e7638c pager: pick notification WAVs from the SD card
Completes the microSD work from the previous commit: wavOpen()'s
"sd:"-prefixed path branch, fmIsAudio()/fmOpenAudio() (the .wav ->
notification-sound chooser opened from the File Manager), and the
popup-dismiss registry entry for it (so Back/Escape via the encoder or
keyboard closes the picker, not just the on-screen X) are all widened
the same way as the previous commit's browsing support -- specific
call sites only, CAP_SD/CAP_FILESYSTEM stay 0 in device_caps.h.

Also updates that file's now-stale CAP_SOUND_FILES comment, which said
the pager's WAV picker only ever reads from SPIFFS -- it can read from
the SD card now too.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-10 16:25:16 -06:00
Tesso M Costa 8c7fb6af5c pager: mount the microSD card and browse it in the File Manager
pagerKeyboardSetBacklight-style dead-hardware situation: the board-level
SD wiring (power rail, card-detect, chip-select parking, shared-SPI bus
reuse) was already done during earlier bring-up, but nothing ever called
SD.begin(), so the slot was unusable. CAP_SD/CAP_FILESYSTEM already
existed for exactly this in device_caps.h, left at 0 with a "pager needs
its own SD wiring" comment.

CAP_SD turns out to gate ~37 call sites across UITask.cpp -- file
manager, WAV picker, DataStore contacts/channels routing, map-tile
fallback, wallpaper scanning, settings backup, screenshots. Scope for
this pass is file-manager browsing only (WAV picker follow-up commit);
flipping the top-level CAP_SD/CAP_FILESYSTEM macros would have silently
turned on all ~37 at once, several referencing T-Deck-only helpers never
vetted for this board. So device_caps.h is untouched -- CAP_SD/
CAP_FILESYSTEM stay 0 for the pager -- and only the specific call sites
needed for browsing are widened with `|| defined(TLORA_PAGER)`.

- fmSdTryMount()/fmSdUnmount()/fmSdClickCb(): widened, plus a pager-only
  sdSharedSPI() (reuses TFT_eSPI::getSPIinstance(), the same shared bus
  the radio already uses -- variants/lilygo_tlora_pager/target.cpp) and
  a card-detect pre-check via the XL9555 expander (PAGER_EXPAND_SD_DET,
  inverted polarity confirmed against LilyGoLib's own installSD()).
  Format support is explicitly out of scope -- the pager's SD row is
  tap-to-open only, no long-press-to-format.
- fmShowRoots(): pager SD row, shown only when a card is actually
  detected (no T-Deck-style "tap to mount" fallback -- the detect line
  makes "not present" unambiguous).
- fmIsSd(), the CAP_FILESYSTEM-gated Apps-drawer "Files" entry (dispatch
  + grid tile), and the insert/remove poll: widened the same way.

All ~30 other CAP_SD/CAP_FILESYSTEM sites (DataStore SD routing, tile
fallback, wallpaper, telemetry, settings backup, screenshots) are
untouched and stay exactly as unavailable on the pager as before.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-10 16:21:46 -06:00
Tesso M Costa c9033a3823 pager: wire up the keyboard backlight (off/on/auto)
pagerKeyboardSetBacklight() existed but nothing called it. The mode
state, NVS persistence, and boot restore were already generic across
every CAP_KEYBOARD board (s_kb_bl_mode, touchPrefsGetKbBacklight()),
so only two pieces were missing for this board:

- updatePagerKbBacklight(): a per-tick apply step, the pager's
  analog of the T-Deck's inline backlight calc / Tanmatsu's
  tanKbBacklightTick(). No brightness curve needed here (the pager's
  backlight is a plain LEDC PWM strip, not a dimmable slider like the
  T-Deck's) -- on/auto-active drive full duty (255), everything else
  (off, idle, screen-off, locked) drives 0. Runs unconditionally in
  the pager's loop branch so it can force the light dark the instant
  the screen goes off/locked.
- A "Keyboard backlight" row in Settings -> Keyboard (pager-only,
  sibling to the T-Deck's slider block) that cycles off/on/auto,
  mirroring the Control Center chip's semantics -- the Control Center
  itself is unreachable on this board (its launcher is touch-only).

Also fixed auto mode actually responding to input: neither
handleHwKey() nor updatePagerEncoder() called noteKbActivity() (the
function that stamps the auto-mode idle timer) -- they only called
the separate noteUserInput() (the screen idle-dim timer), so auto
mode would light briefly at boot and then never again regardless of
typing or turning the encoder. Both now stamp it too.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-10 10:40:25 -06:00
Kaj SchittecatandClaude Opus 4.8 946e73bb0b touch: beta_40 - card-less contacts-save stall fix + long-text auto-fit
Fixes:
- Card-less devices (Heltec V4) froze for seconds: a full contacts rewrite to
  SPIFFS on every advert refresh triggered a multi-second GC in the mesh loop.
  Coalesce advert-driven saves (a contact-set change still saves promptly); SD
  boards unchanged. Flush on reboot/power-off so nothing is lost.
- Long translations (FR/DE/...) overflowed fixed-width labels: new
  uiFitLabelWidth() shrinks the font to fit one line instead of clipping/wrapping
  - applied to the message menu, confirm dialogs, and app-drawer tiles.
- Home signal graph: "tap for details" hint moved to bottom-right so it no longer
  overlaps the "Sig" chip in longer languages.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-10 18:31:26 +02:00
Kaj Schittecat 326d34aaec site: add BFGNeil community video (newest first) 2026-07-10 13:05:02 +02:00
Kaj Schittecat d2fe2ed728 release-notes: beta_39 2026-07-09 23:39:20 +02:00
Kaj SchittecatandClaude Opus 4.8 9547ce6ede touch: chat-history persistence fix + faster delete + emoji tofu fix
Persistence (Leon P / MrWeavis, beta_38):
- Deleting a message or clearing a chat now persists synchronously, so it
  survives an immediate hardware reset instead of "coming back" (the tombstone
  used to ride the 30 s lazy SD flush, which a reset beats).
- The history file is now written compactly — only the used records,
  oldest-first, instead of all ~5000 ring slots every time. A typical chat
  writes ~48 KB instead of ~1.2 MB, so the synchronous delete/clear/reboot
  flush no longer hitches the UI (and normal message flushes are lighter too).
  Old history files still load (the reader derives its slot count from size).

Emoji picker:
- Baked the 14 glyphs that were listed but never in the font (umbrella, coffee,
  pizza, cake, rocket, camera, phone, laptop, calendar, antenna, e-mail, house,
  car, watch); they rendered as the notdef box.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-09 23:38:37 +02:00
Kaj SchittecatandClaude Opus 4.8 49a8f31b8c touch(i18n): full untranslated-text audit + 307 new translation rows
Audited every user-visible string sink across the touch UI and closed the
gaps that had accumulated since the language table was last touched:

- TR() now strips a leading LVGL-symbol glyph (+ spaces) off the lookup key
  and rebuilds the label, so icon-prefixed menu/sheet rows ("<glyph>  Copy")
  translate instead of silently falling back to English.
- Wrapped 95 bare literal sinks (settingsRowLabel / showAlert / showConfirm /
  lv_label_set_text / dropdown / placeholder / checkbox) in TR(); unwrapped 29
  format-only strings that never should have been keys.
- Added 307 missing rows to kI18n[] covering all 11 non-English languages
  (NL DE FR ES IT RU UK BG SR EL PT-BR); keys byte-identical, printf
  placeholders and %-order preserved, Serbian in Cyrillic.

Builds green on T-Deck + Heltec V4; Tanmatsu app 3,169,296 B (107 KB under
the AppFS 50-page load ceiling).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-09 19:38:07 +02:00
Kaj SchittecatandClaude Fable 5 ded72bb91a docs: DEVICES.md support matrix + README board list refresh
One page with every supported board, its install path, release channel
and maturity, plus the open hardware requests and the channel model.
The README board list now covers all five targets and links there.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 14:26:47 +02:00
Kaj SchittecatandClaude Fable 5 cb08116eae flasher/site: ThinkNode M9 + RAK WisMesh Tap V2 web-flash support
Both new S3 boards are installable from the browser now: release.sh
builds and ships their bins per channel, gen-flasher-meta emits their
esp-web-tools manifests, and the site gets install cards for both.
The cards are pinned to the beta feed (with a note) until the first
stable promote that includes their bins; the wmSetChannel comment says
how to unpin then. beta_38's beta feed and GitHub release carry the
new bins retroactively.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 13:55:35 +02:00
Kaj SchittecatandClaude Fable 5 f0a7265dec touch: beta_38 release notes
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 13:15:59 +02:00
Kaj 814c8f5941 Merge pull request #130 from scratchdiver/steve/touch-chat-ui-pr
touch: virtualize chat scrolling (bubble + compact)
2026-07-09 13:14:44 +02:00
Kaj SchittecatandClaude Fable 5 76cd025bf5 tanmatsu: move identity + prefs to the SD card; open-probe the prefs load chain
The P4's internal FFat 'locfd' has a broken FAT metadata layer: open/
read/write work but f_stat/exists()/size() return garbage - and WHICH
garbage shifts with the build. At -Og the exists()-gated identity and
NodePrefs loads worked by luck; the -Os switch flipped the lie and the
device booted with a fresh identity and default name, and profile
changes never survived a reboot (the loads failed, not the saves).
Chat history was unaffected because it already lives on SD_MMC.

- DataStore::useSdMmcStorage(): full-store adoption of the card
  (/meshcomod root, identity store included), mirroring the T-Deck's
  useSdStorage(). The old card-root contacts3/channels2/adv_blobs from
  the secondary-FS era are renamed under /meshcomod.
- Tanmatsu boot: one-time rescue of identity + prefs off FFat by OPEN
  and READ probing (never exists()/size() on that FS), then adopt the
  card. FFat remains the no-card fallback only.
- DataStore::loadPrefs() probes candidates by opening and reading a
  byte instead of exists() - truthful on the P4, identical elsewhere.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 13:00:54 +02:00
Kaj SchittecatandClaude Fable 5 d20241627c touch: flush chat history on the companion CMD_REBOOT (fix messages lost on app-initiated reboot)
Since the beta_35 lazy history writer, message-ring flushes are spaced
up to 30 s apart on the deep SD ring. Every on-device reboot/power path
compensates by calling persistHistoryNow() first, but the companion
protocol's CMD_REBOOT (the phone app's reboot button) went straight to
board.reboot(), dropping everything since the last flush - the newest,
just-read messages, which reads as 'my channel and DM messages get
deleted after a manual reboot' (Leon P, T-Deck under Launcher, beta_35
through beta_37).

persistHistoryNow() is now an AbstractUITask hook (default no-op, so
non-touch companions are unchanged) and CMD_REBOOT calls it before
rebooting, matching the power-menu contract.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 12:48:53 +02:00
Kaj SchittecatandClaude Fable 5 0b886e4fee tanmatsu: build the P4 app at -Os instead of -Og (boot-verified)
The app has been compiling at debug optimization since the port began,
costing ~300 KB of flash-mapped footprint against the launcher's hard
50-page (3,276,800 B) app-load ceiling. At -Os current main is
2,973,520 B, ~296 KB under the ceiling. Boot-verified on the device:
app starts, C6 esp-hosted link up, Wi-Fi associates.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 12:39:55 +02:00
Kaj SchittecatandClaude Fable 5 a49726d4ce touch(tdeck): migrate SPIFFS data to SD on adoption + recovery copy button (beta_36 lost-profile fix)
Users who flipped 'Store data on SD' before beta_36 ran with the toggle
IGNORED (the flag never survived a reboot), so their identity, prefs and
contacts kept living on SPIFFS. When beta_36 made the flag finally take
effect, useSdStorage() pointed the store at an EMPTY card, the identity
store minted a brand-new node, and the user 'lost' their profile. The
data was never gone - it was orphaned on internal flash.

Two-part fix:
- Boot: adopting the card while SPIFFS holds an identity the card lacks
  now copies every SPIFFS file into SD:/meshcomod first (kv files
  flatten to the card's SdNvsPrefs layout). If the identity file fails
  to land, the device stays on SPIFFS for the boot instead of adopting
  a card without it.
- Settings -> Storage gains 'Copy internal data to SD' for the users
  already bitten (their card now holds a fresh identity the boot-time
  no-clobber gate rightly won't touch): confirmation, overwrite-copy of
  everything from internal flash, force the SD pref on, reboot.

Workaround until this ships: toggle 'Store data on SD' OFF and reboot -
the device reads internal flash again and the old profile returns.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 12:29:54 +02:00
Kaj SchittecatandClaude Fable 5 6aa1147eb3 touch: message action menu lays out two buttons per row
With Delete the menu carries up to 7 actions; a single column no longer
fit the 240-px screens without scrolling. Two per row (wider 200-px card,
odd last button on its own row) keeps the whole menu on one screen.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 12:06:52 +02:00
Kaj SchittecatandClaude Fable 5 d9f45405d5 touch: slim scroll-fade jump arrows + message delete + per-chat history wipe
- The chat jump buttons are bare arrows flush against the right edge now
  (28x36 transparent touch target, accent-colored glyph) instead of 40 px
  filled circles; they run at full opacity while the list scrolls and dim
  to 50 percent one second after the last scroll activity. The Tanmatsu
  keeps its F-key chip styling and geometry.
- The long-press message menu gains a Delete row: the message is
  tombstoned in the ring (thread tag blanked, so every walker skips the
  slot and live ring indexes stay valid) and both the chat and the thread
  list refresh.
- The chat/channel settings sheet (in-chat gear and list long-press)
  gains a 'Delete history' row for both DMs and channels: confirmation
  prompt, then every message of the thread is tombstoned. The thread row,
  channel membership and contact stay; only the conversation is wiped.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 12:01:46 +02:00
Kaj SchittecatandClaude Fable 5 f04e01769d tanmatsu: build the P4 app at -Os instead of -Og
The app has been building at debug optimization since the port began.
At -Og the AppFS image sat 2.2 KB OVER the launcher's 50-page load
ceiling with the chat virtualization in; at -Os it is 2,980,688 bytes,
296 KB under the ceiling, retiring the size-locked-platform problem
(and likely speeding the UI up). Needs one on-device boot check before
anything ships with it - the P4 has never run an -Os build.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 11:38:38 +02:00
Kaj SchittecatandClaude Fable 5 9785d8b7d1 fix(chat-virt): review fixes from the PR 130 deep review
- chatVirtReset no longer queues lv_obj_del_async on the divider: the
  empty-thread paths lv_obj_clean two lines later freed it first and the
  deferred lv_obj_del then ran on freed memory (confirmed UAF, plus a
  cross-panel variant when both panels are open). Downstream cleans own
  the widget; the reset only nulls the pointer now.
- Compact rows register bubbleLongPressMenuCb for LV_EVENT_LONG_PRESSED
  (the only event the callback acts on) instead of PRESSED/RELEASED/
  PRESS_LOST/DELETE, all of which it filtered out - the per-message menu
  was completely dead in compact mode.
- Bubble mode gets tap-to-resend back on failed sends (CLICKED handler
  plus the 'tap to resend' footer), matching the compact path and the
  pre-virtualization behavior.
- need_layout gains a content-generation guard (endpoint ring slots): at
  ring capacity n stays constant while content rotates, and equal-count
  thread switches reused stale offsets - rows rendered the next message's
  text at the previous message's position. The dead dirty_timeline rescue
  (cleared before its async consumer could read it) is removed.
- New chatVirtTryAppendLayout fast path: pure appends extend offsets for
  the new tail instead of re-measuring the whole thread (the full measure
  is ~100 ms of UI stall per received message on a 5000-message SD ring).
- lv_async_call failure no longer wedges the render busy flag; the nav
  focus fallback validates s_nav_objs[0] before focusing it (bubbles now
  recycle on scroll-end, so slot 0 can be one tick stale); dead
  chatVirtClearAllChildren/DeleteMsgsChild pair removed; stray
  FIRMWARE_BUILD_DATE bump reverted.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 11:38:25 +02:00
Kaj bf96253308 Merge pull request #138 from 446564/finish-m9
m9 stable
2026-07-09 08:31:47 +02:00
Kaj SchittecatandClaude Fable 5 65a485d28c Merge main (RAK Tap V2 port) into finish-m9
Union of both PRs' landscape home-chart gate (TDECK || TANMATSU || RAK_TAP_V2 || THINKNODE_M9).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 08:26:49 +02:00
Kaj SchittecatandClaude Fable 5 b2950a7f88 fix(m9): restore the T-Deck/M9 control-center card arm + drop unreachable HOME leftover + lock-hint typo
The control-center sizing lost its '#elif HAS_TDECK_GT911' line, which
put the 200 px set_size inside the Tanmatsu arm (shrinking its card
from 384 to 200) and dropped the T-Deck into the portrait else-arm.
Restored as TDECK || M9. Also removed the unreachable duplicate lines
after the M9_KEY_HOME return and fixed 'hole the d-pad' on the lock
screen hint.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 08:24:33 +02:00
Kaj SchittecatandClaude Fable 5 e95dd755e1 fix(rak_tap_v2): stray paren in the CAP_LARGE_SCREEN arm + keep power-menu height on existing boards
The bare ')' under #if CAP_LARGE_SCREEN broke the Tanmatsu (P4) build,
the only target that compiles that arm. The power-menu #else arm went
back to the original card_h = 206 so T-Deck/V4 keep their exact layout.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 08:09:21 +02:00
Ethan-chen1234-zy 2532ddc7ba fix(rak_tap_v2): gate shared-path changes behind HAS_RAK_TAP_V2 2026-07-09 08:09:21 +02:00
Ethan-chen1234-zyandCursor 6309503060 fix(rak_tap_v2): align target with upstream ClockFloorRTC and PubSubClient dep
Signed-off-by: Ethan-chen1234-zy <ethan.chen@rakwireless.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-09 08:09:21 +02:00
Ethan-chen1234-zyandCursor b7bebd508b feat(rak_tap_v2): rebase onto upstream, add device_caps and README
Signed-off-by: Ethan-chen1234-zy <ethan.chen@rakwireless.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-09 08:09:21 +02:00
Ethan-chen1234-zy b470097534 feat(rak_tap_v2): HW CDC upload, tiles partition, hide download mode
Signed-off-by: Ethan-chen1234-zy <ethan.chen@rakwireless.com>
2026-07-09 08:09:21 +02:00
Ethan-chen1234-zy 1aab86b530 feat(rak_tap_v2): BOOT button support, USB CDC, upload fix
- PIN_USER_BTN: -1 -> 0 (enable BOOT key on GPIO0)
- Short press (<1s): toggle screen on/off (no hard-lock)
- Long press (>=1s): open power menu (Power off / Reboot / Cancel)
- Add ARDUINO_USB_CDC_ON_BOOT=1 (stable USB CDC COM port)
- boards/rak_tap_v2.json: use_1200bps_touch=false, wait_for_upload_port=false
  (manual download mode via BOOT+RESET, esptool upload on COM7)
- Remove unused boards/wiscore_rak3312.json
- Remove LovyanGFX from Heltec lib_deps (accidental regression in baseline)

Signed-off-by: Ethan-chen1234-zy <ethan.chen@rakwireless.com>
2026-07-09 08:09:21 +02:00
Ethan-chen1234-zy bc129b5ffb feat(rak_tap_v2): LovyanGFX HW FSPI display driver (30+ fps)
Replace USE_PIN_TFT bit-bang software SPI (~8-10 fps) with LovyanGFX
hardware FSPI (SPI2_HOST, 40 MHz, DMA) matching Meshtastic's architecture.

Files:
- variants/rak_tap_v2/LGFXDisplay.{h,cpp}: new DisplayDriver via LovyanGFX
- variants/rak_tap_v2/target.{h,cpp}: SPI.begin() in radio_init() for FSPI
- platformio.ini: DISPLAY_CLASS=LGFXDisplay, LGFX_INVERT_COLOR, LovyanGFX dep
- src/ui-touch/UITask.cpp: RAK path includes LGFXDisplay + 320x40 LVGL buffer
- NOTICE: LovyanGFX dependency

Signed-off-by: Ethan-chen1234-zy <ethan.chen@rakwireless.com>
2026-07-09 08:09:21 +02:00
Ethan-chen1234-zy 8133a47769 feat(rak_tap_v2): add RAK WisMesh Tap V2 board support (working baseline)
Display: USE_PIN_TFT software SPI, 8-10 fps, 40-line LVGL buffer
Touch: FT5x06 I2C 0x38, runtime rotation 3 + FLIP_X/Y
UI: landscape LV_DISP_ROT_270, mapRaw with RAW_W=240/RAW_H=320
Radio: LoRa SX1262 on HSPI (SPI3_HOST), 240MHz CPU
Signed-off-by: Ethan-chen1234-zy <ethan.chen@rakwireless.com>
2026-07-09 08:09:21 +02:00
Tesso M Costa 4bbfcb5550 pager: let the rotary encoder scroll an open dropdown's list
updatePagerEncoder() never special-cased an open lv_dropdown, so a
plain turn always sent LV_KEY_NEXT/PREV -- but lv_dropdown's own key
handling only understands LV_KEY_UP/DOWN to move the highlighted row
when its list is open, and ignores NEXT/PREV entirely. Those instead
got consumed by the focus group to move focus off the dropdown, so
turning the encoder never moved the highlight and the list stayed
stuck on whatever was already selected (reported: opens fine, but
can't scroll to a choice, in Radio & Mesh's Community Preset and
other dropdowns).

Capture the encoder the same way Tanmatsu's navPump() already does
for its own input path: while navOpenDropdown() is true, route turns
as LV_KEY_DOWN/UP instead of NEXT/PREV. The short-click path already
sends LV_KEY_ENTER, which lv_dropdown uses to confirm the highlighted
row and close, so no change needed there.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 18:56:43 -06:00
Tesso M Costa 9bcad3c2c2 pager: skip redundant radio-param save/reapply on unedited field blur
Radio & Mesh settings auto-saved (flash write + live LR1121 SPI
reconfigure) on every textarea LV_EVENT_DEFOCUSED, even when nothing
changed. Touch boards rarely trip this (a field only blurs on a
deliberate tap-out after editing), but the pager has no touch
fallback, so plain keyboard/encoder navigation blurs a field on every
step -- arrowing through the freq/bw/sf/cr/tx/airtime row re-ran a
real radio reinit up to six times with no edits made, observed on
hardware as escalating multi-second [STALL] ui:lvgl entries.

Skip the save/reapply on a silent (defocus) blur when the parsed
values already match NodePrefs, gated to TLORA_PAGER so touch boards
keep their existing always-save-on-blur behavior unchanged.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 17:54:01 -06:00
Tesso M Costa bf5c6828a3 pager: Enter opens message action menu, Backspace jumps to latest
Enter on a focused chat bubble now opens the same Ack/Mention/Copy/
Info/Block action menu the T-Deck opens on a long-press, instead of
being a no-op. Hoisted navEnterBubble() out of its HAS_TANMATSU-only
guard (it was already board-agnostic) and reused it from the pager's
Enter branch in handleHwKey() -- it forwards Enter as a synthetic
LV_EVENT_LONG_PRESSED to the focused bubble, the same event the touch
long-press itself sends.

A plain Backspace tap also now does what tapping the T-Deck's floating
"scroll to bottom" circle does: jump the chat to the latest message
and hide the circle (mirroring the Tanmatsu F6 hardware-key handler,
which had the jump but was missing the hide), then move nav focus to
the composer so a reply can be typed immediately instead of leaving
focus on whatever bubble was selected pre-jump. Only intercepted while
the circle is actually showing, so Backspace at the bottom of a chat
(or outside one) keeps its normal no-op / hold-to-back behavior.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 15:44:05 -06:00
Tesso M Costa facbe49b01 pager: fix Enter not activating a focused non-composer widget
handleHwKey() treated "a textarea is bound to the on-screen keyboard"
as "we're editing a field", but showKb() binds the composer as soon as
a chat panel opens and never unbinds it just because nav focus moved
elsewhere in the same panel. So with focus on, say, the quick-reply or
emoji icon, Enter fell into the composer's submit/newline handling
instead of activating the actually-focused widget -- the rotary
encoder's short click worked because it bypasses this function
entirely (navPushTap(LV_KEY_ENTER) goes straight into the focus
group). Now only treated as editing when nav focus is really on that
field, mirroring the CAP_TRACKBALL boards' existing s_kbd_nav/
s_nav_ta_editing distinction for the same problem.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 15:10:50 -06:00
Tesso M Costa 3c845115bf pager: lay out Quick Reply as a 2-column grid, widen the card
The pager's 480px landscape screen left most of the quick-reply card's
width empty, since it shared the same 220px single-column sizing as
the narrower T-Deck/Heltec V4 screens. Widened to 360px and switched
to a 2-column grid (3 rows instead of 6) for this board specifically;
the button-placement loop is now column/row-based instead of a single
vertical stack, driven by per-board cols/col_gap constants so the
other boards' layout is unchanged. Focus navigation needed no changes
since it's already purely position-based (navMoveDir scores by each
widget's actual on-screen rect).

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 15:00:40 -06:00
Tesso M Costa f59d9f4b23 pager: add hold-space-to-lock / hold-backspace-to-unlock
Mirrors the T-Deck's spacebar-lock/trackball-unlock experience for the
pager. Unlike the T-Deck's keyboard, the TCA8418 here reports real
press/release, so this is a genuine hold (with a live-filling
"Locking…" progress popup) rather than the T-Deck's tap+countdown
workaround. Backspace was chosen for unlock over the rotary encoder:
its raw held-state stays readable via PagerKeyboard's own poll loop
regardless of screen power state, while the encoder's poller currently
exits early whenever the screen is off.

Fixes three existing bypasses that would otherwise make the new lock
pointless -- on this board, a plain encoder turn, a BOOT-button press,
or any ordinary keypress all unconditionally called wakeScreen()
(which clears the manual-lock flag) with no hold requirement, so
anything at all would instantly unlock a "locked" screen. Each now
checks isManualLock() first; only the deliberate Backspace hold clears
it. The BOOT-button fix is scoped to TLORA_PAGER specifically, since
that same code path is shared with the Heltec V4, which has no
keyboard and relies on BOOT as its only lock/unlock control.

Also updates the two user-facing "how to unlock" hint strings (the
Settings lock-on-screen-off toggle, and the T-Deck-style lock overlay
text, the latter currently dead code on this board since that overlay
is never built here) so they don't keep pointing at a trackball this
board doesn't have.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 14:49:27 -06:00
Kaj SchittecatandClaude Fable 5 48e77933e2 touch: beta_37 release notes
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 22:09:36 +02:00
Tesso M Costa 49a6f80419 pager: let D/F nudge a focused slider, quieten default volume
No touch or trackball on this board means a focused lv_slider (Control
Center brightness, a Settings slider, the Map zoom bar, ...) couldn't
be adjusted at all via keypad nav. D/F now drive it through
navMoveDir()'s existing slider-capture branch -- the same proportional
step, live-update, and persist-on-release the T-Deck trackball's
LEFT/RIGHT already does -- instead of a fixed one-unit-per-press step
that's wrong for every slider's range.

Also lower the pager's default notification volume to 50%: its ES8311
codec + NS4150B amp run louder at a given percentage than the T-Deck's
I2S amp/Tanmatsu's ES8156, so the shared 70% default clipped into
uncomfortable territory on this board specifically.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 13:59:19 -06:00
Kaj SchittecatandClaude Fable 5 667436fdd2 touch(tdeck): GT911 phantom-press watchdogs + bounded init retry
A flash/reset landing mid-I2C-transaction can wedge the GT911 (the S3
resets, the touch controller keeps running) into repeating a stale
pressed frame. The driver's keep-prev-state-on-no-data poll then latched
an eternal press: real touches ignored, trackball clicks eaten (a live
touch outranks the click injection), idle timeout never firing, keyboard
lock/unlock still working - a dead-looking device that survived every
reboot and reflash because only a full power cycle resets the GT911.

Watchdogs in gt911Poll() now force a release when status reads fail
mid-press, when no frame arrives for 250 ms while pressed (a real held
finger produces a frame every GT911 scan cycle), or when one bit-exact
point stays pressed for 10 s (a human touch always jitters) - that last
point is then ignored until it moves or a real lift frame arrives. A
jitter-y phantom can still need a power cycle, but the common wedge
modes self-heal in under a second.

Init is no longer one-shot: the boot probe retries every 500 ms for
~6 s before caching failure, so a GT911 still resetting at the first
attempt no longer costs the session its touch AND keyboard (the kb
poll task only starts once touch inits).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 21:43:40 +02:00
Tesso M Costa d59cf5d9ae pager: fix control-center card overflowing the 222px screen
Adding the Sound chip's HAS_UI_SOUND to the pager built put 6 chips
into a row whose width was hardcoded for 5 (a leftover from when the
row only served the Heltec V4), and the chip's gap constant didn't
match the row's own pad_column, so the extra chip wrapped onto a
clipped 2nd line. Chip width is now derived from the actual chip
count instead of a fixed divisor.

The card height itself was also a shared V4/T-Deck-landscape constant
tuned for a 240px-tall screen; the pager's screen is only 222px tall,
so that height overflowed the visible root and pushed the toggle row
and sysinfo line off the bottom of the physical display. The pager
now sizes its card from the actual available height.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 12:10:23 -06:00
Tesso M Costa e682fbcb5c pager: add notification sound via the onboard ES8311 codec
Brings the T-LoRa Pager to feature parity with the T-Deck's notification
sound (built-in per-slot chimes, custom WAV playback, per-event on/off,
volume, Settings > Sound UI) using the board's ES8311 codec + NS4150B
Class-D amp, previously undriven.

- Es8311Codec: a minimal, hand-rolled I2C register driver (DAC/output path
  only) rather than vendoring Espressif's much larger esp_codec_dev HAL,
  which this single-chip playback-only board doesn't need. Register
  sequence and MCLK clock-divider coefficients are derived from Espressif's
  public es8311.c/es8311_reg.h (Apache-2.0, credited in NOTICE).
- TLoraPagerBoard::setAmpEnabled() toggles the amp around playback rather
  than leaving it permanently on; the existing boot-time AMP_EN drive stays
  as-is since it exists for shared-bus integrity reasons unrelated to audio.
  A boot-time I2C presence probe logs [BOOT] es8311 ok/PROBE FAILED.
- UITask.cpp: pager I2S/codec playback functions mirroring the existing
  T-Deck ones, plumbed into the same uiPlaySlot()/uiPreviewWavFile()
  dispatch the other boards use (which also had two T-Deck-hardcoded call
  sites generalized as part of this). New CAP_SOUND_FILES capability flag
  gates the file-browsing sound picker without reopening real SD support
  (the pager remains SPIFFS-only, decoupled from CAP_SD).
- platformio.ini: I2S pin flags for the pager env, confirmed against
  arduino-esp32's canonical pins_arduino.h for this board.

Verified on hardware: boot log shows es8311 ok, and chimes/volume/WAV
playback/DM+mention sounds all confirmed audible. Build-green on all three
envs; Heltec V4 binary byte-identical, T-Deck flash +16 bytes.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 11:45:33 -06:00
Tesso M Costa db7a43fcc4 pager: add Alt-tap-to-NEXT and backspace-hold-to-back input gestures
PagerKeyboard now distinguishes a solo Alt tap (press+release with
nothing else happening) from Alt held as a modifier (symbol-layer
typing, or the encoder's Alt+turn free-scroll) via
pagerKeyboardConsumeAltTap()/pagerKeyboardMarkAltUsed(), and exposes
pagerKeyboardBackspaceHeld() alongside the existing immediate-'\b'
press behavior.

Wires both into UITask: a solo Alt tap advances focus one step
(LV_KEY_NEXT), same as one rotary detent, and holding Backspace for
1s triggers the same "back" ladder as the encoder's long-press
(pagerNavGoBack(), factored out of updatePagerEncoder so both paths
agree exactly) — giving keyboard-only users a way back without
relying on the encoder. Also routes Enter through navPushTap when no
text field is focused (plain widget nav, including during the setup
wizard) and widens the radio settings SF/CR/TX/AF row's top margin
(was crowding the label above it).

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 11:02:49 -06:00
Tesso M Costa cca9a444e8 gitignore: generalize pager doc tracking to the whole dev-docs/ dir
Replaces the three individually-named TLORA_PAGER_PORT*.md entries with
/dev-docs/ so any future tracker added under that directory is covered
without another gitignore edit; also ignore /crash-dumps/.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-08 11:02:38 -06:00
Enot (ded) Skelly 381658ab2a Merge branch 'main' into finish-m9 2026-07-08 09:44:41 -07:00
Enot (ded) Skelly 4846d4fa51 fix: bug in batt logging, sd didn't check if directory exists
which would mean the user had not yet enabled loggin to sd but only
mounted a card
2026-07-08 09:40:02 -07:00
Enot (ded) Skelly c322b1fa3a chore: update m9 port doc 2026-07-08 09:31:05 -07:00
Steve GlennerandCursor d964c029d9 touch: virtualize chat scrolling (bubble + compact)
Viewport-based message virtualization for open chats: only the visible
window of LVGL widgets is materialised while layout offsets cover the
full thread (up to msgCap). Supports bubble and compact IRC modes, day
separators, jump to oldest/latest, and compressed LVGL scroll coords
for very long histories.

Finger drags advance layout scroll 1:1 even when coords are compressed,
so long histories scroll fluidly without micro-drags that trigger bubble
long-press menus.

Includes LVGL crash hardening from soak testing: defer refreshChatDetail
and bubble reflow off the indev/refresh path, sync-delete during async
render, size chatVirtEnsureMsgIdx to msgCap for the SD deep ring, and
open-to-bottom scroll that does not rely on premature scroll_bottom.

Fixes #126

Signed-off-by: Steve Glenner <steveglenner@hotmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-08 09:21:49 -07:00
Kaj SchittecatandClaude Fable 5 d2d3060051 touch: don't double-shift the layout indicator in the tall chat bar
It is align_to'd against the clock's final translated coords each tick; the
tall-bar top-row translate on top of that pushed its upper half out of the
bar (clipped) inside a chat.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 16:58:49 +02:00
Kaj SchittecatandClaude Fable 5 e2eb0d3118 touch: show the keyboard-layout indicator only inside a chat/channel
Typing (and thus the active layout) only matters in an open conversation;
everywhere else the language name was permanent bar clutter next to the clock.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 16:53:21 +02:00
Kaj SchittecatandClaude Fable 5 dd19cbe52d touch: park the keyboard-layout indicator relative to the clock on every board
The EN/DE indicator sat at a fixed -182 right offset while the clock's left
edge reaches past that in 12-hour mode ('7:45 PM'), overlapping on the T-Deck
bar. The Tanmatsu branch already parked it align_to the clock; un-gate that so
all boards track the clock wherever it lands (12/24h width, charging slide,
centred hide-name mode).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 16:43:15 +02:00
Yaz aa598d626b ui-touch: GPS position as the first quick-reply row
Adds the node's live GPS position as the first row of the chat quick-reply
picker: with a fix it shows the coordinates and a tap inserts them into the
composer at the cursor (same no-auto-send contract as the macro rows, so the
operator can add context before sending); without a live fix the row is
greyed out and disabled. Sharing where you are is one of the most common
things typed into a mesh chat, and hand-copying coordinates from the GPS
screen was the only way to do it.

Signed-off-by: Yaz <yazutsu@users.noreply.github.com>
2026-07-08 16:23:05 +02:00
Steve GlennerandCursor 862ec32f80 touch: fix SD message history flush reliability
Ensure the tile-fetch worker is running before arming a message-ring flush,
fall back to a synchronous write if spawn fails, write ui_msgs_v1.bin via a
.tmp rename for crash-safe replacement, and retry when the worker snapshot is
missing instead of treating the flush as successful.

Signed-off-by: Steve Glenner <steveglenner@hotmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-08 16:21:16 +02:00
Yaz 1eeeb267d2 ui-touch: make the Settings keyboard-backlight Off preset switch the mode off
Follow-up to the keyboard-backlight brightness control (issue #84). The Off
preset used to set the brightness percent to 0 while leaving the backlight
MODE untouched, inventing a second dark state: the keyboard went dark but the
control-center chip - which cycles and shows the mode - kept saying on/auto.

Off now switches the mode off, the same axis the CC chip shows, so the two
surfaces can never disagree. The brightness slider becomes 1-100: dark is
only expressible via the mode, and the on/auto modes always glow visibly at
the chosen level. The stored percent is left untouched by Off, so re-enabling
the backlight restores the previous brightness; a stored 0 from the previous
build is clamped to 1 at boot.

Signed-off-by: Yaz <yazutsu@users.noreply.github.com>
2026-07-08 16:18:16 +02:00
Kaj SchittecatandClaude Fable 5 2b30ca2a5a touch: Tanmatsu umlauts (#129) — ALT accent picker, double-space language cycle, compressed fonts
- ALT-accent picker on the Tanmatsu physical keyboard: hold ALT + letter
  opens the accent popup with the first variant highlighted, the letter
  cycles (auto-repeat walks the options), releasing ALT (its own scancode
  event) inserts the highlighted choice. Popup is nav-skipped/non-clickable
  so keypad-nav focus can't steal the cycle key, SC()-scaled, align-centred.
- Double-tap-space language cycle ported to the Tanmatsu typing path
  (navPump), and keyboardLayoutsApply now updates the active layout even
  with no on-screen keyboard object (was a permanent no-op there).
- Fonts: LV_USE_FONT_COMPRESSED on; extras_font_12/14/16 regenerated
  compressed (identical text glyphs; redundant mono emoji dropped — the
  colour imgfont covers emoji) freeing ~340 KB; new compressed Latin-accent
  extras_lat_20/24/28 spliced into the Large/Huge fallback chain
  (Tanmatsu-only) so umlauts size-match the scaled UI. Tanmatsu app.bin =
  3,269,440 B, UNDER the known-booting 3,271,856 B (50-page AppFS ceiling).
- TEMP: TDECK_KEYCODE_PROBE toast (build-flag gated, inert in releases)
  for mapping the T-Deck alt key.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-08 16:16:53 +02:00
Tesso M Costa dc4ba96825 stop tracking the M7 hardware debug log, same as the other pager trackers
TLORA_PAGER_M7_HW_DEBUG_LOG.md is a blow-by-blow hardware bring-up log,
not a published project doc -- same treatment already applied to
TLORA_PAGER_PORT.md/TLORA_PAGER_PORT_MILESTONES.md and CLAUDE.md. File
stays on disk locally, just out of version control going forward.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 17:19:45 -06:00
Tesso M Costa f18929b312 stop tracking pager port trackers, matching CLAUDE.md's convention
TLORA_PAGER_PORT.md and TLORA_PAGER_PORT_MILESTONES.md are working
hardware bring-up notes, not published project docs -- same treatment
CLAUDE.md/.claude/ already get in this .gitignore. Files stay on disk
locally, just out of version control going forward.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 17:01:06 -06:00
Tesso M Costa df7f9bc2ab pager: fix encoder direction, and Alt+turn free-scroll for nested screens
Encoder direction was backwards on hardware (confirmed by user testing):
kQuadTable's CW/CCW sign didn't match this physical part's wiring, so
turning the way you'd expect to move forward/down moved focus and
scroll backward/up instead. Negated once in pagerEncoderReadDelta()
so every consumer (nav NEXT/PREV, Alt+turn tab-switch, Alt+turn page
scroll) inherits the corrected sense from one place.

Also scope the pager's Alt+encoder gesture: it used to always jump
between main tabs, even from inside a settings sheet or chat, silently
abandoning it. Now Alt+turn only tab-switches at the main-tab level
(navOnMainPage()); inside a nested scrollable screen it instead
free-scrolls the page like a touch drag (navScrollFocused()'s ANIMATED
lv_obj_scroll_by, unlike navFocusCb's one-shot LV_ANIM_OFF
scroll_to_view, reliably repaints on this board), then snaps focus to
whatever's now nearest the top of the visible viewport
(navRefocusFirstVisible()) so plain NEXT/PREV resumes from a visible
spot instead of a focus stuck off-glass.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 16:52:44 -06:00
Enot (ded) Skelly 2a34ad476e fix: m9 lock screen wake + bugfix lock paint
lockscreen was not being painted until after the display
wakes showing the previous screen, changed to paint lock
screen then wake
2026-07-07 15:16:18 -07:00
Enot (ded) Skelly 0ea242c81f feat: m9 long press enter key context menus 2026-07-07 14:55:56 -07:00
Tesso M Costa b3c638842e pager: fix LR1121 TX power default and RX-boosted-gain gating
Boot TX power was left at a conservative 10dBm (Heltec V4's pattern) with
no way to raise it, unlike the T-Deck which boots straight at the chip's
real 22dBm ceiling. On hardware this was silently degrading outbound
range: adverts/DMs sent from the pager were unreliable while inbound
reception was fine, since the far node's own TX power was unaffected.
22dBm is confirmed as this chip's actual sub-GHz HP-PA ceiling via
RadioLib's LR1120::checkOutputPower() (LR1121 inherits it) and matches
trail-mate's own working config for this board.

Also widen the three RX-boosted-gain gates in MyMesh.cpp/DataStore.cpp
that only checked USE_SX1262/USE_SX1268 to include USE_LR1121 --
CustomLR1121Wrapper already implements setRxBoostedGainMode/
getRxBoostedGainMode, so the setting was silently a no-op for this radio.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 15:50:07 -06:00
Enot (ded) Skelly a8f8a79d3f fix: show lock screen settings for m9 2026-07-07 14:47:25 -07:00
Enot (ded) Skelly 30ed2d77f6 fix: m9 control toggle layout 2026-07-07 14:06:23 -07:00
Enot (ded) Skelly c87cd3cc98 chore: update m9 port doc 2026-07-07 13:42:31 -07:00
Enot (ded) Skelly 996eac21fd feat: add buzzer for m9 2026-07-07 13:35:00 -07:00
Enot (ded) Skelly 3a3a37d193 feat: add m9 sd card 2026-07-07 13:23:20 -07:00
Tesso M Costa 05b24f01ad pager: fix encoder wake-selects-Skip, and confirm-before-advance on region pick
Two related first-boot-wizard bugs found on hardware:

- updatePagerEncoder() woke the screen on either a turn OR a bare click.
  Waking via click let the SAME press-release cycle fall straight into
  the short-click logic further down as an ordinary click on whatever was
  already focused -- concretely, it selected "Skip" on the wizard's
  welcome screen the instant the screen lit up. Only a turn wakes the
  screen now; BOOT is unchanged and still wakes via its own path.

- The region step's 20-preset list auto-jumped focus to Next on the
  FIRST click, before the row's colour change was even visible -- no way
  to confirm the right region got picked before focus moved off the
  list. Changed to two-step: the first click on a row selects/recolours
  it and focus stays put; a second click on the row that's ALREADY
  selected is treated as the explicit confirm and jumps focus to Next.

Both gated CAP_KEYPAD_NAV (Tanmatsu + pager); T-Deck/Heltec V4 touch
flows are unaffected either way (moving the internal group focus is
invisible without active keypad-nav).

User-verified fixed on hardware (fresh first-boot flash, region select,
Wi-Fi connect, and map tile auto-download all working).

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 14:16:21 -06:00
Enot (ded) Skelly dcf3958cc7 fix: m9 gps 2026-07-07 12:30:15 -07:00
Enot (ded) Skelly 6de8346e7f feat: add m9 mentions and advert hw button handlers 2026-07-07 10:34:57 -07:00
Tesso M Costa f61b8fbbcf pager: Alt+rotary jumps between main tabs
The bottom tab bar (Chats/Contacts/Home/Map/Settings) is deliberately not
a nav-group focus target, same as T-Deck/Tanmatsu -- but those boards
reach it via their own dedicated hotkeys (programmable keys / coloured
shape keys), which the pager has none of. Plain rotary turning could
therefore only ever move focus within the current screen; the tab bar
icons were unreachable from Home (or anywhere else).

Exposed pagerKeyboardAltHeld() (raw modifier state already tracked by
pagerKeyboardPoll() to drive the symbol layer, just never surfaced
before) and used it in updatePagerEncoder(): holding Alt (the bottom-left
orange key) while turning the encoder now calls navSwitchTab(+-1) per
detent instead of the normal focus-move NEXT/PREV, cycling through the
5 main tabs directly. Alt alone still types nothing, so this doesn't
take anything away from the keyboard.

User-verified fixed on hardware.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 11:21:57 -06:00
Enot (ded) Skelly be32315b98 chore: remove old m9 kb debug print 2026-07-07 10:14:39 -07:00
Tesso M Costa fe4ed029f5 pager: make rotary long-press a real universal back gesture
Two gaps left "hold to go back" not actually working anywhere but inside
a popup:

- The popup registry (anyPopupOpen()/hwKeyDismissTopPopup(), which drives
  the actual dismiss) only recognized HAS_TDECK_GT911/HAS_TANMATSU, so it
  never knew how to close the pager's own Terminal fullscreen view or its
  command picker -- the encoder's long-press was sending a raw Esc key
  that nothing handled. Widened to TLORA_PAGER.

- Even with that fixed, a BARE main tab (Chats, Contacts, Map, Settings)
  is neither a popup nor an open chat/channel detail, so the back cascade
  fell through to a no-op Esc. T-Deck/Tanmatsu don't hit this because they
  have separate dedicated Home hotkeys; the pager has none (no
  programmable keys, and the bottom tab bar is deliberately not a
  nav-group target). Added a third rung: fall back to the Home tab before
  plain Esc, matching every other "close" path in this app (the
  Terminal/Files Home button, the fullscreen-view popup closer) already
  landing on Home rather than a real back-stack.

User-verified fixed on hardware.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 11:12:18 -06:00
Tesso M Costa 53251c33e0 pager: reset idle timer on keyboard and encoder activity
Neither input path called noteUserInput() for the common no-field-focused
case, so the idle timeout kept counting down during active use:

- handleHwKey()'s no-textarea branch only calls noteUserInput() when
  dismissing a popup or matching a tab hotkey. tabForKey() no longer maps
  any letters (tab jumps moved to the trackball-only programmable
  hotkeys) and isDismissKey() always returns false for the pager's full
  QWERTY, so with no field focused, every keypress silently no-op'd here.

- updatePagerEncoder() only called noteUserInput() to wake an already-off
  screen; turning or clicking the encoder while the screen was ON never
  reset the timer.

This board has no touch and no trackball to fall back on for idle-reset,
so both gaps were fatal: the screen dimmed after ~30s of real use.

User-verified fixed on hardware.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 10:45:17 -06:00
Tesso M Costa f9c3db99c2 ui: scope keypad/trackball nav to the frontmost top-layer popup
navMaybeRebuild() re-roots keyboard/rotary focus onto lv_layer_top() as
soon as ANY child is visible there, but collected the WHOLE top layer.
Fullscreen views that spawn their own popups (Terminal's command picker,
file manager prompts/action sheets) add those popups as separate
lv_layer_top() siblings rather than nesting them in the view, so with two
visible top-layer children at once, nav walked the hidden view underneath
before ever reaching the popup on top of it (reported: opening the
terminal's command picker left rotary focus on the terminal behind it).

LVGL has no z-index — child order is stacking order — so the last
visible, non-NAV_SKIP child is the one actually on top. Added
navTopFrontmostChild() and root nav on it instead of the whole top layer.
Single-popup screens are unaffected (same one child either way).

Not board-gated: this is a general nav-focus correctness fix that
benefits any board using keypad/trackball navigation, not pager-specific.

User-verified fixed on hardware.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 10:34:59 -06:00
Tesso M Costa 230b0936bc pager: fix terminal Enter-to-submit and always-on rotary focus highlight
Two related non-touch navigation bugs on the pager's Terminal screen:

- handleHwKey()'s ENTER handling only routed to terminalSubmit() under
  HAS_TDECK_GT911, so physical-keyboard Enter fell through to hideKb()
  instead of running the typed command. Widened to TLORA_PAGER.

- s_nav_show (whether the amber keypad-focus ring is painted) only
  defaulted true for HAS_TANMATSU ("keyboard-only device: focus highlight
  is always visible"); every other board, including the pager, defaulted
  false and only flips true inside CAP_TRACKBALL-gated code, which never
  runs on the pager (no trackball). Since the pager also has no touch,
  rotary-driven focus was moving but never rendered, so the terminal's
  send button looked unselectable. Widened to TLORA_PAGER, matching the
  Tanmatsu's rationale exactly.

User-verified fixed on hardware.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 10:25:10 -06:00
Enot (ded) Skelly 5da14d8bda fix: highlight selected textarea for hw nav 2026-07-07 09:21:29 -07:00
Enot (ded) Skelly 32e1668406 fix: bug in deep nested containers
they did not scroll because the parent was scrollable but they were not.
so scrolling with navigation through elements did not work
2026-07-07 09:15:25 -07:00
Tesso M Costa d4ca18335e pager: keep home TX/RX chart clear of the right-hand button column
makeHome()'s chart_w gate only widened the chart's cleared strip for
HAS_TDECK_GT911/HAS_TANMATSU, so the pager (landscape, same right-hand
Advert/Terminal/Apps/Control column) fell into the full-width else branch
and the chart border/Sig chip ran under the buttons. Add TLORA_PAGER to
the gate, matching the other landscape boards.

User-verified fixed on hardware.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 10:10:00 -06:00
Enot (ded) Skelly 259aa36e40 fix: m9 correct home button behavior
was not working correctly on app drawer
2026-07-07 09:01:16 -07:00
Tesso M Costa 78a6c01f95 pager: fix M7 hardware bring-up bugs, verify UI/keyboard/encoder on device
Six real bugs found and fixed across two hardware sessions (full account in
TLORA_PAGER_M7_HW_DEBUG_LOG.md): stale-NVS BLE bond crash, no screen-wake
path for keyboard/encoder input, wrong TFT_eSPI SPI-port index on ESP32-S3,
missing panel INVON for this ST7796 batch, two SPI hosts fighting over the
shared radio/display pins, and a floating XL9555 ch6 panel hardware-reset
line (the actual root cause of the intermittent black screen, not the SPI
race originally suspected). TLoraPagerBoard::begin() now drives the full
vendor rail set including the display reset pulse and parks shared-SPI
selects high before first bus traffic.

Boot logo, full LVGL UI, QWERTY keyboard navigation, and rotary encoder
nav/select are now verified working on real hardware. Trackers updated:
Milestone 7's UI portion is done; the remaining radio/USB-companion/SD
gates move to a new Milestone 7b so they don't block Milestone 8's
on-device UI pass, which is now active.

All three envs (Heltec V4, T-Deck, pager) build green.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-07 09:44:36 -06:00
Enot (ded) Skelly 51b513b181 fix: m9 backlight level 2026-07-07 08:42:03 -07:00
Kaj SchittecatandClaude Fable 5 6dc09b3185 touch: beta_36 — Launcher SD storage both ways, edit menu on all fields (#122), Wi-Fi full-screen sheets, lockscreen unread (#93), SD update download, AU Mid preset (#121)
- Edit menu (Cut/Copy/Paste/All/Sym) + double-tap select on every settings
  field via attachSettingsTaEvents; menu actions route through the keyboard
  mirror when bound (#122)
- Wi-Fi join/hidden/details sheets: full-screen settings-style pages riding
  the tall status bar title (s_apppage hook), on lv_scr_act so the bar's
  glass row isn't clipped
- Lock screen unread badge (envelope + count, anti-burn-in drift) (#93)
- About: Save update bin to SD (/BINS/wadamesh-<tag>-<channel>.bin) for
  Launcher installs; beta-channel toggle no longer gated on the OTA slot
- Australia (Mid) preset 915.075/125/SF9/CR5 (#121)
- M9: [M9KB] key debug print (bring-up)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-07 11:18:55 +02:00
Kaj SchittecatandClaude Fable 5 b3004b85eb fix(esp32): use_sd toggle follow-up — both directions on Launcher installs (PR #123 review)
Two edges from the #123 review:
- The raw-NVS mirror is best-effort now: on installs with unusable NVS
  (Launcher) the file write is the authoritative copy, so a failed mirror
  no longer fails the setter.
- When prefs actively live on the SD card, the toggle also rewrites the
  SPIFFS copy of touch.kv (record-preserving; new SdNvsPrefs::fileFs()
  accessor tells the setter which fs is active). Without this, boot's
  SPIFFS fallback kept reading the stale use_sd=true and SD storage could
  be turned on but never off again where NVS is broken.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-07 11:06:02 +02:00
Steve GlennerandCursor a7d435b03b fix(esp32): honor use_sd from touch prefs at boot
UI stores the SD toggle in /prefs/touch.kv via SdNvsPrefs; boot only read
raw NVS. Dual-write on change and read NVS with touch.kv fallback so SD
storage selection survives reboot.

Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Steve Glenner <steveglenner@hotmail.com>
2026-07-07 10:58:58 +02:00
Kaj Schittecat 8718e49827 chore: refresh Mesh America catalog for beta_35 2026-07-07 09:50:26 +02:00
Tesso M Costa 641700fad0 touch: wire T-LoRa Pager into UITask (M6)
Adds the pager as a first-class non-touch UI target: new device_caps.h
block (no touch, hw keyboard + rotary-encoder nav, 480x222, GPS/OTA/lock
screen; SD/filesystem left off since the mount code is still hardcoded to
HAS_TDECK_GT911, not genuinely CAP_SD-generic), KEYPAD indev registration
reusing the Tanmatsu keypad plumbing, forced 480x222 landscape rotation,
keyboard/encoder input drain in the main loop, and AW9364-correct
brightness wiring ahead of the existing PWM backlight branch.

Also fixes two latent gaps this surfaced: navMaybeRebuild() was
unreachable for the pager's cap combination (would have left the focus
group permanently empty), and several HAS_TDECK_KEYBOARD-gated helpers
needed their reopened regions individually widened rather than the file
touched wholesale.

All three envs build green; Heltec V4 TFT and T-Deck binaries are
byte-identical to pre-change (25.3%/73.5%), confirming every edit stayed
behind the pager gate.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-06 19:06:31 -06:00
Enot (ded) Skelly 38c0e7a016 correct m9 adc and add backlight handling 2026-07-06 15:45:29 -07:00
Tesso M Costa 3e71867e71 pager: add TCA8418 keyboard + rotary encoder drivers
PagerKeyboard.{h,cpp}: TCA8418 matrix keyboard over I2C. Unlike the
T-Deck's keyboard (a second MCU that resolves ASCII itself), the
TCA8418 only reports raw row/col events, so the keymap and
shift/sym/alt state machine live here -- keymap tables cribbed from
trail-mate's LilyGoKeyboard (same physical PCB). Press/release
polarity verified against the TCA8418 datasheet directly, since it
disagrees with the Adafruit library's own header comment. Backlight is
direct LEDC PWM on GPIO 46, using this framework version's actual
channel-based API (confirmed before writing the call, not assumed).

PagerEncoder.{h,cpp}: true A/B quadrature decode via a standard
Gray-code transition table, ISR-cheap-arithmetic-only like
TDeckTrackball's pattern (that driver's 4 discrete direction pins
aren't actually quadrature, so its exact shape doesn't transfer, only
the ISR/snapshot-read style does). Detent scaling (4 raw transitions
per detent) is an unverified assumption pending hardware bring-up.

Both gated on HAS_PAGER_KEYBOARD/HAS_PAGER_ENCODER, already reached by
every env's existing helpers/input build filter. All three envs build
green.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-06 16:35:11 -06:00
Enot (ded) Skelly 0be7c20600 fix m9 commander layout 2026-07-06 15:14:46 -07:00
Tesso M Costa ae690e3fbb pager: add platformio.ini env (first full compile)
[env:tlora_pager_lr1121_companion_radio_touch], cloned from the T-Deck
env with board/radio/display/GPS deltas for the LR1121 + ST7796 pager.

Two structural fixes were needed to actually get this to compile:

- pins_arduino.h moves to its own variants/lilygo_tlora_pager_pins/
  folder (board JSON's "variant" field updated to match). PlatformIO's
  arduino-esp32 build script unconditionally compiles every source
  file under board_build.variants_dir/<board.variant>/ as a separate
  framework-level library with none of our own lib_deps -- since this
  board (unlike T-Deck/Heltec, which point at framework-bundled
  variants) has no framework-bundled variant of its own, our
  variants_dir override was colliding with our own board-glue files
  and failing to find Wire.h/RadioLib.h.

- CustomLR1121Wrapper.h's bare quoted includes of RadioLibWrappers.h/
  LR11x0Reset.h only resolve for core-lib files living in the same
  directory as their targets; switched to angle-bracket includes with
  the full core-lib subpath.

Also required one small, forced addition to UITask.cpp: its display
class selection only recognized the Tanmatsu vs. everything-else split,
which made this env's own hard compile gate unreachable. Added a single
#elif arm for the pager's display type: no other UITask.cpp behavior
changes, indev/resolution/layout wiring is still a later milestone.

All three envs (Heltec V4, T-Deck, pager) build green.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-06 16:14:00 -06:00
Enot (ded) Skelly ad98f661cc fix m9 navigation 2026-07-06 15:02:15 -07:00
Tesso M Costa 546cc9079a pager: add ST7796 display driver + AW9364 backlight (src/helpers/ui)
ST7796LCDDisplay implements the core's DisplayDriver interface on
TFT_eSPI for the pager's 480x222 landscape panel -- the first real
TFT_eSPI consumer in this codebase, since ST7789LCDDisplay (the sibling
this was modeled on) turns out to be Adafruit_GFX-based for both
Heltec V4 and T-Deck. Every TFT_eSPI call was verified against the
pinned library source rather than assumed.

Backlight is the AW9364 stepped pulse-dimmer, wrapped directly in the
display class via SensorLib's AW9364LedDriver (already a dependency)
rather than a hand-rolled pulse timer, exposing a pct-based
setBrightness()/getBrightness() hook for a later UITask.cpp wiring
pass.

Also adds a compile-time guard for CGRAM_OFFSET: this panel's 222px
glass is narrower than the ST7796 controller's native GRAM, and
TFT_eSPI only applies the required coordinate offset when that flag is
set. Without the guard, a missing flag would build clean but silently
shift every frame by 49px.

Nothing references these files yet, so the shipping T-Deck/Heltec V4
envs are unaffected.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-06 15:10:18 -06:00
Tesso M Costa 9d5df3001d pager: add port tracker + milestone playbook docs
TLORA_PAGER_PORT.md is the living status/decisions/risks tracker for
the T-LoRa Pager port; TLORA_PAGER_PORT_MILESTONES.md breaks the work
into ordered, agent-executable milestones with gates. Kept off main
until the port is further along.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-06 14:24:33 -06:00
Tesso M Costa 82b6d3b56d pager: land LR1121 radio glue (target.h/.cpp + CustomLR1121 wrapper)
CustomLR1121{,Wrapper}.h are adapted from the core fork's CustomLR1110
pair (upstream MeshCore has no LR1121 support yet to crib instead).
target.cpp's radio_init() spells out the LR1121 bring-up sequence
directly since there's no std_init() helper for this chip: begin()
with the NodePrefs-driven params and TCXO voltage passed straight in,
the DIO5/DIO6 RF-switch table, and a CRC-length override to match the
other radio wrappers' wire-protocol framing. Nothing references these
files yet, so the shipping T-Deck/Heltec V4 envs are unaffected.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-06 14:22:51 -06:00
Kaj SchittecatandClaude Fable 5 a38ea1e3bb touch: Elecrow ThinkNode M9 port (ESP32-S3 + LR1110 + I2C QWERTY) — bring-up builds 1-9
New board: ThinkNode_M9_companion_radio_touch env, variants/thinknode_m9/
(board glue, LR1110 target, keyboard driver, partitions, M9_PORT.md pin
reference), boards/thinknode_m9.json, device_caps HAS_THINKNODE_M9 block,
HAS_M9_KEYBOARD input path in the touch UI (d-pad focus nav, tab jump keys,
QWERTY typing).

Based on a contributed bring-up patch by ded (SalishMesh), who also remote-
tested every build on a preproduction unit. Hard-won fixes on top of the
patch, each verified on hardware:

- LR1110 radio init -706: preprod chips run transceiver FW 0x0303, which
  rejects DriveDiosInSleepMode (0x012A, added in FW 0x0308) that RadioLib
  7.x sends unconditionally during begin(). New build-time patch
  scripts/build/patch_radiolib_lr11x0.py tolerates it on old FW;
  radio_init() prints the chip's device/FW/errors either way.
- TCXO: DIO3 at 3.3 V (the patch's active-oscillator/tcxo=0 theory gave
  -707 on hardware).
- Display: rotation 1 (not 3), plus the missing landscape s_ui_rotation
  override so LVGL renders 320x240 instead of portrait-into-landscape.
- Keyboard: the controller is a separate ESP32-S2 I2C slave (0x6C) with
  addressed registers - reads select register 0x01 first (bare reads
  return the HW-version register forever). Boot probe logs the
  controller's HW/FW; backlight duty register wired.
- USB pad release: the keyboard bus lives on GPIO20/21 = the S3's native
  USB D-/D+ pads, owned from reset by the ROM USB-Serial-JTAG (D+ pullup
  on SDA). M9Board::begin() releases them before any bus init.
- GPIO35-37 are octal-PSRAM pins on the S3R8 - never drive them (the
  patch's "SD CS = 36" misread package pin 36 = GPIO48; SD is on the
  shared SPI bus, support returns with PIN_SD_CS=48 later).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 21:49:25 +02:00
Tesso M Costa be1996ce77 pager: land T-LoRa Pager variant skeleton (board JSON + board class)
Board class, pins, and partition table for the LilyGo T-LoRa Pager
(ESP32-S3, LR1121 radio variant), modeled on the T-Deck's shape.
TLoraPagerBoard brings up the XL9555 power-rail expander and BQ27220
fuel gauge over I2C (this board has no VBAT ADC divider). Nothing
references these files yet, so the shipping T-Deck/Heltec V4 envs are
unaffected; radio/display/env wiring land in follow-up commits.

Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
2026-07-06 13:43:24 -06:00
Kaj SchittecatandClaude Fable 5 01900296f3 touch: beta_35 — worker-thread history flush, radio memory guards, 30.5 KB DRAM freed, crash-safe prefs
- History flush runs on the core-0 worker (snapshot + storage-busy gate +
  bounded shutdown wait): kills the V4's multi-second ui:hist stalls and
  the refuses-to-wake-after-message symptom (SPIFFS GC off the UI thread).
- BLE + Wi-Fi runtime enables share the boot co-init heap guard (50 KB
  free + 20 KB block): refuse with a toast + revert the switch instead of
  panicking (BLE) or silently not starting while claiming on (Wi-Fi).
- Internal DRAM: static footprint 95,365 -> 64,908 B (30.5 KB freed):
  serial_interface -> PSRAM; 23 keyboard layout maps const'd -> flash;
  nine rings/tables -> psAlloc PSRAM (UITask/TouchPrefsStore/MyMesh);
  unused TinyUSB MSC + DFU-mode class drivers stubbed out of the link
  (usb_unused_class_stubs.c) — CDC + runtime-DFU untouched, double-flash
  verified over the stubbed stack.
- DataStore prefs writes are crash-safe (write .tmp, swap) with a
  self-healing loader (.tmp recovery) and a truthful save result up to
  the profile-name toast — fixes the boots-with-default-name-once report.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 13:34:24 +02:00
Kaj SchittecatandClaude Fable 5 4e1ac2ca6b touch: beta_34 — buffered LoRa receive ON by default (test channel) + core pin core-v1.16.5
Consumes the new core (buffered receive drain task + RX counters, #13
stock payload layout, GPS-date guard). Fork side:
- TouchPrefs v33 rx_queue, DEFAULT ON for the test channel (fresh
  installs + a one-time migrate for upgraders); opt-out toggle
  'Buffered receive (experimental)' in Radio & Mesh, applies live.
- About live tier shows LoRa RX heard/read/err/late-lost/qdrop, the
  field evidence for the missed-messages fix.
- Spectrum parks/resumes the drain task around raw radio use; MyMesh
  setParams sequences hold the radio mutex.
- TanmatsuLoraRadio: no-op API stubs (P4 keeps its own RX path).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 11:15:52 +02:00
Kaj Schittecat 5d9a184314 chore: refresh Mesh America catalog for beta_33 2026-07-05 23:50:32 +02:00
Kaj SchittecatandClaude Fable 5 8e17b1b071 touch: beta_33 — async MQTT connect (freeze fix) + About sketch-size cache + favorites-full toast
- MqttBridge: reconnect() (blocking DNS + TCP + CONNACK, 2-10 s vs an
  unreachable broker, every 15 s) now runs on a one-shot core-0 task;
  _connecting hands the client between threads. Broker socket writes get
  the same zero-timeout writability probe as the TCP/WS companion
  servers, so a wedged broker fails a publish instead of stalling loop().
- About: ESP.getSketchSize()/getFreeSketchSpace() esp_image_verify-walk
  the whole ~3 MB image (~190 ms each); the 1 Hz refresh cost ~390 ms/s
  and flooded the stall ring (the ui:sbar entries field testers
  photographed). Computed once and cached.
- Favorites: adding past the 16-cap now toasts 'Favorites full (max 16)'
  instead of the wrong 'Removed from favorites'.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-05 23:34:22 +02:00
Kaj SchittecatandClaude Fable 5 b58cecab5c touch: beta_32 — non-blocking TCP/WS companion writes (Wi-Fi freeze fix) + chunked history flush + stall diagnostics
Root cause of the beta_31 periodic 1-2s freezes with Wi-Fi on: every
received mesh packet pushes an RX-log frame to all connected TCP/WS
companion clients from the loop thread, and writeAllBytes called
WiFiClient::write() unguarded — against a stale peer (phone asleep,
half-open socket) that blocks in the framework's 1s select() retries.
The 120ms app timeout only bounded attempts, not the first call.

- TCP+WS servers: probe writability (zero-timeout select on the client
  fd) before every write; lwIP reports writable only with ~2.8KB free,
  a whole frame is ~180B, so probed writes complete instantly.
- Reap clients whose writes fail continuously for 10s (half-open
  sockets previously stayed "connected" forever, eating the write
  budget on every pushed frame).
- Chat-history ring: chunked writer + wider flush spacing (same
  treatment saveContacts got in beta_30).
- Stall tracer: 16-entry ring of >=0.2s loop stalls, shown in About.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-05 22:55:42 +02:00
Kaj Schittecat 816045bb6b chore: refresh Mesh America catalog for beta_31 2026-07-05 21:13:27 +02:00
Kaj SchittecatandClaude Fable 5 11939a744e touch: beta_31 — WhatsApp-style chats tab (avatars + previews) with per-channel custom icons
- Default chat list: 56px rows with a round initials avatar in the thread's
  FNV-hue signature colour, last-message preview (getThreadLastMessage ring
  accessor), time top-right, unread pill + @ below; compact chat mode keeps
  the dense 34px contact-style rows (layout mode mixed into the rebuild sig)
- Per-channel avatar emoji: 'Chat icon' in the thread-settings sheet (tap =
  emoji sheet in new pick mode, long-press = reset to letters); persisted in
  a chmute-style keyed blob (touchPrefsGet/SetChannelEmoji, 24 x 48B)
- Fix: name/preview overlap (LONG_DOT labels need fixed one-line heights)
- Thread-sheet grid gap 6->4 so the 7th channel cell keeps one screen on T-Deck

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-05 21:07:42 +02:00
Kaj SchittecatandClaude Fable 5 f47d71a05b touch: beta_30 — big-mesh contacts perf (buffered save, in-place age labels, coalesced rebuilds) + live Spectrum
- DataStore::saveContacts packs byte-identical 152B records into ~5KB chunk
  writes (was ~12 tiny FS writes per contact: 2.6-3.0s at ~570 contacts on the
  loop thread — the #82 sluggishness); falls back to per-field writes on alloc failure
- Contacts 60s age tick updates the Heard labels in place (was a ~1.3s full
  teardown+rebuild); advert-driven rebuilds coalesced to one per 2.5s
- Spectrum: rolling waterfall row + live trace every quarter sweep (~250ms),
  8-bin/8ms sweep chunks (~20% faster full sweep); trace Y range now tracks the
  live min/max — instant expand, 3dB/sweep contract, 30dB minimum span

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-05 13:08:40 +02:00
Kaj SchittecatandClaude Fable 5 8eb63a7edd touch: beta_29 — clock floor for room-server replay guards, BLE repeats-heard, deep SD history, one-screen popups
- ClockFloorRTC on all boards: persisted monotonic send-timestamp floor (touchPrefs v32),
  garbage-set rejection, trusted-backstep cap; Join no-reply watchdog + server clock
  skew warning from the LOGIN_OK timestamp prefix (issue #89 follow-up)
- BLE repeats-heard: own-echo RX-log frames pass to BLE one-shot; the #46/#54
  congestion skip stays for everything else (issue #94)
- Mirror app-sent channel messages on-device (was Tanmatsu-only from birth)
- Chat delete: persist the ring purge; mesh-channel drop prefers the pinned slot
- Deep SD history (5000-msg ring) + date separators; chat-list rows restyled compact
- Popup unification: popupClose() + k_popup_registry drive dismiss/count/swipe-block
- Thread/channel sheet as one-screen 2-col grid (contact-sheet layout)
- Keypad nav: strip LVGL SCROLL_ON_FOCUS from collected widgets (About-page jump);
  update dot no longer focusable; verchk waits for an IP + retries with backoff
- Tanmatsu: FIRMWARE_RELEASE_TAG from git describe (drop the hand-bumped hardcode)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-05 10:07:16 +02:00
Kaj SchittecatandClaude Opus 4.8 5623237951 site: dismissible donate banner -> support the MeshCore founders
Sticky top banner asking would-be donors to help the MeshCore founders instead — links to the blog post (Learn more) and the givealittle donation page (Donate). Dismissible (x + localStorage), and it shifts the corner FAB rails down while shown so they don't collide with the close button.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-04 15:22:37 +02:00
Kaj SchittecatandClaude Fable 5 b90b8bac14 touch: beta_28 — room-server session fix (#89), ST7789 panel sleep, wyvern feedback batch
- Rooms: re-enable the keep-alive pinger (checkConnections), arm a 128s
  keep-alive on LOGIN_OK (servers send 0), blank-relogin self-heal while a
  room chat is open, 'Log in again' in the room sheet, read-only warning.
  Root-caused against simple_room_server: 3 unACKed pushes freeze a client
  until the server hears from it — and we never pinged (issue #89).
- Burn-in: ST7789 SLPIN/SLPOUT on screen-off (backlight-off alone kept the
  panel driving the static image), lit-lock dim guard on all boards, 10s
  notify-wake re-dim, lock clock pixel drift.
- wyvern.red batch: scroll-keys map zoom, backspace exits empty composer,
  Reset path in the chat sheet, compact chat toggle (TouchPrefs v31),
  clearer delivery glyphs + tap-to-resend on failed sends.
- OTA: hide Install-update when the running image's physical address falls
  outside the esp_ota running slot (mixed/legacy tables; beta_21 coredump).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-04 13:40:02 +02:00
Kaj Schittecat 3585b3a1e0 chore: refresh Mesh America catalog for beta_27 2026-07-04 08:45:41 +02:00
Kaj SchittecatandClaude Fable 5 a4d3715529 release-notes: beta_27 stable rollup (beta_26 + beta_27 since stable beta_25)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-04 08:45:29 +02:00
Kaj SchittecatandClaude Opus 4.8 ffc501d09d touch: hide on-device Install-update button on Launcher installs
touchHasOtaUpdateSlot() checked only that a spare OTA partition exists
(esp_ota_get_next_update_partition != NULL). Under bmorcelli's Launcher a
spare slot exists but is smaller than our image, so the check passed, the
Install-update button showed, and Update.begin() failed "won't fit: Bad Size
Given" (reported by Keith/KM1USR on beta_24 under Launcher). Require the target
slot be at least as large as the running slot; the whole OTA block (Install /
previous-version / beta toggle, already gated on this) then hides on Launcher
installs, where updates go through the Launcher. The update-available notice
still shows.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-03 08:04:35 +02:00
Yaz 61666ac033 ui-touch: keyboard-backlight brightness control for the T-Deck (issue #84)
The T-Keyboard's C3 firmware takes a 2-byte I2C command [0x01, level 0-255],
but the level the UI drove it at was hardcoded 0xFF, so the backlight was
always 100% when lit. Adds a Keyboard backlight control at the top of
Settings -> Keyboard: a live slider plus Off/25/50/75/Max one-tap presets,
scaling the lit level for the on and auto modes (and the new-message flash).
The percent persists in the existing kbd_bl pref shared with the Tanmatsu
slider; adjusting it while the mode is off flips the mode to on, mirroring
the Tanmatsu control-centre behaviour.

Three latency lessons learned on the way:
- pct->duty is gamma-2 mapped: perceived LED brightness is roughly
  logarithmic in duty, so a linear map felt coarse at the dim end.
- the NVS save is debounced (one-shot timer re-armed per change): the pref
  setter rewrites the whole TouchCfg blob via cfgFlush(), which can block
  the UI thread for a good fraction of a second per tap.
- backlight requests now flush on every touch-poll tick (~8 ms) instead of
  riding the ~32 ms keyboard-scan cadence, and the Settings controls request
  the level directly instead of waiting for the next UITask::loop pass - so
  the control feels as immediate as the screen-brightness slider (whose
  ledcWrite hits the ESP32's own PWM peripheral synchronously).

Signed-off-by: Yaz <yazutsu@users.noreply.github.com>
2026-07-03 07:16:08 +02:00
Kaj SchittecatandClaude Opus 4.8 5f69a61c9c touch: beta_26 — fix SPIFFS-GC watchdog reboot loop (contacts->SD + shared guard)
Decoded a T-Deck coredump (Task WDT, loopTask stuck in spiffs_gc_clean under
DataStore::saveContacts): a contact save on a churned SPIFFS can trigger a
multi-second garbage-collection pass that starves core 0 and trips the task
watchdog, giving a reboot loop.

- Route contacts/channels to SD when a card is present, even on upgraded
  devices whose data is still on SPIFFS (main.cpp mounts SD every boot; if not
  fully adopting SD, store.setSecondaryFS(&SD)). DataStore::begin() migrates the
  existing /contacts3 + /channels2 to the card once; identity/prefs stay put.
- Move the ref-counted WdtHeavyGuard into a shared header so the core
  DataStore::saveContacts shares one count with the UI history/backup saves, and
  wrap saveContacts with it (guaranteed fix for card-less devices).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-02 21:11:19 +02:00
Kaj SchittecatandClaude Opus 4.8 ddc4a34d4d docs(site): add microSD-card storage tip to the overview
Recommend keeping a card inserted on SD-capable devices (T-Deck, Tanmatsu) so tiles,
contacts and chat history live on the card and avoid the limited/less-reliable internal flash.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-02 11:08:02 +02:00
Kaj SchittecatandClaude Opus 4.8 df4a675cd3 deploy(meshamerica): match official MeshCore device names + add provider description
TJ Downes flagged that provider device names must match MeshCore's canonical names exactly
or they list as NEW devices instead of folding into the existing tiles. Rename to the official
'Heltec v4 + Expansion Kit (Touch)' and 'LilyGo T-Deck' (verified against the live config), and
add the new optional 'description' blurb shown on the provider badge tooltip.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-02 09:40:15 +02:00
Kaj SchittecatandClaude Opus 4.8 8d068cfcc1 docs(site): add 'Bring your own tiles' offline-maps section to the Map page
Explains the microSD tile-pack layout (/maps/osm or /tiles, z/x/y, PNG/JPEG), the
'Tiles from SD card' toggle, making a pack, and per-board differences (T-Deck / V4 / Tanmatsu).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-02 08:58:16 +02:00
Kaj Schittecat c4f31e5a69 chore: refresh Mesh America catalog for beta_25 2026-07-01 23:44:43 +02:00
Kaj SchittecatandClaude Opus 4.8 0af47e5936 release: beta_25 stable notes — aggregate beta_22..25 over stable beta_21
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 23:44:40 +02:00
Kaj SchittecatandClaude Opus 4.8 492d0886ec touch: beta_25 (test) — contacts-list refresh, advertise-on-boot, Tanmatsu SD tiles + persistence
- Contacts list rebuilds on advert (force past the count-cache) + a count-delta safety
  net, so a node discovered off-tab or added by the phone app shows immediately (#73)
- New "Advertise on boot" toggle in the Advertise app, off by default (#76)
- Tanmatsu: cache Wi-Fi map tiles on microSD (the P4's internal FFat metadata layer is
  broken — f_getfree/f_stat lie); read tiles via open() not the misreporting exists()/size()
- Tanmatsu: persist contacts/channels/chat on microSD (DataStore secondary FS + chat
  history) so they survive reboot; identity/prefs stay on the (working) internal FFat
- Tanmatsu: boot fix (drop Serial.begin re-init of USB-Serial-JTAG), MQTT disabled, popups
  fit + scroll, keyboard-nav scoped to the open popup, 2000 contacts, Large UI default
- Emoji/quick-reply Esc/red-X closes the popup not the chat; lock-screen unlock after msg-wake

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 23:28:13 +02:00
Dan Vybiral 96dffaef58 touch: fix manual telemetry request reliability + async spinner blink
Two bugs in the manual telemetry request path (the Request button in the
telemetry window):

1. Usually only the second request succeeded. The guest LOGIN and the
   telemetry REQ were sent back-to-back, but a repeater drops a REQ from a
   sender it hasn't added to its ACL yet, and the ACL entry isn't committed
   by the time the first REQ is processed — so the first request got no reply
   and the user had to tap twice. Defer the REQ: uiSendRequestAfterGuestLogin()
   sends only the guest LOGIN and fires the REQ from onContactResponse once the
   LOGIN-OK arrives, by which point we're in the repeater's ACL and a direct
   out_path has been learned, so it lands on the first try. Also adds a
   single-flight guard on telemetryRequestNow(), holds auto-poll while a manual
   request is pending (so it can't clobber the pending reply tag), and disarms
   the deferred login on timeout so a late LOGIN-OK can't fire a stale REQ.

2. The status-bar async spinner only blinked for ~1.5s on a telemetry request
   (the markMeshRequest window) then froze, instead of blinking for the whole
   pending window like a status ping. Its active predicate watched the ping
   deadline but not the telemetry timers; OR in the telemetry pending state.

Auto-poll's best-effort chained send and the admin-console login path are
left unchanged.
2026-07-01 20:52:45 +02:00
Kaj SchittecatandClaude Opus 4.8 3a1495784e touch: beta_24 — signal probe uses standard node-discovery packet
The signal probe now sends a zero-hop NODE_DISCOVER_REQ control packet
(the standard MeshCore node-discovery that the Ultra / KiekR apps use)
instead of a trace, which repeaters do not answer. Repeaters reply
directly with a NODE_DISCOVER_RESP, captured in onControlDataRecv by
matching the probe tag into _ui_sig_* SNR/RSSI. Thanks to Tarmo for
decoding the exact packet.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 14:46:33 +02:00
Kaj SchittecatandClaude Opus 4.8 26c9ccdc07 touch: beta_23 (test) — keep the per-packet RX log off BLE (#46, #54)
The device broadcast a PUSH_CODE_LOG_RX_DATA frame to every connected companion —
including BLE — for every LoRa packet it heard. BLE's ~16 frames/sec budget got
saturated on a busy mesh, delaying/dropping the frames that matter: chat messages
(#46) and repeater/room-server admin responses (#54, the "Streamsink" disconnects).
Skip the RX log on the BLE transport in writeFrameToAll; USB/TCP/WS still get it for
the on-device Monitor app. The MeshCore app never consumed it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 10:15:13 +02:00
Kaj SchittecatandClaude Opus 4.8 0d8e635848 site: document Stable vs Test channels + how to opt in
Landing page: a plain-language Stable vs Beta explainer under the install channel
toggle, covering both install paths (flash a channel here, or flip the on-device
"Get test builds" toggle). Userguide: a new "Updates & test builds" section (how
updates work, the two channels, how to turn on test builds) plus a Get-test-builds
line on the About settings card.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 09:19:23 +02:00
Kaj SchittecatandClaude Opus 4.8 0731b5ff67 touch: beta_22 (test) — trace-ping signal probe + companion contact-refresh (#73)
Signal probe: replace the beta_21 zero-hop advert (which nothing replies to, so the
signal never updated) with a directed TRACE ping to the nearest reachable repeater.
It retransmits — a real reply we measure — without flooding the mesh. New
MyMesh::uiSendSignalProbe() picks the shortest-path repeater; the reply is captured
silently in onTraceRecv via _ui_sig_probe_tag. Falls back to a zero-hop advert when
no repeater is known. Thanks to Tarmo for the insight.

Contacts (#73 part A): a contact discovered while a companion app is connected over
BLE now refreshes the device's own Contacts list + notification. onDiscoveredContact
fired the UI notify only in the standalone branch — move it out so it always fires,
and flag the list dirty for UITask::loop to rebuild on the LVGL thread.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 08:46:56 +02:00
b5e428734c release: credit Samuel Coustet (@samuelcoustet, #71) for the MQTT bridge
The beta_21 MQTT bridge is based on @samuelcoustet's PR #71, reworked for privacy
(consent gate, direct messages off by default, payload encryption). Record the
attribution in the release notes + the version.json "what's new".

Co-authored-by: Samuel Coustet <257299705+samuelcoustet@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 18:28:31 +02:00
Kaj SchittecatandClaude Opus 4.8 18904c9a5d deploy(nginx): serve the TEST/BETA channel paths on firmware.wadamesh.com
The two-channel rollout added releases/BETA + latest-beta, but the firmware
vhost only had exact-match handling for the old stable paths. Add:
- location = /releases/BETA  -> serves releases/BETA/index.json at the no-slash
  path the device requests when 'Get test builds (beta)' is on (mirrors TOUCH).
- location /latest-beta/      -> the beta web-flasher feed (was hitting the 404
  catch-all).

Stable paths and all bins under /releases/ were already correct; this only wires
up the new beta directory-index + feed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 17:47:46 +02:00
Kaj Schittecat 39a4db8f03 chore: refresh Mesh America catalog for beta_21 2026-06-30 17:36:58 +02:00
Kaj SchittecatandClaude Opus 4.8 03e50b0609 touch: beta_21 — first stable build + test channel, MQTT bridge, contacts & signal-probe fixes
New: stable/test update channels with an opt-in "Get test builds (beta)" toggle on
OTA devices (switches both the update check and what you install); experimental
opt-in MQTT bridge (consent-gated, payload encryption, direct messages off by
default); Portugal (Narrow) region preset (#74); saved-contacts counter in the
Contacts overflow menu (#72).

Fixed: the signal probe is now strictly zero-hop so a repeater can't re-flood it;
the contact list sorts before capping so the most relevant contacts show, with a
"+N more — search to narrow" footer (#73); the blocked-users list opened from
Contacts shows the two-line title bar with a back button; the Contacts overflow
popup fits the screen again.

Also lands the two-channel release tooling (scripts/release.sh stable/beta modes +
gen-flasher-meta channel arg), the docs site, and the MQTT reference decryptor.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 17:34:11 +02:00
Kaj SchittecatandClaude Opus 4.8 d75db73fc8 release: credit Yazutsu (#66) for the WAV notification sounds in beta_20 notes
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 23:50:46 +02:00
Kaj Schittecat 56cf91ef5b chore: refresh Mesh America catalog for beta_20 2026-06-28 23:36:03 +02:00
Kaj SchittecatandClaude Opus 4.8 b4c941f954 touch: beta_20 - spectrum analyzer, custom sounds, saved Wi-Fi, V4 high-gain RX, flood-scope + channel-send fixes
New: Spectrum analyzer app; custom notification sounds (SD WAV per event);
saved Wi-Fi networks with auto-join; unified chat settings screen; per-channel
mute; Heltec V4.3 high-gain receiver (FEM LNA) toggle; Apps button on the V4
home screen; Blocked list reachable from Contacts + chat settings; Portuguese
(BR) UI language.

Fixed: touch-screen flood adverts now region-scoped so region repeaters relay
them (#68); channel sends matched by name so a message can't go out on the
wrong channel's key; opt-in "scope direct messages to region" so room-server
logins work through a region-only path (#64); Wi-Fi scan no longer cancelled
by the reconnect retry (empty SSID list).

Under the hood: flood-scope rework (channel vs direct floods); Spectrum owns
the SX1262 while open and restores mesh RX on exit; wifiScanIsActive() gate;
FEM KCT8103L LNA wired; TouchPrefsStore migrations for the new prefs. Adds the
previously-untracked device_caps.h.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 23:33:44 +02:00
Kaj Schittecat 1e00ac3876 chore: refresh Mesh America catalog for beta_19 2026-06-27 15:09:40 +02:00
Kaj SchittecatandClaude Opus 4.8 2b45225e0b touch: beta_19 — scroll-popup crash fix, Radio airtime/telemetry, V4 Home fit
- Fix LVGL scroll-momentum use-after-free reboot when a scrollable overlay
  (emoji / quick-reply / add-channel / channel sheets, Wi-Fi scan, pickers,
  app drawer) is freed mid-throw: new closeScrollOverlay() helper
  (lv_indev_wait_release + lv_obj_del_async). Root-caused from field beta_18
  coredumps.
- Radio & Mesh settings: airtime / duty-cycle readout + "Answer telemetry
  requests" toggle, grouped into RADIO / MESH / SIGNAL sections.
- Accent popup dismissed on Enter-to-send (T-Deck physical keyboard).
- Heltec V4: Expansion-Kit Home env line + chart flow below the stats line
  so they fit the 240x320 screen.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 15:08:03 +02:00
Kaj SchittecatandClaude Opus 4.8 dad7d295dc touch: airtime/duty-cycle readout + answer-telemetry toggle in Radio settings
Two firmware-only additions surfacing capability already in the stack:

- Airtime / duty-cycle readout: the radio modal exposed airtime_factor only as a raw
  'AF' number. Add a derived line — '≈ N% max duty cycle · ~M ms / 40-byte packet' —
  computing duty% from MeshCore's af=(100/duty)-1 and the per-packet time-on-air from
  the Semtech closed-form (new loraToaMs helper). Lets EU-868 users see compliance at
  a glance with no measurement.
- Answer telemetry requests toggle: MeshCore already gates telemetry responses on
  _prefs.telemetry_mode_base/env (0=DENY/2=ALLOW_ALL) but it wasn't in the touch UI.
  Add a switch (new UITask::setTelemetryAllow) that sets battery+environment modes;
  location telemetry keeps its own separate setting so a simple 'allow' can't leak
  position.

(RX boosted gain was already a switch in Experimental settings; per-packet RSSI/SNR
is already in the Monitor; region presets already bundle SF/BW/CR — so those research
items were already shipped and not re-added.)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-27 10:21:12 +02:00
Kaj SchittecatandClaude Opus 4.8 2d49fb69ec site: add Tanmatsu support; Telegram -> Discord
- List the Tanmatsu (ESP32-P4) in the hero + meta description.
- Add a Tanmatsu box to the standalone installer: no USB flashing — install from the Tanmatsu app store on-device — plus a link to Nicolai Electronics' shop. Boards grid now auto-fits 3 cards.
- Replace the Telegram floating button with Discord (discord.gg/T8X2UaQ7Sm).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-26 20:45:47 +02:00
Kaj Schittecat 94ef98a12f chore: refresh Mesh America catalog for beta_18 2026-06-26 19:54:08 +02:00
Kaj Schittecat 2db46ec190 release: beta_18 notes 2026-06-26 19:51:31 +02:00
Kaj SchittecatandClaude Opus 4.8 11775ce5ac tanmatsu(lora): apply runtime radio-config changes to the C6 modem
The Tanmatsu's LoRa modem lives on the C6 coprocessor, shared with the Tanmatsu OS's own
LoRa settings. pushConfig() no-op'd once RX polling started (the remote link can block
under RX load), so a runtime frequency/SF/BW/CR/power change from the wadamesh radio
settings only updated _cfg and took effect on the NEXT REBOOT — the radio stayed on
whatever the OS or boot last set. That is the 'change the wadamesh frequency but receive
nothing on it' report, and why wadamesh's settings never overrode the Tanmatsu OS's.

Now a runtime change marks _cfg dirty and recvRaw() applies it on the RX-poll thread,
between polls: drop to STANDBY (so the link isn't under active-RX load and lora_set_config
can't block), push, re-arm continuous RX. wadamesh's settings now reach the modem live
and win over the OS config. The '0.00001 MHz' the OS page showed is the C6 frequency
corrupted by the two configs fighting; wadamesh consistently owning the config should
clear it — needs on-device confirmation.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 19:44:54 +02:00
Kaj SchittecatandClaude Opus 4.8 7d3b4a4336 tanmatsu: the_mesh in PSRAM on the P4 too (build fix for b986f49)
b986f49 moved the_mesh to PSRAM and changed MyMesh.h's extern to 'MyMesh&', but the
Tanmatsu has its OWN main.cpp (tanmatsu/main/main.cpp, separate from src/main.cpp) that
still declared a plain 'MyMesh the_mesh' global — a conflicting declaration that broke
the P4 build (only the S3 envs were built for b986f49). Apply the same placement-new-
into-PSRAM + reference pattern here; the P4's 32 MB PSRAM gets the same DRAM win.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 19:44:54 +02:00
Kaj SchittecatandClaude Opus 4.8 f78e3ed493 touch: settings category labels fit on one line (no mid-word split)
The Settings landing tiles centred their label in card_w - 80 px (40 px margins each
side). On the T-Deck's 2-column landscape layout that left only ~64 px, so a single
word ('Bluetooth') split mid-word and 'Radio & Mesh' / 'Quick replies' wrapped to two
lines. Lay the label out to the RIGHT of the left accent icon and centre within that
region (~100 px usable) instead of symmetric centring — every English category name
now fits on one line, unsplit. Wide cards (V4 portrait) are unaffected; long
translations still wrap at word boundaries.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 19:24:53 +02:00
Kaj SchittecatandClaude Opus 4.8 b986f49e1a core: move the_mesh (~42 KB) to PSRAM — reclaim internal DRAM
the_mesh was the single biggest static internal-DRAM consumer at 42 KB (dominated
by the MAX_CONTACTS=100 ContactInfo array inside it). Internal DRAM (~320 KB) is the
scarce resource on the ESP32-S3 — Wi-Fi/BLE DMA + heap fight over it, and the V4 was
hitting ~99% on map-tile load (issue #47b). PSRAM (8 MB) is plentiful.

Place the whole the_mesh object in PSRAM via placement-new into a heap_caps_malloc
(MALLOC_CAP_SPIRAM) block and bind a reference, so every the_mesh.foo() call site is
unchanged. The constructor still runs at the SAME static-init point as the old direct
global (PSRAM is already up then), so timing and behaviour are identical; only the
address moves off internal DRAM. Falls back to internal RAM if PSRAM is absent.
ESP32-only (STM32/RP2040 keep the plain global). The contacts array rides along
inside the object — no vendored-core change.

Measured on heltec_v4 (.dram0.bss): 124160 -> 82000 B = ~41 KB internal DRAM freed.
Verified on the T-Deck: clean boot, [BOOT] mesh ok, reason=0, zero panic markers.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 19:11:13 +02:00
f6192aa6e5 touch+deploy: opt-in OpenTopoMap style + persist map link-lines (open PRs)
Implements the three open PRs, with OpenStreetMap kept as the shipping default and
OpenTopoMap added as a user toggle (the deploy PRs flipped the default to topo —
this keeps OSM default and makes topo opt-in).

PR #61 (@Yazutsu) — persist the map 'Show link lines' toggle across reboots:
TouchCfg gains map_show_links (cfg v20, default 1); saved in mapOptLinesCb, loaded
in begin().

PR #52/#53 (@samuelcoustet) — OpenTopoMap tile proxy, adapted:
- deploy: tiles.wadamesh.com.conf keeps the default /{z}/{x}/{y}.jpg on OSM and
  adds /opentopo/ (OpenTopoMap) + an explicit /osm/ alias; tile-transcode.py grows
  _fetch_tile_png/_tile_response_from_png helpers feeding /osm + /opentopo while the
  root route stays OSM.
- firmware: new map_style pref (cfg v21, 0=OSM default, 1=OpenTopoMap) + a
  'Topographic map' switch in Map → Options. Topo tiles are namespaced on disk
  (/tiles/topo) and fetched via the proxy's /opentopo route, so the OSM and topo
  caches never collide and toggling is instant for already-cached tiles. Topo
  bypasses the OSM-only microSD packs and always fetches online; the shared
  (z,x,y) fetch-dedup ring is cleared on toggle so the new style re-queues.

Legal: OpenTopoMap map tiles are © OpenTopoMap (CC-BY-SA) over © OpenStreetMap
contributors (ODbL) + SRTM. The on-map © attribution and the Options → Info credits
sheet switch to that text when topo is active; the proxy keeps a contactable
User-Agent + 14-day cache per OpenTopoMap's tile-usage policy.

Topo needs the VPS deploy (restart wadamesh-tile-transcode + reload nginx) before
the /opentopo route serves; until then topo tiles 404 (handled as a permanent miss,
no retry hammer). OSM default is unaffected.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Yazutsu <andrzej@gruziel.pl>
2026-06-26 18:49:41 +02:00
Kaj SchittecatandClaude Opus 4.8 cff58bbaa2 touch: move Discovered sort to a header icon (always visible)
The inline sort button sat after the empty-list early-return, so a Discovered
list with no entries (the common case when auto-add is on) never showed it, and
even when populated it didn't read as a control. Move it to a ⇄ icon button in the
modal header next to the cog — always present, same proven render path as the
cog/purge, opens the same sort sheet. Purge shifts one slot left to make room.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 18:25:31 +02:00
Kaj SchittecatandClaude Opus 4.8 b31e37cbbe touch: contacts Sort sheet closes on a choice + the close-X works
Regression from the previous commit: making the Sort sheet stay open (for the
asc/desc flip) meant picking a sort no longer dismissed it, and the close-X was a
no-op because it reused the backdrop callback whose target==current_target guard
(meant to ignore child taps on the backdrop) rejected the tap on the badge.

- ctSortOptCb applies the choice and closes the sheet again; flip a mode's
  direction by re-opening and tapping the active row (the ▲/▼ arrow shows it).
- The option-sheet close-X now uses an unconditional close handler instead of the
  guarded backdrop one, so it always dismisses (also fixes the Filter + Discovered
  sort sheets, which share the shell).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 18:16:11 +02:00
Kaj SchittecatandClaude Opus 4.8 76f0754d0d touch: emoji additions, Chats-header button reorder + QR icon, distance sort
Emoji: bake 4 more Noto colour glyphs (soccer, american football, moai,
transgender flag) and add them to the picker. The trans flag is a ZWJ sequence
the single-codepoint imgfont lookup can't render directly, so its combined Noto
image is keyed on the lead codepoint (U+1F3F3) with the trailing symbol mapped to
the zero-width glyph — the whole sequence renders as the one flag. Only the 4 new
glyphs are baked + spliced (scripts/build/add-emoji.py); the existing 252 stay
byte-identical (no Noto-main art drift).

Chats header: group the three actions at the LEFT edge in the order + (add) /
✓ (mark all read) / QR (share), and draw a real baked QR glyph (qr_icon.h, from
scripts/build/gen-qr-icon.py, recoloured to the text colour) instead of the old
LV_SYMBOL_IMAGE 'picture' stand-in.

Contacts sort: every sort option now toggles ascending/descending — re-tapping the
active row in the Sort sheet flips it and shows a ▲/▼ arrow. New 'Nearest first'
(distance) sort orders by distance from our GPS and excludes contacts that have
shared no location.

Discovered list: gains the same sort sheet (Recently heard / Name / Nearest, each
asc/desc) via a sort button at the top of the list; distance likewise excludes
no-location entries.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 18:06:24 +02:00
Kaj SchittecatandClaude Opus 4.8 87cb1c3880 touch: retry transiently-failed map tiles instead of pinning them blank (#20)
renderMapTiles already queues every visible tile (edges + corners) on pan,
and queueTileForFetch marks each one 'seen' the instant it is queued. But the
fetch worker only cleared that mark on success — so a tile whose download hit a
TRANSIENT failure stayed flagged forever and was never re-queued. The heap-
safety gate is the common trigger: during a pan the render thread is decoding a
burst of tiles (heavy internal-DRAM use), so the worker's <12 KB-free skip trips
for several of the freshly-queued edge/corner tiles, which then sit blank until
the user forces a full 'reload tiles'. Wi-Fi blips, a full tile cache and proxy
5xx/timeouts had the same one-shot-and-stuck behaviour.

Add tileFetchForget() and drop the 'seen' mark on every transient failure
(heap gate, Wi-Fi down, cache full, negative/5xx/408/429 HTTP, disk write
hiccup) so the next render miss re-queues the tile automatically. A permanent
4xx rejection still stays marked so we don't re-hammer genuinely-absent tiles.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 17:28:41 +02:00
Kaj SchittecatandClaude Opus 4.8 f39e072bd7 touch: stop debug prints corrupting the binary companion stream (#25, #54, #23)
The companion link is a BINARY protocol over Serial (USB-CDC). Unconditional debug
prints in operational paths — [ROOM] login send/resp, [TILE] fetch, [JPG] decode —
interleaved text into that stream and corrupted it. The MeshCore app then throws
'Bad state: Streamsink is bound to a stream' (#54) and the PC-app connect (#25) and
member-room login (#23) fail. Route them through a gated WIRE_DBG macro
(COMPANION_WIRE_DEBUG, off in release) like the existing SYNC_DEBUG_PRINTLN.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 17:18:07 +02:00
Kaj SchittecatandClaude Opus 4.8 bed04417ed touch(v4): narrow the status-bar name window so a long name clears the clock (#47a)
On the 240px V4 bar the node-name window (74px) left only ~4px before the clock, so a
long name visually ran into the time. Shrink it to 66px for clearance. (Best-effort
without a V4 on the bench; clock position may need a follow-up once verified on-device.)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 17:02:38 +02:00
Kaj SchittecatandClaude Opus 4.8 b1adef7364 touch: keyboard-nav toggle no longer snaps the settings list to the top (#45)
beta_15 preserved scroll on close, but turning keyboard-nav ON still jumped to the
top: the focus group was empty (cleared while nav was off) so navMaybeRebuild had no
focus to keep and fell to the first item, scrolling there. Add a one-shot focus hint
that pins focus to the switch you just toggled.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 16:49:09 +02:00
Kaj SchittecatandClaude Opus 4.8 36e53d9a1c crash report: only prompt on a crash-boot, not every reset
'The device restarted after a crash' re-appeared after a manual reset / power-cycle:
the prompt gated only on a coredump EXISTING in flash, and the dump persists across
resets until exported. Gate crashReportMaybePrompt() on this boot's reset reason
(panic / task-WDT / int-WDT) instead. The dump stays exportable from About + esptool.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 16:37:50 +02:00
Kaj SchittecatandClaude Opus 4.8 7498c502cc touch: widen task-watchdog grace to 20s to stop flash-op WDT reboots (#56)
Decoded coredumps (device + the beta_16 ELFs) are all task-watchdog panics:
CPU0=IDLE0 CPU1=IDLE1, core 0 in spi_flash_op_block_func. A legitimate-but-slow
flash burst (SPIFFS GC, or a bulk DataStore save = thousands of writes) parks both
cores with the cache disabled, starving both IDLE tasks past the ~5s default so the
TWDT panics. The burst can't be chunked under the limit easily and the per-core
WdtHeavyGuard only covers core 0, so re-init the TWDT with a 20s grace (still
catches a genuine multi-second hang) instead. esp_task_wdt_init re-init reconfigures
the running TWDT (old API on this arduino-esp32).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 16:30:33 +02:00
Kaj SchittecatandClaude Opus 4.8 bbb7d31975 touch(tdeck): fix kbd backlight stuck-on after flash (#33) + lock-screen burn-in (#55)
#33: tdeckKeyboardSetBacklight only marked the I2C write dirty on a value CHANGE, and
the cached default is 0. A reflash resets the ESP32 but not the keyboard's C3, which
keeps its lit backlight, so the boot 'off' request (0==0) was never sent. Force the
first write so the C3's retained state is always overwritten.

#55: a hard-locked LIT panel never dimmed (clock burning in) because reveals/taps kept
_last_input_ms fresh. Add a burn-in guard: arm _lock_lit_ms only on a real off->lit
transition and dim the locked panel after a bounded window regardless of the screen
timeout or held/ghost touches.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 08:39:40 +02:00
Kaj SchittecatandClaude Opus 4.8 83cf0202f7 tanmatsu app-store: pre-flight validate name/description vs store regex
Catch a comma/em-dash/over-length description locally and abort, instead of
discovering it as a failed verify_metadata check on the upstream PR.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-25 17:56:33 +02:00
Kaj SchittecatandClaude Opus 4.8 142ea87064 tanmatsu app-store: description without comma/em-dash (verify_metadata regex)
The launcher store's verify_metadata check restricts description to
^[A-Za-z0-9_\- .!@#$%^&*()/\\]+$ (no commas, no em-dash). Reword so the
template passes on its own instead of needing a manual PR edit each release.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-25 17:53:36 +02:00
Kaj SchittecatandClaude Opus 4.8 1ca2f4e3e6 scripts: mark tanmatsu-appstore-publish.sh executable
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-25 17:32:21 +02:00
Kaj SchittecatandClaude Opus 4.8 59b1b2ab09 touch(tanmatsu): beta_17 — Vol± gestures, message LED, microSD, backups on FFat, status-bar fixes
- Vol+ short = top-bar dropdown toggle; long hold = sound master toggle
- Message-notification LED: flash on new message, soft green glow on unread; toggle in Display settings
- Backups use the internal FFat partition (export/scan/import) + Import button on the Backups page
- microSD browsable in the file manager (P4 SDMMC slot 0; the C6 radio's slot 1 untouched)
- Status-bar icon overlaps fixed (charging-slide + language indicator now SC-scaled with the cluster)
- Vol- screen sleep/wake/lock (screen-lock work)
- Companion link: TCP server start + BLE bond NVS persistence + app-sent channel-message mirror

All Tanmatsu changes gated #if defined(HAS_TANMATSU); T-Deck/V4 bins stay byte-identical.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-25 17:30:55 +02:00
Kaj SchittecatandClaude Opus 4.8 c62107c28a tanmatsu: untrack esp-idf/esp-idf-tools (were self-referential symlinks)
main committed tanmatsu/esp-idf + esp-idf-tools as symlinks pointing at their
own absolute path (mode 120000). A fresh 'git checkout main' materialises those
self-loops over the real local ESP-IDF install — breaking the build ('too many
levels of symbolic links' at source export.sh) and deleting the gitignored IDF.
Untrack + gitignore them like the build setup expects; the project-local
ESP-IDF is installed locally, never committed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 16:45:04 +02:00
Kaj Schittecat eb0f3cf0b0 chore: refresh Mesh America catalog for beta_16 2026-06-24 15:45:04 +02:00
Kaj SchittecatandClaude Opus 4.8 36a328a4f7 release: beta_16 notes
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 15:42:41 +02:00
Kaj SchittecatandClaude Opus 4.8 13fca6369f touch: OTA previous-version — one button + version popup + confirm
Reworks the earlier-version OTA UI from three inline buttons into a single
'Install a previous version' button that opens a popup of the available older
betas; picking one shows an are-you-sure confirm (reusing showConfirm) before it
closes and hands off to the existing download/verify/reboot flow.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 15:21:37 +02:00
Kaj SchittecatandClaude Opus 4.8 abdb878006 touch: OTA — install a previous version (up to 3 back)
Adds a 'Reinstall an earlier version' section to the Wi-Fi OTA UI (native
dual-OTA boards only): up to three buttons for beta_(latest-1..3), each flashing
that exact published bin via the same download/verify/reboot path. The worker URL
is parameterised on a target version; the existing 'Install update' button now
routes through the same otaStartInstall(latest) helper. Buttons auto-hide when
there aren't that many earlier releases.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 15:08:18 +02:00
Kaj SchittecatandClaude Opus 4.8 2b4f2bc29e touch: fix status-bar clock overlapping the node name on the V4
The clock's runtime placement used the wide-bar -142 offset on every board,
overriding the V4's intended -126 build slot. On the narrow V4 portrait bar that
pulled the clock left into the width-capped node-name window — the long-standing
'clock overlaps the name' issue. Make the placement bar-width-aware: <300 px bars
(V4) use -126/-94, wide bars (T-Deck/Tanmatsu) keep -142/-110.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 14:47:15 +02:00
Kaj SchittecatandClaude Opus 4.8 79b4f10c25 touch: V4 Sensors tab + Home env widget only when sensors present
Refines the Expansion-Kit UI (#29) so it doesn't intrude on a bare V4: the
Sensors tab and the Home environment widget now appear only when an actual
environment sensor (BME280 / GXHTV3) is detected at boot — battery and GPS no
longer count, so a V4 without the Expansion Kit board shows the normal 5-tab
layout and a clean Home (no empty "Batt ----" / "Temp ...." lines). Adds a
"Show Sensors tab" toggle in Display settings to hide it even when sensors are
present (applies on restart). Tab indices resolve at boot so Settings shifts
back to slot 4 when the Sensors tab is absent.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 14:34:29 +02:00
42746ef387 touch: Heltec V4 Expansion Kit UI + mesh console (issue #29)
Heltec V4 Expansion Kit local-sensor UI, board-gated behind HAS_EXPANSION_KIT
(V4 touch env only — T-Deck/Tanmatsu unaffected): a Sensors bottom tab
(atmosphere / GPS / battery + history charts), a Home env summary widget, an
Expansion Kit card in Device settings, and a Local Sensors detail page. Reads
on-board MeshCore sensors (BME280, SHT4x, battery, GPS, buzzer) via the standard
sensor/telemetry API — no new hardware drivers.

Mesh console: enable the existing Terminal on the V4 (HAS_TOUCH_UI), renamed
"Mesh console", with wifi/tcp/ble on-off + ota status quick commands. The
SD-backed file-manager pieces stay T-Deck-only (V4/Tanmatsu get a no-op path).

Tab indices are conditional so non-Expansion boards keep 5 tabs (Settings=4) and
the V4 gets 6 (Sensors=4, Settings=5). The PR's GPS-nav/waypoint and weather
pressure-alarm bundles were intentionally left out.

Ported from PR #29 by @samuelcoustet, re-applied against current main.

Co-Authored-By: samuelcoustet <257299705+samuelcoustet@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 13:57:40 +02:00
300bf89e1a scripts: add companion-protocol serial test harness
Standalone dev tool (pyserial) that drives the companion binary protocol over a
serial port — DEVICE_QUERY/APP_START, battery/storage, stats, telemetry with a
Cayenne-LPP decoder, and meshcomod CLI commands. No firmware coupling; dev-only.

Ported verbatim from PR #29 by @samuelcoustet.

Co-Authored-By: samuelcoustet <257299705+samuelcoustet@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 12:41:50 +02:00
45e46cd3ab touch: EU keyboard layouts (FR/NL/DE/ES/IT) + auto-select by UI language
Adds French (AZERTY), Dutch, German (QWERTZ), Spanish and Italian layouts — both
the on-screen keyboards and the T-Deck physical-keyboard maps (KeyboardLayoutId
FR..IT). Picking a UI language now auto-enables and selects the matching keyboard
layout, so choosing French gives AZERTY without a separate trip to keyboard
settings. Accented letters still come from the long-press accent popup; no new
fonts required. Extended the settings layout-enable list to match the larger enum
(was a latent out-of-bounds once the layout count grew).

Ported from PR #29 by @samuelcoustet — the layout data applied cleanly; the
UITask wiring was re-applied by hand against current main (the PR was cut from
beta_12 and no longer merges).

Co-Authored-By: samuelcoustet <257299705+samuelcoustet@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 12:41:50 +02:00
Kaj SchittecatandClaude Opus 4.8 4bb7c08bf0 site: standalone — 'install a previous version' picker (latest 4 betas + notes)
Collapsible version picker in the standalone install guide: a dropdown of the latest 4 betas (from the GitHub releases API — the firmware-host listing has no CORS), rendered release notes per version, and selecting a version re-points both Install buttons at that build (client-built manifest -> the CORS-enabled firmware-host -merged.bin). Defaults to latest; switching back restores the /latest/ manifest.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-24 12:35:20 +02:00
Kaj Schittecat 97b24c4268 Merge PR #48: per-channel scope shows default region as placeholder (tun0) 2026-06-24 12:11:23 +02:00
Kaj Schittecat 981fcba226 Merge PR #49: contact action-sheet landscape overflow fix (tun0) 2026-06-24 12:11:23 +02:00
Kaj Schittecat 50f73f41b0 Merge PR #50: edge-scroll — modals block background scroll (tun0) 2026-06-24 12:11:23 +02:00
Kaj SchittecatandClaude Opus 4.8 c5c0a04484 touch: restore Wi-Fi OTA self-update on native dual-OTA boards
Re-enables the over-the-air update that #74 stubbed out — the block then was
undersized 1.5 MB OTA slots, and both touch tables are now 3.875 MB A/B. Wi-Fi
self-update runs again on natively-flashed boards (every V4 + standalone T-Deck);
Launcher single-slot installs and the Tanmatsu (AppFS) keep the manual path.

- Gated on touchHasOtaUpdateSlot() (a spare A/B slot exists) — already drives the
  update badge, so Launcher/Tanmatsu never reach the install path.
- Self-contained Arduino Update flow in the touch app (the vendored core's OTA
  allow-list is meshcomod-only, so we don't route through board.startHttpOtaFromUrl).
  Fetches the immutable releases/TOUCH/beta_<N>/<board>.bin over plain HTTP from
  firmware.wadamesh.com on the tile worker (off the UI thread); progress polled by
  a UI timer.
- Update.begin(len) does the spare-slot select AND the size check, so a legacy
  too-small slot fails cleanly and falls back to the manual flasher message.
- Verify (MD5) + set-bootable via Update.end(true), then rebootDevice() (saves
  chat history first). A corrupt/short download leaves the running slot intact.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 11:56:04 +02:00
Ruben Laban 10ea0d8399 touch: fix contact action sheet overflow on landscape display
The grid_items count missed the conditional "Show on map" button,
causing the card height to be calculated short when the contact has a
GPS fix. Additionally, on landscape displays (sh=240) the backdrop is
only 218px, which repeater cards with many buttons already exceeded.

Fix both: pre-check the GPS condition and include it in grid_items,
and cap the card's displayed height to the available backdrop space
with vertical scroll enabled when the content overflows. The close
badge is FLOATING so it stays anchored regardless of scroll position.
2026-06-24 11:11:56 +02:00
Kaj Schittecat 475245c90e chore: refresh Mesh America catalog for beta_15 2026-06-24 11:01:48 +02:00
Kaj SchittecatandClaude Opus 4.8 1f43a8ba37 release: beta_15 notes — amber power-save battery, @-mention picker (#42), overlay scroll-keep (#45), app-send sync (#46), kbd-nav off by default
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 10:58:45 +02:00
Kaj SchittecatandClaude Opus 4.8 d491065719 touch: power-save shows as an amber battery, not a moon icon (T-Deck)
Idle power-save (light-sleep) advertised itself with a separate crescent-moon
glyph in the status bar. Replace it with an iPhone-Low-Power-Mode-style amber
tint on the battery icon (iOS systemYellow): clearer, and frees the bar slot.
The moon stays in the tree but hidden, keeping the layout and its tap handler.

A single applyBattColor() helper owns the battery colour so the map-chrome
restyle (black/white over light tiles) and the per-tick refresh never fight —
the amber overlays whatever base colour the context wants when power-save is on.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 10:54:06 +02:00
Ruben Laban ab52385f98 touch: edge-scroll — don't fall through to background when dialog is at scroll limit
If lv_layer_top() has a visible widget at the search coordinate (i.e. a
modal or dialog is open), stop the layer search there regardless of whether
a scrollable was found. Prevents the content behind the dialog from being
scrolled when the dialog itself has no more room to scroll.
2026-06-24 10:49:40 +02:00
Kaj SchittecatandClaude Opus 4.8 d11a5bb6b2 touch: keep list scroll position when closing an overlay (issue #45)
Closing a settings item / modal / chat with keyboard-nav on snapped the
underlying list back to the top. navMaybeRebuild rebuilds the focus group when
the overlay closes, but the previously-focused element lived inside the overlay
and is gone, so focus fell to the first list item and the list scrolled up to
show it. Affected every screen because every overlay closes through this path.

Stash the page item that had focus when leaving for an overlay/chat, and restore
it on return — so focus, and the scroll position, land back where they were.
Falls back to the prior behaviour if that item is genuinely gone. Most visible on
beta_14 (keyboard-nav defaulted on); new installs now default it off.

Reported by ZorkaTheDog (#45).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 10:31:47 +02:00
Ruben Laban 80af33e7f9 touch: show default region scope as placeholder in per-channel scope field
When a global region scope is configured, the per-channel override input
now shows it as greyed-out placeholder text instead of the generic "#region",
so users can see at a glance what scope an empty field will inherit.
Falls back to "(no default)" when no global scope is set.
2026-06-24 10:29:35 +02:00
Kaj SchittecatandClaude Opus 4.8 c8849916df touch: show companion-app-sent DMs on the device (issue #46, half 1)
A DM sent from the MeshCore companion app went out over the mesh but never
appeared on the T-Deck: the wire protocol deliberately doesn't echo sent
messages back to clients, so the on-device UI (a separate consumer) never saw
app-originated sends. Add an appSentMsgToContact() UI hook (default no-op for
non-touch UIs); the touch UI mirrors the message as a local outgoing bubble in
the recipient's thread. Called from the CMD_SEND_TXT_MSG handler on first
handling only (a client/transport retry was already mirrored).

Still open: the receive direction (T-Deck-received messages reaching the app) —
queueMessage already pushes RESP_CODE_CONTACT_MSG_RECV_V3 to all transports, so
that half needs a frame capture against the real app to pin down.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 09:54:38 +02:00
Kaj SchittecatandClaude Opus 4.8 278b31cc92 touch: keyboard navigation OFF by default (Tanmatsu stays on)
Reverses the v15 force-on. New installs and existing T-Deck/V4 devices now
default to keyboard-nav OFF (a v18 one-time migration flips existing installs
to off); the user's later explicit on/off then persists. The Tanmatsu is exempt
— it has no touchscreen, so keyboard nav is its only input and stays on.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 09:39:28 +02:00
Kaj SchittecatandClaude Opus 4.8 24f338438e touch: tapping an already-selected field enters edit mode
The touch-to-edit path keyed off navFocusCb (a focus CHANGE), so a field that was
already the selected one — e.g. the Profile node-name field, auto-selected on
entry — couldn't be made typable by tapping it (the tap doesn't re-focus, so
navFocusCb never fires). settingsFieldFocusCb already runs on CLICKED; now a real
tap also sets edit mode, so a selected field becomes typable on tap. Keyboard-nav
onto a field still starts in navigate mode (press Enter).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 09:29:05 +02:00
Kaj SchittecatandClaude Opus 4.8 3e1b45504f touch: navTreeSig must not COUNT NAV_SKIP children (complete the accent-box fix)
The previous fix returned 0 from the recursion for NAV_SKIP/HIDDEN subtrees, but
the parent loop still iterated over the added/removed child (h = h*prime + 0),
so the child COUNT still moved the signature. The accent box + @-mention picker
are created/deleted on every keystroke, so the count flipped each time → rebuild
→ edit-mode reset → typing broke mid-word (and Esc then read as navigate-back,
exiting the screen). Now skip those children in the loop entirely so they never
affect the signature.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 09:22:18 +02:00
Kaj SchittecatandClaude Opus 4.8 12c34a2b35 touch: accent/mention box no longer breaks typing in non-chat fields
Non-chat text fields (add-channel, Wi-Fi, room login, settings modals) live on
the top UI layer, so keyboard nav is rooted there (useTop). The accent box and
@-mention picker are ALSO on the top layer, and they were counting toward
navTreeSig() — so each keystroke that showed/hid the box flipped the signature,
triggered a navMaybeRebuild(), and that rebuild's remove-all + re-focus churn
reset edit mode, dropping you out of typing mid-word.

- navTreeSig() now skips NAV_SKIP_FLAG subtrees (accent box, mention picker), so
  those passive overlays never trigger a rebuild.
- navFocusCb() ignores the transient f==null a rebuild's remove-all emits, so any
  other rebuild can't reset edit mode either.

(The T-Deck never used the keyboard mirror — kbMirrorActive() is false there; the
mirror is V4-only for the on-screen keyboard.)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 09:05:25 +02:00
Kaj SchittecatandClaude Opus 4.8 0a3f9fe82f touch: @-mention picker (#42), edit-mode cursor cue, robust edit-state
- @-mention picker (issue #42): typing "@" in a chat composer pops a touch list
  of matching contacts (prefix-filtered, up to 6); tap one to insert "@Name ".
  Passive NAV_SKIP_FLAG overlay like the accent box; touch-select for now. Takes
  priority over the accent box while a mention is active (composerSuggestRefresh).
- Cursor now reflects edit mode: shown only while editing, hidden while a focused
  field is just the keyboard-nav target — a reliable "ready to type" cue
  (navSyncCursor() each nav tick).
- Edit mode is decided only on a genuine move to a different field, so a rebuild
  that re-focuses the same field (e.g. while the accent box is up) no longer
  kicks you out of typing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 08:20:40 +02:00
Kaj SchittecatandClaude Opus 4.8 02cff3389d touch: tap-to-edit on touch focus + map-render watchdog yield
- Keyboard nav: tapping a text field by touch now enters edit mode immediately
  (focus came from the pointer indev) instead of requiring Enter. Reaching a
  field with the letter-nav keys still starts in navigate mode (press Enter).
- Map: yield to IDLE after each tile in renderMapTiles() so a slow multi-tile
  render on loopTask can't starve the task watchdog and panic — fixes a beta_14
  TWDT reboot seen during map use (CPU1=loopTask). The download worker already
  does the same vTaskDelay(1) on its side.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 08:08:16 +02:00
Kaj Schittecat 4e3c212a89 chore: refresh Mesh America catalog for beta_14 2026-06-24 00:43:49 +02:00
Kaj SchittecatandClaude Opus 4.8 a804d709cf release: beta_14 notes — hotfix (kbd-nav-off typing regression)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 00:41:55 +02:00
Kaj SchittecatandClaude Opus 4.8 7111789fa7 touch: fix typing dead when keyboard-nav is OFF (beta_13 regression)
The keyboard-nav rework gated the physical-keyboard typing target on
s_nav_ta_editing (edit mode). That flag is only ever set while keyboard
navigation is ON (navFocusCb, driven by the nav focus group). With keyboard
navigation turned OFF the nav group isn't maintained, so the flag stayed false
and `ta` was always null — keys never reached the focused field and typing was
completely dead on the T-Deck (and Tanmatsu).

Fix: when keyboard-nav is OFF there is no navigation to protect, so a focused
field is always the typing target (ta = ta_focused). Edit-mode gating still
applies only when keyboard-nav is ON. Affects handleHwKey (T-Deck) + navPump
(Tanmatsu); the V4 (no keyboard nav) was never affected.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 00:39:38 +02:00
Kaj SchittecatandClaude Opus 4.8 fbc015cf5c site: Community Videos section + YouTube/Docs/Map quick-link buttons
- New "Community videos" section under the install/flasher area: a JS-array-driven grid with a click-to-play facade (youtube-nocookie, lazy iframe). First entry is KDHD Stuff's review; add more by appending to the VIDEOS array.
- Float the quick-links into stacked left/right rails: left = Telegram + a YouTube button that jumps to the videos section; right = bug report + a Documentation button (placeholder — toasts "coming soon") + a Map button to t413.com's MapTileDl downloader.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-24 00:34:44 +02:00
Kaj Schittecat 3ae9582431 chore: refresh Mesh America catalog for beta_13 2026-06-24 00:02:48 +02:00
Kaj SchittecatandClaude Opus 4.8 36e5ed4c36 release: beta_13 notes — community drop (#39 #40 #22 #38 #29 + keyboard/typing/12h/V4 fixes)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 23:59:56 +02:00
Kaj SchittecatandClaude Opus 4.8 f817fca41c touch: disable crash-report UI on Heltec V4 (no way to retrieve/send the dump)
The boot crash-report prompt + the About-page export button are only useful
where the saved coredump file can actually be retrieved and sent to the devs:
the T-Deck (SD card) and Tanmatsu (FFat, via the launcher file manager). On the
Heltec V4 there's no SD and no user-reachable internal storage, so the prompt
was a dead end. Gate crashDumpCheck() to those boards only — on the V4 the dump
is never detected, so the whole crash-report UI stays off (everything downstream
gates on s_crash_dump_size). The panic coredump still sits in its flash
partition for a USB/esptool pull if ever needed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 23:49:41 +02:00
SamandClaude Sonnet 4.6 5fcf6ddac3 fix: block commands while transport-off confirmation is pending
Any command arriving while s_meshcomod_pending_action is non-NONE and
the timeout hasn't expired previously fell through the confirmation
block and was processed normally, letting a second 'tcp off' / 'ble off'
silently overwrite the pending action and lose the original confirmation.

Add a final else clause that blocks the new command and reminds the user
to 'ok' or 'cancel' the in-flight request.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-23 23:25:02 +02:00
SamandClaude Sonnet 4.6 5e6aaa8852 fix: restart TCP immediately on enable, guard OTA slot, fix toggleTcp alert race, re-enable warnings
- enableTcp() now calls startTcpServer(false) directly instead of relying
  on the main loop — fixes TCP not restarting when wifi_started is false
  (BLE-only mode, radio toggled off, or cold re-enable from USB).

- Add touchHasOtaUpdateSlot() guard to the OTA button creation block so
  the update affordances stay hidden under Launcher (single app slot),
  where ota url would fail silently.

- Fix toggleTcpCb alert race: snapshot isTcpEnabled() before the toggle
  so the alert text reflects the transition, not a post-action re-read
  that could mismatch during OTA suspension.

- Replace global -w with -Wno-deprecated-declarations -Wno-unused-parameter
  in both touch environments to keep third-party lib noise down while
  surfacing real regressions in OTA, network, and companion paths.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-23 23:25:02 +02:00
Kaj Schittecat cd2dc8b3f8 Merge PR #38: touch — optional trackball edge-scroll (tun0) 2026-06-23 23:22:34 +02:00
Kaj Schittecat f4fb7171e5 Merge PR #22: touch — beer emoji, status-bar unread tap, new-contact toast toggle, Czech accents (Vybo)
# Conflicts:
#	src/helpers/esp32/TouchPrefsStore.cpp
2026-06-23 23:22:23 +02:00
Kaj Schittecat 8322b5361d Merge PR #40: ui-touch — room-server posts show author, not room name (Yazutsu, closes #32) 2026-06-23 23:19:14 +02:00
Kaj Schittecat 266f5c8adc Merge PR #39: touch — Direct (0-hop) contact + map filter (tun0) 2026-06-23 23:19:01 +02:00
Kaj SchittecatandClaude Opus 4.8 069aeb8908 touch: keyboard-nav typing fixes, dedicated symbol picker, 12h everywhere
Post-beta_12 touch-UI fixes (T-Deck / Tanmatsu keyboard nav + composer):

Keyboard navigation
- Chat composer auto-edits on open (cursor shows, type immediately); every
  OTHER field stays in navigate mode so the letter-nav keys keep working —
  press select/Enter to edit it. Enter (or Esc/X on Tanmatsu) on an empty
  composer drops back to navigate mode.
- Menu-bar tab-hotkey letters no longer fire while a text field is the focused
  element (fixes a stray tab-jump while typing); directional nav still moves.
- New "Show menu-bar letters" setting (off by default) for the tab hotkeys.

Accent box
- The tap-to-pick accent box no longer steals the keyboard-nav focus group
  (NAV_SKIP_FLAG) — it's a passive hint, so typing continues and a keybind no
  longer navigates. Ready to wire arrow-key selection later.

Composer
- Dedicated "Special characters" picker (% $ @ # & ... currency/math/accents),
  separate from the emoji picker.
- Long-press a sent message -> Resend.

Misc
- 12-hour clock honoured everywhere (top bar, chat bubbles, lock screen), not
  just the chat overview.
- GPS UART RX buffer enlarged only when GPS is enabled (restores V4 RAM).
- Derive time-of-day from received mesh message timestamps when Wi-Fi/GPS off.
- Self-record the task-watchdog context on a TWDT reset for the crash report.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 23:18:34 +02:00
Yazutsu 61a914240f ui-touch: show post author instead of room name for room-server messages
Room posts arrive as TXT_TYPE_SIGNED_PLAIN with the author in the 4-byte sender_prefix and a bare body. The display path passed the room contact's name, so every post showed the room name. Resolve the author from the prefix and pass it as the per-message sender via a new newRoomMsgFromPubWithMeta hook; the room stays the thread. Tested on T-Deck Plus.

Signed-off-by: Yazutsu <andrzej@gruziel.pl>
2026-06-23 22:45:39 +02:00
Ruben Laban 29204dd33f touch: add Direct (0-hop) filter to contact list and map
Contact list gains a "Direct (0-hop)" option in the Filter sheet (value 5)
that shows only nodes heard without any repeater hops (out_path_len == 0).
Header chip shows "Dir" when active. Selecting a filter now auto-dismisses
the sheet (matching sort behaviour).

Map options panel gets a "Direct (0-hop) only" toggle that hides both
contact markers and link lines for any multi-hop or path-unknown node.
2026-06-23 14:36:57 +02:00
Ruben Laban bb86a32b04 touch: add optional edge-scroll for trackball cursor mode
When enabled in Settings → Keyboard, pushing the cursor past any screen
edge routes the overflow into the nearest scrollable widget rather than
absorbing it.  Works on regular tab content (lv_scr_act children) and on
lv_layer_top() overlays such as the app drawer.

Implementation:
- tbFindScrollableAt() hit-tests at the vertical centre of the content
  area (avoids status/tab-bar chrome and per-tab headers), searches
  lv_layer_top() before lv_scr_act(), then walks ancestors to the first
  scrollable with room in the overflow direction.
- scroll_by direction is negated relative to raw overflow (scroll_by(+dy)
  moves children down = reveals earlier content = scroll up).
- Scroll amount is capped to lv_obj_get_scroll_top/bottom/left/right so
  we never push past the widget's content bounds.
- Preference persisted as NVS key "tb_edgesc" (default off).
- Map, Snake, and emoji-picker modes are unaffected (they return before
  cursor mode runs).
2026-06-23 14:07:57 +02:00
Dan Vybiral 4a0d7f5247 touch: beer emoji, status-bar unread tap, new-contact toast toggle, Czech accents
- emoji: bake the beer mug U+1F37A and clinking beers U+1F37B as colour glyphs
  into emoji_data.c (now 252) and add the beer mug to the composer picker; the
  clinking pair was already listed but only rendered monochrome, now colour.
- status bar: tapping the unread badge (envelope + count) on the left now jumps
  to the Chats inbox. The CLICKABLE flag is toggled per-tick so only the badge
  state intercepts the tap — every other left-zone state (Back chevron, profile
  name, OSM credit, blank) keeps the bar's control-center / Back tap.
- contacts: add a "Notify on new contact" toggle to the Auto-add page
  (TouchCfg v8, default ON). When off it suppresses the auto-discovery toast
  chip in UITask::notify(); the diag-log line and tab badge are unaffected.
- keyboard: add the Czech accents c-caron, e-caron, t-caron, z-caron, r-caron
  and u-ring (plus uppercase) to the long-press / tap accent popup. Glyphs are
  already baked in the extras fallback fonts, so no font regeneration needed.

Builds verified on both LilyGo_TDeck_companion_radio_touch and
heltec_v4_tft_companion_radio_usb_tcp_touch.

Signed-off-by: Dan Vybiral <dan.vybiral@greencode.cz>
2026-06-22 20:37:24 +02:00
242 changed files with 62418 additions and 29350 deletions

No files matched your search

+2
View File
@@ -28,6 +28,8 @@ scripts/build/wifi_secrets.h
# Local working notes + agent config (contain ops/infra details — never publish)
CLAUDE.md
.claude/
/dev-docs/
/crash-dumps/
# Custom timestamped build outputs
/builds/
+51
View File
@@ -0,0 +1,51 @@
# Supported devices
Current hardware support, install paths and maturity. "Stable" means the board
ships on the stable release channel; "Beta" means it is new and lives on the
test channel until the next stable promote. Install links:
[flasher.wadamesh.com](https://flasher.wadamesh.com) (browser, Chrome/Edge over
USB) and the [GitHub releases](https://github.com/ALLFATHER-BV/wadamesh/releases).
| Device | MCU / radio | Display and input | Install | Channel | Status |
|---|---|---|---|---|---|
| LilyGo T-Deck / T-Deck Plus | ESP32-S3, SX1262 | 2.8" 320x240 touch, QWERTY, trackball | Web flasher (standalone) or Launcher app image | Stable | Fully supported, reference device |
| Heltec V4 + TFT | ESP32-S3, SX1262 | 2.4" 240x320 touch (CHSC6x) | Web flasher | Stable | Fully supported; Expansion Kit sensors, V4.3 high-gain RX toggle |
| Tanmatsu | ESP32-P4 + ESP32-C6, SX1262 | 4" 800x480, 69-key keyboard (no touch) | Tanmatsu app store on the device (runs under the badge.team launcher, not web-flashable) | Store tracks the test channel | Fully supported; LoRa + Wi-Fi + Bluetooth simultaneously, standalone and companion in one |
| Elecrow ThinkNode M9 | ESP32-S3, LR1110 | 2.4" 240x320 (no touch), I2C QWERTY + d-pad | Web flasher | Beta (new in beta_38) | Hardware-complete community port by ded (#138): GPS, microSD, buzzer, lock screen, d-pad navigation |
| RAK WisMesh Tap V2 (RAK3312) | ESP32-S3, SX1262 | Touch display (LovyanGFX, 30+ fps) | Web flasher | Beta (new in beta_38) | Early community port by Ethac.chen (#136); core mesh, chat and map working |
## Feature notes per board
- **T-Deck**: the everything device: touch, physical keyboard, trackball cursor
or d-pad navigation, microSD (deep 5000-message chat history, map tile packs,
data storage), GPS on the Plus, notification sounds through the I2S speaker.
- **Heltec V4 + TFT**: touch UI with the on-screen keyboard; the optional
Expansion Kit adds environment sensors (home-screen chart) and a piezo
buzzer. V4.3 boards get the switchable high-gain receive LNA toggle.
- **Tanmatsu**: keyboard-driven UI (no touchscreen) with the coloured function
keys mapped to tabs, ALT accent picker, UI scaling (Normal/Large/Huge),
microSD for all persistent data. Ships through the Tanmatsu launcher store,
updates arrive as store updates.
- **ThinkNode M9**: keyboard plus d-pad navigation (no touch), same feature set
as the other boards where the hardware allows. New in beta_38; expect rough
edges and report them.
- **RAK WisMesh Tap V2**: newest port, touch-driven. The browser-flash path is
fresh; if the flasher cannot open the serial port, put the board in download
mode manually and retry, and please report it.
## Requested boards
Open hardware requests, roughly in demand order. Ports are welcome, see
[CONTRIBUTING.md](CONTRIBUTING.md); the M9 and Tap V2 both started as community
PRs.
- LilyGo T-Deck Pro Max: [#62](https://github.com/ALLFATHER-BV/wadamesh/issues/62)
- LilyGo T-pager: [#60](https://github.com/ALLFATHER-BV/wadamesh/issues/60)
- SenseCAP Indicator D1L: [#14](https://github.com/ALLFATHER-BV/wadamesh/issues/14)
## Channels
- **Stable**: the tested default. The flasher installs it unless you pick Beta.
- **Beta**: new features and fixes earlier; on-device opt-in via Settings,
About, "Get test builds (beta)". New boards debut here and move to Stable
with the next promote.
+20 -2
View File
@@ -51,14 +51,32 @@ ed25519 (bundled in lib/ed25519)
AsyncElegantOTA (vendored in arch/esp32/AsyncElegantOTA)
Copyright (c) Ayush Sharma — MIT License
TFT_eSPI (Heltec V4 display backend)
TFT_eSPI (T-LoRa Pager display backend)
Copyright (c) Bodmer — MIT / FreeBSD License — https://github.com/Bodmer/TFT_eSPI
Adafruit GFX / ST7735_ST7789 (T-Deck display backend)
Adafruit GFX / ST7735_ST7789 (T-Deck / Heltec V4 display backend)
Copyright (c) Adafruit Industries — BSD License
chsc6x (Heltec V4 CHSC6x cap-touch driver)
Quency-D — https://github.com/Quency-D/chsc6x
SensorLib (T-LoRa Pager XL9555/BQ27220/AW9364 drivers)
Copyright (c) Lewis He — MIT License — https://github.com/lewisxhe/SensorLib
ES8311 register sequence and clock-divider coefficients (T-LoRa Pager audio
codec driver, variants/lilygo_tlora_pager/Es8311Codec.cpp; T-Display P4 audio
driver, variants/tdisplay_p4/P4Audio.cpp)
Copyright (c) 2023-2026 Espressif Systems (Shanghai) CO LTD
Apache License 2.0 — https://github.com/espressif/esp-adf-libs and
https://github.com/espressif/esp-bsp (components/es8311)
wadamesh's drivers are original code (not copies of esp_codec_dev's
plugin/HAL architecture) but their ES8311 register addresses, startup/
power sequences, and MCLK clock-divider coefficients are derived from
Espressif's public es8311.c/es8311_reg.h; P4Audio.cpp additionally
re-bases the esp-bsp init flow onto Arduino Wire.
LovyanGFX (RAK WisMesh Tap V2 display backend)
Copyright (c) lovyan03 — FreeBSD License — https://github.com/lovyan03/LovyanGFX
This list is not exhaustive and is expanded as dependencies are vendored or
added.
+8 -2
View File
@@ -17,8 +17,14 @@ MeshCore fork via PlatformIO `lib_deps`.
## Boards
- LilyGo T-Deck / T-Deck Plus — env `LilyGo_TDeck_companion_radio_touch`
- Heltec V4 + TFT + CHSC6x touch — env `heltec_v4_tft_companion_radio_usb_tcp_touch`
See **[DEVICES.md](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
+94
View File
@@ -0,0 +1,94 @@
# WadaMesh release channels — Stable + Test
Goal: ship **test** builds to the community fast, let them shake out, then **promote**
a proven test build to **stable**. What ships to stable is exactly what was tested
(promote the binary, don't rebuild).
## Two concepts, kept separate
- **Branches** = where code lives.
- **Channels** = what a device / the flasher pulls (Stable vs Beta).
## Branches
- **`main`** — active line. All work lands here; every *test* release is cut from `main`. (Unchanged from today.)
- **`stable`** — promoted line. Moves only when a test build is blessed. Starts at the **beta_20** commit.
- Promote = `git branch -f stable <blessed beta commit>` + push, then run the stable-promotion publish.
## Versioning / tags
- **Test builds:** `beta_N` (immutable, incrementing), marked **GitHub pre-release**. Also mirrored to a rolling **`beta-latest`** pre-release (overwritten each time) for the Launcher beta sync.
- **Stable:** the blessed `beta_N`, marked **GitHub Latest**. Keep the `beta_N` id for now; friendly `vX.Y` names are an optional later polish (would need a rebuild-with-tag per promotion).
- First stable = **beta_20**.
## Distribution matrix
| Target | Stable | Test / Beta |
|---|---|---|
| GitHub release | blessed `beta_N`, marked **Latest** | every `beta_N`, **pre-release** + rolling `beta-latest` |
| VPS archive | `releases/TOUCH/<beta_N>/` (only blessed lands here) | `releases/BETA/<beta_N>/` |
| VPS channel feed | `stable/` (version.json + bins) | `beta/` (version.json + bins) |
| Flasher (flasher.wadamesh.com) | default | "Beta / testing" toggle |
| On-device update check | stable feed (legacy firmware reads `releases/TOUCH`) | beta feed (Phase 2 setting) |
| LauncherHub (bmorcelli, T-Deck) | existing entry (follows GitHub Latest) | new "WadaMesh (Beta)" entry (Phase 3) |
| Tanmatsu app-store | promote on stable only | (skipped for tests) |
## The linchpin: keeping field devices on stable
Legacy firmware's update check scans `releases/TOUCH/` for the highest `beta_N`. So:
- **Test builds archive under `releases/BETA/`** — invisible to legacy firmware.
- **Promotion copies the blessed build into `releases/TOUCH/`** — legacy devices then see it and show "update available," landing everyone on stable.
Net effect: existing devices quietly settle on **stable (beta_20)** and stop chasing
every beta; beta testers opt in via the flasher Beta toggle (or, later, the on-device
Beta channel).
## Two workflows
### Cut a TEST release (fast, frequent) — from `main`
1. `beta_N` = next number.
2. Build both touch envs with the tag embedded.
3. GitHub: create `beta_N` release **`--prerelease`** with the 7 assets; also refresh the rolling `beta-latest` pre-release.
4. VPS: rsync to `releases/BETA/<beta_N>/` + refresh the `beta/` feed.
5. Flasher Beta toggle now serves it. Skip LauncherHub / Tanmatsu / site. (~minutes)
### Promote to STABLE (deliberate, when proven)
1. `git branch -f stable <beta_N commit>` + push.
2. GitHub: mark that `beta_N` release **Latest** (clear pre-release).
3. VPS: copy `releases/BETA/<beta_N>/` → `releases/TOUCH/<beta_N>/`; refresh `stable/` + `latest/` (flasher stable) feeds.
4. Full fan-out: LauncherHub follows automatically; push the Tanmatsu store; bump the site "what's new."
## Phases
### Phase 1 — channel split, no firmware change (do now)
- [ ] Create + push `stable` branch at beta_20.
- [ ] VPS: stand up `stable/`, `beta/`, `releases/BETA/`; point `latest/` (flasher stable) at beta_20; freeze `releases/TOUCH/` at beta_20.
- [ ] GitHub: ensure beta_20 is **Latest**; future betas → `--prerelease`.
- [ ] Flasher: Stable (default) / Beta toggle + the beta manifest.
- [ ] `release.sh` / `gen-flasher-meta.py`: add `--channel beta|stable` producing the right feed/assets + the rolling `beta-latest`.
- [ ] Rewrite the `wadamesh-release` skill into the two-workflow form.
### Phase 2 — on-device channel selector (ships in a beta, then promoted)
- [ ] Settings → **Update channel: Stable / Beta**, default Stable (persisted).
- [ ] `verchkFetchLatest` reads the `stable/` or `beta/` feed per the setting.
- [ ] Beta devices get the new-beta banner automatically; stable devices never see betas.
### Phase 3 — LauncherHub beta listing (PR to bmorcelli, when wanted)
- [ ] Rolling `beta-latest` already produced in Phase 1.
- [ ] PR `bmorcelli/M5Stack-json-fw`: add a `wadamesh_beta.py` (mirror `bruce_beta.py`, track `beta-latest`) + a `t-deck.json` (Beta) entry.
- [ ] Result: T-Deck Launcher shows **WadaMesh** + **WadaMesh (Beta)**, both auto-synced.
- Until then: T-Deck Launcher beta testers side-load the beta `.bin` manually (it is a T-Deck-only gap; V4 uses the flasher).
## Where current work lands
- The uncommitted post-beta_20 work (auto-advert GUI, message-flash, docs, RAM pass)
plus the hardened **MQTT-privacy** branch → commit to `main` → cut as **beta_21**,
the first TEST release in this model. Community tests it; promote when proven.
- This is exactly the model that handles PR #71: land the reviewed/hardened pieces on
`main`, ship as a beta, promote later.
## Decisions
- **Locked:** `main` + `stable`; keep `beta_N` ids with a Stable/Beta channel label; Phase 1 now, Phase 2 in beta_21, Phase 3 as a fast-follow.
- **Open (reversible):** whether stable later gets friendly `vX.Y` names (needs a rebuild-with-tag per promotion).
+996
View File
@@ -0,0 +1,996 @@
# T-LoRa Pager port — working tracker
Goal: run the **full** wadamesh UI + functionality on the **LilyGo T-LoRa Pager**
(ESP32-S3, **LR1121** radio variant first), kept as **one codebase** with the
existing boards so a UI change ships everywhere at once. This file is the running
plan/status — update it as we go.
Status: **M7's UI portion DONE — boot logo, full LVGL UI, QWERTY
keyboard nav and rotary encoder all VERIFIED WORKING on real hardware
(2026-07-07)**, after root-causing the intermittent black screen to the ST7796
panel's hardware-reset line floating: it's wired to **XL9555 channel 6**, which
both the LilyGoLib doc's channel table and the canonical arduino-esp32 pins
header omit (full war story: `TLORA_PAGER_M7_HW_DEBUG_LOG.md`, session 2 —
including why session 1's radio/display "SPI race" theory was disproven from
TFT_eSPI source). Hardware-comms gates split out to **Milestone 7b**: radio
vs. a live mesh node is now **DONE** (adverts/DMs confirmed reliable both
directions as of 2026-07-11, after the TX-power fix — risk 10; still watch
upstream LR1121 ACK issue #1376 for anything beyond basic reliability), **SD
storage is DONE** (mount/browse/read/write/delete/insert-remove all
hardware-verified — risk 1h), and USB companion device-profile frame
remains untested — see ⑦b for the current breakdown. **Milestone 8
(on-device UI pass) is now active**: fixing weird UI/keyboard behaviors found
by manual testing on the device, human supplying photos/repro steps.
Notification sound (ES8311 codec + NS4150B amp) landed in **Milestone 8b** —
hardware-verified 2026-07-08 (commit `e682fbc`). **M8 is still active**
(on-device UI pass); besides the nav-coverage/222-px audit that's its actual
stated scope (still not started, see risk 8 — this is the single biggest
remaining item), several concrete bugs surfaced and got fixed this
milestone: the radio-settings blur-autosave lag (risk 12), the encoder not
scrolling open dropdowns (fixed 2026-07-08, commit `4bbfcb5`), the keyboard
backlight never being wired up (risk 9, fixed 2026-07-10), and microSD file
manager + WAV-picker support (risk 1h, fixed 2026-07-10, scoped — DataStore
SD routing/chat-history/tiles/wallpaper/backup remain deferred). An
unread-message LED notification was investigated and explicitly decided
against (risk 13) — this board has no onboard LED at all. Risk 11
(keyboard/encoder-driven scroll not repainting) was **ACCEPTED as
workaround-final 2026-07-13** — the Alt+turn free-scroll gesture is the
permanent, intended fix for this hardware, root cause not being pursued
further absent new evidence (see risk 11). **Milestone 10 (SX1262-variant
env) is DONE and hardware-verified** (2026-07-13, `tlora_pager_sx1262_
companion_radio_touch` — see worklist ⑩): a real SX1262 unit completed
setup and confirmed bidirectional live-mesh messaging (public, a custom `#`
channel, and DM). A cluster of keyboard/encoder input-ergonomics fixes
landed 2026-07-08 through 2026-07-14 — Enter/Backspace chat-bubble parity,
the Shift/Caps rework, the accent-variant and @-mention popups both made
encoder-navigable, WASD map panning + Q/E slider nudging, the Fn+Shift
chord's conditional Caps-Lock-vs-Home-jump behavior, and app-drawer tiles'
focus highlight matching their touch-press accent tint — all hardware-
verified; see the dated paragraphs below and the UI-changes inventory table
for specifics. **M8's own stated scope (the 222-px vertical-layout audit +
full focus-nav-coverage pass) still has not been started** — everything
landed in M8 so far has been reactive bug-fixing from user-reported issues,
not the systematic audit itself (risk 8) — this remains the single biggest
open item in the port.
**M8 session 2026-07-07 findings** (radio + nav, all committed:
`b3c6388`/`df7f9bc`):
- **TX power was silently capped at a conservative 10dBm with no way to raise
it** — unlike the T-Deck (boots straight at 22dBm). Found while
investigating a real-mesh DM test: adverts/DMs sent FROM the pager were
unreliable while inbound reception was fine (the far node's own TX was
unaffected) — classic asymmetric-range signature. Fixed to
`LORA_TX_POWER=22`, confirmed as this chip's real sub-GHz HP-PA ceiling via
RadioLib's `LR1120::checkOutputPower()` (LR1121 inherits it: HP PA
auto-selects above 14dBm, valid range -9..22 below 1GHz) and trail-mate's
own `TRAIL_MATE_LORA_TX_POWER_MAX_DBM=22` for this exact board. Existing
saved prefs on an already-flashed device do NOT pick up a new compiled
default — only a fresh/factory-reset device does; raise it manually in
Settings → Radio & Mesh to test on a unit that predates this fix.
- **Risk 1g (RX-boosted-gain never applied for LR1121) fixed** — see risk
entry below.
- **Encoder direction was inverted** — confirmed on hardware, not a
guess: turning the way a user expects to move forward/down moved
focus/scroll backward/up. Fixed in `PagerEncoder.cpp`'s
`pagerEncoderReadDelta()` (negated once at the source, so every consumer
inherits the fix) rather than in UI code.
- **Found a real, still-partially-open rendering bug**: keyboard/encoder-
driven `lv_obj_scroll_to_view(f, LV_ANIM_OFF)` (in `navFocusCb`) does NOT
reliably repaint the newly-scrolled region on this board — confirmed via
hardware logging that focus and DEFOCUSED save side-effects (blur-to-save
toasts) correctly reach fields far down a settings page, but the glass
keeps showing the OLD scroll position throughout. Small new overlays
(the toast itself) still paint fine, since those are fresh objects, not a
repaint of already-rendered scrolled content. Touch-drag scrolling on the
other boards never surfaced this because LVGL's drag/animation handler
re-invalidates every animation tick, papering over the same gap that a
single one-shot `LV_ANIM_OFF` scroll doesn't cover. **Root cause NOT fixed
yet** — an attempted fix (force `lv_obj_invalidate()` on the scrolled
ancestor after `scroll_to_view`) made things WORSE (very slow, ~5 presses
per visible update) without actually fixing the viewport scroll, and was
reverted. **Workaround shipped instead**: holding the pager's orange Alt
key + turning the encoder now free-scrolls the page via
`navScrollFocused()`'s ANIMATED `lv_obj_scroll_by` (which DOES repaint
correctly, consistent with the animation-tick theory above), then snaps
focus to whatever's nearest the top of the now-visible viewport
(`navRefocusFirstVisible()`). This also fixed a pre-existing bug where
Alt+turn always jumped main tabs even from inside a settings sheet/chat —
now scoped to the main-tab level only (`navOnMainPage()`). Plain
NEXT/PREV-driven `scroll_to_view` on a tall settings page is still broken;
picking that apart further (why does one-shot `LV_ANIM_OFF` fail to
invalidate on THIS board specifically?) is unscheduled follow-up — likely
worth checking whether `lv_timer_handler()`'s own per-pass duration
(`[STALL] ui:lvgl`, separately observed at 400ms–1.6s on this board during
this investigation) is a contributing/related factor, not just the
scroll-invalidate call itself.
**M8 session 2026-07-08, chat-bubble Enter/Backspace ergonomics (commits
`facbe49`/`bf5c682`):** a focused non-composer widget (e.g. a Settings row)
didn't activate on Enter in one specific case — fixed. Also added, matching
Tanmatsu's identical no-touch gestures: Enter on a focused chat message
bubble opens the same Ack/Mention/Copy/Info/Block action menu a touch
long-press opens elsewhere (`navEnterBubble()`, shared code — bubbles are
the focusable leaves inside a chat's `msgs` container, identified by
parent); Backspace jumps straight to the newest message when the "scroll to
bottom" button is showing (this board has no touch to tap that floating
button). The rotary encoder's own short click did NOT get the bubble-menu
behavior in this pass — that gap wasn't closed until 2026-07-14 (below).
**M8 session 2026-07-13, Shift/Caps rework + accent-popup keyboard nav
(commits `79df528`/`43f040e`), hardware-verified:** (1) The Shift/Caps key
(`kCapsPos`, renamed `kShiftPos`) changed from trail-mate's original
bare-press-toggle-Caps-Lock to conventional semantics — held alone it's a
momentary Shift (uppercases while held, releases back to normal); held Alt
(Fn) then a Shift press chords into a Caps Lock toggle. New `s_shift_held`
static, same pattern as `s_backspace_held`/`s_space_held`. One documented
edge case: Alt+Shift+O or Alt+Shift+L all three held phantom-ghosts a stray
'q'/'a' (Alt and Shift share row2; col8 is 'o'/'l' on rows 0/1 — a
diode-less-matrix 3-key rectangle, no software fix possible, harmless since
it's not the intended hold-Alt-tap-Shift gesture). (2) The accent-variant
popup (issue #22 — shows accented options when typing a vowel or
`n c s y t z l r`) was completely unreachable on this no-touch board — its
cells are `NAV_SKIP_FLAG`, excluded from the nav group by design (touch
boards pick them by tap). Added a pager-only parallel nav path: Fn(Alt)+
Space arms it, the rotary encoder walks the highlighted variant, the
encoder's own click confirms (synthesizes `LV_EVENT_CLICKED` on the
highlighted cell via `accentNavConfirm()`, reusing `accentBoxCellCb` rather
than duplicating its logic), Backspace cancels without deleting the base
letter. See worklist ⑤ for the full writeup, including the 2026-07-14
follow-up that changed what the Alt+Shift chord actually *does*.
**Same session, Milestone 10 (SX1262-variant env) — DONE, hardware-verified
(commit `4b0c2e9`):** a real SX1262 unit completed setup and confirmed
bidirectional live-mesh messaging (public, a custom `#` channel, and DM).
Full writeup, including the `target.h` missing-include bug found and fixed,
is in worklist ⑩ and `TLORA_PAGER_PORT_MILESTONES.md`'s Milestone 10.
**Same session, WASD map panning + Q/E slider nudge (commit `9881bb0`),
hardware-verified:** the Map tab's pan/drag needed a no-touch equivalent —
W/A/S/D now pan north/west/south/east while the Map tab is active, reusing
`mapNudge()` (previously Tanmatsu's Ctrl+Arrow-only helper, widened to
`defined(HAS_TANMATSU) || defined(TLORA_PAGER)`). This freed up D from the
existing slider-nudge binding (added 2026-07-08 for Control Center
brightness / Settings sliders / the map zoom bar, since none of those can
be dragged without touch or a trackball), which moved from D/F to Q/E so
the two gestures never collide (e.g. the map zoom slider focused while
WASD-panning).
**M8 session 2026-07-14, four more hardware-verified fixes:**
1. **Encoder short click now opens the message action menu too** (commit
`c4c28d4`) — the 2026-07-08 fix above only wired this into keyboard
Enter; the encoder's short click still sent a plain `LV_KEY_ENTER` a
bubble doesn't react to. `updatePagerEncoder()`'s short-click branch now
calls `navEnterBubble()` first, mirroring `handleHwKey()` exactly.
2. **Fn+Shift's effect now depends on UI state** (commit `b16206b`) — the
chord used to toggle Caps Lock unconditionally, even with no text field
focused to see the change reflected in, which was reported as surprising
and purposeless outside of typing. `PagerKeyboard.cpp` no longer decides
the effect (it has no UI visibility) — it only reports the chord via
`pagerKeyboardConsumeAltShiftChord()`; `UITask.cpp`'s new
`updatePagerAltShiftChord()` toggles Caps Lock ONLY while a text field is
actually being edited (same "ta" derivation `handleHwKey()`'s TLORA_PAGER
branch already uses to tell a bound-but-unfocused field apart from one
actually being edited), and jumps straight to Home (`navGoToMainTab`)
everywhere else.
3. **@-mention contact picker made encoder-navigable** (commit `57802eb`) —
the same unreachable-without-touch problem the accent box had, fixed the
same way (`mentionNavRestyle()`/`mentionNavConfirm()` mirror
`accentNavRestyle()`/`accentNavConfirm()` almost exactly), with one
deliberate difference: it grabs the encoder the INSTANT the list appears
rather than requiring an explicit Fn+Space arm, since — unlike the accent
box, which pops up after nearly every letter typed and must not steal
focus from ongoing typing — the mention list only shows once the user
has deliberately typed "@partial" looking for someone to pick, so there's
no ongoing typing to protect.
4. **App-drawer tiles' keyboard/encoder focus highlight normalized to their
own accent tint** (commit `6073b6f`) — tiles previously fell through to
`navFocusCb`'s generic white reverse-video fill when focused via
keyboard/encoder nav (a solid white block over a small rounded icon chip
read as a glitch), instead of the accent-tinted `LV_STATE_PRESSED` look
they already show on a touch press. New `NAV_ACCENTFOCUS_FLAG`
(`LV_OBJ_FLAG_USER_3`) lets `navFocusCb` special-case flagged objects
(mirrors the existing switch/slider special-case) to use that same
accent tint for both states, on every board — not just the pager.
All three envs build green — Milestone ⑥ (UITask wiring)
landed; the pager is a first-class, non-touch UI target. Board JSON verified
(`boards/lilygo-t-lora-pager.json`). Milestones ①–⑥ (variant skeleton, LR1121
radio glue, ST7796 display + AW9364 backlight, platformio.ini env, TCA8418
keyboard + rotary encoder drivers, UITask wiring) landed.
`[env:tlora_pager_lr1121_companion_radio_touch]` compiles clean: **RAM 23.8%
(78088/327680 B), Flash 66.4% (2696465/4063232 B)** — both still comfortably
lower than the two shipping boards (Heltec V4/T-Deck: RAM 25.3%, Flash 73.5%,
unchanged — confirmed byte-identical to pre-M6, zero regression). M1–M5's
build-blocking fixes (variant/pins split, radio-wrapper include paths, the
minimal display-typedef addition) are recorded in Decisions ②/⑧ and worklist
③/⑤ below; M6's own findings follow.
**M6 findings** — the UI-inventory table + worklist ⑥ below have full detail;
the highlights:
- **Two capability flags I initially set were premature and had to be walked
back**: `CAP_SD`/`CAP_FILESYSTEM` looked right from the hardware table (the
pager does have a microSD slot), but the actual mount code
(`fmSdTryMount()`, `#include <SD.h>`) is still hardcoded to
`HAS_TDECK_GT911` specifically — `device_caps.h`'s own `CAP_SD` flag was
never actually wired to it. Turning it on for the pager just produced
`SD`/`CARD_NONE`/`fmSdTryMount` "not declared" errors, not real SD support.
Set back to 0 — a real mount needs its own pager-specific wiring (CS 21, a
non-T-Deck shared-SPI helper), unscheduled follow-up, not this milestone.
- **`navMaybeRebuild()` — the function that actually populates the LVGL focus
group every screen — was unreachable for the pager** in my first pass: it's
only called under `#if defined(HAS_TANMATSU) ... #elif CAP_TRACKBALL ...`,
neither of which the pager matches. Without a fix here the KEYPAD indev
would have an eternally-empty focus group — nothing focusable, navigation
completely dead, despite the indev registration itself being correct. Added
a `#elif defined(TLORA_PAGER)` arm.
- **A self-inflicted `#elif` scoping mistake**: `handleHwKey()` (and several
helpers it calls) live inside a large, multiply "paused and reopened"
`#if defined(HAS_TDECK_KEYBOARD)` region. Widening the wrong reopen point
first orphaned ~50 lines of genuinely T-Deck-specific code (keyboard
backlight-mode timer, notify-flash, spacebar-lock countdown) into what was
meant to be the pager's own simpler branch. Fixed by tracing each reopen's
actual `#endif` (nesting depth, not just grep hits) before touching it, and
keeping the T-Deck-only pieces under their own unwidened, more specific gate.
- **`isDismissKey()`'s T-Deck logic doesn't transfer**: it treats the letters
p/q/a as "dismiss popup" because the T-Deck's sparse keyboard has no
dedicated Esc key. The pager's full QWERTY types those letters constantly —
reusing that mapping would eat normal typing. Returns `false` for the pager
instead; the rotary encoder's long-press already covers ESC.
**Execution playbook: `TLORA_PAGER_PORT_MILESTONES.md`** — the worklist below,
broken into agent-executable milestones with gates and per-file instructions.
---
## Why this port is cheaper than it looks
The scary part — "the device has no touchscreen" — is **already solved in this
codebase**. UITask carries a complete non-touch navigation layer built for the
Tanmatsu (keypad-only) and the T-Deck trackball D-pad mode:
- **Focus-group nav**: `s_nav_group` (`lv_group_t`), amber focus ring + scroll-into-view
(`navFocusCb`), per-screen group rebuild (`navMaybeRebuild`), 2-D directional focus
(`navMoveDir`), tab-bar handling (`navOnTabBar`/`navSwitchTab`) — `UITask.cpp` ~2138–3128.
- **A KEYPAD indev + key FIFO**: `navFifoPush/Pop` feeds `LV_KEY_UP/DOWN/LEFT/RIGHT/
NEXT/PREV/ENTER/ESC` into `tanmatsuKeypadRead` (`UITask.cpp` ~3000). The Tanmatsu
registers ONLY this indev (no pointer) — `UITask.cpp` ~35706–35717. **That branch is
the pager's template.**
- **Physical-keyboard routing**: `handleHwKey()` (`UITask.cpp` ~27990) routes keys
into the focused textarea (edit mode) or into nav (navigate mode, `s_nav_ta_editing`
flag), with the on-screen LVGL keyboard suppressed — exactly how the T-Deck works
today. The pager's QWERTY plugs into this unchanged.
- **Rotary encoder**: no `LV_INDEV_TYPE_ENCODER` needed — encoder ticks map to
`navFifoPush(LV_KEY_NEXT/PREV)` (focus walk), press → `ENTER`, long-press → `ESC`.
Reuses everything above.
So the genuinely NEW work is: the **480×222 ST7796 display driver + layout pass**,
the **TCA8418 keyboard driver** (raw matrix → chars, unlike the T-Deck's C3 which
resolves ASCII for us), the **rotary driver**, the **LR1121 radio glue**, and a
**board class** whose battery/power goes through I²C chips (fuel gauge + IO
expander) instead of an ADC pin.
## Hardware / platform facts
Confirmed from the LilyGo product page, CNX-Software (2025-08-12), Meshtastic docs,
and cross-checked against three working/authoritative sources: upstream
`meshcore-dev/MeshCore`'s pager target (see caveat under Decision ②), the official
[LilyGoLib hardware page](https://github.com/Xinyuan-LilyGO/LilyGoLib/blob/master/docs/hardware/lilygo-t-lora-pager.md),
and `~/dev/trail-mate` (local project with a running LR1121 pager build — pin map
below is from its `variants/lilygo_tlora_pager/pins_arduino.h`, which is
byte-identical on every pin/channel to the canonical
[`espressif/arduino-esp32` pins_arduino.h](https://github.com/espressif/arduino-esp32/blob/master/variants/lilygo_tlora_pager/pins_arduino.h)
for this board). **Caveat**: the LilyGoLib page's own "Pins Map" table has
internal inconsistencies for the XL9555 channel assignments (e.g. it lists
keyboard-enable at ch10 and SD-detect/enable at ch12/ch14, which contradicts
its own "PowerManage Channel" table on the same page *and* the canonical
arduino-esp32 header). We treat the arduino-esp32 header + trail-mate (which
agree with each other and with the "PowerManage Channel" table) as ground
truth — that's what our own `TLoraPagerBoard.cpp` already uses.
| | |
|---|---|
| SoC | ESP32-**S3** @ 240 MHz, 16 MB flash (QIO), **8 MB QSPI PSRAM** (`memory_type: qio_qspi`) |
| Display | 2.33" IPS **ST7796U**, 480×222 (221 PPI, 262K colors, 450 cd/m²), **480×222 landscape**, SPI, **no touch**. CS 38, DC 37, backlight 42 (AW9364 16-level stepped driver). **Hardware reset is XL9555 ch6, NOT unwired** — `TFT_RST=-1` only because it isn't an ESP GPIO; `TLoraPagerBoard::begin()` owns the reset pulse (LOW→50ms→HIGH, vendor sequence). Leaving ch6 floating = intermittent black screen, clean boot log (M7 root cause) |
| Shared SPI bus | **SCK 35, MOSI 34, MISO 33** — display + LoRa + SD + ST25R3916 NFC all on it (like the T-Deck's 40/41/38 — solved pattern, CS discipline + SPI transactions) |
| Radio | **LR1121** (sub-GHz 830–945 MHz + 2.4 GHz; we use sub-GHz only). CS 36, RST 47, BUSY 48, IRQ/DIO1 14. **Also sold with SX1262** (the LilyGoLib page documents the SX1262 retail SKU as primary) — same board/pins, different defines (cheap 2nd env later) |
| Keyboard | Physical QWERTY via **TCA8418** I²C matrix controller (addr `0x34`), INT 6, backlight 46. Raw matrix events — keymap/shift/sym handled on our side |
| Encoder | Rotary A 40, B 41, **press 7** |
| Buttons | **BOOT = GPIO0** (usable as user button + sleep wake — matches both existing boards' `PIN_USER_BTN=0`). Physical power key is PMU QON, not a GPIO — can only wake the device (1s hold), never programmable |
| Power | **BQ25896** charger PMU (addr `0x6B`) + **BQ27220 fuel gauge** (addr `0x55`, battery % / mV over I²C — NOT an ADC divider). Battery: 3.7 V / 1500 mAh (5.55 Wh). DeepSleep ≈530 µA, LightSleep ≈2.26 mA, Power-off ≈26 µA |
| IO expander | **XL9555** (addr `0x20`): DRV_EN ch0, AMP_EN ch1, KB_RST ch2, LORA_EN ch3, GPS_EN ch4, NFC_EN ch5, **DISP_RST ch6 — the ST7796 panel's hardware reset** (missing from BOTH the LilyGoLib doc's channel table and arduino-esp32 master's pins header; confirmed from LilyGoLib's `LilyGo_LoRa_Pager.cpp` begin(), which pulses it LOW→50ms→HIGH before display init — leaving it floating was M7's intermittent-black-screen root cause, see `TLORA_PAGER_M7_HW_DEBUG_LOG.md` session 2), GPS_RST ch7, KB_EN ch8, GPIO_EN ch9, SD_DET ch10, SD_PULLEN ch11, SD_EN ch12 |
| GPS | u-blox **MIA-M10Q**: TX 12, RX 4, PPS 13 |
| I²C bus | SDA 3, SCL 2 — shared by TCA8418 (`0x34`), XL9555 (`0x20`), BQ25896 (`0x6B`), BQ27220 (`0x55`), PCF85063 RTC (`0x51`), BHI260AP IMU (`0x28`), DRV2605 haptics (`0x5A`), ES8311 codec (`0x18`) |
| SD | microSD on the shared SPI bus, CS 21, card-detect via expander (ch10), max 32 GB, **FAT32 only** |
| Audio | ES8311 codec (I²C `0x18`; I2S MCLK 10, SCK/BCK 11, WS 18, SDOUT 45, SDIN 17 — confirmed against arduino-esp32's canonical `variants/lilygo_tlora_pager/pins_arduino.h`, matching LilyGoLib's own `codec.setPins(I2S_MCLK, I2S_SCK, I2S_WS, I2S_SDOUT, I2S_SDIN)` call in `LilyGo_LoRa_Pager.cpp`) driving an **NS4150B** 3 W Class-D amp (enabled via expander AMP_EN ch1, toggled at runtime around playback — not the boot-time permanently-on drive; see Decision below) |
| Misc | PCF85063A RTC (INT 1), BHI260AP IMU (INT 8), ST25R3916 NFC (unused — CS 39, INT 5, powered via expander NFC_EN ch5), USB VID/PID `0x303A:0x82D4` |
## Board JSON — VERIFIED ✅ (landed as `boards/lilygo-t-lora-pager.json`)
The JSON (Meshtastic-lineage; byte-identical to trail-mate's copy) is **correct for
the LR1121 unit but radio-agnostic**: it describes only the S3 module (flash/PSRAM/
USB id/CDC-on-boot), which every radio variant of the pager shares. The radio is
selected by our build flags (`RADIO_CLASS`/`WRAPPER_CLASS` + pins), same as the
existing boards. Notes:
- `partitions: app3M_fat9M_16MB.csv` is just the default — we override with our own
OTA+tiles+spiffs csv via `board_build.partitions` (see worklist ①).
- `variant: lilygo_tlora_pager` + `variants_dir: variants` → needs
`variants/lilygo_tlora_pager/pins_arduino.h` (write our own; don't copy
trail-mate's — it brands `USB_PRODUCT "TRAIL MATE"`).
- `-DARDUINO_USB_MODE=1` (HW-CDC) is in the JSON's extra_flags. The T-Deck ships
MODE=1 fine; the Heltec V4 regressed on it (large companion frames dropped —
see the note in `platformio.ini`). **Verify the device-profile frame over USB
companion early** (worklist ⑦); if it drops bytes, switch to TinyUSB CDC like
the V4.
## Decisions (architecture)
1. **Normal PlatformIO env, T-Deck model** — NOT the Tanmatsu IDF-subproject route.
The pager is a plain ESP32-S3 Arduino target; it slots into `platformio.ini`
next to the existing two envs and into `release.sh`'s env list later.
2. **LR1121 wrappers vendored in the variant dir — zero core-fork churn for
bring-up.** The core fork (`core-v1.16.5`) only has `CustomLR1110*`.
**Re-verified 2026-07-06: upstream `meshcore-dev/MeshCore`'s `main` branch does
NOT currently have `CustomLR1121*` or a `variants/lilygo_tlora_pager/` dir**
(checked `src/helpers/radiolib/` — only `CustomLR1110{,Wrapper}.h` exists there
too; issue [meshcore-dev/MeshCore#861](https://github.com/meshcore-dev/MeshCore/issues/861)
"Support for LR1121" is still open). Earlier research that assumed an
upstream crib source was wrong or looked at a branch/fork that no longer
exists — **re-check upstream at Milestone ② time**, but plan for having to
author `CustomLR1121{,Wrapper}.h` ourselves by adapting the core fork's own
`CustomLR1110{,Wrapper}.h` pair (same RadioLib `LR11x0` family — swap the
base type from `LR1110` to `LR1121`), cross-checked against trail-mate's
`initLoRa()` (which drives RadioLib's stock `LR1121` class directly, no
custom wrapper) for the RF-switch table / `setTCXO` sequence. Since
`CustomLR1121{,Wrapper}.h` only subclass RadioLib's `LR1121` and the core's
`RadioLibWrapper` (both on the include path), they can live in
`variants/lilygo_tlora_pager/` for now and move into the fork at the next
`core-*` tag. Precedent: the Tanmatsu keeps its whole radio bridge in its
variant dir.
**Found at Milestone ④'s first real compile**: `CustomLR1121Wrapper.h`'s
bare quoted `#include "RadioLibWrappers.h"`/`"LR11x0Reset.h"` (copied
verbatim from `CustomLR1110Wrapper.h`'s shape) don't resolve — those work
in the core fork only because the file sits in the *same*
`src/helpers/radiolib/` directory as its targets (quote-include searches
the including file's own directory first); ours lives in the variant dir
instead. Fixed to angle-bracket `<helpers/radiolib/...>` includes, matching
`target.h`'s already-correct pattern for the same headers.
3. **LR1121 init is explicit** (no `std_init`): RF-switch table on **DIO5/DIO6**
(`STBY {L,L} / RX {L,H} / TX {H,L} / TX_HP {H,L}`) + **`setTCXO(3.0f)`** —
confirmed in both trail-mate (`boards/tlora_pager/src/tlora_pager_board.cpp`,
`initLoRa()`) and upstream. Sync word / preamble / CR come from the same
NodePrefs plumbing as the other boards so it interoperates with the mesh.
4. **Display = new `ST7796LCDDisplay` app-side** (in `src/helpers/ui/`), implementing
the core's `DisplayDriver` interface (`begin/width/height/startFrame/endFrame/
setDisplayRotation/writePixelsRGB565`) — that's all the LVGL flush path uses.
TFT_eSPI has `ST7796_DRIVER` (`USER_SETUP_LOADED` + `-D` pin set).
**Correction, landed with Milestone ③**: "the Heltec V4 already builds on
TFT_eSPI, so mirror that wiring" was wrong — `ST7789LCDDisplay` (Heltec
V4's *and* T-Deck's display class, same file) is actually Adafruit_GFX/
Adafruit_ST7789-based; Heltec V4's TFT_eSPI lib_dep/`-D` flags are
vestigial (nothing else in the repo `#include`s `TFT_eSPI.h`). This makes
`ST7796LCDDisplay` the first real TFT_eSPI consumer in this codebase —
every method call was verified directly against the pinned
`bodmer/TFT_eSPI @ ^2.5.43` source, not cribbed from the sibling class.
**Also found and mitigated**: this panel's 222px glass is narrower than
the ST7796 controller's 320px GRAM, requiring a 49px column/row offset
that TFT_eSPI only applies automatically when `-D CGRAM_OFFSET=1` is set —
missing from this decision's original flag list; a `#error` guard in
`ST7796LCDDisplay.cpp` now catches the omission at M4 compile time (see
worklist ③ for the full writeup). Backlight is the AW9364 (stepped pulse
dimming), not a plain GPIO PWM — wrapped in `ST7796LCDDisplay` itself using
`lewisxhe/SensorLib`'s `AW9364LedDriver` directly (a maintained library,
already an M1-established dependency) rather than a hand-rolled driver.
5. **Input = the Tanmatsu registration branch** (KEYPAD indev + `s_nav_group` only,
no pointer indev), gated by a new device cap. Rotary → nav FIFO; TCA8418 →
`handleHwKey()`. New pollable drivers in `src/helpers/input/` following the
existing style (begin/poll/read API, no LVGL inside the driver).
6. **Battery/power via libraries, not hand-rolled** (CONTRIBUTING rule): lewisxhe
**SensorLib** covers BQ27220 (`GaugeBQ27220`), XL9555 (`ExtensionIOXL9555`),
PCF85063, DRV2605; **XPowersLib** covers the BQ25896. `TLoraPagerBoard :
public ESP32Board` overrides `getBattMilliVolts()` (gauge query),
`getManufacturerName()`, power-rail bring-up in `begin()` (expander), and sleep.
7. **One codebase**: all pager-specific UI behavior rides existing/new `CAP_*`
flags in `src/ui-touch/device_caps.h` — no forked screens.
8. **`variants/lilygo_tlora_pager/` app glue and the board's Arduino "variant"
pin map had to split into two directories** — found only by actually
compiling in Milestone ④, not anticipated by any earlier decision.
PlatformIO's arduino-esp32 build script (`platformio-build.py`) always
compiles every source file under `board_build.variants_dir/<board.variant>/`
as a separate `FrameworkArduinoVariant` library, in a build context with
none of our app's `lib_deps` include paths. T-Deck/Heltec V4 never hit this
because their board JSONs point `"variant"` at a variant the *framework*
already bundles (`esp32s3`, `heltec_v4`) — completely separate from our own
`variants/lilygo_tdeck/`/`variants/heltec_v4/` app-glue directories, zero
collision. The pager has no framework-bundled variant, so its board JSON
was forced to set `"variants_dir": "variants"`, pointing PlatformIO's
variant resolution at the exact same directory we'd used for
`TLoraPagerBoard.*`/`target.*`/`CustomLR1121*` — so the framework tried to
compile those too, and failed on missing `Wire.h`/`RadioLib.h`. Fixed by
moving `pins_arduino.h` alone into a new `variants/lilygo_tlora_pager_pins/`
folder and pointing the board JSON's `"variant"` there instead; our own
`TLoraPagerBoard.*`/`target.*`/`CustomLR1121*` stay in
`variants/lilygo_tlora_pager/`, reached only via our own
`build_src_filter`, exactly once. Confirmed safe against
`get_partition_table_csv()`'s similar `variants_dir`-based fallback logic
(moot here since `board_build.partitions` is set to a full explicit path,
which that function returns verbatim once its variant-relative lookup
attempts fail).
9. **Notification sound: hand-rolled ES8311 driver, not a vendored codec HAL.**
`espressif/esp_codec_dev`'s ES8311 device (Apache-2.0, ~4.5k lines across
its generic multi-codec plugin architecture) is more than this
single-chip, playback-only board needs, and defaults to the *new*
`driver/i2s_std.h` API where this codebase's existing T-Deck sound code
uses the legacy `driver/i2s.h` (which already supports MCLK via
`i2s_pin_config_t.mck_io_num`, so no new API family was needed). Wrote
`variants/lilygo_tlora_pager/Es8311Codec.{h,cpp}` instead — ~200 lines,
DAC-only, register sequence and MCLK clock-divider coefficients derived
from Espressif's public `es8311.c`/`es8311_reg.h` (see `NOTICE`), fixed to
a 256x-sample-rate MCLK ratio covering the standard 8k-48k rates
`wavParse()` already accepts. Matches this port's own precedent (T-Deck's
sound code is similarly hand-rolled, ~200 lines) and the milestone rule
against introducing new abstraction layers.
10. **AMP_EN toggled around playback, not left permanently on.** The
boot-time `TLoraPagerBoard::begin()` drive of every expander rail
(including AMP_EN) exists for bus-integrity reasons specific to the boot
window (unpowered chips clamping the shared I²C bus) — unrelated to
audio and left untouched.
`TLoraPagerBoard::setAmpEnabled()` is the runtime toggle the sound code
brackets each chime/WAV with (amp off at idle), matching both the
vendor's own `codec.setPaPinCallback()` pattern and this port's existing
on-demand-resource philosophy (T-Deck installs/uninstalls its I2S driver
per chime for the same reason). Cost is one extra I²C write per
chime start/end on a bus already used for every other rail toggle.
## Worklist (ordered, each step ends build-green for ALL envs)
- [x] ⓪ Research + board JSON verification; land `boards/lilygo-t-lora-pager.json` + this tracker.
- [x] ① **Variant skeleton**: `variants/lilygo_tlora_pager/{pins_arduino.h, TLoraPagerBoard.h/.cpp}` + `partitions_tlora_pager_touch.csv` (T-Deck's OTA/tiles/spiffs/coredump layout, byte-identical offsets). Board class (`TLoraPagerBoard : public ESP32Board`): `begin()` re-inits Wire on SDA3/SCL2, probes the XL9555 expander (addr 0x20) and enables LORA_EN/GPS_EN/KB_EN/KB_RST/SD_EN rails, probes the BQ27220 gauge, handles the deep-sleep RX-packet wake reason (mirrors `TDeckBoard.cpp`). `getBattMilliVolts()` reads the gauge (`refresh()` + `getVoltage()`), falling back to 3700 mV if the probe/refresh fails. `getManufacturerName()` → "LilyGo T-LoRa Pager". `enterDeepSleep()` mirrors `TDeckBoard.h`. BQ25896 charger deliberately left as a TODO (gauge alone covers the UI). `target.{h,cpp}` deferred to ② — nothing references the new files yet, so both shipping envs build unchanged (verified green).
- [x] ② **Radio**: `variants/lilygo_tlora_pager/{CustomLR1121.h, CustomLR1121Wrapper.h, target.h, target.cpp}`.
`CustomLR1121{,Wrapper}.h` authored by adapting the core fork's own
`CustomLR1110{,Wrapper}.h` (LR1110/LR1121 share RadioLib's `LR11x0` base —
confirmed by reading RadioLib 7.6.0 source directly: same protected
`freqMHz`/`spreadingFactor` members, same `getIrqStatus()`/`getRssiInst()`
inherited from `LRxxxx`/`LR11x0`), since upstream has nothing to crib (see
Decision ②). `radio_init()` in `target.cpp`: `spi.begin(...)` →
`radio.begin(LORA_FREQ, LORA_BW, LORA_SF, cr, ..._SYNC_WORD_PRIVATE,
LORA_TX_POWER, 8, 3.0f)` → `setRfSwitchTable(DIO5/DIO6)` → `setCRC(1)`.
**Three deliberate deviations from trail-mate, found by reading RadioLib's
actual source rather than copying its call sequence — see Decision ② for
the full reasoning:**
1. No explicit `radio.reset()` before `begin()` — RadioLib's
`LR11x0::modSetup()`→`findChip()` already resets the chip internally
(with retries); trail-mate's explicit reset is redundant, not wrong.
2. No second `radio.setTCXO(3.0f)` call after `begin()` — trail-mate only
needs that because its `initLoRa()` calls the *zero-arg* `begin()`
(default `tcxoVoltage=1.6V`) and fixes it up after. Our `begin()` passes
`3.0f` as the 8th arg directly, which `LR11x0::modSetup()` already
applies internally — a second call would be a no-op.
3. Added `radio.setCRC(1)` after `begin()` (LR11x0's `begin()` defaults to a
2-byte CRC) to match the 1-byte CRC every other MeshCore radio wrapper
uses for wire-protocol interop (`CustomSX1262::std_init()` makes the
identical override) — trail-mate never needed this since its app isn't
interoperating with MeshCore's own framing.
Also **not** calling `rtc_clock.begin(Wire)` in `radio_init()` — see the new
Risk item below (RTC address collision). `RfSwitchMode_t`/`OpMode_t`/DIO5-6
constants verified to exist with the expected shape directly in the pinned
`jgromes/RadioLib @ ^7.6.0` source (not just trusted from trail-mate).
Env defines for M4 to use: `RADIO_CLASS=CustomLR1121`,
`WRAPPER_CLASS=CustomLR1121Wrapper`, `P_LORA_NSS=36 / _RESET=47 / _BUSY=48 /
_DIO_1=14`, SPI 35/34/33, **`PIN_GPS_RX=12` / `PIN_GPS_TX=4`** (see the GPS
risk item below — these are swapped relative to trail-mate's raw
`GPS_RX`/`GPS_TX` macro values, on purpose), `GPS_BAUD_RATE=38400`. Keep the
standard `RADIOLIB_EXCLUDE_*` set (LR11X0 stays IN; can also exclude SX126X
here).
- [x] ③ **Display**: `src/helpers/ui/ST7796LCDDisplay.{h,cpp}` on TFT_eSPI
(`ST7796_DRIVER`, `TFT_WIDTH=222`, `TFT_HEIGHT=480`, MADCTL rotation for
landscape). This is the **first real TFT_eSPI consumer in this codebase** —
`ST7789LCDDisplay` (the sibling this was "modeled on") turned out to be
Adafruit_GFX/Adafruit_ST7789-based for both Heltec V4 and T-Deck; the
Heltec V4 env's TFT_eSPI lib_dep/`-D` flags are vestigial (nothing
`#include`s `TFT_eSPI.h` anywhere else in the repo). Only the
`DisplayDriver`-satisfying shape was mirrored, not any API calls — every
TFT_eSPI method used (`init`, `setRotation`, `setAttribute`/`CP437_SWITCH`,
`textWidth`, `pushColors`, `writecommand`/`TFT_DISPOFF`, `fillScreen`,
`fillRect`/`drawRect`/`drawPixel`, `setAddrWindow`/`startWrite`/`endWrite`)
was verified directly against the pinned `bodmer/TFT_eSPI @ ^2.5.43` source
in `.pio/libdeps/*/TFT_eSPI/TFT_eSPI.h`, not assumed.
**Found and fixed a real correctness bug in the same pass**: this panel's
222px glass is narrower than the ST7796 controller's 320px GRAM (trail-mate
applies explicit 49px column/row offsets — confirmed the source of the
magic number: `320 - 222 = 98`, halved/centered = 49px each side). TFT_eSPI's
own `ST7796_Rotation.h` already has this exact fix (`colstart=49`/
`rowstart=49` depending on rotation, applied automatically inside every
`setAddrWindow()` call) — but only when `CGRAM_OFFSET` is `#define`d.
Unlike `ST7789_Defines.h` (which self-defines it), `ST7796_Defines.h` does
not, and it was **missing from this milestone's own drafted M4 flag list**.
Without it the build compiles clean but every frame renders shifted/cropped
by 49px with no error — added a `#error` guard in the new `.cpp` that fires
the moment M4 compiles this file without the flag, with the fix spelled out
in the message. **M4 must add `-D CGRAM_OFFSET=1`.**
Backlight: AW9364 stepped pulse-dimmer, wrapped directly in
`ST7796LCDDisplay` (no separate `Aw9364Backlight.{h,cpp}` — `ST7789LCDDisplay`
turned out to have no brightness hook to mirror at all; brightness on the
other two boards is a `UITask.cpp`-owned free function doing raw LEDC PWM
on `PIN_TFT_LEDA_CTL`, which the AW9364's pulse protocol can't use).
Consumes `lewisxhe/SensorLib`'s `AW9364LedDriver` directly (header-only,
already vendored via the M1-established SensorLib dependency) rather than
hand-rolling the pulse timing the milestone doc originally suggested.
Exposes `setBrightness(uint8_t pct)`/`getBrightness()` (0-100, matching the
Settings UI's existing convention) so Milestone 6 can wire it in with one
line. **M6 needs a new branch ahead of `UITask.cpp`'s existing
`PIN_TFT_LEDA_CTL` PWM branch** — once M4 defines that macro for the pager,
the existing LEDC-PWM code would also compile and fight the AW9364's pulse
protocol (a duty cycle is not a valid input to this chip). `NOTICE` updated:
added a `SensorLib` entry (missing since M1) and corrected the `TFT_eSPI`/
`Adafruit GFX` lines' backend descriptions (both were wrong about which
boards use which library). `DISPLAY_CLASS=ST7796LCDDisplay`. Gate: both
shipping envs build unchanged (neither's `build_src_filter` references
`helpers/ui/*.cpp` yet, so the new TU isn't even parsed by either compiler
today) — full compiler verification of the new code waits for M4.
- [x] ④ **Env**: `[env:tlora_pager_lr1121_companion_radio_touch]` in
`platformio.ini`, cloned from the T-Deck env with board/radio/display/GPS/
input deltas (see Decisions ①-④, ⑥-⑧ for exact values and reasoning). Added
lib_deps: `bodmer/TFT_eSPI @ ^2.5.43`, `adafruit/Adafruit TCA8418 @ ^1.0.2`,
`lewisxhe/SensorLib @ 0.3.3` (exact version trail-mate proves works, not
guessed) — **dropped** `adafruit/Adafruit ST7735 and ST7789 Library` from
the cloned list (T-Deck/Heltec's Adafruit display backend; unused here,
TFT_eSPI replaces it). No `XPowersLib` (M1 left the BQ25896 charger out of
scope). `default_envs` left unchanged (still just the two shipping boards).
Also fixed two structural bugs found only by actually compiling (see
Decision ⑧) and added one forced, minimal `UITask.cpp` `#elif
defined(TLORA_PAGER)` arm (display-class typedef only — see the Status
line). **Compile gate: all three envs build green** — verified.
- [x] ⑤ **Input drivers**: `src/helpers/input/{PagerKeyboard,PagerEncoder}.{h,cpp}`.
Gated `HAS_PAGER_KEYBOARD`/`HAS_PAGER_ENCODER`, already reached by every
env's `+<helpers/input/*.cpp>` filter — no `platformio.ini` change needed
for compilation, only the pin flags (`KB_INT=6`, `KB_BACKLIGHT=46`,
`ROTARY_A=40`, `ROTARY_B=41`, `ROTARY_C=7`, matching the repo's
explicit-`-D`-alongside-`.cpp`-fallback convention).
**`PagerKeyboard`**: T-Deck's own keyboard driver turned out to be the
wrong shape to mirror directly — its C3 co-processor resolves ASCII itself
over I2C, so `TDeckKeyboard.cpp` never sees a raw matrix event. The
TCA8418 (Adafruit_TCA8418 lib, already an M4 dependency) reports raw
row/col events instead, so the keymap + shift/sym/alt state machine lives
in `PagerKeyboard.cpp` itself. Reused trail-mate's `LilyGoKeyboard` keymap
tables verbatim (same physical PCB) — `keymap[4][10]`/`symbol_map[4][10]`,
Alt as a hold-to-symbol-layer modifier (no separate physical Symbol key on
this hardware), Backspace special-cased to `'\b'` — UX choices trail-mate
already field-validated, reused rather than re-derived. **The Shift/Caps
key's behavior changed 2026-07-13** from trail-mate's original
press-to-toggle case lock to conventional keyboard semantics: held alone
it's a momentary Shift (uppercases whatever letters are typed while held,
releases back to normal); held Alt + a Shift press instead chords. `kCapsPos`
renamed `kShiftPos` to match. **Chord effect changed again 2026-07-14**:
`PagerKeyboard.cpp` no longer decides what Alt+Shift *does* (it has no UI
visibility) — it only reports the chord via
`pagerKeyboardConsumeAltShiftChord()`; `UITask.cpp`'s
`updatePagerAltShiftChord()` toggles persistent Caps Lock ONLY while a text
field is actually being edited (same "ta" derivation as `handleHwKey()`'s
TLORA_PAGER branch), and jumps straight Home (`navGoToMainTab`) everywhere
else — toggling Caps Lock with no field to see it change in was reported as
surprising/purposeless outside of typing.
See `PagerKeyboard.cpp`'s matrix-legend comment for the one documented
edge case (Alt+Shift+O or Alt+Shift+L all three held phantom-ghosts a
stray 'q'/'a' — a diode-less-matrix limitation, not a bug, and not the
intended gesture). Ring-buffer/SPSC/threading-contract shape
mirrors `TDeckKeyboard.cpp`'s (single poll context, UI-thread-safe
`readKey()`) even though the underlying hardware access differs completely.
Implemented as straightforward polling (`available()`/`getEvent()` drained
every `pagerKeyboardPoll()` call), not INT-pin-gated, despite the milestone
doc's "prefer INT-driven drain" suggestion — trail-mate's own INT handling
does extra `INT_STAT`/`GPIO_INT_STAT` register bookkeeping whose exact
clear-vs-latch semantics weren't independently verified, and an ISR-gated
poll that's wrong would present as "keyboard stops after first keypress" —
a regression only caught on hardware (M7). Polling is explicitly sanctioned
as a fallback by the milestone doc and carries no such risk; INT-driven
draining is a valid future optimization once verified on real hardware.
**`PagerEncoder`**: the milestone's "ISR edge-counting exactly like
`TDeckTrackball.cpp:27-47`" doesn't transfer literally — the T-Deck
trackball is 4 independent direction-pulse GPIOs (no direction logic
needed, each pin already means one direction), not a true A/B quadrature
pair, so it can't answer "which way did it turn." Implemented a standard
Gray-code quadrature transition table instead (both edges of both A and B
feed one ISR, table lookup yields +1/-1/0 per transition) — same
ISR-does-cheap-arithmetic-only shape and `noInterrupts()`-snapshot read
pattern as `TDeckTrackball.cpp`, just the right decode logic for a genuine
quadrature signal. Divides by `PAGER_ENCODER_STEPS_PER_DETENT` (default 4,
the common EC11-style ratio) to convert raw transitions to detents,
carrying the remainder forward across reads — **this divisor is an
unverified assumption, confirm on hardware in M7**.
**Gate:** all three envs build — verified.
- [x] ⑥ **UITask wiring**: `device_caps.h` got its `TLORA_PAGER` cap block (no
touch, no rotate, no large-screen, GPS 1, OTA 1, lock-screen 1; `CAP_SD`/
`CAP_FILESYSTEM` corrected to 0 — see below) plus widened `CAP_KEYBOARD`/
`CAP_KEYPAD_NAV` derivations to recognize `HAS_PAGER_KEYBOARD`/
`TLORA_PAGER`. `UITask.cpp` changes, all pager-gated: KEYPAD indev
registered by widening the Tanmatsu branch's `#if` to
`defined(HAS_TANMATSU) || defined(TLORA_PAGER)` (~35706) — pager reuses
`tanmatsuKeypadRead`'s plumbing but not `bsp_input_get_queue`, which stays
Tanmatsu-only; forced `s_ui_rotation = LV_DISP_ROT_270` and a new
`hor_res=480/ver_res=222` branch (~35626); a new `updatePagerEncoder()`
(delta → `navPushTap(NEXT/PREV)`, click → ENTER, long-press ≥1000ms →
ESC); main-loop drain wired for both `pagerKeyboardPoll()`/
`pagerKeyboardReadKey()` → `handleHwKey()` and the encoder function above;
`applyBrightness()`/`touchScreenBacklight()` got pager-first branches
calling `display.setBrightness()` instead of falling into the
`PIN_TFT_LEDA_CTL` PWM branch (closes risk 1f — PWM would never have
worked on the AW9364's discrete-pulse interface). Draw buffer already
sized off `hor_res` so needed no separate edit. 222-px vertical audit
deferred to on-device measurement (M8) rather than guessed constants — see
risk 8 below. Final sizes: pager RAM 23.8% (78088/327680 B), Flash 66.4%
(2696465/4063232 B); Heltec V4/T-Deck unchanged at 25.3%/73.5% (byte-
identical to pre-M6, confirming the gate on every edit). Three corrections
vs. the milestone doc's assumptions, all found by compiling rather than
assumed — see risks 1h/1i/1j:
- `CAP_SD`/`CAP_FILESYSTEM` looked right from the hardware (real microSD
slot) but the actual mount code is hardcoded to `HAS_TDECK_GT911`, not
truly `CAP_SD`-generic — set back to 0, real support is unscheduled
follow-up.
- `navMaybeRebuild()` (populates the LVGL focus group every screen) wasn't
reachable on the pager's own cap combination — added a
`#elif defined(TLORA_PAGER)` arm; without it the KEYPAD indev would have
had a permanently empty focus group.
- Several T-Deck-keyboard-gated helpers (`handleHwKey`, `isDismissKey`,
`tabForKey`, `navMenubarKeysSync`) live inside multiply "paused and
reopened" `#if defined(HAS_TDECK_KEYBOARD)` regions; widened each
reopen's gate individually (tracing real nesting depth, not just grep
hits) rather than touching the whole file, and kept genuinely
T-Deck-only sub-logic (the p/q/a dismiss-key mapping, which would eat
normal QWERTY typing on the pager) under its own narrower, unwidened gate.
- [x] ⑦ **Headless bring-up gate, UI portion** (needs hardware) — DONE
(2026-07-06/07 sessions, see `TLORA_PAGER_M7_HW_DEBUG_LOG.md`): flash +
serial recipes established; boot clean; SPIFFS mounts; display + boot logo +
full UI + keyboard nav + encoder verified on the glass (after 6 real bugs —
stale-NVS BLE bonds, screen-wake path, TFT_eSPI S3 SPI-port index, panel
INVON, two-SPI-hosts pin theft, and the floating XL9555-ch6 panel reset).
- [~] ⑦b **Radio/USB/SD bring-up gates** (needs hardware + second mesh node) —
**radio joins the live mesh: DONE**, adverts/DMs confirmed reliable both
directions against a second node after the TX-power fix (risk 10,
retested 2026-07-11) — still watch upstream LR1121 ACK issue
meshcore-dev/MeshCore#1376 for anything beyond basic reliability. USB
companion link passing the large device-profile frame (see HW-CDC note
above): still untested. **SD storage: DONE** — real mount, browse,
read/write/delete, and insert/remove detection all confirmed on hardware
(risk 1h). (DataStore/NVS-level SD use — routing contacts/channels to the
card — is a separate, still-deferred feature, not part of this bring-up
gate.) Remove the temporary `[DISP]` register readback in
`ST7796LCDDisplay::begin()` once the USB piece passes.
- [~] ⑧ **On-device UI pass** — ACTIVE: nav-coverage audit screen by screen (every interactive control reachable via focus group — the Tanmatsu work paved this), chat layout at 222 px, map pan via encoder/keys, fonts legibility at 480-wide, plus fixing any weird UI/keyboard behaviors surfaced by manual testing (human provides photos/repro steps).
- [ ] ⑨ **Release pipeline**: add the env:binname pair to `release.sh` `ENVS`, flasher manifest (`deploy/flasher/manifest-tlora-pager.json`), OTA env name via `FIRMWARE_OTA_ENV`. Separate PR.
- [x] ⑩ (Optional, cheap) `tlora_pager_sx1262_...` env for SX1262-variant owners — **DONE, hardware-verified 2026-07-13** (`tlora_pager_sx1262_companion_radio_touch`, all 4 envs green; see `TLORA_PAGER_PORT_MILESTONES.md`'s Milestone 10 for the full writeup, including the `target.h` missing-include bug found + fixed). Radio gate (M7 step 3) confirmed on real hardware: user sent + received messages on public, a custom `#` channel, and DM.
## UI-changes inventory (what actually changes in `src/ui-touch/`)
| Area | Change | Size | Status |
|---|---|---|---|
| Indev registration (~35706) | Widened the Tanmatsu keypad-only branch's gate to `\|\| defined(TLORA_PAGER)`; no pointer indev registered | small | done |
| Input drain (main loop ~37350) | Pager branch: `pagerKeyboardPoll()`+`pagerKeyboardReadKey()`→`handleHwKey()`; `updatePagerEncoder()`→`navPushTap(NEXT/PREV/ENTER/ESC)` | small | done |
| `handleHwKey()` (~27990) and its multiply-reopened `HAS_TDECK_KEYBOARD` regions | Widened each reopen's gate individually to admit `HAS_PAGER_KEYBOARD`; kept the T-Deck-only p/q/a dismiss mapping under its own narrower gate | small | done |
| Resolution block (~35604–35650) | New branch: forced `LV_DISP_ROT_270`, `hor_res=480/ver_res=222` | small | done |
| Draw buffer (~1399) | Sized off `hor_res`, no separate edit needed | trivial | done (no-op) |
| Brightness (`applyBrightness`~28906, `touchScreenBacklight`~36511) | New pager-first branches calling `display.setBrightness()` instead of the PWM `PIN_TFT_LEDA_CTL` path | small | done |
| `navMaybeRebuild()` reachability | Added `#elif defined(TLORA_PAGER)` arm — was unreachable, would've left focus group permanently empty | small | done (bug fix) |
| Vertical budget | Audit `STATUSBAR_H`, `TABBAR_H`, `CHAT_KB_H`, modal/chat height helpers for 222 px | **the real work** | deferred to M8 on-device (risk 8) |
| Focus-nav coverage | Screen-by-screen pass that every control is in `s_nav_group` | medium, on-device | deferred to M8 |
| device_caps.h | New `CAP_*` block: no touch, hw keyboard, encoder, 480×222, GPS, OTA, lock-screen; SD/filesystem left 0 by design — real SD support added via widened individual call sites instead (see risk 1h) | trivial | done |
| Keyboard backlight (`pagerKeyboardSetBacklight()`) | `updatePagerKbBacklight()` tick + Settings → Keyboard cycle row (off/on/auto) | small | done (risk 9) |
| microSD (file manager + WAV picker) | `fmSdTryMount()`/`fmShowRoots()`/`fmIsAudio()` etc. widened to `\|\| defined(TLORA_PAGER)`; DataStore SD routing, chat-history cap, tile/wallpaper/backup SD use still deferred | medium | done, scoped (risk 1h) |
| Chat bubble Enter/Backspace (`handleHwKey()` ~28808) | Enter on a focused bubble opens the Ack/Mention/Copy/Info/Block menu (`navEnterBubble()`); Backspace jumps to the newest message when the scroll-to-bottom button is showing | small | done |
| Shift/Caps (`PagerKeyboard.cpp`) | Held Shift = momentary uppercase; held Alt+Shift = chord (see below for what it does) | small | done |
| Accent-variant popup keyboard nav | Fn+Space arms it; encoder walks variants; encoder click/Enter confirms; Backspace cancels (`s_accentnav_active`/`accentNavRestyle()`/`accentNavConfirm()`) | medium | done |
| @-mention picker keyboard nav | Auto-arms the instant the list appears (no Fn+Space needed); same encoder walk/confirm/cancel as the accent popup (`s_mentionnav_active`/`mentionNavRestyle()`/`mentionNavConfirm()`) | medium | done |
| Encoder short click on a focused bubble | Mirrors keyboard Enter — opens the same action menu instead of a plain ENTER a bubble doesn't react to | small | done |
| Fn+Shift chord effect | Toggles Caps Lock while editing a text field; jumps to Home (`navGoToMainTab`) everywhere else — `PagerKeyboard.cpp` only reports the chord, `UITask.cpp` decides the effect | small | done |
| Map pan (WASD) + slider nudge (Q/E) | WASD pans the Map tab (`mapNudge()`, shared with Tanmatsu's Ctrl+Arrow); Q/E adjust a focused slider (moved off D/F to avoid colliding with WASD) | small | done |
| App-drawer tile focus highlight | `NAV_ACCENTFOCUS_FLAG` makes `navFocusCb` use the tile's own accent tint instead of the generic white reverse-fill, on every board | small | done |
| SX1262-variant env | `tlora_pager_sx1262_companion_radio_touch` — same board/pins, `CustomSX1262`/`CustomSX1262Wrapper` instead of the LR1121 classes | medium | done (worklist ⑩) |
Everything else (map, chat, contacts, channels, settings, companion protocol,
MQTT, OTA) is resolution-agnostic or already keyed off caps.
## Risks / open questions
1. **LR1121 ACK/TX reliability** — upstream issue meshcore-dev/MeshCore#1376 reports
ACK problems on the pager's LR1121 (confirmed still open). Track it; our wrapper
crib should include any upstream fix. Gate ⑦ tests this explicitly.
1b. **No upstream `CustomLR1121` crib source exists yet** (re-verified
2026-07-06 — see Decision ②'s caveat). Milestone ② needs to author the
wrapper by adapting the core fork's `CustomLR1110{,Wrapper}.h`, not by
copying an upstream file. Re-check upstream first in case it lands before
we get there — would save the work.
1c. **GPS `PIN_GPS_RX`/`PIN_GPS_TX` are named from the GPS module's
perspective in wadamesh's own core (`EnvironmentSensorManager.cpp` calls
`Serial1.setPins(PIN_GPS_TX, PIN_GPS_RX)`, and `HardwareSerial::setPins()`
takes `(rxPin, txPin)` — so `PIN_GPS_TX` supplies the ESP's own **RX** pin,
`PIN_GPS_RX` supplies the ESP's own **TX** pin). trail-mate's/the canonical
arduino-esp32 `GPS_RX=4`/`GPS_TX=12` macros are named the OPPOSITE way — its
own `Serial1.begin(baud, cfg, GPS_RX, GPS_TX)` call uses
`HardwareSerial::begin()`'s `(rxPin, txPin)` order directly, so there
`GPS_RX` IS the ESP's own RX pin. **Net result: wadamesh's `PIN_GPS_RX` must
be set to `12` and `PIN_GPS_TX` to `4`** for M4 — the raw trail-mate values
swapped, not copied verbatim. Verified by reading both projects' actual
`Serial1.setPins()`/`begin()` call sites and the ESP32 core's
`HardwareSerial::setPins()`/`begin()` signatures directly, not by trusting
either project's macro names at face value. Baud confirmed at 38400 (same
MIA-M10Q as T-Deck Plus).
1d. **RTC auto-discovery would misread this board's real RTC.**
`AutoDiscoverRTCClock` (core, shared by all boards) only recognizes DS3231
(`0x68`), RV3028 (`0x52`), and PCF8563 (`0x51`) — its probe is a bare I2C ACK
check. This board's PCF85063A sits at that same `0x51` address but has a
different register layout (RTClib's `RTC_PCF8563` driver would misread its
registers), so calling `rtc_clock.begin(Wire)` would silently produce
garbage timestamps instead of a clean fallback. `target.cpp`'s `radio_init()`
deliberately skips that call — same time behavior as T-Deck/Heltec V4 (ESP32
software clock) rather than a false "RTC found" that's actually wrong. Real
PCF85063A support (SensorLib's `SensorPCF85063`) is unscheduled follow-up
work, not part of any milestone ①–⑩ yet.
1e. **`-D CGRAM_OFFSET=1` must land in Milestone ④'s pager env flags.**
This panel's 222px glass is narrower than the ST7796 controller's 320px
GRAM; TFT_eSPI's `ST7796_Rotation.h` only applies the required 49px
column/row offset when this flag is set (unlike `ST7789_Defines.h`, which
self-defines it). Without it, the pager build compiles clean but every
frame renders shifted/cropped by 49px with no error. `ST7796LCDDisplay.cpp`
has a `#error` guard that will catch the omission the moment M4 compiles
this file — but the actual fix belongs in `platformio.ini`, and it's easy
to miss since the build "succeeds."
1f. **M6 must add a pager branch to `UITask.cpp`'s brightness code ahead of
its existing `PIN_TFT_LEDA_CTL` PWM branch.** Milestone ③ reused that
macro name for the pager's AW9364 enable pin (naming consistency across
boards), but `UITask.cpp:~28868`'s `#if defined(PIN_TFT_LEDA_CTL) &&
(PIN_TFT_LEDA_CTL >= 0)` branch drives that pin with 20kHz LEDC PWM — which
the AW9364 does not accept (it needs discrete edge pulses per step, not a
duty cycle). Once M4 defines `PIN_TFT_LEDA_CTL=42` for the pager, that
existing branch will compile and run for it too unless M6 adds a
`#if defined(TLORA_PAGER)` branch first that calls
`display.setBrightness(pct)` instead (the hook `ST7796LCDDisplay` already
exposes for exactly this).
1g. **RX-boosted-gain silently doesn't apply for the pager — RESOLVED
2026-07-07 (commit `b3c6388`).** Was deferred, not fixed, in Milestone ④
(matches M3's shared-file-edit precedent): with `-D USE_LR1121=1` defined
(not `USE_SX1262`/`USE_SX1268`), three call sites defaulted/applied this
radio setting only for the SX126x macros even though `CustomLR1121Wrapper`
already implements `setRxBoostedGainMode`/`getRxBoostedGainMode`:
`src/MyMesh.cpp` ~2540 (default pref value on first boot), ~2556 and ~3355
(actually calling `radio_driver.setRxBoostedGainMode(...)`), and
`src/DataStore.cpp` ~264 (default pref value). Fixed by adding
`|| defined(USE_LR1121)` to all three conditions — safe/additive, zero
behavior change for T-Deck/Heltec V4, verified by all-three-envs build.
(A fourth, core-lib-only gate still exists in `CommonCLI.cpp`'s
`radio.rxgain` companion CLI command, checking `USE_SX1262`/`USE_SX1268`/
`USE_LR1110` — left alone in this pass since it's core-lib, not app code;
now that the three UI/prefs call sites actually apply the setting, adding
`USE_LR1121` there too would be safe follow-up, just unscheduled.)
2. **TCA8418 keymap** — raw matrix + our own shift/sym/alt state machine; the T-Deck
never needed this (its C3 resolves ASCII). Bounded: trail-mate's layout tables are
a working reference. Landed in M5 as `src/helpers/input/PagerKeyboard.cpp`,
polling-based (not INT-pin-gated — see worklist ⑤ for why).
2a. **Encoder detent scaling — RESOLVED on hardware (2026-07-07).** The
assumed 4-transitions-per-detent (`PAGER_ENCODER_STEPS_PER_DETENT`)
matches this part: user drove the menus by encoder and reported it feels
right ("encoder is looking good"), no fractional/multiple stepping.
**Direction was also wrong, found and fixed later the same day**: unlike
scaling, the CW/CCW sign was never actually validated against physical
rotation — `kQuadTable`'s convention didn't match this part's wiring, so
turning the way a user expects to move forward/down moved focus and
page-scroll backward/up instead. Fixed by negating once in
`PagerEncoder.cpp`'s `pagerEncoderReadDelta()` (the driver, not UI code)
so every consumer inherits the corrected sense from one place.
1h. **`CAP_SD`/`CAP_FILESYSTEM` are 0 for the pager despite real microSD
hardware — a latent gap in `device_caps.h`'s own abstraction, not a pager
bug.** **File manager browsing + WAV notification-sound picker RESOLVED
2026-07-10** (commits `8c7fb6a`/`1514e76`), scoped deliberately: `CAP_SD`
turned out to gate ~37 call sites (file manager, WAV picker, DataStore
contacts/channels routing, tile-cache SD fallback, wallpaper scanning,
settings backup, screenshots), so flipping the macro itself would have
silently turned on ~30 unvetted, T-Deck-only-tested features at once.
Instead `CAP_SD`/`CAP_FILESYSTEM` stay 0 by design, and only the ~7
specific call sites needed for browsing + WAV picking were widened with
`|| defined(TLORA_PAGER)` — see those commits for the full categorized
site list. Added `pagerSdCardPresent()` (XL9555 `PAGER_EXPAND_SD_DET`,
confirmed-inverted polarity) and a pager `sdSharedSPI()` (reuses
`TFT_eSPI::getSPIinstance()`, the same bus the radio already shares).
Format support is explicitly out of scope (no `f_mkfs`/`sd_diskio.h` pulled
in) — the pager's SD row is tap-to-open only. Hardware-verified: mount,
browse, read/write/delete, insert/remove detection, and picking a WAV from
SD as a notification sound all confirmed on real hardware. **Still not
done** (unscheduled follow-up, deliberately deferred): DataStore
contacts/channels routing to SD (`setSecondaryFS`, what Tanmatsu/T-Deck
do to dodge SPIFFS GC stalls), the `MAX_UI_MESSAGES_SD` chat-history cap
bump, map-tile SD fallback/offline tile packs, lock-screen wallpaper SD
scanning, and settings/telemetry backup export-import to SD.
1i. **`navMaybeRebuild()` was unreachable for the pager in the first M6
pass.** It's only called under `#if defined(HAS_TANMATSU) ... #elif
CAP_TRACKBALL ...`, neither of which the pager's cap combination matches
(`CAP_TRACKBALL=0`, not `HAS_TANMATSU`). Left alone, the KEYPAD indev
would register successfully but its focus group would stay permanently
empty — total, silent navigation dead-end, easy to miss since the build
still succeeds. Fixed with a `#elif defined(TLORA_PAGER)` arm alongside
the existing branches.
1j. **`isDismissKey()`'s T-Deck p/q/a mapping doesn't transfer to the
pager's full QWERTY** — that mapping exists only because the T-Deck's
sparse keyboard lacks a dedicated Esc key; reusing it verbatim for the
pager would make it impossible to type those three letters normally.
Returns `false` for the pager instead — its Esc equivalent is the rotary
encoder's long-press, handled separately in `updatePagerEncoder()`.
3. **222-px chat screen** — tightest layout wadamesh has shipped (current min is
240). Mitigations: no on-screen keyboard (physical QWERTY), slimmer status/tab
bars, landscape chat already exists (320×240 path).
4. **HW-CDC companion frames** (`ARDUINO_USB_MODE=1`) — known-regressed on the V4,
fine on the T-Deck. Test the big device-profile frame first thing on hardware.
5. **Encoder-only ergonomics** on long lists (contacts @ 2000 max) — NEXT/PREV focus
walk may need page-jump keys from the QWERTY (cheap: map to `navMoveDir`).
6. **Shared SPI contention** (display flush vs radio IRQ vs SD) — same topology the
T-Deck ships, so expected fine via SPI transactions + CS discipline; keep an eye
on SD-write + RX overlap during history flush. **Partially de-risked in M7:**
TFT_eSPI force-defines `SUPPORT_TRANSACTIONS` on ESP32 (its raw-register fast
path still takes the SPI HAL mutex), RadioLib does no SPI from ISRs, and mesh +
UI loops share one task — so there is NO radio/display race (disproven theory,
don't re-chase; see the debug log). CS discipline is now enforced at boot:
`TLoraPagerBoard::begin()` parks LORA_NSS/LORA_RST/SD_CS/NFC_CS OUTPUT-HIGH
before any bus traffic (LilyGoLib's `initShareSPIPins()` equivalent).
7. **NVS-preserving flash chain** applies here too — 4-component flash, never the
merged image (wipes saved Wi-Fi creds).
8. **222-px vertical layout not yet audited against real constants** —
`STATUSBAR_H`/`TABBAR_H`/`CHAT_KB_H` and the modal/chat height helpers were
deliberately left untouched in M6 rather than guessing slimmer values
desk-side; the 480×222 branch compiles and boots (verified by the wordmark
centering math already being generic), but whether every screen actually
fits without clipping/overlap at 222 px tall can only be judged on real
hardware. Do this first in M8, before the broader nav-coverage pass.
9. **Keyboard backlight not wired to any timer/UI — RESOLVED 2026-07-10
(commit `c9033a3`).** `pagerKeyboardSetBacklight()` (M5) worked standalone
but nothing called it. Fixed with a new `updatePagerKbBacklight()` per-tick
apply step (simple on/off at full LEDC duty — no brightness curve, unlike
the T-Deck's dimmable slider) plus a "Keyboard backlight" cycle row
(off/on/auto) in Settings → Keyboard. Also fixed auto mode never actually
responding to input in the same commit: neither `handleHwKey()` nor
`updatePagerEncoder()` called `noteKbActivity()` (the keyboard-backlight
idle timer), only the separate `noteUserInput()` (screen idle timer) — both
now stamp it. Hardware-verified.
10. **TX power default — RESOLVED 2026-07-07 (commit `b3c6388`).** Was
conservatively set to `LORA_TX_POWER=10` with no way to raise it (unlike
the T-Deck, which boots at its chip's real ceiling), following the same
"conservative default, tune on hardware later" note as risk 1g. Found via
a real DM test against a second mesh node: adverts/DMs sent FROM the
pager were unreliable while inbound reception was fine — the far node's
own TX power was unaffected, an asymmetric-range signature pointing
straight at the pager's own TX being too weak (10dBm is ~16x less power
than 22dBm). Fixed to `LORA_TX_POWER=22`, matching the T-Deck's pattern.
22dBm confirmed as a real, safe ceiling for this chip below 1GHz — not a
guess carried over from the sibling boards — via RadioLib's pinned
`LR1120::checkOutputPower()` source (LR1121 inherits it: the HP PA
auto-selects above 14dBm, valid range -9..22) and cross-checked against
trail-mate's own working `TRAIL_MATE_LORA_TX_POWER_MAX_DBM=22` for this
exact board. **Caveat**: a device already flashed before this fix keeps
its saved `tx_power_dbm=10` preference — the new compiled default only
applies to a fresh/factory-reset device; raise it manually in
Settings → Radio & Mesh on units that predate this commit.
**Retested against a second mesh node 2026-07-11: confirmed reliable**
(adverts/DMs both directions) — the fix holds, not just a theoretical
RadioLib-ceiling argument.
11. **Keyboard/encoder-driven scroll-into-view doesn't repaint on this
board — ACCEPTED as workaround-final 2026-07-13, root cause not
pursued further.** User's call: the Alt+turn workaround (shipped
2026-07-07, commit `df7f9bc`) is the practical fix for this hardware —
a genuine root-cause attempt already made things measurably worse and
was reverted (see below), so further root-causing is not planned unless
new evidence surfaces. `navFocusCb`'s `lv_obj_scroll_to_view(f, LV_ANIM_OFF)` (the
call every board's keyboard/trackball nav relies on to bring a newly-
focused off-screen field into view) updates LVGL's internal scroll
model correctly on the pager — confirmed via hardware serial logging
that focus reaches fields far down a tall settings page (their
blur-to-save toasts fire in order) and `lv_obj_get_scroll_y()` genuinely
changes — but the glass never repaints to show the new scroll position.
A small new overlay (the toast itself) still paints fine, since that's a
fresh object, not a repaint of already-rendered scrolled content. This
never surfaced on the T-Deck/Heltec V4 because touch-drag scrolling
there never exercises this code path at all (gesture scrolling
re-invalidates every animation tick, which happens to paper over the
same underlying gap a single one-shot `LV_ANIM_OFF` call doesn't cover)
— so it's a latent bug in shared nav code, not something pager-specific
in origin, just the first board with no touch fallback to mask it.
**Attempted fix that made it WORSE, reverted**: forcing an extra
`lv_obj_invalidate()` on the scrolled ancestor right after
`scroll_to_view` — this made individual focus highlights eventually
repaint, but very slowly (~5 encoder presses per visible update), and
still never actually scrolled the viewport. Do not re-attempt this exact
fix without new evidence. **Workaround shipped instead** (not a fix):
holding the pager's orange Alt key + turning the encoder now
free-scrolls the whole page via `navScrollFocused()`'s **animated**
`lv_obj_scroll_by` (`LV_ANIM_ON`), which empirically DOES repaint
correctly — consistent with the animation-tick theory above — then
snaps focus to whatever's nearest the top of the now-visible viewport
(`navRefocusFirstVisible()`, new). Plain NEXT/PREV navigation into an
off-screen field on a tall settings page (Radio & Mesh, Profile, etc.)
is still broken without using the Alt+turn workaround, and that's
accepted — the Alt+turn gesture is the intended way to reach an
off-screen field on a tall settings page going forward, not a stopgap.
Root-causing the one-shot-invalidate failure (or checking whether the
same gap exists on the touch-less Tanmatsu) is NOT planned work unless
something forces it back open.
12. **Radio & Mesh settings: blur auto-save re-ran a full flash write + live
radio SPI reconfigure on every field defocus — RESOLVED, pager-only fix
(2026-07-08).** User-reported "navigating feels laggy" on this screen
specifically, confirmed on hardware via a `uiCp("ui:nav")` diagnostic
checkpoint (added, measured zero contribution, then removed — the nav
focus-group rebuild was NOT the cause, ruling out risk 11's "maybe it's a
slow render pipeline" theory for THIS symptom). Root cause:
`saveRadioParamsCb` (`UITask.cpp`) is wired to `LV_EVENT_DEFOCUSED` on
every textarea in `buildRadioSettings()` (freq/bw/sf/cr/tx/airtime/region)
and unconditionally called `the_mesh.savePrefs()` +
`the_mesh.applyRadioFromPrefs()` on blur, even when nothing changed. On
touch boards a field only blurs on a deliberate tap-out after an edit —
rare. On the pager there's no touch fallback, so plain keyboard/encoder
"next field" navigation blurs a field on every step: arrowing through the
6-field row re-triggered a real flash write + LR1121 reinit up to six
times with zero edits made. Measured on hardware via `[STALL] ui:lvgl`
(the callback runs synchronously inside LVGL's event dispatch, so its
blocking I/O gets attributed to the `ui:lvgl` checkpoint even though it
isn't a rendering cost): 6 escalating stalls per navigation pass, up to
8.7s each. **Fix**: skip `setRadioParams()`/region persistence on a
silent (DEFOCUSED) blur when the parsed field values already match
`NodePrefs`, gated `#if defined(TLORA_PAGER)` so touch boards keep their
original always-save-on-blur behavior unchanged. Post-fix hardware
capture: one `[STALL] ui:lvgl 702ms` (one-time settings-modal build cost)
instead of the 6-stall escalation, user-confirmed "much better now".
13. **Unread-message LED notification (screen-off glanceable indicator) —
INVESTIGATED, DEFERRED, not implemented (2026-07-10).** User asked whether
this board could get a Tanmatsu-style "glance at the device anytime and
see there's an unread message" indicator while the screen is off. Confirmed
from multiple sources — this repo's `pins_arduino.h` ("no onboard status
LED"), the full XL9555 channel map and I²C device list in the hardware
facts above, the trail-mate reference port (its `board_facts.h` doesn't
even carry an `led_present` field), and freshly-fetched vendor sources
(LilyGoLib's `docs/hardware/lilygo-t-lora-pager.md` hardware doc and its
actual `LilyGo_LoRa_Pager.cpp`/`.h` firmware — the same file that already
caught the DISP_RST/ch6 bug, so trusted as ground truth here too) — **this
board has no onboard LED of any kind.** Tanmatsu has one: a discrete
RGB "envelope" LED on its CH32 coprocessor (`UITask.cpp:2435`,
`msgLedRefresh()`/`msgLedFlash()`) that breathes green while unread and
flashes white on arrival, independent of screen power. The pager's only
real substitute would be pulsing `KB_BACKLIGHT` (GPIO46, wired up this
session via `updatePagerKbBacklight()`), but that's the backlight for the
ENTIRE physical keyboard, not a single low-current indicator LED — a
continuous Tanmatsu-style "breathe while unread" pattern on it would be a
real, likely-not-small standby power cost for however long a message sits
unread (hours), unlike Tanmatsu's tiny dedicated LED. The bounded
alternative (a single brief flash on arrival, mirroring the T-Deck's
existing opt-in "Flash on new message", `UITask.cpp:10446`) has negligible
power cost but was explicitly rejected by the user as not solving the
actual want: a flash you have to be looking at the instant it happens
isn't a "come back later and glance at it" indicator, just a gimmick.
**Decision: do not implement either variant.** Revisit only if this board
ever gets a hardware revision with a real low-power indicator LED, or if a
software-only always-partially-on approach becomes acceptable (not
currently the case).
## References
- Upstream MeshCore (MIT): `meshcore-dev/MeshCore` — does **NOT** currently have
`variants/lilygo_tlora_pager/` or `CustomLR1121*` (re-verified 2026-07-06, see
Decision ②); only `CustomLR1110{,Wrapper}.h` exists in `src/helpers/radiolib/`,
same as our own core fork. Flasher precedent (unrelated to firmware source):
`flasher.meshcore.io/lilygo-t-lora-pager/`
- Local working port (pin map + LR1121 init + keymap + AW9364/BQ27220/XL9555 usage):
`~/dev/trail-mate/boards/tlora_pager/` (esp. `src/tlora_pager_board.cpp initLoRa()`,
`include/boards/tlora_pager/tlora_pager_board.h`) and
`~/dev/trail-mate/variants/lilygo_tlora_pager/pins_arduino.h`
- Canonical pin map (ground truth, matches trail-mate exactly): [`espressif/arduino-esp32`
`variants/lilygo_tlora_pager/pins_arduino.h`](https://github.com/espressif/arduino-esp32/blob/master/variants/lilygo_tlora_pager/pins_arduino.h)
- Official hardware doc (chip list, I²C addresses, power-rail table, electrical
specs): [LilyGoLib `docs/hardware/lilygo-t-lora-pager.md`](https://github.com/Xinyuan-LilyGO/LilyGoLib/blob/master/docs/hardware/lilygo-t-lora-pager.md) —
see the caveat under "Hardware / platform facts" above about its Pins Map
table's internal inconsistencies.
- Hardware docs: LilyGo product page (T-LoRa Pager), CNX-Software 2025-08-12 writeup,
Meshtastic device page (`meshtastic.org/docs/hardware/devices/lilygo/tpager/`)
- In-repo templates: `variants/lilygo_tdeck/` (S3 + SPI radio + shared bus),
Tanmatsu keypad-nav path in `src/ui-touch/UITask.cpp`, `TANMATSU_PORT.md` (tracker
precedent)
- TFT_eSPI's ST7796 driver support (ground truth for the CGRAM_OFFSET/
colstart/rowstart mechanism, Decision ④): `.pio/libdeps/*/TFT_eSPI/TFT_Drivers/{ST7796_Rotation.h,ST7796_Defines.h}`,
cross-checked against `ST7789_Defines.h` and `setAddrWindow()` in
`TFT_eSPI.cpp` — pulled via the pinned `bodmer/TFT_eSPI @ ^2.5.43` lib_dep.
- AW9364 backlight driver actually consumed (not hand-rolled): `lewisxhe/SensorLib`'s
`AW9364LedDriver.hpp` (MIT, header-only) — reference copy at
`~/dev/trail-mate/.pio/libdeps/*/SensorLib/src/AW9364LedDriver.hpp`.
+174
View File
@@ -0,0 +1,174 @@
# T-LoRa Pager: Keyboard & Rotary Encoder Guide
The LilyGo T-LoRa Pager has **no touchscreen and no trackball** — every
screen, every setting, and every chat is driven entirely by the physical
QWERTY keyboard and the rotary encoder knob. If you're coming from the
T-Deck or Heltec V4 (touch-first), this is the one board where learning a
handful of gestures up front pays off immediately. This guide covers both
radio variants (LR1121 and SX1262) — the UI and input handling are identical
on both.
## The two inputs
- **Keyboard** — a physical QWERTY matrix with a Space bar, Backspace, Enter,
a Shift key, and an orange **Fn/Alt** key (bottom-left). No dedicated Esc,
arrow keys, or number row — those are covered by combos below.
- **Rotary encoder** — turn to move the on-screen focus highlight; click
(press the knob) to select. It's your only pointing device, so almost
every screen is navigable with turn + click alone.
Everything below only fires while you're **not** actively typing into a text
field — if a field is focused and you're typing into it, letters type
normally and these combos step out of the way.
## Rotary encoder
| Gesture | Action | Keyboard equivalent |
|---|---|---|
| Turn | Move focus to the next/previous item on screen | **Fn (Alt) tapped alone** moves forward one step (NEXT only — no keyboard way to go backward) |
| Short click | Select / confirm the focused item | **Enter** |
| Hold ~1 s, then release | **Back**: closes a popup → closes an open chat → goes Home → Esc (whichever applies first) | **Backspace held ~1 s** |
| **Fn (Alt) + turn**, on a main tab | Jump directly between the 5 main tabs (Chats / Contacts / Home / Map / Settings) | none — encoder only |
| **Fn (Alt) + turn**, inside a settings page or chat | Scroll the page up/down | none — encoder only |
| Turn, with a dropdown open | Scroll through the dropdown's options | none — encoder only |
| Turn, with the accent picker open | Cycle through the accent variants (see below) | none — encoder only (Fn+Space to enter is shared) |
| Turn, with the @-mention list open | Cycle through matching contacts (see below) | none — encoder only |
The knob doubles as your only way to reach the bottom tab bar — since
there's no touch to tap an icon, **Fn+turn** while on any main tab is the
fastest way to switch sections.
## Keyboard layout
Base layer (no modifier):
```
q w e r t y u i o p
a s d f g h j k l [Enter]
z x c v b n m
[Space]
```
Hold **Fn (Alt)** for numbers/symbols instead:
```
1 2 3 4 5 6 7 8 9 0
* / + - = : ' " @
_ $ ; ? ! , .
[Space]
```
### Shift and Caps Lock
- **Hold Shift + a letter**: that letter (or letters, for as long as you
hold Shift) types uppercase — released, typing goes back to lowercase.
Real momentary Shift, just like a normal keyboard.
- **Hold Fn (Alt), then press Shift**: while you're editing a text field,
toggles **Caps Lock** on/off — stays uppercase until you repeat the chord.
Anywhere else (not editing a field), the chord does nothing.
- Shift alone, tapped with nothing else, does nothing (as expected).
- **Hold Fn (Alt), then press Backspace**: jumps straight to the **Home**
screen — works everywhere, including while you're actively editing a field
(unlike Alt+Shift above, this one isn't context-dependent). Doesn't delete
a character or trigger the plain-Backspace gestures below.
### Special keys
| Key | While editing a text field | Otherwise |
|---|---|---|
| **Enter** | Send / submit / newline | Select the focused item — or, if a chat message bubble is focused, opens its action menu (Ack / Mention / Copy / Info / Block) |
| **Backspace** (tap) | Delete a character | Jump straight to the newest message if you've scrolled up in an open chat |
| **Backspace** (hold ~1 s) | — | Same as the encoder's long-press: **Back** |
| **Backspace** (hold ~1 s) *while the screen is locked* | — | Unlock the screen |
| **Space** (tap) | Types a space | — |
| **Space** (double-tap, within 250 ms) | Switches between English and your configured secondary keyboard layout | — |
| **Space** (hold ~1 s) | — | Locks the screen (shows a "Locking…" progress bar; tapping any key cancels) |
| **Fn (Alt)** tapped alone (press+release, nothing else) | — | Moves focus to the next field/item — a keyboard-only substitute for a turn of the encoder |
The **BOOT** button (top of the device) instantly wakes the screen from
idle-dim. It does *not* unlock a screen you've manually locked with the
Space-hold gesture above — for that, hold Backspace.
## Accented characters
Typing a letter that has accent variants (all vowels, plus `n c s y t z l r`,
both cases) pops up a small row of alternatives above the field. To pick one
without touch:
1. **Fn (Alt) + Space** — jumps focus into the popup.
2. **Turn the encoder** — cycles through the variants.
3. **Enter** — confirms your choice and replaces the letter you just typed.
4. **Backspace** — dismisses the popup and keeps the plain letter.
## @-mentions
Typing `@` followed by a few letters of a contact's name pops up a matching
list in a channel/group chat. Unlike the accent picker above, this one grabs
the encoder **immediately** — no Fn+Space needed, since it only appears once
you've deliberately started typing a mention:
1. **Turn the encoder** — cycles through the matching contacts.
2. **Enter / encoder click** — confirms the highlighted one, replacing
`@partial` with `@FullName ` in your message.
3. **Backspace** — dismisses the list without touching what you typed.
## Sliders
Any focused slider (Control Center brightness, a Settings slider, the Map
zoom bar) can't be dragged without touch — instead:
- **Q** — decrease
- **E** — increase
Each press moves it proportionally (about 20 presses end-to-end) and
persists the new value immediately, the same as releasing a drag.
## Map screen panning
While the **Map** tab is active:
- **W** — pan north
- **A** — pan west
- **S** — pan south
- **D** — pan east
Each press shifts the view a quarter-screen and reloads tiles/markers as
needed.
## Keyboard backlight
**Settings → Keyboard → Keyboard backlight** cycles through three modes
(tap to advance):
- **Off** — always dark
- **On** — always lit
- **Auto** (default) — lights up on any keypress, turns off ~3 seconds after
the last one
Unlike the T-Deck, this is a plain on/off strip under the keys, not a
dimmable brightness curve.
## Quick reference
| Input | Action |
|---|---|
| Turn encoder (or Fn tap = NEXT only) | Move focus |
| Click encoder (or Enter) | Select / confirm |
| Hold encoder ~1s (or hold Backspace ~1s) | Back |
| Fn + turn (main tab) | Switch tabs |
| Fn + turn (page/chat) | Scroll |
| Fn tap alone | Next field |
| Hold Shift + letter | Momentary uppercase |
| Fn + Shift (editing a field) | Toggle Caps Lock |
| Fn + Shift (not editing a field) | Nothing |
| Fn + Backspace (anywhere) | Jump to Home |
| Fn + Space | Enter accent picker |
| @ + letters (composer) | Auto-focuses the mention list — no Fn+Space needed |
| Enter | Select / send / message action menu |
| Backspace (tap) | Delete / jump to latest message |
| Backspace (hold 1s) | Back, or unlock if locked |
| Space (tap) | Space |
| Space (double-tap) | Switch keyboard language |
| Space (hold 1s) | Lock screen |
| Q / E (slider focused) | Decrease / increase |
| W / A / S / D (Map tab) | Pan map north/west/south/east |
+43
View File
@@ -0,0 +1,43 @@
{
"build": {
"arduino": {
"ldscript": "esp32s3_out.ld",
"partitions": "default_16MB.csv",
"memory_type": "qio_opi"
},
"core": "esp32",
"extra_flags": [
"-DBOARD_HAS_PSRAM",
"-DARDUINO_USB_CDC_ON_BOOT=1",
"-DARDUINO_USB_MODE=0",
"-DARDUINO_RUNNING_CORE=1",
"-DARDUINO_EVENT_RUNNING_CORE=1"
],
"f_cpu": "240000000L",
"f_flash": "80000000L",
"flash_mode": "qio",
"psram_type": "opi",
"hwids": [["0x303A", "0x1001"]],
"mcu": "esp32s3",
"variant": "heltec_v4"
},
"connectivity": ["wifi", "bluetooth", "lora"],
"debug": {
"default_tool": "esp-builtin",
"onboard_tools": ["esp-builtin"],
"openocd_target": "esp32s3.cfg"
},
"frameworks": ["arduino", "espidf"],
"name": "heltec_wifi_lora_32 v4-R8 (16 MB FLASH, 8 MB OCTAL PSRAM)",
"upload": {
"flash_size": "16MB",
"maximum_ram_size": 8388608,
"maximum_size": 16777216,
"use_1200bps_touch": true,
"wait_for_upload_port": true,
"require_upload_port": true,
"speed": 921600
},
"url": "https://heltec.org/",
"vendor": "heltec"
}
+41
View File
@@ -0,0 +1,41 @@
{
"build": {
"arduino": {
"ldscript": "esp32s3_out.ld",
"partitions": "app3M_fat9M_16MB.csv",
"memory_type": "qio_qspi"
},
"core": "esp32",
"extra_flags": [
"-DBOARD_HAS_PSRAM",
"-DARDUINO_USB_MODE=1",
"-DARDUINO_RUNNING_CORE=1",
"-DARDUINO_EVENT_RUNNING_CORE=1",
"-DARDUINO_USB_CDC_ON_BOOT=1"
],
"f_cpu": "240000000L",
"f_flash": "80000000L",
"flash_mode": "qio",
"hwids": [["0x303A", "0x82D4"]],
"mcu": "esp32s3",
"variant": "lilygo_tlora_pager_pins",
"variants_dir": "variants"
},
"connectivity": ["wifi"],
"debug": {
"default_tool": "esp-builtin",
"onboard_tools": ["esp-builtin"],
"openocd_target": "esp32s3.cfg"
},
"frameworks": ["arduino", "espidf"],
"name": "LilyGo T-LoRa-Pager (16M Flash 8M QSPI PSRAM )",
"upload": {
"flash_size": "16MB",
"maximum_ram_size": 327680,
"maximum_size": 16777216,
"require_upload_port": true,
"speed": 921600
},
"url": "https://www.lilygo.cc",
"vendor": "LilyGo"
}
+43
View File
@@ -0,0 +1,43 @@
{
"build": {
"arduino": {
"ldscript": "esp32s3_out.ld",
"partitions": "default_16MB.csv",
"memory_type": "qio_opi"
},
"core": "esp32",
"extra_flags": [
"-DBOARD_HAS_PSRAM",
"-DARDUINO_USB_CDC_ON_BOOT=1",
"-DARDUINO_USB_MODE=1",
"-DARDUINO_RUNNING_CORE=1",
"-DARDUINO_EVENT_RUNNING_CORE=1"
],
"f_cpu": "240000000L",
"f_flash": "80000000L",
"flash_mode": "dio",
"psram_type": "qspi",
"hwids": [["0x303A", "0x1001"]],
"mcu": "esp32s3",
"variant": "esp32s3"
},
"connectivity": ["wifi", "bluetooth", "lora"],
"debug": {
"default_tool": "esp-builtin",
"onboard_tools": ["esp-builtin"],
"openocd_target": "esp32s3.cfg"
},
"frameworks": ["arduino", "espidf"],
"name": "RAK WisMesh Tap V2 (16 MB FLASH, 8 MB Octal PSRAM)",
"upload": {
"flash_size": "16MB",
"maximum_ram_size": 8388608,
"maximum_size": 16777216,
"use_1200bps_touch": false,
"wait_for_upload_port": false,
"require_upload_port": true,
"speed": 460800
},
"url": "https://store.rakwireless.com/products/wismesh-tap-v2",
"vendor": "RAKwireless"
}
+40
View File
@@ -0,0 +1,40 @@
{
"build": {
"arduino": {
"ldscript": "esp32s3_out.ld",
"partitions": "default_16MB.csv",
"memory_type": "qio_opi"
},
"core": "esp32",
"extra_flags": [
"-DBOARD_HAS_PSRAM",
"-DARDUINO_USB_CDC_ON_BOOT=0",
"-DARDUINO_RUNNING_CORE=1",
"-DARDUINO_EVENT_RUNNING_CORE=1"
],
"f_cpu": "240000000L",
"f_flash": "80000000L",
"flash_mode": "qio",
"psram_type": "opi",
"hwids": [["0x303A", "0x1001"]],
"mcu": "esp32s3",
"variant": "esp32s3"
},
"connectivity": ["wifi", "bluetooth", "lora", "gps"],
"debug": {
"default_tool": "esp-builtin",
"onboard_tools": ["esp-builtin"],
"openocd_target": "esp32s3.cfg"
},
"frameworks": ["arduino", "espidf"],
"name": "Elecrow ThinkNode M9 (16 MB FLASH, 8 MB PSRAM)",
"upload": {
"flash_size": "16MB",
"maximum_ram_size": 327680,
"maximum_size": 16777216,
"require_upload_port": true,
"speed": 921600
},
"url": "https://www.elecrow.com/",
"vendor": "Elecrow"
}
+14 -1
View File
@@ -3,12 +3,25 @@
Distribution stack for wadamesh: a **VPS nginx origin behind Cloudflare**.
```
tiles.wadamesh.com →CF (HTTP, edge-cached) → nginx → tile.openstreetmap.org
tiles.wadamesh.com →CF (HTTP, edge-cached) → nginx → OpenStreetMap / OpenTopoMap
firmware.wadamesh.com →CF (cache bins) → nginx → /srv/wadamesh/firmware
flasher.wadamesh.com →CF (HTTPS) → web flasher (TODO — see below)
wadamesh.com →CF (HTTPS) → landing page (later)
```
**Map tile styles.** The default `/{z}/{x}/{y}.jpg` route serves **OpenStreetMap**
(the firmware default). An opt-in **OpenTopoMap** topographic style is served from
`/opentopo/{z}/{x}/{y}.jpg` (explicit OSM alias at `/osm/...`); the device requests
it only when the user enables *Map → Options → Topographic map*. Legal: OpenTopoMap
map tiles are **© OpenTopoMap (CC-BY-SA)** over **© OpenStreetMap contributors
(ODbL) + SRTM** — the touch UI shows that attribution when topo is active, and the
14-day disk cache keeps each tile hitting OpenTopoMap at most once per fortnight
(their tile-usage policy asks for a contactable UA + caching, both of which the
transcode service provides). Deploying the topo routes = update
`tiles.wadamesh.com.conf` + `tile-transcode.py`, then
`systemctl restart wadamesh-tile-transcode && nginx -t && systemctl reload nginx`
and purge the Cloudflare cache for `tiles.wadamesh.com/opentopo/*`.
The firmware fetches **tiles + the update-check over plain HTTP** (on-device HTTPS
isn't viable — mbedTLS needs ~30 KB heap, only ~5 KB is free post-Wi-Fi), so the
tile + firmware hosts must stay reachable over HTTP. Cloudflare provides the edge
+15 -2
View File
@@ -44,9 +44,13 @@ if os.path.exists(nf):
# Both touch boards are ESP32-S3, single touch-UI ("gui") role. ota_0 sits at
# 0x10000 on both (partitions_t*_touch.csv), so flash-update@0x10000 is correct.
# `name` MUST match the official MeshCore device name character-for-character, or Mesh America lists it
# as a NEW device instead of folding our firmware into the existing tile (TJ Downes, 2026-06). Canonical
# names verified from apps.meshamerica.com/proxy/flasher/config.json. The V4 entry is the Expansion Kit
# (Touch) variant only, per Kaj. `slug` still maps to our bin filenames on firmware.wadamesh.com.
BOARDS = [
{"name": "wadamesh — Heltec V4 TFT", "slug": "heltec-v4-tft"},
{"name": "wadamesh — LilyGo T-Deck", "slug": "tdeck"},
{"name": "Heltec v4 + Expansion Kit (Touch)", "slug": "heltec-v4-tft"},
{"name": "LilyGo T-Deck", "slug": "tdeck"},
]
def device(b):
@@ -74,7 +78,16 @@ def device(b):
}],
}
# Optional "what's this?" blurb Mesh America shows on a hover tooltip next to our provider badge
# (spec section 3, added by TJ 2026-06-30). Plain text only — rendered escaped, so no markup/links.
DESCRIPTION = (
"WADAMESH is a full touch-screen interface for MeshCore: on-device chat, contacts, a live map "
"with offline tiles, and complete radio settings. Same MeshCore protocol and phone-app companion "
"as stock MeshCore, just a richer on-device front-end."
)
catalog = {
"description": DESCRIPTION,
"maker": {"wadamesh": {"name": "wadamesh"}},
"device": [device(b) for b in BOARDS],
}
+11 -10
View File
@@ -1,4 +1,5 @@
{
"description": "WADAMESH is a full touch-screen interface for MeshCore: on-device chat, contacts, a live map with offline tiles, and complete radio settings. Same MeshCore protocol and phone-app companion as stock MeshCore, just a richer on-device front-end.",
"maker": {
"wadamesh": {
"name": "wadamesh"
@@ -8,7 +9,7 @@
{
"maker": "wadamesh",
"class": "wadamesh",
"name": "wadamesh — Heltec V4 TFT",
"name": "Heltec v4 + Expansion Kit (Touch)",
"type": "esp32",
"tooltip": "<img class='device' src='https://wadamesh.com/wadamesh-icon-512.png'>",
"firmware": [
@@ -16,19 +17,19 @@
"role": "gui",
"title": "Touch UI",
"version": {
"beta_12": {
"notes": "Fixed GPS being slow to get a fix — or sometimes never acquiring at all — on the T-Deck. The GPS receives its data over a small serial buffer, and on the busy touch UI a heavy screen redraw could stall long enough to overflow it and drop the satellite data mid-stream, which forced the receiver to start over. The buffer is now 16x larger, so those redraws no longer cost you the fix — acquisition is back to normal (a fix in about a minute instead of several, or none).\nMore and more people are picking up wadamesh lately — which is genuinely awesome — and it's surfacing feature requests and bug reports fast, in big numbers.\nI can't get back to every post in every channel, but I'm on it: I'm prioritising the fixes and quality-of-life improvements, and I'll be working through them later today. Thanks for all the reports and for the patience!",
"beta_40": {
"notes": "Big translation pass: hundreds of previously-English strings across menus, settings, dialogs and the setup flow are now translated into all 11 non-English languages (Dutch, German, French, Spanish, Italian, Russian, Ukrainian, Bulgarian, Serbian, Greek, Brazilian Portuguese). Menu rows that carry an icon translate too. Switch language under Settings.\nChat scrolling is fully virtualized (contributed by scratchdiver, PR #130): a chat now scrolls through its ENTIRE stored history, up to 5000 messages on SD-card devices, smoothly in both bubble and compact mode, instead of only the most recent rows.\nLong-press any message for a Delete option that removes just that message; the message menu lays its buttons two per row so it fits on one screen.\nThe chat and channel settings sheet gains \"Delete history\": wipes the whole conversation after a confirmation, while the channel membership or contact stays.\nThe in-chat jump buttons are slim arrows tucked against the right edge: fully visible while you scroll, fading to half opacity a second after you stop.\nThinkNode M9 hardware support is complete (contributed by ded, PR #138): GPS, microSD, buzzer, backlight control, lock screen, long-press context menus, and a d-pad-driven setup wizard. It can be installed straight from the web flasher.\nNew board: RAK WisMesh Tap V2 (contributed by Ethac.chen, PR #136), with a 30+ fps display driver, also installable from the web flasher.\nThe Wi-Fi network screens (join a network, hidden network, saved-network details) are full-screen pages now instead of small popups, matching the other settings pages and scrolling properly with the keyboard open.\nThe lock screen shows an envelope with the number of unread messages under the clock, so you can check for news without unlocking (idea from issue #93).\nPasswords with special characters can be entered everywhere: long-press any settings field, including the Wi-Fi password, for a Cut / Copy / Paste / All / Sym menu. Sym opens a picker with the characters the on-screen keyboard lacks (issue #122). Double-tap selects a word.\nFor Launcher installs: a \"Save update bin to SD\" button on the About page downloads the latest firmware of your selected channel into a BINS folder on the SD card, ready to flash from the Launcher. The test-builds toggle is visible on Launcher installs too.\nNew region preset \"Australia (Mid)\": 915.075 MHz, 125 kHz, SF9, CR5 (requested in issue #121).\nYour GPS position is now the first row in the quick-reply picker, so you can send your current coordinates with one tap (contributed by Yazutsu, PR #125).\nTanmatsu: hold ALT and press a letter to open the accent picker; keep ALT held and press again to cycle, release to insert (requested by jochentj, issue #129). Double-tap the space bar to switch between your enabled keyboard languages, same as the T-Deck.\nWhile in a chat, the top bar shows the active keyboard language next to the clock when more than one layout is enabled.\nThe \"Store data on SD\" toggle is now actually honored after a reboot (fix contributed by scratchdiver, PR #123). On Launcher installs it silently reverted to internal storage every boot, which also kept the slow internal-flash writes. Turning it off works reliably now too.\nTurning on \"Store data on SD\" migrates your existing profile, settings and identity to the card FIRST, so upgrading no longer risks adopting an empty card and booting as a brand-new node. If you were already hit by that, Settings -> General -> \"Copy internal data to SD\" restores the profile from internal flash.\nCard-less devices (Heltec V4, and any board without an SD card) no longer freeze for several seconds at a time. A busy mesh re-writes the whole contacts file to internal flash on every advert refresh, and that flash garbage-collection stalled the whole device; contact saves are now coalesced so only real changes (a new or removed node) are written promptly.\nDeleting a message, or clearing a whole chat, now sticks: it survives a reboot or a hardware reset instead of coming back (reported by Leon P and MrWeavis). Deleting is also much faster - chat history is written compactly, only the messages you actually have, so a delete, a history wipe, or a reboot no longer pauses the screen while it saves.\nMessages no longer vanish when you reboot the device from the phone app (reported by Leon P): the app's reboot command now saves chat history first, like every on-device reboot path already did.\nChat history saves to the SD card are more robust: files are written atomically with a fallback save path, so a badly timed reboot can no longer truncate your message history (contributed by scratchdiver, PR #135).\nLonger translated labels (French, German, etc.) that used to clip or wrap now shrink to fit: the message action menu, confirmation dialogs, and the app-drawer tiles all keep their text on one line. The signal card's \"tap for details\" hint no longer overlaps in other languages.\Line truncated
"files": [
{
"type": "flash-wipe",
"name": "wadamesh-heltec-v4-tft-merged.bin",
"url": "https://firmware.wadamesh.com/releases/TOUCH/beta_12/wadamesh-heltec-v4-tft-merged.bin",
"url": "https://firmware.wadamesh.com/releases/TOUCH/beta_40/wadamesh-heltec-v4-tft-merged.bin",
"title": "Full install (bootloader + firmware)"
},
{
"type": "flash-update",
"name": "wadamesh-heltec-v4-tft.bin",
"url": "https://firmware.wadamesh.com/releases/TOUCH/beta_12/wadamesh-heltec-v4-tft.bin",
"url": "https://firmware.wadamesh.com/releases/TOUCH/beta_40/wadamesh-heltec-v4-tft.bin",
"title": "Update (app only)"
}
]
@@ -40,7 +41,7 @@
{
"maker": "wadamesh",
"class": "wadamesh",
"name": "wadamesh — LilyGo T-Deck",
"name": "LilyGo T-Deck",
"type": "esp32",
"tooltip": "<img class='device' src='https://wadamesh.com/wadamesh-icon-512.png'>",
"firmware": [
@@ -48,19 +49,19 @@
"role": "gui",
"title": "Touch UI",
"version": {
"beta_12": {
"notes": "Fixed GPS being slow to get a fix — or sometimes never acquiring at all — on the T-Deck. The GPS receives its data over a small serial buffer, and on the busy touch UI a heavy screen redraw could stall long enough to overflow it and drop the satellite data mid-stream, which forced the receiver to start over. The buffer is now 16x larger, so those redraws no longer cost you the fix — acquisition is back to normal (a fix in about a minute instead of several, or none).\nMore and more people are picking up wadamesh lately — which is genuinely awesome — and it's surfacing feature requests and bug reports fast, in big numbers.\nI can't get back to every post in every channel, but I'm on it: I'm prioritising the fixes and quality-of-life improvements, and I'll be working through them later today. Thanks for all the reports and for the patience!",
"beta_40": {
"notes": "Big translation pass: hundreds of previously-English strings across menus, settings, dialogs and the setup flow are now translated into all 11 non-English languages (Dutch, German, French, Spanish, Italian, Russian, Ukrainian, Bulgarian, Serbian, Greek, Brazilian Portuguese). Menu rows that carry an icon translate too. Switch language under Settings.\nChat scrolling is fully virtualized (contributed by scratchdiver, PR #130): a chat now scrolls through its ENTIRE stored history, up to 5000 messages on SD-card devices, smoothly in both bubble and compact mode, instead of only the most recent rows.\nLong-press any message for a Delete option that removes just that message; the message menu lays its buttons two per row so it fits on one screen.\nThe chat and channel settings sheet gains \"Delete history\": wipes the whole conversation after a confirmation, while the channel membership or contact stays.\nThe in-chat jump buttons are slim arrows tucked against the right edge: fully visible while you scroll, fading to half opacity a second after you stop.\nThinkNode M9 hardware support is complete (contributed by ded, PR #138): GPS, microSD, buzzer, backlight control, lock screen, long-press context menus, and a d-pad-driven setup wizard. It can be installed straight from the web flasher.\nNew board: RAK WisMesh Tap V2 (contributed by Ethac.chen, PR #136), with a 30+ fps display driver, also installable from the web flasher.\nThe Wi-Fi network screens (join a network, hidden network, saved-network details) are full-screen pages now instead of small popups, matching the other settings pages and scrolling properly with the keyboard open.\nThe lock screen shows an envelope with the number of unread messages under the clock, so you can check for news without unlocking (idea from issue #93).\nPasswords with special characters can be entered everywhere: long-press any settings field, including the Wi-Fi password, for a Cut / Copy / Paste / All / Sym menu. Sym opens a picker with the characters the on-screen keyboard lacks (issue #122). Double-tap selects a word.\nFor Launcher installs: a \"Save update bin to SD\" button on the About page downloads the latest firmware of your selected channel into a BINS folder on the SD card, ready to flash from the Launcher. The test-builds toggle is visible on Launcher installs too.\nNew region preset \"Australia (Mid)\": 915.075 MHz, 125 kHz, SF9, CR5 (requested in issue #121).\nYour GPS position is now the first row in the quick-reply picker, so you can send your current coordinates with one tap (contributed by Yazutsu, PR #125).\nTanmatsu: hold ALT and press a letter to open the accent picker; keep ALT held and press again to cycle, release to insert (requested by jochentj, issue #129). Double-tap the space bar to switch between your enabled keyboard languages, same as the T-Deck.\nWhile in a chat, the top bar shows the active keyboard language next to the clock when more than one layout is enabled.\nThe \"Store data on SD\" toggle is now actually honored after a reboot (fix contributed by scratchdiver, PR #123). On Launcher installs it silently reverted to internal storage every boot, which also kept the slow internal-flash writes. Turning it off works reliably now too.\nTurning on \"Store data on SD\" migrates your existing profile, settings and identity to the card FIRST, so upgrading no longer risks adopting an empty card and booting as a brand-new node. If you were already hit by that, Settings -> General -> \"Copy internal data to SD\" restores the profile from internal flash.\nCard-less devices (Heltec V4, and any board without an SD card) no longer freeze for several seconds at a time. A busy mesh re-writes the whole contacts file to internal flash on every advert refresh, and that flash garbage-collection stalled the whole device; contact saves are now coalesced so only real changes (a new or removed node) are written promptly.\nDeleting a message, or clearing a whole chat, now sticks: it survives a reboot or a hardware reset instead of coming back (reported by Leon P and MrWeavis). Deleting is also much faster - chat history is written compactly, only the messages you actually have, so a delete, a history wipe, or a reboot no longer pauses the screen while it saves.\nMessages no longer vanish when you reboot the device from the phone app (reported by Leon P): the app's reboot command now saves chat history first, like every on-device reboot path already did.\nChat history saves to the SD card are more robust: files are written atomically with a fallback save path, so a badly timed reboot can no longer truncate your message history (contributed by scratchdiver, PR #135).\nLonger translated labels (French, German, etc.) that used to clip or wrap now shrink to fit: the message action menu, confirmation dialogs, and the app-drawer tiles all keep their text on one line. The signal card's \"tap for details\" hint no longer overlaps in other languages.\Line truncated
"files": [
{
"type": "flash-wipe",
"name": "wadamesh-tdeck-merged.bin",
"url": "https://firmware.wadamesh.com/releases/TOUCH/beta_12/wadamesh-tdeck-merged.bin",
"url": "https://firmware.wadamesh.com/releases/TOUCH/beta_40/wadamesh-tdeck-merged.bin",
"title": "Full install (bootloader + firmware)"
},
{
"type": "flash-update",
"name": "wadamesh-tdeck.bin",
"url": "https://firmware.wadamesh.com/releases/TOUCH/beta_12/wadamesh-tdeck.bin",
"url": "https://firmware.wadamesh.com/releases/TOUCH/beta_40/wadamesh-tdeck.bin",
"title": "Update (app only)"
}
]
+21 -1
View File
@@ -25,12 +25,22 @@ server {
root /srv/wadamesh/firmware;
# The update-check feed — served at the no-slash path the firmware requests.
# STABLE channel (the default on-device update check).
location = /releases/TOUCH {
default_type application/json;
alias /srv/wadamesh/firmware/releases/TOUCH/index.json;
add_header Cache-Control "public, max-age=60";
}
# Same, for the opt-in TEST/BETA channel — what a device requests when the
# "Get test builds (beta)" switch is on. Without this exact-match the no-slash
# path 301-redirects to a dir with no index and the beta check comes back empty.
location = /releases/BETA {
default_type application/json;
alias /srv/wadamesh/firmware/releases/BETA/index.json;
add_header Cache-Control "public, max-age=60";
}
# Bins + everything else under /releases/. CORS so the browser flasher
# (flasher.wadamesh.com) can fetch the images cross-origin.
location /releases/ {
@@ -41,7 +51,7 @@ server {
}
# Rolling "latest" merged images — the web flasher's manifests point here so
# they always install the newest build (release.sh refreshes this dir).
# they always install the newest build (release.sh refreshes this dir). STABLE.
location /latest/ {
autoindex off;
types { application/octet-stream bin; }
@@ -49,5 +59,15 @@ server {
add_header Access-Control-Allow-Origin "*";
}
# Rolling "latest" for the TEST/BETA channel — the beta web-flasher feed
# (version.json + manifests + rolling bins). Without this it falls to the
# catch-all 404 and the flasher's beta toggle can't load metadata.
location /latest-beta/ {
autoindex off;
types { application/octet-stream bin; }
add_header Cache-Control "public, max-age=300";
add_header Access-Control-Allow-Origin "*";
}
location / { return 404; }
}
+46 -2
View File
@@ -1,4 +1,5 @@
# tiles.wadamesh.com — OSM tile proxy for the wadamesh map tab.
# tiles.wadamesh.com — map-tile proxy for the wadamesh map tab. Default style is
# OpenStreetMap; an opt-in OpenTopoMap topographic style is served from /opentopo/.
#
# The firmware fetches plain HTTP (on-device HTTPS isn't workable: mbedTLS wants
# ~30 KB heap for a handshake and only ~5 KB is free after Wi-Fi associates), so
@@ -62,6 +63,49 @@ server {
proxy_connect_timeout 5s;
}
# OpenTopoMap (topographic) — OPT-IN alternate style. The firmware requests
# this path only when the user enables "Topographic map"; the default
# /{z}/{x}/{y}.jpg above stays OpenStreetMap. Legal: map © OpenTopoMap
# (CC-BY-SA), data © OpenStreetMap contributors + SRTM — the touch UI shows
# that attribution when topo is selected. The 14-day disk cache means each
# tile hits OpenTopoMap at most once per fortnight (their tile policy asks it).
location ~ "^/opentopo/(?<z>[0-9]{1,2})/(?<x>[0-9]{1,7})/(?<y>[0-9]{1,7})\.jpg$" {
proxy_pass http://127.0.0.1:5005/opentopo/$z/$x/$y.jpg;
proxy_set_header Host "tiles.wadamesh.com";
proxy_cache wadamesh_tiles;
proxy_cache_key "opentopo-jpg:$z/$x/$y";
proxy_cache_valid 200 14d;
proxy_cache_valid 404 1d;
proxy_cache_use_stale error timeout updating http_500 http_502 http_503 http_504;
proxy_cache_lock on;
add_header X-Cache-Status $upstream_cache_status always;
add_header Cache-Control "public, max-age=2592000" always;
proxy_buffering on;
proxy_read_timeout 20s;
proxy_connect_timeout 5s;
}
# Explicit OpenStreetMap alias (identical to the default root path above).
location ~ "^/osm/(?<z>[0-9]{1,2})/(?<x>[0-9]{1,7})/(?<y>[0-9]{1,7})\.jpg$" {
proxy_pass http://127.0.0.1:5005/osm/$z/$x/$y.jpg;
proxy_set_header Host "tiles.wadamesh.com";
proxy_cache wadamesh_tiles;
proxy_cache_key "osm-jpg:$z/$x/$y";
proxy_cache_valid 200 14d;
proxy_cache_valid 404 1d;
proxy_cache_use_stale error timeout updating http_500 http_502 http_503 http_504;
proxy_cache_lock on;
add_header X-Cache-Status $upstream_cache_status always;
add_header Cache-Control "public, max-age=2592000" always;
proxy_buffering on;
proxy_read_timeout 20s;
proxy_connect_timeout 5s;
}
# Elevation profile for the line-of-sight analyzer (same local service).
location = /elev {
proxy_pass http://127.0.0.1:5005;
@@ -98,7 +142,7 @@ server {
# Tiny landing so a human hitting the bare hostname isn't met with 404.
location = / {
default_type text/plain;
return 200 "wadamesh tile proxy\n\nUsage: GET /{z}/{x}/{y}.jpg (HTTP only)\nUpstream: tile.openstreetmap.org (PNG transcoded to JPEG)\n";
return 200 "wadamesh tile proxy (HTTP only)\n\n /{z}/{x}/{y}.jpg -> OpenStreetMap (default)\n /osm/{z}/{x}/{y}.jpg -> OpenStreetMap\n /opentopo/{z}/{x}/{y}.jpg -> OpenTopoMap (CC-BY-SA)\n\nUpstream PNG transcoded to JPEG.\n";
}
location / { return 404; }
Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 119 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.0 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 96 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 62 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 83 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 93 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 104 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 105 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 81 KiB

+605
View File
@@ -0,0 +1,605 @@
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>WADAMESH — Documentation</title>
<meta name="description" content="User guide for the WADAMESH touch firmware on the LilyGo T-Deck: home, chat, contacts, map, settings and the built-in apps. Real device screenshots.">
<link rel="icon" href="wadamesh-badge.svg">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@600;700&display=swap" rel="stylesheet">
<style>
:root{
--bg:#ffffff; --bg2:#f4f6f2; --ink:#15181e; --mut:#5d6770;
--line:#e5e8e2; --teal:#15b6a6; --teal-ink:#0e8d80;
color-scheme:light;
}
*{box-sizing:border-box;margin:0;padding:0}
html{scroll-behavior:smooth}
body{font:16px/1.65 -apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Inter,sans-serif; background:var(--bg); color:var(--ink); -webkit-font-smoothing:antialiased}
a{color:var(--teal-ink); text-decoration:none}
.top{position:sticky; top:0; z-index:30; display:flex; align-items:center; gap:14px; padding:12px 22px;
background:rgba(255,255,255,.88); backdrop-filter:saturate(1.2) blur(8px); border-bottom:1px solid var(--line)}
.top .word{font-weight:700; letter-spacing:2px; font-size:1.05rem; color:var(--ink)}
.top .word .t{color:var(--teal)}
.top .tag{font-family:'JetBrains Mono',monospace; font-size:.66rem; letter-spacing:.18em; text-transform:uppercase; color:var(--mut); border:1px solid var(--line); border-radius:100px; padding:4px 9px}
.top .sp{flex:1}
.top .home{display:inline-flex; align-items:center; gap:7px; color:var(--mut); font-size:.86rem; border:1px solid var(--line); border-radius:100px; padding:6px 13px; background:#fff; transition:background .15s,color .15s,border-color .15s}
.top .home:hover{color:var(--teal-ink); background:var(--bg2); border-color:#bfe6e0}
.top .home svg{width:16px;height:16px}
.shell{max-width:1200px; margin:0 auto; display:grid; grid-template-columns:220px 1fr; gap:34px; padding:0 22px}
nav.toc{position:sticky; top:64px; align-self:start; height:calc(100vh - 64px); overflow:auto; padding:26px 0 40px}
nav.toc .grp{font-family:'JetBrains Mono',monospace; font-size:.68rem; letter-spacing:.13em; text-transform:uppercase; color:var(--mut); margin:20px 0 7px}
nav.toc .grp:first-child{margin-top:0}
nav.toc a{display:block; padding:6px 12px; border-radius:9px; color:#46525c; font-size:.92rem; border-left:2px solid transparent}
nav.toc a:hover{background:var(--bg2); color:var(--ink)}
nav.toc a.on{color:var(--teal-ink); background:rgba(21,182,166,.09); border-left-color:var(--teal); font-weight:600}
main{padding:30px 0 90px; min-width:0}
.hero h1{font-size:clamp(1.9rem,4.4vw,2.6rem); letter-spacing:-.5px; font-weight:750}
.hero p{color:var(--mut); max-width:64ch; margin-top:10px; font-size:1.05rem}
.hero .meta{display:flex; gap:8px; flex-wrap:wrap; margin-top:16px}
.chip{display:inline-flex; align-items:center; gap:6px; font-size:.8rem; color:#3a444d; border:1px solid var(--line); border-radius:100px; padding:5px 11px; background:#fff}
.chip svg{width:14px;height:14px;color:var(--teal)}
section.doc{padding:36px 0; border-top:1px solid var(--line); scroll-margin-top:74px}
.doc h2{font-size:1.5rem; font-weight:730; letter-spacing:-.3px; display:flex; align-items:center; gap:10px}
.doc h2 .ico{width:30px;height:30px;border-radius:9px;display:grid;place-items:center;flex:none; background:rgba(21,182,166,.12);color:var(--teal)}
.doc h2 .ico svg{width:18px;height:18px}
.row{display:grid; grid-template-columns:minmax(0,1fr) 372px; gap:34px; align-items:start; margin-top:16px}
@media(max-width:980px){.row{grid-template-columns:1fr}}
.prose{color:#3c454d; min-width:0}
.prose p{margin:0 0 12px}
.prose h3{font-size:1.02rem; margin:18px 0 6px; color:var(--ink)}
.prose ul{margin:4px 0 12px; padding-left:18px}
.prose li{margin:4px 0}
.prose b{color:var(--ink)}
.prose code{font-family:'JetBrains Mono',monospace; font-size:.85em; background:var(--bg2); border:1px solid var(--line); border-radius:6px; padding:1px 6px}
.shot{position:sticky; top:74px}
.cap{text-align:center; font-family:'JetBrains Mono',monospace; font-size:.68rem; color:var(--mut); margin-top:10px; letter-spacing:.04em}
/* T-Deck frame: the real screenshot + a generated QWERTY keyboard (added in JS) */
.device{width:344px; margin:0 auto; background:#16191d; border-radius:16px; padding:12px 12px 9px; border:1px solid #e9ece7; box-shadow:0 24px 60px -30px rgba(21,24,30,.5)}
.device img.screen{display:block; width:320px; height:240px; border-radius:8px}
.kbd{margin:9px auto 2px; display:flex; flex-direction:column; gap:4px; width:312px}
.kr{display:flex; gap:4px; justify-content:center}
.key{flex:1; max-width:28px; height:15px; background:#23282e; border-radius:4px; display:grid; place-items:center; font:8px/1 system-ui; color:#7d8893}
.key.wide{max-width:140px; flex:4}
.gallery{display:grid; grid-template-columns:repeat(auto-fill,minmax(232px,1fr)); gap:20px; margin-top:18px}
.mini{background:#16191d; border-radius:12px; padding:7px; border:1px solid #e9ece7}
.mini img{display:block; width:100%; height:auto; border-radius:6px}
.mini .cap{margin-top:6px}
.webgrid{display:grid; grid-template-columns:repeat(auto-fill,minmax(178px,1fr)); gap:18px; margin-top:22px}
figure.phone{margin:0; background:#16191d; border-radius:20px; padding:8px; border:1px solid #e9ece7; box-shadow:0 18px 44px -26px rgba(21,24,30,.5)}
figure.phone img{display:block; width:100%; height:auto; border-radius:13px}
figure.phone figcaption{text-align:center; font-family:'JetBrains Mono',monospace; font-size:.66rem; color:var(--mut); margin-top:8px; letter-spacing:.04em}
.subh{font-size:1.06rem; font-weight:700; color:var(--ink); margin:30px 0 2px}
/* Settings-page detail cards: real screenshot + what the page does + its controls */
.sgrp{font-family:'JetBrains Mono',monospace; font-size:.7rem; letter-spacing:.14em; text-transform:uppercase; color:var(--mut); margin:30px 0 0; padding-top:4px}
.scards{display:grid; grid-template-columns:repeat(auto-fill,minmax(290px,1fr)); gap:20px; margin-top:13px}
.scard{border:1px solid var(--line); border-radius:14px; background:#fff; padding:13px; display:flex; flex-direction:column}
.scard .thumb{background:#16191d; border-radius:9px; padding:6px}
.scard .thumb img{display:block; width:100%; height:auto; border-radius:5px}
.scard .thumb.ph{aspect-ratio:4/3; display:grid; place-items:center; border:1px dashed #39424b; padding:0}
.scard .thumb.ph span{font-family:'JetBrains Mono',monospace; font-size:.6rem; letter-spacing:.12em; color:#7d8893; text-transform:uppercase}
.scard h3{font-size:1.04rem; margin:12px 0 2px; color:var(--ink); display:flex; align-items:center; gap:8px; flex-wrap:wrap}
.scard h3 .tag{font-family:'JetBrains Mono',monospace; font-size:.58rem; letter-spacing:.05em; text-transform:uppercase; color:var(--teal-ink); background:rgba(21,182,166,.1); border-radius:5px; padding:2px 6px; font-weight:600}
.scard .lede{color:var(--mut); font-size:.9rem; margin:2px 0 9px}
.scard ul{margin:0; padding-left:17px}
.scard li{margin:4px 0; font-size:.89rem; color:#3c454d; line-height:1.5}
.scard li b{color:var(--ink); font-weight:600}
/* Caution callout (amber) */
.callout{display:flex; gap:11px; margin-top:18px; padding:13px 15px; border-radius:11px; background:#fff7ed; border:1px solid #f6dcb8}
.callout .cico{flex:none; width:20px; height:20px; color:#c2740b; margin-top:1px}
.callout .cico svg{width:20px; height:20px}
.callout b{display:block; color:#7c4a03; margin-bottom:3px; font-size:.94rem}
.callout p{margin:0; color:#7a5320; font-size:.9rem; line-height:1.55}
footer{border-top:1px solid var(--line); padding:26px 22px; text-align:center; color:var(--mut); font-size:.85rem}
@media(max-width:980px){
.shell{grid-template-columns:1fr; gap:0}
nav.toc{position:static; height:auto; border-bottom:1px solid var(--line); padding:14px 0; display:flex; gap:6px; overflow:auto; white-space:nowrap}
nav.toc .grp{display:none} nav.toc a{border-left:0; flex:none}
.shot{position:static; margin:0 auto 6px}
}
</style>
</head>
<body>
<div class="top">
<a class="word" href="index.html">WADA<span class="t">MESH</span></a>
<span class="tag">Docs</span>
<span class="sp"></span>
<a class="home" href="index.html"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="m12 19-7-7 7-7"/><path d="M19 12H5"/></svg> Back to site</a>
</div>
<div class="shell">
<nav class="toc" id="toc">
<div class="grp">Start here</div>
<a href="#overview">Overview</a>
<div class="grp">The five tabs</div>
<a href="#home">Home</a>
<a href="#chat">Chat</a>
<a href="#contacts">Contacts</a>
<a href="#map">Map</a>
<a href="#settings">Settings</a>
<div class="grp">With your phone</div>
<a href="#companion">Companion mode</a>
<a href="#remote">Remote &amp; web app</a>
<a href="#web">Web browser</a>
<div class="grp">Reference</div>
<a href="#updates">Updates &amp; test builds</a>
<a href="#settings-pages">Settings pages</a>
<a href="#apps">Apps</a>
</nav>
<main>
<div class="hero" id="overview">
<h1>WADAMESH user guide</h1>
<p>WADAMESH turns a LilyGo T-Deck — its landscape screen, BlackBerry-style keyboard and trackball — into a complete front-end for your MeshCore radio: chat, channels, contacts, a live map and deep radio settings, all on the device. (It also runs on the Heltec V4 and Tanmatsu.) Every screen below is a real screenshot from the device.</p>
<div class="meta">
<span class="chip"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><circle cx="12" cy="12" r="10"/><path d="m9 12 2 2 4-4"/></svg> No phone required</span>
<span class="chip"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M5 12.55a11 11 0 0 1 14 0"/><path d="M8.5 16.4a5 5 0 0 1 7 0"/><line x1="12" y1="20" x2="12" y2="20"/></svg> LoRa + Wi-Fi + Bluetooth</span>
<span class="chip"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><rect x="3" y="3" width="18" height="18" rx="2"/></svg> Keyboard + touch</span>
</div>
<div class="callout">
<span class="cico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M4 4h11l5 5v11a1 1 0 0 1-1 1H5a1 1 0 0 1-1-1V4z"/><path d="M9 4v4M13 4v4"/></svg></span>
<div>
<b>Got a microSD slot? Keep a card inserted.</b>
<p>On devices with a microSD slot (the LilyGo T-Deck and Tanmatsu), wadamesh is best used with a card in place. It keeps map tiles, your contacts and your chat history on the card, which is roomier and far more reliable than the small internal flash, so a card prevents memory issues and stops that data being lost on reboot. The Heltec V4 has no card slot and manages fine on its internal storage.</p>
</div>
</div>
</div>
<section class="doc" id="home">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="m3 9 9-7 9 7v11a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2z"/><path d="M9 22V12h6v10"/></svg></span> Home</h2>
<div class="row">
<div class="prose">
<p>The home tab is your <b>app launcher</b> — a grid of everything on the device:</p>
<ul>
<li><b>Cmdr</b> — the command centre overview.</li>
<li><b>Chats</b>, <b>Contacts</b>, <b>Map</b>, <b>Mentions</b> — jump straight to those.</li>
<li><b>Advertise</b> — announce yourself to the mesh (manual or on a timer).</li>
<li><b>Signal</b> and <b>Monitor</b> — live RX signal and a repeater-style RF activity view.</li>
<li><b>Spectrum</b> — sweep the LoRa band for interference.</li>
<li><b>Settings</b>, <b>Terminal</b> (MeshCore CLI), <b>Files</b> (microSD).</li>
</ul>
<p>The bar along the bottom is always there — it switches the five main tabs (Chat, Contacts, Home, Map, Settings) from anywhere. The top bar shows unread count, time, signal and battery.</p>
</div>
<div class="shot"><div class="device"><img class="screen" src="docs-img/home.png" alt="Home app launcher"></div><div class="cap">Home — app launcher</div></div>
</div>
</section>
<section class="doc" id="chat">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M21 15a2 2 0 0 1-2 2H7l-4 4V5a2 2 0 0 1 2-2h14a2 2 0 0 1 2 2z"/></svg></span> Chat</h2>
<div class="row">
<div class="prose">
<p>Every conversation in one list, newest first — both <b>channels</b> (group chats like <code>#wadamesh</code>, <code>Public</code>) and <b>direct messages</b>. An unread badge shows the count.</p>
<h3>On each row</h3>
<ul>
<li><b>Tap</b> a row to open the conversation, then type on the keyboard to reply.</li>
<li>The <b>gear</b> on the right opens that chat's settings — mute, region &amp; scope, share secret, blocked users, remove — the same screen as the cog inside a chat.</li>
</ul>
<p>The top-right buttons add a contact, mark everything read, and show your QR code.</p>
</div>
<div class="shot"><div class="device"><img class="screen" src="docs-img/chat.png" alt="Chat channel list"></div><div class="cap">Chat — channels &amp; DMs</div></div>
</div>
</section>
<section class="doc" id="contacts">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M16 21v-2a4 4 0 0 0-4-4H6a4 4 0 0 0-4 4v2"/><circle cx="9" cy="7" r="4"/></svg></span> Contacts</h2>
<div class="row">
<div class="prose">
<p>Everyone your node knows — name, type and how recently you heard them. Tap a contact to message it or open its details: signal history, a route trace, telemetry, and share/favourite options.</p>
<p>The <b>overflow menu</b> (top right) holds Search, the <b>Discovered</b> list (nodes heard but not yet added), Add contact, Auto-add settings, and the Blocked list. Auto-add can pull new nodes in from their adverts, or you can add them by hand.</p>
</div>
<div class="shot"><div class="device"><img class="screen" src="docs-img/contacts.png" alt="Contacts list"></div><div class="cap">Contacts</div></div>
</div>
</section>
<section class="doc" id="map">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M9 18l-6 3V6l6-3 6 3 6-3v15l-6 3-6-3z"/><path d="M9 3v15"/><path d="M15 6v15"/></svg></span> Map</h2>
<div class="row">
<div class="prose">
<p>An OpenStreetMap / OpenTopoMap view with your position and your contacts plotted as markers, plus link lines from you to each node. Tiles are fetched over Wi-Fi through the wadamesh proxy and cached to flash (or microSD), so areas you've viewed work offline.</p>
<p>It also has a line-of-sight analyzer: pick a contact and it uses SRTM elevation to show whether terrain blocks the path.</p>
</div>
<div class="shot"><div class="device"><img class="screen" src="docs-img/map.png?v=2" alt="Map"></div><div class="cap">Map</div></div>
</div>
<div class="prose">
<h3>Bring your own tiles (offline maps)</h3>
<p>You don't need Wi-Fi to see the map. Copy a standard OpenStreetMap tile pack onto the T-Deck's microSD card and the map reads straight off the card, fully offline.</p>
<p><b>Where they go.</b> Use the usual slippy-map <code>z/x/y</code> folder layout, in either of these locations on the card:</p>
<ul>
<li><code>/maps/osm/&lt;z&gt;/&lt;x&gt;/&lt;y&gt;.png</code> &mdash; the Meshtastic / MeshCore standard layout (recommended, so packs are interchangeable between apps).</li>
<li><code>/tiles/&lt;z&gt;/&lt;x&gt;/&lt;y&gt;.png</code> &mdash; also read. This is the same folder the Wi-Fi download cache uses, so your own tiles and downloaded ones live side by side.</li>
</ul>
<p><b>Format.</b> 256&times;256 <code>.png</code> tiles (<code>.jpg</code> also works). <code>z</code> is the zoom level and <code>x</code>/<code>y</code> the tile column/row at that zoom &mdash; the same scheme OSM's own tile server and every XYZ tile downloader use, so most ready-made packs drop in unchanged.</p>
<p><b>Turn it on.</b> Open the map's options (the gear button on the map) and switch on <b>Tiles from SD card</b>; the status line confirms <code>Map tiles: microSD</code>. Turn it back off to fetch live tiles over Wi-Fi again.</p>
<p><b>Making a pack.</b> Any XYZ / slippy-map tile downloader works &mdash; point it at OpenStreetMap for your area and a sensible zoom range, then copy the resulting <code>z/x/y</code> folders onto the card. Each extra zoom level roughly quadruples the tile count, so grab only the levels you'll actually use.</p>
<div class="callout">
<span class="cico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="12" cy="12" r="10"/><line x1="12" y1="16" x2="12" y2="12"/><line x1="12" y1="8" x2="12.01" y2="8"/></svg></span>
<div>
<b>Board differences</b>
<p>The "Tiles from SD card" toggle is a T-Deck feature. The Heltec V4 has no microSD slot, so it caches downloaded tiles to a small internal partition (no offline packs there). On the Tanmatsu, tiles &mdash; your own or downloaded &mdash; live at <code>/tiles/&lt;z&gt;/&lt;x&gt;/&lt;y&gt;.jpg</code> on the microSD card; drop JPEG tiles there and they show alongside the downloaded ones.</p>
</div>
</div>
</div>
</section>
<section class="doc" id="settings">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><circle cx="12" cy="12" r="3"/><path d="M19.4 15a1.65 1.65 0 0 0 .33 1.82l.06.06a2 2 0 1 1-2.83 2.83l-.06-.06a1.65 1.65 0 0 0-2.4.33 1.65 1.65 0 0 0-1 1.51V21a2 2 0 0 1-4 0v-.09A1.65 1.65 0 0 0 8 19.4a1.65 1.65 0 0 0-1.82.33l-.06.06a2 2 0 1 1-2.83-2.83l.06-.06a1.65 1.65 0 0 0 .33-2.4 1.65 1.65 0 0 0-1.51-1H1a2 2 0 0 1 0-4h.09A1.65 1.65 0 0 0 3 8z"/></svg></span> Settings</h2>
<div class="row">
<div class="prose">
<p>A tile for each category. Tap one to open its page; the title bar carries a back chevron. The full set is in <a href="#settings-pages">Settings pages</a> below.</p>
<ul>
<li><b>Profile</b> — your name and node identity.</li>
<li><b>Radio &amp; Mesh</b> — frequency, spreading factor, region scope, high-gain receiver, signal probe, auto-advert.</li>
<li><b>Auto-add, Wi-Fi, Bluetooth, GPS</b> — discovery and connectivity.</li>
<li><b>Clock, Battery, Sensors, Display, Keyboard, Sound, Quick replies, Lock screen</b> — the device experience.</li>
<li><b>Language</b> (twelve UI languages), <b>Backups</b>, and <b>About</b> (firmware version, update check, diagnostics).</li>
</ul>
</div>
<div class="shot"><div class="device"><img class="screen" src="docs-img/settings.png" alt="Settings categories"></div><div class="cap">Settings categories</div></div>
</div>
</section>
<section class="doc" id="companion">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><rect x="5" y="2" width="14" height="20" rx="2"/><line x1="11" y1="18" x2="13" y2="18"/></svg></span> Companion mode</h2>
<div class="row">
<div class="prose">
<p>WADAMESH runs everything on its own, but it can also be the radio for the <b>official MeshCore app</b> on your phone (iOS and Android). Your phone brings the big screen and full keyboard; the device does the LoRa. Best of all it works <b>alongside</b> the on-device UI — you can keep using the touch screen while your phone is connected, and your contacts, channels and messages stay in sync between them.</p>
<h3>Three ways to connect</h3>
<ul>
<li><b>USB</b> — plug the device into an Android phone or a computer; the app connects over the cable. Nothing to set up on the device.</li>
<li><b>Bluetooth</b> — turn on Bluetooth in <b>Settings &rarr; Bluetooth</b>. The device appears in the app as <code>MeshCore-&lt;your node name&gt;</code>; pair with the 6-digit code (default <code>123456</code>, changeable on the same page).</li>
<li><b>Wi-Fi</b> — put the device on your network in <b>Settings &rarr; Wi-Fi</b>. On the same Wi-Fi, the app connects to the device's IP address on port <code>5000</code> (the Wi-Fi page shows the IP).</li>
</ul>
<div class="callout">
<span class="cico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M10.29 3.86 1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z"/><line x1="12" y1="9" x2="12" y2="13"/><line x1="12" y1="17" x2="12.01" y2="17"/></svg></span>
<div>
<b>Run Bluetooth and Wi-Fi together only when you need to</b>
<p>Bluetooth and Wi-Fi can be on at the same time, but each one reserves a good chunk of RAM. On the Heltec V4 especially — it has the least free memory of the three boards — keeping both on at once leaves little headroom and can lead to instability or odd behaviour. If you only want the phone app, pick one transport (Bluetooth or Wi-Fi) and leave the other off; if you mostly use the device on its own, keep both off.</p>
</div>
</div>
</div>
<div class="shot"><div class="device"><img class="screen" src="docs-img/set_bluetooth.png" alt="Bluetooth pairing page"></div><div class="cap">Bluetooth &mdash; pairing code</div></div>
</div>
</section>
<section class="doc" id="remote">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M2 16.1A5 5 0 0 1 5.9 20M2 12.05A9 9 0 0 1 9.95 20M2 8V6a2 2 0 0 1 2-2h16a2 2 0 0 1 2 2v12a2 2 0 0 1-2 2h-6"/><line x1="2" y1="20" x2="2.01" y2="20"/></svg></span> Remote &amp; web app</h2>
<div class="row">
<div class="prose">
<p>Over Wi-Fi, a WADAMESH device can put its screen &mdash; or a whole browser app &mdash; on your phone or laptop. There is nothing to install: the device serves a web page you open in any browser on the same network. Turn it on from <b>Home &rarr; Remote</b> (or the Remote screen in Settings), pick a mode, and open the address it shows.</p>
<h3>Three ways to connect</h3>
<ul>
<li><b>Remote app</b> (recommended) &mdash; a full control panel, native to the browser: <b>Chats</b>, <b>Contacts</b>, a <b>Terminal</b> and <b>Settings</b>, with live message notifications. Run the device entirely from your phone.</li>
<li><b>Screen mirror (VNC)</b> &mdash; streams the device's live screen to the browser and sends your taps and key presses back, so you see and drive exactly what is on the device, in real time.</li>
<li><b>Remote UI</b> &mdash; renders the interface off-screen at desktop size (a wide landscape layout) and streams that instead of the small panel, for a roomier view on a big screen.</li>
</ul>
<p>Screen mirror and Remote UI both show the same interface you already know from the device &mdash; mirrored, or drawn larger. The <b>Remote app</b> is different: a browser-native panel built for a phone, shown below.</p>
<h3>Turning it on</h3>
<p>Connect the device to Wi-Fi first, then open <b>Home &rarr; Remote</b>. The screen shows the address to type into your browser (like <code>http://192.168.1.42</code>) and a switch for each mode. Only one streaming mode runs at a time, and the phone and the device must be on the same Wi-Fi network.</p>
</div>
<div class="shot"><div class="device"><img class="screen" src="docs-img/app_remote.png" alt="Remote access screen on the device"></div><div class="cap">Remote &mdash; turn it on, then open the address</div></div>
</div>
<div class="subh">The remote app in a browser</div>
<div class="prose" style="max-width:70ch"><p>The remote app is phone-first. It carries the same status icons as the device (signal, Wi-Fi, Bluetooth, battery), pops up a notification when a message arrives, and refreshes an open chat on its own as replies come in &mdash; so you rarely need to touch the device itself.</p></div>
<div class="webgrid">
<figure class="phone"><img src="docs-img/web_chats.png" alt="Chats tab in the web app"><figcaption>Chats &mdash; DMs, channels, unread badges</figcaption></figure>
<figure class="phone"><img src="docs-img/web_chat.png" alt="A conversation in the web app"><figcaption>A conversation, with delivery ticks</figcaption></figure>
<figure class="phone"><img src="docs-img/web_contacts.png" alt="Contacts tab in the web app"><figcaption>Contacts &mdash; search, sort, filter</figcaption></figure>
<figure class="phone"><img src="docs-img/web_contact_sheet.png" alt="Contact actions in the web app"><figcaption>Tap a contact for actions</figcaption></figure>
<figure class="phone"><img src="docs-img/web_discovered.png" alt="Discovered nodes in the web app"><figcaption>Discovered nodes &mdash; add with a tap</figcaption></figure>
<figure class="phone"><img src="docs-img/web_settings.png" alt="Settings in the web app"><figcaption>Settings &mdash; including live radio</figcaption></figure>
<figure class="phone"><img src="docs-img/web_terminal.png" alt="Terminal in the web app"><figcaption>Terminal &mdash; the MeshCore CLI</figcaption></figure>
</div>
</section>
<section class="doc" id="web">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="12" cy="12" r="10"/><line x1="2" y1="12" x2="22" y2="12"/><path d="M12 2a15.3 15.3 0 0 1 4 10 15.3 15.3 0 0 1-4 10 15.3 15.3 0 0 1-4-10 15.3 15.3 0 0 1 4-10z"/></svg></span> Web browser</h2>
<div class="row">
<div class="prose">
<p>WADAMESH can read the web on its own screen. Open the <b>Web</b> app from the home launcher, type an address, and the device fetches the page and shows it as plain, readable text &mdash; articles, wikis, docs, simple sites. There is no proxy in the middle and nothing is tracked: it pulls the page straight from the site and strips it down to the words.</p>
<ul>
<li><b>Text only</b> &mdash; no JavaScript, no images, no ads. Pages load small and read clean.</li>
<li><b>Tappable links</b> &mdash; follow a link to the next page, with <b>back</b>, <b>forward</b> and <b>refresh</b> in the toolbar.</li>
<li><b>Direct &amp; private</b> &mdash; the device connects to the site itself over Wi-Fi (HTTPS); no server of ours sees what you read.</li>
</ul>
<p>Reading the web on-device takes more memory than the smallest board carries, so the Web app is on the <b>T-Deck</b> and <b>Tanmatsu</b>. On the 2&nbsp;MB Heltec&nbsp;V4 it is hidden &mdash; that board can't complete the secure handshake &mdash; but you can still bounce any link to your phone (below).</p>
</div>
<div class="shot"><div class="device"><img class="screen" src="docs-img/app_web.png" alt="The on-device Web app"></div><div class="cap">Web &mdash; open an address, read it as text</div></div>
</div>
<div class="subh">Links in chat</div>
<div class="prose" style="max-width:70ch"><p>A link that arrives in a message is now tappable. Tap it for a small menu: <b>Open in web</b> loads the page in the on-device browser (T-Deck and Tanmatsu), and <b>Create QR</b> puts a scannable QR code on screen so you can open the link on your phone. Create QR works on <em>every</em> board, including the Heltec&nbsp;V4 &mdash; so even where the browser isn't available, a link is one tap from your phone.</p></div>
<div class="gallery">
<div class="mini"><img src="docs-img/app_web_links.png" alt="Tapping a link in chat opens a menu"><div class="cap">Tap a link &mdash; Open in web, or Create QR</div></div>
<div class="mini"><img src="docs-img/app_web_qr.png" alt="A QR code for a link from chat"><div class="cap">Create QR &mdash; scan to open on your phone</div></div>
</div>
</section>
<section class="doc" id="updates">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M23 4v6h-6"/><path d="M1 20v-6h6"/><path d="M3.51 9a9 9 0 0 1 14.85-3.36L23 10M1 14l4.64 4.36A9 9 0 0 0 20.49 15"/></svg></span> Updates &amp; test builds</h2>
<div class="row">
<div class="prose">
<p>On the boards that update over Wi-Fi (the Heltec V4 and the standalone T-Deck), WADAMESH checks for new firmware on its own. When one is available, <b>Settings &rarr; About</b> shows it and you can flash it straight from the device with <b>Install update</b>, no computer needed. (Under Launcher and on the Tanmatsu you update through Launcher or the app store instead.)</p>
<h3>Two channels: Stable and Test</h3>
<ul>
<li><b>Stable</b> is the default. It is the build that has been tested and is recommended for everyday use. Leave your device on this unless you want to help test.</li>
<li><b>Test (beta)</b> gets new features and fixes earlier, before they are proven. It can be rough, so it is meant for trying things early and reporting bugs, not for a device you rely on.</li>
</ul>
<h3>Turn on test builds</h3>
<p>Flip <b>Settings &rarr; About &rarr; "Get test builds (beta)"</b> on. From then on, both the update check and <b>Install update</b> follow the test channel, so the device offers the newest test build over Wi-Fi. Turn the switch back off to return to stable. You can switch either way at any time.</p>
<p>Prefer to start on a test build from scratch? Pick <b>Beta &middot; testing</b> when you flash from <a href="https://flasher.wadamesh.com" target="_blank" rel="noopener">flasher.wadamesh.com</a>.</p>
</div>
<div class="shot"><div class="device"><img class="screen" src="docs-img/set_about.png" alt="About page"></div><div class="cap">The About page</div></div>
</div>
</section>
<section class="doc" id="settings-pages">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><line x1="4" y1="6" x2="20" y2="6"/><line x1="4" y1="12" x2="20" y2="12"/><line x1="4" y1="18" x2="20" y2="18"/></svg></span> Settings pages</h2>
<div class="prose" style="max-width:68ch"><p>WADAMESH splits its settings into nineteen pages. Here is what each one does and the controls you will find on it. Open any page from the Settings tab; a back chevron in the title bar returns you to the grid.</p></div>
<div class="sgrp">Identity &amp; radio</div>
<div class="scards">
<div class="scard">
<div class="thumb"><img src="docs-img/set_profile.png" alt="Profile settings"></div>
<h3>Profile</h3>
<div class="lede">Who you are on the mesh.</div>
<ul>
<li><b>Node name</b> — your callsign on the network</li>
<li><b>Advert location</b> plus a share-in-advert toggle</li>
<li><b>Identity key</b> and <b>Share QR</b> to hand out your contact</li>
<li><b>Export / Import</b> your whole setup as a JSON backup</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_radio___mesh.png" alt="Radio and Mesh settings"></div>
<h3>Radio &amp; Mesh</h3>
<div class="lede">Every LoRa and mesh parameter, split into RADIO / MESH / SIGNAL.</div>
<ul>
<li><b>Radio</b> — preset, frequency, bandwidth, spreading factor, coding rate, TX power, with a live duty-cycle and airtime-per-packet readout</li>
<li><b>Mesh</b> — answer-telemetry, path-hash size, region scope tag, scope direct messages</li>
<li><b>Signal</b> — high-gain receiver (Heltec V4.3), signal probe, and a shortcut to the Advertise app</li>
<li><b>Experimental</b> — multi-ACKs, client repeat, RX boost, duty meter</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_auto_add.png" alt="Auto-add settings"></div>
<h3>Auto-add</h3>
<div class="lede">Which nodes join Contacts automatically from their adverts.</div>
<ul>
<li>Per-type toggles: <b>chat</b>, <b>repeater</b>, <b>room</b>, <b>sensor</b></li>
<li><b>Overwrite oldest</b> when the contact list is full</li>
<li><b>Notify</b> when a new contact is added</li>
<li><b>Max hops</b> filter for how far away a node can be</li>
</ul>
</div>
</div>
<div class="sgrp">Connectivity</div>
<div class="scards">
<div class="scard">
<div class="thumb"><img src="docs-img/set_wi_fi.png" alt="Wi-Fi settings"></div>
<h3>Wi-Fi</h3>
<div class="lede">For map tiles, clock sync and update checks.</div>
<ul>
<li>On / off with a live status line (IP, signal)</li>
<li><b>Scan</b> and tap an SSID, or type one in by hand</li>
<li><b>Save &amp; reconnect</b> applies live — no reboot</li>
<li>Saved network slots for one-tap quick-connect</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_bluetooth.png" alt="Bluetooth settings"></div>
<h3>Bluetooth</h3>
<div class="lede">Pair with the MeshCore phone app over BLE.</div>
<ul>
<li><b>Enable Bluetooth</b> with a live mode status line</li>
<li>Set a 6-digit <b>pairing code</b> (applies after a reboot)</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_gps.png" alt="GPS settings"></div>
<h3>GPS</h3>
<div class="lede">The on-board GPS receiver.</div>
<ul>
<li>On / off with a live <b>fix status</b> (acquiring, 2D/3D, age)</li>
<li><b>Serial baud</b> rate (applies after a reboot)</li>
<li>Reads "no GPS module" on devices without one</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_mqtt_bridge.png" alt="MQTT bridge settings"></div>
<h3>MQTT bridge <span class="tag">experimental</span></h3>
<div class="lede">Forward received messages to your own MQTT broker.</div>
<ul>
<li>Publishes the <b>text, sender and time</b> of messages your node hears to an MQTT broker</li>
<li>Broker <b>host, port and topic</b>, plus an <b>encryption key</b></li>
<li>Stays off until you <b>accept the privacy note</b> &mdash; anyone who can read the broker sees the messages, so use one you control, never a public broker</li>
</ul>
</div>
</div>
<div class="sgrp">Time &amp; power</div>
<div class="scards">
<div class="scard">
<div class="thumb"><img src="docs-img/set_clock___time.png" alt="Clock and time settings"></div>
<h3>Clock &amp; time</h3>
<div class="lede">Keep the clock right.</div>
<ul>
<li><b>Sync clock</b> from the system / NTP</li>
<li><b>Time zone</b> picker, or a custom UTC offset with steppers</li>
<li><b>12-hour clock</b> toggle</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_battery.png" alt="Battery settings"></div>
<h3>Battery</h3>
<div class="lede">Power readouts and tuning.</div>
<ul>
<li><b>Battery &amp; power history</b> chart</li>
<li><b>Calibrate</b> — tap to set 100% at the current voltage</li>
<li><b>Battery saver</b> throttles the CPU when idle (T-Deck)</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_sensors.png" alt="Sensors settings"></div>
<h3>Sensors <span class="tag">Heltec V4</span></h3>
<div class="lede">For the V4 Expansion Kit.</div>
<ul>
<li><b>Expansion Kit</b> configuration</li>
<li><b>Show Sensors tab</b> in the bottom bar (applies after restart)</li>
</ul>
</div>
</div>
<div class="sgrp">Experience</div>
<div class="scards">
<div class="scard">
<div class="thumb"><img src="docs-img/set_display.png" alt="Display settings"></div>
<h3>Display</h3>
<div class="lede">Look and feel.</div>
<ul>
<li><b>Screen timeout</b> before it sleeps</li>
<li><b>UI size</b> — Normal / Large / Huge</li>
<li><b>Colourful chat bubbles</b>, distance in miles, hide device name</li>
<li><b>Theme colour</b> picker</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_keyboard.png" alt="Keyboard settings"></div>
<h3>Keyboard</h3>
<div class="lede">Typing and on-device input.</div>
<ul>
<li><b>Secondary layouts</b> — Cyrillic, Greek, Arabic, French, German and more</li>
<li><b>Accent popups</b> — long-press for accented letters</li>
<li><b>Enter sends</b> the message (T-Deck)</li>
<li><b>Flash</b> the screen and keys on a new message (T-Deck)</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_sound.png" alt="Sound settings"></div>
<h3>Sound</h3>
<div class="lede">Notification audio.</div>
<ul>
<li>Master sound plus per-type toggles: <b>message</b>, <b>DM</b>, <b>@mention</b></li>
<li>Custom <b>sound files</b> from microSD where supported</li>
<li><b>Volume</b> control (T-Deck / Tanmatsu)</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_quick_replies.png" alt="Quick replies settings"></div>
<h3>Quick replies</h3>
<div class="lede">One-tap canned messages.</div>
<ul>
<li>Edit <b>six</b> short replies</li>
<li>Pick them from the composer to send instantly</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_lock_screen.png" alt="Lock screen settings"></div>
<h3>Lock screen <span class="tag">T-Deck</span></h3>
<div class="lede">A simple lock when idle.</div>
<ul>
<li><b>Wallpaper</b> picker and <b>lock text colour</b></li>
<li><b>Lock when screen off</b>, then hold to unlock</li>
</ul>
</div>
</div>
<div class="sgrp">System</div>
<div class="scards">
<div class="scard">
<div class="thumb ph"><span>Screenshot pending</span></div>
<h3>General</h3>
<div class="lede">Device housekeeping.</div>
<ul>
<li><b>Send advert now</b></li>
<li><b>Store data on SD</b> (reboot)</li>
<li><b>Run setup again</b> from scratch</li>
<li><b>Reboot device</b></li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_backups.png" alt="Backups settings"></div>
<h3>Backups</h3>
<div class="lede">Save and restore your whole config.</div>
<ul>
<li><b>Export</b> a new JSON backup</li>
<li>Restore from the <b>saved list</b></li>
<li><b>Factory reset</b> in the danger zone</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_language.png" alt="Language settings"></div>
<h3>Language</h3>
<div class="lede">Twelve UI languages.</div>
<ul>
<li>Tap a language; the device reboots to apply</li>
</ul>
</div>
<div class="scard">
<div class="thumb"><img src="docs-img/set_about.png" alt="About settings"></div>
<h3>About</h3>
<div class="lede">Version, updates and diagnostics.</div>
<ul>
<li><b>Firmware version</b> plus update check / install</li>
<li><b>Get test builds (beta)</b> switch: opt into the <a href="#updates">test channel</a></li>
<li>Full <b>system diagnostics</b> — uptime, chip, memory, flash, storage</li>
<li><b>Device ID</b> and crash-report export</li>
</ul>
</div>
</div>
</section>
<section class="doc" id="apps">
<h2><span class="ico"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><line x1="8" y1="6" x2="21" y2="6"/><line x1="8" y1="12" x2="21" y2="12"/><line x1="8" y1="18" x2="21" y2="18"/><line x1="3" y1="6" x2="3.01" y2="6"/><line x1="3" y1="12" x2="3.01" y2="12"/><line x1="3" y1="18" x2="3.01" y2="18"/></svg></span> Apps</h2>
<div class="prose" style="max-width:64ch">
<p>Tools from the home launcher. <b>RF Monitor</b> is a repeater-style view of recent packets and radio stats; <b>Spectrum</b> sweeps the band so you can spot interference or find a clear frequency.</p>
</div>
<div class="gallery">
<div class="mini"><img src="docs-img/app_rfmonitor.png" alt="RF Monitor"><div class="cap">RF Monitor</div></div>
<div class="mini"><img src="docs-img/app_spectrum.png" alt="Spectrum analyzer"><div class="cap">Spectrum analyzer</div></div>
</div>
</section>
</main>
</div>
<footer>WADAMESH — open-source MeshCore touch firmware · <a href="index.html">wadamesh.com</a></footer>
<script>
var KB = ['QWERTYUIOP', 'ASDFGHJKL', 'ZXCVBNM'];
document.querySelectorAll('.device').forEach(function(dev){
var kb = document.createElement('div'); kb.className = 'kbd';
KB.forEach(function(rowStr){
var r = document.createElement('div'); r.className = 'kr';
rowStr.split('').forEach(function(ch){ var k = document.createElement('span'); k.className = 'key'; k.textContent = ch; r.appendChild(k); });
kb.appendChild(r);
});
var sp = document.createElement('div'); sp.className = 'kr';
sp.innerHTML = '<span class="key">sym</span><span class="key wide"></span><span class="key">&#9166;</span>';
kb.appendChild(sp);
dev.appendChild(kb);
});
var links = Array.prototype.slice.call(document.querySelectorAll('nav.toc a'));
var obs = new IntersectionObserver(function(es){
es.forEach(function(e){ if (e.isIntersecting) {
links.forEach(function(l){ l.classList.remove('on'); });
var a = document.querySelector('nav.toc a[href="#' + e.target.id + '"]');
if (a) a.classList.add('on');
}});
}, { rootMargin: '-25% 0px -65% 0px' });
['overview','home','chat','contacts','map','settings','companion','settings-pages','apps'].forEach(function(id){ var el = document.getElementById(id); if (el) obs.observe(el); });
</script>
</body>
</html>
+310 -27
View File
@@ -4,7 +4,7 @@
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>WADAMESH — a touchscreen for your mesh radio</title>
<meta name="description" content="Open-source MeshCore touch-UI firmware for the LilyGo T-Deck and Heltec V4. Map, chat, channels, contacts — install from your browser.">
<meta name="description" content="Open-source MeshCore touch-UI firmware for the LilyGo T-Deck, Heltec V4 and Tanmatsu. Map, chat, channels, contacts — install from your browser.">
<link rel="icon" href="wadamesh-badge.svg">
<meta name="theme-color" content="#ffffff">
<link rel="preconnect" href="https://fonts.googleapis.com">
@@ -42,13 +42,21 @@
font-family:'JetBrains Mono',monospace; background:#fff; transition:border-color .15s, color .15s}
.kicker:hover{border-color:var(--teal); color:var(--ink)}
.freeline{margin:0 auto 24px; color:var(--mut); font-size:.92rem}
.fab{position:fixed; top:16px; z-index:45; width:44px; height:44px; border-radius:50%; display:grid; place-items:center;
.fab-rail{position:fixed; top:var(--fab-top,16px); z-index:45; display:flex; flex-direction:column; gap:12px}
/* dismissible donate banner */
.donate-bar{position:sticky; top:0; z-index:50; display:flex; align-items:center; justify-content:center; gap:7px 16px; flex-wrap:wrap;
padding:9px 44px; background:var(--ink); color:#fff; font-size:.9rem; line-height:1.4; text-align:center}
.donate-bar a{color:#fff; text-decoration:underline; text-underline-offset:2px}
.donate-bar .donate-cta{background:var(--teal); color:#fff; text-decoration:none; padding:5px 14px; border-radius:100px; font-weight:650; white-space:nowrap}
.donate-bar .donate-cta:hover{background:var(--cyan)}
.donate-bar .x{position:absolute; right:12px; top:50%; transform:translateY(-50%); background:none; border:0; color:#fff; font-size:1.5rem; line-height:1; cursor:pointer; opacity:.75; padding:0 4px}
.donate-bar .x:hover{opacity:1}
.fab-rail.left{left:16px} .fab-rail.right{right:16px}
.fab{width:44px; height:44px; border-radius:50%; display:grid; place-items:center; cursor:pointer;
background:#fff; border:1px solid var(--line); color:#46525c; box-shadow:0 10px 26px -14px rgba(21,24,30,.45);
transition:border-color .15s, color .15s, transform .15s, box-shadow .15s}
.fab:hover{border-color:var(--teal); color:var(--teal-ink); transform:translateY(-2px); box-shadow:0 14px 30px -14px rgba(21,182,166,.5)}
.fab svg{width:21px; height:21px}
.fab-tg{left:16px}
.fab-bug{right:16px}
.brand{display:flex; align-items:center; justify-content:center; gap:clamp(12px,2.6vw,20px); flex-wrap:wrap; position:relative}
.brand .mark{width:clamp(60px,13vw,88px); height:auto; flex:none}
.brand .word{font-weight:700; font-size:clamp(2rem,7.5vw,3.35rem); letter-spacing:3px; color:var(--ink); line-height:1}
@@ -135,21 +143,80 @@
.step p{color:var(--mut); font-size:.92rem}
.step code{background:#fff; border:1px solid var(--line); border-radius:6px; padding:1px 6px; font-size:.85em; font-family:'JetBrains Mono',monospace}
.boards{display:grid; gap:14px; grid-template-columns:1fr 1fr; max-width:760px; margin:18px auto 0}
.boards{display:grid; gap:14px; grid-template-columns:repeat(auto-fit,minmax(210px,1fr)); max-width:760px; margin:18px auto 0}
@media(max-width:560px){.boards{grid-template-columns:1fr}}
.board{border:1px solid var(--line); background:var(--card); border-radius:14px; padding:18px; display:flex;
flex-direction:column; gap:10px; align-items:flex-start; box-shadow:0 8px 26px -22px rgba(21,24,30,.5)}
.board h4{font-size:1.02rem}
.board p{color:var(--mut); font-size:.86rem}
/* Per-board support-level badge + hover popover (same visual language as the hero pills). */
.sup{position:relative; display:inline-flex; align-items:center; gap:6px; padding:3px 10px; border-radius:999px;
font-size:.72rem; font-weight:700; letter-spacing:.2px; cursor:default; width:max-content}
.sup .dot{width:7px; height:7px; border-radius:50%; flex:none}
.sup.full{background:#e7f6ec; color:#1c7c3f; border:1px solid #bfe6cc}
.sup.full .dot{background:#27a35a}
.sup.part{background:#fdf3e4; color:#9a6410; border:1px solid #f0dcb4}
.sup.part .dot{background:#e3a127}
.sup .pop{position:absolute; top:calc(100% + 11px); left:0; transform:translateY(5px);
width:min(272px,80vw); background:#fff; border:1px solid var(--line); border-radius:12px; padding:13px 15px;
box-shadow:0 18px 44px -18px rgba(21,24,30,.32); text-align:left; font-size:.84rem; font-weight:400;
letter-spacing:0; line-height:1.5; color:var(--mut); opacity:0; visibility:hidden;
transition:opacity .16s ease, transform .16s ease; z-index:20; cursor:default}
.sup .pop b{display:block; color:var(--ink); margin-bottom:4px; font-size:.92rem}
.sup .pop::before{content:""; position:absolute; bottom:100%; left:18px; border:7px solid transparent; border-bottom-color:#fff}
.sup:hover .pop,.sup:focus .pop,.sup:focus-within .pop{opacity:1; visibility:visible; transform:translateY(0)}
esp-web-install-button{--esp-tools-button-color:var(--teal);--esp-tools-button-text-color:#fff}
.dl{display:inline-flex;align-items:center;gap:8px;background:var(--teal);color:#fff;border-radius:9px;
padding:9px 15px;font-weight:650;font-size:.9rem}
.dl:hover{background:var(--teal-ink)}
.dl svg{width:15px;height:15px}
.dl2{display:inline-block;margin-top:-2px;text-decoration:none;line-height:1.3}
.dl2 .dl2-row{display:inline-flex;align-items:center;gap:6px;font-size:.85rem;color:var(--teal);font-weight:700;white-space:nowrap}
.dl2:hover .dl2-row{text-decoration:underline}
.dl2 svg{width:14px;height:14px;flex:none}
.dl2 .dlver{display:block;font-size:.72rem;color:var(--mut);font-weight:600;margin-top:2px;padding-left:20px;letter-spacing:.03em}
.dl2 .dlver:empty{display:none}
.hint{max-width:760px;margin:18px auto 0;color:var(--mut);font-size:.86rem;text-align:center}
/* "install a previous version" picker */
.verpick{max-width:760px; margin:16px auto 0; border:1px solid var(--line); border-radius:12px; background:var(--bg2); text-align:left}
.verpick summary{cursor:pointer; padding:12px 16px; font-weight:600; font-size:.92rem; color:var(--ink); list-style:none; user-select:none}
.verpick summary::-webkit-details-marker{display:none}
.verpick summary::before{content:"\25B8"; color:var(--teal); margin-right:9px; display:inline-block; transition:transform .15s}
.verpick[open] summary::before{transform:rotate(90deg)}
.verpick-body{padding:2px 16px 16px}
.verpick-row{display:flex; align-items:center; gap:10px}
.verpick-row label{font-size:.9rem; color:var(--mut)}
#verSel{font:inherit; font-size:.92rem; padding:7px 11px; border:1px solid var(--line); border-radius:8px; background:#fff; color:var(--ink); cursor:pointer}
.verpick-note{margin:9px 0 0; font-size:.86rem; color:var(--teal-ink)}
.rn{margin-top:12px; max-height:280px; overflow:auto; font-size:.88rem; color:var(--mut); line-height:1.55}
.rn .rn-h{font-size:.92rem; color:var(--ink); font-weight:700; margin:13px 0 5px} .rn .rn-h:first-child{margin-top:0}
.rn ul{margin:5px 0 0; padding-left:18px} .rn li{margin:3px 0}
.rn p{margin:6px 0} .rn code{background:#fff; border:1px solid var(--line); border-radius:5px; padding:1px 5px; font-size:.86em}
.rn a{color:var(--teal-ink)}
.noserial{display:none;color:#b4631a;text-align:center;margin-top:14px}
body.no-serial .noserial{display:block}
/* community videos */
.vids{display:grid; gap:18px; grid-template-columns:repeat(auto-fill,minmax(300px,1fr)); margin-top:34px}
.vid{border:1px solid var(--line); border-radius:16px; overflow:hidden; background:var(--card); box-shadow:0 12px 30px -22px rgba(21,24,30,.5)}
.vid-thumb{position:relative; aspect-ratio:16/9; width:100%; border:0; padding:0; cursor:pointer; display:block; background-size:cover; background-position:center}
.vid-thumb::after{content:""; position:absolute; inset:0; background:rgba(21,24,30,.12); transition:background .15s}
.vid-thumb:hover::after{background:rgba(21,24,30,0)}
.vid-thumb .play{position:absolute; left:50%; top:50%; transform:translate(-50%,-50%); width:62px; height:44px; border-radius:12px;
background:rgba(229,57,53,.94); display:grid; place-items:center; z-index:1; transition:transform .15s, background .15s}
.vid-thumb:hover .play{transform:translate(-50%,-50%) scale(1.07); background:#e53935}
.vid-thumb .play svg{width:24px; height:24px; color:#fff}
.vid-embed{aspect-ratio:16/9; width:100%; border:0; display:block; background:#000}
.vid-cap{padding:13px 15px; font-size:.92rem; color:var(--ink); font-weight:600}
.vid-cap span{display:block; color:var(--mut); font-size:.82rem; font-weight:400; margin-top:2px}
/* toast (docs placeholder etc.) */
.toast{position:fixed; left:50%; bottom:26px; transform:translateX(-50%) translateY(12px); z-index:70;
background:var(--ink); color:#fff; padding:11px 20px; border-radius:100px; font-size:.92rem; font-weight:600;
box-shadow:0 16px 36px -14px rgba(21,24,30,.55); opacity:0; visibility:hidden; pointer-events:none;
transition:opacity .2s ease, transform .2s ease}
.toast.show{opacity:1; visibility:visible; transform:translateX(-50%) translateY(0)}
footer{border-top:1px solid var(--line); margin-top:48px; padding:30px 0 56px; text-align:center; color:var(--mut); font-size:.86rem}
footer a{color:var(--teal-ink)}
.legal-links{margin-top:12px}
@@ -173,15 +240,34 @@
</style>
</head>
<body>
<div class="donate-bar" id="donateBar">
<span>Like the project and want to donate? Help out the <b>MeshCore</b> founders instead. <a href="https://blog.meshcore.io/2026/07/04/help-us-save-meshcore" target="_blank" rel="noopener">Learn more</a></span>
<a class="donate-cta" href="https://givealittle.co.nz/cause/help-us-save-meshcore" target="_blank" rel="noopener">Donate</a>
<button class="x" id="donateX" type="button" aria-label="Dismiss">&times;</button>
</div>
<div id="vanta-bg"></div>
<!-- floating quick links -->
<a class="fab fab-tg" href="https://t.me/+fHuhG67-RFJlNmFk" target="_blank" rel="noopener" aria-label="Join us on Telegram" title="Join us on Telegram">
<svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M9.04 15.47 8.7 19.9c.5 0 .72-.22.98-.47l2.36-2.22 4.89 3.53c.9.5 1.53.24 1.77-.83l3.2-14.5c.3-1.33-.5-1.85-1.36-1.53L1.9 9.46c-1.3.5-1.28 1.22-.22 1.55l5.05 1.57L18.4 5.9c.55-.36 1.05-.16.64.2L9.04 15.47z"/></svg>
</a>
<a class="fab fab-bug" href="https://github.com/ALLFATHER-BV/wadamesh/issues" target="_blank" rel="noopener" aria-label="Report a bug on GitHub" title="Report a bug">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><rect width="8" height="14" x="8" y="6" rx="4"/><path d="m19 7-3 2"/><path d="m5 7 3 2"/><path d="m19 19-3-2"/><path d="m5 19 3-2"/><path d="M20 13h-4"/><path d="M4 13h4"/><path d="m10 4 1 2"/><path d="m14 4-1 2"/></svg>
</a>
<div class="fab-rail left">
<a class="fab" href="https://discord.gg/T8X2UaQ7Sm" target="_blank" rel="noopener" aria-label="Join us on Discord" title="Join us on Discord">
<svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M20.317 4.369a19.79 19.79 0 0 0-4.885-1.515.074.074 0 0 0-.079.037c-.21.375-.444.864-.608 1.249a18.27 18.27 0 0 0-5.487 0 12.6 12.6 0 0 0-.617-1.249.077.077 0 0 0-.079-.037A19.74 19.74 0 0 0 3.677 4.369a.07.07 0 0 0-.032.027C.533 9.046-.32 13.58.099 18.057a.082.082 0 0 0 .031.057 19.9 19.9 0 0 0 5.993 3.03.078.078 0 0 0 .084-.028 14.2 14.2 0 0 0 1.226-1.994.076.076 0 0 0-.041-.106 13.1 13.1 0 0 1-1.872-.892.077.077 0 0 1-.008-.128c.126-.094.252-.192.372-.291a.074.074 0 0 1 .078-.01c3.927 1.793 8.18 1.793 12.061 0a.074.074 0 0 1 .079.009c.12.099.246.198.373.292a.077.077 0 0 1-.006.127 12.3 12.3 0 0 1-1.873.891.077.077 0 0 0-.041.107c.36.698.772 1.362 1.225 1.993a.076.076 0 0 0 .084.028 19.84 19.84 0 0 0 6.002-3.03.077.077 0 0 0 .032-.054c.5-5.177-.838-9.674-3.549-13.66a.06.06 0 0 0-.031-.029zM8.02 15.331c-1.182 0-2.157-1.086-2.157-2.419 0-1.333.956-2.419 2.157-2.419 1.21 0 2.176 1.096 2.157 2.42 0 1.332-.956 2.418-2.157 2.418zm7.975 0c-1.183 0-2.157-1.086-2.157-2.419 0-1.333.955-2.419 2.157-2.419 1.21 0 2.176 1.096 2.157 2.42 0 1.332-.946 2.418-2.157 2.418z"/></svg>
</a>
<a class="fab" href="#videos" aria-label="Community videos" title="Community videos">
<svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M23.498 6.186a3.016 3.016 0 0 0-2.122-2.136C19.505 3.545 12 3.545 12 3.545s-7.505 0-9.377.505A3.017 3.017 0 0 0 .502 6.186C0 8.07 0 12 0 12s0 3.93.502 5.814a3.016 3.016 0 0 0 2.122 2.136c1.871.505 9.376.505 9.376.505s7.505 0 9.377-.505a3.015 3.015 0 0 0 2.122-2.136C24 15.93 24 12 24 12s0-3.93-.502-5.814zM9.545 15.568V8.432L15.818 12l-6.273 3.568z"/></svg>
</a>
</div>
<div class="fab-rail right">
<a class="fab" href="https://github.com/ALLFATHER-BV/wadamesh/issues" target="_blank" rel="noopener" aria-label="Report a bug on GitHub" title="Report a bug">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><rect width="8" height="14" x="8" y="6" rx="4"/><path d="m19 7-3 2"/><path d="m5 7 3 2"/><path d="m19 19-3-2"/><path d="m5 19 3-2"/><path d="M20 13h-4"/><path d="M4 13h4"/><path d="m10 4 1 2"/><path d="m14 4-1 2"/></svg>
</a>
<a class="fab" id="docsBtn" href="docs.html" aria-label="Documentation" title="Documentation">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M15 2H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h12a2 2 0 0 0 2-2V7z"/><path d="M14 2v5h5"/><path d="M16 13H8"/><path d="M16 17H8"/><path d="M10 9H8"/></svg>
</a>
<a class="fab" href="https://t413.com/p/projects/MapTileDl/" target="_blank" rel="noopener" aria-label="Map tile downloader" title="Map tile downloader">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M9 18l-6 3V6l6-3 6 3 6-3v15l-6 3-6-3z"/><path d="M9 3v15"/><path d="M15 6v15"/></svg>
</a>
</div>
<div class="toast" id="toast" role="status" aria-live="polite"></div>
<header>
<div class="wrap">
@@ -221,7 +307,7 @@
<span class="byline">by meshcomod</span>
</div>
<p class="lede">A real touchscreen UI for your mesh radio.</p>
<p class="sub">MeshCore MESHCOMOD firmware for the <b>LilyGo&nbsp;T-Deck</b> and <b>Heltec&nbsp;V4</b> — map, chat, channels and contacts on the device itself, <b>and</b> a companion radio for the <b>MeshCore app</b> at the same time.</p>
<p class="sub">MeshCore MESHCOMOD firmware for the <b>LilyGo&nbsp;T-Deck</b>, <b>Heltec&nbsp;V4</b> and <b>Tanmatsu</b> — map, chat, channels and contacts on the device itself, <b>and</b> a companion radio for the <b>MeshCore app</b> at the same time.</p>
<div class="pills">
<span class="pill" tabindex="0"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M9 20l-6-3V4l6 3 6-3 6 3v13l-6-3-6 3z"/><path d="M9 7v13M15 4v13"/></svg>Offline map
<span class="pop"><b>Offline map</b>A real OpenStreetMap you can pan and zoom on the device. Pre-load tile packs to an SD card for fully offline use, or fetch over Wi-Fi — and see your contacts' GPS positions plotted on it.</span></span>
@@ -266,6 +352,12 @@
<button class="back" data-back>← choose a different path</button>
<div class="guide-head"><h3>Standalone install</h3></div>
<p class="p">Plug the device in over USB and flash it right here. Works in <b>Chrome</b> or <b>Edge</b> on desktop.</p>
<div class="chtoggle" role="group" aria-label="Release channel" style="display:inline-flex;margin:14px 0 0;border:1px solid var(--line);border-radius:10px;overflow:hidden">
<button type="button" data-wm-ch="stable" style="font:inherit;font-size:.85rem;font-weight:600;padding:7px 16px;border:0;background:#fff;color:var(--mut);cursor:pointer">Stable</button>
<button type="button" data-wm-ch="beta" style="font:inherit;font-size:.85rem;font-weight:600;padding:7px 16px;border:0;border-left:1px solid var(--line);background:#fff;color:var(--mut);cursor:pointer">Beta · testing</button>
</div>
<p style="margin:12px auto 0;max-width:600px;text-align:left;font-size:.88rem;line-height:1.6"><b>Stable</b> is the tested default. Pick it unless you want to help test. <b>Beta &middot; testing</b> gets new features and fixes earlier, before they are proven, so it can be rough. It is for trying things early and reporting bugs.<br>Already running WADAMESH? You do not have to reflash to switch channels: turn on <b>Settings &rarr; About &rarr; "Get test builds (beta)"</b> on the device and it updates to test builds over Wi-Fi. Switch it off to go back to stable.</p>
<p data-wm-betahint hidden style="margin:8px auto 0;font-size:.84rem;color:#b4631a;max-width:560px">Beta builds are newer and less tested — for trying things early and reporting bugs. On a T-Deck under Launcher you download the .bin and side-load it.</p>
<div data-whatsnew hidden style="margin:18px auto 0;max-width:560px;background:rgba(21,182,166,.07);border:1px solid rgba(21,182,166,.28);border-radius:12px;padding:13px 16px;text-align:left">
<div style="font-weight:600">What's new in <span data-wn-tag style="color:var(--teal)">the latest build</span></div>
<ul data-wn-notes style="margin:7px 0 0;padding-left:18px;font-size:.9rem;color:var(--mut);line-height:1.55"></ul>
@@ -277,10 +369,55 @@
</div>
<div class="boards">
<div class="board"><h4>Heltec V4 + TFT</h4><p>ESP32-S3 with CHSC6x touch.</p>
<esp-web-install-button manifest="https://firmware.wadamesh.com/latest/manifest-heltec-v4-tft.json"></esp-web-install-button></div>
<span class="sup full" tabindex="0"><span class="dot"></span>Fully supported<span class="pop"><b>Fully supported</b>Everything wadamesh offers works here — this is one of the two primary development boards, tested on every release.</span></span>
<esp-web-install-button id="inst-heltec" manifest="https://firmware.wadamesh.com/latest/manifest-heltec-v4-tft.json"></esp-web-install-button>
<a class="dl2" data-dl-board="heltec-v4-tft" download href="https://firmware.wadamesh.com/latest/wadamesh-heltec-v4-tft-merged.bin"><span class="dl2-row"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</span><span class="dlver" data-dl-ver></span></a></div>
<div class="board"><h4>LilyGo T-Deck / Plus</h4><p>ESP32-S3 keyboard handheld.</p>
<esp-web-install-button manifest="https://firmware.wadamesh.com/latest/manifest-tdeck.json"></esp-web-install-button></div>
<span class="sup full" tabindex="0"><span class="dot"></span>Fully supported<span class="pop"><b>Fully supported</b>Everything wadamesh offers works here — this is one of the two primary development boards, tested on every release.</span></span>
<esp-web-install-button id="inst-tdeck" manifest="https://firmware.wadamesh.com/latest/manifest-tdeck.json"></esp-web-install-button>
<a class="dl2" data-dl-board="tdeck" download href="https://firmware.wadamesh.com/latest/wadamesh-tdeck-merged.bin"><span class="dl2-row"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</span><span class="dlver" data-dl-ver></span></a></div>
<div class="board"><h4>ThinkNode M9</h4><p>ESP32-S3 QWERTY handheld (LR1110).</p>
<span class="sup part" tabindex="0"><span class="dot"></span>Partially supported<span class="pop"><b>Partially supported</b>The core works: LoRa mesh communication, chat, contacts, channels and the phone-app link. Not every feature has been ported or hardware-verified on this board yet.</span></span>
<esp-web-install-button id="inst-m9" manifest="https://firmware.wadamesh.com/latest-beta/manifest-thinknode-m9.json"></esp-web-install-button>
<a class="dl2" data-dl-board="thinknode-m9" data-dl-betaonly download href="https://firmware.wadamesh.com/latest-beta/wadamesh-thinknode-m9-merged.bin"><span class="dl2-row"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</span><span class="dlver" data-dl-ver></span></a>
<p data-wm-betaonly style="color:var(--mut);font-size:.78rem;margin:6px 0 0">New board: beta channel only until the next stable.</p></div>
<div class="board"><h4>RAK WisMesh Tap V2</h4><p>ESP32-S3 touch node.</p>
<span class="sup part" tabindex="0"><span class="dot"></span>Partially supported<span class="pop"><b>Partially supported</b>The core works: LoRa mesh communication, chat, contacts, channels and the phone-app link. Not every feature has been ported or hardware-verified on this board yet.</span></span>
<esp-web-install-button id="inst-rak" manifest="https://firmware.wadamesh.com/latest-beta/manifest-rak-tap-v2.json"></esp-web-install-button>
<a class="dl2" data-dl-board="rak-tap-v2" data-dl-betaonly download href="https://firmware.wadamesh.com/latest-beta/wadamesh-rak-tap-v2-merged.bin"><span class="dl2-row"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</span><span class="dlver" data-dl-ver></span></a>
<p data-wm-betaonly style="color:var(--mut);font-size:.78rem;margin:6px 0 0">New board: beta channel only until the next stable.</p></div>
<div class="board"><h4>Heltec V4-R8 <span style="font-weight:600;color:var(--mut)">(experimental)</span></h4><p>ESP32-S3 &middot; 8&nbsp;MB PSRAM &middot; SD card.</p>
<span class="sup part" tabindex="0"><span class="dot"></span>Partially supported<span class="pop"><b>Partially supported</b>The core works: LoRa mesh communication, chat, contacts, channels and the phone-app link. This revision is still being hardware-verified — flash with care and report back.</span></span>
<esp-web-install-button id="inst-v4r8" manifest="https://firmware.wadamesh.com/latest-beta/manifest-heltec-v4-r8-tft.json"></esp-web-install-button>
<a class="dl2" data-dl-board="heltec-v4-r8-tft" data-dl-betaonly download href="https://firmware.wadamesh.com/latest-beta/wadamesh-heltec-v4-r8-tft-merged.bin"><span class="dl2-row"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</span><span class="dlver" data-dl-ver></span></a>
<p data-wm-betaonly style="color:var(--mut);font-size:.78rem;margin:6px 0 0">New board, not yet hardware-tested &mdash; beta only. Please flash with care and report back.</p></div>
<div class="board"><h4>Tanmatsu</h4><p>ESP32-P4 keyboard handheld.</p>
<span class="sup part" tabindex="0"><span class="dot"></span>Partially supported<span class="pop"><b>Partially supported</b>The core works: LoRa mesh communication, chat, contacts, channels and the phone-app link over Wi-Fi/USB. Some features are still settling on this board (Bluetooth pairing has known gaps).</span></span>
<p style="color:var(--mut);font-size:.84rem;margin:0;line-height:1.5">Already have one? No USB flashing needed — install WADAMESH straight from the <b>Tanmatsu app store</b> on the device.</p>
<a class="dl" href="https://shop.nicolaielectronics.nl/" target="_blank" rel="noopener"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M6 2 3 6v14a2 2 0 0 0 2 2h14a2 2 0 0 0 2-2V6l-3-4z"/><path d="M3 6h18"/><path d="M16 10a4 4 0 0 1-8 0"/></svg>Get a Tanmatsu</a></div>
<div class="board"><h4>LilyGo T-Display P4</h4><p>ESP32-P4 AMOLED touch handheld.</p>
<span class="sup part" tabindex="0"><span class="dot"></span>Partially supported<span class="pop"><b>Partially supported</b>Early port — it's known that not everything works yet, but the core does: LoRa mesh communication, chat, map, GPS and the phone-app link over Wi-Fi or USB. Bluetooth pairing isn't available on this board (a hardware limitation of its stock radio firmware).</span></span>
<esp-web-install-button id="inst-tdp4" manifest="https://firmware.wadamesh.com/latest-beta/manifest-tdisplay-p4.json"></esp-web-install-button>
<a class="dl2" data-dl-board="tdisplay-p4" data-dl-betaonly download href="https://firmware.wadamesh.com/latest-beta/wadamesh-tdisplay-p4-merged.bin"><span class="dl2-row"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</span><span class="dlver" data-dl-ver></span></a>
<p data-wm-betaonly style="color:var(--mut);font-size:.78rem;margin:6px 0 0">New board: beta channel only until the next stable.</p></div>
<div class="board"><h4>LilyGo T-LoRa Pager</h4><p>ESP32-S3 QWERTY + rotary encoder.</p>
<span class="sup part" tabindex="0"><span class="dot"></span>Partially supported<span class="pop"><b>Partially supported</b>New community port (thanks @codemonkeybr). The core works: LoRa mesh communication, chat, contacts, channels and the phone-app link, driven entirely by the keyboard and rotary encoder. Pick the build that matches your radio chip.</span></span>
<p style="color:var(--mut);font-size:.8rem;margin:0">Radio <b>LR1121</b>:</p>
<esp-web-install-button id="inst-pager-lr1121" manifest="https://firmware.wadamesh.com/latest-beta/manifest-tlora-pager-lr1121.json"></esp-web-install-button>
<a class="dl2" data-dl-board="tlora-pager-lr1121" data-dl-betaonly download href="https://firmware.wadamesh.com/latest-beta/wadamesh-tlora-pager-lr1121-merged.bin"><span class="dl2-row"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</span><span class="dlver" data-dl-ver></span></a>
<p style="color:var(--mut);font-size:.8rem;margin:8px 0 0">Radio <b>SX1262</b>:</p>
<esp-web-install-button id="inst-pager-sx1262" manifest="https://firmware.wadamesh.com/latest-beta/manifest-tlora-pager-sx1262.json"></esp-web-install-button>
<a class="dl2" data-dl-board="tlora-pager-sx1262" data-dl-betaonly download href="https://firmware.wadamesh.com/latest-beta/wadamesh-tlora-pager-sx1262-merged.bin"><span class="dl2-row"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</span><span class="dlver" data-dl-ver></span></a>
<p data-wm-betaonly style="color:var(--mut);font-size:.78rem;margin:6px 0 0">New board: beta channel only until the next stable.</p></div>
</div>
<details class="verpick">
<summary>Install a previous version</summary>
<div class="verpick-body">
<div class="verpick-row"><label for="verSel">Version</label><select id="verSel" aria-label="Firmware version"></select></div>
<p class="verpick-note" id="verActive" hidden></p>
<div id="verNotes" class="rn"></div>
</div>
</details>
<div class="noserial">Your browser can't flash here — use <b>Chrome</b> or <b>Edge</b> on a desktop.</div>
<p class="hint">T-Deck not detected? Hold the trackball while tapping reset to force download mode.</p>
</div>
@@ -290,6 +427,11 @@
<div class="guide-head"><h3>Install with bmorcelli's Launcher</h3></div>
<p class="p"><a href="https://bmorcelli.github.io/Launcher/" target="_blank" rel="noopener">Launcher</a> is a multi-app boot menu for ESP32 devices — keep it, and run WADAMESH as one of your apps.</p>
<p class="p" style="margin-top:10px"><b>This path is for the LilyGo&nbsp;T-Deck only.</b> On the Heltec&nbsp;V4, install <a href="#standalone" onclick="choose('standalone');return false">Standalone</a> instead.</p>
<div class="chtoggle" role="group" aria-label="Release channel" style="display:inline-flex;margin:14px 0 0;border:1px solid var(--line);border-radius:10px;overflow:hidden">
<button type="button" data-wm-ch="stable" style="font:inherit;font-size:.85rem;font-weight:600;padding:7px 16px;border:0;background:#fff;color:var(--mut);cursor:pointer">Stable</button>
<button type="button" data-wm-ch="beta" style="font:inherit;font-size:.85rem;font-weight:600;padding:7px 16px;border:0;border-left:1px solid var(--line);background:#fff;color:var(--mut);cursor:pointer">Beta · testing</button>
</div>
<p style="margin:8px auto 0;max-width:560px;font-size:.84rem;color:var(--mut)"><b>Stable</b> is the tested default; <b>Beta</b> gets new builds earlier. The download below follows this choice.</p>
<div class="steps" style="margin-top:22px">
<div class="step"><div class="num">1</div><div><h4>Install Launcher first</h4><p>Flash bmorcelli's Launcher to your device, following its own installer — <a href="https://bmorcelli.github.io/Launcher/" target="_blank" rel="noopener">bmorcelli.github.io/Launcher</a>.</p></div></div>
<div class="step"><div class="num">2</div><div><h4>Add the WADAMESH app</h4><p>Grab the WADAMESH <b>app image</b> for your board below, then install it from Launcher (via its web UI / OTA, or copy the <code>.bin</code> to your SD card).</p></div></div>
@@ -297,13 +439,22 @@
</div>
<div class="boards" style="grid-template-columns:1fr; max-width:380px">
<div class="board"><h4>LilyGo T-Deck / Plus</h4><p>app image (no bootloader)</p>
<a class="dl" href="https://firmware.wadamesh.com/latest/wadamesh-tdeck.bin"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</a></div>
<a class="dl" id="dl-tdeck" download href="https://firmware.wadamesh.com/latest/wadamesh-tdeck.bin"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"><path d="M12 3v12M7 11l5 5 5-5M5 21h14"/></svg>Download .bin</a>
<p style="margin:11px 0 0;font-size:.84rem;color:var(--mut);line-height:1.5">You're downloading version <b data-wn-tag style="color:var(--teal)">…</b><span data-wm-chlabel></span>.<br>The file saves as <code data-dl-fname style="font-size:.82em">wadamesh-tdeck.bin</code> — rename it if you keep several.</p></div>
</div>
<p class="hint">New to Launcher? It's the easiest way to try WADAMESH without giving up your other firmware — and you can fully switch to Standalone any time.</p>
</div>
</div>
</section>
<section id="videos">
<div class="wrap">
<h2 class="h2">Community videos</h2>
<p class="p">Walkthroughs, demos and reviews from the community.</p>
<div class="vids" id="vids"></div>
</div>
</section>
<footer>
<div class="wrap">
Built for the mesh · open source under GPL-3.0 ·
@@ -404,21 +555,153 @@ We use no tracking, analytics, or advertising cookies. Our CDN and security prov
try { if (!localStorage.getItem('wm-cookie-ack')) cbar.classList.add('show'); } catch(_) {}
document.getElementById('cookieok').addEventListener('click', () => { cbar.classList.remove('show'); try { localStorage.setItem('wm-cookie-ack','1'); } catch(_) {} });
// ---- donate banner: dismissible; shifts the corner FABs down while shown ----
(function(){
const bar = document.getElementById('donateBar'); if (!bar) return;
function setFabTop(){ document.documentElement.style.setProperty('--fab-top', (getComputedStyle(bar).display === 'none' ? 16 : bar.offsetHeight + 12) + 'px'); }
try { if (localStorage.getItem('wm-donate-dismiss') === '1') bar.style.display = 'none'; } catch(_) {}
setFabTop();
addEventListener('resize', setFabTop);
document.getElementById('donateX').addEventListener('click', () => { bar.style.display = 'none'; setFabTop(); try { localStorage.setItem('wm-donate-dismiss','1'); } catch(_) {} });
})();
// Live release version + "what's new" — read from the firmware host so the
// flasher always reflects the current build (the release pipeline updates
// version.json; no site redeploy needed per release).
fetch('https://firmware.wadamesh.com/latest/version.json', {cache:'no-store'})
.then(r => r.ok ? r.json() : null)
.then(v => {
if (!v || !v.tag) return;
document.querySelectorAll('[data-wn-tag]').forEach(e => e.textContent = v.tag);
const notes = Array.isArray(v.notes) ? v.notes : [];
document.querySelectorAll('[data-wn-notes]').forEach(ul => {
ul.innerHTML = '';
notes.forEach(n => { const li = document.createElement('li'); li.textContent = n; ul.appendChild(li); });
});
if (notes.length) document.querySelectorAll('[data-whatsnew]').forEach(b => b.hidden = false);
}).catch(()=>{});
// Release channel (Stable default / Beta testing). The toggle swaps the feed dir
// on the firmware host — latest/ (stable) <-> latest-beta/ (beta) — and the install
// manifests, "what's new", the Launcher .bin link and the version picker follow.
const WM = (window.WM = { feed:'latest', arch:'TOUCH' });
// ThinkNode M9 + RAK Tap V2 exist on the BETA feed only until the first stable
// promote that includes them: their install buttons are pinned to latest-beta in
// the HTML and deliberately NOT switched by wmSetChannel. When a stable ships
// with their bins, add them here + to wmSetChannel and drop the pinned notes.
const WM_MAN = { heltec:'manifest-heltec-v4-tft.json', tdeck:'manifest-tdeck.json' };
window.wmManifest = board => 'https://firmware.wadamesh.com/' + WM.feed + '/' + WM_MAN[board];
function wmWhatsNew(){
const wn = document.querySelectorAll('[data-whatsnew]');
fetch('https://firmware.wadamesh.com/' + WM.feed + '/version.json', {cache:'no-store'})
.then(r => r.ok ? r.json() : null)
.then(v => {
if (!v || !v.tag) { wn.forEach(b => b.hidden = true); return; }
document.querySelectorAll('[data-wn-tag]').forEach(e => e.textContent = v.tag);
const notes = Array.isArray(v.notes) ? v.notes : [];
document.querySelectorAll('[data-wn-notes]').forEach(ul => {
ul.innerHTML = '';
notes.forEach(n => { const li = document.createElement('li'); li.textContent = n; ul.appendChild(li); });
});
wn.forEach(b => b.hidden = !notes.length);
}).catch(() => { wn.forEach(b => b.hidden = true); });
}
window.wmSetChannel = function(ch){
WM.feed = ch === 'beta' ? 'latest-beta' : 'latest';
WM.arch = ch === 'beta' ? 'BETA' : 'TOUCH';
const bH = document.getElementById('inst-heltec'), bT = document.getElementById('inst-tdeck');
if (bH) bH.setAttribute('manifest', wmManifest('heltec'));
if (bT) bT.setAttribute('manifest', wmManifest('tdeck'));
const dl = document.getElementById('dl-tdeck');
if (dl) dl.href = 'https://firmware.wadamesh.com/' + WM.feed + '/wadamesh-tdeck.bin';
document.querySelectorAll('[data-wm-chlabel]').forEach(e => e.textContent = ch === 'beta' ? ' · beta (testing)' : ' · stable');
document.querySelectorAll('[data-wm-ch]').forEach(b => { const on = b.getAttribute('data-wm-ch') === ch;
b.style.background = on ? 'var(--teal)' : '#fff'; b.style.color = on ? '#fff' : 'var(--mut)'; });
document.querySelectorAll('[data-wm-betahint]').forEach(e => e.hidden = ch !== 'beta');
const vs = document.getElementById('verSel');
if (vs && vs.options.length) { vs.selectedIndex = 0; vs.dispatchEvent(new Event('change')); }
wmUpdateDownloads();
wmWhatsNew();
};
// Per-board "download the .bin" links on the standalone cards: follow the channel
// toggle (beta-only boards stay pinned to latest-beta) and show the exact version
// each feed serves — both channel tags are fetched once so every link is accurate.
const WM_VER = {};
window.wmUpdateDownloads = function(){
document.querySelectorAll('[data-dl-board]').forEach(a => {
const feed = a.hasAttribute('data-dl-betaonly') ? 'latest-beta' : WM.feed;
a.href = 'https://firmware.wadamesh.com/' + feed + '/wadamesh-' + a.getAttribute('data-dl-board') + '-merged.bin';
const v = a.querySelector('[data-dl-ver]'); if (v) v.textContent = WM_VER[feed] || '';
});
};
['latest','latest-beta'].forEach(feed => fetch('https://firmware.wadamesh.com/' + feed + '/version.json', {cache:'no-store'})
.then(r => r.ok ? r.json() : null).then(v => { if (v && v.tag) { WM_VER[feed] = v.tag; wmUpdateDownloads(); } }).catch(()=>{}));
document.querySelectorAll('[data-wm-ch]').forEach(b => b.addEventListener('click', () => wmSetChannel(b.getAttribute('data-wm-ch'))));
wmSetChannel('stable');
// ---- community videos — add an entry here to add a video ----
const VIDEOS = [
// newest first
{ id: 's-8pRsC0TYA', title: 'WadaMesh: The Feature That Makes T-Deck Plus Stand Out', by: 'BFGNeil' },
{ id: 'V19od8jbFRc', title: 'WadaMesh: The Best T-Deck Firmware So Far', by: 'KDHD Stuff' },
// { id: '<youtube-id>', title: '<title>', by: '<channel>' },
];
const vidsEl = document.getElementById('vids');
if (vidsEl) VIDEOS.forEach(v => {
const card = document.createElement('div'); card.className = 'vid';
const btn = document.createElement('button'); btn.type = 'button'; btn.className = 'vid-thumb';
btn.setAttribute('aria-label', 'Play: ' + (v.title || 'community video'));
btn.style.backgroundImage = 'url(https://i.ytimg.com/vi/' + v.id + '/hqdefault.jpg)';
btn.innerHTML = '<span class="play"><svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M8 5v14l11-7z"/></svg></span>';
btn.addEventListener('click', () => {
const f = document.createElement('iframe'); f.className = 'vid-embed';
f.src = 'https://www.youtube-nocookie.com/embed/' + v.id + '?autoplay=1&rel=0';
f.title = v.title || 'Community video';
f.allow = 'accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture';
f.allowFullscreen = true; f.loading = 'lazy';
card.replaceChild(f, btn);
});
card.appendChild(btn);
if (v.title) {
const cap = document.createElement('div'); cap.className = 'vid-cap'; cap.textContent = v.title;
if (v.by) { const s = document.createElement('span'); s.textContent = 'by ' + v.by; cap.appendChild(s); }
card.appendChild(cap);
}
vidsEl.appendChild(card);
});
// ---- toast + docs placeholder ----
function toast(msg){ const t = document.getElementById('toast'); if (!t) return; t.textContent = msg; t.classList.add('show'); clearTimeout(t._t); t._t = setTimeout(() => t.classList.remove('show'), 2400); }
// The documentation button is a plain link to docs.html (no handler needed).
// ---- standalone: install a previous version (latest 4 betas + release notes) ----
(function(){
const sel = document.getElementById('verSel'); if (!sel) return;
const wrap = sel.closest('.verpick');
const notesEl = document.getElementById('verNotes'), activeEl = document.getElementById('verActive');
const btnH = document.getElementById('inst-heltec'), btnT = document.getElementById('inst-tdeck');
const latestH = () => window.wmManifest('heltec'), latestT = () => window.wmManifest('tdeck');
const num = t => parseInt((String(t).match(/beta_(\d+)/) || [])[1] || '-1', 10);
let notes = {};
const esc = s => s.replace(/&/g,'&amp;').replace(/</g,'&lt;').replace(/>/g,'&gt;');
const inl = s => esc(s).replace(/\*\*(.+?)\*\*/g,'<b>$1</b>').replace(/`([^`]+?)`/g,'<code>$1</code>')
.replace(/\[(.+?)\]\((https?:\/\/[^)\s]+)\)/g,'<a href="$2" target="_blank" rel="noopener">$1</a>');
function md(t){ let out='', ul=false; const close=()=>{ if(ul){ out+='</ul>'; ul=false; } };
(t||'').split(/\r?\n/).forEach(line=>{ line=line.trim(); let m;
if(!line) close();
else if(m=line.match(/^#{1,6}\s+(.*)/)){ close(); out+='<div class="rn-h">'+inl(m[1])+'</div>'; }
else if(m=line.match(/^[-*]\s+(.*)/)){ if(!ul){ out+='<ul>'; ul=true; } out+='<li>'+inl(m[1])+'</li>'; }
else { close(); out+='<p>'+inl(line)+'</p>'; } });
close(); return out; }
function showNotes(tag){ notesEl.innerHTML = notes[tag] ? md(notes[tag])
: '<p>Release notes on <a href="https://github.com/ALLFATHER-BV/wadamesh/releases/tag/'+tag+'" target="_blank" rel="noopener">GitHub</a>.</p>'; }
function blobManifest(tag, board){ const m = { name:'wadamesh '+tag, version:tag, new_install_prompt_erase:true,
builds:[{ chipFamily:'ESP32-S3', parts:[{ path:'https://firmware.wadamesh.com/releases/'+((window.WM&&window.WM.arch)||'TOUCH')+'/'+tag+'/wadamesh-'+board+'-merged.bin', offset:0 }] }] };
return URL.createObjectURL(new Blob([JSON.stringify(m)], {type:'application/json'})); }
function apply(){ const tag = sel.value, isLatest = sel.selectedIndex === 0;
if (isLatest){ if(btnH) btnH.setAttribute('manifest', latestH()); if(btnT) btnT.setAttribute('manifest', latestT()); activeEl.hidden = true; }
else { if(btnH) btnH.setAttribute('manifest', blobManifest(tag,'heltec-v4-tft')); if(btnT) btnT.setAttribute('manifest', blobManifest(tag,'tdeck'));
activeEl.hidden = false; activeEl.innerHTML = 'The <b>Install</b> buttons above now flash <b>'+tag+'</b>.'; }
showNotes(tag); }
// GitHub API gives version list + notes in one CORS-enabled call (the firmware
// host listing has no CORS); bins are still pulled from the firmware host.
fetch('https://api.github.com/repos/ALLFATHER-BV/wadamesh/releases?per_page=12').then(r=>r.ok?r.json():[]).then(rs=>{
const rels = (Array.isArray(rs)?rs:[]).filter(r=>r&&/^beta_\d+$/.test(r.tag_name||''));
rels.forEach(r=>{ notes[r.tag_name]=r.body||''; });
const tags = rels.map(r=>r.tag_name).sort((a,b)=>num(b)-num(a)).slice(0,4);
if (!tags.length){ if(wrap) wrap.hidden = true; return; }
sel.innerHTML = tags.map((t,i)=>'<option value="'+t+'">'+t+(i===0?' — latest':'')+'</option>').join('');
showNotes(tags[0]);
sel.addEventListener('change', apply);
}).catch(()=>{ if(wrap) wrap.hidden = true; });
})();
</script>
@@ -0,0 +1,44 @@
# WadaMesh
A full **[MeshCore](https://github.com/meshcore-dev/MeshCore)** client for the Tanmatsu.
It runs the LoRa mesh, Wi-Fi and Bluetooth radios **all at the same time**, so the device
works as a complete standalone communicator *and* as a phone companion at once — no
mode-switching, no rebooting to swap radios.
MeshCore is an encrypted, infrastructure-free LoRa mesh network — messages hop from device
to device with no cell tower, Wi-Fi or internet in between. WadaMesh gives it a full
graphical front-end on the Tanmatsu's own screen and keyboard.
## Why WadaMesh
- **Multi-radio, simultaneously.** LoRa, Wi-Fi and Bluetooth all live at once. Chat on the
mesh while Wi-Fi streams map tiles and a phone stays paired over Bluetooth — concurrently.
- **Standalone *and* companion at the same time.** A complete client on its own screen and
keyboard, while a phone app can connect over Bluetooth or Wi-Fi in parallel. You don't
have to pick a role.
- **Live mesh map.** Plot yourself and your contacts on a real OpenStreetMap from their
shared GPS positions (tiles fetched and cached over Wi-Fi).
- **Built for the keyboard.** Arrow-key navigation, type-to-edit and function-key shortcuts —
designed around the Tanmatsu's hardware, not bolted on from a touchscreen.
- **Polished and localised.** Full-colour emoji and 11 interface languages.
## Features
- **Messaging** — direct messages and channels with unread markers, a "new messages"
divider and quick replies.
- **Contacts & map** — contact list with live signal and distance, plus the mesh map.
- **Radio control** — frequency / spreading factor / bandwidth / TX power, and GPS.
- **Connectivity** — LoRa, Wi-Fi and Bluetooth at once; use it standalone or as a Wi-Fi +
Bluetooth companion for a phone.
## Links
- Source & releases: <https://github.com/ALLFATHER-BV/wadamesh>
- Web flasher & project info: <https://wadamesh.com>
## Licence
WadaMesh is distributed under **GPL-3.0** — see [LICENSE](LICENSE). It incorporates
[MeshCore](https://github.com/meshcore-dev/MeshCore) (MIT, © Scott Powell /
rippleradios.com); MeshCore-derived files keep their MIT notices, and the combined
work is GPL (MIT is GPL-compatible). See [NOTICE](NOTICE) for third-party licenses.
Binary file not shown.

After

Width:  |  Height:  |  Size: 604 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.0 KiB

@@ -0,0 +1,30 @@
{
"name": "WadaMesh",
"description": "MeshCore client running LoRa Wi-Fi & Bluetooth at once. A standalone unit and phone companion in one.",
"categories": [
"tools",
"utils",
"hardware"
],
"version": "1.0.0",
"icon": {
"16x16": "icon16.png",
"32x32": "icon32.png",
"64x64": "icon64.png"
},
"author": "Kaj Schittecat - ALLFATHER BV",
"license_type": "GPL-3.0",
"license_file": "LICENSE",
"application": [
{
"targets": [
"tanmatsu",
"konsool"
],
"revision": 1,
"type": "appfs",
"executable": "wadamesh.bin",
"assets": []
}
]
}
+36 -11
View File
@@ -39,8 +39,17 @@ except ImportError:
sys.exit("ERROR: pip install flask pillow requests")
OSM_URL = "https://tile.openstreetmap.org/{z}/{x}/{y}.png"
# OSM tile policy: identify yourself with a contactable UA. This is what OSM
# sees — the device never talks to OSM directly.
# OpenTopoMap (topographic / terrain-relief style) — an OPT-IN alternate style.
# The firmware default stays OpenStreetMap; the device only requests /opentopo/
# when the user enables it. Like OSM it serves PNG, so it goes through the same
# fetch+transcode path. Legal: map style © OpenTopoMap (CC-BY-SA), underlying
# data © OpenStreetMap contributors (ODbL) + SRTM — the touch UI shows that
# attribution whenever topo is the selected style. OpenTopoMap's tile-usage
# policy asks for a contactable User-Agent + caching; nginx caches results 14
# days so each unique tile hits OpenTopoMap at most once per fortnight.
OPENTOPO_URL = "https://tile.opentopomap.org/{z}/{x}/{y}.png"
# Tile policy: identify yourself with a contactable UA. This is what the upstream
# tile servers see — the device never talks to them directly.
OSM_UA = "wadamesh-tile-proxy/1.0 (+https://wadamesh.com)"
JPEG_QUALITY = 80 # slippy tiles compress well; 80 ≈ visually lossless
MAX_TILE_BYTES = 256 * 1024
@@ -57,40 +66,56 @@ _session = requests.Session()
_session.headers.update({"User-Agent": OSM_UA, "Accept": "image/png,image/*"})
@app.get("/<int:z>/<int:x>/<int:y>.jpg")
def tile(z: int, x: int, y: int):
# Range-check before touching OSM so we can't be turned into an open proxy.
def _fetch_tile_png(upstream_url: str, z: int, x: int, y: int) -> bytes:
# Range-check before touching the upstream so we can't be turned into an open proxy.
if not (0 <= z <= 19):
abort(404)
n = 1 << z
if not (0 <= x < n and 0 <= y < n):
abort(404)
try:
r = _session.get(OSM_URL.format(z=z, x=x, y=y), timeout=REQUEST_TIMEOUT,
r = _session.get(upstream_url.format(z=z, x=x, y=y), timeout=REQUEST_TIMEOUT,
stream=True)
except requests.RequestException:
abort(502)
if r.status_code != 200:
# Pass OSM's status through (404 = empty/sea tile — nginx caches it).
# Pass the upstream status through (404 = empty/sea tile — nginx caches it).
abort(r.status_code if r.status_code in (404, 429) else 502)
raw = r.raw.read(MAX_TILE_BYTES + 1, decode_content=True)
if len(raw) > MAX_TILE_BYTES:
abort(502)
return raw
def _tile_response_from_png(raw: bytes) -> Response:
try:
img = Image.open(io.BytesIO(raw)).convert("RGB")
out = io.BytesIO()
img.save(out, "JPEG", quality=JPEG_QUALITY, optimize=True)
except Exception:
abort(502)
return Response(out.getvalue(), mimetype="image/jpeg",
headers={"Cache-Control": "public, max-age=2592000"})
# Default path the firmware uses → OpenStreetMap (the shipping default style).
@app.get("/<int:z>/<int:x>/<int:y>.jpg")
def tile(z: int, x: int, y: int):
return _tile_response_from_png(_fetch_tile_png(OSM_URL, z, x, y))
# Explicit OpenStreetMap alias (identical to the root path).
@app.get("/osm/<int:z>/<int:x>/<int:y>.jpg")
def tile_osm(z: int, x: int, y: int):
return _tile_response_from_png(_fetch_tile_png(OSM_URL, z, x, y))
# OpenTopoMap (topographic) — opt-in alternate style selected on the device.
@app.get("/opentopo/<int:z>/<int:x>/<int:y>.jpg")
def tile_opentopo(z: int, x: int, y: int):
return _tile_response_from_png(_fetch_tile_png(OPENTOPO_URL, z, x, y))
@app.get("/elev")
def elev():
"""Elevation profile for the line-of-sight analyzer.
+10 -4
View File
@@ -3,6 +3,10 @@
#define LV_COLOR_DEPTH 16
#define LV_COLOR_16_SWAP 0
// NOTE: LV_USE_LARGE_COORD is intentionally OFF — enabling it caused a boot-time
// LoadProhibited in LVGL on the T-Deck. Chat scroll heights >8191 px are handled
// in UITask via int32 layout offsets + compressed LVGL scroll coords.
// Route LVGL's general allocator through PSRAM-preferred wrappers (defined in
// LvglPsramAlloc.cpp). The board has 8 MB of PSRAM and the ~60 KB of widget
// state LVGL grows during buildUiTree would otherwise come out of the 320 KB
@@ -48,10 +52,11 @@
#define LV_FONT_MONTSERRAT_12 1
#define LV_FONT_MONTSERRAT_14 1
#define LV_FONT_MONTSERRAT_16 1
/* Larger Montserrat sizes for the Tanmatsu's crisp "UI size" (Large/Huge) — render the UI bigger
* at native resolution instead of upscaling a low-res frame. Gated to the Tanmatsu so the
* flash-tighter S3 touch builds don't pay for fonts they never use. */
#if defined(HAS_TANMATSU)
/* Larger Montserrat sizes for the large-screen boards' crisp "UI size" (Large/Huge) — render the
* UI bigger at native resolution instead of upscaling a low-res frame. Gated to the CAP_LARGE_SCREEN
* P4 boards (Tanmatsu + T-Display P4) so the flash-tighter S3 touch builds don't pay for fonts they
* never use. (device_caps.h isn't included here, so match on the board macros directly.) */
#if defined(HAS_TANMATSU) || defined(HAS_TDISPLAY_P4)
#define LV_FONT_MONTSERRAT_18 1
#define LV_FONT_MONTSERRAT_20 1
#define LV_FONT_MONTSERRAT_24 1
@@ -108,6 +113,7 @@
* render full-colour emoji inline with text. The emoji set is pre-baked to
* RGB565+alpha lv_img_dsc_t C-arrays (emoji_data.c) and wired as the tail of the
* font fallback chain in UITask (montserrat -> extras -> emoji). */
#define LV_USE_FONT_COMPRESSED 1 /* decode RLE-compressed extras/accent fonts (Tanmatsu size budget) */
#define LV_USE_IMGFONT 1
/* Bi-directional text + Arabic/Persian contextual shaping. Lets Arabic (and
+932 -4
View File
@@ -7,6 +7,7 @@
default_envs =
heltec_v4_tft_companion_radio_usb_tcp_touch
LilyGo_TDeck_companion_radio_touch
ThinkNode_M9_companion_radio_touch
[env:heltec_v4_tft_companion_radio_usb_tcp_touch]
platform = platformio/espressif32@6.11.0
@@ -17,7 +18,7 @@ board_build.partitions = partitions_tft_touch.csv
extra_scripts = pre:scripts/inject_wifi_env.py, merge-bin.py
build_flags =
-w -DNDEBUG -DRADIOLIB_STATIC_ONLY=1 -DRADIOLIB_GODMODE=1
-Wno-deprecated-declarations -Wno-unused-parameter -DNDEBUG -DRADIOLIB_STATIC_ONLY=1 -DRADIOLIB_GODMODE=1
-D MC_VENDORED_TOUCH_APP
; NOTE: tried -D ARDUINO_USB_MODE=1 (HW-CDC, drops unused TinyUSB MSC/DFU ≈ 12 KB internal
; DRAM) — but on the real V4 the binary companion link regressed: small per-message frames
@@ -127,6 +128,9 @@ build_flags =
-I src/ui-touch
-D UI_LVGL=1
-D HAS_TOUCH_UI=1
; Heltec V4 Expansion Kit: local environment sensors UI (Sensors tab, Home env
; widget, Local-Sensors page). Board-gated — only this env compiles it.
-D HAS_EXPANSION_KIT=1
-D FIRMWARE_OTA_ENV='"heltec_v4_tft_companion_radio_usb_tcp_touch"'
-D ENABLE_ADVERT_ON_BOOT=0
-D LV_CONF_PATH=lv_conf.h
@@ -164,6 +168,7 @@ build_flags =
build_src_filter =
+<*.cpp>
+<*.c>
+<helpers/*.cpp>
+<helpers/esp32/*.cpp>
+<helpers/input/*.cpp>
@@ -175,7 +180,7 @@ lib_deps =
; MeshCore core = the meshcomod monorepo built as a lib, pinned by tag.
; Touch-app files (TouchPrefsStore, WifiRuntimeStore, transports, ...) are
; vendored in this app's src/ and dropped from the lib via -DMC_VENDORED_TOUCH_APP.
https://github.com/ALLFATHER-BV/meshcomod.git#core-v1.16.4
https://github.com/ALLFATHER-BV/meshcomod.git#core-v1.16.5
SPI
Wire
jgromes/RadioLib @ ^7.6.0
@@ -206,6 +211,72 @@ lib_deps =
lvgl/lvgl @ ^8.3.11
bodmer/TFT_eSPI @ ^2.5.43
densaugeo/base64 @ ~1.4.0
knolleary/PubSubClient @ ^2.8.0
; ======================================================================
; Heltec WiFi LoRa 32 V4-R8 (ESP32-S3R8, 8 MB OCTAL PSRAM) + Expansion Kit V2.
; Inherits the V4 TFT env and overrides ONLY the R8 deltas. The 8 MB octal PSRAM
; claims GPIO33-37, so Heltec moved every control signal off them and the V2
; expansion put the TFT on a hardware-SPI bus SHARED with a new micro-SD slot:
; Vext 36->40 (now active-LOW) · GPS_EN 34->42 · LED 35->46 · ADC_Ctrl removed
; TFT (LovyanGFX HW-SPI): MOSI=15 SCK=16 MISO=45 CS=47 DC=48 RST=21 BL=44
; touch (CHSC6x, shares board I2C on 17/18) · micro-SD (shared TFT SPI, CS=3)
; The build defines HELTEC_LORA_V4_TFT too, so it reuses ALL the V4 touch-UI code;
; HELTEC_LORA_V4_R8 gates only the deltas. USB stays TinyUSB-CDC (USB_MODE=0) like
; the V4 — HW-CDC regresses the companion link on this family (see the V4 note).
; UNTESTED (no hardware yet) — pin sources: Meshtastic heltec_v4_r8 variant +
; Heltec V4-R8 pinmap + Expansion_board_V2.03 schematic. On-device TODO: confirm
; the CHSC6x shares Wire on 17/18, the SD_CS=3 read, and the V2 PAM8904 buzzer.
; ======================================================================
[env:heltec_v4_r8_tft_companion_radio_usb_tcp_touch]
extends = env:heltec_v4_tft_companion_radio_usb_tcp_touch
board = heltec_v4_r8
build_flags =
${env:heltec_v4_tft_companion_radio_usb_tcp_touch.build_flags}
; --- V4-R8 deltas (later -D wins on the GCC command line) ---
-D HELTEC_LORA_V4_R8
-D P_LORA_TX_LED=46
-D PIN_VEXT_EN=40
-D PIN_VEXT_EN_ACTIVE=LOW
-D PIN_GPS_EN=42
-D PIN_GPS_RESET=-1
-D PIN_ADC_CTRL=-1
-D ADC_MULTIPLIER=5.07
; TFT on hardware SPI (LovyanGFX), shared with the micro-SD
-D DISPLAY_CLASS=LGFXDisplay
-D PIN_TFT_RST=21
-D PIN_TFT_LEDA_CTL=44
-D PIN_TFT_CS=47
-D PIN_TFT_DC=48
-D PIN_TFT_SCL=16
-D PIN_TFT_SDA=15
-D PIN_TFT_MISO=45
; TFT_eSPI mirror (kept in sync though LovyanGFX drives the panel)
-D TFT_MOSI=15
-D TFT_SCLK=16
-D TFT_MISO=45
-D TFT_CS=47
-D TFT_DC=48
-D TFT_RST=21
-D TFT_BL=44
; touch (CHSC6x) + board I2C unified on GPIO17/18; micro-SD chip-select
-D PIN_TOUCH_SDA=17
-D PIN_TOUCH_SCL=18
; RST=-1 ON PURPOSE (tester repro fix): the Expansion V2 wires the CHSC6x reset to GPIO21 — the
; SAME line as the ST7789 reset. The chsc6x driver hard-pulses its RST at init (+3 retry sites),
; which RESET the LCD mid-boot and wiped its init: logo OK -> screen black -> white/garbled rows
; on any redraw. The LGFX display init already resets both chips via pin 21; the touch driver must
; never drive it (-1 = every pulse in chsc6x_platform no-ops).
-D PIN_TOUCH_RST=-1
-D PIN_TOUCH_INT=43
-D PIN_BOARD_SDA=17
-D PIN_BOARD_SCL=18
-D PIN_SD_CS=3
-D HELTEC_V4_BUZZER_PIN=-1
-D FIRMWARE_OTA_ENV='"heltec_v4_r8_tft_companion_radio_usb_tcp_touch"'
lib_deps =
${env:heltec_v4_tft_companion_radio_usb_tcp_touch.lib_deps}
lovyan03/LovyanGFX@1.2.21
; ======================================================================
; LilyGo T-Deck / T-Deck Plus — flattened equivalent of meshcomod's
@@ -221,7 +292,7 @@ board_build.partitions = variants/lilygo_tdeck/partitions_tdeck_touch.csv
extra_scripts = pre:scripts/inject_wifi_env.py, merge-bin.py
build_flags =
-w -DNDEBUG -DRADIOLIB_STATIC_ONLY=1 -DRADIOLIB_GODMODE=1
-Wno-deprecated-declarations -Wno-unused-parameter -DNDEBUG -DRADIOLIB_STATIC_ONLY=1 -DRADIOLIB_GODMODE=1
-D MC_VENDORED_TOUCH_APP
-D LORA_FREQ=869.618
-D LORA_BW=62.5
@@ -337,6 +408,7 @@ build_flags =
build_src_filter =
+<*.cpp>
+<*.c>
+<helpers/*.cpp>
+<helpers/esp32/*.cpp>
+<helpers/input/*.cpp>
@@ -345,7 +417,7 @@ build_src_filter =
+<../variants/lilygo_tdeck/*.cpp>
lib_deps =
https://github.com/ALLFATHER-BV/meshcomod.git#core-v1.16.4
https://github.com/ALLFATHER-BV/meshcomod.git#core-v1.16.5
SPI
Wire
jgromes/RadioLib @ ^7.6.0
@@ -374,3 +446,859 @@ lib_deps =
file://arch/esp32/AsyncElegantOTA
lvgl/lvgl @ ^8.3.11
densaugeo/base64 @ ~1.4.0
knolleary/PubSubClient @ ^2.8.0
[env:tlora_pager_lr1121_companion_radio_touch]
platform = platformio/espressif32@6.11.0
framework = arduino
board = lilygo-t-lora-pager
monitor_speed = 115200
board_build.partitions = variants/lilygo_tlora_pager/partitions_tlora_pager_touch.csv
extra_scripts = pre:scripts/inject_wifi_env.py, merge-bin.py
build_flags =
-Wno-deprecated-declarations -Wno-unused-parameter -DNDEBUG -DRADIOLIB_STATIC_ONLY=1 -DRADIOLIB_GODMODE=1
-D MC_VENDORED_TOUCH_APP
-D LORA_FREQ=869.618
-D LORA_BW=62.5
-D LORA_SF=8
-D ENABLE_PRIVATE_KEY_IMPORT=1
-D ENABLE_PRIVATE_KEY_EXPORT=1
-D RADIOLIB_EXCLUDE_CC1101=1
-D RADIOLIB_EXCLUDE_RF69=1
-D RADIOLIB_EXCLUDE_SX1231=1
-D RADIOLIB_EXCLUDE_SI443X=1
-D RADIOLIB_EXCLUDE_RFM2X=1
-D RADIOLIB_EXCLUDE_SX128X=1
-D RADIOLIB_EXCLUDE_AFSK=1
-D RADIOLIB_EXCLUDE_AX25=1
-D RADIOLIB_EXCLUDE_HELLSCHREIBER=1
-D RADIOLIB_EXCLUDE_MORSE=1
-D RADIOLIB_EXCLUDE_APRS=1
-D RADIOLIB_EXCLUDE_BELL=1
-D RADIOLIB_EXCLUDE_RTTY=1
-D RADIOLIB_EXCLUDE_SSTV=1
; LR11X0 stays IN (that's our radio family); SX126X isn't used by this env at all.
-D RADIOLIB_EXCLUDE_SX126X=1
-D ESP32_PLATFORM
; --- T-LoRa Pager board ---
-I variants/lilygo_tlora_pager
-D TLORA_PAGER=1
-D BOARD_HAS_PSRAM=1
; 0 = silence ARDUHAL [E] spam, same rationale as the other two envs.
-D CORE_DEBUG_LEVEL=0
-D ARDUINO_USB_CDC_ON_BOOT=1
-D PIN_USER_BTN=0
-D USE_LR1121=1
-D RADIO_CLASS=CustomLR1121
-D WRAPPER_CLASS=CustomLR1121Wrapper
; Full sub-GHz HP-PA power on boot, matching the T-Deck's own LORA_TX_POWER=22
; (not Heltec V4's conservative-10-then-raise-in-Settings pattern). +22dBm is
; this chip's real ceiling for freq < 1GHz -- confirmed against RadioLib's
; pinned LR1120::checkOutputPower() (LR1121 inherits it: HP PA auto-selects
; above 14dBm, valid range -9..22) and trail-mate's own
; TRAIL_MATE_LORA_TX_POWER_MAX_DBM=22 for this exact board -- not a guess
; carried over from the sibling boards. A weak default here (10dBm, ~16x less
; power) was silently degrading outbound range on real hardware: adverts/DMs
; sent FROM the pager were unreliable while inbound reception was fine, since
; the far node's own TX was unaffected.
-D LORA_TX_POWER=22
-D P_LORA_DIO_1=14
-D P_LORA_NSS=36
-D P_LORA_RESET=47
-D P_LORA_BUSY=48
-D P_LORA_SCLK=35
-D P_LORA_MISO=33
-D P_LORA_MOSI=34
-D ENV_INCLUDE_GPS=1
-D ENV_SKIP_GPS_DETECT=1
-D ENV_INCLUDE_AHTX0=0
-D ENV_INCLUDE_BME280=0
-D ENV_INCLUDE_BMP280=0
-D ENV_INCLUDE_SHTC3=0
-D ENV_INCLUDE_SHT4X=0
-D ENV_INCLUDE_LPS22HB=0
-D ENV_INCLUDE_INA3221=0
-D ENV_INCLUDE_INA219=0
-D ENV_INCLUDE_INA226=0
-D ENV_INCLUDE_INA260=0
-D ENV_INCLUDE_MLX90614=0
-D ENV_INCLUDE_VL53L0X=0
-D ENV_INCLUDE_BME680=0
-D ENV_INCLUDE_BMP085=0
-D DISPLAY_SCALE_X=1.0
-D DISPLAY_SCALE_Y=1.0
; AW9364 backlight enable/pulse pin (ST7796LCDDisplay owns brightness -- see
; the CGRAM_OFFSET comment below for why this isn't a plain PWM pin).
-D PIN_TFT_LEDA_CTL=42
; Swapped vs. trail-mate's raw GPS_RX=4/GPS_TX=12: wadamesh's core calls
; Serial1.setPins(PIN_GPS_TX, PIN_GPS_RX), and HardwareSerial::setPins()
; takes (rxPin, txPin) -- so PIN_GPS_TX must be the ESP's own RX pin (4) and
; PIN_GPS_RX the ESP's own TX pin (12). See TLORA_PAGER_PORT.md Risk 1c.
-D PIN_GPS_RX=12
-D PIN_GPS_TX=4
-D GPS_BAUD_RATE=38400
; --- touch UI / companion stack ---
-I include
-I src
-I src/ui-touch
-D UI_LVGL=1
-D HAS_TOUCH_UI=1
-D FIRMWARE_OTA_ENV='"tlora_pager_lr1121_companion_radio_touch"'
-D HAS_PAGER_KEYBOARD=1
-D HAS_PAGER_ENCODER=1
-D KB_INT=6
-D KB_BACKLIGHT=46
-D ROTARY_A=40
-D ROTARY_B=41
-D ROTARY_C=7
; ES8311 codec I2S pins (NS4150B amp downstream, enabled via XL9555
; AMP_EN -- see TLoraPagerBoard::setAmpEnabled()). Confirmed against the
; canonical arduino-esp32 pins_arduino.h for this board -- see
; TLORA_PAGER_PORT.md's Audio row.
-D PIN_I2S_MCLK=10
-D PIN_I2S_BCK=11
-D PIN_I2S_WS=18
-D PIN_I2S_DOUT=45
-D PIN_I2S_SDIN=17
-D ENABLE_ADVERT_ON_BOOT=0
-D LV_CONF_PATH=lv_conf.h
-D LV_CONF_INCLUDE_SIMPLE=1
; Smoother scroll: lower deceleration than LVGL's default (10) so flicks glide
; longer instead of stopping abruptly. lv_conf leaves this unset, so this -D wins.
-D LV_INDEV_DEF_SCROLL_THROW=7
-D MAX_CONTACTS=2000
-D MAX_GROUP_CHANNELS=40
-D DISPLAY_CLASS=ST7796LCDDisplay
-D ADMIN_PASSWORD='"password"'
-D MULTI_TRANSPORT_COMPANION=1
-D WADAMESH_FORK_BUILD=1
-D TCP_PORT=5000
-D WS_PORT=8765
-D BLE_PIN_CODE=123456
-D CONFIG_MBEDTLS_ASYMMETRIC_CONTENT_LEN=1
-D CONFIG_MBEDTLS_SSL_IN_CONTENT_LEN=16384
-D CONFIG_MBEDTLS_SSL_OUT_CONTENT_LEN=4096
; --- ST7796 display (TFT_eSPI) ---
-D USER_SETUP_LOADED=1
-D ST7796_DRIVER=1
; REQUIRED: this panel's 222px glass is narrower than the ST7796 controller's
; 320px GRAM. TFT_eSPI's ST7796_Rotation.h only applies the needed 49px
; column/row offset when this is defined (unlike ST7789, it isn't automatic
; for ST7796) -- ST7796LCDDisplay.cpp #errors at compile time without it.
-D CGRAM_OFFSET=1
; REQUIRED on ESP32-S3: TFT_eSPI_ESP32_S3.h's raw register macros (_spi_user,
; _spi_cmd, _spi_mosi_dlen -- used by begin_tft_write()/TFT_WRITE_BITS) take
; SPI_PORT and feed it straight into IDF's SPI_USER_REG(i)/REG_SPI_BASE(i),
; which only resolves to a real peripheral for i>=2 (SPI2/SPI3); i<2 returns
; base address 0. Leaving both USE_HSPI_PORT/USE_FSPI_PORT undefined makes
; that file fall back to SPI_PORT=FSPI, but FSPI is the *Arduino* enum value
; (0 on S3) rather than the raw IDF host index TFT_eSPI's own macros need --
; so _spi_user resolves to address 0x10, and the very first writecommand()
; in ST7796LCDDisplay::begin()/TFT_eSPI::init() hard-crashes with a
; StoreProhibited panic (confirmed on hardware: black screen, boot-looping
; "Guru Meditation Error" at TFT_eSPI::begin_tft_write()). USE_FSPI_PORT
; forces SPI_PORT=2 (real SPI2/"GPSPI2") consistently across both the raw
; macros and the SPIClass(FSPI) object TFT_eSPI constructs internally.
; USE_HSPI_PORT (real SPI3) is deliberately NOT used here instead: the
; radio's own `SPIClass spi` (variants/lilygo_tlora_pager/target.cpp) takes
; its default ctor arg (HSPI), which the Arduino core also maps to real
; SPI3 -- so picking HSPI for the display would put both peripherals on the
; same physical SPI host and conflict.
-D USE_FSPI_PORT=1
-D TFT_WIDTH=222
-D TFT_HEIGHT=480
-D TFT_MOSI=34
-D TFT_SCLK=35
-D TFT_CS=38
-D TFT_DC=37
-D TFT_RST=-1
-D TFT_MISO=33
-D TFT_BL=-1
; trail-mate's kPagerDisplaySpiClockMhz = 80.
-D SPI_FREQUENCY=80000000
build_src_filter =
+<*.cpp>
+<*.c>
+<helpers/*.cpp>
+<helpers/esp32/*.cpp>
+<helpers/input/*.cpp>
+<helpers/ui/*.cpp>
+<ui-touch/*.cpp>
+<ui-touch/*.c>
+<../variants/lilygo_tlora_pager/*.cpp>
lib_deps =
https://github.com/ALLFATHER-BV/meshcomod.git#core-v1.16.5
SPI
Wire
jgromes/RadioLib @ ^7.6.0
rweather/Crypto @ ^0.4.0
adafruit/RTClib @ ^2.1.3
melopero/Melopero RV3028 @ ^1.1.0
electroniccats/CayenneLPP @ 1.6.1
h2zero/NimBLE-Arduino @ 1.4.3
adafruit/Adafruit INA3221 Library @ ^1.0.1
adafruit/Adafruit INA219 @ ^1.2.3
robtillaart/INA226 @ ^0.6.4
adafruit/Adafruit INA260 Library @ ^1.5.3
adafruit/Adafruit AHTX0 @ ^2.0.5
adafruit/Adafruit BME280 Library @ ^2.3.0
adafruit/Adafruit BMP280 Library @ ^2.6.8
adafruit/Adafruit SHTC3 Library @ ^1.0.1
sensirion/Sensirion I2C SHT4x @ ^1.1.2
arduino-libraries/Arduino_LPS22HB @ ^1.0.2
adafruit/Adafruit MLX90614 Library @ ^2.1.5
adafruit/Adafruit_VL53L0X @ ^1.2.4
stevemarple/MicroNMEA @ ^2.0.6
adafruit/Adafruit BME680 Library @ ^2.0.4
adafruit/Adafruit BMP085 Library @ ^1.2.4
ESP32Async/ESPAsyncWebServer @ 3.10.3
file://arch/esp32/AsyncElegantOTA
lvgl/lvgl @ ^8.3.11
densaugeo/base64 @ ~1.4.0
knolleary/PubSubClient @ ^2.8.0
bodmer/TFT_eSPI @ ^2.5.43
adafruit/Adafruit TCA8418 @ ^1.0.2
lewisxhe/SensorLib @ 0.3.3
; Milestone 10: SX1262-variant env for pager units sold with that radio instead
; of LR1121 -- same board JSON, same variant dir, same physical NSS/RESET/BUSY/
; DIO1/SCLK/MISO/MOSI pins (same PCB slot, just a different chip populated —
; see TLORA_PAGER_PORT.md's hardware-facts table). RADIO_CLASS/WRAPPER_CLASS
; swap to the core fork's CustomSX1262/CustomSX1262Wrapper, the exact same
; generic classes the T-Deck already uses -- see target.cpp's radio_init()
; for why no new radio C++ code was needed, just these build flags.
[env:tlora_pager_sx1262_companion_radio_touch]
platform = platformio/espressif32@6.11.0
framework = arduino
board = lilygo-t-lora-pager
monitor_speed = 115200
board_build.partitions = variants/lilygo_tlora_pager/partitions_tlora_pager_touch.csv
extra_scripts = pre:scripts/inject_wifi_env.py, merge-bin.py
build_flags =
-Wno-deprecated-declarations -Wno-unused-parameter -DNDEBUG -DRADIOLIB_STATIC_ONLY=1 -DRADIOLIB_GODMODE=1
-D MC_VENDORED_TOUCH_APP
-D LORA_FREQ=869.618
-D LORA_BW=62.5
-D LORA_SF=8
-D ENABLE_PRIVATE_KEY_IMPORT=1
-D ENABLE_PRIVATE_KEY_EXPORT=1
-D RADIOLIB_EXCLUDE_CC1101=1
-D RADIOLIB_EXCLUDE_RF69=1
-D RADIOLIB_EXCLUDE_SX1231=1
-D RADIOLIB_EXCLUDE_SI443X=1
-D RADIOLIB_EXCLUDE_RFM2X=1
-D RADIOLIB_EXCLUDE_SX128X=1
-D RADIOLIB_EXCLUDE_AFSK=1
-D RADIOLIB_EXCLUDE_AX25=1
-D RADIOLIB_EXCLUDE_HELLSCHREIBER=1
-D RADIOLIB_EXCLUDE_MORSE=1
-D RADIOLIB_EXCLUDE_APRS=1
-D RADIOLIB_EXCLUDE_BELL=1
-D RADIOLIB_EXCLUDE_RTTY=1
-D RADIOLIB_EXCLUDE_SSTV=1
; SX126X stays IN (that's this env's radio family); LR11X0 isn't used at all.
-D RADIOLIB_EXCLUDE_LR11X0=1
-D ESP32_PLATFORM
; --- T-LoRa Pager board (SX1262 variant) ---
-I variants/lilygo_tlora_pager
-D TLORA_PAGER=1
-D BOARD_HAS_PSRAM=1
; 0 = silence ARDUHAL [E] spam, same rationale as the other envs.
-D CORE_DEBUG_LEVEL=0
-D ARDUINO_USB_CDC_ON_BOOT=1
-D PIN_USER_BTN=0
-D USE_SX1262=1
-D RADIO_CLASS=CustomSX1262
-D WRAPPER_CLASS=CustomSX1262Wrapper
; Same 22dBm ceiling as the LR1121 env -- trail-mate's own reference for this
; exact board (~/dev/trail-mate/boards/tlora_pager) uses the identical
; TRAIL_MATE_LORA_TX_POWER_MAX_DBM=22 for BOTH its LR1121 and SX1262 envs, and
; it's this chip's well-known real ceiling too.
-D LORA_TX_POWER=22
; SX126X_DIO2_AS_RF_SWITCH=true and SX126X_CURRENT_LIMIT=140 are carried over
; from the T-Deck's own SX1262 config -- NOT because this is the T-Deck, but
; because both are tied to the 22dBm target above, not to board-specific analog
; circuitry: RadioLib's own SX126x.cpp already defaults DIO2-as-switch to true
; internally (same value, just made explicit here), and its default current
; limit (60mA) is what silently capped the T-Deck's real TX power below its
; target before that env raised it to 140mA -- the same physics apply to any
; SX1262 module asked to reach 22dBm, not something unique to the T-Deck's PCB.
-D SX126X_DIO2_AS_RF_SWITCH=true
-D SX126X_CURRENT_LIMIT=140
-D SX126X_RX_BOOSTED_GAIN=1
; Deliberately NOT setting SX126X_DIO3_TCXO_VOLTAGE (unlike the T-Deck's
; 1.8f) -- that IS a board-specific analog value (this board's actual TCXO
; circuit), and trail-mate's own working reference for this exact PCB never
; overrides it either, relying on CustomSX1262::std_init()'s built-in 1.6V
; fallback (RadioLib's own SX1262::begin() default) -- which also already
; auto-retries at 0.0f on an SPI-cmd failure if 1.6V doesn't suit this board's
; real hardware. Revisit with a measured value if bring-up shows otherwise.
-D P_LORA_DIO_1=14
-D P_LORA_NSS=36
-D P_LORA_RESET=47
-D P_LORA_BUSY=48
-D P_LORA_SCLK=35
-D P_LORA_MISO=33
-D P_LORA_MOSI=34
-D ENV_INCLUDE_GPS=1
-D ENV_SKIP_GPS_DETECT=1
-D ENV_INCLUDE_AHTX0=0
-D ENV_INCLUDE_BME280=0
-D ENV_INCLUDE_BMP280=0
-D ENV_INCLUDE_SHTC3=0
-D ENV_INCLUDE_SHT4X=0
-D ENV_INCLUDE_LPS22HB=0
-D ENV_INCLUDE_INA3221=0
-D ENV_INCLUDE_INA219=0
-D ENV_INCLUDE_INA226=0
-D ENV_INCLUDE_INA260=0
-D ENV_INCLUDE_MLX90614=0
-D ENV_INCLUDE_VL53L0X=0
-D ENV_INCLUDE_BME680=0
-D ENV_INCLUDE_BMP085=0
-D DISPLAY_SCALE_X=1.0
-D DISPLAY_SCALE_Y=1.0
; AW9364 backlight enable/pulse pin (ST7796LCDDisplay owns brightness -- see
; the CGRAM_OFFSET comment below for why this isn't a plain PWM pin).
-D PIN_TFT_LEDA_CTL=42
; Swapped vs. trail-mate's raw GPS_RX=4/GPS_TX=12: wadamesh's core calls
; Serial1.setPins(PIN_GPS_TX, PIN_GPS_RX), and HardwareSerial::setPins()
; takes (rxPin, txPin) -- so PIN_GPS_TX must be the ESP's own RX pin (4) and
; PIN_GPS_RX the ESP's own TX pin (12). See TLORA_PAGER_PORT.md Risk 1c.
-D PIN_GPS_RX=12
-D PIN_GPS_TX=4
-D GPS_BAUD_RATE=38400
; --- touch UI / companion stack ---
-I include
-I src
-I src/ui-touch
-D UI_LVGL=1
-D HAS_TOUCH_UI=1
-D FIRMWARE_OTA_ENV='"tlora_pager_sx1262_companion_radio_touch"'
-D HAS_PAGER_KEYBOARD=1
-D HAS_PAGER_ENCODER=1
-D KB_INT=6
-D KB_BACKLIGHT=46
-D ROTARY_A=40
-D ROTARY_B=41
-D ROTARY_C=7
; ES8311 codec I2S pins (NS4150B amp downstream, enabled via XL9555
; AMP_EN -- see TLoraPagerBoard::setAmpEnabled()). Confirmed against the
; canonical arduino-esp32 pins_arduino.h for this board -- see
; TLORA_PAGER_PORT.md's Audio row.
-D PIN_I2S_MCLK=10
-D PIN_I2S_BCK=11
-D PIN_I2S_WS=18
-D PIN_I2S_DOUT=45
-D PIN_I2S_SDIN=17
-D ENABLE_ADVERT_ON_BOOT=0
-D LV_CONF_PATH=lv_conf.h
-D LV_CONF_INCLUDE_SIMPLE=1
; Smoother scroll: lower deceleration than LVGL's default (10) so flicks glide
; longer instead of stopping abruptly. lv_conf leaves this unset, so this -D wins.
-D LV_INDEV_DEF_SCROLL_THROW=7
-D MAX_CONTACTS=2000
-D MAX_GROUP_CHANNELS=40
-D DISPLAY_CLASS=ST7796LCDDisplay
-D ADMIN_PASSWORD='"password"'
-D MULTI_TRANSPORT_COMPANION=1
-D WADAMESH_FORK_BUILD=1
-D TCP_PORT=5000
-D WS_PORT=8765
-D BLE_PIN_CODE=123456
-D CONFIG_MBEDTLS_ASYMMETRIC_CONTENT_LEN=1
-D CONFIG_MBEDTLS_SSL_IN_CONTENT_LEN=16384
-D CONFIG_MBEDTLS_SSL_OUT_CONTENT_LEN=4096
; --- ST7796 display (TFT_eSPI) ---
-D USER_SETUP_LOADED=1
-D ST7796_DRIVER=1
; REQUIRED: this panel's 222px glass is narrower than the ST7796 controller's
; 320px GRAM. TFT_eSPI's ST7796_Rotation.h only applies the needed 49px
; column/row offset when this is defined (unlike ST7789, it isn't automatic
; for ST7796) -- ST7796LCDDisplay.cpp #errors at compile time without it.
-D CGRAM_OFFSET=1
; REQUIRED on ESP32-S3: see the LR1121 env's identical comment above --
; same display, same panel, same constraint, unrelated to the radio chip.
-D USE_FSPI_PORT=1
-D TFT_WIDTH=222
-D TFT_HEIGHT=480
-D TFT_MOSI=34
-D TFT_SCLK=35
-D TFT_CS=38
-D TFT_DC=37
-D TFT_RST=-1
-D TFT_MISO=33
-D TFT_BL=-1
; trail-mate's kPagerDisplaySpiClockMhz = 80.
-D SPI_FREQUENCY=80000000
build_src_filter =
+<*.cpp>
+<*.c>
+<helpers/*.cpp>
+<helpers/esp32/*.cpp>
+<helpers/input/*.cpp>
+<helpers/ui/*.cpp>
+<ui-touch/*.cpp>
+<ui-touch/*.c>
+<../variants/lilygo_tlora_pager/*.cpp>
lib_deps =
https://github.com/ALLFATHER-BV/meshcomod.git#core-v1.16.5
SPI
Wire
jgromes/RadioLib @ ^7.6.0
rweather/Crypto @ ^0.4.0
adafruit/RTClib @ ^2.1.3
melopero/Melopero RV3028 @ ^1.1.0
electroniccats/CayenneLPP @ 1.6.1
h2zero/NimBLE-Arduino @ 1.4.3
adafruit/Adafruit INA3221 Library @ ^1.0.1
adafruit/Adafruit INA219 @ ^1.2.3
robtillaart/INA226 @ ^0.6.4
adafruit/Adafruit INA260 Library @ ^1.5.3
adafruit/Adafruit AHTX0 @ ^2.0.5
adafruit/Adafruit BME280 Library @ ^2.3.0
adafruit/Adafruit BMP280 Library @ ^2.6.8
adafruit/Adafruit SHTC3 Library @ ^1.0.1
sensirion/Sensirion I2C SHT4x @ ^1.1.2
arduino-libraries/Arduino_LPS22HB @ ^1.0.2
adafruit/Adafruit MLX90614 Library @ ^2.1.5
adafruit/Adafruit_VL53L0X @ ^1.2.4
stevemarple/MicroNMEA @ ^2.0.6
adafruit/Adafruit BME680 Library @ ^2.0.4
adafruit/Adafruit BMP085 Library @ ^1.2.4
ESP32Async/ESPAsyncWebServer @ 3.10.3
file://arch/esp32/AsyncElegantOTA
lvgl/lvgl @ ^8.3.11
densaugeo/base64 @ ~1.4.0
knolleary/PubSubClient @ ^2.8.0
bodmer/TFT_eSPI @ ^2.5.43
adafruit/Adafruit TCA8418 @ ^1.0.2
lewisxhe/SensorLib @ 0.3.3
[env:ThinkNode_M9_companion_radio_touch]
platform = platformio/espressif32@6.11.0
framework = arduino
board = thinknode_m9
monitor_speed = 115200
board_build.partitions = variants/thinknode_m9/partitions_m9_touch.csv
; patch_radiolib_lr11x0: preprod M9 LR1110s run old transceiver FW that rejects
; DriveDiosInSleepMode (0x012A, FW 0x0308+) with CMD_PERR -> begin() = -706.
; The pre-script makes RadioLib's config() skip it on old FW (idempotent,
; per-env libdeps copy). See scripts/build/patch_radiolib_lr11x0.py.
extra_scripts = pre:scripts/inject_wifi_env.py, pre:scripts/build/patch_radiolib_lr11x0.py, merge-bin.py
build_flags =
-Wno-deprecated-declarations -Wno-unused-parameter -DNDEBUG -DRADIOLIB_STATIC_ONLY=1 -DRADIOLIB_GODMODE=1
-D MC_VENDORED_TOUCH_APP
-D LORA_FREQ=869.618
-D LORA_BW=62.5
-D LORA_SF=8
-D ENABLE_PRIVATE_KEY_IMPORT=1
-D ENABLE_PRIVATE_KEY_EXPORT=1
-D RADIOLIB_EXCLUDE_CC1101=1
-D RADIOLIB_EXCLUDE_RF69=1
-D RADIOLIB_EXCLUDE_SX1231=1
-D RADIOLIB_EXCLUDE_SI443X=1
-D RADIOLIB_EXCLUDE_RFM2X=1
-D RADIOLIB_EXCLUDE_SX128X=1
-D RADIOLIB_EXCLUDE_AFSK=1
-D RADIOLIB_EXCLUDE_AX25=1
-D RADIOLIB_EXCLUDE_HELLSCHREIBER=1
-D RADIOLIB_EXCLUDE_MORSE=1
-D RADIOLIB_EXCLUDE_APRS=1
-D RADIOLIB_EXCLUDE_BELL=1
-D RADIOLIB_EXCLUDE_RTTY=1
-D RADIOLIB_EXCLUDE_SSTV=1
-D ESP32_PLATFORM
; --- ThinkNode M9 board ---
-I variants/thinknode_m9
-D HAS_THINKNODE_M9
-D BOARD_HAS_PSRAM=1
; M9 uses the UART bridge (ttyUSB0), not native USB-CDC — confirmed during
; Specter bring-up. With ARDUINO_USB_CDC_ON_BOOT=1 (the T-Deck's setting)
; app Serial logs go to a ttyACM* port this board doesn't expose and
; appear completely silent.
-D ARDUINO_USB_CDC_ON_BOOT=0
-D PIN_USER_BTN=0
-D RADIO_CLASS=CustomLR1110
-D WRAPPER_CLASS=CustomLR1110Wrapper
-D LORA_TX_POWER=22
; LR1110 clock: TCXO mode at 3.3 V — EMPIRICALLY CONFIRMED on the tester's
; preproduction unit: Meshtastic's thinknode_m9 variant logs "using DIO3 as
; TCXO reference voltage at 3.300000 V" followed by "LR1110 init result 0".
; The earlier theory here (Y1 = self-powered active oscillator -> tcxo must
; be 0) was disproven on hardware: with 0 the chip boots on its internal RC
; (SPI alive, no -2) but the first command needing the real 32 MHz clock is
; rejected -> radio init failed -707 (bring-up build #1, 2026-07-06). The
; schematic's "VTCXO rail" feeding Y1 is evidently the LR1110's own
; TCXO-supply output, so the chip must drive it.
-D LR11X0_DIO3_TCXO_VOLTAGE=3.3
; Bring-up only: RadioLib's own boot prints (found-chip line with the
; transceiver/WiFi/GNSS FW versions, calibration errors). Goes to Serial =
; UART0 on this board. Low volume; drop once the radio is proven.
-D RADIOLIB_DEBUG_BASIC=1
-D RX_BOOSTED_GAIN=true
; DIO5/DIO6 -> RFSW0_V1/RFSW1_V2 confirmed against the V1.0 schematic (LR1110
; block, U7 pins 19/20 -> R19/R20 -> U8 V1/V2) — see target.cpp for the table
; and M9_PORT.md for the crop. The per-mode polarity is the conventional
; 2-pin table every other MeshCore LR1110 board uses, not independently
; re-derived from U8's datasheet (part number isn't printed on the schematic).
-D RF_SWITCH_TABLE
; --- LR1110 SPI / control pins (verified: V1.0 schematic + boot log) ---
-D P_LORA_NSS=39
-D P_LORA_DIO_1=42
-D P_LORA_RESET=45
-D P_LORA_BUSY=41
-D P_LORA_SCLK=40
-D P_LORA_MISO=38
-D P_LORA_MOSI=47
; --- Peripheral I2C bus 0 (Wire): RTC PCF8563 0x51 / IMU QMI8658 0x6b /
; compass QMC6309 0x7c. Brought up by ESP32Board::begin(). ---
-D PIN_BOARD_SDA=7
-D PIN_BOARD_SCL=6
-D PIN_VBAT_READ=13
; --- GPS (CC1167Q, UART1) ---
-D ENV_INCLUDE_GPS=1
-D PIN_GPS_RX=3
-D PIN_GPS_TX=2
-D PIN_GPS_EN=11
-D PIN_GPS_RESET=5
-D PIN_GPS_RESET_ACTIVE=HIGH
; GPS_RST1 -> R46 -> NPN Q16 base: GPIO HIGH turns Q16 on, pulling the module's
; reset pin to GND — so HIGH asserts reset, LOW releases it (inverted vs. library default)
-D PIN_GPS_EN_ACTIVE=LOW
; GPIO10 (GPS ON_OFF) and GPIO4 (1PPS) exist on the schematic but have no
; consumer in this driver yet — reserved, not wired.
-D GPS_BAUD_RATE=115200
-D THINKNODE_M9_BUZZER_PIN=9
-D ENV_INCLUDE_AHTX0=0
-D ENV_INCLUDE_BME280=0
-D ENV_INCLUDE_BMP280=0
-D ENV_INCLUDE_SHTC3=0
-D ENV_INCLUDE_SHT4X=0
-D ENV_INCLUDE_LPS22HB=0
-D ENV_INCLUDE_INA3221=0
-D ENV_INCLUDE_INA219=0
-D ENV_INCLUDE_INA226=0
-D ENV_INCLUDE_INA260=0
-D ENV_INCLUDE_MLX90614=0
-D ENV_INCLUDE_VL53L0X=0
-D ENV_INCLUDE_BME680=0
-D ENV_INCLUDE_BMP085=0
; --- ST7789 panel (manufacturer-confirmed; NOT ILI9341) ---
; No LILYGO_TDECK / HELTEC_LORA_V4_TFT macro is defined, so ST7789LCDDisplay
; uses its default branch (Adafruit_ST7789 over the global `SPI`, the same
; instance the radio uses) — matches the LR1110 reference variants, which
; also share one SPI peripheral across radio + display + (on the M9) SD.
-D DISPLAY_SCALE_X=1.0
-D DISPLAY_SCALE_Y=1.0
; HARDWARE-VERIFIED (bring-up #6, 2026-07-06): rotation 3 rendered the UI
; 180 degrees off on the tester's unit; 1 is the correct landscape
; orientation (keyboard below screen). Adafruit rotations 1/3 are the two
; landscape options, 180 degrees apart.
-D DISPLAY_ROTATION=1
; PIN_TFT_LEDA_CTL is set to -1, NOT left undefined: the installed ST7789LCDDisplay
; references it unconditionally (`if (PIN_TFT_LEDA_CTL != -1)`, no #ifdef guard around
; the macro itself — leaving it undefined is a compile error, not a no-op). -1 makes
; that check skip the pin entirely, since the vendored class always drives it
; active-HIGH, but the M9's backlight is a PNP transistor (active-LOW) — so
; ThinkNodeM9Board owns BL_EN (GPIO17) directly instead (see M9Board.h/.cpp).
; PIN_PERIPH_POWER is the OTHER (also active-low) rail, gating the LCD/GPS/sensors,
; and IS passed through ST7789LCDDisplay's RefCountedDigitalPin constructor arg in
; target.cpp.
-D PIN_TFT_LEDA_CTL=-1
-D PIN_PERIPH_POWER=18
-D PIN_TFT_BL_EN=17
-D PIN_TFT_RST=14
-D PIN_TFT_DC=15
-D PIN_TFT_CS=16
; PIN_TFT_SCL / PIN_TFT_SDA intentionally NOT defined: only the
; USE_PIN_TFT / LILYGO_TDECK / HELTEC_LORA_V4_TFT branches of
; ST7789LCDDisplay's constructor consume them, and M9 uses none of those —
; it takes the default `display(&SPI, PIN_TFT_CS, PIN_TFT_DC, PIN_TFT_RST)`
; branch (global SPI, same instance the radio uses).
;
; NOTE: a software-SPI (USE_PIN_TFT) diagnostic build was tried here to test
; whether the class's hardcoded 80MHz hardware SPI clock was corrupting the
; boot-splash write. It wasn't — software SPI reproduced the EXACT same
; freeze-then-TG1WDT_SYS_RST at the exact same point, just slower, which
; rules out the SPI clock/signal-integrity theory entirely. See
; M9_PORT.md / git history if revisiting that path.
; microSD: on the shared LoRa SPI bus, same as T-Deck. CS is GPIO48 — the
; schematic net SPICLK_N, which is NOT one of the GPIO33-37 octal-PSRAM
; lines: SPICLK_N/GPIO48 (and SPICLK_P/GPIO47) are only reserved on the
; R8V/R16V 1.8V-differential-clock variants. This board is a plain R8 (see
; the env comment above), which uses the ordinary single-ended SPICLK
; instead, so GPIO48 is genuinely free. Confirmed via schematic: GPS_RST1
; and this net were the ones directly identified, not inferred.
-D PIN_SD_CS=48
-D HAS_M9_KEYBOARD=1
; Keyboard bus SCHEMATIC-VERIFIED (V1.0 sheet, bring-up #9): S3 GPIO20 =
; net ESP32-2_SDA, GPIO21 = ESP32-2_SCL, to the keyboard ESP32-S2 (its
; GPIO7/6) through R2/R1 series resistors, pullups R73/R72, S2 powered from
; always-on 3V3 via R3. GPIO19/20 are also the S3's native USB D-/D+ pads —
; M9Board::begin() must release the USB-Serial-JTAG pad claim first.
-D PIN_KB_SDA=20
-D PIN_KB_SCL=21
-D PIN_KB_ADDR=0x6c
; --- touch UI / companion stack (M9 has no touch — keyboard + d-pad text
; entry only; keypad-nav focus traversal is NOT wired yet, see
; M9_PORT.md) ---
-I include
-I src
-I src/ui-touch
-D UI_LVGL=1
-D HAS_TOUCH_UI=1
-D FIRMWARE_OTA_ENV='"ThinkNode_M9_companion_radio_touch"'
-D ENABLE_ADVERT_ON_BOOT=0
-D LV_CONF_PATH=lv_conf.h
-D LV_CONF_INCLUDE_SIMPLE=1
-D LV_INDEV_DEF_SCROLL_THROW=7
-D MAX_CONTACTS=2000
-D MAX_GROUP_CHANNELS=40
-D DISPLAY_CLASS=ST7789LCDDisplay
-D ADMIN_PASSWORD='"password"'
-D MULTI_TRANSPORT_COMPANION=1
-D WADAMESH_FORK_BUILD=1
-D TCP_PORT=5000
-D WS_PORT=8765
-D BLE_PIN_CODE=123456
-D CONFIG_MBEDTLS_ASYMMETRIC_CONTENT_LEN=1
-D CONFIG_MBEDTLS_SSL_IN_CONTENT_LEN=16384
-D CONFIG_MBEDTLS_SSL_OUT_CONTENT_LEN=4096
build_src_filter =
+<*.cpp>
+<*.c>
+<helpers/*.cpp>
+<helpers/esp32/*.cpp>
+<helpers/input/*.cpp>
+<ui-touch/*.cpp>
+<ui-touch/*.c>
+<../variants/thinknode_m9/*.cpp>
lib_deps =
https://github.com/ALLFATHER-BV/meshcomod.git#core-v1.16.5
SPI
Wire
jgromes/RadioLib @ ^7.6.0
rweather/Crypto @ ^0.4.0
adafruit/RTClib @ ^2.1.3
melopero/Melopero RV3028 @ ^1.1.0
electroniccats/CayenneLPP @ 1.6.1
h2zero/NimBLE-Arduino @ 1.4.3
adafruit/Adafruit INA3221 Library @ ^1.0.1
adafruit/Adafruit INA219 @ ^1.2.3
robtillaart/INA226 @ ^0.6.4
adafruit/Adafruit INA260 Library @ ^1.5.3
adafruit/Adafruit AHTX0 @ ^2.0.5
adafruit/Adafruit BME280 Library @ ^2.3.0
adafruit/Adafruit BMP280 Library @ ^2.6.8
adafruit/Adafruit SHTC3 Library @ ^1.0.1
sensirion/Sensirion I2C SHT4x @ ^1.1.2
arduino-libraries/Arduino_LPS22HB @ ^1.0.2
adafruit/Adafruit MLX90614 Library @ ^2.1.5
adafruit/Adafruit_VL53L0X @ ^1.2.4
stevemarple/MicroNMEA @ ^2.0.6
adafruit/Adafruit BME680 Library @ ^2.0.4
adafruit/Adafruit BMP085 Library @ ^1.2.4
adafruit/Adafruit ST7735 and ST7789 Library @ ^1.11.0
ESP32Async/ESPAsyncWebServer @ 3.10.3
file://arch/esp32/AsyncElegantOTA
lvgl/lvgl @ ^8.3.11
densaugeo/base64 @ ~1.4.0
knolleary/PubSubClient @ ^2.8.0
; ======================================================================
; RAK WisMesh Tap V2 — ST7789 TFT + FT5x06 capacitive touch + SX1262.
; RAK3312 module (ESP32-S3, 16 MB Flash DIO, 8 MB Octal PSRAM).
; ======================================================================
[env:rak_tap_v2_companion_radio_touch]
platform = platformio/espressif32@6.11.0
framework = arduino
board = rak_tap_v2
monitor_speed = 115200
board_build.flash_mode = dio ; RAK3312 requires DIO (board JSON defaults to qio)
board_build.partitions = variants/rak_tap_v2/partitions_rak_tap_v2_touch.csv
extra_scripts = pre:scripts/inject_wifi_env.py, merge-bin.py
; Round-1b USB: MODE=1 HW CDC (single COM7). No 1200bps touch — use DTR/RTS reset.
build_unflags =
-D ARDUINO_USB_MODE=0
upload_speed = 460800
upload_flags =
--before=default_reset
--after=hard_reset
build_flags =
-Wno-deprecated-declarations -Wno-unused-parameter -DNDEBUG -DRADIOLIB_STATIC_ONLY=1 -DRADIOLIB_GODMODE=1
-D MC_VENDORED_TOUCH_APP
-D LORA_FREQ=869.618
-D LORA_BW=62.5
-D LORA_SF=8
-D ENABLE_PRIVATE_KEY_IMPORT=1
-D ENABLE_PRIVATE_KEY_EXPORT=1
-D RADIOLIB_EXCLUDE_CC1101=1
-D RADIOLIB_EXCLUDE_RF69=1
-D RADIOLIB_EXCLUDE_SX1231=1
-D RADIOLIB_EXCLUDE_SI443X=1
-D RADIOLIB_EXCLUDE_RFM2X=1
-D RADIOLIB_EXCLUDE_SX128X=1
-D RADIOLIB_EXCLUDE_AFSK=1
-D RADIOLIB_EXCLUDE_AX25=1
-D RADIOLIB_EXCLUDE_HELLSCHREIBER=1
-D RADIOLIB_EXCLUDE_MORSE=1
-D RADIOLIB_EXCLUDE_APRS=1
-D RADIOLIB_EXCLUDE_BELL=1
-D RADIOLIB_EXCLUDE_RTTY=1
-D RADIOLIB_EXCLUDE_SSTV=1
-D ESP32_PLATFORM
; --- sensors (GPS + AHTx0 + BME680 enabled) ---
-D ENV_INCLUDE_GPS=1
-D ENV_INCLUDE_AHTX0=1
-D ENV_INCLUDE_BME280=0
-D ENV_INCLUDE_BMP280=0
-D ENV_INCLUDE_SHTC3=0
-D ENV_INCLUDE_SHT4X=0
-D ENV_INCLUDE_LPS22HB=0
-D ENV_INCLUDE_INA3221=0
-D ENV_INCLUDE_INA219=0
-D ENV_INCLUDE_INA226=0
-D ENV_INCLUDE_INA260=0
-D ENV_INCLUDE_MLX90614=0
-D ENV_INCLUDE_VL53L0X=0
-D ENV_INCLUDE_BME680=1
-D ENV_INCLUDE_BMP085=0
; --- LoRa SX1262 (RAK3312 module, same pins as RAK3112) ---
-I variants/rak_tap_v2
-D RAK_WISMESH_TAP_V2=1
-D USE_SX1262
-D ESP32_CPU_FREQ=240
-D RADIO_CLASS=CustomSX1262
-D WRAPPER_CLASS=CustomSX1262Wrapper
-D LORA_TX_POWER=22
-D P_LORA_TX_LED=46
-D P_LORA_DIO_1=47
-D P_LORA_NSS=7
-D P_LORA_RESET=8
-D P_LORA_BUSY=48
-D P_LORA_SCLK=5
-D P_LORA_MISO=3
-D P_LORA_MOSI=6
-D SX126X_DIO2_AS_RF_SWITCH=true
-D SX126X_DIO3_TCXO_VOLTAGE=1.8
-D SX126X_CURRENT_LIMIT=140
-D SX126X_RX_BOOSTED_GAIN=1
-D PIN_GPS_RX=43
-D PIN_GPS_TX=44
-D PIN_USER_BTN=0
-D PIN_VEXT_EN=14
-D PIN_BOARD_SDA=9
-D PIN_BOARD_SCL=40
; --- TFT (ST7789 240x320, LovyanGFX hardware SPI on FSPI/SPI2_HOST SCL=13/SDA=11) ---
; USB: ARDUINO_USB_* from boards/rak_tap_v2.json (MODE=1 HW CDC, Meshtastic-aligned)
-D DISPLAY_CLASS=LGFXDisplay
-D LGFX_INVERT_COLOR=true ; false=white bg, true=black bg (ST7789 INVON)
-D DISPLAY_ROTATION=3
-D DISPLAY_SCALE_X=1.0
-D DISPLAY_SCALE_Y=1.0
-D PIN_TFT_RST=-1
-D PIN_TFT_LEDA_CTL=41
-D PIN_TFT_LEDA_CTL_ACTIVE=HIGH
-D PIN_TFT_CS=12
-D PIN_TFT_DC=42
-D PIN_TFT_SCL=13
-D PIN_TFT_SDA=11
; --- FT5x06 capacitive touch (I2C0 addr 0x38, SDA=9/SCL=40) ---
-D HAS_RAK_TAP_V2=1
-D RAK_TS_FLIP_X=1
-D RAK_TS_FLIP_Y=1
-D PIN_TOUCH_SDA=9
-D PIN_TOUCH_SCL=40
-D PIN_TOUCH_INT=39
; --- touch UI / companion stack ---
-I include
-I src
-I src/ui-touch
-D UI_LVGL=1
-D HAS_TOUCH_UI=1
-D FIRMWARE_OTA_ENV='"rak_tap_v2_companion_radio_touch"'
-D ENABLE_ADVERT_ON_BOOT=0
-D LV_CONF_PATH=lv_conf.h
-D LV_CONF_INCLUDE_SIMPLE=1
-D LV_INDEV_DEF_SCROLL_THROW=7
-D USER_SETUP_LOADED=1
-D ST7789_DRIVER=1
-D TFT_WIDTH=320
-D TFT_HEIGHT=240
-D TFT_MOSI=11
-D TFT_SCLK=13
-D TFT_CS=12
-D TFT_DC=42
-D TFT_RST=-1
-D TFT_MISO=-1
-D SPI_FREQUENCY=40000000
-D TFT_RGB_ORDER=TFT_RGB
-D TFT_INVERSION_ON=1
-D TFT_BL=41
-D TFT_BACKLIGHT_ON=1
-D MAX_CONTACTS=2000
-D MAX_GROUP_CHANNELS=40
-D ADMIN_PASSWORD='"password"'
-D MULTI_TRANSPORT_COMPANION=1
-D WADAMESH_FORK_BUILD=1
-D TCP_PORT=5000
-D WS_PORT=8765
-D BLE_PIN_CODE=123456
-D CONFIG_MBEDTLS_ASYMMETRIC_CONTENT_LEN=1
-D CONFIG_MBEDTLS_SSL_IN_CONTENT_LEN=16384
-D CONFIG_MBEDTLS_SSL_OUT_CONTENT_LEN=4096
build_src_filter =
+<*.cpp>
+<helpers/*.cpp>
+<helpers/esp32/*.cpp>
+<helpers/input/*.cpp>
+<ui-touch/*.cpp>
+<ui-touch/*.c>
+<../variants/rak_tap_v2/*.cpp>
lib_deps =
https://github.com/ALLFATHER-BV/meshcomod.git#core-v1.16.5
SPI
Wire
jgromes/RadioLib @ ^7.6.0
rweather/Crypto @ ^0.4.0
adafruit/RTClib @ ^2.1.3
melopero/Melopero RV3028 @ ^1.1.0
electroniccats/CayenneLPP @ 1.6.1
h2zero/NimBLE-Arduino @ 1.4.3
adafruit/Adafruit INA3221 Library @ ^1.0.1
adafruit/Adafruit INA219 @ ^1.2.3
robtillaart/INA226 @ ^0.6.4
adafruit/Adafruit INA260 Library @ ^1.5.3
adafruit/Adafruit AHTX0 @ ^2.0.5
adafruit/Adafruit BME280 Library @ ^2.3.0
adafruit/Adafruit BMP280 Library @ ^2.6.8
adafruit/Adafruit SHTC3 Library @ ^1.0.1
sensirion/Sensirion I2C SHT4x @ ^1.1.2
arduino-libraries/Arduino_LPS22HB @ ^1.0.2
adafruit/Adafruit MLX90614 Library @ ^2.1.5
adafruit/Adafruit_VL53L0X @ ^1.2.4
stevemarple/MicroNMEA @ ^2.0.6
adafruit/Adafruit BME680 Library @ ^2.0.4
adafruit/Adafruit BMP085 Library @ ^1.2.4
adafruit/Adafruit ST7735 and ST7789 Library @ ^1.11.0
ESP32Async/ESPAsyncWebServer @ 3.10.3
file://arch/esp32/AsyncElegantOTA
lvgl/lvgl @ ^8.3.11
lovyan03/LovyanGFX@1.2.21
bodmer/TFT_eSPI @ ^2.5.43
densaugeo/base64 @ ~1.4.0
knolleary/PubSubClient @ ^2.8.0
+29
View File
@@ -0,0 +1,29 @@
# beta_13 — community drop (one user-facing note per non-blank, non-# line; # lines are section comments)
# --- A note from Kaj (headline) ---
This one's a community release — thank you! A bunch of the features below came from contributor pull requests, and the rest are the keyboard, typing and quality-of-life fixes I promised after the last drop. Huge thanks to everyone sending PRs, opening issues and reporting bugs: Yazutsu, tun0, Vybo and samuelcoustet all have their work in this build. Keep it coming.
# --- Typing & keyboard navigation (T-Deck + Tanmatsu) ---
Open a chat or channel and the cursor is ready — you can type straight away. Every other text field now waits for Enter before it captures the keyboard, so the letter-navigation keys keep working until you actually want to type.
Pressing Enter (or Esc / the back button) on an empty message box drops the cursor and re-selects the field, so you can navigate away with the buttons again.
The menu-bar letter shortcuts no longer jump you to another page while you're typing in a field.
New "Show menu-bar letters" setting under Settings -> Keyboard (off by default) — turn it on to see the tab hotkey letters on the bar.
The accent pop-up no longer grabs the keyboard when it appears, so you can keep typing right through it.
# --- Composer ---
New dedicated "Special characters" picker for symbols that aren't on the keyboard (% $ @ # & =, currency, maths, accents) — separate from the emoji picker.
Long-press one of your sent messages to Resend it.
# --- Clock ---
The 12-hour clock setting now applies everywhere — the top bar, the chat bubbles and the lock screen — not just the chat list.
# --- From contributors ---
Room-server posts now show the actual author's name on each message instead of the room's own name. (Yazutsu, #40)
New "Direct (0-hop)" filter for the contact list and the map — show only nodes you're hearing directly, with no repeater hops in between. (tun0, #39)
Beer emoji in colour, tap the unread badge in the status bar to jump to your Chats, a new "notify on new contact" toggle, and Czech accents in the accent pop-up. (Vybo, #22)
Optional trackball "edge scroll" — push the cursor past a screen edge to scroll the list underneath it (off by default, under Settings -> Keyboard). (tun0, #38)
TCP now restarts immediately after you turn it off and on again, the OTA action is hidden when there's no update slot to use, and a TCP-toggle alert glitch is fixed. (samuelcoustet, #29)
# --- Fixes ---
Heltec V4: removed the after-crash report prompt — that board has no SD card or reachable storage to save the report to, so it was a dead end. (The T-Deck still offers it.)
When both Wi-Fi and GPS are off, the clock now sets itself from the timestamps on messages received over the mesh.
+7
View File
@@ -0,0 +1,7 @@
# beta_14 — hotfix (one user-facing note per non-blank, non-# line; # lines are section comments)
# --- Fix (headline) ---
Fixed a bug introduced in beta_13: if you had turned keyboard navigation OFF (Settings -> Keyboard), the physical keyboard stopped typing into text fields entirely on the T-Deck and Tanmatsu. Typing now works again with keyboard navigation off; with it on, nothing changed. (The Heltec V4 was never affected.)
# --- Also in this release ---
Includes everything from beta_13: room-server posts show the author's name, the Direct (0-hop) contact + map filter, beer emoji with a status-bar unread tap and a new-contact toast toggle and Czech accents, optional trackball edge-scroll, the dedicated special-characters picker, the 12-hour clock applied everywhere, and the keyboard navigation + typing improvements.
+18
View File
@@ -0,0 +1,18 @@
# beta_15 (one user-facing note per non-blank, non-# line; # lines are section comments)
# --- New ---
Power-saving now shows as an amber battery icon in the status bar — like iPhone's Low Power Mode — instead of a separate moon icon (T-Deck).
New @-mention picker: type @ in the message box to pick a contact from a list and drop their name in (thanks robinshizuyo-dev, #42).
# --- Fixed ---
Closing a settings item, menu or chat no longer snaps the list back to the top — it stays where you left it (thanks ZorkaTheDog, #45).
Messages you send from the MeshCore companion app now also show up on the device, in the right conversation (thanks HonzaDandy, #46).
Typing is more reliable on the T-Deck and Tanmatsu: tapping a text field — even one that's already highlighted — starts typing right away, and the accent pop-up no longer interrupts typing outside of chats.
The text cursor now only appears when a field is actually ready for input, so it's a dependable "you can type now" cue.
Smoother map panning: tile rendering no longer trips the watchdog and reboots during heavy scrolling.
# --- Changed ---
Keyboard navigation is now OFF by default. If you prefer driving the UI with the trackball / arrow keys, switch it back on in Settings -> Keyboard (your choice sticks until you change it). The Tanmatsu keeps it on, since it has no touchscreen.
# --- Also in this release ---
Includes everything from beta_14 and the earlier betas.
+16
View File
@@ -0,0 +1,16 @@
# beta_16 (one user-facing note per non-blank, non-# line; # lines are section comments)
# --- New ---
Heltec V4 Expansion Kit support: a dedicated Sensors tab (temperature, humidity, pressure, GPS and battery, with small history charts), a Home-screen environment readout, and an on-device "mesh console" for poking at the radio. It only turns up when a sensor board is actually attached, so a bare V4 looks exactly as it did before. This one was a real grind to land — it came in as a huge pull request built on an old beta, and getting it in cleanly meant re-doing most of it by hand against the current code and carefully fencing it all off so it can't bloat or disturb the T-Deck and Tanmatsu builds. Thanks to Samuel Coustet for the original work (#29).
French, Dutch, German, Spanish and Italian keyboards, on-screen and on the T-Deck's physical keys. Choosing one of those as your interface language now auto-selects the matching layout. Also from Samuel Coustet (#29).
Wi-Fi firmware updates are back: on a normally-flashed device (not the Launcher) you can update straight from Settings -> About, no cable needed.
You can also roll back now — "Install a previous version" lets you reinstall one of the last few releases over Wi-Fi, with a confirmation first since it's a downgrade.
# --- Fixed ---
The status-bar clock no longer overlaps the node name on the V4 (it had been crammed against it for a good while).
Closing a dialog no longer lets a scroll carry through to the page behind it (thanks tun0, #50).
The contact action sheet no longer overflows the screen in landscape (thanks tun0, #49).
The per-channel region field now shows your default region as the hint, instead of a generic placeholder (thanks tun0, #48).
# --- Also ---
Everything from beta_15 is included.
+23
View File
@@ -0,0 +1,23 @@
# beta_18 (one user-facing note per non-blank, non-# line; # lines are section comments)
# --- New ---
A topographic map style: turn on Map -> Options -> "Topographic map" for terrain-relief tiles (OpenStreetMap stays the default). Thanks to Samuel Coustet for the proxy work (#52).
New emoji in the picker: soccer ball, american football, moai, and the transgender flag.
Contacts can now sort ascending or descending, and there's a new "Nearest first" sort that orders contacts by distance from you (contacts without a shared location are left out).
The Discovered list gets the same sorting — by most-recently-heard, name, or distance — from a new sort button in its header.
The Chats header is tidied up: the add / mark-all-read / share-contact buttons are grouped together on the left, and sharing your contact now uses a proper QR icon.
# --- Fixed ---
The USB/PC companion connection no longer drops or throws "bad state" errors mid-session. The same fix also clears up repeater admin mode disconnecting and not being able to log in to member rooms.
Map tiles along the edges and corners of the view now fill in automatically as you pan, instead of needing a manual "reload tiles".
Reclaimed about 41 KB of memory by moving a large internal buffer to PSRAM — this fixes the Heltec V4 running out of RAM and rebooting when it loaded map tiles, and leaves more headroom on every board.
The map's "Show link lines" toggle is now remembered across reboots. Thanks to Yazutsu (#61).
Settings category names (Bluetooth, Radio & Mesh, Quick replies, ...) now fit on one line instead of wrapping or splitting mid-word.
Turning keyboard navigation on or off no longer snaps the settings list back to the top.
Heltec V4: the node name in the status bar no longer covers the clock.
T-Deck: the keyboard backlight no longer gets stuck on after flashing when it's set to Off.
Crash reporting is more reliable (it only prompts after an actual crash, not on every restart), and there are fewer stray reboots while saving settings.
Tanmatsu: changing the LoRa radio settings (frequency and so on) now takes effect immediately, without needing a reboot, and the app's settings now drive the radio.
# --- Also ---
Everything from beta_16 (and the Tanmatsu's beta_17) is included.
+14
View File
@@ -0,0 +1,14 @@
# beta_19 (one user-facing note per non-blank, non-# line; # lines are section comments)
# --- New ---
Radio & Mesh settings now show an airtime / duty-cycle readout: roughly how much of the airtime budget your current spreading factor, bandwidth and coding rate use, plus the time-on-air per packet — handy for staying inside regional limits like EU 868.
A new "Answer telemetry requests" toggle in Radio & Mesh settings controls whether other nodes can pull your battery and environment telemetry.
The Radio & Mesh settings page is now split into clear RADIO / MESH / SIGNAL sections so the options are easier to find.
# --- Fixed ---
Fixed a reboot that could happen when you closed a scrollable popup — the emoji picker, quick replies, the Wi-Fi scan list, the app drawer and similar — while it was still coasting from a flick. Thanks to everyone who sent in crash reports.
The accent popup no longer lingers on screen after you send a message on the T-Deck keyboard.
Heltec V4: the Expansion Kit environment line and mini chart on the Home screen no longer overlap the status text or run off the bottom of the display.
# --- Also ---
Everything from beta_18 is included.
+33
View File
@@ -0,0 +1,33 @@
# beta_20 (one user-facing note per non-blank, non-# line; # lines are section comments)
# --- New ---
Spectrum analyzer: a new app in the app drawer that sweeps the LoRa band and draws a live spectrum with a waterfall under it, a colour scale on the side and a peak-frequency readout. Handy for spotting interference or finding a quiet part of the band before you settle on a frequency.
Custom notification sounds: you can set your own notification sound from a 16-bit WAV file on the SD card, per event, instead of only the built-in chime. There is also a separate switch for the direct-message chime. Contributed by Yazutsu (#66).
Saved Wi-Fi networks: the device remembers more than one network now and can auto-join them. Each saved network has its own auto-join switch and can be forgotten on its own.
One chat settings screen: the gear on a chat or channel row, a long-press on that row, and the cog inside an open chat now all open the same screen. Everything is in one place: mark as read, mute messages, mute mentions, region and scope, share secret, blocked users, and remove or delete.
Per-channel mute: silence the notification sound for a single channel while the rest keep chiming.
High-gain receiver for the Heltec V4.3: the V4.3 front-end module has a roughly 17 dB receive amplifier that the firmware never switched on, so every V4.3 shipped with it bypassed. There is now a "High-gain receiver (FEM LNA)" toggle under Radio and Mesh, in the Signal section. Turning it on can noticeably improve weak-signal reception in quiet or remote spots; in a noisy area it can overload the front end, so it is off by default. V4.2 boards do not have this amplifier and do not show the toggle. Thanks to Wireless Rocks for the report and the measurements.
Apps button on the Heltec V4 home screen: the V4 home screen now has an Apps button next to Send advert, so the app drawer (Spectrum, RF Monitor, Snake and the rest) is one tap away. The T-Deck and Tanmatsu already had this.
Blocked list is easier to reach: open it from Contacts (the overflow menu) and from the chat settings screen, not only from where it used to live.
Portuguese (Brazil) is now a UI language, which brings the total to twelve. Community translation.
# --- Fixed ---
Adverts sent from the touch screen are now relayed by region-scoped repeaters. The advert went out without a region tag, so a repeater set to a single region dropped it, while the same advert sent from the phone app got through. The device now tags its flood advert the same way the phone companion does. (Issue #68, reported by EricMW61.)
A message could be transmitted on the wrong channel. After you added or removed channels the cached channel index could drift, so a message typed in one channel was sent on another channel's key. It looked correct on your own screen but arrived in the other channel. The send path now matches the target channel by name at the moment of sending, so this can no longer happen.
Room server logins could time out when the only route to the server was through a region-scoped repeater. A new opt-in toggle, "Scope direct messages to region" under Radio and Mesh, in the Signal section, tags your direct, login and admin messages with your region so a region-only repeater will relay them. It is off by default, so cross-region messaging is unchanged for anyone who does not need it. (Issue #64, reported by randelreiss.)
The Wi-Fi scan could come back empty. If a scan ran while the device was already connected, the automatic reconnect could cancel it mid-sweep and the list returned zero networks. The scan and the reconnect no longer fight over the radio, and the SSID list loads reliably again.
# --- Under the hood ---
Flood scoping was reworked so channel floods and direct floods are handled separately. Channel and group messages stay tagged with your region scope so public channels remain contained, while direct messages, logins and admin traffic stay unscoped by default to keep cross-region messaging working. The new region-scope toggle opts the direct traffic into the region tag (issue #64), and the advert path was moved onto the same scoping the phone companion already used (issue #68).
The Spectrum app and the mesh share one radio. While Spectrum is open it takes ownership of the SX1262 so the mesh loop does not re-tune or re-arm receive underneath the sweep, and leaving the app restores the mesh radio settings and resumes normal receive. The sweep also waits out the chip's RSSI settle time after each retune and takes a short peak reading per step, so the trace shows real energy instead of the reset floor.
A shared flag now tells the main loop when a Wi-Fi scan is running, so the periodic reconnect does not disconnect and reconnect during a sweep, and auto-reconnect is paused for the length of the scan.
The Heltec V4.3 front-end module (KCT8103L) is now driven for receive with its low-noise amplifier behind the new setting. This is the large amplifier and it is separate from the SX1262's own internal RX-boost bit, which is only a fraction of a dB.
The new settings (per-channel mute, custom sounds, saved Wi-Fi networks, the high-gain and region-scope toggles, and the trackball-navigation default) are stored with versioned migrations, so updating from an earlier beta keeps your existing settings.
# --- Changed ---
Trackball and keypad navigation is off by default now and marked experimental, because it still has rough edges. With it off you get the on-screen cursor as before. When it is on it can now reach the top-bar buttons and the back and cog buttons on settings and tool pages.
First-time setup no longer has a Wi-Fi step. Instead it explains that the device can run Wi-Fi and Bluetooth at the same time, as a standalone radio and a phone companion together, and that you set those up later in Settings.
RF Monitor and Spectrum now use the title bar with a back button, the same as the settings pages.
# --- Also ---
Everything from beta_19 is included.
+16
View File
@@ -0,0 +1,16 @@
# beta_21 (one user-facing note per non-blank, non-# line; # lines are section comments)
# --- New ---
Stable and test update channels. beta_21 is the first stable build. On devices that update over Wi-Fi there is now a "Get test builds (beta)" switch on the About screen: leave it off to stay on stable releases, or turn it on to receive test builds earlier — it switches both the "update available" check and the firmware you install to the test channel. You can go back to stable at any time.
MQTT bridge (highly experimental, off by default). An opt-in bridge that forwards the messages your node receives to an MQTT broker of your choice, so you can log your mesh or wire it into other tools. It is gated behind a privacy consent you have to tick, direct messages are excluded unless you deliberately enable them, and the payload can be sealed with an encryption key so only you can read it. Use a broker you control, never a public one. This is experimental and may change. Contributed by Samuel Coustet (@samuelcoustet, PR #71), reworked for privacy.
Portugal (Narrow) region preset, so Portuguese users can pick the local defaults in one tap. (Issue #74, requested by Salgueiron.)
Saved-contacts counter. The Contacts overflow menu now shows how many contacts you have saved out of the maximum it can hold (for example 42 / 2000). (Issue #72, asked by Buko84.)
# --- Fixed ---
The signal probe never travels past the first node now. The "auto-discover" signal pulse, and the probe behind the Signal popup, are sent strictly zero-hop, so a repeater can no longer re-flood them across the mesh. The probe only measures the link to whatever hears it first, which is what it was always meant to do.
Your most relevant contacts now show when you have a lot of them. The on-screen contact list is capped for performance, but it was trimming the list before sorting it, so some contacts could drop out of view. It now sorts first, shows the closest matches, and adds a "+N more — search to narrow the list" line at the bottom. (Issue #73, reported by 1nerdherder.)
The blocked-users list opened from Contacts now shows the proper two-line title bar with a back button, instead of an unlabelled screen.
The Contacts overflow popup fits the screen again after the saved-contacts counter was added.
# --- Also ---
Everything from beta_20 is included.
+8
View File
@@ -0,0 +1,8 @@
# beta_22 (TEST build — one user-facing note per non-blank, non-# line; # lines are section comments)
# --- Fixed ---
The signal probe reads a real signal again. In beta_21 the probe was changed to a zero-hop advert so it could never be re-flooded across the mesh — but nothing answers a zero-hop advert, so the signal reading stopped updating. It now sends a directed trace "ping" to your nearest repeater instead: the repeater replies directly (it still never floods the mesh) and the device reads the link signal from that reply. So you get both — no mesh flooding, and a live signal again. Thanks to Tarmo for spotting this and suggesting the fix.
Contacts discovered while your phone is connected now show on the device too. If the T-Deck was connected to the MeshCore phone app over Bluetooth and heard a new node, the node appeared on the phone but not on the device's own screen, and the Contacts list did not refresh. The device now updates its own Contacts list and notification whether or not a phone app is connected. (Issue #73, reported by 1nerdherder.)
# --- Also ---
This is a test-channel build (opt in with "Get test builds" on the About screen). Everything from beta_21, the first stable, is included.
+11
View File
@@ -0,0 +1,11 @@
# beta_23 (TEST build — one user-facing note per non-blank, non-# line; # lines are section comments)
# --- Fixed ---
Bluetooth companion reliability, especially messages and repeater admin. When a phone or Mac was connected over Bluetooth, the device was sending it a log entry for every LoRa packet it heard — on a busy mesh that swamped the Bluetooth link and starved the frames that actually matter. The device no longer sends that packet log over Bluetooth (USB and Wi-Fi companions still get it), so incoming messages reach the app and repeater / room-server admin (Manage Regions, saving parameters) stops timing out and dropping the connection. (Issues #46 and #54.)
# --- Also in this test line (carried from beta_22) ---
The signal probe reads a real signal again: it sends a directed trace "ping" to your nearest repeater, which replies, instead of a zero-hop advert that nothing answers. Thanks to Tarmo for spotting it.
Contacts discovered while your phone is connected now also show on the device's own screen, not just in the phone app. (Issue #73.)
# --- Also ---
This is a test-channel build (opt in with "Get test builds" on the About screen). Everything from the stable beta_21 is included.
+7
View File
@@ -0,0 +1,7 @@
# beta_24 (TEST build — one user-facing note per non-blank, non-# line; # lines are section comments)
# --- Fixed ---
The signal probe now reads a real signal to your nearest repeater. It sends the standard mesh node-discovery request that repeaters actually answer, instead of the trace packet from the last test build that they ignored, so the signal reading updates again. This is the same request the Ultra and KiekR apps use. Thanks to Tarmo for decoding the exact packet.
# --- Also ---
This is a test-channel build (opt in with "Get test builds" on the About screen). Everything from the stable beta_21 and the earlier test builds is included.
+21
View File
@@ -0,0 +1,21 @@
# beta_25 (STABLE — rolls up the beta_22..25 test builds on top of the previous stable, beta_21.
# One user-facing note per non-blank, non-# line; # lines are section comments.)
# --- Fixed ---
The signal probe reads a live signal to your nearest repeater again. It sends the standard mesh node-discovery request that repeaters actually answer (the same one the Ultra and KiekR apps use), so the signal reading updates. Thanks to Tarmo for decoding the exact packet.
Bluetooth companion reliability, especially messages and repeater / room-server admin. The device no longer floods the Bluetooth link with a per-packet log (USB and Wi-Fi companions still get it), so incoming messages reach the app and admin actions like Manage Regions stop timing out. (Issues #46 and #54.)
Contacts show up right away. A node you discover, even while you're on another screen or one the phone app adds over Bluetooth, now appears in your contact list immediately instead of only after you change the sort. Thanks to 1nerdherder for the report. (Issue #73.)
Manual telemetry and status requests now work on the first tap instead of needing a second. Thanks to Dan Vybiral (@Vybo) for the fix. (Issue #81.)
On the emoji picker and quick-chat replies, pressing Esc or the red X now closes just the popup instead of the whole chat screen.
Lock screen: you can now unlock the device after the screen wakes from an incoming message.
# --- New ---
New "Advertise on boot" option in the Advertise app (off by default): turn it on to send one advert when the device powers on, so nearby nodes refresh your details after a reflash. (Issue #76.)
# --- Tanmatsu ---
Tanmatsu: Wi-Fi map tiles now download and display, cached to the microSD card.
Tanmatsu: contacts and message history now survive a reboot (moved to the microSD card, so keep a card inserted).
Tanmatsu: fixed the crash that stopped the app from booting; popups now fit the screen and scroll, and keyboard navigation stays inside an open popup.
# --- Also ---
This is the new stable build, promoted from the beta_25 test channel. It includes everything from the beta_22, beta_23, beta_24 and beta_25 test builds.
+8
View File
@@ -0,0 +1,8 @@
# beta_26 (TEST) — storage-reliability fix on top of the current stable (beta_25).
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Fixed ---
Fixed a reboot loop that could hit while the device saved its contact list. Internal-flash housekeeping during a save could freeze the device long enough to trip the watchdog and restart it; that save no longer trips it. Thanks to the crash report that pinned it down.
# --- Improved ---
On devices with a microSD card, contacts and channels are now kept on the card (like chat history and map tiles already are). That frees the small internal flash and puts the frequently-rewritten files on the more reliable card. Your existing contacts move to the card automatically the first time; your identity and settings stay in internal flash, so the node is unchanged.
+15
View File
@@ -0,0 +1,15 @@
# beta_27 (STABLE — rolls up the beta_26 + beta_27 test builds on top of the previous stable, beta_25.
# One user-facing note per non-blank, non-# line; # lines are section comments.)
# --- Fixed ---
Fixed a reboot loop that could hit while the device saved its contact list. Internal-flash housekeeping during a save could freeze the device long enough to trip the watchdog and restart it; that save no longer trips it. Thanks to the crash report that pinned it down.
Devices installed under the Launcher no longer show the on-device "Install update" button. That update path only works on a standalone flash; under the Launcher it failed with "won't fit: Bad Size Given". The "update available" note stays, but you update through the Launcher instead. Thanks to Keith (KM1USR) for the report.
# --- New ---
Keyboard backlight brightness control on the T-Deck: a live slider plus Off / 25 / 50 / 75 / Max presets in Settings > Keyboard. It dims smoothly (fine-grained at the low end), applies to the on and auto modes and the new-message flash, and survives a reboot. Thanks to Yazutsu (PR #85).
# --- Improved ---
On devices with a microSD card, contacts and channels are now kept on the card (like chat history and map tiles already are). Your existing contacts move over automatically on first boot; your identity and settings stay in internal flash, so the node is unchanged. Keep the card inserted afterwards - the contact list lives on it, and an older firmware won't look there if you ever downgrade.
# --- Also ---
This is the new stable build, promoted from the beta_27 test channel. It includes everything from the beta_26 and beta_27 test builds.
+13
View File
@@ -0,0 +1,13 @@
# beta_28 (TEST) — room-server session fix + the wyvern.red feedback batch, on top of stable beta_27.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Fixed ---
Room servers no longer go one-way "frozen". The device now keeps its room login session alive in the background and automatically logs back in when the session drops, so posts keep being delivered and new room messages keep arriving. There is also a new "Log in again" option in the room chat's menu, and a clear warning when the room only granted you read-only access (posts would previously just vanish). Thanks to EricMW61 for the report (issue #89).
The screen now truly switches off in standby. Before, only the backlight went dark while the panel kept displaying the last image - the actual cause of the LCD ghosting / burn-in some of you noticed. The panel itself now sleeps, and on wake your screen is back instantly. Also: a lit lock screen now always dims on every board, a screen woken by a message re-darkens after 10 seconds, and the lock-screen clock drifts a few pixels to avoid ghosting. Thanks to wyvern.red for pinning this down.
The on-device "Install update" now also hides on mixed or older partition layouts where an update could crash the device halfway through (found via a user crash report - thanks!).
# --- New ---
Compact messages (IRC style): a new toggle in chat settings shows one dense line per message instead of bubbles, fitting two to three times more history on screen. Off by default. (wyvern.red's suggestion.)
Clearer delivery ticks: an up-arrow means sent but not yet confirmed, a double check means the other side confirmed it, and a failed message now says "tap to resend" - one tap resends it. (wyvern.red)
Keyboard navigation: the scroll keys (F/C) now zoom the map, and backspace in an empty message box exits typing mode so the navigation keys work again. (wyvern.red)
"Reset path" is now also in the chat's own menu next to Blocked users, so you can force a fresh route without going through Contacts.
+17
View File
@@ -0,0 +1,17 @@
# beta_29 (TEST) — clock hardening for room servers, BLE repeats-heard fix, deeper SD chat history, one-screen popups. On top of beta_28.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Fixed ---
Room logins can no longer be silently locked out by the device clock. Room servers quietly reject anything older than the newest timestamp they have seen from you, so a clock that stepped backwards (a reboot without GPS or phone around, or a sync correcting a fast clock) black-holed every Join with zero feedback. The device now remembers the newest timestamp it has used across reboots so it can never fall behind itself, a Join that gets no reply shows a clear error after 20 seconds (including what the device thinks the time is) instead of spinning forever, and the device warns you when its clock and the room server's clock disagree. Thanks to EricMW61 for the follow-up testing on issue #89.
"Repeats heard" works again over Bluetooth. The companion app counts repeats from the per-packet RX log, which beta_23 stopped sending over BLE to fix congestion. The firmware now recognises packets that are repeats of your own messages and lets exactly those through to BLE, so the counter works and the congestion fix stays. Thanks to daryldakine for the clean bisect (issue #94).
Messages sent from the phone app through the device now also appear on the device itself, as your own outgoing message in that channel. This worked for direct messages but never for channels.
Deleting a chat or channel now sticks. Deleted messages could survive in storage and resurrect the chat later, and removing a channel could miss the underlying channel entry so the thread came right back.
Settings pages no longer jump down when opened on keyboard-navigation devices, and the red update dot can no longer steal the selection from the About button.
The update check no longer shows "couldn't reach the update server" for six hours after one failed attempt. It now waits for Wi-Fi to actually have an address and retries within a minute.
The Tanmatsu About page now shows the real firmware version instead of a stale hardcoded one.
# --- New ---
Much deeper chat history on devices with an SD card: up to 5000 messages instead of 500, with date separators (Today, Yesterday, day names) between messages from different days. Note for testers: if you later downgrade below beta_29, the older build will not read the larger history file and will start with an empty history.
Chat and channel rows in the messages tab now use the same compact style as the Contacts tab, fitting more conversations on screen.
The chat or channel settings sheet (long-press or the gear) now fits on one screen, laid out like the contact menu, instead of scrolling.
Compact chat mode is easier to read: messages alternate between two background tones.
+11
View File
@@ -0,0 +1,11 @@
# beta_30 (TEST) — the big-mesh sluggishness fix + a much faster Spectrum analyzer. On top of beta_29.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Fixed ---
The periodic multi-second freezes on busy meshes are gone. Saving the contact list to storage took up to 3 seconds at ~570 contacts and ran on the UI thread every couple of minutes, which is exactly the trackball and touch hesitation people felt since beta_25. The save now writes the same data in a few large chunks instead of thousands of tiny ones, cutting it to a fraction. Thanks to guinnessbear for the report and Yazutsu for the precise measurements that pinned this down (issue #82).
The Contacts tab no longer rebuilds itself every 60 seconds just to refresh the "heard 2h ago" labels - they update in place now. That rebuild cost over a second on large contact lists and could yank the list while you were scrolling.
A burst of adverts can no longer queue several back-to-back Contacts rebuilds; they are now coalesced.
# --- Improved ---
The Spectrum analyzer feels live now: the waterfall gets a new line about four times per second instead of once per sweep, the trace advances across the band as it sweeps (like a bench analyzer), and a full sweep is about 20 percent faster.
The Spectrum trace also scales itself to the signal now: the chart tracks the live minimum and maximum, jumping out instantly for a strong signal (no more clipping flat at the top) and easing back once it is gone.
+9
View File
@@ -0,0 +1,9 @@
# beta_31 (TEST) — the new chats tab: avatars, message previews, custom channel icons. On top of beta_30.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- New ---
The chats tab has a fresh look: each conversation now shows a round avatar in that chat's signature colour (the same colour its bubbles use) with the first two letters of the name, the last message previewed under the name, the time top right and the unread count below it. Compact chat mode keeps the dense single-line rows instead, so both styles are available.
Channels can have a custom icon: open the channel's settings (long-press or the gear) and tap "Chat icon" to pick any emoji as its avatar. Long-press the same entry to go back to the automatic letters. The choice is remembered per channel.
# --- Fixed ---
Long chat names no longer wrap onto the message preview underneath.
+9
View File
@@ -0,0 +1,9 @@
# beta_32 (TEST) — the Wi-Fi freeze fix: a stale phone/web connection can no longer stall the device. On top of beta_31.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Fixed ---
The 1-2 second freezes every ~10 seconds some users saw with Wi-Fi on are gone. When a phone app or web client was connected over Wi-Fi and that connection went stale (phone asleep, walked out of range), every received mesh packet made the device wait on the dead connection before the UI could continue. The device now only writes to a connection when it can accept data immediately, and a connection that stays unresponsive for 10 seconds straight is dropped so the client can reconnect cleanly.
Saving chat history could briefly hitch the UI on busy meshes: the history file now writes in a few large chunks instead of thousands of tiny ones (the same treatment the contact list got in beta_30), and background saves are spaced further apart while messages stream in.
# --- New ---
The About page now shows recent loop stalls (anything over 0.2 seconds, newest first), so freeze reports can be confirmed or ruled out at a glance.
+7
View File
@@ -0,0 +1,7 @@
# beta_33 (TEST) — the MQTT freeze fix + the About page no longer stalls itself. On top of beta_32.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Fixed ---
The freezes with MQTT enabled are gone. Connecting to the broker (DNS lookup, TCP connect, login) could block the device for 2-10 seconds and retried every 15 seconds while the broker was unreachable, all on the UI thread. Connection attempts now run fully in the background, and writes to a broker that stops responding are skipped instead of waited on (the same treatment beta_32 gave phone/web connections). Tip: if your bridge keeps reconnecting, check the broker address and credentials - a healthy connection does not retry.
The About page caused a ~0.4 second hitch every second while it was open: computing the firmware image size checksums the whole ~3 MB app in flash and ran twice per refresh. It is now computed once per boot, so About (and its stall list) no longer disturbs the very measurements it shows.
Favoriting a contact when the favorites list is full (16) now says "Favorites full (max 16)" instead of the incorrect "Removed from favorites".
+11
View File
@@ -0,0 +1,11 @@
# beta_34 (TEST) - buffered receive: the missed-messages fix, ON by default on this test build. On top of beta_33.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- New ---
This build changes how the device collects packets from the LoRa radio, and the new way is ON by default so the test channel can prove it. Background: the radio chip holds only one received packet at a time, and until now the firmware only collected it when the main loop got around to it, the same loop that draws the screen. If the interface kept the loop busy while two packets arrived back to back, the first one was silently overwritten. That is the "my device missed a message another device right next to it heard" problem some of you reported, and why it affected this firmware but not stock MeshCore, which has no screen to draw. A small dedicated background task now collects every packet within about a millisecond of it arriving, no matter what the interface is doing.
Because the receive path is the heart of the device, this ships with a safety hatch: if you see anything odd with receiving, sending, or the Spectrum analyzer, turn off "Buffered receive (experimental)" in Settings > Radio & Mesh (applies instantly, no reboot) and you are back on the old path. Please report it either way, that is exactly what the test channel is for.
The About page now shows LoRa receive counters (heard / read / late-lost). "late-lost" counts packets the radio heard but the firmware failed to collect in time. With buffered receive on it should stay at zero. If you turn the toggle off on a busy mesh you may watch it creep up, which is the old bug happening live.
# --- Fixed ---
Messages sent by wadamesh no longer carry a few stray bytes at the end that stock MeshCore devices and some companion apps displayed as garbage characters after the text (issue #13).
A GPS module reporting a bogus date can no longer drag the device clock back to the year 1902 (core clock guard).
+11
View File
@@ -0,0 +1,11 @@
# beta_35 (TEST) - V4 breathing room: freezes fixed, 30 KB of internal RAM back, crash-safe settings. On top of beta_34.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Fixed ---
Heltec V4: multi-second freezes right after receiving messages are gone, including the screen refusing to wake from dark mode. Saving chat history to the internal flash could stall the device for up to 6 seconds (the V4 has no SD card, and internal flash pauses for housekeeping); that save now runs on a background task, so the screen and touch stay responsive no matter what storage is doing.
Turning Bluetooth on while Wi-Fi is running no longer reboots the device when memory is tight: the switch now checks free memory first and tells you "Not enough free memory for Bluetooth. Turn Wi-Fi off first." instead of crashing.
The same protection applies the other way around: turning Wi-Fi on with Bluetooth active used to claim "Wi-Fi on" while the radio silently never started. It now either really starts or tells you why it cannot.
Settings could vanish for a single boot after an unlucky reboot (the device came up with a default name once, then recovered). Settings writes are now crash-safe: a reboot or power cut at any moment leaves at least one intact copy on storage, the loader self-heals from it, and a failed save now says "Couldn't save the name to storage" instead of pretending it worked.
# --- Improved ---
About 30 KB of the ESP32's scarce internal RAM has been freed by moving buffers to the external PSRAM and dropping unused USB components from the build. This is the headroom that makes Wi-Fi and Bluetooth run together comfortably again, especially on the Heltec V4.
+13
View File
@@ -0,0 +1,13 @@
# beta_36 (TEST) - Launcher SD storage really works now, Wi-Fi settings redesign, symbol passwords, lock-screen unread count. On top of beta_35.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Fixed ---
The "Store data on SD" toggle is now actually honored after a reboot (fix contributed by scratchdiver, PR #123). On Launcher installs the setting silently reverted to internal storage every boot, which also meant those devices kept the slow internal-flash writes. If you run wadamesh under the Launcher and your mesh is busy, this one is for you: flip the toggle once and contacts and settings really move to the SD card.
Turning "Store data on SD" off works reliably now too, including on Launcher installs (follow-up to PR #123).
Passwords with special characters can now be entered everywhere: long-press any settings field, including the Wi-Fi password, for the Cut / Copy / Paste / All / Sym menu. Sym opens a picker with the characters the on-screen keyboard does not have (issue #122). Double-tap selects a word.
# --- New ---
The Wi-Fi network screens (join a network, hidden network, saved-network details) are full-screen pages now instead of small popups: same style as the other settings pages, title in the top bar, tap the bar to go back, and everything scrolls properly with the keyboard open.
The lock screen shows an envelope with the number of unread messages under the clock, so you can check for news without unlocking (idea from issue #93). It disappears when there is nothing unread.
For Launcher installs: a "Save update bin to SD" button on the About page downloads the latest firmware of your selected channel into a BINS folder on the SD card, named with the version and channel, ready to flash from the Launcher. The test-builds toggle is now visible on Launcher installs as well.
New region preset "Australia (Mid)": 915.075 MHz, 125 kHz, SF9, CR5 (requested in issue #121).
+15
View File
@@ -0,0 +1,15 @@
# beta_37 (TEST) - Tanmatsu ALT accents + language switching, GPS quick reply, T-Deck touch self-heal, SD history reliability. On top of beta_36.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- New ---
Tanmatsu: hold ALT and press a letter to open the accent picker (a with ALT gives an accent popup, just like long-press on the touch boards). Keep ALT held and press the letter again to cycle through the options; release ALT to insert the highlighted one. Requested by jochentj in issue #129.
Tanmatsu: double-tap the space bar to switch between your enabled keyboard languages, same as on the T-Deck.
Accented letters on the Tanmatsu now render at full size at the Large and Huge UI scales instead of noticeably smaller (issue #129). Made possible by moving all boards to compressed UI fonts, which also frees a chunk of firmware space.
Your GPS position is now the first row in the quick-reply picker, so you can send your current coordinates with one tap (contributed by Yazutsu, PR #125).
While in a chat or channel, the top bar shows the active keyboard language next to the clock (only when more than one layout is enabled), so you can see what double-tap-space switched to.
# --- Fixed ---
The keyboard-backlight "Off" preset now actually switches the backlight off and stays off, instead of leaving the previous mode running (contributed by Yazutsu, PR #88).
Chat history saves to the SD card are more robust: files are written atomically and a fallback save path covers the background worker not being armed yet, so a badly timed reboot can no longer truncate your message history (contributed by scratchdiver, PR #135).
T-Deck: if the touch controller glitches into a stuck "phantom finger" state (everything looked frozen, touch dead, trackball clicks eaten, and the screen never timed out), the driver now detects it and recovers within seconds. Previously only a full power cycle would clear it.
T-Deck: touch initialisation at boot now retries for a few seconds instead of giving up after a single attempt. A slow-to-wake touch controller could previously cost you touch AND keyboard for the whole session.
+17
View File
@@ -0,0 +1,17 @@
# beta_38 (TEST) - Full-history chat scrolling, message delete, two new boards, storage integrity fixes. On top of beta_37.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- New ---
Chat scrolling is fully virtualized (contributed by scratchdiver, PR #130): a chat now scrolls through its ENTIRE stored history, up to 5000 messages on SD-card devices, smoothly in both bubble and compact mode, instead of only the most recent rows. Several LVGL crash fixes came along with it.
Long-press any message for a new Delete option that removes just that message. The message menu now lays its buttons out two per row so it always fits on one screen.
The chat and channel settings sheet gains "Delete history": wipes the whole conversation after a confirmation, while the channel membership or contact stays.
The in-chat jump buttons are now slim arrows tucked against the right edge of the screen: fully visible while you scroll, fading to half opacity a second after you stop.
ThinkNode M9 hardware support is complete (contributed by ded, PR #138): GPS, microSD, buzzer, backlight control, lock screen, long-press context menus, and a d-pad-driven setup wizard. His fixes for focus scrolling in nested pages and the lock-screen paint order benefit every keyboard-nav board.
New board in the source tree: RAK WisMesh Tap V2 (contributed by Ethac.chen, PR #136), with a 30+ fps display driver. Prebuilt images follow once the web-flasher integration lands.
Tanmatsu: the app now builds size-optimized, roughly 300 KB smaller, leaving real headroom under the launcher's app-size limit for future features.
# --- Fixed ---
Messages no longer vanish when you reboot the device from the phone app (reported by Leon P). The history writer batches saves up to 30 seconds apart, and the app's reboot command skipped the final save that every on-device reboot path does - so the newest messages, read or unread, were lost. The reboot command now saves first.
T-Deck: turning on "Store data on SD" now migrates your existing profile, settings and identity to the card FIRST. Upgrading to beta_36/37 with the toggle already on could adopt an empty card and boot as a brand-new node while your real profile sat orphaned on internal flash.
T-Deck: for anyone already hit by that: Set -> General -> "Copy internal data to SD" restores the profile from internal flash onto the card (confirmation, then automatic reboot). Until you run it, toggling "Store data on SD" OFF and rebooting also brings the old profile back.
Tanmatsu: profile name, settings and the node identity now persist reliably across reboots. They lived on the internal flash partition whose metadata layer is unreliable on this board; they now live on the SD card with everything else, and existing data is rescued automatically on first boot.
+11
View File
@@ -0,0 +1,11 @@
# beta_39 (TEST) - Translations, deletes that stick and are fast, emoji fixes. On top of beta_38.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- New ---
Big translation pass: hundreds of previously-English strings across menus, settings, dialogs and the setup flow are now translated into all 11 non-English languages (Dutch, German, French, Spanish, Italian, Russian, Ukrainian, Bulgarian, Serbian, Greek, Brazilian Portuguese). Menu rows that carry an icon now translate too, instead of silently falling back to English. Switch language under Settings.
ThinkNode M9 and RAK WisMesh Tap V2 can now be installed straight from the web flasher.
# --- Fixed ---
Deleting a message, or clearing a whole chat, now sticks: it survives a reboot or a hardware reset instead of coming back (reported by Leon P and MrWeavis). The delete used to sit in a save that was batched up to 30 seconds later, so a reset in that window undid it.
Deleting is also much faster now. The chat history is written compactly - only the messages you actually have, instead of the full 5000-slot ring every time - so a delete, a history wipe, or a reboot no longer pauses the screen while it saves. Normal message saving is lighter too.
Emoji picker: the food and object emoji that showed as empty boxes (umbrella, coffee, pizza, cake, rocket, camera, phone, laptop, calendar, antenna, e-mail, house, car, watch) now render properly - they were listed but never baked into the font.
+32
View File
@@ -0,0 +1,32 @@
# beta_40 (STABLE) - the first stable since beta_35. Rolls up everything from beta_36 through beta_40: reliable SD storage, message delete + full-history scrolling, a big translation pass, two new boards, and a pile of storage/perf/stability fixes.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- New ---
Big translation pass: hundreds of previously-English strings across menus, settings, dialogs and the setup flow are now translated into all 11 non-English languages (Dutch, German, French, Spanish, Italian, Russian, Ukrainian, Bulgarian, Serbian, Greek, Brazilian Portuguese). Menu rows that carry an icon translate too. Switch language under Settings.
Chat scrolling is fully virtualized (contributed by scratchdiver, PR #130): a chat now scrolls through its ENTIRE stored history, up to 5000 messages on SD-card devices, smoothly in both bubble and compact mode, instead of only the most recent rows.
Long-press any message for a Delete option that removes just that message; the message menu lays its buttons two per row so it fits on one screen.
The chat and channel settings sheet gains "Delete history": wipes the whole conversation after a confirmation, while the channel membership or contact stays.
The in-chat jump buttons are slim arrows tucked against the right edge: fully visible while you scroll, fading to half opacity a second after you stop.
ThinkNode M9 hardware support is complete (contributed by ded, PR #138): GPS, microSD, buzzer, backlight control, lock screen, long-press context menus, and a d-pad-driven setup wizard. It can be installed straight from the web flasher.
New board: RAK WisMesh Tap V2 (contributed by Ethac.chen, PR #136), with a 30+ fps display driver, also installable from the web flasher.
The Wi-Fi network screens (join a network, hidden network, saved-network details) are full-screen pages now instead of small popups, matching the other settings pages and scrolling properly with the keyboard open.
The lock screen shows an envelope with the number of unread messages under the clock, so you can check for news without unlocking (idea from issue #93).
Passwords with special characters can be entered everywhere: long-press any settings field, including the Wi-Fi password, for a Cut / Copy / Paste / All / Sym menu. Sym opens a picker with the characters the on-screen keyboard lacks (issue #122). Double-tap selects a word.
For Launcher installs: a "Save update bin to SD" button on the About page downloads the latest firmware of your selected channel into a BINS folder on the SD card, ready to flash from the Launcher. The test-builds toggle is visible on Launcher installs too.
New region preset "Australia (Mid)": 915.075 MHz, 125 kHz, SF9, CR5 (requested in issue #121).
Your GPS position is now the first row in the quick-reply picker, so you can send your current coordinates with one tap (contributed by Yazutsu, PR #125).
Tanmatsu: hold ALT and press a letter to open the accent picker; keep ALT held and press again to cycle, release to insert (requested by jochentj, issue #129). Double-tap the space bar to switch between your enabled keyboard languages, same as the T-Deck.
While in a chat, the top bar shows the active keyboard language next to the clock when more than one layout is enabled.
# --- Fixed ---
The "Store data on SD" toggle is now actually honored after a reboot (fix contributed by scratchdiver, PR #123). On Launcher installs it silently reverted to internal storage every boot, which also kept the slow internal-flash writes. Turning it off works reliably now too.
Turning on "Store data on SD" migrates your existing profile, settings and identity to the card FIRST, so upgrading no longer risks adopting an empty card and booting as a brand-new node. If you were already hit by that, Settings -> General -> "Copy internal data to SD" restores the profile from internal flash.
Card-less devices (Heltec V4, and any board without an SD card) no longer freeze for several seconds at a time. A busy mesh re-writes the whole contacts file to internal flash on every advert refresh, and that flash garbage-collection stalled the whole device; contact saves are now coalesced so only real changes (a new or removed node) are written promptly.
Deleting a message, or clearing a whole chat, now sticks: it survives a reboot or a hardware reset instead of coming back (reported by Leon P and MrWeavis). Deleting is also much faster - chat history is written compactly, only the messages you actually have, so a delete, a history wipe, or a reboot no longer pauses the screen while it saves.
Messages no longer vanish when you reboot the device from the phone app (reported by Leon P): the app's reboot command now saves chat history first, like every on-device reboot path already did.
Chat history saves to the SD card are more robust: files are written atomically with a fallback save path, so a badly timed reboot can no longer truncate your message history (contributed by scratchdiver, PR #135).
Longer translated labels (French, German, etc.) that used to clip or wrap now shrink to fit: the message action menu, confirmation dialogs, and the app-drawer tiles all keep their text on one line. The signal card's "tap for details" hint no longer overlaps in other languages.
Emoji picker: the food and object emoji that showed as empty boxes (umbrella, coffee, pizza, cake, rocket, camera, phone, laptop, calendar, antenna, e-mail, house, car, watch) now render properly.
Tanmatsu: profile name, settings and the node identity persist reliably across reboots (moved off the unreliable internal-flash partition onto the SD card, with existing data rescued on first boot). Accented letters render at full size at the Large and Huge UI scales. The About page shows the correct firmware version now.
T-Deck: if the touch controller glitches into a stuck "phantom finger" state (touch dead, trackball clicks eaten, screen never timing out), the driver detects it and recovers within seconds instead of needing a full power cycle. Touch initialisation at boot also retries for a few seconds instead of giving up after one attempt.
The keyboard-backlight "Off" preset now actually switches the backlight off and stays off (contributed by Yazutsu, PR #88).
+10
View File
@@ -0,0 +1,10 @@
# beta_41 (TEST) - experimental web control: view and drive the wadamesh UI from a phone or desktop browser over Wi-Fi. Two new apps, VNC and REMOTE.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- New ---
New VNC app (in the app drawer, between Advertise and Signal): it mirrors the live device screen into a web browser over Wi-Fi and lets you drive it. Taps and typing in the browser control the device, and anything that changes on the device shows up in the browser. Turn it on, then open http://<device-ip>:8765/ from any browser on the same network. The app page itself is scrollable.
New REMOTE app: a headless mode that renders the whole UI at a larger, browser-friendly resolution and serves it over Wi-Fi, while the device's own screen drops to a placeholder showing the address to open. Meant for driving a device as a web client, and as groundwork for screenless hardware. Turning it on or off reboots the device. On the web page a Rotate button flips between landscape (desktop) and portrait (phone); on the device, double-tap the space bar to leave remote mode.
Both features are served by the device itself over plain Wi-Fi - no phone app, no account, no cloud, just a browser on the same network.
# --- Note ---
This is an experimental first cut, and an honest heads-up from Kaj: for me the remote UI still feels too slow, and I will most likely move toward a dedicated, lighter remote client instead of streaming the entire live UI. It is in this test build mainly because community feedback on it would be genuinely useful - if you try it, let us know how it runs for you and what you would actually want from a web or remote client.
+9
View File
@@ -0,0 +1,9 @@
# beta_42 (TEST) - fixes for the beta_41 REMOTE mode: it works on the Heltec V4 now, and keyboard-less boards can leave it.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Fixed ---
REMOTE mode now works on the Heltec V4 TFT (and other 2 MB-PSRAM boards) instead of showing a black screen in the browser. Its off-screen renderer needed more free memory than those boards had, so nothing was streamed; the buffers are sized to fit now, and the render is a bit smaller and faster as a result. VNC was never affected and already worked.
Keyboard-less touch boards (Heltec V4, RAK WisMesh Tap) can leave REMOTE mode again: touch and hold the device screen for about 3 seconds. Those boards have no SPACE key, which used to be the only way out on the device.
# --- New ---
The web page has an "Exit remote" button (with a confirmation) that leaves REMOTE mode from any browser, on any board.
+24
View File
@@ -0,0 +1,24 @@
# beta_43 (TEST) - the browser control panel grows into a full remote app (Chats, Contacts, Discovered, Settings), plus a Heltec V4 map-tile fix.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- New: web control panel ---
The browser control panel is now a full remote app - you can run the device from your phone or laptop without ever picking up the T-Deck. Proper Chats, Contacts, Terminal and Settings tabs.
Contacts tab: search, sort and filter your contacts, see each one's distance, coordinates and last-heard age, and tap a contact for the same actions you get on the device (favourite, block, reset path, remove).
Discovered nodes show up in the browser too, each with a one-tap "Add" to save it as a contact - so you can build your whole contact list from the web app.
Chats tab: pop-up notifications (with an optional beep) when a message arrives, and the open chat refreshes on its own as replies come in - no manual reload.
Acknowledgements and repeats-heard now show for messages you send from the web app, the same as on the device.
A Settings page for the everyday options that make sense remotely, including live radio changes.
A quick-command button in the Terminal that drops common commands straight into the input box.
# --- New: device ---
Map options has a "Tile debug overlay" toggle (off by default) that shows a live read-out of the map-tile pipeline, for diagnosing tile problems.
# --- Fixed ---
Heltec V4: map tiles downloaded but only the top of the map rendered and the rest stayed black. The 2 MB-PSRAM V4 was running out of contiguous memory for the tile grid; tiles now reuse a small fixed pool and only load what is on screen, so the whole map fills in smoothly again.
Heltec V4 in remote/VNC mode: typing from a physical keyboard in the browser now works (it previously only worked on the T-Deck).
The remote-access screen on the device is clearer: the IP address is shown at the top, the explanation is shorter and more accurate, the toggles sit above it, and the address box only appears once remote access is on.
The Terminal "help" command now lists every command, on both the device and the web terminal (it was missing a lot).
# --- Changed ---
The web app header now shows the same signal, Wi-Fi, Bluetooth and battery icons as the device status bar, and the title reads WADAMESH.
The contact and chat sort/filter controls open a menu to pick an option instead of cycling through them on each tap.
+15
View File
@@ -0,0 +1,15 @@
# beta_44 (TEST) - an on-device text web browser, tappable links in chat, and a French-keyboard spacebar fix.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- New: on-device web browser ---
New "Web" app: open a URL and read the page as plain text - articles, wikis, docs, plain sites - right on the device. No proxy, no tracking, no JavaScript or images; just the words. Links are tappable, and there are back, forward and refresh buttons.
The Web app needs the memory only the 8 MB boards have (T-Deck, Tanmatsu), so it is hidden on the 2 MB Heltec V4 - that board can't complete an on-device HTTPS handshake.
# --- New: links in chat ---
Links in a chat are now tappable. Tap one for a small menu: "Open in web" loads the page in the on-device browser, and "Create QR" shows a scannable QR code so you can open the link on your phone.
Create QR works on every board, including the Heltec V4 - so even where the browser isn't available you can still bounce a link to your phone.
# --- Fixed ---
French (AZERTY) on-screen keyboard: the spacebar is back in the normal letter view (along with the OK and keyboard-switch keys). You no longer have to switch to the symbols page just to type a space.
Heltec V4: web page fetching and map tiles are more resilient when memory is tight.
Home signal & traffic box: the "tap for details" cue is back at the top of the box.
+24
View File
@@ -0,0 +1,24 @@
# beta_45 (TEST) - three new boards (LilyGo T-LoRa Pager, LilyGo T-Display P4, Heltec V4-R8), plus fixes.
# One user-facing note per non-blank, non-# line; # lines are section comments.
# --- Community ---
Big thanks to @codemonkeybr, who contributed the entire LilyGo T-LoRa Pager port this cycle.
# --- New board: LilyGo T-LoRa Pager (by @codemonkeybr, PR #149) ---
New board: the LilyGo T-LoRa Pager (ESP32-S3) - a QWERTY-keyboard handheld with a rotary encoder and no touchscreen. The whole UI is driven from the keyboard and the encoder, both radio variants are supported (LR1121 and SX1262), and everything was verified on real hardware against a live mesh.
Pager controls: the rotary encoder scrolls and its click opens menus; a universal back gesture, screen lock, keyboard backlight modes, an accent-character picker and an @-mention picker are all keyboard/encoder driven. There is a full shortcut reference on the site.
# --- New board: LilyGo T-Display P4 ---
New board: the LilyGo T-Display P4 (ESP32-P4) - an AMOLED touchscreen handheld. Early port, marked "partially supported": LoRa mesh, chat, the map, GPS and the phone-app companion over Wi-Fi/USB all work. Bluetooth pairing is not available on this board (a limitation of its stock radio-coprocessor firmware); pair over Wi-Fi or USB instead.
T-Display P4: screen brightness and notification sound now work and have Control-Center sliders, and the browser-based screen mirror / remote apps work over Wi-Fi.
# --- New board: Heltec V4-R8 ---
New board: the Heltec WiFi LoRa 32 V4-R8 (8 MB PSRAM) with the Expansion Kit V2 (microSD). Marked "partially supported" while it finishes hardware testing.
# --- Fixed ---
Heltec V4-R8: fixed random hard-freezes that needed a reset - the touch controller was sharing I2C pins with the clock and sensors in a way that could wedge the bus. It no longer does.
Tanmatsu (and other keyboard-only boards): you can now select and edit the Wi-Fi network name and password fields in Wi-Fi settings - the join screen's fields were previously unreachable with the keyboard.
T-Display P4: the clock now sets itself over Wi-Fi even where NTP is blocked, and won't get stuck on a bad date reported by the hardware clock.
# --- Also ---
The flasher site now shows a support badge on every board (fully vs partially supported); hover it for what works.
+205
View File
@@ -0,0 +1,205 @@
#!/usr/bin/env python3
# Bake a few EXTRA Noto colour emoji into src/ui-touch/emoji_data.{c,h} WITHOUT
# regenerating (and re-downloading) the existing 252 — those stay byte-identical,
# so there's no Noto-`main` art drift. Splices new glyph arrays + sorted lookup
# entries into the file in place. Re-run is idempotent (new cps replace, existing
# untouched). PX must match the existing bake (16) and the imgfont in UITask.
#
# python3 scripts/build/add-emoji.py
#
# Source art: googlefonts/noto-emoji png/128 (OFL). RGB565+alpha, swap=0.
import os, re, sys, urllib.request
from PIL import Image
PX = 16
HERE = os.path.dirname(os.path.abspath(__file__))
ROOT = os.path.abspath(os.path.join(HERE, "..", ".."))
OUTDIR = os.path.join(ROOT, "src", "ui-touch")
OUTC = os.path.join(OUTDIR, "emoji_data.c")
OUTH = os.path.join(OUTDIR, "emoji_data.h")
CACHE = os.path.join(ROOT, "data", "emoji-cache")
BASE = "https://raw.githubusercontent.com/googlefonts/noto-emoji/main/png/128/emoji_u{}.png"
os.makedirs(CACHE, exist_ok=True)
# Single-codepoint emoji: (codepoint, noto-filename-stem)
SINGLE = [
(0x26BD, "26bd"), # soccer ball âš½
(0x1F3C8, "1f3c8"), # american football ðŸ
(0x1F5FF, "1f5ff"), # moai 🗿
# objects/food listed in the picker (k_emoji_items) but never baked -> they
# rendered as the notdef box on-device (the beta_38 "emoji tofu"). Bake them.
(0x2614, "2614"), # umbrella with rain
(0x2615, "2615"), # hot beverage
(0x1F355, "1f355"), # pizza
(0x1F382, "1f382"), # birthday cake
(0x1F680, "1f680"), # rocket
(0x1F4F7, "1f4f7"), # camera
(0x1F4F1, "1f4f1"), # mobile phone
(0x1F4BB, "1f4bb"), # laptop
(0x1F310, "1f310"), # globe with meridians (Web app icon)
(0x1F4C5, "1f4c5"), # calendar
(0x1F4E1, "1f4e1"), # satellite antenna
(0x1F4E7, "1f4e7"), # e-mail
(0x1F3E0, "1f3e0"), # house
(0x1F697, "1f697"), # car
(0x231A, "231a"), # watch (sat between car + bulb in the picker, still tofu)
]
# ZWJ sequences baked as ONE combined image, keyed on the lead codepoint, with the
# trailing visible symbol(s) mapped to the zero-width glyph so the whole UTF-8
# sequence renders as the single combined emoji. The bare lead cp (a plain waving
# white flag U+1F3F3) is not offered anywhere in the UI, so reusing it as the key
# is safe. (noto-emoji drops the FE0F variation selectors from png filenames.)
SEQ = [
# (key_cp, noto-stem, [extra cps -> zero])
(0x1F3F3, "1f3f3_200d_26a7", [0x26A7]), # transgender flag ðŸ³ï¸â€âš§ï¸
]
# Country/region flags: a regional-indicator PAIR (e.g. LS = U+1F1F1 U+1F1F8) baked
# as ONE image keyed on the LEAD indicator, the trailing indicator mapped to the
# zero-width glyph (same trick as SEQ). Noto's png/128 ships no flags, so pull the
# flat rectangle from the same Noto project's third_party/region-flags. No bare
# regional indicator is ever offered in the UI, so reusing the lead cp as the key
# is safe — and the picker currently has no other flag using these indicators.
FLAGS = [
# (lead_cp, trail_cp, ISO-3166-alpha-2)
(0x1F1F1, 0x1F1F8, "LS"), # Lesotho
]
def fetch(stem):
fn = os.path.join(CACHE, "u_{}.png".format(stem))
if os.path.exists(fn) and os.path.getsize(fn) > 0:
return fn
for url in (BASE.format(stem), BASE.format(stem + "_fe0f")):
try:
req = urllib.request.Request(url, headers={"User-Agent": "emoji-gen"})
data = urllib.request.urlopen(req, timeout=20).read()
with open(fn, "wb") as f:
f.write(data)
return fn
except Exception:
continue
return None
def fetch_flag(iso):
fn = os.path.join(CACHE, "flag_{}.png".format(iso))
if os.path.exists(fn) and os.path.getsize(fn) > 0:
return fn
url = ("https://raw.githubusercontent.com/googlefonts/noto-emoji/main"
"/third_party/region-flags/png/{}.png".format(iso))
try:
req = urllib.request.Request(url, headers={"User-Agent": "emoji-gen"})
data = urllib.request.urlopen(req, timeout=20).read()
with open(fn, "wb") as f:
f.write(data)
return fn
except Exception:
return None
def to_rgb565a8(img):
# IDENTICAL to gen-emoji-font.py: autocrop transparent margin, bottom-align to
# the text baseline, emit [lo, hi, alpha] per pixel (LV_COLOR_16_SWAP=0).
PAD_BOTTOM = 0
img = img.convert("RGBA")
bbox = img.split()[3].getbbox()
if bbox:
img = img.crop(bbox)
w, h = img.size
avail_h = PX - PAD_BOTTOM
scale = min(PX / w, avail_h / h)
nw, nh = max(1, round(w * scale)), max(1, round(h * scale))
content = img.resize((nw, nh), Image.LANCZOS)
canvas = Image.new("RGBA", (PX, PX), (0, 0, 0, 0))
canvas.paste(content, ((PX - nw) // 2, PX - PAD_BOTTOM - nh))
out = bytearray()
for (r, g, b, a) in canvas.getdata():
v = ((r & 0xF8) << 8) | ((g & 0xFC) << 3) | (b >> 3)
out += bytes((v & 0xFF, (v >> 8) & 0xFF, a))
return out
# ---- bake the new glyphs ----
new_defs = [] # (cp, ename, bytes)
new_entries = [] # (cp, ref)
for cp, stem in SINGLE:
fn = fetch(stem)
if not fn:
sys.exit("FAILED to fetch U+{:X} ({})".format(cp, stem))
new_defs.append((cp, "e_{:x}".format(cp), to_rgb565a8(Image.open(fn))))
new_entries.append((cp, "d_{:x}".format(cp)))
for key_cp, stem, zeros in SEQ:
fn = fetch(stem)
if not fn:
sys.exit("FAILED to fetch combined {} for U+{:X}".format(stem, key_cp))
new_defs.append((key_cp, "e_{:x}".format(key_cp), to_rgb565a8(Image.open(fn))))
new_entries.append((key_cp, "d_{:x}".format(key_cp)))
for z in zeros:
new_entries.append((z, "d_zero"))
for lead_cp, trail_cp, iso in FLAGS:
fn = fetch_flag(iso)
if not fn:
sys.exit("FAILED to fetch flag {} for U+{:X}".format(iso, lead_cp))
new_defs.append((lead_cp, "e_{:x}".format(lead_cp), to_rgb565a8(Image.open(fn))))
new_entries.append((lead_cp, "d_{:x}".format(lead_cp)))
new_entries.append((trail_cp, "d_zero"))
# ---- splice into emoji_data.c ----
src = open(OUTC).read()
TYPE_MARK = "\ntypedef struct { uint32_t cp;"
FUNC_MARK = "const lv_img_dsc_t* emojiGlyphLookup(uint32_t cp) {"
head = src[:src.index(TYPE_MARK)] # header + includes + all glyph defs
func = src[src.index(FUNC_MARK):] # the binary-search getter (verbatim)
# Idempotency: on a RE-RUN, `head` still holds the e_/d_ glyph defs spliced in by a
# PRIOR run (they live before the typedef), so blindly re-appending new_defs would
# redefine them ("redefinition of e_26bd"). Strip any def for a cp we're about to
# re-bake; the lookup table dedups separately (bycp), so this only touches defs.
for _cp, _ename, _data in new_defs:
_hx = "{:x}".format(_cp)
head = re.sub(r"static const uint8_t e_" + _hx + r"\[\] = [^;]*;\n", "", head)
head = re.sub(r"static const lv_img_dsc_t d_" + _hx + r" = [^;]*;\n", "", head)
# Existing lookup entries (includes the FE0F/FE0E/200D -> d_zero rows).
existing = [(int(cp, 16), ref) for cp, ref in
re.findall(r"\{\s*(0x[0-9A-Fa-f]+)u,\s*&(\w+)\s*\}", src)]
bycp = {cp: ref for cp, ref in existing}
for cp, ref in new_entries: # new cps win; never demote a real glyph to zero
if not (ref == "d_zero" and bycp.get(cp, "d_zero") != "d_zero"):
bycp[cp] = ref
entries = sorted(bycp.items())
count = sum(1 for _, ref in entries if ref != "d_zero")
# New glyph array + dsc definitions (appended after the existing ones).
defs = []
for cp, ename, data in new_defs:
defs.append("static const uint8_t {}[] = {{{}}};".format(ename, ",".join(str(b) for b in data)))
defs.append("static const lv_img_dsc_t d_{:x} = {{ {{ LV_IMG_CF_TRUE_COLOR_ALPHA, 0, 0, {}, {} }}, sizeof({}), {} }};"
.format(cp, PX, PX, ename, ename))
out = []
out.append(head.rstrip("\n"))
out.append("")
out.append("\n".join(defs))
out.append("")
out.append("typedef struct { uint32_t cp; const lv_img_dsc_t* dsc; } EmojiGlyph;")
out.append("static const EmojiGlyph kGlyphs[] = {")
for cp, ref in entries:
out.append(" {{ 0x{:X}u, &{} }},".format(cp, ref))
out.append("};")
out.append("const uint16_t kEmojiGlyphCount = {};".format(count))
out.append("")
out.append(func.rstrip("\n"))
out.append("")
open(OUTC, "w").write("\n".join(out))
# ---- header comment count ----
h = open(OUTH).read()
h = re.sub(r"// \d+ Noto colour emoji", "// {} Noto colour emoji".format(count), h, count=1)
open(OUTH, "w").write(h)
print("added {} glyphs -> {} total ({} lookup rows incl zero-width)".format(
len(new_defs), count, len(entries)))
+36 -22
View File
@@ -1,21 +1,27 @@
#!/usr/bin/env python3
# Generate the web-flasher metadata that must roll with every release:
# - version.json : {tag, notes[]} — the site shows this ("what's new")
# - version.json : {tag, channel, notes[]} — the site shows this ("what's new")
# - manifest-tdeck.json : esp-web-tools manifest (its "version" drives the
# - manifest-heltec-v4-tft.json install dialog, so it must equal the tag)
#
# These live next to the rolling bins at firmware.wadamesh.com/latest/, so the
# flasher always reflects the current release without a site redeploy. The
# manifests themselves point at the IMMUTABLE per-tag bins (see below) to dodge
# the latest/*.bin 4h edge cache.
# These live next to the rolling bins in a per-channel feed dir on
# firmware.wadamesh.com (latest/ for stable, latest-beta/ for the test channel),
# so the flasher always reflects the current release without a site redeploy. The
# manifests themselves point at the IMMUTABLE per-tag bins (releases/TOUCH for
# stable, releases/BETA for beta) to dodge the latest/*.bin 4h edge cache.
#
# Usage: gen-flasher-meta.py <tag> <outdir> [notes_file]
# notes_file: one note per non-empty line (plain text); optional.
# Usage: gen-flasher-meta.py <tag> <outdir> [notes_file] [channel]
# notes_file: one note per non-empty line (plain text); optional ("" to skip).
# channel: "stable" (default) or "beta" — picks the immutable archive dir
# (releases/TOUCH vs releases/BETA) the manifests point at, and is
# recorded in version.json so the site/flasher can label the channel.
import sys, json, os
tag = sys.argv[1]
outdir = sys.argv[2]
notes_file = sys.argv[3] if len(sys.argv) > 3 else None
notes_file = sys.argv[3] if len(sys.argv) > 3 and sys.argv[3] else None
channel = sys.argv[4] if len(sys.argv) > 4 else "stable"
archive = "BETA" if channel == "beta" else "TOUCH"
notes = []
if notes_file and os.path.exists(notes_file):
@@ -24,29 +30,37 @@ if notes_file and os.path.exists(notes_file):
os.makedirs(outdir, exist_ok=True)
with open(os.path.join(outdir, "version.json"), "w") as f:
json.dump({"tag": tag, "notes": notes}, f, indent=2)
json.dump({"tag": tag, "channel": channel, "notes": notes}, f, indent=2)
# manifest filename -> (display name, merged-bin filename, chipFamily).
# chipFamily is ESP32-S3 for every board except the P4-class T-Display P4.
BOARDS = {
"manifest-tdeck.json": ("wadamesh — LilyGo T-Deck", "wadamesh-tdeck-merged.bin"),
"manifest-heltec-v4-tft.json": ("wadamesh — Heltec V4 TFT", "wadamesh-heltec-v4-tft-merged.bin"),
"manifest-tdeck.json": ("wadamesh — LilyGo T-Deck", "wadamesh-tdeck-merged.bin", "ESP32-S3"),
"manifest-heltec-v4-tft.json": ("wadamesh — Heltec V4 TFT", "wadamesh-heltec-v4-tft-merged.bin", "ESP32-S3"),
"manifest-thinknode-m9.json": ("wadamesh — ThinkNode M9", "wadamesh-thinknode-m9-merged.bin", "ESP32-S3"),
"manifest-rak-tap-v2.json": ("wadamesh — RAK WisMesh Tap V2", "wadamesh-rak-tap-v2-merged.bin", "ESP32-S3"),
"manifest-heltec-v4-r8-tft.json": ("wadamesh — Heltec V4-R8 (experimental)", "wadamesh-heltec-v4-r8-tft-merged.bin", "ESP32-S3"),
"manifest-tlora-pager-lr1121.json": ("wadamesh — LilyGo T-LoRa Pager (LR1121)", "wadamesh-tlora-pager-lr1121-merged.bin", "ESP32-S3"),
"manifest-tlora-pager-sx1262.json": ("wadamesh — LilyGo T-LoRa Pager (SX1262)", "wadamesh-tlora-pager-sx1262-merged.bin", "ESP32-S3"),
"manifest-tdisplay-p4.json": ("wadamesh — LilyGo T-Display P4", "wadamesh-tdisplay-p4-merged.bin", "ESP32-P4"),
}
for fn, (name, binf) in BOARDS.items():
for fn, (name, binf, chip) in BOARDS.items():
manifest = {
"name": name,
"name": name + ("" if channel == "stable" else " (beta)"),
"version": tag,
"new_install_prompt_erase": True,
"builds": [{
"chipFamily": "ESP32-S3",
# Point at the IMMUTABLE per-tag bin, NOT latest/. The latest/*.bin URLs
# are stable filenames cached 4h (max-age=14400) and overwritten in place,
# so for up to 4h after a release the flasher could hand out the PREVIOUS
# beta's bytes while version.json already advertised the new tag. The
# per-tag path is never overwritten, so its (24h) cache is always correct.
# The manifest itself is max-age=300, so this new path propagates in <=5min.
"parts": [{"path": f"https://firmware.wadamesh.com/releases/TOUCH/{tag}/{binf}", "offset": 0}],
"chipFamily": chip,
# Point at the IMMUTABLE per-tag bin, NOT the rolling feed bin. The feed
# *.bin URLs are stable filenames cached 4h and overwritten in place, so
# for up to 4h after a release the flasher could hand out the PREVIOUS
# build's bytes while version.json already advertised the new tag. The
# per-tag path is never overwritten, so its cache is always correct. The
# manifest itself is max-age=300, so the new path propagates in <=5min.
"parts": [{"path": f"https://firmware.wadamesh.com/releases/{archive}/{tag}/{binf}", "offset": 0}],
}],
}
with open(os.path.join(outdir, fn), "w") as f:
json.dump(manifest, f, indent=2)
print(f"wrote version.json + 2 manifests for {tag} -> {outdir} (notes: {len(notes)})")
print(f"wrote version.json + {len(BOARDS)} manifests for {tag} ({channel}) -> {outdir} (notes: {len(notes)})")
+51
View File
@@ -0,0 +1,51 @@
#!/usr/bin/env python3
# Generate src/ui-touch/qr_icon.h: a small, recolour-able "QR code" glyph baked to
# an LVGL TRUE_COLOR_ALPHA lv_img_dsc (white opaque modules, transparent ground —
# tinted to the button text colour at runtime via img_recolor). There is no QR
# glyph in the Montserrat/symbol font, so the Chats-header Share button draws this
# instead of the old stand-in LV_SYMBOL_IMAGE ("picture") icon.
#
# python3 scripts/build/gen-qr-icon.py
#
# Same pixel encoding as the emoji bake: [lo, hi, alpha], LV_COLOR_16_SWAP=0.
import os
SCALE = 2 # px per module -> 9 modules * 2 = 18x18 px
HERE = os.path.dirname(os.path.abspath(__file__))
ROOT = os.path.abspath(os.path.join(HERE, "..", ".."))
OUT = os.path.join(ROOT, "src", "ui-touch", "qr_icon.h")
# 9x9 module grid. Three finder patterns (ring: 111/101/111) at TL/TR/BL corners,
# scattered data modules + a small alignment block bottom-right so it reads as a QR.
P = [
[1,1,1,0,1,0,1,1,1],
[1,0,1,0,0,0,1,0,1],
[1,1,1,0,1,0,1,1,1],
[0,0,0,0,0,0,0,0,0],
[1,0,1,0,1,1,0,1,0],
[0,0,0,0,1,1,0,0,1],
[1,1,1,0,0,0,1,0,1],
[1,0,1,0,1,0,0,1,0],
[1,1,1,0,0,1,1,0,1],
]
MODS = len(P)
W = H = MODS * SCALE
data = bytearray()
for y in range(H):
for x in range(W):
on = P[y // SCALE][x // SCALE]
if on:
data += bytes((0xFF, 0xFF, 0xFF)) # white RGB565 (lo,hi) + alpha 255
else:
data += bytes((0x00, 0x00, 0x00)) # transparent
with open(OUT, "w") as f:
f.write("// AUTO-GENERATED by scripts/build/gen-qr-icon.py — do not edit.\n")
f.write("// %dx%d recolour-able QR glyph for the Chats-header Share button.\n#pragma once\n" % (W, H))
f.write('#include "lvgl.h"\n\n')
f.write("static const uint8_t qr_icon_map[] = {%s};\n" % ",".join(str(b) for b in data))
f.write("static const lv_img_dsc_t qr_icon_dsc = { { LV_IMG_CF_TRUE_COLOR_ALPHA, 0, 0, %d, %d }, sizeof(qr_icon_map), qr_icon_map };\n"
% (W, H))
print("wrote %s (%dx%d, %d bytes)" % (OUT, W, H, len(data)))
+52
View File
@@ -0,0 +1,52 @@
# Patches the vendored RadioLib so LR11x0::config() tolerates old LR1110
# transceiver firmware that predates DriveDiosInSleepMode (opcode 0x012A,
# added in the 0x0308 firmware release). RadioLib >= 7.x sends it
# unconditionally during begin(); older chip firmware answers CMD_PERR,
# which turns an otherwise healthy radio.begin() into -706
# (RADIOLIB_ERR_SPI_CMD_INVALID). Preproduction Elecrow ThinkNode M9 units
# ship with such firmware (Meshtastic works on them only because it pins an
# older RadioLib that doesn't send the command).
#
# The command is an optional nicety (stops DIO glitches in sleep mode), so
# skipping it on old firmware is safe.
#
# Idempotent. Each PlatformIO env has its own libdeps copy, so this only
# affects envs that list this script in extra_scripts (the M9 env).
# NOTE: on a completely fresh checkout the first build may run before
# RadioLib is downloaded - the script then warns and the patch lands on the
# next build. Re-run `pio run` once if you see the warning.
Import("env")
import os
MARKER = "wadamesh-lr1110-oldfw-patch"
OLD = """ state = this->driveDiosInSleepMode(true);
RADIOLIB_ASSERT(state);"""
NEW = """ state = this->driveDiosInSleepMode(true);
// wadamesh-lr1110-oldfw-patch: LR1110 transceiver FW older than 0x0308
// doesn't implement DriveDiosInSleepMode (0x012A) and answers CMD_PERR,
// which would abort init (-706) on an otherwise healthy radio. The command
// only stops DIO glitches in sleep mode - safe to skip on old firmware.
if(state == RADIOLIB_ERR_SPI_CMD_INVALID) {
RADIOLIB_DEBUG_BASIC_PRINTLN("DriveDiosInSleepMode unsupported (old LR11x0 FW), skipping");
state = RADIOLIB_ERR_NONE;
}
RADIOLIB_ASSERT(state);"""
path = os.path.join(env.subst("$PROJECT_LIBDEPS_DIR"), env.subst("$PIOENV"),
"RadioLib", "src", "modules", "LR11x0", "LR11x0.cpp")
if not os.path.isfile(path):
print("[patch_radiolib_lr11x0] WARNING: %s not found (libdeps not fetched yet?)" % path)
print("[patch_radiolib_lr11x0] WARNING: RadioLib NOT patched - re-run the build once libdeps exist")
else:
with open(path) as f:
src = f.read()
if MARKER in src:
print("[patch_radiolib_lr11x0] already patched")
elif OLD in src:
with open(path, "w") as f:
f.write(src.replace(OLD, NEW, 1))
print("[patch_radiolib_lr11x0] patched LR11x0::config() for old-FW tolerance")
else:
print("[patch_radiolib_lr11x0] WARNING: pattern not found - RadioLib version drift?")
print("[patch_radiolib_lr11x0] WARNING: check LR11x0::config() by hand, NOT patched")
+84
View File
@@ -0,0 +1,84 @@
#!/usr/bin/env python3
"""
Documentation screenshot capture for the DOC_CAPTURE firmware build.
Build the firmware with -DDOC_CAPTURE, flash it to the T-Deck, then run:
python3 scripts/doc/capture.py /dev/cu.usbmodemXXXX [outdir]
The device waits for a 'G' byte, then walks every screen and streams each
framebuffer over USB as a 16-bit BMP wrapped in <<<WMSHOT ...>>> / <<<WMEND>>>
markers. This script sends 'G', reads each frame, and writes a PNG per screen
(via macOS `sips`; falls back to leaving the .bmp if sips is unavailable).
"""
import sys, os, re, time, subprocess
try:
import serial
except ImportError:
sys.exit("pyserial not found. Try: /Library/Developer/CommandLineTools/usr/bin/python3 -m pip install pyserial")
if len(sys.argv) < 2:
sys.exit("usage: capture.py <serial-port> [outdir]")
port = sys.argv[1]
outdir = sys.argv[2] if len(sys.argv) > 2 else "doc-shots"
os.makedirs(outdir, exist_ok=True)
ser = serial.Serial(port, 115200, timeout=2)
print(f"listening on {port} -> {outdir}/")
hdr_re = re.compile(rb"<<<WMSHOT name=(\S+) w=(\d+) h=(\d+) bytes=(\d+)>>>")
def read_exact(n):
data = bytearray()
while len(data) < n:
chunk = ser.read(n - len(data))
if not chunk:
break
data += chunk
return bytes(data)
count = 0
started = False
last_go = 0.0
deadline = time.time() + 90 # give the device up to 90s to start
while time.time() < deadline:
if not started and time.time() - last_go > 0.4:
ser.write(b"G") # nudge the device to begin the tour
ser.flush()
last_go = time.time()
line = ser.readline()
if not line:
continue
if b"WMTOUR START" in line:
started = True
print("tour started")
continue
if b"WMTOUR END" in line:
print("tour ended")
break
m = hdr_re.search(line)
if not m:
continue
name = m.group(1).decode()
nbytes = int(m.group(4))
data = read_exact(nbytes)
if len(data) != nbytes:
print(f" ! {name}: short read {len(data)}/{nbytes}")
continue
bmp = os.path.join(outdir, name + ".bmp")
png = os.path.join(outdir, name + ".png")
with open(bmp, "wb") as f:
f.write(data)
try:
subprocess.run(["sips", "-s", "format", "png", bmp, "--out", png],
check=True, capture_output=True)
os.remove(bmp)
count += 1
print(f" [{count:2d}] {name}.png ({nbytes} bytes)")
except Exception as e:
count += 1
print(f" [{count:2d}] {name}.bmp ({nbytes} bytes; sips convert failed: {e})")
ser.close()
print(f"done: {count} screenshots in {outdir}/")
Loaded 100 of 242 files, more files were not shown because too many files have changed in this diff. Show more