Fix Android sensor recovery and add safe Move flow by shroominic · Pull Request #55 · shroominic/OpenGlucose

shroominic · 2026-08-16T08:10:53Z

Summary

Fix Android scan, discovery, bonding, notification subscription, and retry sequencing.
Add an explicit crash-safe Move sensor to another phone flow using the Bluetooth Bond Management Service.
Keep normal Disconnect non-destructive.
Add privacy-safe private diagnostics and a side-by-side debug application ID.

Full pre-push make check passed, including tooling, formatting, analyzers, unit/integration tests, Android/web/iOS builds, signing fail-closed checks, and native iOS tests.
476 unit tests and 1 integration test passed before commit.
Independent review found no P0-P2 issues.
Physical Pixel 9a / Android 17 evidence: session reached authenticated operation; the Move control-point write received GATT success; GATT disconnected; Android bond changed from bonded to none.
OPPO re-pair validation follows after the USB cable is switched.

Normal Disconnect preserves the sensor and Android bonds.
Move requires a ready authenticated session, exact plan binding, explicit confirmation, durable outcome state, and one write-with-response.
Unknown control-point outcomes fail closed: no automatic retry, local unpair, or marker clear.
The legacy unsafe unpair path is rejected.

fix: make Android sensor setup and transfer reliable

d7d1fb5

shroominic merged commit b969a63 into main Aug 16, 2026
9 checks passed

shroominic mentioned this pull request Sep 1, 2026

Release readiness: Android compatibility, stable 0.1, and external TestFlight #34

Open

13 tasks