Did anyone get it to work on wm6.1? i install it and it installs, but when i try to go to settings it will not go any farther. I like to have in say whos calling. Its a feature i can't live without! any help would be appreciated!
wolfskin
I think this is a problem when using the "official" 6.1 base. When I load it, it freezes after the install (like when it tries to load the "Help" file) and I must SR the phone. The next boot will be fine until it seems to start the Voice Command program, at which point will freeze the device. I had to hard reset to recover.
Others have reported Dutty's and other 6.1 releases not based on the "official" ROMs work with Voice Command.
i have it installed, haven't noticed any problems or than it needs to be tweaked to anounce calls. all other features, buttons, menus work.
i cant resist this one
READ THE FORUMS
http://forum.xda-developers.com/showthread.php?t=365118&page=6
1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)
Mine works with Schaps...
I am the same way, i must have MSVC for my blutooth carkit...Schaps is the only one i could get it to work well on; however, I din't try it on Dutty's
Just Tested on Alex's WM6.1 Home BETA 2
Works Great.
No problems...works on WM6.1
OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.
Same Here, no issues (Except the caller id anouncement)
Works fine for wm6.1 and its fine with my parrot carkit actually bluetooth audio much much better now
WM6.1 VoiceCommand 1.6 US
Works fine here - in fact BETTER than with original TYTN release where it would often hang just after hoing the lookup till you hit the Red Phone Key.
Now that it sounds like BT volume is better with 6.1, has anyone taken the time to compare registry settings between WM6 and WM6.1 to see what the differences are?
asking it to play music, and than anything works for me, no issues.
Laubscherc said:
Same Here, no issues (Except the caller id anouncement)
Click to expand...
Click to collapse
Did you go into Settings-Personal-VC and check "announce incoming callers"?
Mine is working completely without any hacks.
In the official 3.03 used in Alex's 6.1 Beta 1, MSVC didn't work for me, crashed the settings.
Now with Alex's Beta 2 he used official 3.02 and MSVC works perfectly.
asfoor said:
OK Guys... Do this test... Press and say "play music", it will ask you by saying "what do you want to play?", say "Anything" ( one of the choices), and let me know if it works.
I have dutty V3 and it works fine. On any wm6.1 rom, it will freeze. That is what I am experiencing with VC.
Click to expand...
Click to collapse
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!
MELPHBOY said:
I am experencing the same issue,
I have dutty V4 and it works fine. On any wm6.1 rom, I get the Voice Command.asx error message (The file Voice Command cannot be open. Either it is not signed with a trusuted cerification, or one of it components cannot be. found. If problem persists, try reinstalling orrestoring this file). Ireinstalled several this and soft reset also, but the issue still remain.
Help!
Click to expand...
Click to collapse
Use Kaiser Tweak in disable the trusted certification.
alltheway said:
Use Kaiser Tweak in disable the trusted certification.
Click to expand...
Click to collapse
Not true....
The Voice Command.asx is NOT part of Kaiser Tweak Menu. There are only two certificates to disable or enable. Even if you were to disable both the WiFi certificate announcement or the BT Certificate announcement, the VC.asx certificate right violation still shows when you request or command the VC, and will not respond to the command.
Did you locate the certificate disable/enable on your phone Kaiser Tweak before you decided to post your response?
Unless you can prove me wrong, I AM WAITING.........
pkley said:
1.6.1722 works out of the box for me, even launches from the headset. HOWEVER, it totally doesn't recognize ANYTHING I say! Totally the opposite of my normal experience. Normally I have to install ZaJules BTCommand, enable, reset, disable, reset to get the headset launch to work.
Hmm, I'll have to try another version.
***Update***
after radio update it is working PERFECTLY! Also it does seem to make a big difference which minor version of MSVC you're using - 1.6.17913 is what I have, my manager has 1.6.4xxx and his won't work from the headset after trying all my common tricks (although he's on Dutty v4, not 6.1)
Click to expand...
Click to collapse
What radio did you upgrade to ? just tried all 3 and still doesnt work for me
Related
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Atra said:
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Click to expand...
Click to collapse
What else do you have loaded on your phone(s) that have this issue. I use VC on all WM6 and WM5 roms that I've run (and ones I've cooked, like the Crossbow Reloaded ones you mentioned) and have never had this error and I've never tweaked around registry settings. I just install the cab and it works...
Are you installing VC 1.6 US?
With all the WM6 roms i've used (not as many as some but i'm new here) I haven't had an issue with VC 1.6 US either.
don't think it's a definite answer, but i did have this problem in the past when i installed voice command on my memory card rather than on phone memory. sometimes during loadup after a soft reset i would get that error...think it's because it takes longer to load from the card and voice command is setup to run right away (always in the background)...
if it's installed on the phone memory...dunno...sorry
I run VC 1.6 US and have never had a problem with it. I always install it in main memory.
I give..
Going back to WM5 Molski. To answer some of the post..
It's VC 1.6
No other software loaded..Fresh flash.
Installed to device, not storage *only option offered for install location*.
Get a message during device install: (...recommend installing to main memory. Do you still want to install to "."...) I answer Yes because it just aborts install to say No.
Thanks for the replies guys..
<--[Totally Screwed]
OK, now I have no sound from the speakers and Mic not working. While in Phone mode, the speaker button stays in the On position and won't turn off. Got the old Voice Command registry settings in place but it seems the new problem is the culprit. Going to start a new thread with new problem unless someone has any ideas..
Closing out
Back up and functioning on Molski 3.3 Crossbow. From what I can tell, during the WM 6 load, the speaker phone option became stuck in the On position but the speakers and Mic were not functioning. Voice Command seemed to know there was a problem and gave the "..restart VC.." message. After re-flashing Molski (a few times, still no joy), I flashed with the wired earbud/Mic connected. After flash and phone restart, I removed the headset while in phone mode. Speaker button reset to normal, phone speakers/mic started working again. Reloaded Voice Command and all worked.
aaahh the joys of PDAdome.. Where else can you get the thrill of accomplishment by getting back to the same friggin place
Thanks again for the replies all..
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Give Molski a try..
Avatar28 said:
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Click to expand...
Click to collapse
I didn't have any problems with his roms (..and went back to it with no probs). Only started having problems after I tried the Faria WM6. If the Molski works for you let me know. We'll give Faria a nudge.. Good Luck!
VC issues I've run across
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
At one point I had a strange issue with the bluetooth microphone.... VC would work fine (I'd ask "what time is it" and it would tell me the time) but when I was in a call, no one could here me.... I ended up enabling and then disabling auto gain control... wallah, mic works again.... weirdness.... (don't think this was rom related)
Anyway... the roms that I've had this problem with was XDA Mobile 6 (release 1... relase 2 is kicking a$$) and I think NBD 7.1... never had a problem with a ny Pandora cooked roms.....
Anyway... my $.02... (I'll probably get change)
kudo's to the rom wizards that be...
never had a problem. Installed in a few different roms. works fine
installed to main memory.
wolverine9827 said:
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
Click to expand...
Click to collapse
Voice Command Bluetooth Fix
View attachment 43147
I can't take credit for this and I can't give credit but Thank you...!
I've used this and has worked when VC w/n initiate via earpiece.
There's several threads on the specifics of this cab.
Hi,
HTC today posted a hot fix for bluetooth at their e-Club.
Description:
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Br,
Mads
Downloaded it from HTc.cOM
Installation instructions
Follow the instructions below to download and install the hot fix on your device:
Make sure you have Microsoft ActiveSync® installed on your Windows XP PC or Windows Mobile Device Center on your Windows Vista® PC. You can find Microsoft ActiveSync from this link or Windows Mobile Device Center from this link.
Connect and synchronize your device with your PC via Microsoft ActiveSync® or Windows Mobile Device Center using the USB cable.
To download thehot fix, first select the check box below. Next, select thehot fix and the desired FTP site then click Download.
Copy the hot fix, which is a cab file, to your device.
To install the hot fix, tap the cab file and follow the on-screen instructions.
Here is the file:
http://rapidshare.com/files/77588898/TyTNII_BT_Hotfix.zip
Enjoy,
Nadavi
Extracted madsnm's posted cab, which is the same as nadavi's. This is a replacement file for OEM\OEMDrivers\TIInit_4_2_38.bts (a.k.a. \windows\TIInit_4_2_38.bts for non-chefs).
I've re-attached it as the naked file (without the cab installer or the self-extracting exe installer).
Any decent chef should be able to figure out how to turn a single file into an OEM package
Edit: Forgot to add that there are no registry entries, as I've already created registry dumps before/after install...
Edit3: It *IS* the same as the one in the AT&T 1.60 ROM. I did a file compare and there are no binary differences.
Although I am not having any problems as mentioned in the fix log, but the idea of HTC releasing something for us is great .
taiseer999 said:
Although I am not having any problems as mentioned in the fix log, but the idea of HTC releasing something for us is great .
Click to expand...
Click to collapse
Thats right!
Waiting for WM6.1 ROM! or maybe new WM06 Full Touch rom from HTC....
Just my two Cents....
Nadavi
Nadavi said:
Thats right!
Waiting for WM6.1 ROM! or maybe new WM06 Full Touch rom from HTC....
Just my two Cents....
Nadavi
Click to expand...
Click to collapse
well, 6.1 ROM doesnt really looks appealing to me, i believe most of us would want our freaking D3D driver to improve our kaiser speed.
come'on HTC, give us our driver. We want our kaiser to work @ its full potential!
almost forgot, to the brothers at the top 3 post, THANKS for sharing!
Solved my "bad" connection to the BT carset - thx....
ruffruff said:
well, 6.1 ROM doesnt really looks appealing to me, i believe most of us would want our freaking D3D driver to improve our kaiser speed.
come'on HTC, give us our driver. We want our kaiser to work @ its full potential!
almost forgot, to the brothers at the top 3 post, THANKS for sharing!
Click to expand...
Click to collapse
OT but the driver is there. Look here for more info. There's also an XDA thread on this. We just need to tweak it out for general purpose acceleration.
Sleuth255 said:
OT but the driver is there. Look here for more info. There's also an XDA thread on this. We just need to tweak it out for general purpose acceleration.
Click to expand...
Click to collapse
It doesn't say much if they hacked something for Coreplayer, or it was a general fix from HTC for all Windows Mobile devices running the MSM chipset.
Would be nice if the Kaiser was as snappy as that dual-keyboard Pantech running WM6 Standard.
I'm at loss to say if all the UI (and general system) lag is from too much use of .NET, lack of hardware accelerated graphics drivers, or Pro just runs slower than Standard because of the touch-screen support.
Hmm...wonder why i didn't get an email from the e-Club about this. I log into the site and find the fix just fine but I thought I'm supposed to get a notification about it (i'm pretty positive that was my preference when signing up)
Anyway, does this hot fix help in pairing bluetooth with car kits and devices that had problems or were incompatible thus far.
I've never experienced dropped calls with my BT connection, but I do have another problem that is pissing me off.
I have two different Pioneer stereos in two different vehicles. The AVIC-Z1 and the Premier DEH-P980BT.
When I first try to initiate a call with the 980, the connection is made, but the audio is somewhere in limbo between the phone and car speakers. There is a BT connection, but it takes about a minute and a half to actually start sounding through the speakers. By that time, the receiving end has hung up.
Since it only happens for the first call of the ride, I've been getting in the car, calling my voicemail, and waiting until I can hear the voicemail prompts. After that, I can make and receive call normally until I shut the car off.
If this fixes the problem I'm having, I'll be ecstatic.
Hi,
I have no noticable problems with BT exept the sound quality. Will be anything better or maybe worst if I install this upgrade? Does anybody have experience on it?
Thx
Mikus
NuShrike said:
It doesn't say much if they hacked something for Coreplayer, or it was a general fix from HTC for all Windows Mobile devices running the MSM chipset.
Would be nice if the Kaiser was as snappy as that dual-keyboard Pantech running WM6 Standard.
I'm at loss to say if all the UI (and general system) lag is from too much use of .NET, lack of hardware accelerated graphics drivers, or Pro just runs slower than Standard because of the touch-screen support.
Click to expand...
Click to collapse
Sounds like they had to change something with the drivers. So they're there but poorly implemented. And sounds like they'll give us driver info once its released. I'll buy it if it fixes the D3D support!
Still garbled on my Tilt with an Infinity G35..now how do I deleted the Kai6492_HotFix from my Programs directory? I can't see to find it...yet the icon is still there. Any one know?
Flapjack said:
I've never experienced dropped calls with my BT connection, but I do have another problem that is pissing me off.
I have two different Pioneer stereos in two different vehicles. The AVIC-Z1 and the Premier DEH-P980BT.
When I first try to initiate a call with the 980, the connection is made, but the audio is somewhere in limbo between the phone and car speakers. There is a BT connection, but it takes about a minute and a half to actually start sounding through the speakers. By that time, the receiving end has hung up.
Since it only happens for the first call of the ride, I've been getting in the car, calling my voicemail, and waiting until I can hear the voicemail prompts. After that, I can make and receive call normally until I shut the car off.
If this fixes the problem I'm having, I'll be ecstatic.
Click to expand...
Click to collapse
here's what causes that issue on my phone:
hit the ms voice command button and hear the beep prompt.
now hold the button down till you get the cancel beep.
now make a call. you will get no audio either direction.
turn the phone off, and the sound starts working. turn it back on and it's gone again.
key the ms voicecommand button again and let the time expire instead of holding to cancel.
make another call, and the audio will be fine, except for a 5 to 10 second delay.
see if this is how your phone behaves also. if I don't ever cancel a ms voicecommand by holding the button down, everything seems to work fine.
After installing the "fix" I could no longer use voice dial with any of my bluetooth headsets. Uninstalling the fix fixed it.....go figure.....
I think that HTC really need to have more, serious, knowledgable beta testers to tryout this stuff with various software and hardware scenarios before releasing the device. Some of these "bloggers" that they send new, unreleased devices to are either cronies or don't know much, or will not test the devices thoroughly and/or report back to HTC what problems that they experienced. I am a Verizon and AT&T user. Have seen these anamolies between diferent devices for some time now. The Mogul and XV6800 don't have the same issues we have, however, I guarantee you they do have others such as the De-activated GPS flaw that happened recently in the Mogul.
Unfortunately my Kaiser didn't work still with this hotfix. I installed on my device few times, I rebooted the headset and nothing. Probably it's like that because my ROM is 1.83, it's original polish version of it. How can I resolve the problem of bt headset ?
The fix file is a CAB (download from HTC e-club)... I install the CAB and find a link under software menu... I tap it... and another installation is done... I must soft reset the device... and stop...
Okai... so I think in this way the fix is gone... but... I have yet the cab installed under Software CAB and Installed application... can I uninstall it? The trashes pissing me :-D
or for att users go here....
http://forum.xda-developers.com/search.php?searchid=8811535
I have just upgraded to the tilt .
I have installed ms voice Command 1.6 and also the bt voice Command hack to allow voice Command to come over my bluetooth . Well it's not working . even if I edit the reg. I also tried the vc16btfix , still didn't work. is there something i'm missing ?
criddle said:
I have just upgraded to the tilt .
I have installed ms voice Command 1.6 and also the bt voice Command hack to allow voice Command to come over my bluetooth . Well it's not working . even if I edit the reg. I also tried the vc16btfix , still didn't work. is there something i'm missing ?
Click to expand...
Click to collapse
I have 8925 with Custel ROM. I've read here and there that people upgrade and install the BT Hack...
But I never had to. I had the 8525 and I remember I had to add the BT Hack (and give it like 15 seconds or whatever...) to transfer all audio to BT. But at least on my 8925, right out of hard reset, VC 1.6 works fine with my BT Headset (Jabra, Jawbone, few Motorolas, etc...all of them works fine).
Search button is a good friend on this forum it helped me find my solution for this exact same problem
Try this:
Edvard_Greig said:
Hallelujah! I finally figured it out- so it did have to do with the XCSDM setting I believe... so here is what I did for anyone else that is wondering:
1. Installed MSVC 1.6 (from the link in the TNT ROM posted earlier)
2. Soft Reset
3a. Made registry change to set Path = \Program Files\Voice Command\voicecmd.exe (no quotes)
3b. Change button assignment (assigned to Button 6/PTT in my case)
4. Soft Reset
5. Enable XCSDM
6. Soft Reset
7. Disable XCSDM
8. Soft Reset
9. Pair Bluetooth Headset
It seems to be working...the best I can figure is that when it initially gets installed the XCSDM doesn't have any value at all, but by enabling it, and then disabling it, it actually turns it off as opposed to having a null value. Also note that since I am using Alex's 'UltraClean' ROM, there were never any Cyberon installation traces, and therefore I ignored those sections.
In any case it seems to be working great and I'm very happy.
Thank you everyone for all your help, and hopefully what I listed above will help someone else.
Click to expand...
Click to collapse
found in this thread over here: http://forum.xda-developers.com/showthread.php?t=333260&highlight=Microsoft+Voice+Command&page=16
i'm using the original wm6 that came with th tilt. when I do push the button on my headset it's like all the handset volume is transferred to the headset
i had same issues then i tried the steps above and solved my problem i'm not on the original att rom anymore though i'm using dutty's dualtouch v3 rom. You should try those steps mentioned above should solve your problem if not then dunno sorry i went crazy my self trying to fix this problem then when i tried this solution it worked i was so happy all the headaches and times searching forums finally paid off LOL. Anyhow good luck.
Running Dutty's v2K fixed and . . .
no issues with MSVC 1.6 without hack. sometimes stops responding but either turning my BT off and on again, or SR fixes it. Using a Jawbone if that makes a difference.
Problem after updating to new ATT Tilt Rom
I cant use voice command through the headset anymore after upgrading the rom from HTC. What happens now is when I press the Bluetooth button it transfers any sound to the headset (Music playing from MP or in call voice) but will not allow me to use any Voice command functions.
Please HELP!!
Redundant...
Another dead thread that wouldn't have to be killed if the search function was used...
I originally posted this in the thread for Dutty's 4/29 release, but I've since had it happen in other cooked WM6.1 ROMs so I figured it should be moved out to it's own thread.
When I try to start up Garmin (installs fine), I get the splash screen and then it completely quits before anything else shows up. A few other XDA members have mentioned that they don't have problems and pointed towards checking the software that I have installed. So I did a hard reset, installed Garmin first, and then tested it after every piece of software that I installed.
It worked fine everytime so I thought it maybe just needed to be installed first to workaround any other conflicts. I happily started setting everything else up thinking that I was good to go. After I ran KaiserTweak, Schap's Advanced Config, and changed some stuff in the standard settings options, I tested Garmin again. This time, back to the original problem.
The only setting that I can think of that should matter is aGPS, but that doesn't seem to make a difference and the program quits before it even makes any indication that it's ready to touch the GPS receiver.
I'm going to keep messing with settings and stuff to see what I can find, but I figured I'd document it here for anyone else as well as see if anyone has any ideas on what settings it could be.
This is really driving me nuts.
AndyNJ said:
I originally posted this in the thread for Dutty's 4/29 release, but I've since had it happen in other cooked WM6.1 ROMs so I figured it should be moved out to it's own thread.
When I try to start up Garmin (installs fine), I get the splash screen and then it completely quits before anything else shows up. A few other XDA members have mentioned that they don't have problems and pointed towards checking the software that I have installed. So I did a hard reset, installed Garmin first, and then tested it after every piece of software that I installed.
It worked fine everytime so I thought it maybe just needed to be installed first to workaround any other conflicts. I happily started setting everything else up thinking that I was good to go. After I ran KaiserTweak, Schap's Advanced Config, and changed some stuff in the standard settings options, I tested Garmin again. This time, back to the original problem.
The only setting that I can think of that should matter is aGPS, but that doesn't seem to make a difference and the program quits before it even makes any indication that it's ready to touch the GPS receiver.
I'm going to keep messing with settings and stuff to see what I can find, but I figured I'd document it here for anyone else as well as see if anyone has any ideas on what settings it could be.
This is really driving me nuts.
Click to expand...
Click to collapse
I had same problem for some time and solved it with new version of Garmin 42030 which works perfect with any cooked rom.Send me a message to [email protected] and I will send you link for Garmin 42030.I can not post link on here.
Check your inbox
AndyNJ said:
I originally posted this in the thread for Dutty's 4/29 release, but I've since had it happen in other cooked WM6.1 ROMs so I figured it should be moved out to it's own thread.
When I try to start up Garmin (installs fine), I get the splash screen and then it completely quits before anything else shows up. A few other XDA members have mentioned that they don't have problems and pointed towards checking the software that I have installed. So I did a hard reset, installed Garmin first, and then tested it after every piece of software that I installed.
It worked fine everytime so I thought it maybe just needed to be installed first to workaround any other conflicts. I happily started setting everything else up thinking that I was good to go. After I ran KaiserTweak, Schap's Advanced Config, and changed some stuff in the standard settings options, I tested Garmin again. This time, back to the original problem.
The only setting that I can think of that should matter is aGPS, but that doesn't seem to make a difference and the program quits before it even makes any indication that it's ready to touch the GPS receiver.
I'm going to keep messing with settings and stuff to see what I can find, but I figured I'd document it here for anyone else as well as see if anyone has any ideas on what settings it could be.
This is really driving me nuts.
Click to expand...
Click to collapse
I am sending files right now.
Awesome. Thanks so much.
I'll try it out when I get home from work tonight and post back here.
Garmin Mobile XT version 4.20.50 is out
For those with Garmin Mobile XT, you can download the update from the Garmin website at
http://www8.garmin.com/support/download_details.jsp?id=3389.
It does not have the voice, help or basemap files, so this will not help you if you are trying to warez the software. You must already be an owner.
This version works great with WM 6.1, as I travel frequently and it has not had a problem with any of the 6.1 ROMs I have tried.
Good luck!
Dean
Death ROM v3.5 beta
Radio 1.65.16.25
Garmin Update
drbowden said:
For those with Garmin Mobile XT, you can download the update from the Garmin website at
http://www8.garmin.com/support/download_details.jsp?id=3389.
It does not have the voice, help or basemap files, so this will not help you if you are trying to warez the software. You must already be an owner.
This version works great with WM 6.1, as I travel frequently and it has not had a problem with any of the 6.1 ROMs I have tried.
Good luck!
Dean
Death ROM v3.5 beta
Radio 1.65.16.25
Click to expand...
Click to collapse
Thanks.I just installed update over my previous version 4.20.30 and I can confirm that works just fine.
Just installed the updated version and I"m still having the same exact problem.
Actually, now about 10 seconds after it quits, I get an error message that pops up saying "Data type misalignment at Program addess 0x03F94E04 in background thread NULL (Main InitInstance)"
Didn't get that before.
When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?
I'm using 1.6.21040.
Gave an error during installation, but seems to be working as far as announcing calls and reading texts.
I have tried to installed version 1.6.21725 and it seems to work fine, but I tried to link to the key virtually using AE Buttons, everything collapsed. The lnk file just got deleted: any suggestion.
How did you guys use to assign to a key?
Was asking the same question. Install worked with one error message. The program works when I start it manually, but I cannot find a way to assign execution to a specific button press. Looking for ideas here.
Toby
i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way
I've switched to 21725 and used aebutton plus to assign it to long press windows key, all works perfectly now.
I dont want to use aebutton plus, so I tried to use the old Long_Send.lnk and had no luck, am I doing something wrong?
or is it a diffrent name in 6.5
MSVC
I got that error too but it has stopped for some reason and now works well.
Version is v1.6.21040
I tried to upload a cab for you but it wouldn't upload.
I use MSVC for text to speech, to announce calls, read emails to me and announce calendar reminders.
This version won't read text msgs.
I don't use it for voice commands, Cyberon Voice Speed Dialer is much better for that.
mallman said:
When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?
Click to expand...
Click to collapse
mallman said:
i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way
Click to expand...
Click to collapse
WHICH LINK DID YOU USE, THE SHORT OR LONG ONE??
Thanks!
I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.
MSVC cab
Oops!
Got it.
NotATreoFan said:
I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.
Click to expand...
Click to collapse
So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.
bill340 said:
So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.
Click to expand...
Click to collapse
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.
I Think I've Found An Answer
If you go into the registry and go to:
\\HKLM\Software\OEM\VoiceCommand
and edit the value for VoiceCmdEnable to 1 (it was set to 0 on my HD2), then soft reset.
Now you should be able to get Voice Command working through BT, at least it's working for me at the moment.
It does not help fo rme at all...
No change!
Which version of MSVC do you use?
I'm not entirely sure, but in the Voice Command settings it shows v1.60.4622.0
weepatc said:
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.
Click to expand...
Click to collapse
In my case it is very similar, but when i activate voice command with the assigned button on my HD2 and not via the headset, everthing works as it should. Maby thats a indication how to get it worki`n the right way.
VoiceCommander Working
Hi,
Initially I couldnt get the BT to connect to VC (just got a BT disconnect beep in my ear).
Tried installing 2nd time (over the top), and seemed to 1/2 work but sometimes I would have to say name I wanting to dial through handset - then it would put call through BT - strange.
Finally, I noticed that if the BT headset was on when the phone was switched on (fluke that happened), it worked fine.
If the BT headset is switched on after the phone, it still plays up. Not tried turning BT on handset off and on whilst BT headset turned on yet - something to try tonight I guess.
Note : this only started working a day or so ago so not tested throughly yet.
My VC version is 1.6.4622.0.
I also noticed that on handango - a new VC version is available (updated 20/11/2009) which says works with Touch HD2 - but only USA voice at the mo so I'm waiting for the UK (hopefully released soon).
Hope the above helps.
Looks like I have an old version of Voice Command MSVC1.6.19214. How do I get a later version? Don't see why I should have to pay for it again when it is still 1.6.
Sorry, my bad - not working anymore. Worked for one day, then I get the same as everyone else