rod.sl...@gmail.com
unread,Feb 20, 2015, 11:56:45 AM2/20/15Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to joao...@googlegroups.com
I'm hoping some more experienced Tasker users can help with this one:
Run of thee mill Alarm Clock App, uses a scene and updates scene elements as you would expect.
The scene has a voice button which fires up AutoVoice Recognise and here's where the problems start.
The clock app has a real time update task running with a 1 second delay in it, otherwise, all the time.
When I trigger Recognise a number of problems show themselves.
AutoVoice first of all hides the current clock display scene and takes focus. I can't find a way to stop it doing this apart from checking if the scene is hidden and showing it again, but this is ugly. Even with this hack, the following problems are inconsistently consistent.
Delays. Autovoice is sometimes / often slow to respond and inconsistent in the time it takes to first fire up / respond and fails recognition often (this is not normally a problem when the clock app isn't running)
Or AV will appear to stop responding, hanging the update app and then a few minutes later while using Tasker, the AV task will complete for no reason I can see either.
This seems to affect Say Alerts as they also seem to stop working or are delayed.
I'm guessing it's because the update task is running constantly. So I've tried disabling the scene and the update task while the various autovoice tasks are running, but if AV fails, the update process doesn't continue, again don't understand why this is very inconsistent and overall even with this hack, the problems are inconsistently consistent.
Any ideas ?