Hi! I'm wonder to solve the following situation: 1. You pair your BT device with your computer and use it. 2. Then go somewhere else and pair it with another computer to use it there. 3. Finally you go back to the first computer and want to use the device again with the first computer. In this situation, depending on the device, the first pairing could be lost if the device supports only one pairing. Some mice/keyboards support only one pairing, but there are also other devices supporting more than one pairing at each time. If the device lost the pairing, the connect attempt with the device will likely reject our link key. With the current BlueZ, this is "Paired: yes" for us, but we can't initiate the secure connection. To solve this we would need to, in order: 1. Remove the device. 2. Wait for the device to appear in the discovery session. 3. Pair again with the device (re-trust is if needed, etc). Can we solve this or make it easier? I'm thinking about adding a "Discovering" boolean property to the Device1 interface that tells you if a device (paired or not, connected or not) is in discovery mode. We know that because we see an inquiry response while discovering. I would also modify the "Pair" method to allow to re-pair a device that is Paired and Discovering instead of returning an error for that case. What do you think? Alex. -- 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
