Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.2
-
None
-
-
8
-
Team One Foundation Sprint 50
Description
Service scan with QBluetoothServiceDiscoveryAgent first performs a device scan, and once the device scan is completed, a service (SDP) scan is triggered automatically.
However when starting the QtConnectivity pingpong example with Windows in the client role, the device scan often doesn't stop and consequently the service scan doesn't start.
This seems to be (at least) because the
QWinRTBluetoothDeviceDiscoveryWorker::m_pendingPairedDevices
has been decremented too many times, to "-1". The related checks to determine if the scan is then finished or not are not then done properly and scan is not terminated.
The excessive decrement implications are likely two-fold:
1) The device scan never stops
2) Some devices are left unscanned and their services are not found
Hence it is important to understand why this happens instead of just changing the checks.
N.B. this is not consistent behaviour, other kind of behaviour, even a success, can occasionally be seen. This means there is some timing or pairing related factors at play too.
Attachments
For Gerrit Dashboard: QTBUG-99685 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
391140,3 | Decrement the pending paired device counter only once per device | dev | qt/qtconnectivity | Status: MERGED | +2 | 0 |
392399,2 | Decrement the pending paired device counter only once per device | 6.3 | qt/qtconnectivity | Status: MERGED | +2 | 0 |
392400,2 | Decrement the pending paired device counter only once per device | 6.2 | qt/qtconnectivity | Status: MERGED | +2 | 0 |
392401,4 | Decrement the pending paired device counter only once per device | tqtc/lts-5.15 | qt/tqtc-qtconnectivity | Status: MERGED | +2 | 0 |