Hi Kevin, On Fri, Dec 1, 2017 at 9:46 PM, Kevin Snow <Kevin@xxxxxxxxxxx> wrote: > > We have a product using BlueZ. The device has both BLE and BR/EDR (for Audio). When attempting to make a BLE connection from some Android devices, the connection establishes as BR/EDR. Thus, our service UUID isn’t visible and can’t be accessed. I’ve been told this is per the Bluetooth Spec, although I’ve been unable to find it in the spec. Additionally,I don’t understand why the spec would do this as it effectively makes dual mode (both BLE and BR/EDR) worthless if the connection will be BR/EDR. This problem does not happen with Apple devices. They always connect as BLE. Many Android are fine too, just not all. I guess this depends on how old the Android is, previously 4.0 spec did not allow connecting on LE. Btw, how are you advertising? > One workaround would be to expose the BLE service via BR/EDR. Has anyone done this? I suppose you are talking about GATT services, we will need to do some fixes in order to support this, I will have a look into this since that is mandatory for qualification. > We’re very eager to wrap this up. Is there a BlueZ expert out there open to a short term contract to help us through this? Any modifications made to BlueZ would of course become part of the open source. We don’t want anything custom, just for our product to be completed. > > Thanks > > Kevin Snow > kevin@xxxxxxxxxxx > > > -- > 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 -- Luiz Augusto von Dentz -- 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
