Fix usage of API that is marked deprecated.

Change-Id: I82fe0911f6783a709356211b001e1d377f694642
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

ATT_OP_READ_BY_TYPE_REQUEST may return more than one char description
per response packet. Due to a missing offset adjustment we only ever
read the first description. Subsequent description were read by
issuing a new READ_BY_TYPE request. This is very inefficient as
at worst 3 times as many requests had to be send to the device.

Change-Id: I83ca75a42425fe230926411f068112865c249061
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

Change-Id: I8b2c8931b3755306491deff51b57d1476fe87e3a
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

handledata contains a 16bit char handle in the lower bits and
may contains a 16bit descriptor handle in its upper 16 bits.
When doing blob read requests for descriptors the upper 16 bit
may be cut off and the descriptor read turns into a characteristic
read. In turn this switches the internal
state of the service discovery state machine causing an endless loop
between descriptor and characteristic reads.

Change-Id: Ia66f230e8fb018da51c3ce32db936d02a0b195b8
Task-number: QTBUG-47028
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

The enum value is 32 bit. the field we are reading is 8bit. Ensure that
the higher bits are always set to 0.

Change-Id: I317a877e23645c2785fd75e38494103f2272d2cd
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

Change-Id: Iedd83bb8f9d31268fb5a17879feaaf97a82f86cc
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

This patch permits Android clients to choose the security level
before connecting to the server.

This may also used by some older devices (Android 4.1 or lower)
to connect if they don't support the so far predetermined secure
way of connecting via rfcomm.

Task-number: QTBUG-46377
Change-Id: I3f72f183e7ead16bec57a0ce83e9a96324675312
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

This permits Bluez clients to determine the security level before
connecting to the server.

Note that the server may change the sec level at runtime without the
user noticing. If the user wants to detect such cases socketDescriptor()
in compination with getsockopt() should be used.

Task-number: QTBUG-46377
Change-Id: I3bc4fcd62dc44d9e2e14e5a6e7416e3bb8e0d50b
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

1.) Remove the usage SOL_RFCOMM & SOL_L2CAP. They were replaced
by SOL_BLUEOOTH. The same applies to RFCOMM_LM & L2CAP_LM which were
replaced by BT_SECURITY.

2.) Fix securityFlags() when socket was closed already. It always
triggered undesirable error messages as the code assumed a valid socket
fd.

3.) Fix setSecurityFlags() when calling after the server socket was
closed. The docs state that this function shall be called before
listen is called. However after the socket was closed for the first time
the security level could not be set anymore because the server socket is
invalid until the next call to listen(). To solve this problem the
initial security level is stored and applied during listen().

These changes imply a slightly different runtime behavior of securityFlags().
While the socket is closed it returns the stored value and during
runtime the actual runtime level is returned.

Change-Id: I720e6ac94a569397c4fec0058a1d388a1f35ecae
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

This permits the API user to determine the security parameters for the
connect attempt to the remote SPP service.

Task-number: QTBUG-46377
Change-Id: I1ed5ea0f5a32aa08dcedc46a34b0377654e420b2
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

Remove Q_ENUMS in favor of the new Q_ENUM macro which provides
registration as meta enum and a debug stream operator.

Register some enums via Q_ENUM to improve debug output
and types auto-registration.

Change-Id: I31c9535a2de7da1783b4ec967612c02a57cb62ff
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

[ChangeLog][QtNfc][Platform Specific Changes] Removed
support for Blackberry 10 from QtNfc.

Change-Id: Ideca878656826de7d04dda96bd213895433a3737
Reviewed-by: Rafael Roquetto <rafael.roquetto@kdab.com>

In 5.5 we don't support it anymore although other parts of the
documentation and the code base still have the details. The complete
removal happens in Qt 5.6.

This change prepares qtconnectivity for the removal of the
"Qt for Blackberry" link in the general Qt docs.

Change-Id: I8d51191caf34e4b4b57b0b072f543447213eeb23
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>

Change-Id: Iea466eb5224c3f53c3c363b09702acc2fc803e70
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

[ChangeLog][QtBluetooth][Platform Specific Changes] Removed
support for Blackberry 10.

Change-Id: I431c4f34bb10aa3668542df7a8b3403b61bf4705
Reviewed-by: Rafael Roquetto <rafael.roquetto@kdab.com>
Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>

Change-Id: Icb2908106e8b869b6682b4945935cd801d67241e
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

The new BTLE aware device discovery crashes due to a wrong internal
activity state. The device discovery emits finished() signal when
the SDP discovery finishes. It does not continue with BTLE scans
oin Android releases 4.1.x or earlier.
The signal emission causes the classes dtor to run.
In turn the dtor calls stop() because the activity flag
still indicates a running device scan which emits error(), which calls
the classes dtor and the entire loop continues until a stack overflow
is caused.

Task-number: QTBUG-46588
Change-Id: If7e4af6773c6063cee11f59e0b0db477fea0c003
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

Change-Id: I7b46391bb7cbd303eac0e85a9782cdd358e80775
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

Change-Id: I6120f7feba0c37b8ca81bf5c3546e4c0a1868d14
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

Change-Id: I6098b32fc0b28cdebd5447f59961102c655418ca
Reviewed-by: Peter Rustler <peter.rustler@basyskom.com>
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

Change-Id: Ife85fc5a3e01752de07e91ba49216363ca5a5789
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

Device address and service name changes never triggered the signal
despite the documentation and Q_PROPERTY definitions requiring it.

Change-Id: I5d3d5f827b3e092bce3c2e7a4ce3cf687b251e6e
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

Change-Id: Ic940a8a61797c05f930b8063b67c1602292bb266
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

Change-Id: Id4ff2740cb89b0c20cd66a823a145855d28c2ec4
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

The actual message was:
> warning: dereferencing type-punned pointer will break strict-aliasing
  rules [-Wstrict-aliasing]

Change-Id: I70f30da77a925e50032c5a82014af2e1aee511fb
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

Change-Id: I5d0302f37199a21d281e0dd20fb785dfb60b84b3
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

Change-Id: Ifcae07ef5e046f45848495f4d6af973cde713fdf
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

QLEController(QBluetoothAddress) ctor is not usable on iOS and OSX.
On those platforms we have to use QLECOntroller(QBluetoothDeviceInfo).

We mark the QBluetoothAddress based ctors of QLEController obsolete
and remove most uses of them. This cleans up some ifdefs throughout
the QtBluetooth code base.

Change-Id: Ibe1e3fa271a29461e39fc3c0eeba7a910a250077
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

Task-number: QTBUG-45435
Change-Id: I3ded6bf88d3980481e386073ce160d5d54520034
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

Android can only handle a defined count of simultaneously connections to bluetooth le
devices. Every Android device have a different defined amount of possible simultaneously connections.
If we do not close the connection and reconnect to the device or another device,
the count of used connections get up. If we exceed the maximum connection count we can not connect
to bluetooth le devices anymore.
The only way to recover is to restart the application to reset the open connection count.

This patch closes the connection after it has been disconnected.

Change-Id: Id96a69ef07eb973216495a0ba8e46fd639338165
Reviewed-by: Frank Meerkoetter <frank.meerkoetter@basyskom.com>
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

In current implementation of processDiscoveredDevices, if we receive the same
device again with different coreConfiguration, the device will be just replaced.
In Android there are 2 ways to scan for bluetooth devices. One is the scan for all
bluetooth devices (including LE) and one for scanning just LE devices.
Currently they are used both, which means we receive dual devices multiple times.

Depending of the arrival in time of the QBluetoothDeviceInfo the coreConfiguration is different.
In the List of discovered devices this lead to devices reported as LE only or classic only
which is wrong.

If the Application calls discoveredDevices() it will get a list with wrong coreConfiguration.

This patch update the coreConfiguration of the QBluetoothDeviceInfo in list.

Change-Id: I312544ca513503c5d6b31a1ca0cfbe530c0be911
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
Reviewed-by: Frank Meerkoetter <frank.meerkoetter@basyskom.com>

Change-Id: I414965f475a1b66aec30098804c71ef07b80a032
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

So far we tried to detect Bluez5. If we couldn't find it the code
automatically assumed Bluez4. That's not always true though as
the Bluez daemon (bluetoothd) may not actually be running.

In such cases we print a warning from now on.

Change-Id: I6bf803ab21cb8906bb786bc0549db8e1bb3a0a3b
Task-number: QTBUG-45750
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

Follow-up commit will fix the headers clean test properly by
adding the missing assignment operator to
QNdefNfcSmartPosterRecord.

This reverts commit 2d4f7fd1

.

Change-Id: I9bbe381a429f695e70770ba7de33ecd704d63a86
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>

Required to pass the headersclean test.

Change-Id: I0b274ee90c4172dde99dc2f8f60525466fb8d35f
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>

Add read descriptor/characteristic support for iOS and OS X.

Change-Id: If7547f3756dc37930052c9cefd243d6063bcab1c
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

Skip check, required for
qtbase/ 6668f5becfb8fcb6d10e42495c6ea5cdba2d15c5.

Change-Id: Ie14c1f6201e60f71ce694323bf209422c7dba779
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

This was caused by the new headersclean enforcing warnings as errors

Change-Id: Idd595fc4cf78411a80ff3dbb46477d5130a04c3e
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

handleFor(Characteristic|Descriptor)() find a handle for a given
char and desc. We should reuse it inside the read notifier for
chars and descs.

In addition, under certain circumstances the read/write queue operation
was finished although the queue was not empty yet. This happened when
the last read operation failed with a certain type of error.
Now we always finish with a call to performNextIO().

Change-Id: Ifdb66c0b03d25ae19db7c49bcbe70eeec2665b6e
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>

- doc fixes

Change-Id: I4a5f413672d30c53be0cfcb022953e8ba3da6a83
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>