Bluetooth nonfunctional

[Linus Torvalds]

On Sun, May 13, 2018 at 12:00 PM Willem Ferguson <

Thank yo so much for your time, Linus. Nope, same error. Error bar at
bottom of Subsurface screen "Unsupported operation".

Yeah, that's just the "none of the protocols we tried worked" error case.

Failed to connect to device 00:13:43:5B:8F:BE .
Device state QBluetoothSocket::UnconnectedState .
Error: QBluetoothSocket::UnknownSocketError

So it's simply that Qt doesn't successfully connect to the device at all,
and we never even get to the point where we can talk to it.

Why _that_ happens, I have absolutely no idea. There is simply not a lot of
information to go on. It's like the device isn't paired.

We simply do

serial_port->socket->connectToService(remoteDeviceAddress, ..

and then wait for the socket to go into ConnectedState. Which it obviously
doesn't do. IOW, this isn't a subsurface issue, it's something else.

Now, you *could* try the attached hacky patch, that tries to avoid using Qt
for this, and uses the libdivecomputer rfcomm functionality instead.

This patch requires that you have libbluetooth installed
(bluez-libs-devel), and honestly, I don't think that the Qt rfcomm code is
the problem. But I guess it's easy enough to test this patch.

Other than this patch, I would suggest just trying to unpair and then
re-pair the device. I assume you've done that a number of times already and
it didn't make any difference.

I guess at some point I should just get one of those stupid rfcomm devices.

Linus

[Dirk Hohndel]

Post by Linus Torvalds
On Sun, May 13, 2018 at 12:00 PM Willem Ferguson <

Thank yo so much for your time, Linus. Nope, same error. Error bar at
bottom of Subsurface screen "Unsupported operation".

Yeah, that's just the "none of the protocols we tried worked" error case.

Failed to connect to device 00:13:43:5B:8F:BE .
Device state QBluetoothSocket::UnconnectedState .
Error: QBluetoothSocket::UnknownSocketError

So it's simply that Qt doesn't successfully connect to the device at all,
and we never even get to the point where we can talk to it.
Why _that_ happens, I have absolutely no idea. There is simply not a lot of
information to go on. It's like the device isn't paired.

In my experience with the Petrel 2, once it decides to be stupid, it stays
stupid. Remove the battery for at least 15 minutes. Forget the pairing on
your computer. Insert battery, fix clock, pair again with your computer.
Try again.

At one point I had to do that three times until it decided to play with my
Mac again. There is something SERIOUSLY broken - and my current
guess is that it's in the BT/BLE stack on the Shearwater Petrel 2

/D

[Benjamin]

When mine starts to play stupid, I find that it sometimes helps to 1.
forget the pairing 2. reset the pc 3. pair with the petrel and then to try
and download again. Sometimes it almost seems that the bluetooth on the pc
side is the bit which is causing the problems.

Just my 2 cents.

Benjamin

Post by Dirk Hohndel

On May 13, 2018, at 12:36 PM, Linus Torvalds <
On Sun, May 13, 2018 at 12:00 PM Willem Ferguson <

Thank yo so much for your time, Linus. Nope, same error. Error bar at
bottom of Subsurface screen "Unsupported operation".

Yeah, that's just the "none of the protocols we tried worked" error case.

Failed to connect to device 00:13:43:5B:8F:BE .
Device state QBluetoothSocket::UnconnectedState .
Error: QBluetoothSocket::UnknownSocketError

So it's simply that Qt doesn't successfully connect to the device at all,
and we never even get to the point where we can talk to it.
Why _that_ happens, I have absolutely no idea. There is simply not a lot

of

information to go on. It's like the device isn't paired.

In my experience with the Petrel 2, once it decides to be stupid, it stays
stupid. Remove the battery for at least 15 minutes. Forget the pairing on
your computer. Insert battery, fix clock, pair again with your computer.
Try again.
At one point I had to do that three times until it decided to play with my
Mac again. There is something SERIOUSLY broken - and my current
guess is that it's in the BT/BLE stack on the Shearwater Petrel 2
/D
_______________________________________________
subsurface mailing list
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

[Willem Ferguson]

Post by Dirk Hohndel
In my experience with the Petrel 2, once it decides to be stupid, it stays
stupid. Remove the battery for at least 15 minutes. Forget the pairing on
your computer. Insert battery, fix clock, pair again with your computer.
Try again.
At one point I had to do that three times until it decided to play with my
Mac again. There is something SERIOUSLY broken - and my current
guess is that it's in the BT/BLE stack on the Shearwater Petrel 2
/D

Your diagnosis was accurate. When I tried downloading using the
Shearwater software on Win it also did not succeed. After removing the
battery download was successful in Subsurface. So it looks like the
problem is indeed in the Shearwater, not in the download software.

Thank you so much for your time.

Kind regards,

willem