Related
Hi
Anyone found any software that offers reliable voice dialing? The MDA Pro comes with somet called "Voice Speed Dial" Its sh1te!
Has a habit of trashing the voice tags of its own accord, and often does not respond when I press button on bluetooth headset.
When the device is closed and off and you press the button on headset nothing happens (PPC is starting up etc) several presses are usually required before you can actually call the contact.
I just tried a trial version of microsoft voice command 1.5 (this I believe is what imate is shipping) unfortunately it cannot understand a word I say!! (could be the devonian accent).
I said 'call work' it said 'calling 999' I managed to hit it with a brick before it actually did call 999 !!!
Anyone suggest something that actually works (flawlessly). I dont mind training it if that means its gonna work!
Nigel
"microsoft voice command" all the way.
Thing is that it doesn't support dutch, but it does support english, german and american, so if you speak any of these languages you will have to get this program.
Dunno about the trial version, but the full version requires you to pronounce right. You can test this by letting someone call you first so you can hear how the program expects you how to pronounce it. (I have dutch names and they are completely different when pronounced by the voice command)
Hope this helps.
I've flashed my MDA Pro with the I-Mate JASJAR rom, and the standard voice dial on that works like a charm!
It even work from my Jabra BT800!
Grrrrr
I'm a native English speaker and it dont ruddy understand me!!
Sounds like many people here have gone for the JasJar rom on their devices. I guess I will give this a go - I just dont want to end up with a useless brick.
Nigel
MS Voice Command - works for me on my jas jar via my moto BT headset even in the car when driving (i.e. with plenty background noise).
If you follow the tips on the MS VC website it makes it even more reliable.
The HTC voicedial program works great for me, and complies with my HS810 headset without any issues whatsoever. In fact it's even recognised my commands with music running in the background. I've tried MSVC in the past on other XDA's and found it to be rather cumbersome.
Ant
I found that Microsoft Voice command when started via bluetooth headset does not turn the link off when it's finished.
The way i got this to work with BT was to replace the file sddialer.exe in the windows folder with the voicecmd.exe file from MS VC.
Does anyone else know a better way of doing this to allow for the BT headset to be turned off automatically once listening is finished ?
Voicedial works, I just find it really slow. It is 100% reliable on the recognition front though.
What I noticed with voice command was an instant response. Press the button and speak, no wait of any kind for the 'beep'.
Voice command simply sticks an icon on the task bar, it does not have to load some monster gui before you can speak. Ditching the gui would be a step forward for the built in voicedial.
Nigel
steverae said:
I found that Microsoft Voice command when started via bluetooth headset does not turn the link off when it's finished
Click to expand...
Click to collapse
Hi
How did you get voice command to respond to the bluetooth headset in the first place?
With VC installed, the button on my BT headset is still starting the old HTC voicedial software.
Is there some registry setting somewhere to tell it what to launch?
Nigel
Yes there is a simple registry hack, it's posted else where in these forums but here it is again
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 works for me and everyone else who has tried it AFAIK
Hi
How did you get voice command to respond to the bluetooth headset in the first place?
With VC installed, the button on my BT headset is still starting the old HTC voicedial software.
Is there some registry setting somewhere to tell it what to launch?
Nigel
Click to expand...
Click to collapse
I simply replace the file sddialer.exe with the voicecmd.exe and renamed the voicecmd.exe to sddialer.exe. After a softreset that's it.
Still can't fathom out a way to close the BT link though without doing it manunally from the headset.
Also does anyone have Fonix Voice Central installed on their Universal, i always get an error saying unsigned program or summit like that when i try to install the trial.
voicedial
I am italian mother tongue. Cyberon voicedial works incredibly well. I tried vito's program in the past. Average it could recognize 10%.
The cyb's software is awsome. I use it with a Jabra BT800 headset and recognize voice even in noisy environment.
Must tell that I am very satisfied with my JJ. Absolutely no problems in any way.
Installing unsigned apps on WM5
Trying to install Fonix Voice Central 3.0 Trial on my new Universal but keep getting an error stating unable to install as it is from a untrusted source or is an unsigned program.
Please help
Hi
OK, so its more reliable when using the bluetooth headset - it even understands devonian! BUT and this is a big but... why the heck does it not work when the device is closed (screen inside) and switched off??
Nuts... I get the beep from voice command after pressing button on the headset, but it ignores what I say. Performing the same thing with the screen open laptop or pda style (with device switched off) works fine, but not with the ruddy screen closed.
Anyone else experienced this?? Screen closed it how my device stays most of the time.
I see what people have been saying about it leaving the bluetooth channel open after as well - mad!
Nigel
Voice command does not respond when unit closed
Hi
Voice command not responding when unit closed (screen inside), and using button on BT headset.
Has no-one else found this, and if it works for them can they post rom versions. Certainly does not work on MDA Pro shipped rom!
When unit open, or screen folded outside PDA style, VC does respond to BT headset fine. Just not when its closed.
Nigel
I have imate JJ italian rom.
Works perfectly with Jabra BT800 and device switched off (screen closed down).
No problem at all!
Thanks - looks like a bug in the ancient MDA Pro software.
I was holding off flashing it with imate roms case I heard a rumour that t-mobile are about to release a new rom soon which may be newer again I suppose.
Nigel
Well, I put the imate rom on there and that did not solve it. Voice command does not work from bluetooth headset when unit closed. It gives me the beep prompt to say its listening, but it never responds. Open screen and all is well.
Save me some money anyway, no point in buying Voice Command if it does not work properly!
Nigel
veletron said:
Voicedial works, I just find it really slow. It is 100% reliable on the recognition front though.
What I noticed with voice command was an instant response. Press the button and speak, no wait of any kind for the 'beep'.
Voice command simply sticks an icon on the task bar, it does not have to load some monster gui before you can speak. Ditching the gui would be a step forward for the built in voicedial.
Nigel
Click to expand...
Click to collapse
Ive just been using the bog standard voice recognition. No problems at all, even works with background noise.
Im guessing that some people havent read instructions properly
The HTC software that comes with the device does work (reliably) its just too slow to be of any use.
10 secs to respond when unit is off/closed. If I dont get a prompt response i'll press the button on the headset again which seems to confuse the hell out of it.
This is my reason for trying voice command... Response time from voice command (from unit off) is 2 secs max. Unfortunately it does not ruddy well work when lid is closed (no matter whether unit is on/off).
Nigel
I am very sorry in advance if this issue has been raised elsewhere on the site, but after spending quite some time searching for an answer by both the forum search and google search, I am going round in circles and haven't found a solution.
I have a UK Tmobile Vario 2 (Hermes) running its original Rom (I have been too scared to flash it in case I break the phone as I don't really know what I am doing) and I have a Motorola S705 A2DP headset. I love the feature on VC 1.6 which reads out new text messages in full but can't find any way of routing the audio for this feature through my bt headset. The incoming call notification works through the headset but every time an SMS comes through it pauses A2DP, reads it via the phones loudspeaker, then diverts sound back to the headset again?!?
I went on the WIKI and found the Voice Command section. I tried installing the patch/program it suggests and did the tweaks it said to the registry , but it didn't make any difference on this problem.
I just wondered if this is an unfixable problem, or if there is anything I can do to get it working because this feature would be incredibly useful to me (I ride a motorbike and to get texts read through my headset when riding would be excellent).
Thanks in advance for any help guys. Sorry again if I am raising a known issue, if I am, if you could point me in the right direction it would be much appreciated.
have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.
bapski said:
have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.
Click to expand...
Click to collapse
Thanks Bapski, I have just installed it but unfortunately it hasn't helped thank you anyway though, it was definitely worth a try
Well, I have had a good read through the threads on Voice Command and all the fixes for the headset button but it seems nothing yet solves the problem of routing the SMS notification through the headset which is a shame, it would have been so useful.
Well, hopefully, when I get my nice new Kaiser upgrade (whenever that may be ) .. I will have more luck with the bluetooth audio
Don't buy a phone with a MS BT stack because they will never fix the problem..MS has known about this for so long its just sad..The next phone I get will have a widcomm bt stack.
Yeh, got to say that the bluetooth hasn't been particularly great ... especially when trying to get it working on A2DP.
If only I hadn't stumbled across VC 1.6 I would be none the wiser and wouldn't even know it is possible to have SMS messages read out oh well
it doesnt work dont even bother, I loved it on my wizard, but there is a hardware problem with the heremes or whatever the problem is the last revision of the BT stack doesnt fix it and its never worked. all the patches and fixes only work for awhile then just stop and rquire a cryptic series of hacks to make them half work again. your better off buying a thai slave to read your messages to you.
I have had the Sprint Touch for 2 weeks now and really miss MS Voice Command.
Anyone have it working and what are the steps ?
Scott
anywhereanytime said:
I have had the Sprint Touch for 2 weeks now and really miss MS Voice Command.
Anyone have it working and what are the steps ?
Scott
Click to expand...
Click to collapse
Just install it. MS Voice Command 1.6 works just fine
no problem with call anouncement,or voice confirmation over BT?
imradar said:
no problem with call anouncement,or voice confirmation over BT?
Click to expand...
Click to collapse
No prob with my Motorola HT820 and my S9. Call anounce works just fine and even reads my text messages
Thanks for the replies ... I just bought a Blue Ant Z9 and will report once I install it.
I really miss MS Voice Command also, there are three major issues.
1. Any speech or announcements from Voice Command via BT (Bluetooth) have very low volume.
2. Bluetooth dialing confirmation when confirming a number to call is not recognized most if not all of the time.
3. After pressing the button to start voice command, many times you will not hear the beep over the phones internal speaker or over bluetooth. It seams that the phone delays opening up the sound channel a second or so, and the beep is never heard.
I would love to see workaround or fixes to these.
Only #2 has a work around by disabling confirmations.
Blue Ant Z9
Today I played with my new Blue Ant Z9 headset - GREAT headset.
Using the Z9, VC understands the initial command whether it's dialing, help, start, etc. But, when VC repeats the command, VC times out.
Where do you turn notifications OFF - I could only see under the VC menu where you could chose either Bluetooth or wired/device speaker ?
Anyone using a Z9 successfully - I have firmware v3.0
I contacted Z9 tech support and they will be monitoring this thread to see if they can help find a solution ... but it's probably VC itself.
Scott
Uninstall the Cyberon Voice Dialer
I recall reading on either the Titan/Mogul thread or the HTC Elf/Touch thread something about the bluetooth "voice command" path being directed to the Cyberon and that it must be changed somehow to allow VC to work properly?
I disabled the Cyberon Speed Dialer, but can't find how to remove it. Does anyone know how to remove the Cyberon "Dialer" software?
Scott
VC 1.6 WORKS - but NOT with Bluetooth
Today I played some more and VC 1.6 definitely works over the speaker and built-in mic - VERY COOL - BUT, NOT with bluetooth (we are using the Blue Ant Z9)
SAME PROBLEM reported across many threads - when VC 1.6 "confirms" the command, it then hangs up (turns off listening)
This seems to be a common problem across many HTC devices, so I searched quite a lot and found this under the Hermes thread.
http://wiki.xda-developers.com/index.php?pagename=Hermes_Utils
ANY EXPERTS OUT THERE to give this a try and report back ??
--------------------------------------------------------------------------
How to make Microsoft Voice Command 1.6 work (WM5 & WM6 tested!).
(caution, this MAY disable all incoming call notifications over the speaker and obviously doesn't route the notifications to the headset - that's a MS stack problem...)
NB The 'Program Files' directory mentioned several times below, may be different on non-english language versions of WM (see below).
Install VC 1.6 (make sure it is in Main memory)
Download Bluetooth Voice Command 0.9f.cab here - related forum thread
Download ?BTVoiceCommand.exe here - related forum thread
Download replacement btagext.dll here (Unknown if this works with WM6?) - related forum thread
Run .9f Hack
Create the Folder \Program Files\Bluetooth Voice Command (should be created during the .9f cab install)
Copy ?BTVoiceCommand.exe and btagext.dll into this folder
Go to newly created BT Voice Command config (in Programs) and tick the check box "Enabled"
Set command duration to 30 (or more - check by experiment when set up)
Set or check that the following registry keys are set (I had to manually change Path to ?BTVoiceCommand.exe.)
HKLM\SOFTWARE\OEM\?VoiceCommand\Path = "\Program Files\Bluetooth Voice Command\?BTVoiceCommand.exe"
HKLM\SOFTWARE\OEM\?VoiceCommand\?VoiceCmdDuration = 30
HKLM\SOFTWARE\Microsoft\Bluetooth\?AudioGateway\?BTAGExtModule = "\Program Files\Bluetooth Voice Command\btagext.dll"
a. (For reference: http://forum.xda-developers.com/showthread.php?t=283412&page=7 )
*Go into the registry (HKLM\SOFTWARE\OEM\?VoiceCommand\) and set ?LaunchAPEnable to 1 (I wasn't sure if this was necessary...but it's working now)
Soft reset device
Delete Headset Pairing
Recreate Headset Pairing.
*NOTE: first time you invoke voice command using BT headset button, you may get the "run this program yes/no?" option on your screen. You have to QUICKLY hit "yes" or your phone will have to be soft reset to exit the prompt.
Set Side button to ?VoiceCommand (if desired for backup when using Mortscript described below)
You may also need to create the directory \Program Files\Bluetooth Voice Command and move the files over if you live in a different country and MS installs everything to something similar - like Programme...
WM6 specific:
If using the .09f file downloaded from the link above, the registry key should look slightly different:
HKLM\SOFTWARE\OEM\?VoiceCommand\Path = "\Program Files\Bluetooth Voice Command\BTVCBasic.exe"
You may still encounter a problem where approx 15 s after initiating a call using MSVC from your headset button, the sound is routed back to the handset. A subsequent press on the button usually reroutes the sound to the headset, but sometimes disconnects the call instead. We are hoping for a fix for this.
--------------------------------------------------------------------------
Today I played some more and VC 1.6 definitely works over the speaker and built-in mic - VERY COOL - BUT, NOT with bluetooth (we are using the Blue Ant Z9)
SAME PROBLEM reported across many threads - when VC 1.6 "confirms" the command, it then hangs up (turns off listening)
This seems to be a common problem across many HTC devices, so I searched quite a lot and found this under the Hermes thread.
http://wiki.xda-developers.com/index.php?pagename=Hermes_Utils
ANY EXPERTS OUT THERE to give this a try and report back ??
---------------
Gave it a try tonight. The hack does still work, but doens't give us anything more than what we already have. While it will launch voice command, it still has a problem with confirmations. I am thinking that the BT stack on the touch is having a problem with this. It beeps, waits for input, then responds, then waits for input again. Somehow with this 2nd input something goes wrong. I have not had confirmations work once for me over bluetooth.
I am waiting on my Touch to get there and this is very important to me.
If confirmations are turned off, does it work properly?
fowen said:
I am waiting on my Touch to get there and this is very important to me.
If confirmations are turned off, does it work properly?
Click to expand...
Click to collapse
Please read message #6. Other than those issues it functions.
Anyone get VC 1.6 to work with a Blue Ant Z9 BT headset yet ??
I have the vogue and the Jawbone with VC 1.6 - sametime out problems as listed before, however, when you go to settings>VC>phone and turn confirmation off it works absolutely perfectly w/o a hitch. I hit the button, it plays through the headset - I name the perp - it announces the name and dials...no issues what so ever. I think this is an acceptable fix and if the name does not come through you can just hang up quickly and try again... I'd rather do this then hack it given there is no confirmation that it works.
So yes... VC 1.6 work through BT w/ confirmation set to off.
jessiethe3rd said:
I have the vogue and the Jawbone with VC 1.6 - sametime out problems as listed before, however, when you go to settings>VC>phone and turn confirmation off it works absolutely perfectly w/o a hitch. I hit the button, it plays through the headset - I name the perp - it announces the name and dials...no issues what so ever. I think this is an acceptable fix and if the name does not come through you can just hang up quickly and try again... I'd rather do this then hack it given there is no confirmation that it works.
So yes... VC 1.6 work through BT w/ confirmation set to off.
Click to expand...
Click to collapse
I tried it with my Blue Ant Z9 and it does not work without a hitch - the volume is very low and it does not seem to get the perp correct even most of the time. I will do some more experimenting and contact Blue Ant tech support.
I got my Blue Ant Z9 working ... there is a delay when you press the Multifunction button of several seconds and I had to watch the screen to see whan VC came on.
The dial and call "work" only the first time - if you say Call Jack and there are multiple numbers for Jack, VC asks Call Jack at Work or Mobile (say there are both). If you respond and say Call Mobile - VC hangs up just like before the turn off confirmation.
However, if you say Call Jack at Work, VC correctly calls the number.
Are you able to go multiple levels of recognition on the Jawbone ??
I'll take what I can get for now.
Oh, yes when someone calls me that is in my contacts I get NO notification or Caller iD - is that one of the things that still doesn't work ??
I recently saw this on the Titan thread - anyone know if the Sprint Touch and Sprint Mogul are the same ?
Anyone get the caller ID announce to work yet ??
http://forum.xda-developers.com/showthread.php?t=352638
Hi,
I still cannot get it to launch with my Jawbone BT headset...
I tried the instructions...
Anyone have anything to help me further?
LIP
Motorola H500 with MSVC1.6 is fully funtional even on confirm call, mobile/home etc
I used to use MSVC 1.6 on the Tytn2 on WM6.5 (see sig) and the confirmation notifications when you called someone always used the bluetooth headset. Since running it on the Leo MSVC seems to use the loudspeaker on the handset instead of the bluetooth headset even though every setting is marked as "Announce notifications using Bluetooth hands free only"
Anyone else having this issue as I did a search and couldn't find anyone.
Edit: Just had it working once but then the other end couldn't hear me when the call connected. Then I tried again and it had reverted back to not working.
I went to Bluetooth settings, Advanced, Audio and ticked the box then rebooted the phone...
I have this same problem! Its annoying... you want to make a call and the prompts/confirmation come from the phone... Please, can someone figure this out?
Bumping thread as it should be resolvable
Starfury said:
Bumping thread as it should be resolvable
Click to expand...
Click to collapse
IT isn't... I have done more research..
The Leo (and the TouchPro2) use a Widcomm BT stack as opposed to the usual MS stack. Sadly, this means the BT won't play nice with a lot of different apps/equipment. This isn't something that can be swapped out easily as NRG has pointed out. Touch Pro 2 users are still facing the same problems even though that phone was released much earlier. Some however have reported some success when using certain custom ROMS... how its working with some ROMS and not others is still a mystery it seems
I would watch the ROM Development thread carefully to see if a ROM what works with our MSVC shows up....
Hello,
Is there a workaround... ?
Thanks in advance for any info,
Jean-Jacques
I have the same problem. I'm using an old phone when I need to use hands-free. After spending a lot of money on my HD2, I'm not impressed.
I there a particular combination of headset and software that does work, especially for voice dialing?
have you tried this?
I would, but I don't know if I even have voice command on my phone.
http://forum.xda-developers.com/showthread.php?t=634494
DrATty said:
I there a particular combination of headset and software that does work, especially for voice dialing?
Click to expand...
Click to collapse
Does not work with my helmet bike with scala-rider Q2, but does with does with Philips SH9000 stereo headset...
Mono/Stereo seems to matter.
Any workaround would be veryyyy appreciated
Jean-Jacques
Workaround
Hi,
for this following workaround seems the only way to get it runnin:
My BT-Headset has the ability to be set as a Stereo-Device. When I establish a connection to this Stereo-Device, I can use it (my BT Headset) to give Commands and recieve "answers" from the VC. In case I want to start a phone-Call, my headset changes the connection automatically from "Stereo-Device" to "Handsfree-Device" and back, after finishing the Call.
This may be the Reason, why someone here already got it running with a BT-Stereo-Headset.?
Sorry for my bad english...
Hello,
I've got a lot of problems with Voice Command + LEO + BT Headphone.
Voice command speaks on the Leo (Do you want to call Mr TITI at work?) instead of speaking in headphone.
Do you have similar problems??? In France we all have it.
Do you have a solution?
Thanks in advance.
Hi, I have the same problem: some times it use the headset, some times the phone pseaker....
I have other problem with VC 1.6.21725:
- as Mail are read perectly, I have no SMS read.
- Call announcment are not thrown every times I have an incoming call...
Any help?
Is there anymore development for VC? or is it discontinued to Tellme?
same problem here....
does anyone have a solution yet? how to make Leo let voice command speak via bluetooth? Not through the the device? I searched the hole Forum. Any tips and hints that where given didn't work for me. So, if someone have an Idea please post.
Thank you.
Joshua
Same thing happens with Cyberon VSD I am using. Hope someone finds a solution. This didn't happen both in my Omnia and Topaz.
There are a lot of threads here discussing this problem... do a search if you want to research it.
Basically, it is because the HD2 uses the Widcomm BT stack instead of the usual MS one... it will not play nice with many apps (and some hardware) which may have been written with the MS one in mind. This is not an easy thing to fix by just cooking into ROMs too. THe guys with the Touch Pro 2 have this same issues longer than us HD2 owners cause of the same stack... and they still have no solution.
Our only hope is that Widcomm updates their stack to play nice... or more importantly, MSVC or CSVD issues an update that will play nice with the Widcomm stack. Last update to MSVC was shown on Handango site as 20th Nov 2009.... I would like to hear from anyone who has tested this with our units.
Seems to have no issues to our problem
Looks like it's a problem of certain BT headset devices.
Look here http://forum.xda-developers.com/showpost.php?p=5318249&postcount=31