Garmin Fenix 8 - Software 13.35 breaks touchscreen functionality
A workaround exists

Garmin has quietly rolled out software update 13.35, and unlike previous beta versions, this is an official release. However, for some users—including myself—this update has brought unexpected issues. This morning, I was convinced that my Garmin Fenix 8 51mm AMOLED’s touchscreen had completely stopped working.
The Issue: A Non-Responsive Touchscreen
I woke up at 6:30 AM, not by choice—my kid decided it was time to start the day. As part of my morning routine, I disabled Sleep Mode and started checking my Morning Report. That’s when I noticed something unusual: the touchscreen wasn’t responding at all.
At first, I thought I had accidentally disabled the touch function. I used the button shortcut to manually enable touch, only to find that it was already enabled. Just to be sure, I toggled it off and back on again—but nothing changed. The screen was still unresponsive.
Next, I restarted the watch, hoping that a quick reboot would fix the issue. No luck. At this point, I started to think I might have a defective unit. My initial reaction? At least it’s still under warranty. But then, I remembered something important: I had installed the 13.35 update just yesterday afternoon. Could this be the culprit?
Searching for Answers
A quick Google search led me to a Garmin forum thread discussing similar touchscreen problems. It seemed I wasn’t alone. However, I ran into another obstacle: the Garmin forums were down. I had to wait nearly 30 minutes before the website came back online due to an unexpected outage between 7 AM and 8 AM CET. Just my luck!
Once I finally accessed the forums, I found multiple users reporting the same issue—confirming my suspicion that update 13.35 was to blame. However, there was no official acknowledgment from Garmin yet, leaving affected users scrambling for solutions.
The Workaround: How to Fix the Touchscreen Issue
After some trial and error, I discovered a temporary workaround. If you wake up before your Focus Mode Sleep time ends, the touchscreen may become unresponsive. The fix? Manually adjust the Sleep Mode end time so that it ends before the current time.

Here’s how to do it:
- Go to your Sleep Mode settings.
- Adjust the end time to a point that is already in the past.
- Restart your watch—this step is crucial, as the fix won’t work without it.
And just like that, the touchscreen should start working again!
Some users have reported an alternative solution that works without restarting the watch. According to them, simply pressing the upper left button (which controls the backlight) restores touch functionality. Unfortunately, this didn’t work for me, but it’s worth trying if you encounter the same issue.
Is Garmin Aware of the Issue?
As of now, Garmin has yet to acknowledge or provide an official fix for this problem. This leaves users in a frustrating position, especially those who rely on the touchscreen for navigation and workouts.
Given that the problem seems to be linked to the Sleep Mode settings, it’s likely that Garmin will need to issue a firmware/software update to properly resolve the bug. Until then, affected users will have to rely on the workaround mentioned above.
Final Thoughts
If you’ve installed Garmin update 13.35 and are experiencing touchscreen issues, don’t panic—your watch isn’t broken, and there’s no need to rush to customer support just yet. While it’s frustrating and inconvenient, manually adjusting your Sleep Mode settings and performing a restart should temporarily restore functionality until an official fix is available.
Hopefully, Garmin will acknowledge the problem and release a software patch soon to address the issue permanently. In the meantime, if you come across any additional fixes, alternative workarounds, or troubleshooting steps that worked for you, be sure to share them with the community. The more information we can gather, the better!
Have you encountered this issue? What has your experience been like? Let me know in the comments!




Comments
There are no comments for this story
Be the first to respond and start the conversation.