Tell HN: Google Maps is again requiring wi-fi scanning to enable navigation
As far as I can tell it's an exact copy of the behavior they exhibited last year and discussed in this thread: https://news.ycombinator.com/item?id=30167865
Personally when I turn off my Wi-Fi I want it to be off, period.
23 comments
[ 5.3 ms ] story [ 55.7 ms ] threadGooglers correct me on this, but from observation, that's how it seems to work.
I have actually tested this. It would take 45sec with just GPS, but under 7sec with WiFi.
Knowing Google's ethics (haha) they will definitely use this data also to advertise services to the people living there, as "now" they know exactly where you live and thus may push more relevant ads instead of a random store 500km away.
Even if you take advantage of tricks like out-of-band time, almanac, and ephemeris data, it can still take in the neighborhood of 10 seconds to get a fix. I imagine wifi is also less susceptible to issues that plague GPS like multipath and urban canyons
(b) When you or anyone else don't have a GPS signal because you're indoors, Google can run a Wi-Fi scan and geolocate you indoors from (a)
Also, s/Google/Apple/, s/Google/Mozilla/, they all do the same thing.
You can even run a Wi-Fi scan yourself with "sudo iwlist scanning", put the data in the appropriate format, and send it to Google's API [1] or Mozilla's API [2] for geolocation.
[1] https://developers.google.com/maps/documentation/geolocation...
[2] https://ichnaea.readthedocs.io/en/latest/api/geolocate.html#...
I decided to clear the app data, everything is in the cloud anyway and boom, all the issues are magically gone.