Languages

Menu
Sites
Language
Setting the auto_connect flag to true in the bt_gatt_connect function reboots Gear S3.

I am trying to connect to a BLE device using the bt_gatt_connect function using the following code:

ret = bt_gatt_connect(remote_address, true);
if (ret != BT_ERROR_NONE) {
    dlog_print(DLOG_ERROR, LOG_TAG, "Failed to connect LE device.");
} else {
	dlog_print(DLOG_INFO, LOG_TAG, "GATT connect Success!");
}

dlog_print(DLOG_ERROR, LOG_TAG, "GATT Exception : %s", strerror(errno));

However, when I set the auto_connect flag to true, it causes device rebooting.

The return value of the function is BT_ERROR_NONE, but it does not proceed to the next statement. What is very strange is that these issues do not occur in Gear S2 but in Gear S3. I tested it over and over again, but I always showed the same issue. In Gear S2, connection is normal and Auto Connection function works normally. And in Gear S3, if the auto_conenct flag is set to false, a normal connection is made. However, Auto Connection function does not work.

When Gear S3 reboots the device itself, it does not log Crash Information, nor does it generate any error logs.

List

Responses

4 Replies
Yasin Ali

Hi,

You may try a light reset. Check for privileges and features that must be present considering your

whole application. Also check for API conflict, if any resolve it.

Thanks

June Heo

I tried

- Light Reset

- Factory Reset

- Update firmware

- Connect to new phone

- Give all priviliges / features in manifest

- Eliminate every other codes except bt_init & gatt_connect

- Try to connect other BLE devices

 

Anything wasn't solve the issue. But in Gear S2, it still works perfectly.

Yasin Ali

Then you may try with different approach for your solution devlopment.

For example you may try with Samsung Accessory Protocol (SAP).

G-M NGUEKO

SAP answer is not on the point AT ALL, here we are trying to connect the gearS3 towards a generic ble device.

So it looks like a bug of the bluetooth (ble stack) on the gearS3. Maybe it is due to tizen 2.3.2 since on the gearS2 it works (I assume the original poster didn't upgrade its gearS2 to tizen 2.3.2).

hopefully it will be fixed with tizen 3.0.0 on the gearS3. :-)

Note that I have the same issue of crashing , and the crash was so bad that I lost all my Shealth data fo that day togetehr with the Shealth profile on my gearS3 !!!