TTS without google

[RZHSSNZDH]

My phone's OS is lineageOS and I do not have any google service on it. I think it is why the app's voice guide does not work.
1- Is my detection true?
2- If it is, is there a way to resove this?

[RedAuburn]

That's partially correct, gapps includes a TTS app by default, while vanilla LineageOS doesn't. There are open alternatives such as RHVoice and eSpeak, but they sound very robotic.

The best option is to install Google's "Speech Recognition & Synthesis" app either via a Google play client like Aurora Store, or by downloading the APK on a site like APKPure etc.
You can disable network access to the app via long press to go to the app info, then disabling "allow network access" in the "mobile data usage" panel. I know it being made by Google feels bad, but it really is the best option IMO, particularly after disabling network access.

[RZHSSNZDH]

Thank you! I installed eSpeak. It is a little difficult to understand its voice, but it is better than nothing :)
I am strongly standing against installing google services.

[Misalf-git]

I have eSpeak installed as well, on a LineageOS-based ROM + MicroG, but I thought I give it another go because RedAuburn's answer was that thorough.
Google's "Speech Recognition & Synthesis" works without proprietary Google services - I don't know if MicroG fills the holes in that case though.

[RedAuburn]

yup, the google tts doesn't rely on Google services (although it may use them when network access is allowed)

[biodranik]

Did you read https://organicmaps.app/faq/voice/text-to-speech-android-tts/ ?

[Misalf-git]

Good to know.
However, before restricting network access, downloading language specific voice files through it's TTS settings seems to be required.

[GlytchMeister]

I've installed RHVoice but I can't install Espeak to do the workaround to get RHVoice to work on a custom degoogled ROM. I'm on Graphene OS. Espeak shows as incompatible when I try to install it.

Espeak's latest release is also quite old.

Is there any other workaround for this issue? Perhaps another, more modern FOSS TTS to replace espeak in this workaround? Or just a FOSS TTS that just works with no workaround?