Skip to main content

Voice synthesis not remembered

ABRP always resets the german voice from de-de-x-deb-local back to de-DE-language, which is the worst voice I’ve ever heard.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Status: In Progress6 comments

This request was merged into another request

Comments6

  • Katya S. changed status to Awaiting Clarification
    Team•

    Jun 11, 2025

    Pinned

    Hi @Stephan Sickert,

    Could you try and reinstall the app as suggested in Settings for voice and speed cameras are not saved ?

    • Stephan Sickert

      •

      Jun 15, 2025

      Hi Katya,

      Unfortunately, this doesn't help.

      I installed the App on another phone (Oneplus 13) and this also falls back to the language default after some time.

      Regards,

      Stephan

  • Samuel_ABRP

    Team•

    Oct 9, 2025

    Hey Stephan,

    does this still happen on recent versions? If so could you please add more details? Everything could help here, as we are not able to reproduce this. Do you for example have to login again before this happens? Or does it also switch voice during navigation? Or does it only happen, when the app was in background / not active / restarted? If you can find a way to reproduce it, please let us know.

    • Stephan Sickert

      •

      Oct 9, 2025

      This only happens after closing the app (during charging or after reaching the destination). It doesn't happen when navigating. I also must not log in again.

      On my wife's Pixel 7 this problem does occur not as often as on my Xiaomi 14 or OnePlus 13, where it's resetting every time.

      • Samuel_ABRP

        Team•

        Oct 13, 2025

        Hey, we couldn’t reproduce it on any of the phones we have, but I made some changes in the TTS initialization sequence, so let’s hope that fixes the issues. It will be available in the next release (> 6.1.6), so please let me know, if that solves the issue for you.

      • Samuel_ABRP

        Team•

        Oct 15, 2025

        I finally found the root cause for this, a fix will be available with the next beta.