Don't set the internal service discovery state twice to the same

The first call is not necessary as nothing has changed in the meantime.

Change-Id: I8db51fd725dd210b3d5c7b01d399d24877bf9b2f
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Fix remaining compiler warnings in QtConnectivity module

Change-Id: Iafadb39642c6b2944e8a873bdee49fb87e3ed5e9
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Use QLoggingCategory in Bluetooth QML import plugin.

Add some minor include cleanups as well.

Task-number: QTBUG-32253
Change-Id: I2ccb813a9dd85ca16c1ed8aab962418df8157890
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Merge remote-tracking branch 'origin/stable' into dev

Conflicts:
	src/bluetooth/qbluetoothservicediscoveryagent_qnx.cpp

Change-Id: Ic9e5cb3989426b90f6dad58d53dba366638ff35f
Add change log for 5.2.1

Change-Id: I12b294e9d3db91a1580b022ccae9dacb5b841ae0
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Don't build scanner example without QtQuick

Task-number: QTBUG-35711
Change-Id: I0406fb5edd8fb2a90046308853485eaaa4311a26
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Print error message in Bluetooth QML scanner example.

It required 15 min debugging the not working application till it was
discovered that the Bluetooth device was not turned on.

Change-Id: I05318c78dd4f19780d0b6343a4ae781703c18d91
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Document a somewhat peculiar signal behavior mismatch during Bt discovery

Change-Id: I8f9ac85e7753a9d6142bbefcd0e4bcda09e0f3d8
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reset QML Bluetooth discovery model if an error occurred during device discovery

This is due to a behavior difference of the finished() signal between
service and device discovery.

Change-Id: I59d6358171275987f07f86a6da80e8435445fd0e
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Emit PoweredOffError if required during device discovery start on Bluez

Change-Id: I12406b2a0fef831ed2e96340fac73156dfa71848
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Bump MODULE_VERSION to 5.2.2

Change-Id: I6a6f84dbc6cb3b38cb910464f2519222813b6caa
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reduce SDP discovery debug output on Bluez

Printing the entire SDP xml is just too verbose. This reduces the output
by multiple pages.

Change-Id: I08ffb7799f3c9f5a61de224e58e565719d44b81b
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Cleanup more duplicated code in SDP discovery class.

Change-Id: I4b6be592204cc435bfec508725d64cb8f7529a3b
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Merge remote-tracking branch 'origin/stable' into dev

Conflicts:
	.qmake.conf

Change-Id: I7295292bb7d9b5fc7eba8f099f4592b70de80d11
whitespace fixes

remove trailing whitespace, expand tab

Change-Id: I3361c6c431231c7463bb1dc9b53268935b22a72b
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Don't stop Bt discoveries while we have InvalidBluetoothAdapterError

This change complements 23a3863de809a4051ae6db4942145cb0cb624d6c.

The discovery process should not stop when the passed local adapter
address is invalid. While the first change ensures that start() cannot
be called stop() was still callable. The platform specific implementations
potentially set lastError to something else und thus would permit
a call to start() later on. This may lead to invalid internal states.

Change-Id: Ibfd87374bf712614fad90172894ea2e009ba198a
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>