The specification says: "Only the significant part of the Advertising
Data is transmitted in the advertising packets". This seems to refer to
the data that is actually sent by the hardware and not to the data used
in the HCI command, as our original implementation assumed. At least
there seem to be controllers who won't accept such "short" packets.

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

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

When given the choice, devices will try to establish the GATT connection
over BR/EDR, which we don't offer. It also makes little sense,
considering we advertise over an LE mechanism only.
This patch makes connections from e.g. Android and iPhone work.

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

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

Task-number: QTBUG-51152
Change-Id: I5e4eee324f0008291be734db7a9d984071ca57c9
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

It has obviously never been compiled with Qt 5. The code includes
headers that have long been removed, uses classes  that don't exist at
all and so on. There is no trivial fix.

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

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

Task-number: QTBUG-41175
Change-Id: I62d74236faf9161681306d952e409e23e0cea24d
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

Conflicts:
	.qmake.conf
	src/bluetooth/qlowenergycontroller_bluez.cpp

Change-Id: I00f45a2a22a045e7836f2caeb76cc5599ced6279

Change-Id: Iabf0939a5f23c5da85de3a73545cd8abdc9a3e65

Change-Id: I4d93ed117fab0047a9d6c90bb3eaa3755c0fa523
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>

The AddressInfo::type member was not properly initialised.

Change-Id: I79c8e1d00d4cb03e3d073a23bb4dbf6b9d510b7c
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>

The build system generates wrapper scripts for direct host tool calls.
This scripts should not be tracked by git.

Change-Id: I9b2c9521c2c12e38f32ae69621d72e18eb33945b
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>
Reviewed-by: Timur Pocheptsov <timur.pocheptsov@theqtcompany.com>

Fixes a few qdoc warnings and improves the available content.

Change-Id: I286cfdeb85d3be2d100e00150efedf7645096f69
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>

Adding the new list elements is all well and nice, but we have to clear
the existing ones first.

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

These files were forgotten in commit c516f615

.

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

lecmacverifier.cpp:99:6: warning: unused parameter ‘message’ [-Wunused-parameter]
 bool LeCmacVerifier::verify(const QByteArray &message, const quint128 &csrk,
                                               ^
lecmacverifier.cpp:99:6: warning: unused parameter ‘csrk’ [-Wunused-parameter]
lecmacverifier.cpp:99:6: warning: unused parameter ‘expectedMac’ [-Wunused-parameter]

Change-Id: I3ae882ebbc967d6694151e90d7463c88a05a8529
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>

Change-Id: Ie993ef22029b1d05f39e4edc8f859841790ca6a6

Change-Id: Iadd9905f4129ede5f0c06b1e1a88a8f932c37c70
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>

Change-Id: I7d4546b31b966a0ac2ac82379a55eefc0f966b19
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>

- This is how we get at the signature resolving key:
    1) On connection from a client, we read the key from the
       respective BlueZ settings file (BlueZ 5 only, as I did
       not manage to find out where BlueZ 4 keeps this information).
    2) Also monitor the HCI traffic for key updates (due to re-pairing).
- While there is an autotest for the actual hashing procedure, the
  overall feature cannot be easily tested for various reasons (there is
  no signed write support in our client API, for one). However, to help
  with manual testing, the server part of our autotest now exposes a
  characteristic that supports signed writes.
- This feature requires a Linux kernel >= 3.7.

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

Change-Id: I25358eae40c07d8e5ba1224b3508c5fee95d3a85

While discovering descriptors, when handles are not numbered
sequentially, the discovery stopped as soon as "no attribute in given
range found" error is received. However, there could be more
characteristics pending. As a result, descriptors for those
characteristics where never discovered.

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

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

Source branch is gerrit/neard.

Change-Id: Ifbefad5ec236964740b93e2ef5c0213997adde44

Change-Id: I1422ab23ef1abd812eb5523105cbadc8ef1aa015
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>

Change-Id: I2c799dbac99c66d5e87fd92efc215e121064cfde
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>

Change-Id: If9cf6718cbd619dd7ce38db2da274fe9d0a41fb7

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

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

We now take the following rules from the specification into account:
    - Signed writes are only possible if the two devices are bonded.
    - Signed writes are not allowed if the link is encrypted.
    - If the link is encrypted, a normal (unsigned) write command can be
      used to write an attribute even if it is specified that a signed
      write is required. That is because the encryption provides the
      same level of trust as the signature.

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

Otherwise, a malicious device could crash our application.

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

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

The value we compare against can be smaller than zero.

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

From Qt 5.7 -> LGPL v2.1 isn't an option anymore, see
http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/


Updated license headers to use new LGPL header instead of LGPL21 one
(in those files which will be under LGPL v3)

Change-Id: I856c13e2a6d4d12c46e1286b0ca1c092ee4608f8
Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>

From Qt 5.7 -> tools & applications are lisenced under GPL v3 with some
exceptions, see
http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/


Updated license headers to use new GPL-EXCEPT header instead of LGPL21 one
(in those files which will be under GPL 3 with exceptions)

Change-Id: I37338c968d8cb5a056cd42e1130cfa077b12d164
Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>

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

Implemented for BlueZ only.

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

Change-Id: Ib5a9f4e5c0eef85a1acd93454d842bbb0d615751
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>

Change-Id: Ic1f3ca5075174addfbc6d76f31d9b89d2c654d19
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>