I should have added that I wiped data for the Subsurface mobile app before retrying the download, and generating the *subsurface.log* and *libdivecomputer.log* files. This was meant to ensure that it attempted to download all dives, rather than just the one from this weekend. The result was still "Info: No new dives downloaded from dive computer".
On Mon, Oct 8, 2018 at 12:01 PM Adric Norris <landstander...@gmail.com> wrote: > Ah, it looks like I had somehow disabled Storage permission for the app. > No wonder I couldn't find the diagnostic files. > > I've attached a zipfile containing *subsurface.log* and > *libdivecomputer.log*. > > On Mon, Oct 8, 2018 at 11:50 AM Dirk Hohndel <d...@hohndel.org> wrote: > >> >> On Oct 8, 2018, at 9:28 AM, Adric Norris <landstander...@gmail.com> >> wrote: >> >> I had an issue over the weekend, where I was unable to download a >> recently completed dive via BLE using Subsurface mobile 2.1.4 (4.8.3.0) for >> Android. No errors were reported, and the G2 did indicate that a device was >> connected during the download attempt, but Subsurface kept reporting that >> no new dives were found. Restarting the phone didn't make any difference. >> >> Unlike the desktop version, I didn't see any option to force download of >> all dives or create a libdivecomputer logfile (although the documentation >> indicates the latter should be present in Settings). So I'm not sure if the >> app wasn't seeing the new dive, or for some reason wasn't considering it to >> be a valid item and consequently skipping it. The only difference I can >> think of from previous dives, which were downloaded successfully, is that >> this one was had the G2 set to Sidemount mode. >> >> >> Subsurface-mobile always creates a log file and libdivecomputer log file. >> After an unsuccessful attempt, simply go to the About page, click the >> button and then paste the log files into an email message. >> >> This morning I tried again, via USB from a Windows 10 VM this time, and >> the dive was recognized and processed without issue. So if it is related to >> Sidemount mode (and that's *pure* speculation), the issue appears to be >> specific to the mobile app. >> >> >> No, I doubt it's sidemount related. More likely a BLE issue. >> >> The phone in question is a Google Pixel XL running Android 9, which has >> been used a number of times to successfully download dives from my G2. The >> G2 is running the current 1.4 firmware. >> >> Any suggestions on how I should go about diagnosing this issue? I'll be >> happy to provide libdivecomputer dump/log files, if someone can let me know >> how to generate them from the Android mobile app. >> >> >> See above. Please try a BLE download on the phone and then send the log >> files >> >> /D >> >> > > -- > "In the beginning the Universe was created. This has made a lot of people > very angry and been widely regarded as a bad move." -Douglas Adams > -- "In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move." -Douglas Adams
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface