Document the multipoint AVRCP routing quirk on Linux - #65
Open
phedoreanu wants to merge 1 commit into
Open
phedoreanu wants to merge 1 commit into
phedoreanu wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a paragraph to the Linux platform quirks. With a multipoint headset and a second device connected, the headset's play/pause key and its wear-sensor pause go to the other device unless BlueZ has a registered AVRCP player, which it does not have by default. Found while testing #63 on a WH-1000XM6 with a phone connected: nothing arrives on the headset link and no media key is generated, while the same actions reach Linux as soon as
mpris-proxyruns. The section already recommendsmpris-proxyfor metadata, so this notes the second reason to run it and the user unit that keeps it up.