Related

Alerts Getting Stuck/Repeating After Updating to 20.29

brn360
1 month ago

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?

  • 0 1 month ago in reply to 5456322

    Yep exactly! I'm glad you got a video of it. Hopefully there will be a fix soon.

  • 0 1 month ago

    I had the exact same issue on my enduro 3 this morning during my run when I hit my rest periods. Software version 11.64. Had to restart my phone to break out of the loop.

  • 0 1 month ago in reply to 1355594

    Ah that's very interesting. Looks like we now have 3 different devices with the same problem confirmed. What kind of phone do you have? Just wondering if it might be Android specific or if that has nothing to do with it.

  • 0 1 month ago

    Yeterday I had a similar problem, never had that before. I am also on 20.29

  • 0 1 month ago

    I have the same problem.  Garmin forerunner 965 with latest software update and galaxy S23 ultra phone.

  • 0 1 month ago in reply to 1198518

    Yeah it seems like they definitely messed something up with the latest update. I was on support chat with Garmin yesterday and all I could get out of that was that they told me to try unpairing the watch from my phone, restarting my phone and my watch, and then repairing the watch. I seriously doubt that's going to fix it, but I will report back if it happens to. Otherwise, hopefully enough people complain that they get a fix out soon haha.

  • 0 1 month ago

    For everyone that sees this, I'm not sure how long it will be before we get an actual fix for this bug, and I also don't know how many different types of watches and phones it affects. However, at least with my devices (Forerunner 965 and Galaxy S22 Ultra), I have found a bit of a workaround.

    It may only work on Samsung phones because it requires opening Bixby, but maybe you can find something similar that works on your phone if you have something else. It's annoying, but it's better than completely restarting your phone.

    Once the alert gets stuck/starts repeating, if you hold down the power button to open up Bixby, it seems to interrupt the conflict between the alert and your phone and allows the alert to finish as normal. Sometimes you may have to do this a couple times because if Bixby says "Interrupted by Spotify" instead of "Interrupted by Connect", it doesn't seem to work. But on my run today, I only had to do it a max of 2 times per stuck alert to get things back to normal.

    Again, this is still super annoying, but it's a lot better than having to restart your phone or just listen to the alert freak out for your entire run.

    I'd also like to add that the recommendation from Garmin Support to unpair my watch, restart my watch and phone, and pair the watch again did not do anything to help this problem, so I wouldn't waste your time with that.

  • 0 1 month ago

    All-

    Thank you for your participation in this forum thread.  So that I may assist you further, please reply with the following:

    1. May we, if necessary, have permission to email you?
    2. May we, if necessary, have permission to view/access your Garmin Connect account?
    3. In what country do you live?