Re: Can't connect a Xbox one controller

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Le vendredi 19 août 2016 à 11:43 +0300, Luiz Augusto von Dentz a
écrit :
> Hi Anthony,
> 
> On Thu, Aug 18, 2016 at 8:46 PM, Anthony Bourguignon <contact@toniob.
> net> wrote:
> > 
> > Le jeudi 18 août 2016 à 19:20 +0300, Luiz Augusto von Dentz a écrit
> > :
> > > 
> > > Hi Anthony,
> > > 
> > > On Thu, Aug 18, 2016 at 5:52 PM, Anthony Bourguignon <contact@ton
> > > iob.
> > > net> wrote:
> > > > 
> > > > 
> > > > 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
> > > > > @ton
> > > > > iob.
> > > > > 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 ?
> > > 
> > > Well perhaps we can compare to what other stacks are responding,
> > > but
> > > this seem quite weird given L2CAP_Config request is an essential
> > > part
> > > of setting up L2CAP connections so a response with unknown
> > > options
> > > sounds kind broken, but perhaps other stacks are ignoring it.
> > 
> > I've juste made a capture with my android tablet. Maybe it'll help.
> > Association failed two times and succeded on the third one.
> 
> It seems the configuration request works just fine here:
> 
> < ACL Data TX: Handle 13 flags 0x02 dlen 12
> 
>                                                            83.379233
>       L2CAP: Connection Request (0x02) ident 15 len 4
>         PSM: 17 (0x0011)
>         Source CID: 75
> > 
> > HCI Event: Number of Completed Packets (0x13) plen
> > 5                                                                  
> >                                                                    
> >               83.381502
>         Num handles: 1
>         Handle: 13
>         Count: 1
> > 
> > ACL Data RX: Handle 13 flags 0x02 dlen
> > 16                                                                 
> >                                                                    
> >                           83.383358
>       L2CAP: Connection Response (0x03) ident 15 len 8
>         Destination CID: 64
>         Source CID: 75
>         Result: Connection pending (0x0001)
>         Status: No further information available (0x0000)
> > 
> > ACL Data RX: Handle 13 flags 0x02 dlen
> > 16                                                                 
> >                                                                    
> >                           83.384600
>       L2CAP: Connection Response (0x03) ident 15 len 8
>         Destination CID: 64
>         Source CID: 75
>         Result: Connection successful (0x0000)
>         Status: No further information available (0x0000)
> < ACL Data TX: Handle 13 flags 0x02 dlen 16
> 
>                                                            83.385274
>       L2CAP: Configure Request (0x04) ident 16 len 8
>         Destination CID: 64
>         Flags: 0x0000
>         Option: Maximum Transmission Unit (0x01) [mandatory]
>           MTU: 640
> > 
> > ACL Data RX: Handle 13 flags 0x02 dlen
> > 16                                                                 
> >                                                                    
> >                           83.385939
>       L2CAP: Configure Request (0x04) ident 5 len 8
>         Destination CID: 75
>         Flags: 0x0000
>         Option: Maximum Transmission Unit (0x01) [mandatory]
>           MTU: 1480
> < ACL Data TX: Handle 13 flags 0x02 dlen 14
> 
>                                                            83.386624
>       L2CAP: Configure Response (0x05) ident 5 len 6
>         Source CID: 64
>         Flags: 0x0000
>         Result: Success (0x0000)
> > 
> > HCI Event: Number of Completed Packets (0x13) plen
> > 5                                                                  
> >                                                                    
> >               83.387708
>         Num handles: 1
>         Handle: 13
>         Count: 1
> > 
> > ACL Data RX: Handle 13 flags 0x02 dlen
> > 14                                                                 
> >                                                                    
> >                           83.388425
>       L2CAP: Configure Response (0x05) ident 16 len 6
>         Source CID: 75
>         Flags: 0x0000
>         Result: Success (0x0000)
> 
> There is another difference here is that the connection to PSM 17 is
> started by the Android device while in our case it is started by the
> controller without doing any SDP(?) which sounds like the controller
> has been connected before or it is not behaving like a HID device. Is
> there a way to reset the controller to a state that it clears the
> paired devices?

Here is a new dump from the android device. I've paired the xbox
controller to another device before for it to change its bluetooth pair
(I hope it worked).
btsnoop��>�f� �>�ol �>�rY �>��� �>����>�� 		�>���3��
�>����??���2�ZO>�
	Nokia 302�?�6 �?�] �?�� �?�!� �?�ߧ/��&?��9��?���?��
�&?����?�J�?�y=�&?��?����&?�box Wireless Controller�?��&?�		�?��?�
�&?�����?��?��&?��?��?� 

�?��?�
		�?�
�?�7@		�?�7�?�F�?��?��?��?��>���{��?��?��?�#
�?��?� �B)Q�&?�		�B)SP�B)W�B)YG		�B)[��&?�

�B)^��&?�

�B)a�
�&?�		�B)d�H&?�

�B)g�+	�&?�

�B)on
+�&?��B)�}2	�&?�

�B+�:3
�&?�E

�B+��,�&?�

�B+�
,�&?�

�B,��6�&?��B,��&?��_���g*�!�z�B,˙�B,� L�B-]�B-_� @L�B-b� @�B-d� L��B-h: 
@�B-o��B-rl 
L�B-t��B-wf @5����B-~w���B-�� ��L{w5�5�	
	5	
	5
5	5	5	5		en	j			55		%	%	%				^		��B-� @5����B-��  �B-�p L			(		�B-�, @L�B-���B-� @L�B-� M�B.F��B.I� @M�B.L3 @�B.N� M��B.Q� 
@�B.W��B.Z�B.]: 
M�B._� @5����B.i���B.� ��M{w6�5�	
	5	
	5
5	5	5	5		en	j			55		%	%	%				^		��B.� @5����B/(<���B/�T ��M{w			(		67	
	5$	
	5
5	5	5	5		en	j			55$		
55
5	5	�B/��@5����B/�R���B/�, ��M{w%Xbox Bluetooth Gamepad	%Gamepad	%Microsoft Corporation					@	!	(	(	6:67"&2	���B/�� @5����B/����B/� ��M{w	�	0	1'���u���	3	4'���u��	2&��u
�%u��	5&��u
�%u��	9%5F;fu��Bu��B/� @5����B/�����B0� ��M{w%5Ee�	)
%u�
�%u��	���	�%�u�%u���	!��	�%u��%u��	p%du��	PfU�B0L @5����B0�B08 zvMqn&�u��	�&�u��eU	|&�u���	 &�u���55				(		(	
(				�	
(	(�B0� @M�B0%��B0(c @M�B0� 	N�B1
�B1� 	@N�B1 N��B1s 
@�B1�
@�B1��B1# 

N�B1&.�B1)� 
@5�B13�B16; N	�B19�@����B1E����B1N� ��N{w5�	
	5	
	5
5	5	5	5		en	j			55		%	%	%				^		�	�B1QC @����B1^d�B1`� N
		(		�B1e @N�B1q��B1u( @N�B1w� O�B1��B1� @O�B1�
@�B1�	O��B1�� 
	@�B2�B2� 

O�B2��B2
n 
@5$�B2��B2� O	�B2� @����B2!����B2(� ��O{w67	
	5$	
	5
5	5	5	5		en	j			55$		
55
5	5	%Xbox Bluetooth	�B2*� @���	�B24����B2;� ��O{w Gamepad	%Gamepad	%Microsoft Corporation					@	!	(	(	6:67"&2	��	�	0	1'���
�B2=�@���
�B2H9���B2Os ��O{wu���	3	4'���u��	2&��u
�%u��	5&��u
�%u��	9%5F;fu��Bu�%5Ee�	�B2Qq @����B2[����B2b���O{w)
%u�
�%u��	���	�%�u�%u���	!��	�%u��%u��	p%du��	PfU&�u��	�&�B2d�@����B2o_oo�B2v� jfOa^�u��eU	|&�u���	 &�u���55				(		(	
(				�	
(	(�B2x�@O�B2���B2�� @O�B2��B2���B2��B2� @�B2��B2�/ @@�B3 @@�B3+ @��B3� 
@��B3 

@�B3t�B3 
@�B3��B3� A�B3&� AA�B3)L�B3+� AA�B3. A��B30* A��B32� 
A�B37s�B3;� 
A�B3>[�B4C��B4K� A���ځ

[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux