Repository navigation
Android 0.3.10 — MeshCore contact and reconnect fixes
Pre-releaseMeshCrossway Android 0.3.10 — MeshCore contact and reconnect fixes
Install over your existing MeshCrossway app and choose Update. The permanent signing certificate is unchanged. Local messages, settings, favorites, tracks and offline maps are retained during an in-place update.
- Resolve actual radio membership after new contact adverts. A contact auto-added by the radio becomes available without redundant manual approval; excluded/unapproved discoveries remain pending. No automatic ADD command is sent.
- Treat contact NOT_FOUND as a normal lifecycle result. Fresh adverts can resolve re-added contacts without reconnecting. Repeated adverts coalesce, and a newer advert is not lost when an older lookup finishes.
- Preserve pending verification as soon as Bluetooth accepts a settings write, including a disconnect before the write callback/response. Reconnection checks actual values with GET commands and never replays the SET automatically.
Validation includes 96 MeshCore regression checks, 206 Meshtastic conformance checks, existing protocol/browser/migration suites, Android API 29/35 smoke and storage fixtures, build, lint and permanent certificate verification. Tests cover successful/unsuccessful membership lookup, manual approval, re-addition, interrupted writes and readback mismatch. Physical radio and RF testing remain necessary; these are bounded regression results, not a claim of full official-app parity.
Prior 0.3.9 settings/readback, UTF-8 names, signed TX power, repeat-mode preservation and bounded late-ACK improvements are retained. Pending verification and late-ACK correlation survive BLE reconnection only while the service remains alive and the same radio is selected. Late-ACK retention remains bounded to ten minutes; no automatic message retransmission is enabled.
The APK checksum and permanent certificate fingerprint are attached to this release.