I've also recently experienced problems with TTS voice announcments. My selected voice was English (UK), it then reverted to default English (American accent). When I swapped to another language (French) there were noticable gaps over bluetooth where the French directions should have been (no voice directions). When I swapped back to UK English then I got the American accent again. There was a recent update to Google text-to-speech but I don't know if that is part of the problem.
On Sunday, 1 September 2019 23:39:32 UTC+10, Aceman444 wrote: > > TTS voices inside OsmAnd are only part of the equation. They define what > words OsmAnd should say in voice commands. > There need to be another app/module to know how to pronounce those words > via the sound output (speaker). > Check if you have such application. It is usually part of Android (check > in Android settings -> accessibility -> text to speech) or can be > downloaded from Google Play, Google Text to speech app. > > Do you have such a module installed in the Lineage OS 16 with microG? > > Dňa sobota, 31. augusta 2019 12:39:29 UTC+2 Joshuap r napísal(-a): >> >> Hello, >> >> I am using OSMAnd+ 3.5.6 from F-Droid on a lineage 16 (Android 9) with >> microG. >> No matter which TTS language I use, it doesn't work. Language packs >> consisting of voice recordings work. >> >> When I use the OsmAnd development extension to test the languages, the >> same problem occurs. >> >> >> I would be happy about a hint what the problem is. >> >> Thanks a lot >> Joshua >> > -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/6538e8a1-8758-4ab2-9db2-9f3c030ea725%40googlegroups.com.
