[pulseaudio-discuss] [PATCH 2/2, v2] backend-native: send DBus signal on headset button press

Georg Chini georg at chini.tk
Sat Mar 11 19:27:33 UTC 2017

> I tried searching the net, and it looks like ButtonPress is not a
> documented signal. Did you invent the signal yourself? If it's your
> invention, I don't think the org.bluez.Headset interface should be
> used. The org.bluez namespace should be controlled by the BlueZ
> project. I would expect the dbus daemon to reject such signals anyway,
> because pulseaudio hasn't been granted the right to send signals with
> that interface on the system bus.

It is an invented signal, but it is not rejected. I did not know which
name space to use, so I choose org.bluez because it is a bluez
event. I don't mind using something else if you have a better idea.

> I'm a bit uncertain whether using D-Bus for this is the best option
> anyway. If this is a new pulseaudio specific interface, the native
> protocol might be a better choice.
I thought D-Bus is the right interface because bluez normally
uses the D-Bus and pressing the headset button is a bluez event.

The reason for this patch was that I wrote an application to handle
mobile phones and it was a nice feature to be able to use the button.
I don't mind dropping that patch completely if you think it is out of
scope for pulseaudio.

More information about the pulseaudio-discuss mailing list