By popular demand, we are now vending bluetooth network data via the API and basic search pages. Please consider the detail results a non-final implementation, as bluetooth devices are highly mobile.

per the other post, the data is preserved!

The "switching" behavior isn't something we've encountered before, but tapping the notifications in the taskbar, lock screen, or custom dialog overlays (lost / acquired GPS, etc) will switch back to the app.

-ark

Thanks for the feedback. The data *is* saved to the phone on reboot, and will be included in the next transaction. The notion of "Runs" rely on in-memory state in order to keep a coherent portrait of a single execution of the program, but observations and networks are logged to the database as they ...

the scan throttling should not affect overall performance - we haven't seen or heard much about an interactivity problem in that respect (nor does the play store "app not responding" dashboard show an increase). Historically, slowness in interactivity has been commonly associated with: 1. database a...

you'll still recieve discovery credit for any APs you're the first to find, and they'll still be geolocated - the timestamps-less locations will just be given lower weights than later observations with valid timestamps, and so long as you don't clear your DB, you'll be able to re-export these with v...

Absolutely; the KML export just disqualifies those because broken time stamps are often a proxy sign of bad GPS signal. You can gather data and export upload once the patch is in. You can also upload on a rolling basis and re upload when the date stamps are fixed

documented issue here:
https://github.com/kismetwireless/kismet/issues/122


proposed a patch here:
https://github.com/kismetwireless/kismet/pull/123

happy to hear if i've made a mistake - it's been a long time since i've used

ah, kismet is inserting "Mar" instead of "03" in the date stamps, which doesn't match our format.

ah, I've found the problem - the time value we populate in that table isn't getting set correctly on the observations. watch this space for details.

looking through the logs, I get: No locations results for transid 20190305-0008 - if the file doesn't contain coordinates, wigle doesn't attempt to build KML. since the link is a direct download, there isn't a good channel to provide an error message. feel free to post transids here, I can check the...

oh interesting - we'll check it out.

As a reminder, those KML files are just about your uploads, not a good way of evaluating the WiGLE trilateration tech.

Indeed, we're looking into whether or not the Lineage folks would consider a patch to remedy this!
If anyone has connections there, we'd love to get a read on what the criteria are, whether they'd consider it!

Cheers,

wow, yeah, the images make that easier to spot; they've been there all along, but only if you were using a screenreader or viewing source. They started out as a riff on Prince's spoken word stuff from Graffiti Bridge, if that tells you how old they are. Good spot. We owe you stickers, if you want 'em!

We use a wide range of technology, much of it is hand-rolled (since we've been around a while, a lot of new cool stuff has arrived, and we haven't always incorporated it). A few elements of our tech stack we're really happy with: - MySQL / MariaDB have worked for us since the start - ElasticSearch i...

Right now, we don't back-up your observation data for you; only the list of APs you have seen.

You can use the map tile overlays ("Mine" in settings) and search function to view your previously located APs.