Hi Vinicius, On Fri, Jan 25, 2013, Vinicius Costa Gomes wrote: > The only problem with this aproach that I found while testing is the > problem exposed on the message of commit 5/6: If the remote device is > out of range during pairing any connection attempt will fail until the > Connection Complete event comes (with an error). This is the reason > that we put the devices in the connect list before pairing. > > Is this reason enough to have the device put in the connect list > during pairing? I don't think so. The mgmt_pair_device should have a timeout for LE devices on the kernel side, but since this is not the case with current kernel versions we'll need a workaround in user space. I.e. instead of using scanning (I assume that's what putting it on the connect list will do) you should just use a simple timeout (g_timeout_add_seconds) and call mgmt_cancel_pair_device if it expires. Johan -- 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
