Both of these bugs sound annoying and should be fixed. Right now it seems that we have a strange bug that makes us not always do the right thing when figuring out which dives to download. I'd love to understand if it indeed downloaded the exact same dives that were already in the dive log or if there was possibly a change in the dives in the divelog compared to what's on the dive computer (maybe the times were off and you fixed them or something)? The crash is of course harder to analyze because unless you are able to connect to your tablet with adb, it's very hard to figure out exactly WHERE it crashed...
Any pointers you can provide would help us narrow things down. Thanks /D > On Sep 22, 2019, at 1:06 PM, John Smith <[email protected]> wrote: > > Tested using Lenovo Tablet running Oreo. > > Most things seemed to work ok, nothing stood out on display and cloud > connection. > > Tried to download from Shearwater Petrel 2 via Bluetooth. Connection was > Bluetooth classic. Connected to subsurface once paired, but subsurface tried > to download all the dives on the Petrel rather than only the new ones. Also > when downloading, if I pressed the quit/cancel button in the download dialog > whilst still connected to DC, subsurface would crash and need to restart. It > didnt crash if not connected.
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
