fix: move FEAT_RX_POWERSAVE to Features.h; no extra [LOC] on "Stop after" change

- FEAT_RX_POWERSAVE lived in MyMesh.h, but SettingsScreen.h only pulls
  Features.h -- it saw the flag only via include order, and an undefined
  macro in `#if` silently reads as 0, which would split the build the day
  it's flipped to 1. Now defined in Features.h (the home of FEAT_* flags),
  which MyMesh.h includes; comment/doc pointers updated.
- Changing Live Share's "Stop after" restarted the whole session, forcing
  an immediate re-announce [LOC] although the position hadn't changed. It
  now restarts only the duration clock (restartLocShareClock()).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Jakub
2026-09-24 15:50:37 +02:00
co-authored by Claude Opus 5.5
parent 299fcf2c13
commit 1620df6c10
10 changed files with 32 additions and 24 deletions
+1 -1
View File
@@ -384,7 +384,7 @@ Radio, both **default OFF**. Under field testing; not yet merged.
already noted below (native NRF52 companion power-saving from the v1.16
upstream merge) — safe, but doesn't touch the dominant power draw (the radio in
continuous RX), unlike a real duty-cycle.
- **Resolution:** `examples/companion_radio/MyMesh.h` now defines
- **Resolution:** `examples/companion_radio/Features.h` now defines
`FEAT_RX_POWERSAVE 0`, gating out the Settings row (`SettingsScreen.h`), the
Diagnostics RXPS watchdog row (`DiagnosticsScreen.h`), and every call site that
would apply `_prefs.rx_powersave` to the radio or to CAD auto-enable