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

Bug report Version 21.19 - Disabled touch still active during activities

Touch screen is still active despite being turned off for all activities, both during the activity and whilst stopped. Have confirmed touch is set to disabled on both the activity menu and general setting.

This is especially frustrating when recording an activity when it's raining as this causes the screen to cycle through data screens. Also runs the risk of accidentally deleting an activity if paused. 

Bug seems to have started following the v21.19 update.

  • We are aware of this disruption and are currently investigating. I apologize for any frustration!

  • I updated my watch to v21.19 today and confirmed the same symptoms after reading about it in other forum posts and online articles. Enabling touch in the settings and then disabling again didn't make a difference for me either, but rebooting the watch has apparently fixed it completely.

  • I updated to v21.19 earlier today and confirmed the same symptoms after reading about it. Rebooting the watch fixed it for me.

  • I had the same problem after updating to 21.19. Restarting the watch fixed the problem for me.

  • Not only are activites now permanently touch enabled, the interface also goes crazy and detects all kinds of phantom input, has reconfigured data fields and makes it almost impossible to quit an activity. As soon as I pause the activity with the physical button and navigate to the menu the watch detects an input and continues the activity. Rebooting the watch didn't help either. 

    This is absolutely crazy and renders the watch entirely unusable for any activity. This needs to be fixed yesterday.

  • I’ve noticed the same behaviour on 965, restarts helps for couple of hours but later on touchscreen keeps being active during activity despite all settings set to “off” :/

  • All, 

    Thank you for your patience as we investigated this disruption. This has been fixed in Beta 21.20 which is currently at 100%. Feel free to wait for the live update if you prefer. 

    See Public Beta Version 21.20 - 100% for the full change log. I will update this thread once the update is live!