From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v3 RESEND] avrcp: Poll GetPlayStatus when position changed event unsupported
Date: Mon, 16 Nov 2026 20:00:13 +0000 [thread overview]
Message-ID: <179485921352.3860040.5845821355706416129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116093308.79430-1-frederic.danis@collabora.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 16 Nov 2026 10:33:08 +0100 you wrote:
> Some remote targets do not support the AVRCP_EVENT_PLAYBACK_POS_CHANGED
> notification, meaning bluetoothd never learns about track position
> updates for such devices.
>
> When this event is not present in the capabilities reported by the
> remote, fall back to polling AVRCP_GET_PLAY_STATUS once a second so
> the media player position stays in sync. Polling is only kept running
> while playback is actively progressing (playing) and is stopped
> otherwise, and is torn down on session destruction.
>
> [...]
Here is the summary with links:
- [BlueZ,v3,RESEND] avrcp: Poll GetPlayStatus when position changed event unsupported
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8a3bdbb1f5c5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-16 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 9:33 [PATCH BlueZ v3 RESEND] avrcp: Poll GetPlayStatus when position changed event unsupported Frédéric Danis
2026-11-16 20:00 ` patchwork-bot+bluetooth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179485921352.3860040.5845821355706416129.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox