Related
Can someone please help. I have a new XDA II purchased a couple of weeks ago. I want to add voice dial so that I can record a voice tag to a specific contact, press a button on my bluetooth headset and the XDA II phone will dial that person for me.
Can some kind person please guide me exactly how to go about setting this up?
JSS
You can't record voice tag unfortunatelly... Microsoft sells Microsoft Voice command for
pocket pc for 30$.. you don't need to train it or record voice tag.. it just recognize what
you say. it isn't bad
you can grab it from www.suprnova.com in the App/pocket pc section (you will need a bittorrent client, ABC http://pingpong-abc.sourceforge.net).
You can use Neuvoice: http://www.neuvoice.com/xdasoftware.php
Allows you to record your own commands. I had problems with some English programs to recognize Dutch names in my contacts.
Neuvoice has to be trained, and this takes some time, but works perfect with foreign languages.
i use vito voice dialer
works great you record your voice tags then if you have button plus installed i have mine lined to the contacts button if i hold it down it will say please say name so you say the voicetag and itll begin to dial works very well
I tried MS voicecommand, and i was not impressed. The thing about "not training" is that it will recognise only the obvious. Also, it was very bad, to pathetic, in recognising things with the earphones on. Add to that noise when driving, it was impossible.
I found the fonix voicedial was very good. I downloaded a trial (gave me a few eeeks to use it, now theres a sensible trial period!), and it was very good.
I havent used vito, maybe give it a go.
fonix is very good fun to play with but it likes to call my dad most of the time lol im like mum....
dial dad
does your head in lol
Vito is the best one ive tried
but fonix is very fun to play with lol
I am french and i need to 'train tag'.
I use neu voice navigator.
For 9,99$, the voice recognition works very well, indoor, outdoor with wind and driving in the car.
Voice dial for XDA II
Thanks to all of you so far. I went to the Vito site and read that it does not work for XDA II.
""IMPORTANT! Doesn't work on MDAII/XDAII
VITO VoiceDialer PE is not currently supported by XDAII/MDAII. When recording a voice tag it brings up an error "Cannot process this file" Our development team is working on the solution. We apologize for the inconvenience. ""
Hopefully this can be fixed soon. I will try some other sites
JSS
I've tried Fonix and MS Voice Command on XDAII and in my view MS Voice Command is the best. Contrary to one of the posts above I've found it very accurate especially after learning how to speak to it after the first couple of days. It works well with the wired earpiece but will not work with a bluetooth headset as it takes its input only from the microphone. As such it is a viable hands free solution and you dont need to train it so if you add a new contact then it is automatically recognised. Beware that the current US version doesnt support dialling of UK phone numbers ie you cannot say 'dial 0113 205 3345' as it will only accept 7 and 10 digit numbers that do not begin with a zero.
I tried MS Voice Command and I must concur with others opinions. Because you cannot train it to learn your voice, it means that you must learn to speak the way it wants you to speak. Fair enough, but the 24-hour trial period is too short. After 24 hours, I could not get it to perform to my satisfaction. Perhaps with a longer trial period I might have learned how to use it.
That is why I am not buying it.
I've tried MS Voice command, and found that unless you want to speak with an American accent then don't bother.
I've also just tried Neuvoice, which works with tags that you assign, and that seems to work extremely well. Now if only one of them could work with a Bluetooth headset! But I guess that's a the fault of the XDA's bluetooth implementation, rather than any of the software.
I purchased MS Voice command (use on my XD2) and as everyone has said it is no good unless you use an american accent...only problem is that I keep talking like an American now :roll: LOL
Thanks - Sunny.
""I've also just tried Neuvoice, which works with tags that you assign, and that seems to work extremely well. Now if only one of them could work with a Bluetooth headset! But I guess that's a the fault of the XDA's bluetooth implementation, rather than any of the software.""
Thanks again. Of course, if it does not work with a bluetooth headset, there really is not much point having it until it does, because the whole idea is to make voice dial calls that are completely 'hands fee'.
I spoke with O2 Mobile Internet support team who tell me that the software will soon have an update (bugfix) which will apparently fix this problem and allow the XDA II to work for voice dial. Does anyone know what this is, when is it coming and how will we be able to get it and put it onto our XDA???
JSS
XDA II update
latest information from O2 is quoting Spring 2004.................
.....................so that'll be 2005 then!
ian
I suppose we will have to rely on the brains of the wonderful people on this forum who will surely come up with a way around the problems.
There must be some way through it. All ideas are welcome
JSS
Bougth a second hand P800 this week to compare with the XDA II.
I must say that the P800 is much more advanced on the phone point. It may be not as performant, but the thing works quite nicely. Voice control works perfect, also with BT headset.
And controlling and operating the phone is much easier thanks to the jog dial. I also like the better implemantation of the phone settings and options. Don't understand why this isn't implemented on more devices.
Think MS still has a long way to go with Pocket PC Phone Edition to reach at least the same phone functionality...
@ Jos
do you know why that is?
its because the p800 is a symbian phone with PDA features
the XDA is a PDA with mobile features
theres the difference
and p800 camera is ****e lol
Hi all!
I Just changed from a P800, and fully agree with gazzaman2k and Jos, P800 is a "so-so good" phone, but a very POOR PDA.
XDAII is a fully functional PDA, but the phone parts leaves so much to be desired......
Any way, I still would be using my P800, should I have been able to fix the SYNC problem.... A phone PDA UNABLE to sync with with your PC is a useless combo. Not to mention the full distress recoveries I had to do with my Outlook contact and agenda files.....
I ended up recovering my old T68 phone, (I need it for the BT carkit) I passed my Cassiopeia EM505 to a friend, my wife got my P800 (unable to sell it on e-bay) and I'm so-so satisfied with my XDA.
Until:
1.- it gets the handsfree BT issue solved (car kit usage)
2.- The Voice command functions are fully implemented (BT headset too)
3.- The phone functions are VERY MUCH IMPROVED (one hand use)
I would NOT consider the XDAII a "PHONE-PDA", but a "PDA-phone". (Capitals being removed intentionally)
BTW, most of the "Voice/dial command" programs I tried are useless and/or unreliable.
but also :x
Indeed, I agree the XDA II is a PDA-PHONE and the P800 a PHONE-PDA.
Would be nice to see an OS that would run on the fast hardware of the XDA II with all the plusses of Pocket PC and Symbian...
And the P800 is for my girlfriend. She needed a new phone and I could get this one for a fair price. Plus it gives me the chance to play around with both en see the pros and cons of both.
For performance and Outlook sync, I prefer the XDA II, but for phone funcionality I prefer the P800...
Voice diaing continued...
The XDA II is a quality PDA with phone functions. Since, I understand, other PDA's (even those without built in phones) are able to have voice dial functions for add-on phones, it seems to me that the XDA II could easily also have these functions. I think that it would just mean getting the right software. How and where from I would like to know?
It may be possible to improve the phone functions, but the single one thing that would improve the XDA II for me is the addition of voice dialing via bluetooth - so that you can record a tag to a contact, press a button on the earpiece, say the contact name and then the number is dialed. That handsfree capability would be a very good start - and let's face it, with driving restrictions etc, these days, it really is essential if the XDA II is ever going to be of any value as a mobile phone.
What I need to know for certain is:-
1.Is there a software that will allow me to have this function.
JSS
Hi Guys: I have got the Widcomm Phone edition stack working on my unit.
It seems to be fine but I have not fully tested all aspects of the software - so if any little bits don't work, let me know...
You need to install the official widcomm 1-4-1-59 version
Then you can upgrade it using the cab file I have made.
The 1.4.1.59 version file I got from the following topic
http://forum.xda-developers.com/viewtopic.php?p=57550#57550
thanks go to mamaich for the file.
the upgrade file consistes of the PE edition files and the required registry entries.
Let me know how you all go on with it - but I am not really a hacker so any serious probs I will not be able to fix...
if anyone else can improve on the installation be my guest
any news about which profiles it support that ms or the old one dont support ?
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
I can't garauntee it works perfectly, so I suggest everyone make a backup of their system before use.
has anyone tested any BT headset with this new stack?
I've got it installed and it all seems to work well exept for the handsfree/headset profile, I have set up my headset ok it is discovered and bonds fine but when I try to connect from the xda2 the connection fails after "waiting for device" for some time. tried with a motorola hs 810 and a neovoice usb, same with both. Anyone got any ideas?
BT headset
I have a 6315 and an XDA 2, I haven't tried the BT Stack on the XDA 2 yet but I found when I bondeded my HBH-30 to my 6315 once it made the connection my BT Headset shut off for some reson. This caused the bonding to fail, but as soon as I turned my headset back on (while it was trying to discover services) it completed the process and worked on my 6315. I'm not sure if this will be the same, but it's worth a shot.
Brandon
Test results
Hi fellows
Here is little bit of my testing of this new BT Stack, which we all awaiting for..
Proc…
1. Installed as per instructions 1.59 without any problem. During installation was prom to override .dll files – agreed to do that. For good or for bad – will see later.
2. Installed .cab file provided by icarusbop (big thanks to him for doing this) without any problem. Screen shots will be attached below.
3. Reset it as requested upon installation and got Widcomm BT working instead of MS BT..
4. Paired it with my BlueTrek G2 within 3 seconds (which took usually 10 sec with MS BT)
5. BT recognized G2 as device with Headset/Hands-Free profiles and asked to use as default… I said yes…
Here comes Cons part ;(
1. Unfortunately even after paring – my I-Mate can not get connected with G2 (see screen shot)
2. As you can see in another screen shot – there is Hands Free menu – it can not be accessed, or can be accessed ONLY while connection is established.
3. AND the last L … So, this new BT is not working now… I decided to go back to MS BT… SURPISE!!! I am getting message that BT HARDWARE IS NOT INSTALL ON THIS UNIT…. L Assumption - .dll files were overwritten (see Proc 1)
Here is my 2 cents in this jorney… I am hoping that described problems can be fixed and we can make it working (without doing hard reset on my device )
Paul
thanks guys! for testing hands-free/headset profile. by now everything seems to work fine with this new stack except for hands-free/headset profile.
New comments to my testing
1. I tried what NeoCole recommended - didn't work for me
2. As soon as new BT is OFF - MS BT is working fine .....uf
LETS FIX THE HEADSET PART PLEASE
I posted this is another thread - but in case someone does not read that thread . . . it is relevant here as well.
If the intent of this is to get voice dialing without touching the device, that is by only pressing a button on the headset to initiate a voice-dial program to make the call, there is no evidence this works with this BT stack either.
I have been reading other forums with people who have the H6315 already (mine is in the mail to me now) and none of them have been able to make this work. Nor is there any mention of this capability in any of the literature and/or documentation for this device. It seems that if this was a feature of this phone, it would be prominently displayed!
Voice Command
Okay.. on my 6315 I press the headset button, it beeps, sound and voice is now transfered to the headset. I do this before I initate voice command. Now all I do is press a button that activates Voice Command on the PPC and walla, I'm speaking and listening through my BT Headset. This is a huge step forward from using the MS Stack, and I feel that since the Phone Edition of the Widcomm is 1.0.0 I'm sure that they'll associate a hardware button with the headset button in future releases. Anyhow.. I think that the functionality of the Widcomm BT Stack is well worth the work. The XDA 2 would be a lot better device if the BT Stack worked 100% of the time and was fully compatibile.
I also have not got it working.
the Hp 6315 is well know to still require a hardware button press (not on the headset) to activate voice command. They can still not do with any nokia or SE phone can do easily.
Surur
VoiceCommand
That would be correct... One press of the HW Button does it all on a Regular phone.
The 6315 has brought it closer to allow you to interact with programs using your BT Headset, but yes you must still activate the programs on your handset before you can use them with your headset.
So.. to sum it up...
1. You can't interact with Voice Command using MS BT Stack on an XDA 2
2. You can interact with Voice Command using Widcomm Stack on 6315, but you have to activate the headset first, then start VoiceCommand on the PPC by using the HW Button.
Hopefully through this thread we'll be able to give the XDA 2 the same functionality as the 6315.
And maybe if Widcomm provides an update to allow the headset to activate a HW button, we'll be to the one step solution.
I do not want my comments to be read as stating that this is not a worthwile endeavor. I simply meant to make sure that someone does not go to the trouble of installing this new stack (particularly those who might be considered novices) with the mistaken impression that by doing so they will have that "one step" voice dialing solution.
This is by all means a worthwile endeavor, but it is merely a step down the road . . . not the final destination.
Y'all are doing good work - keep on blazing that trail!
hm.. I would think that it is more of MS Voice Dial functionality than BT - to recognize signal sent from headset as request for voice dialing.
When MS released first version of Voice Dialing they did not expect new functionality to have BT headset with hands-free profile connected to the device.
paired with my Jabra 250 = ok
connected to my Jabra 250 = failed
No luck with Moto headset
Eveything else seem to be working. No problems with detecting and working with BT access point
rehman said:
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
Click to expand...
Click to collapse
Hi Rehman,
i tried to install and uninstall, for the very first time i didn't have to get a Hard-Reset done. the volume didn't disappear. so i believe trying it wont be a harm, but yet i would recommend to get a full Backup first.
Trying to figure this out
Okay, I looked through the whole registry. I can't find anything out of the ordinary. Only thing I can think of is the sound driver. Does anyone know what DLL that is? I bet it's a different version.
If someone that knows more about which DLL does what. Let's get all the DLL's that could pertain to Sound and Phone and compair the 6315 DLL's with the ones on the XDA2.
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
After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.
Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!
WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.
PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.
PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)
This problem can be solved by changing a key in the registry:
Code:
HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)
Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.
PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)
There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/
I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)
PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.
PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?
PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?
And last but not least: Will you still be able to use your phone as a "phone" then?
Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto
Regards, Licht
Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.
Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.
Would LOVE to have a fix that would let me use with all headsets.
How does the jetware stuff work? I heard it screws up some other things?
Cause of "works only once" problem discovered?
I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:
All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.
I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").
Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.
Changed over to Tytn... works perfectly without any hacks
here's my FWIW answer:
After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)
Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.
Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.
Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.
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