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

[Rick Walsh]

On 23 August 2017 at 20:03, Miika Turkia  wrote:

> On Wed, Aug 23, 2017 at 12:55 PM, Rick Walsh  wrote:
> >
> >
> > On 23 Aug. 2017 19:21, "Anton Lundin"  wrote:
> >
> > 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.
> >
> >> 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?
> >
> > I tried that today. Downloaded qt5.9.1, and used ccmake in
> subsurface/build
> > to point to the right qt directories. But the build fails because it
> doesn't
> > have webkit. Is there some trick to make it work?
> >
> > I downloaded dives succesfully on Windows 7 with the latest binary.
>
> ccmake one more time, and switch to webengine
>

Thanks, I'll try that when I get a chance - hopefully some time in the
coming days.  I really hope I don't have to compile Qt myself.

Any idea why the mobile download might failing using Dirk's apk, and how
this could be debugged?

I'm using my Windows 7 laptop now.  I don't have my dive computer with me,
but going to the download dialog the BT address doesn't have the le:
prefix, so it appears that the successful download was using ordinary BT.

Cheers,

Rick
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

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

[Dirk Hohndel]

> On Aug 23, 2017, at 2:21 AM, Anton Lundin  wrote:
>>> 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.

I think BLE will not work with any of the dive computers we have tried so far
unless you have at least Qt 5.9 - I have lost track (sorry), what the matrix is
on Linux, I think for the EON Steel you still need one patch on top of 5.9.1,
the G2 and the Shearwaters should work with 5.9.1.

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

A lot

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

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

[Lubomir I. Ivanov]

On 23 August 2017 at 13:40, Salvador Cuñat  wrote:
> Hi
>
> 2017-08-23 11:55 GMT+02:00 Rick Walsh :
>>
>>
>>
>> On 23 Aug. 2017 19:21, "Anton Lundin"  wrote:
>>
>> 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.
>>
>> > 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?
>>
>>
>
> On Debian unstable, moving to Qt 5.9 fails (since a week or two) because
> distro has moved to openssl 1.1 (as Linus pointed out some time ago). Didn't
> try on updated fedora for a while, but it's quite fast adding security
> updates.
>

ouch,

they would need to manually patch their Qt 5.9 build to support
openssl 1.1 or users would have to wait for the next Qt release (and
Debian needs to include that too) to be able to use Qt with openssl
1.1.

like some have pointed out - openssl 1.1 isn't really more secure than
the 1.0x series. on the other hand this move might break Qt apps for
thousands of people.
:facepalm:

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

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

[Salvador Cuñat]

Hi

2017-08-23 11:55 GMT+02:00 Rick Walsh :

>
>
> On 23 Aug. 2017 19:21, "Anton Lundin"  wrote:
>
> 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.
>
> > 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?
>
>
>
On Debian unstable, moving to Qt 5.9 fails (since a week or two) because
distro has moved to openssl 1.1 (as Linus pointed out some time ago).
Didn't try on updated fedora for a while, but it's quite fast adding
security updates.

Regards

Salva.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

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

[Miika Turkia]

On Wed, Aug 23, 2017 at 12:55 PM, Rick Walsh  wrote:
>
>
> On 23 Aug. 2017 19:21, "Anton Lundin"  wrote:
>
> 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.
>
>> 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?
>
> I tried that today. Downloaded qt5.9.1, and used ccmake in subsurface/build
> to point to the right qt directories. But the build fails because it doesn't
> have webkit. Is there some trick to make it work?
>
> I downloaded dives succesfully on Windows 7 with the latest binary.

ccmake one more time, and switch to webengine

miika
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

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

[Rick Walsh]

On 23 Aug. 2017 19:21, "Anton Lundin"  wrote:

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.

> 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?

I tried that today. Downloaded qt5.9.1, and used ccmake in subsurface/build
to point to the right qt directories. But the build fails because it
doesn't have webkit. Is there some trick to make it work?

I downloaded dives succesfully on Windows 7 with the latest binary.

Cheers,
Rick
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: 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
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

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 "{1800--1000-8000-00805f9b34fb}"
 .. ignoring standard service
Found service "{180a--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
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface