Wigle Wifi for Android: Suggestions

[arkasha]

What if we just add the device from the upload header to the rows on the site, instead of all this complication? Won’t identify non-CSV uploads, but that’s a vanishingly small percentage these days.

[pejacoby]

Seeing the addition of the device type in the Uploads display tip-out this morning -- nice! I like it.

Follow-on question: how do the 'device' entries correlate to the valuse shown in the Stats > Octet/Channel/File > "Type" table on the far right? I can see the phone models go under Stats > Android. Are the JHewitt's all "wardriver.uk-mod"? Where do the AtomGPS and other newer variants appear?

[arkasha]

this all depends on how the software implementer fills out the "pre-header" in the CSV. One could even customize it if with the JHewitt and AtomGPS boards!
https://api.wigle.net/csvFormat-1_6.html

[pejacoby]

Cool, current code for the M5 Atoms has been using "model=AtomWigler" and "device=M5ATOMGPS" since 1.4.
The values were "model=GPS Kit" and "device=M5ATOM" in Lozaning's original code up through 1.3 mods by Luke, which I have one device still running.

Should be lots of files uploaded with both of those.

JHewitt's code catches the various device types and populates model and device with "wardriver.uk rev# {mod info}" as appropriate for related mods.

I'm way outside WigleWifi suggestions now, sorry for the thread hijack.

[CyberDriver]

Hello,

It would be great to have an option that would allow the user to see the channel frequency of an AP (e.g. 2.437 MHz) or the channel number (e.g. from 1 to 13 in the 2.4 GHz range) as it used to be the case with the former versions, depending on the user preference.

Despite the fact I have large knowledge about radio stuff and therefore frequencies, it is sometimes (very) tricky to recognize which frequency is assigned to which channel.
A kind of "converter" option would be very useful.

Thanks,
C.D.

[arkasha]

this was a tough decision, since channel numbers are more convenient, but increasingly less useful. On the list view (the one we assume you're talking about), there's very limited screen real-estate, we decided "at least frequencies are 'sure'" whereas channel numbers are increasingly useless with all the new standards. We could also consider adding it on screens "when it fits" instead of replacing frequency?

Honestly, the hardest thing about adding a preference is translating it into 30 languages.

[CoD_Segfault]

Talking at Shmoocon, you had the suggestion of ignoring all the networks near home to speed up trilateration since they already have enough observations and won't get any more accurate. It would be nice to have an import/export option for the list of MAC addresses in the app. Plain text would be wonderful, as it would be portable to other devices as well.

[arkasha]

Note that you can accomplish this today with Tasker and the start/stop scan intents - useful, since a static list of networks would require continual upkeep, whereas tasker offers convenient "when connected to" and geofencing options.

[computerb0y]

Note that you can accomplish this today with Tasker and the start/stop scan intents - useful, since a static list of networks would require continual upkeep, whereas tasker offers convenient "when connected to" and geofencing options.

Really appreciate the geofencing stuff, thank you