Commit: 21fb4064f252a08b87418125cf66fb7460e0ed95
Parent: 4f589213525a15177ff2a6a9e231b822219fc368
Author: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
Committer: Szymon Janc <szymon.janc@tieto.com>
Date: 2014-08-20 11:23:56
Tree: e376ddcadf582023e5dffe80149c0f7cece1147f

android/bluetooth: Update pairing status on pair complete event So far BfA updates android bond state after link key(s) are distributed. With LE pairing it might happen that no keys are distributed e.g remote device has Initiator Key Distribution and Responder Key Distribution set to 0. In such case link is encrypted with STK and after its disconnected, pairing needs to be done again. With this patch Android will get update about pairing complete just after BfA gets pairing complete from the kernel. It solve issue withnot updated Android settings application, which is hanging on "Pairing", in case when no keys are distributed. However, bacause Android does not see the difference between bonded / paired devices and because Android does not allow to update its bond state if FSM it is not in 'pending' state, BfA updates Android with BONDED state on pair_complete with success. This is how we are doing so far for bonding and non-bonding pairing. Note: BfA will update its bonded state after link key(s) are distribiuted.

Diffstat

M android/bluetooth.c | 13 +++++- - - - - - - -

1 files changed, 5 insertions(+), 8 deletions(-)

View Full Diff | Patch