linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
Date: Mon, 21 Feb 2022 09:12:48 -0800	[thread overview]
Message-ID: <CABBYNZL3ARfn7DkQ7n_P-NqHvThdB+EbeKoHkEEk1i0g3iZVeg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtTpHQe2co3fLNs5csKQchmwH=3YwQOvFnuc2nhjRseVnw@mail.gmail.com>

Hi Chris,

On Thu, Feb 17, 2022 at 7:49 PM Chris Murphy <lists@colorremedies.com> wrote:
>
> On Thu, Feb 17, 2022 at 5:15 PM Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
> >
> > Hi Chris,
> >
> > On Thu, Feb 17, 2022 at 3:36 PM Chris Murphy <lists@colorremedies.com> wrote:
> > >
> > > OK I started over, and for now keeping the reporting constrained to
> > > the hardware I personally have on hand.
> > >
> > > Hardware:
> > > Lenovo Thinkpad X1 Carbon Gen 7
> > > Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560
> > > Jefferson Peak (JfP)
> > > Sony 1000XM3 headset
> > > bluez-5.63-3.fc36.x86_64
> > >
> > > kernel 5.17.0-rc4
> > > * remove the paired headset with bluetoothctl
> > > * reset the headset so it's not longer paired either
> > > * put the headset in pairing mode
> > > * GNOME Settings Bluetooth panel sees -> LE_WH-1000XM3, Not Setup
> > > * click on Not Setup and nothing happens
> >
> > Well from the logs it doesn't seem the GNOME Setting is trying to do
> > anything, have you tried bluetoothctl> connect <address>
>
> `bluetoothctl scan on`  does see the device
> $ bluetoothctl pair 38:18:4C:24:2D:1D
> Device 38:18:4C:24:2D:1D not available
> $ bluetoothctl connect 38:18:4C:24:2D:1D
> Device 38:18:4C:24:2D:1D not available

Well you are unable to scan the device you won't be able to connect to
it, are you sure the device is discoverable?

> $ journalctl -b -o short-monotonic --no-hostname | grep -i blue
> https://drive.google.com/file/d/1x9EDvDx6XUowyRy2056n6uW-4PLx5KRb/view?usp=sharing
>
>
>
> --
> Chris Murphy



-- 
Luiz Augusto von Dentz

  parent reply	other threads:[~2022-02-21 17:13 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  1:44 bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices Chris Murphy
2022-02-15 15:29 ` Chris Murphy
2022-02-15 15:38   ` Chris Murphy
2022-02-16  3:47     ` Chris Murphy
2022-02-16 23:49       ` Luiz Augusto von Dentz
2022-02-17  1:35         ` Chris Murphy
2022-02-17 23:36           ` Chris Murphy
2022-02-18  0:15             ` Luiz Augusto von Dentz
2022-02-18  3:49               ` Chris Murphy
2022-02-21 11:39                 ` Chris Clayton
2022-02-21 13:22                 ` Chris Clayton
2022-02-21 17:11                   ` Luiz Augusto von Dentz
2022-02-21 20:23                     ` Chris Clayton
2022-02-21 21:27                       ` Luiz Augusto von Dentz
2022-02-21 22:33                         ` Chris Clayton
2022-02-22 20:03                           ` Chris Clayton
2022-02-23 17:51                             ` Luiz Augusto von Dentz
2022-02-23 22:42                               ` Chris Clayton
2022-02-24  5:59                                 ` Chris Clayton
2022-02-24  8:16                                   ` Luiz Augusto von Dentz
2022-02-24 10:08                                     ` Chris Clayton
2022-02-24 15:16                                       ` Luiz Augusto von Dentz
2022-02-24 16:18                                         ` Thorsten Leemhuis
2022-02-26  8:04                                         ` Chris Clayton
2022-02-28 19:34                                           ` Luiz Augusto von Dentz
2022-02-28 21:02                                             ` Chris Clayton
2022-02-28 21:20                                               ` Luiz Augusto von Dentz
2022-03-01  9:26                                                 ` Chris Clayton
2022-03-01 18:34                                                   ` Luiz Augusto von Dentz
2022-03-01 18:56                                                     ` Chris Clayton
2022-03-01 18:57                                                     ` Luiz Augusto von Dentz
2022-03-01 19:40                                                       ` Chris Clayton
2022-03-01 22:40                                                         ` Luiz Augusto von Dentz
2022-03-01 22:47                                                           ` Luiz Augusto von Dentz
2022-03-02  2:31                                                             ` Luiz Augusto von Dentz
2022-03-02  6:55                                                               ` Luiz Augusto von Dentz
2022-03-02  9:59                                                                 ` Chris Clayton
2022-03-02  8:54                                                             ` Chris Clayton
2022-02-24  8:24                                   ` Chris Clayton
2022-02-21 17:12                 ` Luiz Augusto von Dentz [this message]
2022-02-21 17:18                   ` Luiz Augusto von Dentz
2022-02-24 10:26 ` Thorsten Leemhuis

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=CABBYNZL3ARfn7DkQ7n_P-NqHvThdB+EbeKoHkEEk1i0g3iZVeg@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lists@colorremedies.com \
    /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;
as well as URLs for NNTP newsgroup(s).