Google TTS Update - Error: TTS: failed to initialize

828 views
Skip to first unread message

francwalter

unread,
Jul 3, 2016, 2:58:15 AM7/3/16
to Tasker
Hallo

Since a while I use a Task which says every morning the weather. I have therefore some "Say" Actions in it where I use the Google TTS, which came with the Google-App (App-id=com.google.android.googlequicksearchbox vs 6.0.23.21).
Each language I download offline has less then 10 MB, so this is not that huge TTS monsters from before and the quality of speech is quite good.
On my system also pre-installed is the Pico TTS, which is pitifully bad in comparison to the google`s TTS. It is a poor, metallic machine sound, not nice, nearly unusable in modern times.

But since some days the Say-Action fell back to Pico TTS in the morning, when the Task is triggered.
So I checked it and set it again to Google TTS in the Task in the Say-Action (but which was still set), and it worked initially, but not in the next morning, when again Pico was used.
So I disabled the Pico TTS so that Tasker must use Google TTS, with the result that in the next morning, when the Task is started automatically by my Tasker Time-Profile, I just got an error:

TTS: failed to initialize

If I manually set it again in only one of my four Say-Actions, the TTS works again for a while but will fail again next day.

I strongly guess that the problem started when there was an update of Google-App after 30th of June (or maybe with a Tasker update some days before which I think is much less likely).

What can I do?
I don't want to go back to Pico TTS!

My System: Samsung Galaxy S4 with CyanogenMod 12.1 and Tasker 4.8u5

Thank's
frank

francwalter

unread,
Jul 3, 2016, 3:16:21 AM7/3/16
to Tasker
As I read in another post there was a hint to add a Profile with Event > Tasker > Monitor Start and start with it an empty Say-Action.
I doubt this would help, I guess it will just fire the error as well.
The thing is, I cannot test it very good because if I choose the Google-TTS in the Say-Action after this it will work for a while.
I guess until the TTS is unloaded from memory (latest on the next morning).


Frank Röhm

unread,
Jul 3, 2016, 3:40:52 AM7/3/16
to tas...@googlegroups.com
And Yes, in
Settings > Misc > Reduce Ressource Usage
ist deactivated

francwalter

unread,
Jul 5, 2016, 4:52:57 AM7/5/16
to Tasker
Am Sonntag, 3. Juli 2016 09:16:21 UTC+2 schrieb francwalter:
As I read in another post there was a hint to add a Profile with Event > Tasker > Monitor Start and start with it an empty Say-Action.

Nope, doesn't change anything.
I went back to the Pico TTS now :(

Is there no one else having this problem? Is there no solution?

francwalter

unread,
Jul 7, 2016, 9:22:18 AM7/7/16
to Tasker
I mixed it up, I was wrong!
It is not the Google App which provides the TTS, it is the Google Text-to-speech App (com.google.android.tts).
I tried the previous version (I have chronical Titanium Backups) but this didn't change a thing.
So this has nothing to do with the TTS Update.

I then tested, if it is related to Greenify (com.oasisfeng.greenify), which is often buggy, and which I have under suspicion to "greenify" the TTS to hard:
Yes, with Greenify disabled (frozen/deactivated or uninstalled) the TTS works!!!. I was in the beta tester program, so I left this. Anyway, the beta is buggy at the moment.
I reverted to Greenify 2.8.1 (not beta) and now it works again :)

Reply all
Reply to author
Forward
0 new messages