Linux bluetooth development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 222151] MT7925 (0489:e111): BT firmware 20260813113236 (linux-firmware 50e034a2) breaks HFP calls and fails WMT init; 20260605184935 works
Date: Wed, 28 Oct 2026 12:12:03 +0000	[thread overview]
Message-ID: <bug-222151-62941-U86ivLQYv0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222151-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=222151

--- Comment #1 from purpleritza@gmail.com ---
Correction after further analysis: most of the call failures in my original
report were NOT caused by the firmware. The repeating failures correlate with
the wireplumber version, not the BT firmware build.

Per boot, counting "Failure in Bluetooth audio transport" loops (>= 4 within
3 minutes: HFP/A2DP profile flip-flopping, both bluez nodes going to error):

  Boot start        wireplumber  BT firmware build          Loops
  ----------------  -----------  -------------------------  -----
  2026-09-28 12:40  0.5.15       20260813113236                 0
  2026-10-03 11:07  0.5.18       20260605 + 20260813            3
  2026-10-07 11:36  0.5.18       20260605184935                 1
  2026-10-07 11:59  0.5.15       20260605184935                 0
  2026-10-15 11:00  0.5.15       20260605184935                 0
  2026-10-17 19:53  0.5.15       20260605 + 20260813            0
  2026-10-25 15:49  0.5.18       20260605184935                 5

Every loop happened on wireplumber 0.5.18, with either firmware build; none
on 0.5.15. I will report that part to wireplumber separately.

What remains attributable to firmware 20260813113236:

1. WMT init failure on this machine:

  BT build        Loads  WMT init failures
  20260605184935     71  0
  20260813113236     16  2 (2026-09-27, 2026-10-17)

2. Single mid-call HFP drops with wireplumber 0.5.15:

  BT build        Time on wireplumber 0.5.15  Mid-call HFP drops
  20260605184935  ~16 days                    0
  20260813113236  ~7.5 days                   2 (2026-09-28, 2026-10-19
12:02:56)

   The 2026-10-19 drop is the log in my original report. The only drop seen
   on 20260605184935 was during A2DP playback, not a call. Small sample, so
   weaker evidence than the WMT init failure.

Current setup, no call problems so far: linux-firmware-mediatek 20260810-2
(BT build 20260605184935) + wireplumber 0.5.15, kernel 7.2.11.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2026-10-28 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 10:57 [Bug 222151] New: MT7925 (0489:e111): BT firmware 20260813113236 (linux-firmware 50e034a2) breaks HFP calls and fails WMT init; 20260605184935 works bugzilla-daemon
2026-10-19 11:02 ` [Bug 222151] " bugzilla-daemon
2026-10-19 11:02 ` bugzilla-daemon
2026-10-28 12:12 ` bugzilla-daemon [this message]
2026-10-28 12:12 ` [Bug 222151] MT7925 (0489:e111): BT firmware 20260813113236 (linux-firmware 50e034a2) intermittently fails WMT init, possibly drops HFP calls; 20260605184935 does not 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-222151-62941-U86ivLQYv0@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