public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 211969] New: AX200 Bluetooth audio devices disconnect after random intervals
Date: Fri, 26 Feb 2021 20:09:04 +0000	[thread overview]
Message-ID: <bug-211969-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 211969
           Summary: AX200 Bluetooth audio devices disconnect after random
                    intervals
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.11.1
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: ddimaggio324@gmail.com
        Regression: No

I've personally observed this issue on kernels 5.10 and 5.11.
Connecting my headphones with both PulseAudio and PipeWire causes disconnects
since a linux-firmware package upgrade (20210208.b79d239-1, Arch Linux).
Downgrading the package to 20201218.646f159-1 solves my problem.
The bug causes my headphones to disconnect after anywhere from 5 minutes to 3
hours, though I found PipeWire causes the disconnect to happen closer to the 30
minute range.


There are a few user accounts posting about their experiences with this in the
following links:


https://bbs.archlinux.org/viewtopic.php?pid=1957011#p1957011
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/732

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

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

             reply	other threads:[~2021-02-26 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 20:09 bugzilla-daemon [this message]
2021-04-12  3:34 ` [Bug 211969] AX200 Bluetooth audio devices disconnect after random intervals 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-211969-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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