>Do you have any chance to test the latest RC candidate? There were lots of bug >fixes for QtBluetooth (over 30 just for Bluez 4): > >https://qt.gitorious.org/qt/qtconnectivity/source/9b11226f3d23dfb4c6b8457f2a839584666cda6a:dist/changes-5.3.0 > >Most of them would have gone into Qt 5.2.2 if it would have been released. As >it stands now they have moved into 5.3. > >Another reason why I'd like to ask you to use the 5.3 code line is because it >has tracing capabilities. It can tell much more details on >what might be >happening. I would like to ask you to add the trace activation code to your >main() function as can be seen in > >https://qt.gitorious.org/qt/qtconnectivity/source/9b11226f3d23dfb4c6b8457f2a839584666cda6a:tests/bttestui/main.cpp > >The actual line is: > QLoggingCategory::setFilterRules(QStringLiteral("qt.bluetooth* = true")); > >Then you could send me the trace output please? Alternatively you may just use >the bttestui app to which the above link points to.
I will try to do the tests as soon as I get 5.3 beta installed and working. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
