All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
Date: Fri, 28 Jun 2019 13:05:05 +0000	[thread overview]
Message-ID: <bug-203997-62941-JRGT59dUaG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203997-62941@https.bugzilla.kernel.org/>

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

Søren Holm (sgh@sgh.dk) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sgh@sgh.dk

--- Comment #4 from Søren Holm (sgh@sgh.dk) ---
(In reply to Daniel Ponte from comment #3)
> Seeing similar with Logitech H800 headphones. Sometimes it stays connected.
> Curiously enough, HFP profile sometimes works (using tanuk's pulseaudio-hfp
> patch), but A2DP absolutely will not activate. The headphones will even
> register with pulseaudio as a bare device but A2DP remains unavailable.

I have the exact same problem also with H800 headset.

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

  parent reply	other threads:[~2019-06-28 13:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
2019-06-27  0:22 ` [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15 bugzilla-daemon
2019-06-27 13:35 ` bugzilla-daemon
2019-06-28 13:05 ` bugzilla-daemon [this message]
2019-07-01  7:15 ` bugzilla-daemon
2019-07-01 12:23 ` bugzilla-daemon
2019-07-07 11:33 ` bugzilla-daemon
2019-07-07 11:43 ` bugzilla-daemon
2019-09-02 11:44 ` bugzilla-daemon
2019-09-02 11:49 ` bugzilla-daemon
2019-09-03 12:37 ` bugzilla-daemon
2019-09-03 12:45 ` bugzilla-daemon
2019-09-08 12:19 ` 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-203997-62941-JRGT59dUaG@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 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.