Legacy Bluetooth missing again

[Long, Martin]

Hi Dirk,

Thanks. Yes, I did report it the last time, and I believe it was you who
worked on the fix. At the time I wasn't aware of the CI builds available
through github, and I waited for it to be released on the official Beta
channel through the Play Store.

I think the problem possibly was that I experienced the same problem where
I kept opening up the app after each update to find it still wasn't
working, and made the assumption that the fix hadn't made it into a build
yet. I probably later got it working by deleting the pairing.

The confusing part is that the bug you fixed was one where only BLE address
was showing for dual-stack devices. The current situation seems to exhibit
the same symptoms - the BLE address still shows, while the classic address
does not. For this reason it APPEARS like it is a regression, when in fact
it is not, it is a known integration issue with a work around.

For the record, I have worked on open source projects, and understand that
everything is a "gift" to the community, so thank you to you, Linus, and
everyone else who has contributed (including even myself a little while
back). It can just be very frustrating when software I've come to rely on
stops working.

Martin

On 5 July 2018 at 16:41, Dirk Hohndel <dirk at hohndel.org> wrote:

>
> > On Jul 5, 2018, at 8:29 AM, Long, Martin <martin at longhome.co.uk> wrote:
> >
> > Ah, so maybe it disappeared because I'd paired my petrel with my PC in
> order to test the ppo2 download.
>
> Yes - I can actually reproduce that behavior here. For the Suunto you have
> to explicitly delete a pairing, the Shearwater doesn't offer that.
> Additionally, you can get the Shearwater in a state where it refuses to
> give up its idea of its state. Shearwater themselves recommend removing the
> battery and waiting about 15 seconds for the BT settings to reset.
>
> > Thing is I'd tried unpairing and re-pairing several times, to no avail.
> Anyway it's working now, and the good news is that the ppO2 data also came
> through for my new dives. Excellent work.
>
> I'm glad this is working. I'm puzzled how it would make a difference to
> the ability to pair if you re-install Subsurface... but let's simply
> remember this as "last ditch attempt" when other, saner approaches don't
> work :-)
>
> One request - your email sounded like you had this not working for weeks
> and were rather frustrated. Apparently we (the community) and I (as the
> maintainer) sometimes don't do a good job listening to people who are
> stuck. Please be persistent and tell us when things are broken for you so
> we prioritize the effort to fix them...
>
> Thanks for the feedback!
>
> /D
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20180706/1142cb87/attachment-0001.html>