summaryrefslogtreecommitdiffstats
path: root/core/btdiscovery.cpp
diff options
context:
space:
mode:
authorGravatar Dirk Hohndel <dirk@hohndel.org>2017-07-03 17:28:27 -0700
committerGravatar Dirk Hohndel <dirk@hohndel.org>2017-07-03 21:58:26 -0700
commit345e063eb5ff76306e4aafc110351c1bee0e1335 (patch)
treead649caa76be212ea55aad416d69e64d8f572591 /core/btdiscovery.cpp
parentbc864c3bce9a004f60879d33e61f97511ecbed93 (diff)
downloadsubsurface-345e063eb5ff76306e4aafc110351c1bee0e1335.tar.gz
Rewrite the matching code for BT devices
This should be much more robust in getting us the correct Bluetooth address and the correct vendor / product for our selection. When we pick a paired device, we extract the address right from its name. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'core/btdiscovery.cpp')
-rw-r--r--core/btdiscovery.cpp5
1 files changed, 0 insertions, 5 deletions
diff --git a/core/btdiscovery.cpp b/core/btdiscovery.cpp
index 6b0cf266d..a59bb5ccd 100644
--- a/core/btdiscovery.cpp
+++ b/core/btdiscovery.cpp
@@ -175,11 +175,6 @@ QList<BTDiscovery::btVendorProduct> BTDiscovery::getBtDcs()
return btDCs;
}
-QList <BTDiscovery::btVendorProduct> BTDiscovery::getBtAllDevices()
-{
- return btAllDevices;
-}
-
// Android: As Qt is not able to pull the pairing data from a device, i
// a lengthy discovery process is needed to see what devices are paired. On
// https://forum.qt.io/topic/46075/solved-bluetooth-list-paired-devices