Hi Jamie, >>For the application’s purpose, it’s critical that the notification is recieved with the minimum latency. > > Is there any reason why you wish to have the button in a disconnected state when inactive over having it in a connected state but with a high connection interval and a large slave latency? A high slave latency means it can stay in sleep mode if there is nothing to report back to the central device for a specified number of packets so is perfect for battery powered devices. The only reason is: very high expectations of battery life. I recall we played with the slave latency in the past, but we will reevaluate and see if it's a feasible option. Thanks for the suggestion. Regardless, I am still curious to know if disconnecting and sending the notification right away (as Luiz suggests) isn't racy with respect to StartNotify(). -- 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
