Hi Inga, On Fri, Jan 28, 2011 at 03:30, Inga Stotland <ingas@xxxxxxxxxxxxxx> wrote: [...] > Thank you for your response about enabling GATT over D-Bus. > I was following the instructions from your notes. > However, when trying to test D-Bus operations for GATT, I cannot seem to get > org.bluez.Characteristic interface to register... > Have you been able to get GATT D-Bus interface to work just with BR/EDR (no LE)? yup! I am able to use GATT related D-Bus interface to work with BR/EDR. In the beginning, back to Bluez release 4.80, we can trigger the discovering service when registering the client. Then it can store few files in /var/lib/bluetooth/BT_ADDR. When we start bluetooth daemon, it would register GATT D-Bus interface based on those files. If you'd like to see those D-Bus interface, you could rollback to release 4.80. You can use gatttoool to discover the primary service, and copy 'primary', 'attributes' and 'characteristic' files. Then you could use the latest Bluez, but move those files to the same folder. You should be able to see the GATT D-Bus interface. > > Thanks, > > Inga Stotland > > ingas@xxxxxxxxxxxxxx > Employee of Qualcomm Innovation Center, Inc. > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum > Regards, Erin Yueh -- 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
