linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Bourguignon <contact@toniob.net>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Can't connect a Xbox one controller
Date: Thu, 18 Aug 2016 16:52:34 +0200	[thread overview]
Message-ID: <1471531954.4976.13.camel@toniob.net> (raw)
In-Reply-To: <CABBYNZKvqrbF7XzW4yShJyM2wXWckJX7X5PD6gU=mT7Pg6HUGw@mail.gmail.com>

Le jeudi 18 août 2016 à 16:56 +0300, Luiz Augusto von Dentz a écrit :
> Hi Anthony,
> 
> On Thu, Aug 18, 2016 at 1:11 PM, Anthony Bourguignon <contact@toniob.
> net> wrote:
> > 
> > Hi,
> > 
> > I've recently bought a new xbox one controller as the 2016 version
> > has
> > bluetooth connectivity.
> > 
> > The controller is pairing and connecting well on a windows 10
> > computer
> > and an android 4.4 tablet. But I can"t make it connect under linux
> > (Debian unstable, kernel 4.6 and 4.7-rc7, bluez 5.40 from
> > experimental). The pairing is ok but when I try to connect to
> > controller, it stays connected for less than one second, then
> > disconnects, then connects again and so one until the controller
> > goes
> > to sleep, because of the lack of a remote connection.
> > 
> > Any idea ?
> 
> It seems there is some problem configuring the L2CAP connection
> (probably for SDP):
> 
> > 
> > ACL data: handle 256 flags 0x02 dlen 15
>     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 3 clen 1
>       Failure - unknown options
>       RFC
> < ACL data: handle 256 flags 0x00 dlen 12
>     L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040

So, is it a bug of bluez or of the controller firmware ? Why is it
possible to make a connection with an android tablet ?

Is there something more I can do to help ?

  reply	other threads:[~2016-08-18 14:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 10:11 Can't connect a Xbox one controller Anthony Bourguignon
2016-08-18 13:56 ` Luiz Augusto von Dentz
2016-08-18 14:52   ` Anthony Bourguignon [this message]
2016-08-18 16:20     ` Luiz Augusto von Dentz
2016-08-18 17:46       ` Anthony Bourguignon
2016-08-19  8:43         ` Luiz Augusto von Dentz
2016-08-19  9:28           ` Anthony Bourguignon
2016-08-19 18:02 ` Vinicius Costa Gomes
     [not found]   ` <1471642506.3626.5.camel@toniob.net>
2016-08-19 23:34     ` Vinicius Costa Gomes
2016-08-20 12:54       ` Anthony Bourguignon
2016-08-24 14:02         ` Vinicius Costa Gomes
2017-11-09 13:49           ` Bastien Nocera
2017-11-09 14:28             ` Bastien Nocera
2017-11-09 15:11               ` Bastien Nocera
2017-11-13 10:04                 ` Bastien Nocera

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=1471531954.4976.13.camel@toniob.net \
    --to=contact@toniob.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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).