Say Wavenet Action Stops Working after Running a Number of Times.

[Jake myers]

I am developing a custom voice assistant for my home using an old Android smart phone, but I have run into a peculiar issue. Say wavenet seems to just stop working randomly. The only fix I have found is to force stop tasker or to restart my device. And even then it still always stops working again soon after. I believe it is happening after say wavenet is run a certain number of times as I can quickly recreate the issue by executing it many times whereas in normal operation of my code it randomly stops after a decent period depending on the amount of use. I know the issue has something to do with the phone as I am unable to recreate it on my current smartphone. I have tried every variation of the say wavenet settings and nothing seems to fix it. I even factory reset the phone to see if that would help. The phone in question is a Droid Maxx 2 running android 7.1.1 if that helps. I would appreciate any assistance you can provide.

[João Dias]

Hi. Thanks for the report! Can you please check what happens when you run the action manually inside a Task in Tasker? Does it show an error when it stops working?

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[Jake myers]

Hi, when I run the action after it stops working it simply does not say anything. There is no error shown. I even checked the log and it seems as though its running the same as always. I have no idea why it just stops saying things.

[João Dias]

Thanks. So if you run the action manually inside Tasker it still turns green indicated that it ran successfully?

[Jake myers]

Yes, exactly. 

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/CAG6Z%2BFeJtOpB9VaZ0GZLk1gstLwUyAFuj3wi55NC3bNGq1GOhg%40mail.gmail.com.

[Jake myers]

So could you think of any reason this might be happening? At this point I'm considering just going with a different text to speech system.

[Duckredbeard]

Does your profile that runs this have a "limit repeats" checked?  Maybe have a different context run the same task and see if it stops there too.  I would just do a simple context that you don't already use for another config (app open, orientation face down, or charging start).

[Jake myers]

The issue is not with the actions not running, it is with them not working when run. For example if I make task that just has a ton of say wavenet actions in a row, it will start fine, and then after a number of actions it will simply stop actually saying anything. It still indicates that each action has run successfully, but they do nothing. From this point on, the say wavenet action will continue this behavior of not working whatsoever until I either force stop tasker or restart my device. 

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/7f8ac524-f5b3-41bc-ac27-6527fd993bebn%40googlegroups.com.

[João Dias]

Thanks Jake. Would it be possible for you to export a task like that so I can try to reproduce exactly what you have and see if the same happens here?