My VoiceCommand OEM Fixed

crawrj · #1 (**permalink**) 03-05-2007, 04:18 PM

OK the OEM is working now. I was able to fix the Media Player commands problem. The only thing that is bothering me and I have made so many changes I can't remember if it was always like this. Using IDTransfer when and incoming call comes in I only hear the announcement if the volume is up. If I have it on vibrate it doesn't tell me who is calling. I thought this worked before but can't be sure. Can anyone else tell me how theirs is working? Thanks for the help. I have uploaded the new rgu file to ftp.

**jamesus** · #2 (**permalink**) 03-05-2007, 06:58 PM

I am using colonel's currently and I think when it is on vibrate or the system sound is turned down, the announcement does not come through...

crawrj · #3 (**permalink**) 03-05-2007, 08:33 PM

Thanks for the feedback. It is appreciated.

nikki2beeps · #4 (**permalink**) 03-06-2007, 08:54 PM

Wow! crawj you rule, I havent reflashed to test but nice job. I wonder if you could let us know what the problem was? I greatly appreciate all the work in getting this done but what you learned could help others in making their own OEM's. Was it a whole diffrent registry export or was something not exporting correctly from the stock cab etc. Thanks in advance for your time.

crawrj · #5 (**permalink**) 03-07-2007, 12:09 AM

Quote:

Originally Posted by nikki2beeps

Wow! crawj you rule, I havent reflashed to test but nice job. I wonder if you could let us know what the problem was? I greatly appreciate all the work in getting this done but what you learned could help others in making their own OEM's. Was it a whole diffrent registry export or was something not exporting correctly from the stock cab etc. Thanks in advance for your time.

I am not certain yet. It was a registry setting but I haven't compared my old one with my new one to find the difference. I did a before dump installed voice command and did an after dump. I then took the new reg entries and made the .rgu Once I get a chance I will compare to find the differences but if you copy just the .rgu file over everything should work fine. I don't if this is the same with all the Voice Command OEM's but this one also works for announcing calls over bt. You don't need IDTransfer installed.

**colonel** · #6 (**permalink**) 03-07-2007, 12:56 AM

No IDTransfer needed? Wow. If you want, just post your reg dumps and I will go through them. Plus it will give me a chance to compare to my stuff.

crawrj · #7 (**permalink**) 03-07-2007, 09:58 AM

Quote:

Originally Posted by colonel

No IDTransfer needed? Wow. If you want, just post your reg dumps and I will go through them. Plus it will give me a chance to compare to my stuff.

You can grab the .rgu from the VoiceCommand folder in Kitchen OEM. Thanks for going through it.

crawrj · #8 (**permalink**) 03-07-2007, 10:02 AM

OK This is a stretch but somebody give this a try for me. I don't think we ever needed IDTranfer but maybe I am wrong. Somebody flash their phone with one of the roms that include voice command. Colonel if you want to do this with yours it would be great. Once it is up and running set your volume for both phone and pda to the second notch. Call the phone and see if vc transfers callerid to the phone. If it does now turn it up and see if it still does. What I found on mine is that if I tried it with the volume up too loud it would not work. It would kick it right back to the phone. But if I did it on a low setting it worked. And after it made its first connection you could turn the volume to anything you wanted. I appreciate the assistance in determining whether this works on any other roms.

xyzzy · #9 (**permalink**) 03-07-2007, 01:15 PM

As long as you guys are tinkering with the registry settings for Voice Command, you may want to try making this change...

Try changing HKLM\software\microsoft\voicecommand\speech\Reject ionThreshold

from 45 to 10

This setting determines when Voice Command says "Please Repeat". If the confidence score from the recognizer is below that threshold and above the ignore threshold (10) it will ask for a repeat. It turns out the engine is getting it right plenty of times and we're throwing away a perfectly good recognition because this threshold is too high. Change it to 10 and you might find you get better accuracy.

Another one you might want to set:
HKLM\software\microsoft\voicecommand\speech\Blueto othPTTDelay

this one isn't actually set anywhere by default, but it does have an impact. By default, when initiated via bluetooth, Voice Command will open the bluetooth audio gateway, and then wait for 400 ms before playing the audio indicator. Well, on the jawbone, it seems that keeping the audio channel open a bit longer improves accuracy. Also, this value is apparently too small on some headsets and results in some people not hearing the audio indicator. So you might want to try setting this value to 2000 (the maximum), which will cause VC to open the audio channel, wait for 2 seconds and then play the indicator.

**luv2chill** · #10 (**permalink**) 03-07-2007, 01:24 PM

Nice to see you here xyzzy. Thanks for the "insider" reg hacks!