|
||||
Re: voice command not announcing incoming calls
[QUOTE=reefland;806140]
If your incoming announcements don't play, it's likely that VC is still working fine. You can test this by looking for this file on your device using FileExplorer. My Device\Application Data\Volatile\TSCallerID.wav Double tap the file to play it in Media Player, it should speak out the contents of it (last caller). If this works, then you know Voice Commander is working fine, its the phone not playing it. Thanks reefland! Your info is excellent. I have an interesting situation though. My VC works perfectly for everything except incoming call announcements. When I went to My Device\Application Data\Volatile\, there was no TSCallerID.wav file. Just one IEMoPageOver file and a lot of XMEInst01 files. That's probably at least part of the problem. Any thoughts on how to get a TSCallerID.wav to drop into the folder?
__________________
Stephen AKA WanderingMinstrel
Jornada>Apache>TouchPro>Epic 4G |
|
||||
Re: voice command not announcing incoming calls
Are u sure you have incoming calls checked in VC settings? I would think that the file would be created if this was set in VC.
__________________
Master Electrician
Last edited by dallas contractor; 03-29-2009 at 04:59 PM. |
|
||||
Re: voice command not announcing incoming calls
Yes. All VC options are checked in the VC settings, including incoming calls on the secondary page. I tried deselecting and rechecking the phone options but nothing new showed up in the Volatile folder. Possibly a new unsolvable mystery.
|
|
||||
Re: voice command not announcing incoming calls
I was having problems with this reg fix too. Three things that helped:
1) Make sure you have your phone set to announce incoming calls through the phone's speaker if you aren't using bluetooth. That was my first mistake. I had checked it once, but somehow during a reset it got set back to "Bluetooth Only." 2) For some strange reason my phone had an extra slash in the following key: My Device\Application Data\Volatile\\TSCallerID.wavI changed it to the following. Not sure if it helped or not (maybe it can recognize double "\"): My Device\Application Data\Volatile\TSCallerID.wav3) Make sure you in the Voice Command settings that you don't have it set to announce calls only during free times. Otherwise, if your phone has you scheduled for a meeting or event you won't hear the command come through. Hope this helps. Last edited by brannonz; 03-30-2009 at 01:05 PM. |
This post has been thanked 1 times. |
|
||||
Re: voice command not announcing incoming calls
Mystery solved! I called myself a few times from my landline phone last night. One (or more) of the calls left a TSCCallerID.wav file in place and it works. Reading back through this thread, I see that someone pointed out that the TSCCallerID files are self-generating when you get calls. I just don't get calls that much. The phone part is definitely not my primary use for my TP.
So I'm good to go on the suggested reg fix. |
|
||||
Re: voice command not announcing incoming calls
Start -> Settings -> Voice Command; select "Phone", press "Options", select "Announce incoming calls".
The reg hack here works nicely. I have the extra "\" noted above; removing it doesn't help and it always comes back. Like many systems, extra slashes are ignored here, it seems. I finally figured out how to get the TP to vibrate and announce the incoming call. Set the system volume to "on" (something above vibrate), and then in TF3D settings -> Sound, set "Ring Type" to "vibrate only". That way you don't have to actually have the ringer on to hear the announcements. If you set the TP to vibrate mode, it won't say the name/number. |
|
||||
Re: voice command not announcing incoming calls
Quote:
|
This post has been thanked 1 times. |
|
||||
Re: voice command not announcing incoming calls
use phm regedit. when you first open it, it should say my device with a plus. click the plus and four options are available. click the plus by hkey_current_user and follow all the directions from the post you quoted and you are good to go. if you need more help, post back here.
|
|
|
|