Hi again, On Tue, Dec 26, 2017 at 5:22 PM, Ahmed Alsharif <ahmeds2000x@xxxxxxxxx> wrote: > Hi Luiz, > > On Tue, Dec 26, 2017 at 2:18 PM, Luiz Augusto von Dentz > <luiz.dentz@xxxxxxxxx> wrote: >> Hi Ahmed, >> Note that StartNotify is intended to work offline, so when it connects it >> will subscribe which seem this would prevent that to happen. > > Thanks for the clarification, this does indeed prevent that from > happening, sorry for the silly mistake on my side. I'm interested in hearing your thoughts on the following: Isn't it a bit inconsistent, that when a device is connected, and a characteristic is already notifying, no error is returned when trying to subscribe to it again (bluez-5.43 and below used to actually return an "Already notifying" error), but when a device is not connected, an InProgress error is returned? This means that an InProgress error just tells us that a device is not connected, which only adds ambiguity I think. Cheers:) -- 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
