From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 202515] Bluetooth LE Extended Connect returning Command Disallowed
Date: Thu, 07 Feb 2019 23:48:27 +0000 [thread overview]
Message-ID: <bug-202515-62941-i0YCUNQMNt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202515-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202515
--- Comment #14 from Mathias Tillman (master.homer@gmail.com) ---
Sorry, was too quick to reply. As it turns out, the set ext scanning params
command *is* required, or it won't find any LE devices properly when scanning -
it will connect to already paired devices though.
As a test I decided to try and remove the set ext scanning params check
completely, and just send it even though it's reported as being not supported -
oddly enough this works, and scans are again working properly, so it definitely
seems like a problem with the controller.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-02-07 23:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 0:01 [Bug 202515] New: Bluetooth LE Extended Connect returning Command Disallowed bugzilla-daemon
2019-02-06 8:27 ` [Bug 202515] " bugzilla-daemon
2019-02-06 8:27 ` bugzilla-daemon
2019-02-06 9:07 ` bugzilla-daemon
2019-02-06 9:42 ` bugzilla-daemon
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:19 ` bugzilla-daemon
2019-02-06 11:58 ` bugzilla-daemon
2019-02-06 12:18 ` bugzilla-daemon
2019-02-06 19:36 ` bugzilla-daemon
2019-02-07 12:59 ` bugzilla-daemon
2019-02-07 22:55 ` bugzilla-daemon
2019-02-07 23:05 ` bugzilla-daemon
2019-02-07 23:48 ` bugzilla-daemon [this message]
2019-02-08 16:16 ` bugzilla-daemon
2019-02-08 17:35 ` bugzilla-daemon
2019-02-08 21:39 ` 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-202515-62941-i0YCUNQMNt@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;
as well as URLs for NNTP newsgroup(s).