970 Sluggish Maps, especially during a Run makes this feature nearly unusable

970 Maps doe not function while on a run after loading a course and hitting navigation. 

Note that using the standalone Maps feature alone is relatively slow, but once you are on your run, i assume because there is other processing going on, the maps feature is so delayed as to make it useless. 

The issue here is typically the WHOLE purpose of the navigate feature is you are in a new area and are using to help you not get lost.  But if you can not pan/zoom and see where you are without stopping your run and waiting for it to load it is not functional.  

For software engineer reference I only have 2 data screens on, and the "workout" adds a 3rd automatically.  So NOT a lot of extra data is being processes here. 

Link of an example below

https://imgur.com/a/DgyMmFx

Can Garmin "Cache" the area better?

  • I had about the same problem. For me it was the maps that where corrupted.

    - Do you get any error during load, when restarting the watch?

    In my case the maps could not be managed (remove/add) by using Garmin Express or on the watch. So I deleted them manually in the file system then reinstalled.