Branch: refs/heads/master Home: https://github.com/bluez/bluez Commit: 8572f2430980ae75c9df9b51adf86cca9e2d85f0 https://github.com/bluez/bluez/commit/8572f2430980ae75c9df9b51adf86cca9e2d85f0 Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> Date: 2024-10-18 (Fri, 18 Oct 2024) Changed paths: M Makefile.am A doc/hci.rst Log Message: ----------- doc: Add initial HCI(7) documentation This adds initial documentation for HCI sockets. Commit: 923379409010602254233103689c8ed2ff2a6cc6 https://github.com/bluez/bluez/commit/923379409010602254233103689c8ed2ff2a6cc6 Author: Marijn Suijten <marijn.suijten@xxxxxxxxxxxxxx> Date: 2024-10-21 (Mon, 21 Oct 2024) Changed paths: M profiles/audio/avrcp.c M src/btd.h M src/main.c M src/main.conf Log Message: ----------- audio/avrcp: Guard SetAbsoluteVolume without target behind config value Commit 179ccb936 ("avrcp: Set volume if volume changed event is registered") invented a workaround that allows SetAbsoluteVolume to be sent to a remote device that does _not_ implement the AVRCP TG profile, as long as it previously registered for the EVENT_VOLUME_CHANGED notification. This is strange as the TG role is required to be able to send commands to the peer, but the commit must have been applied to the tree for a reason. We discussed in [1] that workarounds for dubious peers and software stacks should be guarded behind a config entry in main.conf, so this starts out by introducing a new [AVRCP] category that will later be extended with other workarounds. It guards the changed functionality behind a `VolumeWithoutTarget = false` boolean to disallow this obscure check. [1]: https://lore.kernel.org/linux-bluetooth/20211025210206.bkt5wovzmkmt6teg@xxxxxxxxxxxxxx/ Commit: 8baabd2f5c131f902d79e20829b117edffd46d1a https://github.com/bluez/bluez/commit/8baabd2f5c131f902d79e20829b117edffd46d1a Author: Marijn Suijten <marijn.suijten@xxxxxxxxxxxxxx> Date: 2024-10-21 (Mon, 21 Oct 2024) Changed paths: M profiles/audio/avrcp.c Log Message: ----------- audio/avrcp: Only allow absolute volume call/event on category-2 peers Restrict the use of SetAbsoluteVolume and EVENT_VOLUME_CHANGED to peers with at least AVRCP version 1.4 and AVRCP_FEATURE_CATEGORY_2 on their respective target or controller profiles. For backwards-compatibility, add a (default-enabled) `VolumeCategory = true` configuration option under `[AVRCP]` to allow optionally disabling this new check. Compare: https://github.com/bluez/bluez/compare/b5b51017ea18...8baabd2f5c13 To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
