Tizen Developers

Hello,

Thank you for your answer. I have read all that tutorial multiple times. 

Yes the device can be found in callback of bt_adapter_foreach_bonded_device, but that callback does not return BLE service handles.

To get these handles I have to use connect to BLE device and get them with  bt_gatt_client_get_service. So I use bt_gatt_connect and bt_gatt_client_create with address I got from bt_adapter_foreach_bonded_device. After that I use bt_gatt_client_get_service to get handle of service with uuid I got from bt_adapter_foreach_bonded_device. But this method returns BT_ERROR_NO_DATA.

Hi,
As I understand it works 1st time but it does not work after Tizen phone has been rebooted.  Or bt_gatt_client_get_service does not work all time?
Alexey.

Hello,

Yes, It works after device was LeScanned and connected (bonded) after LeScan (bt_gatt_client_get_service also works). And after disconnect /reconnect also works correctly. But if device was rebooted it does not work until I do unpair (on watch and phone) and repeat LeScan/bonding. I think it works because those handles are cached by OS during LeScan (or bonding), and I could use them, but after reboot this cache dissapears and I have to rediscover that service handles. The only way I have found how I can do it is to unpair devices and repeat LeScan.

And my question can be reformulated as: Is there any way to discover services on particular device (with known address, which is bonded and does not advertise scan records by LeScan)? Or Tizen somehow does it (discovering services) automatically (as there is no function discover_services)? If it does it automatically, when does it do discovery?

For example Android has similar case, there is a method getServices, but is works only after services was discovered by LeScan or  btDeviceInstance.discoverServices() and returns only cached values and so will not work after reboot. Is there any similar to btDeviceInstance.discoverServices() function?

I have found out that problem even not in services. It is in connection with gatt. I do bond with watch. All works correctly. After it I reboot Tizen phone.

I can see watch among bonded with values "bonded" "not connected". I use 

ret = bt_gatt_connect(dev_mac_, true);

It returns ok and I just wait for connection.

And see callback on connection gatt_connection_state_changed_cb(int result, bool connected, const char *remote_address, void *data) twice. First is returns connected with watch and secondly in less than second it returns disconnected. If I try to connect_gatt in case of status disconnect - it will be endless loop. It callback will invoked: connect, disconnect, connect, disconnect, connect, disconnect...

I looked at watch - status of connection on watch does not change, which means that Tizen invoke callback connected but no connection really made. And this probably is the reason I can't use services.

Before reboot this code does not cycle. And I have similar code for Android all is ok - so I don't think the reason is in watch. 

Hi,
Yes in case of endless loop connect/disconnect it looks like error. What mobile device/watch did you use?
Is this loop for any case? Did you try other variants of connection between different Tizen devices?
Alexey.

Hi Leonid,

As of now services can be discovered or retrieved only after connection is established, even if device is already bonded.

And there is no such API to discover services explictly like bt_gatt_discover_characteristics so far. So evertime when Application wants to access services, connection has to be established.

1. bt_gatt_connect

2. bt_gatt_client_create

We will check more on this and get back to you. Please provide us the information about the binary version you used.

Regards,

Paras

I am sorry, but I can't share the logs. This phone is not mine, I'm just writing library which should work with Tizen and use this phone to test it. The real owner of phone prohibited sharing the logs. 

Maybe someone else having this issue could share the logs.