On Sunday 18 of May 2014 13:53:55 Szymon Janc wrote: > Hi, > > This improves (fix) the way dual mode devices are handled. Bearer type is > now tracked and allows to use correct one for dual mode device. > > This also adds tracking if remote device was bonded or not. This is in > preparation for fixing no bond pairing. Android HAL does not distinguish > between pairing and bonding and appears to be ignoring bond state change > bonded->no_bond from stack. This leads to situation when device is no longer > paired (after being disconnected) but still being listed as bonded in > Android Framework. Possible solution would be to not call bond_state change > to bonded for no bond case (this seems to be what Bluedroid is doing [1]) > but this still needs further analyze and testing. > > BR > Szymon Janc > > > [1] http://androidxref.com/4.4.2_r1/xref/external/bluetooth/bluedroid/btif/src/btif_dm.c#338 > > Szymon Janc (5): > android/bluetooth: Track device last connected bearer > android/bluetooth: Fix pairing of dual mode devices > android/bluetooth: Fix unpairing dual mode device > android/bluetooth: Track if paired device is bonded > android/bluetooth: Simplify check if device type changed > > android/bluetooth.c | 315 ++++++++++++++++++++++++++++++++++++++-------------- > 1 file changed, 233 insertions(+), 82 deletions(-) > > Pushed. -- Best regards, Szymon Janc -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
