> On Apr 25, 2018, at 1:34 PM, Dirk Hohndel <d...@hohndel.org> wrote: >> or similar. But it _would_ be good to test that this actually makes >> Petrel 2 work with rfcomm. Because it's certainly possible that there >> is something else wrong with rfcomm. > > Right now I'm testing. > > (1) BT-only Petrel and Android: works > - but if you cancel on the Petrel (which makes it shut down its BT > stack) then Subsurface-mobile gets confused. It keeps sitting in the > download screen, Cancel doesn't work, and I can't get it to show me > the dives that it has downloaded so far. > (2) dual stack Petrel 2 and Android: > - RF Connect claims this is an LE only device > - whatever I try, it refuses to pair / connect / bond > I know that this Petrel 2 has connected to this Android phone before, > so this is yet another of these "what the heck is going on" situations. > Next I'll remove the battery and reboot the phone, but I'm running out > of ideas how to make this work.
And after rebooting everything I finally got it connected. Subsurface sees it both as LE and classic device. I tried downloading via both protocols and in both cases got "Dive computer transport not supported". So we must be doing something wrong there. I'll add more debugging output to see what I can figure out. /D _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
