> On Apr 12, 2015, at 7:58 AM, Anton Lundin <[email protected]> wrote: > > On 12 April, 2015 - Rick Walsh wrote: > > My tips are: > > Use rfcomm connect instead of bind. Watch the command and make sure the > rfcomm channel have connected before starting any communication over it. > > Make sure you gave rfcomm -i [hciX|bdaddr] the right device as your > "source". Eg. by default it uses hci0 on my machine, the built in > problematic device.
Also make sure that you don’t have another program grab the port before Subsurface tries to open it. ModemManager is notorious for doing that… /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
