• Question

  • I have a little suggestion for which ever team is responsible for Microsoft Windows Moble Voice Command.




    Increase the font size by 10, bold it and add please to the end of it!


    It's been over a year since MSVC 1.6 has been released and still no solution to getting it to work on newer devices using mono bluetooth headsets. Yes I know the website states that on newer (getting older) devices like HTC TyTN ect , the audio comes out of the device speaker, and yes I know it also states the same for older revisions WM6 OS versions but that's total B.S. I wish my life was that easy, I could use that same approach for work, I could post little messages like that to on my desk. "Any request sent to this mailbox from a corporate address results in no response", "The occupant of this chair is available between the hours of 11:00am to 2:00pm"


    Seriously, it's been frustrating and not just for me, do a search on the web for Microsoft Voice Command 1.6 and you'll find posts everywhere about people wanting a fix. I know HTC and other vendors changed the way things work with the Bluetooth Audio Gateway but it's still fixable, Cyberons Voice Dialer works fine so they obviously worked around this problem.


    The frustrating thing is I upgrade to Voice Command 1.6 a month before I upgrade my HTC Wizard to an HTC Trinity. It was working great on my HTC Wizard and I was really happy at the improvements over MSVC 1.5. Bluetooth dialing, much better recognization, announcements to my BT headset was awesome when I was in meetings and driving, never had to look at my phone to see what a message was about or who was calling. Wish I could say the same for my HTC Trinity!


    Microsoft Voice Command is such an awesome program, everyone I know who's used it can't live without it. Some of my colleagues who were getting caught in the IPhone hype and were thinking of getting one couldn't because they didn't want to lose Voice Command (at least the ones with older devices who have it working). I've been looking everywhere for some kind of solution so I know Microsoft has big plans for MSVC on windows mobile, creating an API for software developers to use expanding it's functionality to virtually any application. This is awesome and probably it will be fixed to work with mono bluetooth headsets then, or maybe not but I hope so. Why do we have to wait that long, this should have been fixed months after the program was released so if anyone on the Microsoft Voice Command team see's this, I say again with PLEASE PLEASE PLEASE PLEASE.....





    Sunday, November 4, 2007 5:51 PM

All replies

  • I'd like to add my voice to this chorus!  My device is not a phone, but it is bluetooth enabled.  Apparently, because of this fact, MSVC will not function on it.


    Aside from this fact, I love my iPAQ... but I'd love it a whole lot more if the copy of MSVC that I bought (and loved) for my Toshiba e755 worked on my shiny new iPAQ hx2415.


    Voice Command was one of the coolest apps to ever come along for the Pocket PC/Smart Phone.  If there were a version that worked with my iPAQ, I'd buy it in a second!


    Side note: I ditched my Toshiba because the company didn't stand behind its product.  I've sworn off Toshiba for that reason.  Many others in the Pocket PC community did, as well.  Today, Toshiba is out of the PPC business.  I would hate to think that Microsoft wouldn't stand behind Voice Command, a very fine product, indeed!

    Wednesday, November 14, 2007 1:54 AM
  • I just purchased a new XV6800. I do not mind the voice recognition if you already have the person in your contact list. The really upsetting issue is that a new law will go into effect in many states requiring completely handsfree operations.


    If I do not have a contact in my contact list and a tag assigned, I cannot instruct the phone to do "digit dial" or "call" 555-1212 for instance.


    All new phones should have the ability to download an update that allows full handsfree voice recogntion through bluetooth devices. Short of that is a violation of the new handsfree laws coming into effect.


    Even the bug in the Microsoft Voice Commander 1.6 violates the law.


    With the amount of high tech coders, I am suprized that no one has written the code to fix this issue.


    Shame on you Microsoft. Fix this code as this is an embarrasment to your company and highly limits these very expensive devices.


    I hope that some Microsoft engineers read these posts. It would be helpful from a public relations standpoint that there would be Microsoft engineers reading the posts and acknowledge the problem and give a timeline on when the issue is expected to be fixed.

    Friday, December 7, 2007 7:40 PM
  • i have the 6800 from verizon and voice command works hands free with my bluetooth headset.  i had to do a bunch of stuff to make it work, if you search the forums you will find the fixes.  to make it work i had to disable the confirmation when dialing because the bluetooth ear piece does not let you respond to the voice commands questions.  you can issue single commands completely hands free though.  i is frustrating still, even though it works to a 'limited' extent, and quite rediculous as well, that there is not an official fix to this problem.  it can't be that hard to fix.

    Monday, December 10, 2007 2:25 PM
  • If you have been able to make it work on your XV6800, then you would be a great contributor if you documented the step by step process to make it work.


    A good example is when the iPhone was cracked. He published step by step instructions on how to make it work.


    What would be also helpful is if someone would actually code a patch that can be applied to VC 1.6 without having to edit registry entries.


    Anyone up to the challenge???



    Monday, December 10, 2007 7:18 PM


    Please! This is almost a deal breaker for me with my new XV6800 (HTC TITA100). I was so pleased with this device until I found that Microsoft Voice Command doesn't work through bluetooth. I might just return it and keep using my XV6700 (which works great with MSVC 1.6). Microsoft has done an excelent job of developing voice recognition technology for the Windows Mobile platform, only to shut it down by not testing it with current WM6 hardware.





    Thursday, January 3, 2008 5:22 AM
  • I have the Verizon XV6800 as well, and voice command does work, but only partially.  The "bunch of stuff" you had to do DOES NOT MAKE VOICE COMMAND WORK as you posted, but rather it handicaps voice command so that it works in a limited manner by turning OFF the dialing confirmation prompts.  Therefore, with calling confirmation prompts off, voice command will work and dial (without confirmation), so if it mis-hears what you requested, you have to force the phone to disconnect and try again.


    Microsoft really needs to address these Bluetooth issues and release version 1.7 of Voice Command.

    Wednesday, January 9, 2008 8:33 PM

    I'd settle for 1.6.0001 with working bluetooth on mono headsets Smile


    It really a shame, a year since it's release and still no fix. I can't tell you how wonderful it was when I had it working on my old K-Jam. To hear an incoming call, email, text message when in a meeting, or when driving or making a call in the car with the simple click of the bluetooth headset. Not to mention how many people were sold on PPC devices just by initiating a call in their presence.


    I really hope someone at Microsoft is watching this thread and working on some kind of fix instead of waiting for the next mature release. This should have been addressed half a year ago!


    Thursday, January 10, 2008 6:23 AM
  • Proud to be a Verizon XV6800 user.


    The interesting thing that I have found is that 60% of the functionality for Voice Command is absent.


    As previously mentioned correctly, you can turn off comfirmation, but that is risky if the announced dial name is heard wrong.


    One thing I loved with my 6700 and VC was notifications via my head set (Jabra) for incoming calls (who is calling), calendar items and daily tasks.  I don't get that anymore.  However I gave my 6700 to my daughter (movies, music, chat, email ... she loves it) and we upgraded the OS to MS Windows Mobile 6 along with all the HTC plugins - including the HTC CommManager plugin.  She is able to get announcements and notifications via VC.  It use to lock up on me.  I suspect because it would run out of memory space to operate.


    I am wondering though if this is not more of a 6800 OS issue.  With the BT device, it does not appear to be actively paired at all times - only when I activate the BT to make a call or start an app.  This is also true with my Motorola BT device.


    I would appreciate it if anyone could correct me on this thought.


    I suspect that if it is only paired when you push the BT device button we would need an upgrade to the OS pairing algorithm.  I think the HTC CommManager plugin may provide this, but I don't want to install it quite yet to test that theory.


    The 6800 CommManager logic may be intentional to save power on in some clever way.  I don't see a real power savings though since my BT device is on - pinging away and my 6800 BT mode is live.


    Just trying to think though the nonconformance.


    Hope I am not be convoluted.  Any thoughts?

    Wednesday, January 16, 2008 4:45 PM
  • I simply want to add my voice to the request "FIX MICROSOFT VOICE COMMAND 1.6 TO WORK WITH MONO BLUETOOTH HEADSETS!"


    I bought mine two days ago; it was advertised at being compatible with my device.  The use of hands-free functionality is required by the laws of my state and mvc doesn't work.  A call to MS tech support was useless as they'd charge me more than the software costs.




    Thursday, February 7, 2008 6:42 PM
  • Guess what?  MVC doesn't allow hands-free dialing with stereo headsets, either.  It cost me $130.00 to find this out.


    Sunday, February 10, 2008 5:30 PM



    I would like to add my voice as well.  I had an i730 and loved it.  Now,  I have a Tilt and have been pleased with the improvements and fustrated as well. It like buying a Porsche and having to put doughnut tires on it. ( I have a MotoRokr too and would like that to work too)


    Please, Please fix it. 





    Monday, February 18, 2008 2:10 PM
  • It’s ridiculous.  Microsoft owns the OS the device is running, owns the application, and can’t make the two work correctly.  What trash.  It’s really ashamed when end-user’s have to keep fiddling to make things partially work when MS and others are getting paid for the software. 


    It’s this kind of thing that really makes me want the Google phone to arrive.  At least they will have an open platform where everyone can contribute and benefit. 



    Friday, February 22, 2008 9:44 PM
  • I have a 2 month old AT&T Tilt and a 2 month old Jawbone BT headset.  Acquired the Voice Command 1.6 4 days ago.  Everything works perfectly EXCEPT the Caller ID. Does not work on either the device or the BT.  Is it something I am doing wrong or is it a software problem?  I've tried Microsoft (they want $259 to talk to me), I've tried Handango where it was purchased (they sell them, they don't fix them...contact Microsoft) and even HTC the phone mfg. (they suggest reading blogs).  After reading over 1000 of these entries I still have no idea what to do.  Does ANYONE have a suggestion?


    Thursday, April 3, 2008 8:37 PM
  • Count me in too.  Shame on MS.  I had the same wonderful pairing of XV6700 and VC 1.5 (not even 1.6) and the thing was virtually a BANK VAULT of reliability.  I don't have the time in my day to repeat a contact's name (the results not even close) 10 times and finally having to manually dial the person or pick them out of my calling history list; yeah, while driving; part of the job.


    This is the MOST AGGREGIOUS, INFANTILE, SELFISH BEHAVIOR I have experienced since I shelled $5k out for my Dell XPS700 and it took Dell 1 year to acknowledge that the motherboard in over 2 million of them (all, essentially) had a defective RAID CONTROLLER on the Motherboard.  It took them so long to "Come to Mama" that the 590i SLI motherboard wasn't even available any more and they had to replace those 2 million machines with NVidia's newer 680i SLI NForce motherboard and all the ancillary stuff that had to install with it.


    You'd think that Microsoft would learn from Dell's billion dollar gaff, but STUPID IS AS STUPID DOES, thanks "Forrest".


    So, the next time you have a choice of phones and operating systems, what are you going to do ?  I'm fermenting that one right now.  Nokia had been working Symbian for the last 7 years.  Why not ?


    As a side, while Dell grovelled at how they were going to make things right, a 20 year old kid at PC Club built me a clone with that same 680i SLI motherboard, stuffed with enterprise WD drives and dual 8800 GTX graphics cards and all the fixinings for my HiDef editing in less than 7 days !!!  Oh, man.  The thing screams through heavy loads and is stellar.  Now, I have two machines and the clone lays a whoopin' on the machine from Dell, even with the new 680i SLI motherboard replacement.


    Maybe all the development team is so old that they are demented at this point and can't remember what they coded.


    I'm out, until there's a fix; and I'm eyeing my XV6700, so I don't kill myself on the road or take someone with me when I do.


    Cheer$, MS,


    Monday, April 21, 2008 8:54 AM

    I am surprised I never saw this thread before. I know for a fact I have posted in these forums before regarding the issues raised here. I too had a stellar performance with my PPC6700 (Sprint) and VC 1.6. They worked so well I was really impressed. Then I upgraded last June to the PPC6800 (Sprint Mogul) and was so disappointed to find out that VC 1.6 did not work as advertised. Imagine my surprise. I thought when you upgrade on the hardware that the software should really work seeing that the software was a fairly new release. But no MS continues to drag their own name in the mud by doing ill planned things like these. Like releasing new hardware and OS without properly testing their previously released software programs to make sure they work as well as they did on previous hardware and OS. One should not have to tweak VC 1.6 to get it to work. I read several threads and posts on some of my favorite cell phone chat sites and found the only fix to this to be turning off confirmations. Therefore by turning this off, you don't get any text message notifications over BT, you don't get any calendar announcements over BT. You certainly cannot confirm the name of the person you requested to be called over BT and the list goes on of what cannot be done over BT. The whole reason I purchased the software was to use it with BT. I agree with most of your posts about how MS has been dragging their feet with regards to addressing this problem. But alas they have finally addressed it.


    After all this time they have indeed addressed this I believe. I was checking my account on Sprint's site and there was a link for support I clicked it and there it had something for checking updates. I clicked that and to my surprise it took you to HTC's site and there was a new ROM release. Now, I don't check the cell phone chat and forum sites with the frequency I once did when first upgrading to my first 3G phone some 4 years ago. But after seeing that on HTC's site I immediately I went to one of my favorites PPCGEEKS.com and found that there was a new ROM released by MS and that HTC had it for downloading. I read many a thread about it and what this new ROM was supposed to mean. Finally I took the plunge the other day afer much deliberation and found that yes for once MS was listening however slow they were to react. They listened nonetheless. I downloaded it from HTC's site.  The new ROM 3.35.651.2 seems to have fixed the problem with the bluetooth stack. I can now respond when asked mobile or home number. I can answer yes or no if it found a number. I haven't checked the other things that VC 1.6 is supposed to be able to do yet but I will.

    Wednesday, April 30, 2008 7:56 PM
  • OK, for those of you with the 6800 (XV, PPC, etc) and MSVC 1.6, and we all have the exact same symptoms, I spoke with an HTC tech today.  He said that they were reworking the firmware to address all the issues (he didn't offer it up right away).  He said that they had expected to release it in mid-May, but the issue has become more complex than originally thought (you know how you can have oblique problems when you change one thing).  Well, he wasn't exactly precise with the date for the Firmware upgrade to be available, but said, "Mid-July" should be the latest date when it will be ready from all that he had heard.

    Yes to all your wonder that every vendor, the OEM and Sturdy ole Microsoft know about it.

    I was really impressed by the ealier poster who said Cyberton (sp) had managed to design their Voice Commander & Voice Command products to manage without all the memory requirements.  The problem is, that this Taiwanese company refuses to make their products available for retail sale; they are ONLY delivered on certain devices (Smartphones/PPCs).  That seems awfully shortsighted to me, when they exclaim that the products work on nearly every platform from Symbian to Win6 (and all the Mobile Win products).  Maybe if enough of us "bang on them", they will see the dollars breaking their doors down.  I encourage each of you to spread the word and leave a "plea" on their website.

    For me, it's off to my Verizon Store to get my XV6700 reactivated and the XV6800 sent dormant, until the Firmware is out and verified to be stable, unless Microsoft and its VC team can find the time to slim down the current version and give us an update that works.  Whatever, on go the lights of my Bank Vault reliable XV6700/VC 1.5 combo; and off with the lights on my XV 6800 for now.  What a travesty.  At least Microsoft gives us these forums to exchange ideas, answers and verify "gaffs" in their products.  Try to do that on Verizon's site.  Hah.  Great network, service, stores & staff, absolutely inexcusable excuse for a knowledge base or user forums (non-existent) to match their sites ridiculous navigation.


    I hope this helps those who have this specific hardware/software issue.


    Don't forget to inundate www.cyberon.com with your "pleas" for retail packages for us.  Microsoft just might take this one in the undergarments, if Cyberon comes to the rescue.




    Saturday, May 3, 2008 3:25 AM

    Your comments are only partially true.  MS does own the software and DID own the OS but many hardware manufacturers do not use the OS "out of the box" but customize it for their device.  In addition MS has no control over the firmware and can not force harware manufactures to comply with standards. 


    If you are familiar with how voice recognition works, you would know it is done through sampling and pattern matching.  Many of the complaints stem from mono headset and bluetooth both of which tend to have either 8 bit sound encoding rather than 16 bit.  Bluetooth is also subject to "noise".  I have 2 phone and same bluetooth headset is almost unusable with the one and crystal clear on the other.  On the "bad" phone, the headset and phone must be within perhaps a foot for it to work.  On the other i can easliy walk around the room without an issue.


    MS made it clear upfront that there were issues with this software and certain hardware.  It's the same "driver" issues that always arise with an operating system. 

    Friday, May 30, 2008 4:20 PM
  • John B,


    If I didn't know any better I'd say you're the MS Voice Command Apologist. ;-)


    I'm very familiar with how voice recognition works.  The main issue that we are all describing does not arise from bluetooth interference, S/N ratio for the bluetooth connections, sample rate, or other bluetooth mysticism. 


    When MS released Windows Mobile 6, the Bluetooth stack and communications simply were not 100% compatible with the previous version.  People like me are using MANY different types of bluetooth handfree connections, on relatively the same hardware platform; only the OS is different, different enough to break Voice Command for the simplest of operations.  When OEMs received the OS to load on their phones, there was a basic BT connectivity for headsets (which had been upgraded by MICROSOFT to allow for the BT 2.0 protocols).  Microsoft needs to upgrade Voice Command to be compatible with the BASE Windows Mobile 6 OS.  Pretty straightforward.

    Saturday, May 31, 2008 1:23 AM

    Hi guys,

    I too have the same issue. cant really get voice commands to phone via bt headset.

    I am using the samsung i900 using wm 6.1 but with a stereo bt though.

    dont think all manufacturers have pedged not to comply with ms standards (to make sure vc works with bt)

    most likely problem with wm. its a long time no one posted. have you got a solution ?

    Wednesday, December 10, 2008 1:13 PM