summaryrefslogtreecommitdiffstats
path: root/src/bluetooth/qlowenergycharacteristicdata.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Use SPDX license identifiersLucie Gérard2022-06-101-38/+2
| | | | | | | | | | | Replace the current license disclaimer in files by a SPDX-License-Identifier. License files are organized under LICENSES directory. Pick-to: 6.4 Task-number: QTBUG-67283 Change-Id: Ifc22d8ae24532e9a1093ca613ed6590a1992bc39 Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
* Android BT LE Server: Enable NTF if both NTF & IND requestedJuha Vuolle2021-11-231-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The Bluetooth specification does not explicitly dictate the behavior if a characteristic supports both Notifications and Indications, or if a bluetooth client enables both. It turns out that the bluetooth stack implementations vary on how they deal with this somewhat unusual combination. The root cause for this commit is that if a characteristic supports both NTF & IND, a Bluez client developer has no way to tell which one to use; independent of what the Bluez client asks for, the Bluez will send a request for both. In that case the Qt BT LE Android server implementation does not enable either. With Apple client on the other hand, the developer can only ask for a NTF if both NTF & IND are possible. This seems a somewhat sensible strategy and this commit implements similar behavior on the Qt BT LE Android server. In addition the commit prints a warning if both NTF & IND properties are set when creating the characteristics on the Server side. Pick-to: 6.2 Fixes: QTBUG-96743 Change-Id: I3899fdb15b435d63bbcef2c02a1491a93cb3d722 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> Reviewed-by: Andreas Buhr <andreas.buhr@qt.io> Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
* Make comparison operators hidden friends in QtBluetoothAndreas Buhr2021-03-121-16/+23
| | | | | | | | | | This patch changes all comparison operators in QtBluetooth to hidden friends. Thereby, they are symmetric and can only be found through ADL, not polluting the global namespace. Fixes: QTBUG-91553 Change-Id: I4357dd3fee51beb86e68a9c7a01ea6b6c93f135f Reviewed-by: Karsten Heimrich <karsten.heimrich@qt.io>
* Replace foreach with for loop and set QT_NO_FOREACHOliver Wolff2018-08-151-1/+1
| | | | | | | | To avoid unnecessary copies, const is used wherever possible. Change-Id: Ic743716512751cfd24fad5bd37c244b115dd26fe Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
* Bluetooth LE: Fix two list setter functions.Christian Kandeler2016-02-091-0/+1
| | | | | | | | 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>
* Update to new Qt license headersneardAlex Blasche2016-01-261-15/+21
| | | | | Change-Id: I2c799dbac99c66d5e87fd92efc215e121064cfde Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>
* Bluetooth LE: Implement GATT server write support.Christian Kandeler2015-12-151-2/+41
| | | | | | | | | | Write Request, Write Command and Execute Write Request are fully implemented now. Signed Write support is still missing. Notifications and Indications are sent. The server side gets informed via the respective signals when a client writes a characteristic or descriptor. Change-Id: Icba6a0270f6e1c4c3ed2ba61b55c1a5fbb69752b Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
* Bluetooth LE: Implement ATT access permissions.Christian Kandeler2015-12-041-2/+47
| | | | | Change-Id: I456d083d45569ea8d61f0a659f72646d653143d1 Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
* Bluetooth: Add API to set up GATT services.Christian Kandeler2015-11-201-0/+189
This is the next step in implementing LE peripheral support. Change-Id: I5e8cb186d556e7bfb9ae8a5e60e051ff7398b77d Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>