pejacoby
commented
4 months ago One additional issue identified -- as the 'new' file numbers overlap with uploads from a long time ago, Wigle is returning status to the auto-upload process indicating it already has the file, so no upload occurs. Screenshot attached of two runs today.
The first run was an hour walk with a file size of 310kb. Obviously there are more than "0 total" APs in this file -- no upload was attempted after a reboot.
The second file is from a quick reboot where I let everything fire up and start scanning, then shut down. Here too the file size and WiFi total count don't make sense -- 2kb file yes, but containing 3157 APs is unlikely. Again no upload attempted here on the reboot.
Previous files since the factory reset auto-uploaded but I'm guessing that is because there was no matching filename found in the call to Wigle.
Let me know if you need any other info. I was able to upload the larger file via the Upload link in the interface and Wigle is processing it.
JosephHewitt
When
bcis reset (due to a factory reset), new files will be generated with low IDs again meaning the filenames can collide with previous capture files.Capture files are currently opened with
FILE_APPENDmeaning new data can be appended to old captures. This likely won't result in any lost capture data at all, but will cause duplicate data when uploading to WiGLE and could cause user confusion.I can think of a few ways to fix this, but I think this would be the best approach:
On first boot (or after a factory reset), iterate the current capture files and find the highest ID. This can then be used to set
bcin the NVS so the captures will continue exactly as they did before the reset. This does mean the factory reset becomes slightly less 'hard' than previously implemented, but the documentation can also be updated to encourage users to delete all of their capture files before resetting the device if they are experiencing issues; this will cause thebcvalue to be fully reset along with everything else.