Upgraded to the latest O2 Rom but cannot hear my Microsoft Voice Command voice after saying something after the beep.
Have turned the volume up. Voice command still works but not voice prompts. Any ideas?
S
happened to me, i just reinstalled the app and it worked fine.
Related
I'm fed up! currently using an Ericsson HBH-662 with it, and it's crap!!! I can only use the headset to activate the voice command once. Clicking the headset button does not release the channel. Consequently when I try and start MS Voice again I just get a dull click in the ericsson earpiece and it will not activate the headset.
Can anyone recommend a headset that is working well with the voice command hack.
thanks.
Is MS Upgrading Voice Command
I had exactly the same problem, I followed the instructions to get MS Voice Command to activate via the headset, then I couldn't disconnect. So I gave up.
I'm waiting for MS to release an upgrade that works properly with BT
It is a problem with VC not the headset. Note that VC isn't designed to do what we are trying. It requires a reg hack to even implement it. Hopefully it'll change, but a new headset likely won't help.
I recently upgraded to the new 2.24 ROM. I reinstalled all my applicaitons, and everything is working just fine with one exceptions. When I activesync my device, MS Voice Command locks up and won't respond. I'm using a Nokia BH-800 headset. If I charge the phone on the AC charger, I don't have a problem. I tried turing the headset off and turning off bluetooth on the phone, but the only recourse is a soft reset. When MS Voice Command is locked up, I can still receive calls through the headset and everything else operates normally. I have tried to uninstall and reinstall MS Voice Command, but the problem persists. Can someone offer a solution for this?
Hey, i just got a bluetooth headset. There is a phone button, that if you push it you can say whoever you want to call and it calls them (or is supposed to), is there any way that i can have this button work with Voice Command 1.5 instead of the phone default thing? because it works a lot better, and i have to program the voices in for the phone default program.
Thanks in advance.
I don't think it'll work with VC 1.5, but MS has just released version 1.6, which claims to support voice dial -- you can get it from Handango.
After all the problems with Voice Command 1.6 and BT headsets I had with the Trinity and WM5, I just got an unexpected bonus.
Last night I decided to install mUn's TE of WM6.
I set up TomTom and Mobile Device Center 6.1 etc.
This morning I thought I might just try Voice Command. So I installed the UK 1.6 version, paired my headset (a Motorola H500) and changed the default mapping for "Button 1" back to the way I like it (CommManager).
Lo and behold pressing the BT headset button activates Voice Command. And it even appears to be working through the headset mic.
I put my phone face down 10 feet away and whispered a command which worked!
hoorah.
I hope it keeps working now ;-)
I got the Epic 4G on the 31st, but out of the box I can't seem to get voice dial or voice search working. I'll click on voice dial and it will say "listening" but it doesn't really hear anything. Eventually, it just times out and says "try again". The same goes for voice search. It prompts me with "Speak now" but eventually times out and says "No Speech Heard". It's as if the mic isn't working. But I don't think there's anything wrong with the mic because I can have phone conversations without any problems. So, I don't think it's a hardware problem. It seems like this is some kind of bug in the software. I don't see any settings for these apps that I can modify. Anyone else having the same problem? Any suggestions for fixing?
Nevermind
I seem to have figured out the problem. If I turn off my bluetooth headset, the voice search and voice dial work. Apparently, it cuts off the mic on the phone when a headset is paired. I'm a little disappointed because Voice Command on my windows mobile devices didn't have this problem. If I initiated voice command on the phone, the mic on the phone would still work. If I initiated voice command from my headset, it enabled the mic on the headset.
I see no options in Android to initiate voice search or voice dial from the headset. Since I normally have a headset paired at all times, I guess I can't use these apps. Bummer.
Coming from winmo, I have to say that the only thing I miss and the only thing that winmo did better than android is voice dial. Android voice dial, even in froyo and even with Vlingo does not give you a true hands free experience because you cannot initiate it without launching the program from the screen, and it will not confirm by voice -- you have to confirm with a screen press or cross your fingers and let it autodial. Very disappointing.
Disoppointed with voice recording/dialing.
I sure was hoping that 2.2 would fix the voice dialing also. This may make me take the phone back before the 30 days are up. The voice MEMO is also a problem. Go to notes and try to do a voice memo...it's hit or miss and when you do see the mic recording, it will only record for a few seconds and then a screen comes up that says it cannot connect to the server. What's up with that. Very disappointed with the voice recording/dialing features of this phone.