sonora
commented
2 years ago Well, it's not too common that there is no TTS engine available, but even when, it is quite unclear if none is installed or just not activated. The mitigation depends on this as well as on the system itself... For instance on a Samsung phone I have just tested the menu path you specifiy "Android settings -> accessibility -> " gets you nowhere near where you could activate, let alone install, a TTS engine. Hence I am inclined to say OsmAnd can not sensically contain and maintain what to do on any given device where TTS seems not available for any individual reason.
🚀 feature request
Description
If no TTS Library is installed, you get the error message "Could not start tts engine" (see https://github.com/osmandapp/OsmAnd/issues/9637 and https://www.reddit.com/r/OsmAnd/comments/afaeo4/voice_guidance_does_not_work/ ) and OSM stays silent. It would be nice if the error message said instead: Could not start tts engine. Go To Android settings -> accessibility -> Text-to-speech and make sure a working engine is set as "Preferred engine".
Sidenote: GrapheneOS has no TTS library installed by default: https://grapheneos.org/usage#accessibility