Meshtastic-Android/core/data/src
James Rich 646858cc39 fix(handshake): use 60 s stall guard for Stage 2 to match SDK behavior
Stage 2 of the handshake drains the full node database, which on meshes
with 50+ nodes can comfortably exceed the previous 30 s stall guard and
trigger a spurious want_config_id retry mid-drain. The meshtastic-client
KMP SDK uses a 60 s timeout for this stage for the same reason.

Split HANDSHAKE_TIMEOUT into HANDSHAKE_TIMEOUT_STAGE1 (30 s) and
HANDSHAKE_TIMEOUT_STAGE2 (60 s) and thread the duration through
startHandshakeStallGuard so each call site picks the right value.
2026-04-20 11:29:13 -05:00
..
androidMain/kotlin/org/meshtastic/core/data refactor: leverage CMP 1.11 + Lifecycle 2.11 — v2 test API, Json privacy, dropUnlessResumed nav guards (#5112) 2026-04-13 20:02:31 +00:00
commonMain/kotlin/org/meshtastic/core/data fix(handshake): use 60 s stall guard for Stage 2 to match SDK behavior 2026-04-20 11:29:13 -05:00
commonTest/kotlin/org/meshtastic/core/data chore: review-cleanup fleet (audit + fix + hardening) (#5158) 2026-04-17 00:02:59 +00:00