[21.19] BUG – touch is always enabled during activity

Seraph 1 day ago

Hi, after update to 21.19 public release, during activity (in my case walking and running) touchscreen is always enabled and can be operated by touch. Things doesn’t change when checking settings of each of those activities and in main settings menu for display. Everything is set to “touch disabled” or “use only on map”, but touchscreen stays touch sensitive. Even disabling touchscreen via shortcut on my device doesn’t seem to make any effect.

Please do something with this ASAP.

Ah – and YES – I’ve restarted device after update and made a WiFi sync.

Top Replies

Garmin-Sierra 1 day ago +1 verified

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

All Replies

+1 Garmin-Sierra 1 day ago

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

0 Seraph 1 day ago in reply to Garmin-Sierra

Wonderful! Thank you for fast response!

0 morey000 1 day ago

Yup. Touch is on for me too

0 formax 16 hours ago

This happened at me until I restarted my watch and it works properly now.

0 jkissane_ 13 hours ago

I was out for a run in the rain at lunchtime today & noticed the same as the wet sleeve of my jacket was swiping through the data fields. Touch is disabled for running like you said so a new feature in 21.19.

0 Seraph 11 hours ago in reply to formax

I thought that would solve the issue, but after short success of "killing" touch on walking activity it came back few hours later. I assume it came back, when I started different activity, which had touch enabled by faulty update.

0 Seraph 11 hours ago in reply to jkissane_

"It's not a bug, it's a feature" :D

0 Elbo 11 hours ago in reply to Seraph

I got an email from dutch garmin support stating the bug where touch for maps only during workouts doesn’t always work should be fixed in 21.19

Well, it’s not fixed. But Garmin developers probably broke it some more.

Garmin-Sierra are you aware of this email, the old bug, the lack of fixing, and how it most likely broke it some more (and that the release notes lack the mention off work on the touch during activities. Why are garmin developers so lazy for not properly mentioning everything in the release notes?)

Maybe this info helps you telling developers that there is a lot of work to do for them and that they should test more (or, start to test. That would really help)