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

Activity datafields change by itself

In my opinion the feature to change datafields during activity by long pressing any datafield is useless or at least there should be ability to lock datafields in the settings. It is quite annoying that datafields keep changing by itself during an activity if my shirt sleeve or sweaty arm hair touch the screen. And I don't want to disable touch screen during activity just because of this because then I can't use the map properly.

I think this could be fixed with one of these solutions:

  1. Completely delete the ability to change datafields during activity by long pressing datafields.
  2. Add ability to lock datafields.
  3. Make the touch screen better to ignore accidental touches made by arm hair or a shirt sleeve. (I've noticed that especially synthetic materials used in sports shirts cause a lot of wrong touches whereas cotton does not. Accidental touches also happen often when the map screen is active. Even the slightest touch of  sweaty hair may activate the map zooming and panning function and pan the map.)

Please Garmin, fix this asap! It is really frustrating to keep fixing my datadields again and again during activity.

Top Replies

  • Make the touch screen better to ignore accidental touches made by arm hair or a shirt sleeve. (I've noticed that especially synthetic materials used in sports shirts cause a lot of wrong touches…

All Replies

  • Make the touch screen better to ignore accidental touches made by arm hair or a shirt sleeve. (I've noticed that especially synthetic materials used in sports shirts cause a lot of wrong touches whereas cotton does not. Accidental touches also happen often when the map screen is active. Even the slightest touch of  sweaty hair may activate the map zooming and panning function and pan the map.)

    I mean, people have been complaining about this kind of problem forever with garmin's touchscreen watches. While the touch UX has improved a lot since, say, 2015 (when the 630 came out and i first personally experienced accidental touch issues like you described), these phantom touch complaints haven't gone away. I've seen them in the forums for every touch-enabled Garmin watch that came out since then.

    It seems that Garmin's strategy is to sidestep the problem by disabling touch on the pause menu, where a couple of accidental touches could cause an activity to be unintentionally saved or discarded.

    I just think that if they haven't figured out how to ignore accidental touches after all this time, it's probably not gonna happen.

    And I don't want to disable touch screen during activity just because of this because then I can't use the map properly.

    If you disable touch during an activity, can't you just scroll to the map page, press START to enter pan/zoom mode, and use touch freely?

    That's how it works on my 955 (which afaik, has very similar firmware to 955). Other than scrolling to the map page itself, it's just one additional button press. (Yeah it's annoying, I know.)

    • Completely delete the ability to change datafields during activity by long pressing datafields.
    • Add ability to lock datafields.

    Having the ability to lock datafields would be nice. It could just be a checkbox/toggle option with a name like "edit data fields with touch".

    Alternatively, the UI for editing datafields via touch could change. It's kinda annoying that once you've selected a new data field, the way to (implicitly) confirm your changes is to tap anywhere on the screen. The only way to undo your changes is to press Back or swipe left.

    IMO there should be an explicit confirmation prompt for changing a data field. Then again:
    - if the prompt is too simple (e.g. one button for yes, another button for no, just all the other yes/no prompts), then it would be too easy to accidentally trigger confirmation as well

    - if the prompt is too complex (e.g. drag slider to confirm), then it might be annoying. (small price to pay tho.)

    I think there's a few things in the UI that would benefit from having a "drag to confirm" prompt, as opposed to the existing "yes/no" prompts.