AutoVoice Autovoice Recognized not recognizing

Discussion in 'AutoApps' started by Durntdude, Jul 29, 2016.

  1. Durntdude

    Durntdude New Member

    Joined:
    Nov 19, 2015
    Messages:
    8
    Likes Received:
    0
    Off the bat, this has been an ongoing issues for a while and I don't recall exactly when it started.

    Scenario:
    1) Set up a new task with just Autovoice Recognized (no settings changes)
    2) click the start button and the command will timeout in approximately 2 seconds

    If I start talking instantly, or am talking when it starts the recognizing window, it will stay active until I stop talking (so this works). If I hide the dialog and set a timeout, it will work properly. If I just have autovoice recognized don't start talking within 1-2 seconds then it will timeout.

    Any ideas?

    EDIT: I have gone in to autovoice->advanced->no command matched timeout and changed it to 6 and 10 seconds but it still times out in 2 seconds or so
     
    Last edited: Jul 29, 2016
  2. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,479
    Likes Received:
    806
    Does the same thing happen with the "Get Voice" action in Tasker?
     
  3. Durntdude

    Durntdude New Member

    Joined:
    Nov 19, 2015
    Messages:
    8
    Likes Received:
    0
    The Get Voice action in tasker pulls up the voice recognition for about 6 seconds (which is odd, the timeout is set for 30 seconds and the autovoice no matched is set to 10 seconds)
     
  4. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,479
    Likes Received:
    806
    Thank you. Can you please tell me what version of the Google App you have installed? Thanks!
     
  5. Durntdude

    Durntdude New Member

    Joined:
    Nov 19, 2015
    Messages:
    8
    Likes Received:
    0
    Sorry for the late response (been hectic here),
    Google App version 6.1.28.16.arm
     
  6. Durntdude

    Durntdude New Member

    Joined:
    Nov 19, 2015
    Messages:
    8
    Likes Received:
    0
    Actually, I think I just figured out the issue, and it is silly. If I have media volume maxed (at 15), the timeout is 1-2 seconds. If I mute the Media volume, it times out in about 5-6 seconds (reasonable). I think that the beep to let you know that voice recognition is active is triggering as a voice response on the voice recognized command

    EDIT: That being said, is Autovoice timeout limited to the Google App timeout? Also is there a way to adjust the recognition about 1/2 sec later so the beep doesn't trigger failed recognize?
     
  7. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,479
    Likes Received:
    806
    Oh, that's weird, yeah :/

    Unfortunately no, I can't postpone recognition until after the beep, sorry!
     
  8. Durntdude

    Durntdude New Member

    Joined:
    Nov 19, 2015
    Messages:
    8
    Likes Received:
    0
    That's fine, I'll just do a beep, mute music, recognize, music volume up again
     

Share This Page