fix(ble): connect G2 arms with autoConnect=true

Direct connect (autoConnect=false) is supervised less patiently by Android's
BLE stack; the ring already requires autoConnect=true for this reason, and the
glasses arms showed the same short-lived direct-connect drops. Switch both
arms' beginConnect and connect to autoConnect=true.
This commit is contained in:
MasterControl committed 2026-11-14 20:05:15 +00:00
1 parent 3eb9b09e3d
commit a9df3de59b
3 files changed
+21 -18

No files matched your search

@@ -231,17 +231,16 @@ class FaceclawBleManager(context: Context) {
fun connect(address: String?, timeoutMs: Int): Boolean = connect(address, timeoutMs, false)
/**
* EXPERIMENTAL (2026-09-11): the ring specifically needs autoConnect=true.
* Even's own vendor app connects the ring with Android's autoConnect flag
* set (confirmed via its own BLE debug log, "connect() - device: ...,
* auto: true"), while every other faceclaw connection (both glasses arms)
* uses autoConnect=false. Direct connect (false) is faster to establish
* but Android supervises it less patiently; a live test showed the
* ring-only direct connection dying almost exactly 5 seconds in,
* repeatedly, with nothing else competing for it. autoConnect=true can
* take much longer to actually complete (Android manages it as a
* background reconnect, not an immediate attempt), so this needs its own
* longer timeout. Like [connect], waits on an attempt already pending.
* autoConnect=true is used for the ring and both glasses arms. The ring specifically
* needs it (Even's own vendor app connects the ring with Android's autoConnect flag
* set, confirmed via its own BLE debug log, "connect() - device: ...,
* auto: true"). A live test showed a ring-only direct connection dying almost
* exactly 5 seconds in, repeatedly, with nothing else competing for it, and the
* glasses arms showed the same "less patiently supervised" direct-connect drop.
* Direct connect (false) is faster to establish but Android supervises it less
* patiently. autoConnect=true can take much longer to actually complete (Android
* manages it as a background reconnect, not an immediate attempt), so it needs its
* own longer timeout. Like [connect], waits on an attempt already pending.
*/
fun connect(address: String?, timeoutMs: Int, autoConnect: Boolean): Boolean {
val key = requireAddress(address)