Current location position is not stable

NicoleLeiva

Hello!

We are using version 200.6.0 of the SDK and have noticed an issue where the location position pointer is unstable, constantly moving or jumping when the device remains in the same position. After debugging, we found that the accuracy is inconsistent at times. However, this issue does not occur while navigating.

Here, I've attached a video as a reference.

Is this a known bug?
Is there a planned fix for future SDK versions?

To mitigate the problem, we had to implement a CustomLocationDataSource.

 

Shubham_Sharma

Could you help provide some more context to help us narrow down the cause of the issue: 

• You mentioned issue doesn't appear when navigating, what Autopanmode does this behavior show up?
• From the video shared, it seems like the location display momentarily loses accuracy, then starts to pan to an "approximate" location and gains back location accuracy again in 1-2 seconds. Does the blue dot location position only jump around when the Location accuracy measurements are unreliable? 
• Is this issue reproducible in one device type or any device? Similarly, is the issue reproducible in previous ArcGIS Maps SDK versions? 

Here are some tips to help improve the location updates received by the GPS sensor: 

• Option 1:

If it becomes clear that your device’s GNSS measurements are consistently inaccurate (>20m), you could consider a few approaches to help improve location stability: Set High-Accuracy Criteria, you can configure high-accuracy criteria by creating an instance of Criteria and then passing it to the requestLocationUpdates. This signals to Android that your app prefers the highest-accuracy sensors.

• Option 2:

Enable “Force Full GNSS” (Developer Options) You can enable developer options to “Force full GNSS measurements” (no duty cycling) to ensure the device uses maximum power and tracks all satellite constellations/frequencies. 

 

 

 

 

 

 

 

 

 

 

 

While testing accuracy logs, ensure Improve Location Accuracy is enabled: Link

Please feel free to reach out if you need any further assistance or want help verifying the behavior. I'm curious to know if using CustomLocationDataSource was helpful because of filtering out inaccurate location measurements, or if there was another solution that you found helpful!