My System: Samsung Galaxy S4 with CyanogenMod 12.1 and Tasker 4.
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). 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. 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: 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. It is a poor, metallic machine sound, not nice, nearly unusable in modern times.īut since some days the Say-Action fell back to Pico TTS in the morning, when the Task is triggered.
Profile>Event>Type 'Off' in the filter and choose 'Display Off' Task>Type 'Wait' in the filter, set the time accordingly Task>Go to plugin and choose Hibernate. I followed these steps I found in another post and it works if I let the screen go to sleep on it's own.
On my system also pre-installed is the Pico TTS, which is pitifully bad in comparison to the google`s TTS. Greenify/Hibernate apps when I locked phone. I have therefore some "Say" Actions in it where I use the Google TTS, which came with the Google-App (App-id= vs 6.0.23.21).Įach 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. Since a while I use a Task which says every morning the weather.