You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(esp32): port AP-First gate to the ESP32, covering 0x3FD/0x3EE/0x370 (#100/#108/#52)
The ESP32 injected ungated, so on 2026.14.x the FSD-enable (0x3FD/0x3EE) fired on the
AP activation edge — the steer-jerk @dunckencn reports on China 2026.8.3.6 HW3 (#108) —
and per @jewelrylin's #100 finding the nag-killer 0x370 echo trips the same preflight
and can block AP readiness on HW4. AP-First was Flipper-only.
Add the AP-First gate to the ESP32: a new ap_first prefs key + web-dashboard toggle
(off by default), fsd_ap_first_allows() (das_ap_state >= 2 held stable for
AP_FIRST_STABLE_MS=1000), ap_unstable_tick_ms stamped each frame while AP is not
engaged, and the gate applied to the 0x3FD, 0x3EE and 0x370 TX paths. Strictly
conservative: it can only withhold injection until AP is engaged and stable, never
inject more; default-off preserves current behavior.
Note vs the Flipper: the Flipper gates only 0x3FD/0x3EE; this also gates the nag 0x370
(the #100 extension). The Flipper side is unchanged in this commit.
All 7 ESP32 envs build; host suite (234) unaffected (shared core untouched).
0 commit comments