Linux bluetooth development
 help / color / mirror / Atom feed
From: Jan-Michael <jan.brummer@tabos.org>
To: linux-bluetooth@vger.kernel.org
Cc: jan.brummer@tabos.org
Subject: [PATCH v4 BlueZ 0/1] Add cover art support
Date: Fri,  9 Oct 2026 15:49:23 +0200	[thread overview]
Message-ID: <20261009134924.122040-1-jan.brummer@tabos.org> (raw)
In-Reply-To: <20260803195620.255866-1-jan.brummer@tabos.org>

BlueZ wasn't able to display cover art in car's headunits due to missing
cover art support. Add missing pieces to allow sending cover arts:

 - Add AVRCP BIP Cover Art Responder
 - Advertise Cover Art Support

v2:
Dropped the patch that relaxed the sandbox of the systemd unit.
bluetoothd no longer touches the filesystem at all: instead of
reading the file mpris:artUrl points to, it asks the player for the
image data over D-Bus, and mpris-proxy answers that call
for the players it registers (patch 5). ProtectHome= and the
capability bounding set stay exactly as they are.

v3:
Update based on review comments, e.g. moved to obex

v4:
Fix CheckPatch findings

Tested on a Fairphone 5 and OnePlus 6T with a VW head unit.

Jan-Michael Brummer (1):
  Add cover art support

 Makefile.plugins           |   4 +-
 doc/org.bluez.Media.rst    |  21 ++
 profiles/audio/avrcp-bip.c | 608 +++++++++++++++++++++++++++++++++++++
 profiles/audio/avrcp-bip.h |  46 +++
 profiles/audio/avrcp.c     |  92 +++++-
 profiles/audio/media.c     | 194 ++++++++++++
 src/bluetooth.conf         |   1 +
 tools/mpris-proxy.c        |  81 +++++
 8 files changed, 1041 insertions(+), 6 deletions(-)
 create mode 100644 profiles/audio/avrcp-bip.c
 create mode 100644 profiles/audio/avrcp-bip.h

-- 
2.55.0


  parent reply	other threads:[~2026-10-09 13:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 19:55 [PATCH BlueZ 0/1] Add cover art support Jan-Michael
2026-08-03 19:55 ` [PATCH BlueZ 1/1] " Jan-Michael
2026-08-03 20:56   ` Bastien Nocera
     [not found]     ` <6716CF9D-9856-4371-B55E-FFB8E6914B74@tabos.org>
2026-08-03 22:29       ` Bastien Nocera
2026-08-03 21:29   ` bluez.test.bot
2026-08-31 15:00 ` [PATCH v2 BlueZ 0/1] " Jan-Michael
2026-08-31 15:00   ` [PATCH BlueZ] " Jan-Michael
2026-08-31 20:59     ` Luiz Augusto von Dentz
2026-08-31 21:38     ` [BlueZ] " bluez.test.bot
2026-09-07 19:34 ` [PATCH v3 BlueZ 0/1] " Jan-Michael
2026-09-07 19:34   ` [PATCH v3 BlueZ] " Jan-Michael
2026-09-07 22:07     ` [v3,BlueZ] " bluez.test.bot
2026-09-08 18:07     ` bluez.test.bot
2026-09-23 18:44     ` bluez.test.bot
2026-10-09 13:49 ` Jan-Michael [this message]
2026-10-09 13:49   ` [PATCH BlueZ] " Jan-Michael
2026-10-09 15:58     ` [BlueZ] " bluez.test.bot

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=20261009134924.122040-1-jan.brummer@tabos.org \
    --to=jan.brummer@tabos.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