On Mon, Jun 05, 2017 at 05:00:27PM +0200, Joakim Bygdell wrote: > > > > > > I have a first generation OSCT3 with BT and it presents it self as "BM+SR > > > 3B82" > > > > We learned from HW that this should never be the case with production > > OSTC. Hmm. Not sure what to do here... that's a generic ID for the chip > > they used - not sure if it's smart to assume that's an OSTC. But maybe > > that's what we should do? Or we need another UI to pick the device... > > The "3B82" are the last 4 characters in the device address and as long as > there is only one paired device we should be able to match it.
Yes, that's the default for that chip. So any device with that chip that didn't program a different name will show up with this pattern of BT name... > > > USB download from a OSTC3 works and takes about 2 min, but it does not > > work > > > from a Suunto Vyper. > > > > That's interesting. Which phone / device? Which OS? Rooted? > > > > One+, Cyanogenmod 13 I bet that doesn't enforce SELinux /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
