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

Audio Alerts Still Given When Set to Off in Android GCM APP

I'd like to disable audio promts my phone makes every lap. I went to Settings > Phone > Audio Prompts and disabled Lap Alerts. But this didn't change anything. I also tried to change Dialect to completly different language and change the type of Hear Rate Alert but once I start an activity my phone makes the same audio prompts and nothing changes. Am I looking in a wrong place or is this a bug?
I'm using Instinct 2 solar with firmware 6.16

  • I believe this is a bug. My instinct 2 was not doing this 2 days ago and just started today. No way to disable audio prompts for lap and heart rate. I believe it started with the last Garmin connect app release but I could be wrong.

  • Side note. Apparently laps while strength training is the same as the number of seconds that have passed (e.g. 300 seconds passed you're on lap 300 when announced). Not sure if intended or bug but kinda funny 

  • Updated June 13th, 2022:

    This issue has been resolved with Garmin Connect, v4.55.1.

  • UPDATE: found the settings I thought you met Garmin Connect settings not Instinct 2 settings

    - Android Connect Mobile App Version 4.52

    - Alerts are set to off

    - Audio Prompts: Laps Alert on, all other audio  prompts off, dialect English

    --Alert type Pace/speed off,alert type average pace/speed,alert frequency lap

    --Alert type Heart rate off, Alert type Heart Rate, Alert Frequency Lap

    - I was recording Strength training, Every Set lap and heart rate was announced

    - Only English

    • Android 12, Android Connect Mobile 4.52
    • Settings > Phone > Alerts are off
    • Settings > Phone > Audio Prompts
      • Lap Alert (Off)
      • Pace/Speed Alert
        • Staus (Off)
        • Alert Type (Avg. Pace/Speed)
        • Alert Frequency (Lap)
      • Heart Rate Alert
        • Status (Off)
        • Alert Type (Heart Rate)
        • Alert Frequency (Lap)
      • Dialect (English - US)
    • During Walking activity - every lap (1km), During Strength activity - every new Set
    • I tried changing English - US to Čeština, Dialect was still English.

    I played around with Settings > Phone > Audio Prompts and it seems like nothing there changes anything.

    As 9098866 mentions I also started noticing this around 3 days ago (09.03.2022).

    I tried restarting the Watch and the Phone.

  • For anyone that sees this thread, if you are experiencing the same issue and you are willing to provide the details requested, please highlight my name and send me a Private Message. Thank you!

  • I am experiencing the same issue with my Instinct 2 Standard Edition. I tried turning off phone audio prompts both on my Instinct 2 and in the Garmin Connect App and it still plays lap and set audio prompts through my phone.  Is this a bug?  If not, can you please help me?

    I additionally tried reseting the Instinct 2 to factory defaults, deleted it from my Garmin Connect profile and deleted the bluetooth settings and it still made audio alerts on my phone with the audio prompts turned off on the watch and the phone or either or.  I was able to change the dialect to Australian from US successfully though as the user above was not able to do that.

    Instinct 2 Firmware: 6.16 (122c2c9)

    Garmin Connect Version 4.52 on Google Pixel 6 Running Android 12

  • This is a bug. Garmin is currently working on it. In the mean time you can go to settings/phone and turn the connection off during activites. Then back on after activities. I've found this the best way to stop the audio alerts until this is fixed.

  • Former Member
    0 Former Member over 3 years ago

    I have same issue. Sent info to Chris and to support. It is driving me crazy and it seems like many models have had or have this issue? Is there a timeline on how/when this will be fixed? Not everyone have this issue as I understand? 

    I am thinking to return the watch to be honest but that is a complicated process as well..

  • I am no longer seeing this issue on Garmin connect version 4.53. is this confirmed fixed?