Speed audio prompts with 3 decimal places

Jatzzek 1 month ago

After the last update, speed audio prompts are announced with an accuracy of three decimal places (at least in the case of Bike activity). Previously, speed audio prompts were announced with an accuracy of 1 decimal place and that was really OK. At the moment it takes ages for the synthetic voice to pronounce the full speed value, and nobody needs such accuracy for anything. This is really annoying.

Garmin please fix this.

Top Replies

Garmin-Sierra 24 days ago +2 verified

All,

We are aware and are investigating this concern. At this time it looks like it only occurs when the audio prompts are coming through the phone's speakers or headphones that are paired with your phone…
2314079 26 days ago +1

Happens when running a gpx course as well "Turn left in 17.381 metres" ... absolutely pointless
RadekGorbi 25 days ago +1

Yes, I have the same while running. Decimal value is not needed, better is to round it out.

All Replies

0 PubBike 1 month ago

The order of the prompts seems to keep changing. I expect the lap announcement to come first but this doesn't happen either. I've also experienced problems with the lap announcement not happening at all until I restarted the phone.

Also, if I have power alerts configured, and then I ride a bike without a power meter, the power alert still happens but says "Average power 65,535 watts".

I've submitted a support request for these two issues.

0 Ian the Morris Dancer 30 days ago

FR955 FW22.22: turn by turn navigation for running also gives audio prompts to three decimal places, i.e., the nearest millimetre! Again, pointless and time wasting. To the nearest metre would be more than adequate!

0 lenrok258 30 days ago

I'm pretty much sure it was not intended thus it's a bug.
Garmin, could you please fix it? It's extremely annoying.

0 2314079 26 days ago

Happens when running a gpx course as well "Turn left in 17.381 metres" ... absolutely pointless

0 RadekGorbi 25 days ago

Yes, I have the same while running. Decimal value is not needed, better is to round it out.

0 Jatzzek 25 days ago

Hey Garmin do you really think it matters to anyone whether they are riding at 18.372 km/h or 18.4 km/h?

Or does anyone care whether he/she has to turn in 20 m 36 cm and 5 mm, or simply in 20 m?

0 1641945 24 days ago

Seems like a issue with the garmin connect app.

If you connect your headphones to the watch instead of to your phone, the everything seems fine.

Garmin is already aware of this, now its waiting for a bug fix.

+1 Garmin-Sierra 24 days ago

All,

We are aware and are investigating this concern. At this time it looks like it only occurs when the audio prompts are coming through the phone's speakers or headphones that are paired with your phone. If your headphones are paired to the watch directly, the 3 decimal places are not announced.

Please let me know if I may have permission to add you to the impact of our report by answering the following:

Please confirm if you heard the prompts with the 3 decimal places with your watch paired to your phone, watch, or both.
If necessary, may we have permission to reach you via email?

Thank you!

0 2314079 24 days ago in reply to Garmin-Sierra

Heard whilst connected to phone. Ok to email.

0 RadekGorbi 24 days ago in reply to Garmin-Sierra

Happy to help.

1. Command voice from phone.

2. OK