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

[Rick Walsh]

Hi,

After nearly three months of terrible sea conditions near home, I managed
some data collection a couple of days ago.  On trying to download to my
phone (Galaxy S7) running Subsurface-mobile 4.6.4.734 (Dirk's build), it
fails.  The log includes:

"13.963: DCDownloadThread started for Petrel 2 on LE:00:13:43:0E:6B:D0"
Starting download from  BT
Starting the thread 0
Creating Android Central/Client support for BTLE
qt_ble_open( 00:13:43:0E:6B:D0 )
Connection updated: error: QLowEnergyController::Error(NoError) oldState:
QLowEnergyController::ControllerState(ConnectingState) newState:
QLowEnergyController::ControllerState(ConnectedState)
connected to the controller for device 00:13:43:0E:6B:D0
  .. discovering services
Service discovery initiated
Found service "{00001800-0000-1000-8000-00805f9b34fb}"
 .. ignoring standard service
Found service "{0000180a-0000-1000-8000-00805f9b34fb}"
 .. ignoring standard service
Found service "{fe25c237-0ece-443c-b0aa-e02033e7029d}"
 .. created service object QLowEnergyService(0xc025edc0)
Discovery of "{fe25c237-0ece-443c-b0aa-e02033e7029d}" started
Service "fe25c237-0ece-443c-b0aa-e02033e7029d" discovered (start: 9 end: 9
) QLowEnergyServicePrivate(0xc03fd500)
 .. done discovering services
 .. discovering details
 .. enabling notifications
Finishing the thread Dive data import error dives downloaded 0
no new dives downloaded
"14.622: DCDownloadThread finished"

Previously (at some time between late May and July) I had been able to
download from my Petrel 2, but only using regular (non-BLE) Bluetooth.
Since then I updated the firmware to v44 (I think it was v37 before - in
any case before Shearwater released their cloud mobile app).

I'm not sure if the change to being able to download is due to subsurface,
libdivecomputer, or the firmware.  In any case, we should support the
current firmware.

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?

Thanks,

Rick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20170823/5caef338/attachment.html>