On Tue, 2016-08-09 at 22:55 +0200, Pali Rohár wrote: > On Tuesday 09 August 2016 13:15:17 Tanu Kaskinen wrote: > > On Tue, 2016-08-09 at 09:04 +0200, Pali Rohár wrote: > > > On Tuesday 09 August 2016 01:12:21 Tanu Kaskinen wrote: > > > > These profile names work only with BlueZ 4. With BlueZ 5 the > > > > profile names are "headset_head_unit" and "a2dp_sink". Pali, > > > > would you be willing to write a patch makes the code handle both > > > > BlueZ versions? > > > > > > I can look at it and write patch. But I do not have bluez5 so > > > somebody else would need to test it. > > > > I can test it if that seems necessary after reviewing the code. > > Ok. > > Do you have an idea how to detect if pulse card is bluez4 or bluez5? I > need that detection in bluetooth policy module... You could detect that by checking what profile names the card uses, but that's pretty ugly, IMHO. I think the best solution would be to change the PA_PROP_DEVICE_API property value from "bluez" to "bluez4"/"bluez5". -- Tanu
