Related
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

Voice prompts stopped reading numbers correctly

scottishwildcat

For at least a year now, the voice prompts on my Pixel 3a seems to have lost the ability to read out numbers correctly. It used to say things like "lap eleven, one fifty-nine", which was fine. Now she says things like "Lap 1 1 1 5 9", which can take quite some effort to decipher.

Anyone else getting this? Is there anything I can try my end, or is it a Garmin bug, or indeed an Android bug?

  • 0

    I've been having this for a while now too. From the timing of when this started happening for me, I think Google changed something in the Google Text-to-Speech (Google TTS) engine and/or Google Assistant that does not play well with Garmin Connect Mobile for Android.

    There are more posts about this problem starting to appear on the forums so you are not alone.

  • 0 in reply to Scillonian

    Thanks... couldn't find any when I searched but good to know it's not just me.

  • 0

    For me I am now fairly certain the problem is with Google TTS.

    I side loaded another text-to-speech engine on to my phone and switched to that one under Settings > Accessibility > Text-to-speech output > Preferred engine (Android 10). For the two activities I have done since making this change, the audio prompts have been as expected.

  • 0 in reply to Scillonian

    Hmm, I just tried that too, but the Garmin app still seems to be using the same voice.

    EDIT: Never mind, seems to be working after rebooting the phone. Will see how it goes on my next run...

  • 0 in reply to scottishwildcat

    You've already figured it out, but it is a requirement of Android that you need to restart the phone/tablet for any changes to the preferred Text-to-Speech Engine to take effect.

  • 0 in reply to Scillonian

    To be fair, it only seems to be a requirement for badly-written and/or third-party apps... Google's own apps started using it immediately, as you'd expect.

  • 0 in reply to scottishwildcat

    I forgot you were using something decent like a Pixel 3a.

    I'm currently using a Nokia branded HMD Global disaster. The hardware is OK but their implementation of Android 10 is flaky with no hope of them fixing it.

    Looking to replace it soon with maybe a Pixel 4a of some kind as I prefer the pure Android experience.

Copyright © 1996-2025 Garmin Ltd. or its subsidiaries