Cleaned up and rebased "libdivecomputer-NG" branch

Linus Torvalds torvalds at
Wed Apr 25 16:24:25 PDT 2018

On Wed, Apr 25, 2018 at 4:21 PM, Dirk Hohndel <dirk at> wrote:
>> Ok, so it's using the BLE code, it just isn't able to get a service list. Odd.
> Indeed - what's the next step to debug this? My guess is that we should
> somehow dump what we get back?

We do. Normally you'd see that whole song and dance:

  connected to the controller for device F0:73:0A:BA:CD:F9
    .. discovering services
  Sending read_by_group_type request, startHandle: 1 endHandle: ffff 2800
  Received size: 3 data: "035000"
  Server MTU: 80 resulting mtu: 80
  Received size: 14 data: "11060100090000180a000a000118"
  Found uuid: "{00001800-0000-1000-8000-00805f9b34fb}" start handle: 1
end handle: 9
  Found service "{00001800-0000-1000-8000-00805f9b34fb}"

from our normal BLE debug messages.

>> Maybe the same old "Shearwater dive computers have some random memory
>> of what they talked to last, and refuse to talk to anybody else". With
>> some unknown rule for what that memory is..
> Yeah, but Shearwater says it doesn't. There must be something magic that
> we aren't sending to the dive computer. Or something.

It may just have some very limited bluetooth stack, and be very picky,
and there's something randomly going wrong.


More information about the subsurface mailing list