[TEST REQUEST] Windows Bluetooth LE build

Lubomir I. Ivanov neolit123 at gmail.com
Sat Sep 29 15:07:17 PDT 2018

On Sun, 30 Sep 2018 at 01:03, Dirk Hohndel <dirk at hohndel.org> wrote:
> > On Sep 29, 2018, at 2:57 PM, Linus Torvalds <torvalds at linux-foundation.org> wrote:
> >
> > On Sat, Sep 29, 2018 at 2:47 PM Lubomir I. Ivanov <neolit123 at gmail.com> wrote:
> >>
> >> random addresses should not be used on Win32.
> >
> > Afaik, the dive computers that need random addresses will simply not
> > respond to the static ones.
> >
> > It's not a "choice" you can make. It's the other end that says that
> > they need a random address.
> >
> > Now, it's possible that Windows does the selection automatically
> > (that's how it *should* work, and Bluez is being stupid about it), but
> > then it shouldn't matter whether you set the random address bit or
> > not.
> Interestingly enough, the two BLE dive computers I tried with are
> both Shearwaters who AFAIK require random addresses. I don't
> see, however, how that would cause the error pairing.
> The third one (Suunto EON Steel) I couldn't figure out how to even
> pair with Windows 10...
> Still trying to figure out how to get the logging to work...

Dirk notice that Steve is being able to discover the device, but then
fails to connect:

from what i've understood on your end it fails finding the device in
the list of BT(LE) devices nearby, so it fails in an earlier step?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: petrel2ext.jpg
Type: image/jpeg
Size: 251115 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20180930/93023e18/attachment-0001.jpg>

More information about the subsurface mailing list