viewtopic.php?f=3&t=2435 might help!

well, obviously we're pretty proud of WiGLE WiFi Wardriving! Even if WiWiWa isn't your favorite, phone stumbling has a few great upsides: the networks you observe are the networks within practical range no need to schlep around a fragile stack of gear everything is on a battery not much setup and st...

I appears we have an occasional issue where the application trying to show "Toast" during application launch or shut-down can result in the above exception. We haven't been able to reproduce this locally, but we'd love information from people who've experienced this. We've begun the proces...

Hi eka-eka, Thanks for your interest! I'm not quite sure which question you're asking here, so I'll provide some information and you can let us know if you need more detail. WiGLE actually receives measurements - observations from mobile client and various stumbling packages, rather than pre-compute...

Great, thanks for all the info. We'll archive this thread so that people in similar circumstances can read up. Two final notes: 1. That particular error should be isolated so long as you don't delete the old filesystem allocation (handing the damaged flash cell(s) back as "free" space.) 2....

With the release of Oreo, SDK compatibility for versions below Ice Cream Sandwich are being removed. We'll bump our minimum version as of WiWiWa 2.22, which means Gingerbread and Honeycomb (and earlier!) users will either need to stay on old versions of WiGLE WiFi (all versions are archived on Githu...

Fix should be working most everywhere - let us know how it's working for you!

Fix for this should be deployed on most devices now - if you're not running 2.21 yet, please update and let us know how things are working!

Yikes - this looks like an actual disk-level interaction problem - SD memory does age and develop flaws. 1. If you can back up your SQLite database: DO IT! (see if you can copy the file off via ADB/your favorite file manager). 2. Depending on your usual use case for WiWiWa, there are a few things yo...

That certainly looks like the same or related. Can you try de-authorizing and re-authorizing?

Thanks for your help!

Two reports that this is working in 2.21. Not working for you? Let us know!

Initial reports say that release 2.21 has fixed this in at least two cases; keep us posted!

Probably a transient network problem - sorry for the difficulty!

I'd initially made a mistake in the config- should be fixed now!

Moving conversation to our new Bugs forum - viewtopic.php?f=13&t=2465 for this issue.