* bluez: avrcp: Initial value of absolute volume
@ 2019-06-12 7:25 Arun Raghavan
0 siblings, 0 replies; only message in thread
From: Arun Raghavan @ 2019-06-12 7:25 UTC (permalink / raw)
I'm using BlueZ as A2DP Sink and AVRCP controller on my laptop, and had a question about how absolute volume should work when I connect a phone to my laptop.
I notice in btmon that at connection time, the phone sends a register notification for the absolute volume event, and BlueZ responds with a current absolute volume of 100%. In the code, this seems to be initialised at media_transport_init_sink() and the initial volume is hard-coded to 127.
What this means is that after my initial connection to the device, I set some volume, disconnect and reconnect, and the volume is now 100% and any changes on the phone cause the device to play at full volume.
I can, of course, set a volume as soon as the transport is created from the client side, but it seems wrong to me that we communicate an incorrect initial value.
Am I missing something? If not, perhaps we can allow an initial volume to be passed during SetConfiguration so that the transport is initialised with the correct volume?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-12 7:25 bluez: avrcp: Initial value of absolute volume Arun Raghavan
Linux-Bluetooth Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/ public-inbox