The program is behaving as expected. This also affects a very small number of users. The problem lies in the "fuzziness" of the network location and the proximity of another geographic area. It's related to the fact that the people who live in this area probably never use Google maps, so there is very little correcting information going back to Google to correct the network location.
I just thought it was an interesting case where the program is working perfectly yet the results on the user end aren't satisfactory. We're not going to change anything in the program. If we were to decrease the minimum accuracy to less than 3,000 meters, many users would be forced to wait for a better fix. Also, more users would end up seeing the "location not computed" message which would decrease the user experience for no real gain in program functionality. -John Coryat -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/android-discuss/-/6nJWuGtYdaEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
