Gracefully recover on bad attempt to cancel LE connection
According to logs some devices are stuck when in BLE_CONN_CANCEL state. That is they sent "LE Create Connection Cancel" request, and are awaiting "LE Connection Complete" event with invalid handle forever. But they wait and wait, and the event never arrive. That's because "LE Create Connection Cancel" was sent, when connection attempt is not pending. In such case, we should act upon command complete status, and decide to leave BLE_CONN_CANCEL state. To properly fix this issue, one would have to implement a proper queue for managing LE connection attempt state, preferably for scratch. This fix just give option of graceful recovery. Test: sl4a GattConnectTest Bug: 75290221 Change-Id: I7e7a377c789ac0a587390320fbf504267cca8727 (cherry picked from commit b0a9f9f23f7405bc088695e1d91763aced70b9fd)
Loading
Please register or sign in to comment