Repository navigation
Android 0.3.9 — MeshCore reliability corrections
Pre-releaseMeshCrossway Android 0.3.9 — MeshCore reliability corrections
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.
- Verify MeshCore settings using fresh radio readback. A normal radio error keeps the connection alive and shows the failure. A partially applied multi-command save refreshes the actual values.
- Preserve Companion repeat mode when editing radio parameters, and verify preset radio/path changes as one transaction.
- Keep discoveries separate from approved radio contacts. Add explicit approval/removal actions and reconcile deleted contacts and full contact refreshes while retaining historical messages.
- Enforce a 31-byte UTF-8 name limit. An already truncated name remains readable so it can be repaired from the app.
- Decode negative TX power correctly and use the device's advertised maximum instead of a fixed 22 dBm ceiling.
- Gate advanced settings by Companion protocol support and coalesce repeated reads. Unsupported features no longer cause reconnect loops.
- Track receiver-side contact activity and live DM receipt separately from sender advert time. Initial backlog does not make every contact appear freshly heard.
- Reconcile matching late delivery ACKs with bounded retention, including BLE reconnection while the service is running.
- Preserve the integer extra-ACK count when changing unrelated privacy settings.
- Continue draining messages immediately after an unsupported channel-data item.
Validation includes the existing regression suites, 206 Meshtastic conformance checks, 66 MeshCore regression checks, Android settings/contact-persistence fixtures on API 29 and 35, build, lint and permanent certificate verification. Physical-radio and RF validation remain necessary. The app is a public beta; full official-app feature parity is not included.
Pending verification survives BLE reconnection without replaying SET commands. After repeated recovery failures, the app offers an explicit check or use-current-settings action. Late-ACK retention is limited to ten minutes and service lifetime; automatic retransmission is not enabled.
The APK checksum and permanent certificate fingerprint are attached to this release.