Running audio prompt to the millimeter (v22.22)

Yes i noticed that after a recent update...

Same for me - decimal precision up to 3rd digit regardless of unit, i.e., 1.234 km or 4.567 m.

I'm looking for the "LOL" button.

I bet if you set Units to miles it would round nicely to whole feet. However I am not willing to try this out.

UPDATE: interestingly, I am still on 22.22 and .... it correctly rounded the meters (whole) and kilometers (to the first decimal).

How, I don't care, but good job Garmin :-p 

Edit: nope. Its back. See below for details

All, if anyone is still experiencing this, please respond to the following: 

1. What are your Units set to?
2. In addition to hearing the strangely rounded decimals, are you also seeing them displayed on the watch?
3. Does this happen for every upcoming turn while navigating?
4. Are your turn prompts still correct?
5. May I have permission to reach you via email, if necessary?

Yup, still getting it (although it seems, its not always like this....)

1. Units: kilometers

2. No, the watch shows 1.1km but voice tols me 1.136km

3. At every turn

4. Mostly correct, sometimes turns are missing, but I've always had that

5. Sure, reach me out!

I made a video recording of it  so you can see and hear in action

1.Kilometres 

2. No, the watch shows 3.3 km, but as others have said it tells me 3.314 km distance. I also have my heart rate zones spoken out in three decimal places, zone 2.234, at each kilometer lap. 

3. Yes

4. When I get a turn prompt, as others have said, some turn prompts are missing. 

5. Yes

Hi, 

After having contact with Garmin support for another issue where the sequence of instructions is wrong (first garmin says the next turn is 102,123meter to the right, but for now turn left), I connected my headphones to my watch instead of to my phone.

Guess what?? Both problem solved at once. 

Anyone else with this problem wants to try this and see if this was a lucky shot? 

Best regards 

Bart

I've just been out to test my watch with the headphones connected directly and can concur that everything works as it should, no strange rounding of numbers. So rather than it being a watch update, is it the connect mobile app causing the anomaly or my android phones software?