Hi Sonny, > This was needed to support emulation of Android apps's Bluetooth API > on top of BlueZ. Android expects to be able to access the SDP database > of a remote device via its HAL interface > (https://android.googlesource.com/platform/system/bt/+/master/include/hardware/bt_sdp.h#38). > > Thanks for the feedback, we will revisit this and see if a redesign > based on your suggestion is possible. if you can get this done by using existing APIs and the Profile API, then that would be best. I would have to get myself a bit more familiar with the Android APIs. However in the worst case, we can introduce an Android specific D-Bus API as part of a plugin. It would be then disabled in standard Linux systems. >From BlueZ for Android project, we fundamentally took the Android HAL parts 1:1 and mapped them to a Unix based protocol. Then the Android bluetoothd had to do the rest of the work. A similar approach (and using D-Bus) might be most efficient here actually. However as Luiz noted, we need to be careful that bluetoothd system services / profiles are not messed with. Meaning bluetoothd has to play guardian on what Android apps can do. On a side note, I am going to remove the BlueZ for Android code from the tree. Let me know if you find parts of it still useful. It is git, so we can always bring it back, but if you already have some idea on how to utilize it, feel free to start with that right away. Regards Marcel
