Details
-
Bug
-
Resolution: Invalid
-
P2: Important
-
None
-
5.5.0
-
None
Description
bluez is disconnecting devices 3 minutes after discovery as stated in "Device discovery" in this http://www.bluez.org/bluez-5-api-introduction-and-porting-guide/ , even though this signal - QLowEnergyController::connected() is triggering.
Why does bluez not recognize the devices as being connected and continuing to drop the connection?
This bug report - https://bugreports.qt.io/browse/QTBUG-44622 - was quite likely the same issue.
I attached the hcidump verbose log from create connection to disconnect.
Attachments
Issue Links
- duplicates
-
QTBUG-44622 BLE code works on bluez 4.101, not working on bluez 5.28
- Closed