STOP *** BREAK MY WATCH - (Map Glitch)

Garmin what *** happened ?

Stop breaking my watch with your *** updates ?

Do you guys do not test your releases ? Do you have integration tests ? How come you always manage to break things with your updates ?

I used to use the map feature with some data displayed (pace, time and BPM), but today it was all *** messed up...

The map was constantly going in map zoom mode, and I was losing the context of my run....As long as I was trying to stick to the normal map screen, it  goes in map zoom mode, while running I tried to go back and constantly it glitches back to map zoom mode...I could not know my pace, and constantly  my run  was interrupted by this constant need to display the informations...you try go back and accidently  it was adding a new lap...***...

Worst, sometimes I  stopped the watch because of a redlight and I dont know why it goes to "do you want to save the activity?" ... and if you not pay attention you press Next because you want just to resume the Activity,  and it goes ahead to ask you RPE etc...*** don't try to be too clever...

Very very poor experience today...

Very very poor...

  • Worst, sometimes I  stopped the watch because of a redlight and I dont know why it goes to "do you want to save the activity?"

    To avoid this problem, open activity settings and set power save timeout to extended.

    Normally, the watch will try to automatically save an activity after it's paused for 5 minutes, but when you change the power save timeout to extended, it waits 25 minutes instead.

  • Hmm interesting..but I definitely  do not take 5 min to wait for a redlight...

    Thanks for your answer, I will try this

  • Hmm interesting..but I definitely  do not take 5 min to wait for a redlight...

    Hmm could be a bug then.

    If you're seeing the prompt to save the activity and a countdown to automatically save it, that's def the "power save timeout" feature. It's annoyed runners for years and it's the first thing I change when I get a new Garmin watch.

    Idk if the bug in your case would be that the timeout is too small, or that it somehow counts "inactivity" the wrong way. My understanding is that for the purposes of this feature, "inactivity" really means that the activity is paused.

    Here's the relevant manual section:

    https://www8.garmin.com/manuals/webhelp/GUID-0221611A-992D-495E-8DED-1DD448F7A066/EN-US/GUID-BB0CF463-4070-4FA9-8612-82751F82E316.html

    Power Save Timeout

    Sets the power-save timeout length for how long your watch stays in training mode, for example, when you are waiting for a race to start. The Normal option sets the watch to enter low-power watch mode after 5 minutes of inactivity. The Extended option sets the watch to enter low-power watch mode after 25 minutes of inactivity. The extended mode can result in shorter battery life between charges.

    Yeah this description is vague and misleading. It's not literally "inactivity" but it's the activity being paused. And it's not "low-power watch mode" but it's automatically saving the activity.

    This exact description was also used in older manuals where the feature works exactly the same as I described, so I wouldn't read too much into the manual, except for the part which says the timeout is either 5 minutes or 25 minutes.

  • It is definitely the "save activity" screen and not the power save one.

    I have seen from there and there in the forums that "phantom touch/moves" could be one of the reason, so disabling " the touch feature while doing  the Activity could help and solve all the issues I described in the original message

  • Oh yeah it could definitely be phantom touches triggering the Save menu item. That makes a lot more sense based on what you originally said.

    In that case, changing the power save timeout won't help you :/

    There's a whole history to this on Forerunner 955 (and probably your FR965 too):

    - originally touch was enabled in the pause menu (as long as touch was enabled in the activity) and there was no confirmation for saving your activity, so one phantom touch would be a disaster. (I *think* fr955/fr965 were like this originally, but if not, some older watches were)

    - at some point, touch was completely disabled in the pause menu, to avoid this problem, but lots of people who liked using touch for everything complained

    - finally, they re-enabled touch in the pause menu (as long as it's enabled in the activity), but they also added a confirmation prompt for saving your activity, if you used touch to select Save (instead of triggering it with the START button)

    Sounds good in theory, but like you pointed out, it's too easy to trigger the save confirmation by accident.

    If the problem is phantom touches, then I think your only choice to disable touch in the activity or change it to "Map Only".

  • Ok just an update.

    I did a run today with the touch screen off, and it worked perfectly fine. So I think that was definitely related to phantom moves/touches.

  • sometimes I  stopped the watch because of a redlight

    A tip could be to enable auto pause in which the watch pause activity when you stop moving and un-pause once you start moving again

  • Mine will take you back to the map screen every single turn notification, and I can't figure out how to stop this. I'm find with a data fields page with 'next turn' and 'dist to next turn' but every time I approach and reach a turn it's straight back to the map which I don't want. Any idea how I stop this going to maps?