Testing v392 with OSTC Sport

[Dirk Hohndel]

On Thu, Jul 13, 2017 at 03:39:30PM +0200, Matthias Heinrichs wrote:
> Am 13.07.2017 um 15:03 schrieb Dirk Hohndel:
> > It tries to associate Bluetooth names (and the correspondong addresses)
> > with known patterns for dive computer names. I'm actually surprised that
> > this didn't end up with an error that it can't determine the address - but
> > maybe the slightly odd BT names of the OSTC devices worked out in our
> > favor here and it was misdetected?
> 
> I'd prefer a small pop-up with a list to choose from (Detected devices).
> Makes this all a bit more robust and future proof. In case /we/ choose the
> rename the newest model different /again/.

Dive computer makers so far have not shown a lot of care when it comes to
naming their devices on BT/BLE - so yes, we'll have to come up with
something better.

> Divemate had the same problems and they now keep a list of all possible BT
> names in their code. I still use one of the earliest OSTC3 BLE prototypes
> personally and it still has it's default name like "BlueMod+SR", for
> example.

Cringe.

Yeah, I get your point. I'll work on that prior to the final
Subsurface-mobile 2.0 release.

/D