fix(ble): drop CONNECTION_PRIORITY_HIGH for G2 arms #22
+7
-5
@@ -2464,11 +2464,13 @@ class GlassesSessionCore(
|
||||
throw ArmUnreachableException(if (address.equals(leftAddress, ignoreCase = true)) "left" else "right", address)
|
||||
}
|
||||
}
|
||||
// requestConnectionPriority has no callback in this Android compile target, so there is
|
||||
// no reliable completion point to keep it in the global GATT operation pipeline. But it's
|
||||
// important enough for performance that we call it anyways.
|
||||
link.requestHighPriority(address)
|
||||
|
||||
// Deliberately NOT requesting CONNECTION_PRIORITY_HIGH for the arms (mirrors the
|
||||
// ring in connectRing). HIGH negotiates a ~5 s supervision timeout (interval=12 /
|
||||
// timeout=500, 5000 ms) which makes the link die on any >5 s BLE gap and can strand
|
||||
// an arm in a half-open "connected" state where it stops advertising and is only
|
||||
// recoverable by a 5-tap reset. BALANCED's longer supervision timeout survives those
|
||||
// gaps. The firmware's own fast-profile request (ble_link.c) still negotiates speed
|
||||
// when a transfer needs it.
|
||||
link.requestMtu(address, ConnectionOptions.DESIRED_MTU, ConnectionOptions.CONNECT_TIMEOUT_MS)
|
||||
|
||||
if (!link.discoverServices(address, ConnectionOptions.SERVICES_TIMEOUT_MS)) {
|
||||
|
||||
Reference in new issue
Block a user