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

FR255 (non music): Audio Prompts broken since 19.18

In the middle of a run the audio prompts stopped working between 2 successive laps and have been gone ever since.

I'm using Garmin Connect 5.2  and have tried with most previous versions since 4.60. Also tried various degrees of resetting, pairing, un-pairing etc.

Music is connected via BT headset and playing on an Android 10.

It's crazy how Garmin can release those firmware updates without proper regression testing. It's even more crazy how there's no way to downgrade a firmware on a FR255.

  • I never experienced this bug as such out of the blue.

    But I lost the audio prompts once with this scenario:

    - start my run with music from my smartphone 

    - the audio prompts work

    - mid run, switch to watch's music (long press the music button, start the music) without stopping the workout

    - then audio prompts disappear until I reboot my phone

    My headphones are BT multipoint and should work in this scenario I guess.

  • Ok, figured this out after stumbling across the following from the 955 forum:

    Audio Prompt Voice Playback

    If you have Bluetooth headphones paired to your Garmin device or paired smartphone or tablet, the native voice settings will vary. When the Bluetooth headphones are only paired to the Garmin Device, the audio prompt voice will follow your setting selections from the Garmin Connect app. If you have your Bluetooth headphones paired to your smartphone or tablet, the audio prompt voice may default to your smartphone's text-to-speech settings instead. 

    Since my watch is a 255 non-music, the output has to exclusively come from the Android Text-To-Speech engine via the Connect App.

    On my Android this is called "Speech Recognition and Synthesis from Google" and is a system app. After clearing its data,cache and disable/enabling it, the audio prompts starting working again.

    In conclusion, it doesn't appear to be related to the 19.18 firmware.