Hi Jose, On Mon, Dec 12, 2016 at 3:35 PM, José Bollo <jose.bollo@xxxxxxx> wrote: > Hi all, > > Using the commit c64b4d9e8dc3e36672061f39a9dba19ad0fb1ef1, the issue > is sloved. Great! Thank you. > > But my issue was also related to the fact that 'connected' was > received before availability of the attributes/services. The code was > disconnecting with the effect that not attributes/services coulded be > discovered. > > Should I that the variable "ServicesResolved" is intended to reflect > the service resolution state? How long should I wait after being > connected for the ServiceResolved Status? Is there a way to know that > service resolution is in progress? You should use ServicesResolved and wait until it becomes 1/true, while it is false it means it is in progress, when connected, but it should be quite fast to resolve the services once the cache is populated. -- 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
