|
||||
In a nutshell,
I installed VC the normal method deleted the entire VoiceCommand registry key under HKEY_local_machine/software/oem/ removed everything under the startup directory except for VC (In the windows directory I made the VC link point to the VC executable located in the Program Files directory... and I added a link to it in the startup directory) Then installed the Sp1. Seems to work fine for me. |
|
||||
I'm thinking that many of us tried to run the Trial Version, then realized that wouldn't work and also tried uninstalling/reinstalling (which perhaps broke some registry keys or pointers -because after that your "given method" didnt work) then I found I could get it to work by doing what I said above.
|
|
||||
Raging Idiot: You shouldn't need to do that and the other stuff should just work. I know Colonel's roms have adopted the same format for install and he's using the same reg keys and file sets that I sent out some time back so it's not just isolated to this rom. On your next hard reset, try just copying the exe and creating the shortcut, soft reset and odds are it will be working. If your deleting the keys at: HKEY_local_machine/software/oem/ then your going to mess with the button mapping and need to re-map it. Instead just cahnge the path value from the exe to be blank. Also if your removing eveything from the startup, then you may have issues with the mail app as it would no longer be running at stratup as well.
There is a possiblity that they changed something in the VC install, but I have not heard of any changes to the app. If your installing 3rd party apps, hold off on them until after you check VC. -saridnour |
|
||||
Okay. Finally got it working. Had to install it again. then did a reset after the software prompted for it.
I copied the .exe to the windows dir and all is working now. Also, I had to register Wisbarlite before I could get it to work. Not sure why. I am using a vzw xv6700 |
|
||||
PPCFreak: Are you installing Voicecommand, saving off the exe doing a hard reset then copying the exe back to the windows dir and shortcut to the sindows\start up dir? If your just installing and copying, then your just installing the app and not using whats built in (also taking up storage space). Not that it's that big of deal, but if your trying to cut down on storage space usage all you really need to do is get the exe in the windows dir and start up shortcut after a hard reset, no other loading of bits to the storage area or overwriting of reg keys. As to having to register wisebar. Its possible that the app expired if you did not set the date and time when your hard reset. I was guessing that some trial stuff could expire if it saw one date at reset then another a year or so later after syncing thus exprieing the trial.
-saridnour |
|
||||
I installed the app to the memory. I copied off the exe but have not done the hard reset yet (this is the 2 soft keys (2 "-" keys) plus the softreset button correct?).
Plan on doing that later on. And yes, I understand right now I am taking up extra storage space (which is at a premium since there isn't all that much to begin with). Currently, just using the voicecmd.exe out of the windows dir (where I copied it from). This would be using your custom button mapping correct? |
|
||||
PPCFreak: Hard reset two front soft keys + the reset button. Will confirm with a screen asking if you want to clear it. You should have also seen this when you installed the rom or you may have other issues still on your device! YOU MUST HARD RESET. When you hard reset, it will clear all reg values, apps, shortcuts, etc from the device (not storage card) and will go back to the rom default values and locations. Thus moving the exe back to the windows dir (and startup) at this point should be using all default (unmodified) values. When you installed the app it reset all reg values, mapping, etc so you are using a different config now than the defaults.
-saridnour |
|
||||
start/settings/personal/buttons ...that'll put you were you need to be.
I put button 1 (windows key) to be voice command. Works great. Doesn't matter that I deleted the registry key for VC under software/oem/. |
|
||||
Ok, this is weird. I made the change Raging suggested, setting the announce destination to bluetooth when available. Now, the announcements alternate. First call, to the phone speaker, second call, to the headset and so on. Any ideas?
jim |
|
|
|