On Wed, Mar 20, 2013 at 9:10 PM, Alex Deymo <deymo@xxxxxxxxxxxx> wrote: > The implemented logic is: > For each new org.bluez.Device1.Pair call that ends in a pin request (not SSP) > we *iterate* the list of pincode callbacks from plugins trying every callback > until it returns 0 (no pincode). > Does this mean that the user/agent will have to issue repeated Pair attempts/method calls to successfully pair a device? That seems like a poor user experience to me, and is different to the patches previously submitted which would retry inside the Bluetooth daemon. There's also the risk that the first failed pairing attempt will, if you drop the connection to the device, cause the device to leave page scan mode entirely requiring user interaction there as well (re-pushing the Connect/Pair button, for example). Scott -- Scott James Remnant | Chrome OS Systems | keybuk@xxxxxxxxxx | Google -- 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
