On Mon, Jan 30, 2012 at 1:51 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: >> > We have to also ensure that we do not disconnect the ACL in between the >> > retry attempts. Otherwise some car kits might cancel their pairing >> > procedure and you have to have user interaction to get it back into >> > pairing mode. So if the ACL gets disconnect, then we should just fail >> > and cancel the bonding. >> > >> In my testing, OS X/iOS drop the ACL between retry attempts - so we >> wouldn't be any worse than they are. I'm not sure whether it's even >> possible in bluez to avoid dropping the ACL? > > Is Apple doing retried pairing (or auto-pairing) as well? > They are; they send 0000 to the device, and then if it fails, it retries after about 3s. Android does the same (from the bluez Agent, ick) > Strictly speaking the ACL disconnect is host stack triggered. So you > have HCI_Authentication_Requested and you can just execute that again > with the same link. We also do have a ACL disconnect timeout handling of > 2 seconds that will allow sockets to re-use the same ACL link. Can you > provide some hcidump traces from your test cases? > Sure, probably will be a few days though. I may have a play and see if I can get it to avoid dropping the ACL link too. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist? -- 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
