Skip to main content

TTS engines other than Google speech recognition and synthesis not detected

Questions

I have three TTS engines installed on my Pixel 8 Pro + GrapheneOS (Android 16): SherpaTTS, RHVoice, and the Google standard one. They all seem to work fine when I test them in the TTS output submenu of accessibility: I press play and hear the sample output.

They also work in other navigation software that uses TTS (OsmAnd).

Only the Google implementation however works in ABRP; if I go to settings → navigation → navigation voice when SherpaTTS or RHVoice selected in the accessibility settings ABRP insists that I have no voice engine installed and asks me to download the Google implementation.

Somehow the detection of whether TTS is available seems to be hardcoded to the Google implementation; would it be possible to switch to whichever built-in method Android offers? In particular, SherpaTTS offers much better models than Google, so I’d love to be able to use it in ABRP.

Posted by XYZ ·
Status: Completed3 comments

Log in to comment and vote

Comments3

  • Christoph L

    •

    Feb 13

    This problem also occures on /e/os . ABPR falls back to using eSpeak which seema to be installed with the os (but delivers bad quality especially in german).

    SherpaTTS is installed and selected as default TTS but not used by ABRP.

    Would be great, if this could be changed to use better voice navigation on degoogled phones.

  • Linda ABRP

    Team•

    Dec 1, 2025

    Hi

    Right now it’s only Google that works but it might change in the future.

    • Didier Bretagnol

      •

      Jun 14

      Hello,

      6 months later, and still at the same point on this subject…

      Is there some fresh news? It would be great!