| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
This global operator was added to QBluetoothDeviceInfo
and QLowEnergyService flags.
Change-Id: Ic841cf8c08a2289a9c112dc6283c8891dcc8750e
Reviewed-by: Konstantin Ritt <ritt.ks@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
There is no need for this class anymore as QBluetoothServiceInfo
covers the same information.
Change-Id: I411a8abb68b34a3a4893a67ee9fac096f44bbd62
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
|
|
|
| |
This change incorporates the change from QLECharacteristicInfo to
QLECharacteristic.
Change-Id: I0fc6d31b60975e3b0cccc7666df9c0555350f40f
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
|
|
|
|
|
|
|
|
|
|
| |
- Rename test due to class renaming
- Test all class properties
- Fix QLowEnergyDescriptor::uuid() when using invalid descriptor
- Fixup dead code in QLowEnergyController unit test
Change-Id: I5ffed5b67db786e6c2d9752ca51d2ede51e3f176
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Bluez implementation is the only working implementation for BTLE.
However the current approach of using gatttool via QProcess is not
viable going forward. The tool output is not standardized, the Bluez
developers don't recommend it for anything but debugging and some
Linux distros don't even ship it. Since Bluez does not have any high
level API for BTLE GATT we have to use L2CP sockets to communicate
with the GATT server of the peer device.
The current QLowEnergyController API needs a lot of API changes
going forward as some elements cause problems in the long term.
In summary we need a new internal implementation and a new API for
QLowEnergyController. It is far too much effort to change both elements
at the same time. Hence QLowEnergyControllerNew was added with first
simple API elements. Ultimately it should replace the existing class.
For now the old API stays as is for reference purposes. All other
BTLE classes work just fine for now.
Last but not least a unit test was added. The test assumes the existence
of the TI Sensor tag and verifies all its known characteristics
and descriptors. Ultimately it will help to verify the proper
detection of all details. Right now the test detects all services
and characteristics but not all descriptors.
Change-Id: I6ff1a16da1604be57f5564ae99919ffe7187d02e
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
| |
It seems they were added but never enabled. Due to recent API changes
they didn't even compile.
Change-Id: Ia2d8f6c87f5f02728b1e6451e828ff88bb4527d0
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-22017
Change-Id: I3e5613153d2496567f7afd87c8a0a44c1067a4e7
Reviewed-by: Nedim Hadzic <nedimhadzija@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
| |
Change-Id: I4e20a50549f69367652bd6881a3c541aa283c128
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-31738
Change-Id: I153c3ea4b03edc0e699596a30f395bfe5cab9d16
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't require CONFIG+=nfc to build QtNfc lib.
This prevents proper test execution and there is no API commitment until
the API is offcially released anyway.
Excludes three auto tests from -developer-build builds
as they require Q_AUTOTEST_EXPORT.
Fixes compile errors associated to namespace'd builds of Qt.
Revert "Remove not needed symbol 'qHash(const QNdefRecord&)'"
The symbol is needed during compilation by Windows.
This reverts commit 39901af48f40f0672731a1f62dc003c4b37d1fec.
Change-Id: I61c644bbfc4906729e6d2b9deb741989030c8624
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
|
|
|
|
|
| |
Change-Id: I810dc7b5863c1674390a7e471845f1779cbba98c
Reviewed-by: Tasuku Suzuki <stasuku@gmail.com>
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Includes the following changes:
* Conditionally enables building of the NFC module when qmake is
run with CONFIG+=nfc.
* Correctly build within the QtNfc namespace.
* Fix compile errors in examples, enable building of NFC examples.
* Fix compile errors in tests, enable building of NFC tests.
Mark the some NFC tests as insignificant as they currently crash.
Notably does not enable NFC documentation generation.
Task-number: QTBUG-22015
Change-Id: I9ff170c45848c8f0215e9427797922f840c2f015
Reviewed-by: Alex <ablasche@gmail.com>
|
|
|
|
|
| |
Change-Id: I485e3316cb7b0a84513511e5b834b33a19e341a8
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
|
|
|
|
|
| |
Change-Id: I47e9673790c6ec264f3985fefdb35dfbfc2fd482
Reviewed-by: Andrew Stanley-Jones <andrew.stanley-jones@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tst_qbluetoothservicediscoveryagent crashes when being tested, this
would be an acceptable, however it crashes and overruns the 10 minute
timeout for tests. This adds a significant percentage to both the
qtconnectivity and qt5 integration. It is being disabled for this
reason.
Task-number: QTBUG-22017
Change-Id: I34c4b72a62c3e54443df6270261e22371645342e
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently there is no way of verifying the QtNFC API. This decision will
be revisited by future Qt releases. Furthermore there will be no
commitment that the re-enabled QtNFC API will be source or binary
compatible to the version disabled by this commit.
Change-Id: I9aea986189d48b5c2368ce6b2c7ff20e2c94f2f8
Reviewed-by: Lars Knoll <lars.knoll@nokia.com>
Reviewed-by: Michael Zanetti <michael.zanetti@nokia.com>
Reviewed-by: Oliver Woltermann <oliver.woltermann@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enabled compilation of all autotests which are able to compile.
Enabled enforcing the results of all autotests which pass.
Raised bugs for autotests which don't fall into the above two
categories.
Task-number: QTBUG-22015
Task-number: QTBUG-22016
Task-number: QTBUG-22017
Change-Id: I860a8f6e44dc6ab563ecc3f7d178f778fefa9d64
Reviewed-by: Alex <alex.blasche@nokia.com>
|
|
Change-Id: Ic2be21fd11e2fdb96185fe9269cebbe08b6de87a
Reviewed-on: http://codereview.qt-project.org/4783
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Alex <alex.blasche@nokia.com>
|