Bluetooth / BLE failing with Shearwater Petrel 2 on mobile and desktop

[Anton Lundin]

On 23 August, 2017 - Rick Walsh wrote:

> Hi,
> 
...

> Downloading to my desktop (v4.6.4-737-g5de49401c89c, built with Qt5.7.1 on
> Fedora 26) also fails now.  From the command line:
> 
> build with Qt Version 5.7.1, runtime from Qt Version 5.7.1
> qt.bluetooth.bluez: Bluez 5 detected.
> qt.bluetooth.bluez: Creating QtBluezDiscoveryManager
> qt.bluetooth.bluez: Discovered:  "00:13:43:0E:6B:D0" "Petrel" Num UUIDs 3
> total device 0 cached RSSI 0 Class 0
> qt.bluetooth.bluez: Updating RSSI for "00:13:43:0E:6B:D0" QVariant(short,
> -59)
> qt.bluetooth.bluez: void QBluetoothDeviceDiscoveryAgentPrivate::stop()
> 
> INFO: FTDI disabled
> qt.bluetooth.bluez: No settings found for peer device.
> qt.bluetooth.bluez: HCI event triggered, type: e
> qt.bluetooth.bluez: HCI event triggered, type: e
> [12.217318] ERROR: Failed to open the serial port. [in
> ../../src/shearwater_common.c:46 (shearwater_common_open)]
> INFO: dc_deveice_open error value of -6
> 
> >From the libdivecomputer log:
> INFO: Open: name=LE:00:13:43:0E:6B:D0
> ERROR: Failed to open the serial port. [in ../../src/shearwater_common.c:46
> (shearwater_common_open)]
> 
> Does anyone have any clue how to fix this?

I don't know if 5.7.1 is modern enough for BT LE stuff on bluez. There's
a "// HACK ALERT! Qt 5.9 needs this for proper Bluez operation" and such
which points one towards a modern Qt.

Test with a newer Qt. Newer is better? What could possibly go wrong?


//Anton


-- 
Anton Lundin	+46702-161604