BT Button and AutoVoice

[karr...@gmail.com]

Hi All,

I was glad to run across Autovoice for home automation. I think I've gotten the command chaining, but for the life of me can't get it to start voice recognition with BT device button. I don't see much discussion about this here, so thought I would ask.

I'm using a little Jabra EXTREME2 and it has a main button that reports "Connected" when pressed, but does not seem to trigger anything with AutoVoice (according to the logs). I've checked my Android device for music apps that may have grabbed it and disabled those. I have AutoVoice Recognized as the only Action in a new Profile. Are there models of BT headsets that work well with AutoVoice?

TK

[João Dias]

Can you initate calls with that bluetooth headset? That's the button that usually works with AutoVoice.

--
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/groups/opt_out.

[Caine the King]

I believe so, though I've never used it for that. The thing only has one button, but it only responds with "Connected" when I press it. Doesn't seem to trigger AutoVoice. If there is another BT device that is known to work, I could get that, but I wanted to make sure it's not something else before buying another headset.

[João Dias]

What if you long-press that button?

If you manage to make phone calls with that headset, then it should also work with AutoVoice.

You just have to clear the defaults for the dialer app, so Android will ask you what app you want to use.

[Caine the King]

I'm actually setting all this up on a non-phone Android tablet, so it doesn't make calls. But getting it to the point of Android asking what app to use is useful, it should, shouldn't it? I'll fiddle with that. I don't know that the button press is making it to Android at all.

[João Dias]

Yeah it should... Let me know what you can find.

[Caine the King]

Bought another BT headset, a Plantronics Marque 2 M165 and it also does not trigger Autovoice, either with a single button press, two presses or a 2 second press. The Autovoice log shows that it sees a BT device and all, but something isn't working. This is on a stock ROM Transformer tablet, so I'm not sure what's going on.

Writing this as I try things. I went into Voice Search to check the settings there and saw that Google Now was disabled, so I went through the initialization and update to enable it.

Woo ha, now it pops up with the choice between Autovoice or Google Now, so this is progress.

[João Dias]

So if you select AutoVoice, what happens?

[Caine the King]

It works! For whatever reason, Google Now wasn't enabled on my tablet (I've never used it before, so maybe it came in on a recent upgrade and was disabled by default), so I had to go into Voice Search settings to get to where to enable it. Then I selected AutoVoice and Always and now it's immediately picking up on single tap for Autovoice and working through the headset. Theory, without being a dev, that maybe it took a second app competing for BT headset touches to trigger the choice of app. I haven't tried the process on my phone, but I'll maybe try to capture it better there, if it turns out to be the same fix.

Nice. :)

[João Dias]

That isn't really a good reason for that to happen, but maybe that's just the way it works. :)

Can you do a step by step on how you made it work? I have a customer with a similar problem and maybe 

this will fix it for him too. :)

Glad you got it working!

João

[Caine the King]

Sure, will do. There never is a good reason for computers to do half the things they do but they do. :)

[Caine the King]

As far as I can tell, if a long-hold on a BT headset (which was the first Autovoice BT Pressed button on two handsets I have) results in no response, I found this works, sort of. In testing between a tablet and a Samsung Galaxy II phone, it was enough to force the device to prompt for the default app to use for the long-press on the headset. 

- Go to Apps and flick over to All

- Click on Google Search (this was the only app that I found that had grabbed the BT headset, though your device might have music apps, etc to check)

- Make sure it's not Disabled and scroll down to click Clear defaults.

- Clear defaults in this way on any other apps that might use the BT headset.

If you've cleared the default app for any and all apps that might be grabbing it and are still not getting response from Autovoice, try installing the free Bluetooth Launch app (in the Play store) for the sole purpose of giving the device one other app to have to choose from. On my phone, that kicked in the screen for deciding which app to open when the long-press is detected.

Once that app choice window comes up, select the always checkbox and Autovoice (if on a phone) or Autovoice and then click Always (if using a tablet). Now you can uninstall Bluetooth Launch if you like (it isn't needed for this to work from now on).

This may be tricky to trigger the default app choice, but after managing to set Autovoice as the default app for long press on the BT headset, my BT Recognize started working. Just getting to that point is tricky. If you have Titanium Backup and freeze apps through it, make sure Voice Search is not frozen also. I hope this helps others.

TK

[João Dias]

Great.

Thanks for the step-by-step! Hope this helps someone.

João

[scinta...@gmail.com]

I'm having the same problem with a "Just wireless Blue bt-15k2" and trying to tie this into my htc evo v (cyanogenmod) and galaxy tab (cyanogenmod). I can pull audio through the headset, but the buttons want to default through the voice dialer.

I already have autovoice working naturally through the phone and have a shortcut widget tied to a 'get voice' task on my homescreen.

A short press on button 1 gives me a beep and pulls the voice dialer, the medium press turns it off, long press pairs. For Button 2, It cycles through default volume levels on short and redials my previous contact for long press.

Anyways, i tried going through Caine's walkthrough, search was enabled and wasn't tied to anything, and I did the same with the voice dialer app, no defaults to clear. Still, I wiped out the cashe on both apps and i'm pretty much back to where I started.

I also tried using Bluetooth Launch to reset relationship between the button press and the phone, but i'm not getting any results.

Finally, the in-app options for tasker and autovoice arn't changing the situation either.

Also, in any of these situations -- even disabling the voicedialer app, button 2 always redials the previous number.

[João Dias]

Very sorry, but I'm afraid I can be of limited help here. I only have 1 bluetooth headset to test this on, so I don't have much chance to debug stuff.

On this one, I think the community will be of much more help then me with their findings.

Sorry!

[naydee....@gmail.com]

Seems your voice dialer app is holding onto the single tap. You can find the phone app and use the clear default button in order to get this to work. the only drawback of using the single click is that you cannot make phone calls from your device as even when you go into your phone book to make calls it won't launch auto voice. This happen to me on my Motorola RAZR

[Tony Scinta III]

I don't know why its working now but wasn't before, but I disabled Voice Dialer and I was finally given a choice of how to handle my bluetooth button.

[samuelr...@gmail.com]

I maybe completely mistaken, but I think that autovoice fails to recognize that a command has been sent via bluetooth without a bluetooth activation by media button profile with an entry task that points to the plugin...

I set up an extensive set of profiles and linked them to a zoom activation of autovoice by widget button press...

each time I press the widget button I can use autovoice and the appropriate action is triggered with no difficulty...

however without an activation profile in tasker a though autovoice collects data from the button press it is not sent on for action by tasker...

for me this has basically been the irritation of training myself to remember which button to push on the bluetooth... sounds like it has been a much greater issue to you...

[bboisso...@gmail.com]

Has anyone tried the Martian watch and autovoice yet? I'm considering buying one. As far as I can tell, the watch works like a headset so this thread should be appropriate. It would be great to hear from someone with first hand experience though.

[djwyl...@gmail.com]

On Friday, December 20, 2013 11:00:08 AM UTC-6, bboisso...@gmail.com wrote:
> Has anyone tried the Martian watch and autovoice yet? I'm considering buying one. As far as I can tell, the watch works like a headset so this thread should be appropriate. It would be great to hear from someone with first hand experience though.

Not yet everyones waiting for apps to bridge them