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

Unhappy because software is buggy

As described earlier, zooming into tracks isn't working any more:
forums.garmin.com/.../display-track-of-an-activity-does-not-work-any-more


I was now doing a reset hoping to get this solved  by selecting >system >reset default settings on the watch

- Reset was taking 31 minutes. Most of the time it was displayed "loading maps...".

- Had to reenter language, age, weight etc.

- all activities  are still on the watch

- Software shows v.3.9 (did not yet connect to Garmin Express or Garmin Express Mobile)

- If I select the map track of an activity, this is still faulty.


Is this expected system behaviour? Is there another way to reset watch to the state it has been delivered?

  • I am unable to recreate this on my 945 with 3.90. Is there one activity type that is doing this, or is it multiple? Also, these are activities that were recorded on this device, correct? 

  • Yes, these are activities that are recorded on this device. It's faulty for all running activities. Don't have another type with GPS activated.

    How do I get the device in the state, I got it from garmin, please?

  • Via the watch menu, you can’t roll back the software. It will stay on 3.9 until I get a .gcd file out of an older beta download. 

    to do a full reset, you hab to use the list entry in the reset menu. Should be something like „reset data and settings“ (my watch is not in English, it can be different.)

  • I saw similar behavior- Garmin Express decided to upgrade in the middle of a software update.  The update said that it finished and I unplugged the watch.  At that time it got stuck on "loading maps" for over an hour. I did a factory reset and it took about 1/2 hour to get beyond "loading maps".  After it finally finished everything seems to work ok.  No idea what is was doing for all that time.

  • @ thank you to clarify this!

    @Garmin @all

    Run Garmin Basecamp for the 1st time.

    For the first 3h and 10 minutes I got green progress bars

    Finally, when progress bars ended the names changed from e.g. "gmapsup1" to "TopActive Europe 2019".

    Is this an expected behaviour or is something messed up with the maps? What could I do to get this solved?

    Would it make sense, to right click on the maps in Basecamp and to select "Install maps on Forrerunner 945"? Do I have to delete maps on 945 manually first?

    Or is there a way to get rid of corrupt maps on the Forerunner 945 and to install it with a fresh copy from Garmin?

    Any help highly appriciated!

  • I would like to help, but I am now confused as to what you are trying to do. You referenced an issue you are having when viewing the map of an activity on the device itself. I am still looking into this and may need to gather some information from your device directly to investigate. 

    You then mentioned rolling back software, which is something we do not officially support outside of beta programs, but you are now posting screenshots from basecamp. I am just confused what your goal is now and would welcome some clarification. 

    Are you still wanting to view the map of an activity from within your 945's history menu? Or are you trying to install different maps with basecamp? 

    Any clarification is appreciated and I apologize again for any frustrations you've run into. 

  • I'm still working to get the issue fixed with my 945 as described at the very top of this thread.

    - Zooming into a track does not work as track disappears. If zooming out, track gets again visible

    - Scrolling of the map section works neither

    - Map shows a lack of details

    I made this movie to illustrate the issue:

    Click here to play this video

    What I did with Basecamp is just a try to get this fixed. As for my understanding, this has something to do with the maps.

    Also to get the device into a state it was delivered was an idea to get this fixed, as this issue started just some time ago. And when I got this device it was fine.

  • Just want to mention, that issue is not yet solved.