- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there any way in the headset application (on a CYBT-343026) to determine the cause of a disconnect from a phone. There are 2 things we'd like to determine:
1) did the disconnect come from the phone actually terminating the connection by shutting down a music app or disconnecting in the Bluetooth settings?
2) did the disconnect occur because the phone went out of range and cannot be "seen" anymore.
Based on the type of disconnect, I need to determine if I should accept the disconnect or try to reestablish the connection.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Corey,
I think in BT classic , the only option is to use wiced_bt_dev_register_connection_status_change API ( /20706-A2_Bluetooth/include/wiced_bt_dev.h ) . In the wiced_bt_connection_status_change_cback_t call back you will get the disconnect reason .
Thanks,
Anjana
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Corey,
I think in BT classic , the only option is to use wiced_bt_dev_register_connection_status_change API ( /20706-A2_Bluetooth/include/wiced_bt_dev.h ) . In the wiced_bt_connection_status_change_cback_t call back you will get the disconnect reason .
Thanks,
Anjana