dgruici

Hello! I'd be happy to. Unfortunately, it is the case that the app has no lower limit on accuracy. We are passing through the values that Android's location provider is giving us, no changes or adjustments. It would be nice if we were limiting the accuracy as that would be a much easier explanation of either reasons why, or putting in something in a later release to shut that off, but as it stands currently, that is what the system is providing for the accuracy. The truly unfortunate part is there could be a lot of reasons why everyone is seeing different behavior. I myself have seen the accuracy go as low as 10ft/~3m (and go as high as 116ft/~35m), but on average I see the ~33ft/10m that everyone is experiencing. I saw the mention of GLONASS and went down that rabbit hole of information as well. At the moment, I can't find anything definitive on whether or not the location provider that is available on Android is using it. My assumption is no. I know that certain smartphones are capable of hitting the other satellite providers and getting raw data, but there isn't anything official that I am seeing from Android other than how to get the data and ways to model it (found it here: https://developer.android.com/guide/topics/sensors/gnss). For this one, I am not sure how to answer this behavior from Locus Map without actually looking at their code (which I am sure they won't let me do since I am a competitor ). From the comments it seems like they are getting raw GPS but that would mean users on pre-2016 devices would not have access to this (like the above link from Android talks about) and the app supports back to Android 4.1. So Locus Map should still be using the regular location provider and should have the same average case of ~33ft/10m. However, this is just me making assumptions based on three comments in a thread, so please take that for what it is. To sum up and answer the original question, there is no filter or limiter added to the accuracy that the app is displaying. Whatever the Android OS sends is what we show. GLONASS and the other satellite providers are accessible by some Android devices, but I cannot find documentation stating that it is used in their location providers yet (but I am still looking). For Locus Map, I am assuming that user has had the same experience I have every once in a while, when I am testing, where the accuracy becomes better than the average case of ~33ft/10m. I am also still looking deeper for something that backs the claim that the FusedLocationProvider limits to ~33ft/10m, like what the Locus Map forum post has shown. That shouldn't happen based on how it works, but I don't have any hard facts to prove or deny just yet. Does this help answer the question?

Thank you wills2find for bringing this up, and for ErewashPaddler for doubly confirming it. It was an issue with our service that was sending out the messages not recognizing that our users actually updated their app. We went and fixed it. You should see the adjustment in the next 15 minutes if not sooner. Thank you again for reporting this. I apologize for how annoying that message was.

Hi wills2find! Are you able to log into the app after seeing it once? Or does it continuously appear? It sounds like the service we are using caught the older version but is being slow on realizing that you upgraded.

Hi there! Thank you for the feedback. We have updated that string to not be so "arousing" and the change for it should be out soon in a future release. Thanks again for letting us know!