ah shoot. a note here for everyone: PLEASE, BACK UP YOUR LOCAL DATABASE BEFORE UNINSTALLING THE APP. Part of Android's recent-ish filesystem requirement is removing all application files upon uninstallation. (they make exceptions for external storage, but they've limited that to docs and images now)...

not a translation error - "execution" is intentional, and a clarification.
"Run" has been ambiguous and misleading since the beginning of the app.
Both mean "during the current execution of the program."

The maps do provide a certain degree of offline caching, but it depends on your device; it bases that one OS version, free space, etc. we don't have much control over what it choses to keep/delete. As always, pull requests are welcome!

The fix is the APK mentioned above in this conversation - when you upload, that will try and prompt Android to install the new cert chains (and updated Play libraries), but this is a short-term fix. Google has already stopped supporting these releases, and won't update the Play services indefinitely...

There we way too many criteria people wanted to use for "when to upload" when we had a ticket open on this - and even more conditions when people wanted NOT to upload. That's why instead we implemented it as a "broadcast intent" so you could configure your criteria for yourself: ...

This starts being a surprise at Android 5.1.1 and up (the earlier versions simply can't get the correct cert authority chains.) 1. Chrome versions matter here - I don't know how far back the Chrome versions could handle the newer cert chains, and when devices on those Android versions stop getting u...

Are the connection problems all on a pre-Android 5 phone? The certificate core for those older phones may just not be able to handle newer trust-chains

(the limitation is NOT just our app, but the whole SSL library for Android)

We've looked into this quite a bit - unfortunately, it appears that it's not practical for a hobby project to qualify for Android Auto integration.

We're suggesting that the next time you pressed the "upload" button in the app when you DID have a connection, all those networks got uploaded. Uploading the file generated during the failed upload wouldn't make a difference after that - it would effectively be all duplicates. The app does...

Worth noting that a failed upload doesn't mean those networks are lost - only that they'll get uploaded next time you upload.

PS: previous (perhaps earlier) examples had date stamp problems, too - beware this current rev, we expect the correct number of digits in each position.

obvi we're happy to help if we can, but we'd prefer not to "special case" our parsing too much - folks already complain about how long it takes to get their files processed!

-ark

Talk to the maintainer - that line is kinda close, but it's got some mistakes and a weird starting number/bar. Do they claim it works for WiGLE?

https://api.wigle.net/csvFormat.html

this issue is fixed in the latest build.

I'm afraid this isn't really a practical application of the data or the app. 1. this is subject to coincidence - if you're driving in the same direction at the same speed as cars, or walking in a crowd, there will be far more "false positives" than anything meaningful. Every device on publ...