this is a new one for us; since WiGLE uses a "service," we need an explicit "exit" to terminate both UI app and service; that menu item should do that.

Can you tell us what app version you're using?

that's networks seen in the course of the run, and the number of networks seen during each scan period (and how long it took to actually cycle the driver/hardware)

Interesting; we'll look into the equivalent of this in software.

Cheers,

-ark

unfortunately, we don't know of a way to improve scan speed beyond this on Pie right now.
We're engaging on all fronts to try and find a way to keep wardriving on android alive.

We haven't extended the same degree of configurability to Bluetooth yet, but it should be free from comparable limitations.

there's a real case for low-gain stumbling - it's why we love pocket-based rigs and phones!

You get really accurate portraits of location (in exchange for lower "yield")

Cheers, and keep on stumbling!

-ark

Hi there! We rely on the Android API - so we're a passive scanning tool, and OS- and API-mediated. The rate varies by device, OS version, and driver (we work on a lot of hardware!). Since the android API doesn't expose raw packet information, you likely won't be catching any hidden networks with WiG...

Cool, please keep us posted here! This is probably the endpoint you'll want to use to see updates to the trilaterated position: https://api.wigle.net/swagger#/Network_search_and_information_tools/search_1 However in order to see the list of observations per network, check out: https://api.wigle.net/...

We've updated our web map tech, and want to make sure it's working for everyone. We've started a topic for feedback in the forums - please let us know if they're working for you!

First issue: Tor Browser locks down WebGL features to prevent some browser fingerprinting (which is good), but it results in broken maps. Following this report: https://trac.torproject.org/projects/tor/ticket/27290 I was able to get the maps working in TorBrowser using the following steps: visit abo...

Hi all, starting a topic for folks to report issues with the new maps. As stated in the news, our Google Mapping bill was stratospheric under their new billing policy, so we're trying out a new mapping system. We've cleaned up some initial Safari issues, and I think we're in a working beta, but if y...

The "Settings" hamburger menu should have additional configuration options for what sounds and speech are used!

That sounds like an additional power-saving measure specific to your handset - perhaps the WiFi power has its own power-save settings? This is the first we've heard of an issue like this, as far as we can tell.

Hi all,

Thanks for the input on this. I think we've got Safari fixed - would you mind clearing caches and retesting to make sure onlymine/others works on safari now?

This is a really cool experiment! A word of warning on methodology: it appears that you're trying to infer database behavior from the KML exports per-upload, which isn't working the way you expect it to. If you want to estimate the signal effects, I'd use the API to query distinct BSSIDs after each ...

quick update - basic CORS stuff should be fixed between www.wigle.net and wigle.net query URLS, but we still haven't gotten to the core of Safari's refusal to transmit session header. We'll keep working on it.

-ark