Hi Justinas, On Thu, Jul 9, 2015 at 11:12 AM, Justinas Vilimas <justinas@xxxxxxxxxxxx> wrote: > Hello everyone, > > I am having trouble on retrieving GATT services with Android >=5.0 devices. GATT services are hosted on a RaspberryPi B+ (with a Bluetooth 4.0 dongle ASUS BT-400). > > I have tested with numerous configurations using different BlueZ versions, kernels and phone models with no success. Android <5.0 and iOS devices work perfectly fine. > > Current latest setup I use is 4.1.1+ kernel and 5.32 BlueZ build with experimental enabled. > > The whole procedure is as follows: > 1. I start the hci0 device and then launch the 5.32 bluetoothd with -nEd params. > > 2. I initially set the advertising data with this command: > sudo hcitool -i hci0 cmd 0x08 0x0008 14 02 01 02 02 0A A0 0D 09 54 61 62 6C 65 41 69 72 54 56 53 57 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 If you are running bluetoothd you should probably not use hcitool manually to advertise, use LEAdvertisingManager1 interface: https://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/advertising-api.txt It will also take care of start advertising. > 3. And enable advertising with the command: sudo ./hciconfig hci0 leadv 0 > > 4. Also I start the sample ‘example-gatt-server’ from the test folder in the BlueZ repository. > > The bluetoothd seems to accept the sample gatt services and add it to the gatt-database. > > When trying to connect to the RPi, Android device successfully discovers the peripheral and successfully connects to it. The device also retrieves initial 1800 and 1801 services, but no additional services from the ‘example-gatt-server'. Whereas Android <5.0 and all tested iOS devices successfully retrieves all GATT services and is able to read or write the discovered characteristics. > > I noticed in the bluetoothd log that Android 5.0 fails to perform the MTU exchange: > bluetoothd[11618]: src/adapter.c:connected_callback() hci0 device 48:59:29:61:F0:54 connected eir_len 14 > bluetoothd[11618]: src/adapter.c:new_link_key_callback() hci0 new key for 48:59:29:61:F0:54 type 4 pin_len 0 store_hint 0 > bluetoothd[11618]: src/device.c:device_bonding_complete() bonding (nil) status 0x00 > bluetoothd[11618]: src/adapter.c:resume_discovery() > bluetoothd[11618]: src/gatt-database.c:connect_cb() New incoming LE ATT connection > bluetoothd[11618]: attrib/gattrib.c:g_attrib_ref() 0x16233d8: g_attrib_ref=1 > bluetoothd[11618]: src/device.c:gatt_debug() MTU Exchange failed. ATT ECODE: 0x06 > bluetoothd[11618]: src/device.c:gatt_client_ready_cb() status: failed, error: 6 Error code 6 is for not supported error, I suppose we can still use MTU as 23 in that case and continue from there, but it beats me why Android would go back and remove support for it. > How is Android >=5.0 different from older versions and iOS when talking with GATT server? Is there any way to solve this? > > Help is greatly appreciated, thanks! > > Best wishes, > Justinas Vilimas > > -- > 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
