WiGLE.net

Hi,

I am running Wigle Wifi on my Samsung GS2 phone. I noticed a few days ago that the dashboard showed my "total distance" from about 1500km to over 100,000km.

Yesterday and today I noticed that it seems to take a very long time (waited about 30 minutes yesterday, today waited for over 15 minutes) to get a GPS or network lock. Yesterday when I attempted war driving again about 2 hours later, it seemed to get GPS lock within 2 minutes on that attempt. Both times I checked with the google maps app to see if I got a GPS lock and the maps app worked fine (even when wigle could not get any lock). That seems to indicate that my GPS works fine.

Today I uninstalled / reinstalled the app, just in case there were issues with it. After that it took about 1 minute to get a network lock, followed by GPS lock another 2 minutes later.

Under the list window it showed that it detected about 700 new wifi points, but in dashboard it showed "New nets since upload" as 0.

I did an upload nevertheless, and it seems to have been reflected in my stats here.

I am running the latest version available in Market (can't see the version number in the app itself when I looked around).

Not sure what is going on.

I have the Samsung GS2 phone too. The GPS is almost as temperamental as my old Galaxy. I don't think Samsung puts very much effort into the details.

I have the Samsung GS2 phone too. The GPS is almost as temperamental as my old Galaxy. I don't think Samsung puts very much effort into the details.

Actually I normally get GPS lock on my other apps within a minute usually. And wigle is also supposed to get a location lock by using the telco towers if GPS is not working. In my case it did not get a lock from anything at all.

Anyway as I stated, I checked if my GPS was working by using the maps app from google where it got a lock from GPS within seconds.

If the phone has gps lock, WigleWifi will use it, as long as the accuracy isn't an insanely high value measured in miles (which happens far too often). By default WigleWifi will only use GPS and not use network locations, there's an option for that in the settings page if you want to enable it. If you see the dashboard say zero networks, or zero observations, right after startup it's because the count over the database hasn't completed yet. We have a todo to get rid of that initial counting altogether.

bobzilla, the dashboard was checked after it detected 700 new wifi points. That was over a 20 minutes trip in a car. So wigle was running for at least 20 minutes before I checked the dashboard. Nevertheless there were the other issues which I mentioned observing as well.

Anyway it seems to be working fine again, since I did that reinstall. Not sure what happened initially or why it happened.

I went on a 500 mile trip and noticed there was a 50% chance of Wigle losing GPS updates after using Google Maps or Facebook checkins. The Wigle gps cordinates would hang and not update. It happened with both my Samsung S and S2. Looks like an Android bug, but I've had long runs show up at a single location.

I've noticed some oddities where google maps seems to interfere. This seemed to start after one of the gingerbread updates. Apps really shouldn't be able to interfere with each other, especially when they're both basically just listening for events. We haven't really found a way around it, we try to restart our gps listening infrastructure if there hasn't been an update in a while, that can un-stick it.