audio/transport: Only store volume when also emitting DBus prop change By setting a2dp->volume early in set_volume() the resulting call to media_transport_update_volume() when an AVRCP reply is received will likely see the same volume received (unless the peer rounded it to another value) and bail on equality, before emitting a DBus property change. This results in DBus clients not being made aware of the change unless the peer is an audio source (that receives a notification about changed volume, instead of a command to _set_ a new volume), where set_volume() immediately raises the DBus signal. This issue is observed when playing back audio to headphones through an AbsoluteVolume-enabled audio server like PulseAudio, which does not receive the "Volume" change (while the peer does change volume) when setting this property externally using ie. dbus-send.

Diffstat

1 files changed, 3 insertions(+), 3 deletions(-)