Garmin has closed the book on the Forerunner 970 ghost touch problem, and the book does not have an ending. The long-running forum thread on unintended screen inputs is now locked, and Garmin's parting advice is to contact support and have the watch looked at individually.
That is not a fix. It is a handoff.
What owners are actually seeing
The original poster described it plainly: scrolling through glances, the watch sometimes behaves as if he swiped and tapped at the same time, registering a touch instead of a scroll. There is a small hitch right before it happens, like the panel stops tracking his finger and reads a press instead.
It gets worse from there in the replies. One owner said it had already happened on three watches. Another bought four units in a shop and found one that behaved, which turned out to be from the oldest production run in the store. Another said a replacement arrived working, then a second replacement developed the same fault.
Reports in the thread span glances, settings, activity menus and health metrics, so it is not one screen or one activity exposed to a stray palm. Several owners said it survived watch resets, phone-free setup and Wi-Fi setup, and showed up on both the firmware the watch shipped with and later versions.
Some users also reported that enabling the always-on display reduced the phantom inputs, which is a strange clue. It suggests a wake or refresh path rather than a dirty panel, though nobody outside Garmin can confirm that.
What Garmin said, and what it stopped saying
Garmin's first reply in the thread was standard triage. Update the watch, take off any screen protector, clean the display, restart it, then report the software version, whether the fault is constant or intermittent, and send a video through Garmin's secure file upload.
That is a sensible first pass. It is also the same advice Garmin gives for almost every touch complaint, and it did not stop the reports.
Then came the line that matters: Garmin said it was looking into the behavior on a case-by-case basis. Not a known software bug with a fix in progress. Not a service campaign. Case by case.
The final staff reply, posted a few days ago, repeated the theme. If your Forerunner 970 is on the latest software and still misbehaving, contact your local Garmin Support office.
Right after that, the discussion was locked. Existing posts stay up, but nobody can add to them.
Garmin locking a thread is not proof it considers the issue solved. Plenty of product forums get locked to stop pile-ons. But locking a five-month thread where owners were still posting videos, serial numbers and replacement history does remove the most public record of how widespread this is, and it moves the conversation into private support tickets where nobody can count it.
19.23 arrived this week and left the touchscreen alone
The timing makes this sting a little more. Garmin began rolling out Forerunner 970 software 19.23 on November 18, at a phased 50 percent of units.
That release is not empty. It brings dog profiles, dog activities and 15 new badges, along with a set of fixes elsewhere. What it does not bring, according to Garmin's own changelog, is anything about unintended touches or touchscreen sensitivity.
So the newest stable build for the watch, shipped in the same week Garmin closed the complaint thread, does not address the complaint.
Go back through the history and the pattern repeats. An earlier Forerunner hotfix was specifically pitched as fixing false inputs on the touchscreen, and reports continued afterwards. Whatever that patch changed, it did not end this.
The hardware question nobody has answered
The thread leaves two possibilities on the table and refuses to pick one.
The case for hardware: the same owner going through three watches, the shop test where four units out of four behaved differently, and one owner's note that a unit from an older production run felt fine. If the fault were pure software, all four shop units would have failed the same way.
The case for software: reports that the always-on display changes the behavior, reports that some people saw improvement after a firmware update, and the sheer spread of serial prefixes owners have posted, with no single batch emerging.
Garmin has not publicly identified a defective production run, has not issued a service program, and has not said whether engineering found a root cause. Owners are left guessing, which is exactly what a case-by-case policy produces.
What to do if yours does it
If your Forerunner 970 opens glances you never touched, the sequence that gives you the best shot at a remedy is short.
- Confirm you are on the current software (19.23 at the time of writing) before you contact anyone, because support will ask.
- Record a short video of the fault happening. Garmin's own staff asked for exactly this, through the secure file upload process linked in the thread.
- Have your serial number and the date and place of purchase ready.
- If you have already had a replacement with the same fault, say so up front. That history is the strongest argument you have for a different outcome.
- Note whether the always-on display changes anything for you. It is a real variable other owners have flagged.
The watch is still usable. Physical buttons cover navigation, and the touchscreen fault is intermittent rather than constant for most people. But this is a premium running watch with a sapphire lens and a titanium bezel, and a panel that reads scrolls as taps is not something you should have to work around on a watch at that level. If you are shopping, the Forerunner 970 is widely discounted right now, while the older Forerunner 965 does not appear in this complaint thread at all.
If you want the counterpoint, our Forerunner 970 and 570 launch breakdown covers what Garmin changed for this generation, and the 24.20 and 19.23 dog profile rollout covers what this week's firmware actually delivered. The Fenix 9 Pro registration failures from last week are a separate mess, but they show the same pattern of Garmin handling problems one customer at a time.
Bottom Line
Garmin has spent five months collecting evidence on Forerunner 970 ghost touches, has shipped at least one hotfix that was supposed to address false inputs, and has now closed the public thread with a case-by-case support line and no published root cause.
That is the weakest possible ending for a flagship running watch. Owners with a faulty unit should push for a replacement and document everything, because Garmin's own reply makes the individual ticket the only path left. Everyone else should know that buying a 970 today still means a small chance of a touchscreen that argues with you.
Sources: Garmin Forums thread 438628, Garmin Forums 19.23 release thread, Gadgets & Wearables, Notebookcheck on the earlier hotfix, r/Garmin ghost touch reports, r/garminforerunner thread.





