What are the plans for eSpeak?

## Summary

/e/OS currently ships eSpeak as the system default text-to-speech engine. eSpeak’s formant synthesis produces very low-quality, robotic output that degrades every component relying on the system TTS service (`TextToSpeech` API): TalkBack/screen readers, navigation voice prompts, read-aloud features.

This issue proposes evaluating and integrating a modern, fully open-source neural TTS engine as the default, keeping eSpeak only as fallback.

Background

  • eSpeak was introduced as a replacement after LineageOS removed Pico-TTS (Android 9). Community thread: Alternative to eSpeak?
  • eSpeak qualities: GPLv3, ~2 MB including dozens of languages, fully offline. This explains the original choice.
  • Limitation: formant-based synthesis, quality far below current standards; recurring user complaints for years, no alternative shipped by default. Users must manually discover and install third-party engines (RHVoice, SherpaTTS…), which is not discoverable.

Proposed solution

Evaluate **SherpaTTS** as candidate default engine:

Alternative candidates considered:

  • **RHVoice** (GPL): good quality, smaller footprint, but **no French support** — insufficient for global coverage alone.
  • Pico-TTS: removed upstream by LineageOS; re-adding it would mean maintaining it ourselves.

Suggested integration

  1. Ship the neural engine as default TTS engine in `/e/OS` builds.
  2. Fetch/download voice models on demand (per-language), similar to the existing voice data download flow, to keep system image size small.
  3. Keep eSpeak installed as fallback for low-RAM devices and languages not covered by Piper models.
  4. Ensure `Settings → Accessibility → Text-to-speech output` correctly lists both engines.
  5. Update /e/OS documentation accordingly.

Acceptance criteria

  • [ ] System TTS output uses the neural engine by default on supported devices
  • [ ] French, English (+ other major languages) voices available offline
  • [ ] eSpeak remains selectable as fallback engine
  • [ ] No Google dependencies introduced (checked against /e/OS de-Googling policy)
  • [ ] Verified with TalkBack and a navigation app (e.g. Organic Maps voice prompts)

Hmmm …

Your research seems to omit

https://gitlab.e.foundation/e/os/android_prebuilts_prebuiltapks_lfs/-/commit/21f89587c9a179313d661c7e9896a5f88295f380

I find Pico TTS.

1 Like

i have been using

Supertonic TTS

as with all open source software it seems to have some bugs but i am for the most part very satisfied with the natural quality of its voice. havent tried the other alternatives you mention

1 Like

Yes but today, nothing in the release.

it is on the phone.

Version 1.0 com.svox.pico

Just
$(call inherit-product, external/svox/svox_tts.mk)
and call it a day :)
1 Like