the Android version(s) matters a great deal - specifically, the TLS1.2-and-up support is just basic security practice at this point; it's Android < 4.4.3's lack of support for TLS1.2/1.3 without a forced install that's the problem, FOSS builds should still support modern TLS! Google forcing us to dr...

This puts us is tough spot; below 4.4 has been unsupported for years, and we’re delighted people are still using the app successfully on it. Google is forcing us to drop support for old versions to keep publishing in the Play Store- so we can’t reliably release a patch to use strong TLS versions now...

A few questions: - Radio Type - is there a complete list of supported types? - Channel - within 802.11n and 802.11ax, channel number + radio type doesn't map conclusively to a frequency - We have some previous VS1 uploads with some unusual quirks, including lat/long values that use different coordin...

Let me know if it works right now? re-enabled (old, broken) TLS1.1

Oh heck - this is because we recently undertook an SSL certificate upgrade.
Android 4.1.2 has been deprecated, and the recent Google Play Store policy updates forced us to drop support for older phones in new releases.

We'll see whether there's a work-around for this - watch this space.

can you share:
- App version
- Device make and model
- Android Version?

that's super useful. The "improbably short time" messages come from us ignoring suspiciously short interval between bluetooth scans - this is because most vendors have implemented a "double up" for ranging queries (which don't help us much): https://stackoverflow.com/questions/36...

The "Basic Search" Bluetooth tab has the view you're looking for. We don't put bluetooth front-and-center because location for BT devices (much of which are mobile) isn't particularly meaningful compared to cell and WiFi.

oh heck!
Thanks for the bug report. Any chance you can get us a crash report, or a debug log when it's not responding to help diagnose?

opened an issue on our github corresponding to this issue!

https://github.com/wiglenet/wigle-wifi- ... issues/582

Shoot, almost certainly a bug with the new pagination logic. I'll be looking at it over the weekend. A couple of questions: - if you scroll to the top and swipe down to refresh, does it that fix/change things? - What's displayed when you first launch the activity? - when you re-start the activity (g...

Worth noting that you can set your defaults, too - even if you don’t like enabling all the browser cruft (and OS settings) to allow that controversial feature. Tap “set default” when logged in and looking at the spot you’d like to be your default on the map.

Samsung? We've had this problems with some vendor day:night listview implementations.

Not to worry - GPS trouble happens with some frequency on both Kismet and Android rigs.
Email us at the admin address (in the footer of every page) with the transaction ID (from your uploads page) - we'll zero it out!


-ark

A couple of preliminary questions: Do you have a network connection? Google maps require a network connection to fetch tiles. Depending on your device the google libraries may or may not be supported - what are you running the app on? From where did you install the app? 2.64 is an outdated version f...