It's in the plugin actions set in tasker.
Depends, if you want ;-) I don't. But, I like my music button on my headset the way it is. I'm suggesting tasker > action > AutoVoice Recognized > headset controls > (Use Headset/Use If Last) allows voice recognition through Bluetooth device
* note: that's my default task action on a BT primary button press ;-)
Is higher the volume of the microphone bluetooth radio? More higher than the volume of the phone?
I think I understand what you're saying, and I think you're referring to a microphones sensitivity level. That depends based on your BT device class, which varies greatly. Usually it's anywhere within -4dB, 0dB, and +20dB.
A -4dB device sounds like the user is down the far end of a hallway, whereas a +20dB almost sounds like someone's inside your head between your ears. Some BT radios can change microphone sensitivity levels, but it's device class determines it's range of viable performance.
A1: AutoVoice Recognize [ Configuration:
Voice command with headset Package:com.joaomgcd.autovoice Name:AutoVoice Recognize Timeout (Seconds):0 ]
It's found in the action > plugin > AutoVoice Recognized Command
You need to use a recognized action.
No worries :-) most don't know that. AutoVoice doesn't specifically imply it either from what I recall.
One,
I tried profile, status (connected Bluetooth) and task input and output. No works well. It works ok if input / output / input. Bluetooth connected is not event. Is state.
Yeah, that won't work. As I mentioned, you want BT connected to activate a profile name context for use in reference within the task action flow. The action flow of the launch task which initiates the voice prompt should activate either a prompt using headset recognition (if the profile referenced is active) or a voice prompt without headset recognition if that profile active context is not found.
Two,
"On" enabled, I can not listen music,... Alpine Radio CD / screen: "NO NAME". Only "NO NAME".
Ah. Then deactivate this after whatever response desired is supplied. You could also check if %MTRACK is set, pause, route audio, wait till say action completes, route audio back, and resume play within an action flow if you desired.
Hope this helps.
What is the description of the launch task used in your lock screen widgetlocker?
Here's mine, which details which prompt to initiate. This is why you need:
AutoVoice Recognition (5)
A1: If [ %PACTIVE ~R Caller Recording Disable ]
A2: System Volume [ Level:7 Display:Off Sound:Off ]
A3: Media Volume [ Level:15 Display:Off Sound:Off ]
A4: BT Voice Volume [ Level:15 Display:Off Sound:Off ]
A5: AutoVoice Recognize [ Configuration:Voice command with headset Package:com.joaomgcd.autovoice Name:AutoVoice Recognize Timeout (Seconds):0 Continue Task After Error:On ] If [ %PACTIVE ~R Caller Recording Disable ]
A6: Vibrate [ Time:200 ] If [ %SILENT ~ vibrate ]
A7: Else
A8: AutoVoice Recognize [ Configuration:Voice command without headset Package:com.joaomgcd.autovoice Name:AutoVoice Recognize Timeout (Seconds):0 Continue Task After Error:On ]
A9: End If
The profile 'Caller Recording Disable' is active whenever a BT connection is present.
As result, when this task is run a voice prompt using BT recognition appears if a device is connected. Otherwise, a voice prompt for phone recognition is used.
I think the problem here, is you haven't constructed a method dynamically that allows the desired prompt to appear. Tasker needs to know if a BT device is connected and change the actions as result.