WiGLE.net

Sorry if this is a topic already well explained, but my question does regard the app.

I'm sure the Wigle.net website can handle many more observation recordings due to the sheer amount of people registered on here, but for some networks, both phones I have that run the Android app seem sort of odd in the amount they want to read. Some networks I pass by a lot, such as going to the store, and it seems the app only either will record a sort of "soft-max" of 256, or 512. I say a soft-max due to earlier one network, despite only having 512 observations, the map showed more. I know the code exists on GitHub, but I'm not great at reading it, so there's probably a few things I'm not understanding.

how are you determining the number of observations in the DB?

In the app, when clicking on a network, it has the listed observations in the top bar with the other network information, yet for some networks the listed number of observations doesn't match what's shown on the map.
I just noticed it yesterday about an hour or so before I posted this, I'm not too sure how else to explain it yet. The only reasonable explanation I've found is from you I believe, that the Wiggle site has a better back end and phones aren't made with a large DB in mind?

that's because Google maps would bog down/drain your battery rapidly with too large a number of dots.

You can change your local build to retrieve more, but you'll find that Google Maps will become unresponsive/the app will run out of memory, or the phone out of battery if you set this much higher (your mileage will vary based on your device).

https://github.com/wiglenet/wigle-wifi- ... y.java#L83

We determined this limit through experimentation using a wide variety of handsets.