This change updates the Bluetooth documentation to reflect the addition
of the native Win32 backend.

Task-number: QTBUG-40698
Change-Id: I8d2bc2146527a17f1f47fff541730b94f58286fb
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

Change-Id: I83175151c0eef1a11d2f21648cc04c86e46777c1

This change enables the optional use of the Win32-based Bluetooth
backend on Windows. By default, the WinRT backend is used, if
supported by the platform. The use of the Win32 backend must be
selected by the -native-win32-bluetooth configuration option.

Task-number: QTBUG-40698
Change-Id: I6904bf077467d826e3ff5ad026ebae5f955f2e37
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

 Conflicts:
	src/bluetooth/qlowenergycontroller_darwin.mm
	src/bluetooth/qbluetoothdevicediscoveryagent_ios.mm

The latter was auto-resolved by keeping, but is in fact removed on dev, so reremoved.

Change-Id: Ifa47f61836450d59ea8e47a92b84f57ab06863f7

Change-Id: Ib78a07e39387cfe5edd97015f1e9e3095c86d4fa
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

htonl and htons cannot be found when compiling src/sdpscanner. This patch
extends the bluez compile test such that the missing symbols are checked
as well. As outcome RHEL 6.10 will have no bluez support and the dummy
backend will be built.

Fixes: QTBUG-74581
Change-Id: Ie71ed05d72f94e43630be41bc589de5f24fb2194
Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>

Instead, use the shared implementation (and the declaration from the *_p.h)

Fixes: QTBUG-75348
Change-Id: Icbcbb752df1a9b8865ea4f4ef06f2b59dda577cd
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>

Task-number: QTBUG-75348
Change-Id: I5e2e08291cd17c1f1ef8639d422f4421520ed371
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

Implement the proper interface from QBluetoothSocketBasePrivate,
remove a dummy base class. Remove all public API from
qbluetoothsocket_osx.mm and re-use the code in qbluetoothsocket.cpp.
The code generally is the same, a bit of re-hashin/deletion.

Task-number: QTBUG-75348
Change-Id: I0034dfd283daf9d51775d8f9551b85d2d436aa85
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

 Conflicts:
	.qmake.conf

Change-Id: Ic20d930b8efc843c39c6ab2af5848612d27fd661

 Conflicts:
	.qmake.conf

Change-Id: I48ae70ffcb475ced4a05619310f496527cdd4166

Task-number: QTBUG-74391
Change-Id: I4e66d50a4b98a728956e351d1603e26933dd02c7
Reviewed-by: Paul Wicking <paul.wicking@qt.io>

handle and GATT_INSUFFICIENT_AUTHENTICATION and GATT_INSUFFICIENT_ENCRYPTION
statuses explicitly to close the established connection with AuthorizationError

Change-Id: I6077d2b4e90daaac527fff7145bc71d7a4e032a3
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

when Android receives GATT_INSUFFICIENT_AUTHORIZATION or GATT_INSUFFICIENT_ENCRYPTION,
it breaks connection with fair reason GATT_CONN_TERMINATE_LOCAL_HOST,
which shadows the original GATT_INSUFFICIENT_ENCRYPTION from the user.
As we didn't see Android closing connection with GATT_CONN_TERMINATE_LOCAL_HOST
in cases other than described above, naively treat it like AuthorizationError

Change-Id: I43a19c9eaf793a595765850938d757a09324a545
Reviewed-by: Evgeniy Gagarin <eeiaao@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

... somewhat prospective fix (I do not have the new iOS yet), so far build
never failed with my current SDK.

Fixes: QTBUG-76847
Change-Id: Iab75c3cd47144cd83b679b1dbf82339e29c07bd1
Reviewed-by: André Klitzing <aklitzing@gmail.com>
Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>

intended to distinguish an arbitrary disconnection
from disconnection due to insufficient authorization/encryption

Change-Id: Ifcf73d0444fe6fd3a8d5d90155f3db572d6e23d1
Reviewed-by: Evgeniy Gagarin <eeiaao@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

Some code can be re-used from the shared public implementation.
*_osx_p.h is not needed either.

Task-number: QTBUG-75348
Change-Id: If373b74edebe9a9db90e820016cf779a1726baed
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

Binary compatibility files added.

Change-Id: I0e4d8f361769e9a7484fa0b61a70b63d0b5f86e1
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

Change-Id: Ia7d6c7678e68e0ea5943d06fdfbb5a150a87c149

Change-Id: Ibe7380268ccde015045aee61ba23b7569687d46d

Change-Id: I13eb1c8ad1e507e0dc2e70404fcf383dc2bacdd9

 Conflicts:
	.qmake.conf

Change-Id: Idffd7323261ff89c9d7d69a33b88696c5e656015

Change-Id: I38bcbad1bc8d0f03ba0ee3aa09f8c3e867dd6bca

Java-style iterators are scheduled for deprecation, or at the very
least banned from use in Qt code.

Change-Id: If50aade7e5a57f247ec8c0e77103dfd2d2160c3c
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
 

Change-Id: Iad2cfc593f6a9d3b554a2d4f7c16d6173071f7c8

Change-Id: I5745baded59252fefc1ee56cf9a3b662e310ba58

We can run into problems if the list of low energy services is changed
from threads other than the main thread. Make it possible to log this
information in order to debug these problems more easily.

Task-number: QTBUG-75907
Change-Id: Icda8dff45b8c1a72291ade0b1d6f734ab485a241
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
 
 

As callbacks do not necessarily happen on Qt's main thread, it is
possible that we access the service list while it is being changed if we
access it from the callback directly. Doing this can cause application
crashes. Thus we hand back the information about a changed characteristic
to the main thread via signal/slot and handle it from the main thread.

With QLowEnergyControllerPrivateWinRTNew having the Q_OBJECT macro, we
can no longer use forward declares for the GATT classes as moc chokes on
these. Thus an include is used.

Fixes: QTBUG-75907
Change-Id: I063794eecf904921ff55fab76a5bdde3a9aebf44
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
 

Change-Id: I71eafba9e7ff47dbfd89e3a650b83b55d1196693
Reviewed-by: André de la Rocha <andre.rocha@qt.io>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
 
 

It was not taking care of the CoreBluetooth's inability to work with
addresses. Otherwise, the same code path as Android/WinRT must
be used (two connections are possible).

Fixes: QTBUG-76203
Change-Id: I523130b916f7e8163f2a4a23617a0076216add80
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
 

This change sets the Qt::AA_EnableHighDpiScaling application attribute.
It also uses nullptr to initialize pointers and adds a trivial
optimization to the low energy scanner example.

Change-Id: Ia923573ad78108a2a6a72be4c0948ea97a7ec094
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>