Audio language change not takling effect
-
In the Android app, I set the audio language to English.
Afterwards I select a route or Favorite and start navigation.
To my surprise, the app voice talking does not match the previously selected voice. In fact it's not even a native English speaker.I have repeated this with different English voices, but not once was the selected voice used for navigation.
Best regards, Makro
-
In the Android app, I set the audio language to English.
Afterwards I select a route or Favorite and start navigation.
To my surprise, the app voice talking does not match the previously selected voice. In fact it's not even a native English speaker.I have repeated this with different English voices, but not once was the selected voice used for navigation.
@Makro witch audio engine did you select and what kind of phone are you using
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S20FE mounted on a Quadlock and using Android Auto in my car -
I have the same problem. Oneplus 12. Voice engine is Google.Android which is the only TTS engine Avaliable.
I set mine to Australian English and it defaults back to British English which I don't mind but it isn't working correctly.
-
@Makro witch audio engine did you select and what kind of phone are you using
@Makro witch audio engine did you select and what kind of phone are you using
I have two engines available, a Google and a Samsung. Switching between them does not solve it, so I don't think it's related to the speech engine.
BTW, same result using my Samsung Active tab 3 and my Samsung Galaxy s24+.
Best regards, Makro
-
@Makro witch audio engine did you select and what kind of phone are you using
I have two engines available, a Google and a Samsung. Switching between them does not solve it, so I don't think it's related to the speech engine.
BTW, same result using my Samsung Active tab 3 and my Samsung Galaxy s24+.
@Makro use the Google Android engine. Can you choose a deferent cvoice overthere?
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S20FE mounted on a Quadlock and using Android Auto in my car -
@Makro use the Google Android engine. Can you choose a deferent cvoice overthere?
@Makro use the Google Android engine. Can you choose a deferent cvoice overthere?
Yes I tried various voices with both the Google and the Samsung engine. All my efforts are ignored.
Another bug is that the app writes in Dutch instead of English, but that's a minor issue, not related to the voice issue.
Best regards, Makro
-
@Makro use the Google Android engine. Can you choose a deferent cvoice overthere?
Yes I tried various voices with both the Google and the Samsung engine. All my efforts are ignored.
Another bug is that the app writes in Dutch instead of English, but that's a minor issue, not related to the voice issue.
@Makro I think you’ve done the wright steps. Maybe @Corjan-Meijerink can something smart about your problem
-
@Makro use the Google Android engine. Can you choose a deferent cvoice overthere?
Yes I tried various voices with both the Google and the Samsung engine. All my efforts are ignored.
Another bug is that the app writes in Dutch instead of English, but that's a minor issue, not related to the voice issue.
@Makro Yep same here, selected Belgium voice to check. The voice stays Dutch same as on the mobile phone.
Van Zumo 550 naar Navigator V naar Carpe iter V4b met MRA
-
@Makro Yep same here, selected Belgium voice to check. The voice stays Dutch same as on the mobile phone.
@Leike-Lodiers, I have been mentioning this before, also in our test group, but got no response. So I thought is was my phone's problem. I think the voice settings are not honored anymore since some versions, and the app defaults to the system voice. @Corjan-Meijerink?
-
I'll need to investigate this issue! Sorry for the inconvenience.
-
undefined Makro referenced this topic
-
Issue is solved in the 4.3.9 update
