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

Cause Ghost Touch

Hello everyone,

I've owned a Forerunner 570 since June 3rd and, like quite a few others, I'm struggling with the ghost touch issue.

These are the problems I'm experiencing (along with some others here in the forum):

- With certain watch faces, the watch frequently acts on its own in the widget overview, randomly selecting or even moving widgets. It often takes several presses of the back button to return to the watch face.

-With the default watch face, the random widget selection happens mostly shortly after waking the watch and only occasionally.

- If you're in the widget overview and let the watch go back into sleep mode, then wake it again using the gesture, it often taps on widgets by itself.

-If you wake the watch and press the start button at exactly the same time, random actions are often triggered in the training menu, regardless of the watch face.

Since Garmin hasn't released a new update for nearly three weeks, I did some investigating myself and found the following:

- The problem disappears completely when Always-On Display is enabled.

- The Forerunner 970 often experiences the same issues.

- The problem seems to occur more frequently — or perhaps exclusively — on the 47mm version of the Forerunner 570.

- I had the watch for just two days when the 6.17 update was released, but I'm fairly sure the problem didn’t exist before that. The changelog specifically mentions battery optimization for the 47mm version’s watch face, which might be causing the issue.

- All ghost touch issues mainly occur right after waking the watch and immediately switching from the watch face to another menu (widget or training menu). There have been no false inputs in the settings menu, for example.

To me, this really seems like a software problem — what do you think? I'm checking for updates every day, hoping to finally enjoy the watch, and I’m very disappointed that such a widespread bug hasn’t been fixed, especially in such an expensive device so shortly after release.