From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215576] New: HSP/HFP mSBC profile broken with QCA6174
Date: Mon, 07 Feb 2022 18:00:39 +0000 [thread overview]
Message-ID: <bug-215576-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215576
Bug ID: 215576
Summary: HSP/HFP mSBC profile broken with QCA6174
Product: Drivers
Version: 2.5
Kernel Version: 5.16.7
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: mike@mjones.io
Regression: No
Created attachment 300405
--> https://bugzilla.kernel.org/attachment.cgi?id=300405&action=edit
dmesg with 5.16.7
Between v5.15 and v5.16, mSBC via pipewire stopped working with the QCA6174
adapter.
Switching to the HSP/HFP profile with mSBC codec in pipewire produces a loud
buzzing sound, and the microphone does not function. When using PulseAudio
instead of pipewire, the buzzing is absent but audio input/output also don't
work.
Other users are reporting the same issue at [1].
I ran a git bisect between these two versions and the issue seems to have been
caused by this commit:
[b2af264ad3af437238c9500aa830ebcafb180e05] Bluetooth: Add support for
HCI_Enhanced_Setup_Synchronous_Connection command
[1] https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2019
--
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-02-07 18:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:00 bugzilla-daemon [this message]
2022-02-08 6:49 ` [Bug 215576] New: HSP/HFP mSBC profile broken with QCA6174 Thorsten Leemhuis
2022-03-07 11:24 ` [Bug 215576] New: HSP/HFP mSBC profile broken with QCA6174 #forregzbot Thorsten Leemhuis
2022-04-10 8:56 ` Thorsten Leemhuis
2022-05-30 10:38 ` Thorsten Leemhuis
2022-02-08 6:49 ` [Bug 215576] HSP/HFP mSBC profile broken with QCA6174 bugzilla-daemon
2022-02-09 17:27 ` bugzilla-daemon
2022-02-14 15:09 ` bugzilla-daemon
2022-02-18 14:15 ` bugzilla-daemon
2022-02-18 20:55 ` Luiz Augusto von Dentz
2022-02-18 20:55 ` bugzilla-daemon
2022-02-18 21:44 ` [Bug,215576] " bluez.test.bot
2022-02-26 15:03 ` [Bug 215576] " bugzilla-daemon
2022-02-26 15:31 ` bugzilla-daemon
2022-02-26 16:21 ` bugzilla-daemon
2022-02-27 17:00 ` bugzilla-daemon
2022-03-09 11:50 ` bugzilla-daemon
2022-03-29 20:21 ` bugzilla-daemon
2022-05-27 10:52 ` bugzilla-daemon
2022-05-27 22:59 ` bugzilla-daemon
2022-05-28 0:15 ` bugzilla-daemon
2022-05-30 11:12 ` bugzilla-daemon
2022-06-18 19:17 ` bugzilla-daemon
2022-06-19 16:46 ` bugzilla-daemon
2022-06-19 17:08 ` bugzilla-daemon
2022-06-19 17:47 ` bugzilla-daemon
2022-07-04 15:55 ` bugzilla-daemon
2022-07-05 9:30 ` 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-215576-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.