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

Alerts Getting Stuck/Repeating After Updating to 20.29

Hello! I've only had my Forerunner 965 for a couple of weeks now, and it was working perfectly when I got it. I usually have my phone with me, so I will just listen to music or a podcast through Spotify on my phone instead of through the watch. Before the update to 20.29, I had no problem at all with any of the alerts during activities. For example, setting a high heart rate alert would go like this: heart rate goes above set zone, my music pauses, alert voice says "Heart Rate High", music resumes, I continue with my activity. Exactly how it should be.

However, since the update, the alert voice will get stuck and repeat itself over and over again while rapidly pausing and playing my music. It sounds like "Heart rate heart rate heart rate heart rate heart rate heart rate heart rate heart rate heart rate..." and just continues this like a skipping CD. My phone also seems to freeze up and become very slow or even unresponsive. There is nothing I can do to stop this repetition on either my phone or my watch except for completely restarting my phone.

Also, it is not just with the alerts I set myself. If I create a workout and the alerts are telling me about the upcoming segments of the workout, it will get stuck saying, for example, "recover recover recover recover recover recover recover recover recover..." There's no gap between these or anything. It happens as quickly as if you were to read that as a sentence.

I would think it's something to do with my phone since I have to restart it to stop the stuck alerts, but I was not having this problem at all before I updated the watch to 20.29 a few days ago. I assume it must be a bug introduced there.

For additional info, my phone is a Samsung Galaxy S22 Ultra and I am using the Samsung Galaxy Buds 2 Bluetooth Earbuds with it. The phone, earbuds, and Garmin Connect are all up to date.

Is anyone else having this problem? Is it possible to roll back the watch to an earlier version until this is resolved?