Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Erratic GPS Data

Nirmal Puranik
over 3 years ago

Erratic Connected GPS. Used to work fine now it isnshowing only straightline and distance calculated is also wrong. Steps are fine. GPS map data and distance is comletely wrong. No changes in usage problem started on its own.

  • 0 over 3 years ago

    Which Garmin device are you using?

  • 0 over 3 years ago in reply to seilogramp

    Vivomove Luxe. I use a samsung S22 Android phone. 

  • +1 over 3 years ago

    The next time you record an outdoor activity using the Connected GPS feature of your Vivomove, keep an eye on the Garmin Connect app. If it continuously shows active connection (a green dot on the circle around the icon of the watch at the top), or if it regularly refreeshes the heart rate and/or steps, then it means the connection between the watch and the phone is working fine, and that the wrong GPS data is to be blamed to your phone. Oppositely, if you see that the connection between the watch, and the phone is dropping, then it means that it is not the GPS that is to be blamed, but rather a problem in the Bluetooth connectivity. For this kind of problems, you best consult the Sync / Connection Troubleshooting Guide, where there are the most possible reasons listed.

  • +1 over 3 years ago in reply to trux

    Thanks for the input, I did the check as suggested. The connectivity from the Device to the phone was steady. The GPS was erratic on the phone itself. I had based on earlier posts - checked that there was no battery optimization setting for the Garmin Connect App. However on further checking I realized that the recent update had enabled battery saver as a default for the phone. 

    I turned the off Battery Saver option while on the outdoor activity and the GPS worked fine. I checked this on two out door activity in the last two days and can confirm that turning off the battery saver option during the activity resolved the issue. I now turn off the battery saver option during the activity and turn it on again once back. This is working well for me.

    Thanks a lot for the help on sorting this out