{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicqco7onas2cpdfp7i7fnvytwpp5dn3fh5gfj4o54opbnraepjyhm",
    "uri": "at://did:plc:34cg4tn4iwemk3v5k3n3adwf/app.bsky.feed.post/3mivnptbcwi42"
  },
  "path": "/t/what-s-the-best-tts-text-to-speech-app-for-android-in-2026/34240#post_6",
  "publishedAt": "2026-04-06T17:14:15.000Z",
  "site": "https://forum.f-droid.org",
  "textContent": "bob.fg:\n\n> This is the bug I encountered today after a clean install.\n\nEasily fixed via ADB – I had the same here on LOS based ROMs. Assuming you use SherpaTTS:\n\n\n    $ adb shell settings get secure tts_default_synth\n    none\n    $ adb shell settings put secure \"tts_default_synth\" org.woheller69.ttsengine\n    $ adb shell settings get secure tts_default_synth\n    org.woheller69.ttsengine\n\n\nNow, SherpaTTS will work. And yes, it’s a known bug in LOS, since around 2024 – somehow, whatever TTS you install, will not be registered properly with the system (which is what this ADB command does).\n\nTo your original question: yes, I’d recommend SherpaTTS. Depending what languages you need, RHVoice should also be a good choice. Only when your “language needs” are not covered by either, I’d go with eSpeak – which has good language coverage, but sounds rather robotic in comparison.",
  "title": "What’s the best TTS (text-to-speech) app for Android in 2026?"
}