Legacy Bluetooth Vs LE regression on Android / Shearwater.

[Long, Martin]

Hmmm. It does appear to be the same ongoing issue rather than a regression.
Using nRF connect I was eventually able to unpair it as BLE and get it to
pair as legacy. It seems like chance as to which will happen first time. I
wonder if there is anything we could do to prompt or assist in making this
a bit easier on the user.

On Tue, 26 Mar 2019, 18:55 Long, Martin, <martin at longhome.co.uk> wrote:

> I've found a thread:
> http://lists.subsurface-divelog.org/pipermail/subsurface/2018-July/032464.html
>
> However in that thread I managed to fix myself eventually. Those steps
> don't seem to be working now. Legacy doesn't show, BLE does, but doesn't
> work.
>
> On Tue, 26 Mar 2019, 00:37 Long, Martin, <martin at longhome.co.uk> wrote:
>
>> Hi,
>>
>> There seems to be another regression in the current Android version. I
>> reported this a while ago and I think it was fixed by either Linus or Dirk.
>> Well... It's back.
>>
>> My Petrel (JJ-CCR, Divecan) is again only showing up as an LE device. It
>> used to show up as both legacy AND LE in the list but LE has never worked
>> for this device (worth noting that LE does work for my single-stack
>> Perdix).
>>
>> It is important that the legacy Bluetooth is shown for these dual stack
>> devices, as that is the only way I can download from my Petrel. I'll have a
>> dig through the archives and see if I can find my original report of this
>> in the morning. For now, a screenshot.
>>
>> Thanks
>>
>> Martin
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20190326/b731aaa4/attachment.html>