From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221722] Blanket HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN for all MediaTek chips breaks HFP mSBC microphone on MT7925 (0489:e111)
Date: Mon, 19 Oct 2026 11:11:52 +0000 [thread overview]
Message-ID: <bug-221722-62941-YRRbBrkYTv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221722-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221722
--- Comment #2 from purpleritza@gmail.com ---
Update from the reporter: I can no longer reproduce the silent mSBC microphone
on
this machine (0489:e111, kernel 7.2.8, BT firmware build 20260605184935).
With HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN still applied ("HCI Enhanced
Setup
Synchronous Connection command is advertised, but not supported" is logged),
recording from the headset mic gave real signal in both profiles:
headset-head-unit-cvsd max -16.5 dB
headset-head-unit max -18.3 dB (mSBC)
The call failures I see now are tracked separately in bug 222151 (BT firmware
20260813113236 regression). Leaving this open since another reporter is
affected
on 0e8d:e025.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-10-19 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 16:39 [Bug 221722] New: Blanket HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN for all MediaTek chips breaks HFP mSBC microphone on MT7925 (0489:e111) bugzilla-daemon
2026-07-04 17:22 ` [Bug,221722] " bluez.test.bot
2026-07-24 17:19 ` [Bug 221722] " bugzilla-daemon
2026-10-19 11:11 ` bugzilla-daemon [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=bug-221722-62941-YRRbBrkYTv@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