Intermittent failure to start Notification Session |
|||||||||||
Issue descriptionI've recently begun to see some errors starting a notification session (see [1]). The error returned to the callback is GATT_ERROR_FAILED. Bluetooth folks, what does this mean, and how can I prevent this error from occurring? [1] https://cs.chromium.org/chromium/src/device/bluetooth/bluetooth_remote_gatt_characteristic.h?gsn=StartNotifySession
,
Aug 15 2017
,
Aug 16 2017
,
Aug 25 2017
,
Aug 30 2017
Changed name to differentiate from Issue 760413.
,
Sep 13 2017
,
Sep 13 2017
This may be an Android side issue. Starting a notification session is just a normal write to the client characteristic configuration descriptor for that remote characteristic. If that write fails, the start notification session will also fail. Do we have logs for this?
,
Sep 13 2017
,
Sep 13 2017
Kyle to get us logs.
,
Sep 15 2017
khorimoto@ any update on the logs?
,
Sep 15 2017
Will get logs on Monday morning.
,
Sep 18 2017
jonmann@ to get logs for this one. Jon, please make sure you enable Bluetooth HCI logs on your Android device before testing. Thanks!
,
Sep 20 2017
,
Sep 20 2017
couldn't reproduce with latest builds |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by khorimoto@chromium.org
, Aug 8 2017