I tested it with Qt 5.11.0, but more deficiency detected.
The General Attribute also undetected and characteristic write is not working :(

@NicoFrom13 Hi, Were you able to use this work in progress qtconnectivity? Is it properly working ?

Awesome man.

That show me that sometimes ask the question is more usefull than searching for hours....

I didn't know that i could not use Windows SDK with MinGW i understand now. windows SDK needs to be with Visual compiler ...

Many thanks have a nice Day.

Hi and welcome to devnet,

Glad you found out and thanks for sharing.

Since you have ti working now please mark the thread as solved using the "Topic Tools" button so that other forum uses may know a solution has been found :)

Then I'd recommend asking this on the interest mailing list. You'll find there the QtBluetooth module maintainers/developers.

Hi,

There might just be not much people on this forum that use the QtBluetooth module.

In that case, there's always the interest mailing list where you can find Qt's developers/maintainers.

A bit of a late response, but...

Assuming the GATT server on the other end has a characteristic that allows for Indicate, then the only thing that needs to change is the value that you write to the descriptor. Set Bit 1 of the CCC to enable indicates by writing "0200" instead of "0100" (the descriptor is little-endian according to the BLE documentation for the Client Characteristic Configuration descriptor).

As far as I know, indications are delivered with the characteristicChanged signal just like notifications.

I know this question is old, but it seems noone is answering BLE related questions here. (I've just posted such a question myself, and fear noone will anwer it either).

I developed an app based on the same example, and it worked fine under both android 4.3.2, 5.1.2, and 6.0. However, the customer came with an android 5.01, and sure enough, the app did not work as expected. It seemed to "hang" and tried to connect to two devices at the same time, etc. We did not investigate it further. This was with Qt 5.6, so the issue is not resolved, and may never be, since with newer versions of Android it is working fine.

Hi,

There's a WIP branch in the qtbluetooth module for Windows, you can check the state there.

@kuzulis Thanks!

@pbljung said in BLE demos fail on Android:

errorReceived

these errors can happen
see my comments on top of

void MyBluetoothDeviceInfo::onControllerError(QLowEnergyController::Error error)

in https://github.com/ekke/ekkesBTLEexample/blob/master/cpp/bt/mybluetoothdeviceinfo.cpp

not only 133 (reported as unhandled error)
also 34 and 8 can happen
see also all the discussions at https://bugreports.qt.io/browse/QTBUG-31674
per ex from my comment on 133:

while developing new example app for BT LE and Qt 5.8 using QtQuickControls2 for Android, iOS I also run into GATT ERROR 133 googled and found out that this bug iseems not to be a Qt Bug. some more infos here: https://github.com/NordicSemiconductor/Android-nRF-Toolbox/issues/9 https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/android-5.1.1_r13/stack/include/gatt_api.h of course would be great if Qt could handle error 133 my workaround: if getting a QLowEnergyController::ConnectionError I try to reconnect up to 5 times with a delay of 1000ms In most cases 2nd or 3rd retry will connect without the error.

BTW: find out more on my new BTLE Example APP: http://bit.ly/ekkeBTLEapp

Maybe you should just do bluetooth turn off/on programmaticaly from your app, before using of an BLE.

A BTLE port towards WinRT is currently going on and we hope to have it supported with Qt 5.8.

Please note that this does not include classic / desktop Windows, as the APIset is not available for this platform.

@csanders Bump this. I've got the same issue. Anyone at Qt able to shed some light on why it's so difficult to perform these features on iOS?

I'm assuming it's something to do with Apple's MFi?

Thx, i will give it a try

Thank you for answer, I'll look forwad this version !