@SpaceToon said in Dummy backend running. Qt Bluetooth module is non-functional (Bluetooth Low Energy): So is it possible with the MSVC Compiler? No. You will need to build your code for Linux. It is better to do this on a Linux machine as cross compiling from Windows to Linux will be a lot of work. You can have a virtual machine with Linux to build for Linux.

In my opinion too. I'll try to open an issue

@raven-worx Yes, your are right that it is a little unclear in the term that I had used, I think the term that actually used for BLE pairing is PASSKEY rather than PIN-CODE, but essentially the question stays the same. I have updated original question accordingly. Sorry for not answering on that for too long, but at the end of the day I have finished with using Bluez-Qt library. I had to update it with Low Energy functionality by myself, but it was rather easier for me since I am familiar with Bluez DBus Api. So, AFAIK, the Qt Bluetooth module does not provide any functionality similar to what Bluez's agent provides, i.e. it is not possible to perform general pairing/bonding procedure with different IO (Input-Output) capabilities. Please correct me, if I am wrong.

@J.Hilk Thanks for your answer. But I want to ask how can I know I have to choose one over the another? After running the application "Bluetooth File Transfer" I faced the following error: Thanks in advance!

@elsa Check the kits and see if any red marks.

@HansVL nope, thats conform with my 10.1 experience

You should also use the correct command line prompt for building especially if you start with the one provided by Visual Studio.

@eshirshov Опытным путём выяснилось: соединения отфильтровывались: static const QLatin1String serviceUuid("e8e10f95-1a70-4b27-9ccf-02010264e9c8"); m_discoveryAgent->setUuidFilter(uuid); патч: //m_discoveryAgent->setUuidFilter(uuid);

You're welcome ! I'm pretty sure not all these packages are necessary but at least you have it working now :)

Thank you for your answer. I didn't think this functionnality isn't supported by windows. @SGaist I find indeed your previous answer. I will look this

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

@raven-worx no, sorry, as said in the last post it doens't listen for incoming pairing request. Is the application which has to issue a pairing request! It's quite different. Of course the final result is pretty the same, but I didn't understand how it works from the documentation.

Hi and welcome to devnet, That's a question you might want to bring to the interest mailing list. You'll find there the QtConnectivity module's developers/maintainers. This forum is more user oriented.

Hi, That's a bug that should have been fixed for the next release.

@SGaist Ah right - "configure" is ambiguous due to the two step configuration, once by the configure script for qtbase and once by the qmake for the other modules. This is not so obviously that the summary of the configure script does not warn about disabled features in submodules due to missing dependencies.

Hi, It depends, the 5.7 branch will contain the current work for the next 5.7 release so if you need something that's not in 5.7.0 you should follow 5.7. Otherwise 5.7.0. Note that 5.7.0 is almost out.

@SGaist Hey, thank you. I will try it there.

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

Hi all again, I made one more test and I found that in case of active polling of QLowEnergyCharacteristic.value() I can see (probably) all data which were sent from remote side. From all these tests it seems to be the characteristicsChanged signal which is not emitted / accepted.

Hi and welcome to devnet, I'd recommend asking this question on the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

You use QBluetoothLocalDevce LocalDevice.is it available？what's the LocalDevice.isValid() return back?

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.

It Looks like this problem appear after I start QBluetoothServiceDiscoveryAgent->start and before The program enter to QBluetoothServiceDiscoveryAgent->serviceDiscovered. It means that this method (java.lang.String java.lang.String.toString()) is call in QBluetoothServiceDiscoveryAgent. I updated SDK and nothing has changed. Should i write this in java, becouse with QBluetoothServiceDiscoveryAgent is something wrong?

Hi, Windows is not yet a supported platform however you can check the wip/winbranch from the qtconnectivity module to try.

Yep It's not supported on Windows. Easiest is to use Ubuntu. You should be able to install it in for example VirtualBox and share the USB device there.

Hi, Not really a Qt question, you should rather check on the IMX/Linux distribution you're using to see what is happening

i think the only things you need to do is open or shutdown bluetooth, find bluetooth devices and connect if needed. all the other things must have been done by the hardware vendor

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