Environment
- App: nRF Connect for Mobile (Android / iOS, latest release)
- DUT: Bluetooth dual‑mode device (supports both BR/EDR(Classic BT) and BLE)
Describe the issue When using nRF Connect for Mobile to connect to a dual‑mode Bluetooth device: If the BR/EDR (Classic Bluetooth) link gets disconnected, the nRF Connect UI reports the device as Disconnected. However, the underlying BLE GATT physical link is still alive.
This creates misleading UI status: the app displays disconnected state, but actual BLE connection is maintained and functional.
We would like to confirm:
- Is this expected application behavior, or is this a UI‑state‑tracking bug inside nRF Connect for Mobile?
- For dual‑mode peripherals, does nRF Connect track BR/EDR and BLE connection states separately or merged together?
Steps to reproduce
- Establish both BR/EDR (Classic BT) and BLE connections with a dual‑mode DUT from mobile phone.
- Keep BLE GATT connection active in nRF Connect for Mobile.
- Trigger disconnection of only the BR/EDR link (Classic Bluetooth).
- Observe nRF Connect UI: device shows status as Disconnected.