How to Create Custom Android Voice Commands with Tasker and AutoVoice

If you’re using a device that runs Jelly Bean or higher, we’ll start by hijacking the Google Now command (since you can still get to the same functions from the Google search box). However, you can modify the following instructions to trigger AutoVoice with any Tasker state:P

Note: If you want to use the Google Now-style launche I’m doing, install Assistant Event for Tasker from the Play Store (this allows you to commandeer the normal Google Now gesture). Otherwise, you can alter the instructions below to create your own unique trigger.P

Create the AutoVoice listening trigger profile:P

  1. In Tasker, under Profiles tap the plus sign to create a new profile.
  2. Select “State.”
  3. Select “Plugin.”
  4. Select “Assistant Event for Tasker.”
  5. Tap the “Edit” button next to “Configuration.” (This will automatically “configure” the plugin, you won’t need to actually edit anything.)
  6. Tap the back arrow at the top left to get to the main page of the app, where you’ll be prompted to create a new task.

Create the AutoVoice trigger task:P

  1. Name it “Listen for Commands.”
  2. Tap the plus sign to add a new Action.
  3. Tap “Plugin.”
  4. Select “AutoVoice Recognize.”
  5. Tap “Edit” next to “Configuration” and tap the checkmark (no changes needed here).
  6. Tap the back arrow at the top left to get back to the main page of the app.

With this in place, you’re ready to start creating custom commands. Now, if this is how you’d like to trigger your custom commands, skip ahead to the sections below for actually doing cool stuff. However, if you want your phone to continuously listen for voice commands without action (and get all Kirk with your Android), follow these instructions instead:P

  1. Create the AutoVoice continuous listening trigger:
  1. Under Profiles tap the plus sign to create a new profile.
  2. Select “State.”
  3. Select “Display.”
  4. Select “Display State.”
  5. Set “Is” to “On.”
  6. Continue actions for creating the AutoVoice trigger task in step 3 above.

This particular implementation will result in your phone only listening for commands when your display is on. You can instruct it to listen when the display is off, but this can already be a huge battery drain as is. I would not advise trying this option

See Full Story on lifehacker.com

Leave a Reply