From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216615] New: mSBC codec not supported for 0e8d:0616 (MediaTek RZ616)
Date: Sat, 22 Oct 2022 13:18:00 +0000 [thread overview]
Message-ID: <bug-216615-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216615
Bug ID: 216615
Summary: mSBC codec not supported for 0e8d:0616 (MediaTek
RZ616)
Product: Drivers
Version: 2.5
Kernel Version: 5.19.0-21-generic
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: marelo64@gmail.com
Regression: No
Created attachment 303073
--> https://bugzilla.kernel.org/attachment.cgi?id=303073&action=edit
Logs for multiple relevant commands
- Ubuntu ticket: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2783
- Pipewire ticket:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2783
---
While the bluetooth adapter `0e8d:0616` is supposed to support HFP/mSBC
(detected as such by pipewire), when switching to it, it fails and fall back to
the low quality HFP/CVSD audio codec.
According to pipewire's dev, it could be an issue with the driver for that
specific adapter since my headset (Pixel Buds Pro) works well on another
machine with the exact same software stack (Ubuntu 22.10) but another bluetooth
adapter where the Pixel Buds Pro works well with HFP/mSBC.
See logs attached.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-10-22 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 13:18 bugzilla-daemon [this message]
2022-10-22 13:18 ` [Bug 216615] mSBC codec not supported for 0e8d:0616 (MediaTek RZ616) bugzilla-daemon
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=bug-216615-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.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