Voice prompts issues

[Rob Verhoeff]

@Ed-Van-Auken Under what kind of circumstances does this happen? An A–B route, a roundtrip or a self-made route with waypoints? In the latter case, the cause of the less effective voice guidance may be that your waypoint is placed too close to a junction or right on top of a roundabout.

[RainerT]

Simply share the route.
Sometimes the BT-Connection to your helmet is laggy, especially in case you have another sound source (music) active.
RT

[Ed Van Auken]

I have been using it this week to get around the town I was visiting. Mainly as A-B route.

[Rob Verhoeff]

@Ed-Van-Auken Then I also start thinking more about a BT connection that isn’t optimal. Possibly poor GPS reception?

[M. Schrijver]

It can be software (MRA) related. But you are the first to mention this and the last update is already from a while ago. So the chance it is MRA related is small.
Most likely your headset itself or the combination phone and headset.

Are you using other software like i.e Spotify together with MRA. Maybe even Samsung Soundassistant?

[F Nick]

I often have the same issue . Can’t work out the cause . Annoying as hell!

[Con Hennekens]

I have had the same issue as well. I think it is caused by my Sync3 AA/CP headend. I have not heard it with my direct connected helmet headset.

[Graeme]

Hi have the same issue, on Android auto devices on the bike and in the car, you miss the first bit of the announcement, e.g. at a turn that's 400 yards away, you just year "hundred yards turn left". Can the start of the announcement be padded to make the connection to the Bluetooth device happen prior to the announcement?

[Con Hennekens]

@Graeme, indeed, and probably no coincidence: the time it takes for the audio duck (the lowered music volume) to be restored takes a long time. Probably the time needed for those lost syllables...

[M. Schrijver]

I have not noticed this on my Android Auto setup. The instructions were always complete not a part of it.
I've not yet used 4.4.0/4.4.1.