Has anybody got the above or a similar headset to work with the jasjar and ms voice command 1.5.
I have tried the advice in several of the other posts and i am not getting anywhere fast.
I have a successful pairing with the phone and the headset, as the headset kicks in and allows me handsfree operation whilst driving. I had no issues installing ms voice command.
I have downloaded resco and altered the settings in the registry like advised by rilot in earlier posts however all i get when i push the button on the bt headset is a neverending intermittent beep which only goes off when i power down the headset.
Anyhelp as always is greatly appreciated. I would love to get this software, or even the bundled cyberon voice speed dial software, to work of the headset
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 am encountering a problem where after some time (do not know how long exactly) my BT headset seems not to synchronize with my TyTN. So when an incoming call arrives I am unable to answer it using the BT headset. Also, when I try to use Voice dialing it efuses to use my BT headset.
Only when I do a soft reset it works.
any ideas?
I have the same problem with a SonyEricsson HBH-610A.
Some times the bluetooth stops it self and I have to activate it agan.
Today when I tried to install the headset again, it searched forever and then I got the message, "Problem with Internal Bluetooth Hardware" and a OK button??
Only when I do a soft reset it saves the problem.
It actually drives me nuts, because I want to answer calles when the TyTN is in its holster.
I am using a Plantronics 655 with my TyTN running VC 1.5 with the common registry hack and have similar problems but not exactly the same. I want to be able to initiate voice dialing via the headset but when VC repeats the command it comes through the phone speaker and not the headset which also means my confirmation of the command has to be through the phone rather than the headset. Also, when a call comes in my TyTN speaks the name and number of the calling party through the telephone speaker but only beeps in my headset. To me it should be speaking to me through the headset.
I'm trying to get down to the bottom of this issue so it can be resolved through coordinated pressure on the responsible party(s).
Any help I receive will go to help all BT users of VC on the TyTN.
I am using a Plantronics 655 with my TyTN running VC 1.5 with the common registry hack and have similar problems but not exactly the same. I want to be able to initiate voice dialing via the headset but when VC repeats the command it comes through the phone speaker and not the headset which also means my confirmation of the command has to be through the phone rather than the headset. Also, when a call comes in my TyTN speaks the name and number of the calling party through the telephone speaker but only beeps in my headset. To me it should be speaking to me through the headset.
I'm trying to get down to the bottom of this issue so it can be resolved through coordinated pressure on the responsible party(s).
Any help I receive will go to help all BT users of VC on the TyTN.
Any of you guys had managed to get the voice commands coming out from your BT headsets using MS VC 1.6?
i.e. you press BT headset to activate VC 1.6, instructions from VC 1.6 comes through BT headset, you give instructions through Mic of BT headset.
I tried searching in the forum and only managed to find one thread here but that seems to be only applicable to Hermes.
Any help on this would be appreciated.
Working flawless on my wizard. did you setup VC6 to announce via BT? sometimes we miss the simplest things
EDIT: I'm using the motorola H500
From MS Voice Command troubleshooting
Bluetooth Usage Trouble
Pressing the Bluetooth headset button doesn’t do anything
You must soft reset your phone after you’ve installed Voice Command before the Bluetooth headset will work for initiating Voice Commands.
If this doesn’t resolve the problem, it is likely that you are trying to use the Bluetooth functionality on an unsupported device. Voice Command’s Bluetooth functionality will work on devices that include the Microsoft Bluetooth stack, that conform to Microsoft’s guidelines for Bluetooth driver implementation, and for devices that have the correct hardware implementation necessary to route system audio through the Bluetooth headset.
If you have a device that does not include the Microsoft Bluetooth stack, you may be able to route all system audio through the headset using the Bluetooth stack vendor’s Bluetooth control panel. If you can, you can use Voice Command over Bluetooth by pressing a hardware button on the device and conducting the interaction via the headset. The Bluetooth audio routing options will not work properly on devices that do not use the Microsoft Bluetooth stack. You should select “Announce notifications using Bluetooth hands free if available” on these devices.
Click to expand...
Click to collapse
I think you'll need AKU3
_Nomad_ said:
Working flawless on my wizard. did you setup VC6 to announce via BT? sometimes we miss the simplest things
EDIT: I'm using the motorola H500
Click to expand...
Click to collapse
You were right. I missed setting up VC 1.6 to announce via BT. BTW, I had since set it to 2nd option from top, i.e. Annouce notifications using BT hands free if available. When I received an incoming call earlier, I believe the notifications came through the speakerphone as well as my BT headset, and when I spoke, I believe it went through the BT headset. Is this behaviour correct?
If I set to 1st option of Announce notifications using BT hands free only, does it mean incoming calls will go to BT head set only, and nothing from speakerphone?
Thanks.
_Nomad_ said:
From MS Voice Command troubleshooting
I think you'll need AKU3
Click to expand...
Click to collapse
I'm on AKU 3.3, Xplode R1 rom. Thanks.
zard said:
You were right. I missed setting up VC 1.6 to announce via BT. BTW, I had since set it to 2nd option from top, i.e. Annouce notifications using BT hands free if available. When I received an incoming call earlier, I believe the notifications came through the speakerphone as well as my BT headset, and when I spoke, I believe it went through the BT headset. Is this behaviour correct?
If I set to 1st option of Announce notifications using BT hands free only, does it mean incoming calls will go to BT head set only, and nothing from speakerphone?
Thanks.
Click to expand...
Click to collapse
When you initiate a call with the BT hands free button, does the instructions from VC 1.6 come from your Wizard or BT hands free? If you give your instructions, does it goes through the BT hands free MIC or Wizard Mic?
I'm having an intermittant problem with the voice announcing. I can initiate the voice command with the button on my bt headset, I get the little beeps prompting me to speak, I give the command and then 75% of the time I dont get the voice announcement back saying "call soandso home?" but the contact will come up on the screen Every now and then I will get the voice prompt...cant figure out why its intermittant.
I'm using the plantronics 655 with the tmobile wing.
Does anyone have a step-by-step way of removing that blasted Cyberon rubbish from the Ameo? I bought (having tried, um... other sources) MSVC 1.6 UK from Handango, wondering if perhaps a real EXE-from-PC install would somehow work "better", but same problems.
I had it working yesterday via BT headset to listen, but no notifications came through so commands were messed up. Removed it, and installed again; I've remapped the "Web 'n' Walk" key to activate it. Now what I don't understand is this:
Installed yesterday. No attempt to remove Cyberon:
Worked okay for a while. Worked with BT headset button. Didn't respond to commands from BSH-100 headphones, but they're junk anyway. Bluetooth started getting unreliable and wouldn't pair with Nokia BH-200 headset after working fine with it for an hour or so.
Removed MSVC. Reinstalled. It's in the startup folder and so forth. Button on wired headset triggers damn Voice Speed Dial. Haven't tried bluetooth yet. Responds to commands with hardware button, but no option exists to map command to wired headset button.
Removed Sddaemon startup item. STILL comes up when I use the wired headset button.
It's REALLY annoying and frustrating, as MS Voice Command DOES work effectively as a tool. It just doesn't, well, work. And I think nearly all of the problems it has are down to the presence of this Voice Speed Dial, which I will never use - I'm not recording voice tags for everything, this is the 21st Century!
Also, why doesn't TCPMP follow UI conventions?! It keeps starting up in portrait mode and won't fix itself unless I use the T-Mobile "screen rotation" icon.
EDIT:
Okay. I paired the Anycom headset to it.
As a Bluetooth headset, the button dials, makes calls, and if held, brings up Voice Commander. Notifications now come through the headset, and commands are definitely going to the device, but music is played through the unit, not the headphones.
As stereo headphones, the buttons work, but it doesn't hear commands from the microphone in the headphones - only via the built-in microphone. But music (with joint stereo enabled) comes through the headphones alright.
Other than that the Ameo definitely kicks arse, having GPS etc. built in is excellent. Is it really 802.11g, though - or is it like a hacked Universal with 802.11b speed pretending to be 802.11g?
I used to have VoiceCommand and BlueAudio perfectly working on my X1. Now this crappy X2 that messes up so much, canNOT run any Audio to the Bluetooth Headset.
It should have the MS Bluetooth Stack so these programs should work. Perhaps it is some registry change that makes them work?
Anybody got them to work and know how to? Thanks!
It seems that the Bluetooth AudioGateway dll files is not working properly. Tried different dll's from different versions but still did not find the "correct" working one. Anybody???
Couldn't get MS Voice Command working.
Vito Voice Dialer works great though.
Haven't managed to make my X2 work with my existing bluetooth headset.
X2 says it's paierd with the device, but then you can't answer calls or anything else.
If it wasn't for the $$$ I spent to buy this piece of crap, I'd have a new phone already!
Okay, is this vito voice dialer dialing VIA bluetooth or not? And HOW do you press a key on the phone to activate it? What key? And just read their manual, they don't even mention any bluetooth capability there. Can you use bluetooth and how?
Because voice command works (more or less) HOWEVER NOT via bluetooth and since there is NO hard/software button to assign to it, it cannot be activated via the phone either!
I have to press the bluetooth button and then the sound (mic and voice) come out of the phone speaker.
I strongly think this has to do with the bluetooth gateway SE is using with the X2. But I was hoping somebody technical could have found a solution by now. For me voice dialing is essential and my X1 was perfect.
With blue audio I could listen to musik on a mono bluetooth!
Just to mention it, I use SE hbh-PV740 and it always works if making 'regular' calls via the phone over bluetooth. But I cannot initiate it nor voice dial.
I can't get my X2 to do anything with my bluetooth kit, so all your questions re: bluetooth I can't answer.
I start vito from a button on the screen and it works.
For me and my phone, the vito product is much more accurate and reliable than voice command.