All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Grandel <fgrandel@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Szymon Janc <Szymon.Janc@tieto.com>,
	BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Problems with incoming connection request on Nexus 4
Date: Thu, 30 Jul 2015 14:21:14 +0200	[thread overview]
Message-ID: <55BA16BA.5060302@gmail.com> (raw)
In-Reply-To: <BC4DBE9E-8369-4B20-BBE5-F175DD4C5626@holtmann.org>

Hi Marcel,

 >> Symptoms:
>> - The connection request times out.
>> - bt_io_accept() is being called but the accept_cb (=connect_cb) only gets called when the request times out.
>> - the device is stuck in the CONNECT READY state and never reaches the CONNECTED state
>>
>>
>> Any ideas how I could analyze/solve that problem? I'm stuck on this for many hours already...
>
> what does btmon actually tell you about what is going on with HCI.

= New Index: 10:68:3F:56:AD:35 (BR/EDR,UNKNOWN,hci0)            [hci0] 
0.629837
@ Advertising Added: 1
< HCI Command: LE Set Advertising Para.. (0x08|0x0006) plen 15  [hci0] 
4.398493
         Min advertising interval: 1280.000 msec (0x0800)
         Max advertising interval: 1280.000 msec (0x0800)
         Type: Connectable undirected - ADV_IND (0x00)
         Own address type: Public (0x00)
         Direct address type: Public (0x00)
         Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
         Channel map: 37, 38, 39 (0x07)
         Filter policy: Allow Scan Request from Any, Allow Connect 
Request from Any (0x00)
 > HCI Event: Command Complete (0x0e) plen 4                     [hci0] 
4.401392
       LE Set Advertising Parameters (0x08|0x0006) ncmd 1
         Status: Success (0x00)
< HCI Command: LE Set Advertise Enable (0x08|0x000a) plen 1     [hci0] 
4.401484
         Advertising: Enabled (0x01)
 > HCI Event: Command Complete (0x0e) plen 4                     [hci0] 
4.402277
       LE Set Advertise Enable (0x08|0x000a) ncmd 1
         Status: Success (0x00)

There is no connection related HCI activity going on at all on the Nexus 
4 side. You can see from the debug logs that I sent before, that the 
connection is being initiated correctly. The bt_io_accept() call does 
return without error, just the accept callback never gets called. To me 
it seems as if the Nexus4 was not responding to the incoming connect 
request.

 > Remember that a connection disables advertising in the controller.

The advertising being aborted on connect is not a problem. The 
advertising part works flawlessly. Connecting

Florian

  reply	other threads:[~2015-07-30 12:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  2:10 Problems with incoming connection request on Nexus 4 Florian Grandel
2015-07-29 13:51 ` Marcel Holtmann
2015-07-30 12:21   ` Florian Grandel [this message]
2015-07-30 12:25     ` Marcel Holtmann
2015-07-30 13:11       ` Florian Grandel
2015-07-30 16:00         ` Marcel Holtmann
2015-07-30 16:22           ` Adam Moore
2015-07-31 19:47           ` Lukasz Rymanowski
2015-07-31 22:41             ` Adam Moore
2015-08-01 18:54               ` Florian Grandel
2015-08-05  0:07                 ` Adam Moore
2015-08-05  1:32                   ` Marcel Holtmann

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=55BA16BA.5060302@gmail.com \
    --to=fgrandel@gmail.com \
    --cc=Szymon.Janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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.