Re: Not shown registered gatt services on an android 5.1.1

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

 



Hello Luiz,


On 7 April 2016 at 13:17, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote:
> Hi Tak,
>
> On Thu, Apr 7, 2016 at 2:20 PM, Hyuntak Lee <pphdev12@xxxxxxxxx> wrote:
>> Dears,
>>
>> I am testing a gatt server with iphone and android.
>> iPhone is working nicely, but unfortunately andorid cannot retrive
>> registered GATT services.
>> I tested with a bluez-5.39/test/example-gatt-server file.
>> Can you advice me?
>>
>> My step is below:
>>
>> * Peripheral env
>> ** Bluez 5.39
>> ** Linux Kernel 3.18
>> ** BT Dongle: NEXT-204BT(CSR 4.0)
>>
>> * Central env
>> ** Android 5.1.1 and iOS 9.3.1
>> ** Test app: nRF MCP
>>
>> * Build configure
>> ./configure --prefix=/usr     \
>>             --sysconfdir=/etc    \
>>             --localstatedir=/var \
>>             --enable-library      \
>>             --enable-experimental \
>>             --disable-systemd
>>
>> * STEP
>> 1. Executes a bluetooth daemon:
>> $ bluetoothd -ndE
>>
>> 2. Register gatt services
>> $ python bluez-5.39/test/example-gatt-server
>> For register service(Heart Rate, Battery Service)
>>
>> 3. To advertising and pairing:
>> $ hciconfig hci0 reset
>> $ hciconfig hci0 pscan;   # PSCAN need to pair with android
>> $ hcitool -i hci0 cmd 0x08 0x000a 00;
>> $ hcitool -i hci0 cmd 0x08 0x0008 03 02 0a 0a 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00;
>> $ hcitool -i hci0 cmd 0x08 0x000a 01;
>>
>> 4. connect to gatt server
>> 4.1 with iOS 9.3.1
>> Retrieved list
>> - Heart Rate (UUID: 0x180D)
>> - Battery Service (UUID: 0x180F)
>>
>> 4.2 with android 5.1.1
>> Retrieved list
>> - Generic Attribute(UUID: 0x1801)
>> - Generic Access(UUID: 0x1800)
>>
>>
>>
>> Only android don't get registerted services.
>> I founded different part of bluetoothd log in the case of iphone and
>> android. I hope these are helpful to you.
>>
>> Logs of iOS case:
>>
>> bluetoothd[2976]: src/gatt-database.c:connect_cb() New incoming LE ATT
>> connection
>> bluetoothd[2976]: attrib/gattrib.c:g_attrib_ref() 0x1e53230: g_attrib_ref=1
>> bluetoothd[2976]: src/gatt-client.c:btd_gatt_client_connected() Device
>> connected.
>> bluetoothd[2976]: src/device.c:load_gatt_db() Restoring
>> 57:92:97:B5:A8:C4 gatt database from file
>> bluetoothd[2976]: No cache for 57:92:97:B5:A8:C4
>> bluetoothd[2976]: src/device.c:gatt_debug() MTU exchange complete, with MTU: 158
>> bluetoothd[2976]: src/device.c:gatt_debug() Read By Grp Type - start:
>> 0x0001 end: 0xffff
>> bluetoothd[2976]: src/device.c:gatt_debug() Read By Grp Type - start:
>> 0x0021 end: 0xffff
>> bluetoothd[2976]: src/device.c:gatt_debug() Read By Type - start:
>> 0x0006 end: 0x0009
>> bluetoothd[2976]: src/device.c:gatt_debug() Find Info - start: 0x0009
>> end: 0x0009
>> bluetoothd[2976]: src/device.c:gatt_debug() Write Req - handle: 0x0009
>> bluetoothd[2976]: src/gatt-database.c:gatt_ccc_write_cb() CCC write
>> called for handle: 0x0009
>> bluetoothd[2976]: src/device.c:gatt_debug() Primary services found: 8
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x0001, end:
>> 0x0005, uuid: 00001800-0000-1000-8000-00805f9b34fb
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x0006, end:
>> 0x0009, uuid: 00001801-0000-1000-8000-00805f9b34fb
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x000a, end:
>> 0x000e, uuid: d0611e78-bbb4-4591-a5f8-487910ae4366
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x000f, end:
>> 0x0012, uuid: 0000180f-0000-1000-8000-00805f9b34fb
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x0013, end:
>> 0x0018, uuid: 00001805-0000-1000-8000-00805f9b34fb
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x0019, end:
>> 0x001d, uuid: 0000180a-0000-1000-8000-00805f9b34fb
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x001e, end:
>> 0x0027, uuid: 7905f431-b5ce-4e99-a40f-4b1e122d00d0
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x0028, end:
>> 0x0033, uuid: 89d3502b-0f36-433a-8ef4-c502ad55f8dc
>> bluetoothd[2976]: src/device.c:gatt_debug() Secondary service
>> discovery failed. ATT ECODE: 0x0a
>>
>> Logs of android case:
>>
>> bluetoothd[2976]: src/gatt-database.c:connect_cb() New incoming LE ATT
>> connection
>> bluetoothd[2976]: attrib/gattrib.c:g_attrib_ref() 0x1e35fe8: g_attrib_ref=1
>> bluetoothd[2976]: src/gatt-client.c:btd_gatt_client_connected() Device
>> connected.
>> bluetoothd[2976]: src/device.c:load_gatt_db() Restoring
>> 30:75:12:94:47:D5 gatt database from file
>> bluetoothd[2976]: No cache for 30:75:12:94:47:D5
>> bluetoothd[2976]: src/device.c:gatt_debug() MTU Exchange failed. ATT ECODE: 0x06
>
> We did have some problems with Android up to 4.4 when Android would
> stop sending any request when it gets a MTU Exchange but this has been
> working with 5.1 and later so Im not sure if this is related. You can
> check if that is the case with the following patch:
> http://www.spinics.net/lists/linux-bluetooth/msg66498.html (I end up
> abandoning it since it was supposed to work with more recent
> Androids).
>

I'm seeing the same issue of an Android phone that will not connect to a
Bluez (5.38) gatt server running on a Raspberry Pi.
An iPhone 4S (ios 9.3.1) will connect as will another Raspberry Pi using
bluetoothctl (5.36).
The phone that will not connect is a Google Nexus 5x (Android 6.0.1)

I'm use nRF Master Control Panel app on both iPhone and Android.
The log file from Android is:

nRF Master Control Panel, 2016-04-07
No name (00:02:5B:03:E3:E3)
V21:34:19.768Connecting to 00:02:5B:03:E3:E3...
D21:34:19.777gatt = device.connectGatt(autoConnect = false)
D21:34:24.943[Callback] Connection state changed with status: 133 and new
state: DISCONNECTED (0)
E21:34:24.955Error 133 (0x85): GATT ERROR
I21:34:24.969Disconnected
D21:34:24.981gatt.close()

I've tried adding the patch you suggested above and I still see the same in
the phones log file.

The error message on the phone is the same as I have had before and has been
solved previously by adding  'ControllerMode = le' in main.conf. History of
that discussion is at:
 http://marc.info/?l=linux-bluetooth&m=145505537711496&w=2

Since moving to 5.38 modifying the main.conf no longer seems to fix the issue.


>> bluetoothd[2976]: src/device.c:gatt_debug() Primary services found: 2
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x0001, end:
>> 0x0005, uuid: 00001801-0000-1000-8000-00805f9b34fb
>> bluetoothd[2976]: src/device.c:gatt_debug() start: 0x0014, end:
>> 0xffff, uuid: 00001800-0000-1000-8000-00805f9b34fb
>> bluetoothd[2976]: src/device.c:gatt_debug() Secondary service
>> discovery failed. ATT ECODE: 0x10
>>
>>
>> It looks like if request is from an android, cannot find primary services.
>> How can I use a GATT service with an android?
>> Pls advise me.
>>
>> Best Regards,
>> Tak
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>
> --
> Luiz Augusto von Dentz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[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