All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Grandel <fgrandel@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>,
	Szymon Janc <Szymon.Janc@tieto.com>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Problems with incoming connection request on Nexus 4
Date: Wed, 29 Jul 2015 04:10:28 +0200	[thread overview]
Message-ID: <55B83614.8090702@gmail.com> (raw)

Hi Marcel and Szymon,

I'm currently testing my code on my Nexus 4 device. Multi-Advertising 
works nicely but I can't get the device to accept incoming connection 
requests while in peripheral mode. I'm using Nordic's nRF Master Control 
app on my Samsung S4 in the central role for testing.

Here some sample debug output. When launching the connection request I get:

07-29 03:14:36.816  16843-16843/? I/bluetoothd﹕
mgmt_if: > 0b 00 00 00 1e 00 05 46 ab c2 01 94 00 00 00 00
.......F........

07-29 03:14:36.816  16843-16843/? I/bluetoothd﹕
mgmt_if:   00 11 00 0b 09 66 67 2d 73 61 6d 73 75 6e 67 04
.....fg-samsung.

07-29 03:14:36.816  16843-16843/? I/bluetoothd﹕
mgmt_if:   0d 0c 02 5a
...Z

07-29 03:14:36.816  16843-16843/? I/bluetoothd﹕
mgmt_if: [0x0000] event 0x000b

07-29 03:14:36.816  16843-16843/? D/bluetoothd﹕
external/bluetooth/bluez/android/bluetooth.c:mgmt_device_connected_event() 
94:01:C2:AB:46:05 type 0

07-29 03:14:36.829  16817-16875/com.android.bluetooth D/BlueZ﹕ 
external/bluetooth/bluez/android/hal-bluetooth.c:handle_acl_state_changed() 
state 0

07-29 03:14:37.100  16843-16843/? D/bluetoothd﹕ 
external/bluetooth/bluez/android/gatt.c:connect_confirm()

07-29 03:14:37.100  16843-16843/? D/bluetoothd﹕ 
external/bluetooth/bluez/android/gatt.c:device_set_state() gatt: Device 
94:01:C2:AB:46:05 state changed DISCONNECTED -> CONNECT READY


And then after the timeout:

07-29 03:15:07.083  16843-16843/? D/bluetoothd﹕ 
external/bluetooth/bluez/android/gatt.c:connect_cb()

07-29 03:15:07.083  16843-16843/? E/bluetoothd﹕ gatt: connection failed 
HUP or ERR on socket: Connection reset by peer (104)

07-29 03:15:07.083  16843-16843/? D/bluetoothd﹕ 
external/bluetooth/bluez/android/gatt.c:device_set_state() gatt: Device 
94:01:C2:AB:46:05 state changed CONNECT READY -> DISCONNECTED


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...

Thanks!

Florian

             reply	other threads:[~2015-07-29  2:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  2:10 Florian Grandel [this message]
2015-07-29 13:51 ` Problems with incoming connection request on Nexus 4 Marcel Holtmann
2015-07-30 12:21   ` Florian Grandel
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=55B83614.8090702@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.