So in the dialer settings, for answering/ending calls, I've got "using voice commands" checked so that if I have my hands full I can answer an incoming call by saying "answer".
That said, this feature is of little value if the speaker phone isn't also automatically enabled (at least it's of little value unless you have a bluetooth headset on or something).
Is there a way to get the speaker phone to come on with a voice command or, better yet, automatically when I answer a call using a voice command?
fwiw, I'm on a retail variant running the lollipop update.
Thanks!
Related
Hiya, I got a BT800 for Christmas from my lovely wife and am having a hell of a time getting it to activate voice dialling!
Having paired it and chosen to use it as the hands free device, I can use it for phone calls that I start from the phone, but the Exec doesn't do anything when I 'tap' the answer button (one beep) or squeeze it(beep, pause, beep).
I've even just restored the original rom (hard-reset, basic install) and it still doesn't do anything...
Did anyone else have this problem? Is there a stage I'm missing out?
Hope someone can help, I've a nasty feeling it's too late to return it to Amazon...
Might be a daft question, but have you added your voice tags (or re-added after hard reset)?
Thanks for the reply, I was never intending to use voice speed dial (preferring voice command by miles) and so didn't record any tags. Even without any, you should still get the app launching and a message that there aren't any tags recorded. My problem was that I wasn't even getting that.
I can't claim to have solved the problem, but at least I no longer have it! I reinstalled the original O2 ext_rom and did a nice clean "Basic" install then put my customised ext_rom back and reset again. Having paired the headset I was able to launch voice speed dial from it, so went ahead and installed voice command, made the registry change to launch VC from the headset and am laughing.
I wish I knew what had caused the problem so I could avoid doing it again! I suspect that it was an attempt to restore my bluetooth registry settings on a rebuild that was the cause... Certainly I didn't try to set it up automatically the second time round and it *did* work, but there are too many variables to be sure.
HTH someone!
The Universal has no NATIVE support for Voice Dial using Voice Command. You have to do the following so it will work via VOICE COMMAND as it has to bypass the Installed Vocie software:
Install Voice Command to the default location.
Fire up a registry editor
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Modify the string marked "path" from the default \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
This should now launch Voice Command
Maybe you made a mistake like missing a letter?
If you have done the above and it still doesnt work, then i'm just as lost as you are
sorry, browser problem, message was posted twice
I'm using the BT800 with my Qtek 9000 (Original ROM) and don't have any problems with voice dialing. After pressing the button on the Jabra within a second or 2 the voice dialing application is started, I hear a start sound, speak the name and it automatically starts dialing.
I have installed the latest BT800 firmware (becaus of the international dialing bug) and had not tested this functionality with the original firmware. Which firmware are you using?
MvanIperen said:
I'm using the BT800 with my Qtek 9000 (Original ROM) and don't have any problems with voice dialing. After pressing the button on the Jabra within a second or 2 the voice dialing application is started, I hear a start sound, speak the name and it automatically starts dialing.
I have installed the latest BT800 firmware (becaus of the international dialing bug) and had not tested this functionality with the original firmware. Which firmware are you using?
Click to expand...
Click to collapse
Which button do you have to press to activate the voice dial? The left or the right button under the LCD? Is it Tap or Hold, the button i mean?
@jorgee: 1st post - thanks, that's what I meant earlier when I said I'd done the reg fix and it all worked
2nd post - to activate voice dialling on a UK O2 Exec, you press the 2nd button from the left on the front of the device - next to the camera button.
@ MvanIperen, I'm using the latest BT800 firmware too, when I did a couple of rebuilds, the problem went away and it now behaves as you describe.
@ all, thanks for the replies! It was just me after all! Mental note: Mess with the registry at your peril!
[quote="this_mike
2nd post - to activate voice dialling on a UK O2 Exec, you press the 2nd button from the left on the front of the device - next to the camera button.
[/quote]
I meant is there anyway to activate voice dial from the headset? Can i only activate it by pressing the voice command button? I mean lets say my phone's in my drawer and i have the BT800, do i have to pull out the phone to be able to use the voice dial?
Jorgee said:
I meant is there anyway to activate voice dial from the headset? Can i only activate it by pressing the voice command button? I mean lets say my phone's in my drawer and i have the BT800, do i have to pull out the phone to be able to use the voice dial?
Click to expand...
Click to collapse
Maybe I misunderstand what you're asking.
You posted the registry change to make this work higher up the page.
Pressing the answer button on the headset does fire up Voice Command but only if the display is open or in portrait mode. If it's closed in your pocket protecting the screen then it won't work
I've never installed voice command, i was talking about the built in voice dial application. If the QTEK is in my pocket, and i want to call someone, which button on the headset/BT800 do i press to activate voice dial? And is it push or push and hold? Do i ghet any kind of audible warning telling me i can start speaking the voice tag?
I hope this time i am a bit clearer, sorry for the previous confusing post.
Jorgee said:
I've never installed voice command, i was talking about the built in voice dial application. If the QTEK is in my pocket, and i want to call someone, which button on the headset/BT800 do i press to activate voice dial? And is it push or push and hold? Do i ghet any kind of audible warning telling me i can start speaking the voice tag?
I hope this time i am a bit clearer, sorry for the previous confusing post.
Click to expand...
Click to collapse
On the BT800:
- To activate voice dialling (whether using MS Voice Command or the 'standard' voice dialling app) using a BT800 headset, press briefly the button nearest the headset microphone.
- To redial from the headset the last number dialled, press and HOLD the button nearest the headset microphone.
This works for me whatever situation the Exec is in: open, closed, portrait, landscape. I'm using the default voice-dialling software, not the MS one. Hope this helps.
Thanks SiliconS,
That was the answer i was looking for, sorry i had to bother you guys instead of reading the manual as my manual is in Spanish and i am only a beginner-intermediate level reader.
Again THANKS!!!! Very appreciated
Are any of you folks running WM2003SE? See, I was able to make that registry change and do a soft reset and have Voice Command working through the BT headset on my old machine, but it was running WM2003 (not the second edition version). From what I have read, SE doesn't seem to like that registry change, as when you make it, all that will happen is the connection opens when you tap the button on the HS, but the ability to use VC is not there.
I know there must be some way to do this. Any opinions or suggestions would be fab!
Thanks much!
Hi.
I have spent months trying replacement VC files and cabs in hope to get consistant Call notifications to various BT ear pieces with no resolution.
Has anyone been able to enable VCs call announcements to reach any BT ear piece.
THX.
Do you mean that your ear piece tells you when a call is coming in? If so I use the Voicecommand cab that's in the add ons for vp36's ROM: http://forum.xda-developers.com/showthread.php?t=334946&highlight=vp3G.
I also use the little Jabra ear piece: http://www.jabra.com/Sites/Jabra/NA-US/products/Pages/JabraBT8040.aspx
I can initiate Voice Command with it and the ear piece tells me when calls are coming in.
If you are expecting VoiceCommand to tell you the name of who is calling in that you recorded, I don't think it actually does that.
Just read the specs for 1.6 and it looks like it does include what you want. We'll see if we can find a cab for it. If you find it post the link here and I will do the same.
The bottom line is this..You need a headset with the AD2P profile like the one linked above. You also need to install the .cab linked and enable it once installed.
I use the Jabra BT8010 myself..If you don't have a headset with AD2P its not gonna happen so no need to go further.
Now if you have all this like I do then yes notifications with come through the headset. If you want incoming calls announced then goto Start/Settings/Voice Command then highlight phone and click options...check off 'Announce incoming calls' then press ok.
So when I'm driving in my car I can tell if I got a email or txt msg just by the tone I have set for each. If I turn on announce calls then it will say what I have in my contacts.
i have gotten voice command to work thru the bluetooth on the atom life with the jawbone, even to call announce. problem is whenever i turn up the volume enough to hear things, voice dialing produces horrible feedback (squealing noise) and the pone does not recognize the command,
any fixes people know of?
thanks
Hope for the reply. Met the same problem.
fzman said:
i have gotten voice command to work thru the bluetooth on the atom life with the jawbone, even to call announce. problem is whenever i turn up the volume enough to hear things, voice dialing produces horrible feedback (squealing noise) and the pone does not recognize the command,
any fixes people know of?
thanks
Click to expand...
Click to collapse
How did you get the MS voice command to work through the BT headset? I can't seem to get it working is there a registry hack required?
This isn't a complaint, just a bug report.
System: Sprint TP2 (Rhod400)
Build: [MJG]Rhod.2.2Froyo.082610 w/8-27 sound patch (modules-2.6.27.46-01149-g74aec59.tar and update zImage)
Install Type: Clean Install
Problem: Voice Search does not initialize the mic.
To recreate:
1) Boot into Android.
2) Start Voice Search.
Voice search will fail as no sound will be recorded. However, voice search itself *does work* if you start it with the mic active.
To see voice search working:
1) Boot into Andorid.
2) Make a phone call.
3) End the call.
4) Immediately start voice search.
5) Voice search will record the sound (you will see the mic icon flash white) and run the search as expected.
Note: Voice search closes the mic when finished, so if you attempt to immediately use it a second time, it will fail.
I hadn't seen this noted anywhere and as such wanted to mention it since the sound system is now in a much better state.
I think the same thing happened to me, unless I dont know how to use the program but i'm sure i do.
Its called talking tom cat. it records your voice then replays it in high pitch kitty talk. I pressed record, spoke into the mouth piece both normally and very loud. It didn't playback anything.
gamescan said:
This isn't a complaint, just a bug report.
System: Sprint TP2 (Rhod400)
Build: [MJG]Rhod.2.2Froyo.082610 w/8-27 sound patch (modules-2.6.27.46-01149-g74aec59.tar and update zImage)
Install Type: Clean Install
Problem: Voice Search does not initialize the mic.
To recreate:
1) Boot into Android.
2) Start Voice Search.
Voice search will fail as no sound will be recorded. However, voice search itself *does work* if you start it with the mic active.
To see voice search working:
1) Boot into Andorid.
2) Make a phone call.
3) End the call.
4) Immediately start voice search.
5) Voice search will record the sound (you will see the mic icon flash white) and run the search as expected.
Note: Voice search closes the mic when finished, so if you attempt to immediately use it a second time, it will fail.
I hadn't seen this noted anywhere and as such wanted to mention it since the sound system is now in a much better state.
Click to expand...
Click to collapse
This works for me fine, as long as the first thing I do when I turn my phone on, and make a phone call. After that it just work.
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.