Windows: optimize BTLE device discovery

Previously we were doing full service discovery every time when the
BluetoothLEAdvertisementWatcher reports a new advertisement.
This results in a very high CPU usage during BTLE device discovery
on some configurations.

In practice such approach might not be needed, because most BTLE
devices repeatedly advertise the same data.

With this patch we do a detailed service discovery only when a new
device is added, or when the list of advertised services has changed.
Note that we still need to handle all the incoming advertisements,
because we want to report changes in other parameters, such as RSSI.

Fixes: QTBUG-111116
Pick-to: 6.5 6.5.0 6.2
Change-Id: I0863739a2fb21d04e9a728adc68e3f197f1966e3
Reviewed-by: Juha Vuolle <juha.vuolle@qt.io>
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>

0 files changed, 0 insertions, 0 deletions