I'm running version 4.4, not rooted, Moto x. Utilizing Tasker, what is the easiest way to have the touchless control prompt "ok google now" directly initiate/bring up the Utter voice command app to it's listening state? I can accomplish this no problem with the screen on and unlocked, but I want the ability to also launch it with the screen off/inactive. I am most familiar with utter but will be fine using any voice command app if necessary. I just want to be able to utilize UItter voice command capabilities without it always being in a permanent listening state, which really drains my phone's battery life. Thanks for any suggestions!
I am also interested in this. The following thread should give you some leads:
http://forum.xda-developers.com/moto-x/general/moto-x-offline-recognition-solved-t2571466
Utter
masterfisher166 said:
I'm running version 4.4, not rooted, Moto x. Utilizing Tasker, what is the easiest way to have the touchless control prompt "ok google now" directly initiate/bring up the Utter voice command app to it's listening state? I can accomplish this no problem with the screen on and unlocked, but I want the ability to also launch it with the screen off/inactive. I am most familiar with utter but will be fine using any voice command app if necessary. I just want to be able to utilize UItter voice command capabilities without it always being in a permanent listening state, which really drains my phone's battery life. Thanks for any suggestions!
Click to expand...
Click to collapse
I use the Ok Google now trigger intent xposed module and in tasker use it to launch the utter! Shortcut available from the playstore so that way I have always listening capability without the battery drain that permanent recognition from utter brings and it works perfectly everytime, the alternative is to use touchless controls together with auto voice recognise within tasker and get the Google now api xposed module so that you're still using Google now but tasker tasks can be implemented by voice in Google now, hope that helps although you need to be rooted which I have only just reread your comment to see that you are not
Without root, your options are a bit limited. Utter! Has a direct shortcut to launch its voice recognizer? If so, you can say "OK, Google now, open (utter! shortcut name) app" Kinda awkward, but it should work.
Sent from my XT1060 using XDA Premium 4 mobile app
<br />
I use the Ok Google now trigger intent xposed module and in tasker use it to launch the utter! Shortcut available from the playstore so that way I have always listening capability without the battery drain that permanent recognition from utter brings and it works perfectly everytime, the alternative is to use touchless controls together with auto voice recognise within tasker and get the Google now api xposed module so that you're still using Google now but tasker tasks can be implemented by voice in Google now, hope that helps although you need to be rooted which I have only just reread your comment to see that you are not<br/>
Can you elaborate on this? I'm not a big Tasker user.
Sent from my XT1053 using Tapatalk
Touchless utter
overthatscreen said:
<br />
I use the Ok Google now trigger intent xposed module and in tasker use it to launch the utter! Shortcut available from the playstore so that way I have always listening capability without the battery drain that permanent recognition from utter brings and it works perfectly everytime, the alternative is to use touchless controls together with auto voice recognise within tasker and get the Google now api xposed module so that you're still using Google now but tasker tasks can be implemented by voice in Google now, hope that helps although you need to be rooted which I have only just reread your comment to see that you are not<br/>
Can you elaborate on this? I'm not a big Tasker user.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Download and install utter quick launch from the playstore and the okgooglenowtriggerintent module from xposed, once you have activated it and rebooted in xposed framework open tasker and create a new profile, hit event then in the popup start to type intent and send intent will appear, hit that and in the action section type the following:
com.hawkjm.okgooglenowtriggerintent.AUDIO_TRIGGER
Press back and new task popup will appear, choose application and select utter quick launch, make sure tasker is running and the new profile is active in tasker and keep pressing back until tasker exits, now everytime you say ok Google now utter will listen instead of Google now, you might want to customise the response from your command in utter, I changed mine simply to yes each time I activate utter and bear in mind that it has nothing to do with the wake up command settings in utter, I hope that all makes sense
If it's the tasker tasks in Google now that you are interested in then download autovoice from the playstore and the Google search api from the xposed framework application downloads section and activate it and reboot,
Open autovoice and scroll to the bottom and make sure that Google search api is enabled then open the Google search api app that you downloaded (should now be an icon) swipe across to the right and make sure autovoice is there, if not then reboot, if so open tasker, create a profile, select state, plugin, autovoice recognised then next to configuration hit the edit button, scroll to command filter and type the Phrase that you want to be recognised for example Toggle bluetooth, back out of it and hit the tick, then select the task that you want to perform (the possibilities are endless) and back out of tasker until it closes then try out your command, create new profiles for each autovoice command that you want to execute,
Google search will try and search for whatever you say even though it will execute your task, if you're fine with that then leave it as it is, if you want Google search to close after executing certain commands then under each task that you create press plus, select if and make the top line look like this:
%avsource ~ googlenow
Then hit back, hot plus and type kill application and select that option, search for google search and tick use root,
Hit back again and hit plus and type end if and select it and then hit back until tasker exits. Now whenever you say that particular command Google now will execute it and then return to where you were previously, if you don't want to do that for each task simply create a profile for recognising the Phrase homepage and have it run the task homepage
mpd81 said:
Download and install utter quick launch from the playstore and the okgooglenowtriggerintent module from xposed, once you have activated it and rebooted in xposed framework open tasker and create a new profile, hit event then in the popup start to type intent and send intent will appear, hit that and in the action section type the following:
com.hawkjm.okgooglenowtriggerintent.AUDIO_TRIGGER
Press back and new task popup will appear, choose application and select utter quick launch, make sure tasker is running and the new profile is active in tasker and keep pressing back until tasker exits, now everytime you say ok Google now utter will listen instead of Google now, you might want to customise the response from your command in utter, I changed mine simply to yes each time I activate utter and bear in mind that it has nothing to do with the wake up command settings in utter, I hope that all makes sense
If it's the tasker tasks in Google now that you are interested in then download autovoice from the playstore and the Google search api from the xposed framework application downloads section and activate it and reboot,
Open autovoice and scroll to the bottom and make sure that Google search api is enabled then open the Google search api app that you downloaded (should now be an icon) swipe across to the right and make sure autovoice is there, if not then reboot, if so open tasker, create a profile, select state, plugin, autovoice recognised then next to configuration hit the edit button, scroll to command filter and type the Phrase that you want to be recognised for example Toggle bluetooth, back out of it and hit the tick, then select the task that you want to perform (the possibilities are endless) and back out of tasker until it closes then try out your command, create new profiles for each autovoice command that you want to execute,
Google search will try and search for whatever you say even though it will execute your task, if you're fine with that then leave it as it is, if you want Google search to close after executing certain commands then under each task that you create press plus, select if and make the top line look like this:
%avsource ~ googlenow
Then hit back, hot plus and type kill application and select that option, search for google search and tick use root,
Hit back again and hit plus and type end if and select it and then hit back until tasker exits. Now whenever you say that particular command Google now will execute it and then return to where you were previously, if you don't want to do that for each task simply create a profile for recognising the Phrase homepage and have it run the task homepage
Click to expand...
Click to collapse
Great topic! Learning more about integrating Google Now and AutoVoice, but i have some doubts yet
I have a MotoX and do not want to leave the continuous mode autovoice on because MotoX has dedicated processor for voice recognition, intend
use "OK Google Now" to enable the continuous mode autovoice.
Could be accomplished?
"OK NOW GOOGLE", "MOTO X" "TURN ON TV"
^MotoX feature
^Enable AutoVoice
^Action
dont like Utter!...
Easily acomplished
klucilla said:
Great topic! Learning more about integrating Google Now and AutoVoice, but i have some doubts yet
I have a MotoX and do not want to leave the continuous mode autovoice on because MotoX has dedicated processor for voice recognition, intend
use "OK Google Now" to enable the continuous mode autovoice.
Could be accomplished?
"OK NOW GOOGLE", "MOTO X" "TURN ON TV"
^MotoX feature
^Enable AutoVoice
^Action
dont like Utter!...
Click to expand...
Click to collapse
You can accomplish it a couple of ways, if you use the okgooglenowintent xposed module as described above and instead of choosing utter quick launch you choose autovoice recognise as your task and give your commands that way (using this xposed module doesn't use autovoice permanent recognition, it uses the same as the touchless control does its just intercepting and switching touchless control for whatever app you replace it with so it doesn't drain any battery)
Or you can get the Google search api xposed module and set it up like I have above so that all of your tasker tasks are accomplished using Google now, so for example at screen off "OK Google Now turn on the tv" and providing you have the tasker task setup using the autovoice recognised profile or will perform the task for you
Just to clarify, using autovoice recognised under profile in tasker does not drain the battery as it's not the same thing as continuous listening mode in autovoice and you are using the moto x dedicated core for listening for your ok Google now command
Here it is an easy way to post to Twitter using Tasker and AutoVoice
Foreplay:
1. Go to IFTTT's web page and sign up.
2. Download Do Note from the Play Store.
3. Choose the Recipe : Post a quick Tweet.
4. Download Autovoice and AutoInput from the Play Store.
You are ready to go!
Profile:
State>Plugin>Autovoice Recognize. Check Event Behaviour. Command Filter; " post (?<message>.+) to Twitter" Check Regex. (Creating a variable)
Task:
1. Say> Text: Tweeting %message. Ok? (It allows you to check if everything is going according to the plan.)
2. AutoVoice Recognize Prompt Text: %message. Matching options: Check Don't Trigger Conditions.( AutoVoice will pop up. You must check if the message is ok and say yes.)
3. If Condition: %avcomm ~yes ( Set a condition because if the message is wrong the task will not be fired.)
4. Launch apps> DO NOTE
5. Wait 2 seconds
6. Type %message
7. Wait 8 seconds
8. AutoInput> Action> Easy set up. Go to DO NOTE , click on ADD on the notification bar, go back to DO Note and click on the send button. Then click on the Accept button of the notification and go back to AutoInput. Select the button you pressed and accept the settings. (This will make AutoInput click on the send button.)
9. End if
If Type does not work for you, you can use Set Clipboard with the text %message and paste it using AutoInput: Actions>Paste>Text> %message. This will make AutoInput paste your tweet on the focus.
Have fun!
I'm new to Tasker and trying to set up a profile that will start my radar detector app when connected to my car's BT, and one that will exit the app when BT disconnects.
I've been successful in creating the profiles that are triggered by the BT connect and disconnect. I've also created the task to start my app on the BT connect. However, I am stuck on how to exit the app when BT disconnects.
The app in question, Esccort Live, can be exited by pressing BACK and clicking on the "OK" prompt. To accomplish this, I trying to use AutoInput to do the following:
1. Press BACK
2. Look for "OK"
3. Click on "OK"
Seems simple, but I can't figure out how to do these three steps.
Also, when using a profile that is triggered by a BT connect or disconnect, is there a way to clear this state once the profile's tasks have been executed?
Any help would be most appreciated.
Jack
Some thoughts for you. You may need to put a pause (e.g. wait 1 sec) since auto input can respond faster than the screen can update. Or flash an alert between the autoinput commands. If the Escort Live app isn't in the foreground when you are trying to make an action on it, try opening recent apps using AutoInput, then reselect the app.
BTW, I'm not sure what you are asking to reset on the BT connect/disconnect. Maybe what you want is to use a variable that is set/unset on connect/disconnect and then that variable triggers your task.
How do I create a profile in Tasker that will start a program and then a process within that program? I would like to start a program, then another program and then a process within that program such as: run PerkTv then run Repititouch and then load a profile/process then run it.
Unless the app has an intent you can call to initiate the "process", you probably need to script input touches. Either by:
1) using "run script actions" with the command "input tap X Y". The X Y are the coordinates of the tap location. Turn "pointer location" on in settings -> developer options to find them (requires root)
or
2) using the AutoInput plugin (doesn't require root but does require access to adb)
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Been trying to Google a solution but in vein.
I want my Flic button to trigger a task.
I make a Profile in Tasker, choose event -> Plugin -> Flic and select my button and behaviour.
To this event I choose one of my tasks.
So far so good. The task executes when I click my Flic button. Great!
After a while, leaving the room with my phone or rebooting the phone, nothing happens when I'm back and click my Flic! I'll then have to open Tasker, edit my Flic-event under profiles and save the Flic behavior again for it to execute when I click my Flic.
Why does it disconnect like this? It only works just after creating the event.
Please help. Desperate!
Have you asked the plug-in developer for help? This sounds like it's in their court. Looking at the Tasker run log might give some insight, but my guess is it's at a lower level than that.
Reading through the FLIC community support it looks like there are reports of hit or miss and maybe only a double click action will work with Tasker.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Thanks for your reply ktmom!
I found a workaround for my problem.
I simply put my task as a shortcut (instead of a widget/task) on my homescreen. I can then assign my task within Flic app by choosing "Launch shortcut" under "Phone control" in Flic app...
However I'm still bothered by that previous mentioned problem.
Things are sort of working now !
Good workaround idea!
Maybe one day they'll fix the issue so we don't have to keep an extra shortcut to make it work!