Continuous mode in AutoVoice working intermitantly

593 views
Skip to first unread message

william....@gmail.com

unread,
Feb 16, 2015, 5:10:49 AM2/16/15
to joao...@googlegroups.com
Hi , the Continuous Mode in AutoVoice (V 2.0.25) is not working very well and stops working all the time. In order to get it working, I have to turn the continuous mode off and the on again. I am using Autovoice to change the Google Now Hotword (using Tasker and AutoVoice), which is working with audio response.

Does anybody know how to get AutoVoice Continuous mode to work more reliably?

João Dias

unread,
Feb 16, 2015, 10:20:41 AM2/16/15
to joao...@googlegroups.com
Hi there.

Can you please try this:
- clear logs
- enable system logs
- start autovoice continuous
- wait till it stops working
-export logs and paste them here

Thanks and sorry for the trouble!

On Mon, Feb 16, 2015 at 10:10 AM, <william....@gmail.com> wrote:
Hi , the Continuous Mode in AutoVoice (V 2.0.25) is not working very well and stops working all the time. In order to get it working, I have to turn the continuous mode off and the on again. I am using Autovoice to change the Google Now Hotword (using Tasker and AutoVoice), which is working with audio response.

Does anybody know how to get AutoVoice Continuous mode to work more reliably?

--
You received this message because you are subscribed to the Google Groups "joaomgcd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joaomgcd+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

william.walker39

unread,
Feb 16, 2015, 11:36:24 AM2/16/15
to joao...@googlegroups.com
Hi,

Thank you for your reply,

I did as you requested and the resultant logfile is below. The Google Now Hotword I used is 'Computer' and it stoped working after only one command. But before this example, I did get it to work for ~10 commands before it stopped working. It has never worked that well before, perhaps it had something to do with clearing out all the logs, which I had never done before.

By the way, since I contacted you I have gotten a new Hotword to work reliably by using the App: Mic+. It also does not erase the Google Now information as I observed with AutoVoice, and it doez not make beeping sounds all the time.

But even though this works with Mic+, I am still very interested in getting it to work with AutoVoice because it is more powerful and versitile.

Thank you for looking into the problem,

William Walker


-------------logfile------------
Trigger Words - 2015-02-16 17:11:31.282 - Removed trigger words:
what time is it
Profile Matches - 2015-02-16 17:11:26.664 - "media on" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.649 - "cast tv" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.634 - "media mute" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.619 - "cast monitor on" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.606 - "unit bright" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.590 - "unit dim" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.573 - "cast off" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.550 - "s voice" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.519 - "cast william tv" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.498 - "heater" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.448 - "home screen" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.398 - "system" matches "what time is it": false
Profile Matches - 2015-02-16 17:11:26.322 - "computer" matches "what time is it": false
Trigger Words - 2015-02-16 17:11:26.273 - Current trigger words:
what time is it
Trigger Words - 2015-02-16 17:11:26.268 - Added trigger words:
what time is it
Recognition - 2015-02-16 17:11:25.384 - Got commands: Received possible commands:
what time is it

Trigger Words - 2015-02-16 17:11:25.078 - Removed trigger words:
computer
Computer
pewter
komputer
Profile Matches - 2015-02-16 17:11:20.869 - "system" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.851 - "system" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.833 - "system" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.826 - "system" matches "computer": false
Continuous - 2015-02-16 17:11:20.787 - Beginning of speech...
Profile Matches - 2015-02-16 17:11:20.781 - "media on" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.778 - "media on" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.775 - "media on" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.769 - "media on" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.757 - "cast tv" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.753 - "cast tv" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.749 - "cast tv" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.747 - "cast tv" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.735 - "media mute" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.732 - "media mute" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.729 - "media mute" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.726 - "media mute" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.714 - "cast monitor on" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.712 - "cast monitor on" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.709 - "cast monitor on" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.703 - "cast monitor on" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.690 - "unit bright" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.686 - "unit bright" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.684 - "unit bright" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.681 - "unit bright" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.670 - "unit dim" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.667 - "unit dim" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.665 - "unit dim" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.662 - "unit dim" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.651 - "cast off" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.649 - "cast off" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.647 - "cast off" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.644 - "cast off" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.632 - "s voice" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.630 - "s voice" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.627 - "s voice" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.624 - "s voice" matches "computer": false
Continuous - 2015-02-16 17:11:20.613 - Unmuted Successfully
Continuous - 2015-02-16 17:11:20.609 - Ready for continuous speech...
Profile Matches - 2015-02-16 17:11:20.595 - "cast william tv" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.586 - "cast william tv" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.550 - "cast william tv" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.547 - "cast william tv" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.529 - "heater" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.519 - "heater" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.503 - "heater" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.482 - "heater" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.460 - "home screen" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.454 - "home screen" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.447 - "home screen" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.431 - "home screen" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.335 - "system" matches "komputer": false
Profile Matches - 2015-02-16 17:11:20.326 - "system" matches "pewter": false
Profile Matches - 2015-02-16 17:11:20.307 - "system" matches "computer": false
Profile Matches - 2015-02-16 17:11:20.303 - "system" matches "computer": false
Continuous - 2015-02-16 17:11:20.188 - Unmuted Successfully
Continuous - 2015-02-16 17:11:20.181 - Ready for continuous speech...
Recognition - 2015-02-16 17:11:20.170 - Clearing last command id
Profile Matches - 2015-02-16 17:11:20.131 - No Last Command Id matches No Last Matched Command Id
Profile Matches - 2015-02-16 17:11:20.125 - "computer" matches "computer": true
Continuous - 2015-02-16 17:11:20.097 - Message Start listening
Continuous - 2015-02-16 17:11:20.091 - Muted Successfully
Continuous - 2015-02-16 17:11:20.087 - Message canceled recognizer
Trigger Words - 2015-02-16 17:11:20.069 - Current trigger words:
computer
Computer
pewter
komputer
Trigger Words - 2015-02-16 17:11:20.064 - Added trigger words:
computer
Computer
pewter
komputer
Continuous - 2015-02-16 17:11:20.057 - End of speech
Continuous - 2015-02-16 17:11:20.045 - Restarting continuous listener
Recognition - 2015-02-16 17:11:20.000 - Got commands: Received possible commands (continuous):
computer
computer
pewter
komputer

Continuous - 2015-02-16 17:11:19.962 - 4 results from continuous!
Continuous - 2015-02-16 17:11:19.943 - Message Start listening
Continuous - 2015-02-16 17:11:19.937 - Muted Successfully
Continuous - 2015-02-16 17:11:19.928 - Error: RecognitionService busy
Continuous - 2015-02-16 17:11:19.921 - Message Start listening
Continuous - 2015-02-16 17:11:19.914 - Muted Successfully
Continuous - 2015-02-16 17:11:19.910 - Error: RecognitionService busy
Continuous - 2015-02-16 17:11:19.905 - Message Start listening
Continuous - 2015-02-16 17:11:19.901 - Muted Successfully
Continuous - 2015-02-16 17:11:19.896 - Error: RecognitionService busy
Continuous - 2015-02-16 17:11:19.888 - Message Start listening
Continuous - 2015-02-16 17:11:19.883 - Muted Successfully
Continuous - 2015-02-16 17:11:19.879 - Error: RecognitionService busy
Continuous - 2015-02-16 17:11:19.876 - Message Start listening




Sent from Samsung tablet
You received this message because you are subscribed to a topic in the Google Groups "joaomgcd" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/joaomgcd/W-gwjD5q7to/unsubscribe.
To unsubscribe from this group and all its topics, send an email to joaomgcd+u...@googlegroups.com.

Mike Kramer

unread,
Feb 16, 2015, 11:53:29 AM2/16/15
to joao...@googlegroups.com, william....@gmail.com
I have been having problems too with continuous listening. It stopped completely, after a reinstall it started working again, but not for long. I cleared the app data, and it was working again. But after a few hours the recognition is getting slower and slower (sometimes a couple of minutes between the command and a toast), and very often it does not listen at all.

João Dias

unread,
Feb 18, 2015, 6:52:36 AM2/18/15
to joao...@googlegroups.com
Hi again. The google now hotword is not related to AutoVoice continuous, so that won't have any interference here.
Also what do you mean by "erase the Google Now information"?
Also, have you tried changing the stream to mute in the AutoVoice app so that it doesn't beep all the time?

Thanks and sorry for the trouble

Mike Kramer

unread,
Feb 18, 2015, 7:17:17 AM2/18/15
to joao...@googlegroups.com
To be honest no idea of whats going on. Without me doing anything its all working fine again. I temporarily tried to go via ok google but that did not work at all, and its not really the way I want to go so it doesn't matter that I could not get it to work. I changed everything I had changed to use ok google back to what I had before after it all started working again. Sorry about this, it sounds strange, but I do not know why it behaved so strange and then decided to work fine again. Its when all of a sudden it stops working, you see how much you got used to voice control, even with all the imperfections, and I am lost when it doesn't work...

João Dias

unread,
Feb 19, 2015, 9:07:56 AM2/19/15
to joao...@googlegroups.com
Can you please try this version and see if it works better regarding the beeping? Thanks!

Mike Kramer

unread,
Feb 23, 2015, 4:16:44 AM2/23/15
to joao...@googlegroups.com
I do not have any beeping any more, but I have another problem. I have autovoice continuous on all the time, but it stops working after a day, even though it is still on in the autovoice settings. If I reboot, it works again.

João Dias

unread,
Feb 23, 2015, 5:03:51 AM2/23/15
to joao...@googlegroups.com
After it stops working can you check what the AutoVoice logs say please? Maybe there's some hint there to what could be wrong. Thanks!

Mike Kramer

unread,
Feb 23, 2015, 5:25:23 AM2/23/15
to joao...@googlegroups.com
I will turn on the logs tonight, and check next time it happens.

Mike Kramer

unread,
Feb 23, 2015, 3:59:32 PM2/23/15
to joao...@googlegroups.com
Tonight when i came home it was not working again. I looked at teh logs, cannot see anything there, but last entry was more than 24 hours ago !
I restarted my tablet, which normally fixes it, but it didnt fix it this time. I had system logs enabled, and sent you that log via email. I deleted the cache and app data, and then entered all my settings again, and its working now. Maybe you can see something in the logs.

This is the first log before the restart (the emailed one is the later one):

Continuous - 2015-02-22 18:17:59.564 - Continuous Service started
Trigger Words - 2015-02-21 19:12:20.962 - Current trigger words:
hi now
Recognition - 2015-02-21 19:12:20.947 - Got commands: Received possible commands (continuous):
hi now
Continuous - 2015-02-21 19:12:20.926 - 1 results from continuous!
Trigger Words - 2015-02-21 19:09:09.577 - Current trigger words:
hi thanks
Recognition - 2015-02-21 19:09:09.554 - Got commands: Received possible commands (continuous):
hi thanks
Continuous - 2015-02-21 19:09:09.539 - 1 results from continuous!
Trigger Words - 2015-02-21 19:08:35.401 - Current trigger words:
hello hello
Recognition - 2015-02-21 19:08:35.387 - Got commands: Received possible commands (continuous):
hello hello
Continuous - 2015-02-21 19:08:35.370 - 1 results from continuous!

Trigger Words - 2015-02-21 19:07:06.632 - Current trigger words:
something is 314
something is real
something is 340

This is not complete but I thought I leave the earlier bits out

João Dias

unread,
Feb 24, 2015, 4:18:26 AM2/24/15
to joao...@googlegroups.com
Thanks. just saw your logs.
Do you have the "Ok Google" always on enabled?

Mike Kramer

unread,
Feb 24, 2015, 5:14:55 AM2/24/15
to joao...@googlegroups.com
In autovoice I have the google now integration enabled normally. In my Android settings I have everything relating to voice control disabled, not to interfere with autovoice continuous. The tablet is wall mounted, and dedicated to autovoice and displaying my cameras only.

João Dias

unread,
Feb 24, 2015, 5:25:32 AM2/24/15
to joao...@googlegroups.com
I see. It seems that something starts to interfere with the microphone at some point and AutoVoice can't hear what you're saying. Do you have any other app installed that could be using the microphone?

Mike Kramer

unread,
Feb 24, 2015, 5:35:20 AM2/24/15
to joao...@googlegroups.com
Not really. As I said, I have very few apps installed, tasker and the autoapps, and 2 camera viewing apps. And I think I have everything with voice disabled. But we had a discussion before, sometimes my autovoice goes 'deaf' for a few seconds, and then listens again. I took another tablet, and installed Cyanogen mod on it, to keep it simple... I did the same there, disabled all voice inputs, and still had autovoice going 'deaf' for a few seconds at the time. I am not sure if this is related, but from what you are saying I have a suspicion it could be

João Dias

unread,
Feb 24, 2015, 5:48:05 AM2/24/15
to joao...@googlegroups.com
When you enable AutoVoice continuous does it show an icon on your task bar saying that it is listening?

Mike Kramer

unread,
Feb 24, 2015, 5:51:01 AM2/24/15
to joao...@googlegroups.com
yes it does

João Dias

unread,
Feb 24, 2015, 5:56:30 AM2/24/15
to joao...@googlegroups.com
On those logs you sent me before, do you know if AutoVoice was listening at the time those logs were generated? I guess there's no way for you to know that right?

Mike Kramer

unread,
Feb 24, 2015, 6:13:39 AM2/24/15
to joao...@googlegroups.com
I tried saying a few things while capturing the log, but no toast came up. So it was in listening mode, but it was 'deaf' if you understand what I mean...

João Dias

unread,
Feb 26, 2015, 10:12:07 AM2/26/15
to joao...@googlegroups.com
Thanks. Sorry, I really cannot reproduce it, I wish I could. I'll keep looking for a solution, thanks
Message has been deleted

andre...@jkd.ro

unread,
Mar 3, 2015, 4:20:18 PM3/3/15
to joao...@googlegroups.com
Hi,
I have exactly the same problems.
1. When I turn on continuous mode - the Media volume is automatically set to min. If I manually turn is louder I start hearing some strange beeps form time to time.
2. The most annoying problem: Autovoice continuous is turning itself off from time to time (I didn't noticed any pattern but in generally in not on more than 1 hour). The icon in the taskbar ramains on even if Autovoice is off.
I use galaxy note4. Tried with both google now on and off (which is running perfectly).

Please help,

João Dias

unread,
Mar 4, 2015, 5:27:57 AM3/4/15
to joao...@googlegroups.com
1. That's why the volume is turned to minimum, so you don't hear the beeps :) Unfortunately there's no way for me to remove the beeps
2. Can you please enable system logs in AutoVOice and then export them when the service stops working? Thanks

Reply all
Reply to author
Forward
0 new messages