Database Develop

Voice Commands Over Bluetooth Works on TuMa v1.3 - WM5 ROM

I have posted This thread to assist anyone like me, who is not a programming whiz. Got to Install this mainly through trial and error and I am not an expert in this. So If anyone can make my steps easier please do!
This is a Variation Installation For a thread a while back in October 2005 Author Ncruz and effjay. Ncruz Posted a wm5 cab. This cab does not install directly due to permissions. However I have extracted the files using windows cab manager.
First are the files are required in windows. If it asks about permissions copy to PDA root folder then copy with Resco File Explorer and overwrite. Next are the registry files. You can import them with a registry program such as tre or regedit.
If you want Microsoft Voice commands to be the default program overwrite SSDialer.exe in windows folder with Voicecmd.exe from Program files/Voice command/ otherwise Cyberon Voice is initiated when you press headset.
I will post the cab in its entirity although it will not install, incase someone knows an easier method to get voice commands working Please contibute to this thread. However this method worked for me. Below in the zip are the files Extracted with Win Cab manager in zip format so you can copy zip to your pda then extract them to the correct folders, along with the registry files you need to import to registry.
N.B..sound of Voice commands is through PDA and not headset. Pressing headset connect button opens Cyberon or active voice command depending on what you have

Can not seem to be able to import the reg files....

OKay, got the files to import and the files copied - no go for me. Darn-it.

Installation
did you do a soft reset with the software built with the rom and repair the bluetooth headset

I might have reset without using the software reset....
However, got it working with this cab file that I found on my storage card. I even got MS Voice Command to work when I hit my BT Headset button.
Heck, it did not even change the record button to SSDialer! I would have thought it would but it did not. So, I am happy!

glad its working for you

now how can i do?
download odie3 's cab file and install? that's right?
Then, when device auto turn off, bt still go off as before?

I can't download files..... Where can I get them?

Re: now how can i do?
kriengkrai said:
download odie3 's cab file and install? that's right?
Then, when device auto turn off, bt still go off as before?
Click to expand...
Click to collapse
The only way I know how to keep BT on is by plugging in my Device to a power source and doing a soft-reset. As long as I do not turn it off with the power button or have it set to auto-power off while plug in, BT will stay on. I do this everytime I get into my car - since it takes me a hour [sometimes more] to get home, so my BT Headset always works.
Hopefully I explained that correctly for you to understand....

Odie
Your query confirmed. The Wlan manager icon from the today screen goes as a side effect of installing the cab. Wifi still works but the Icon in today is not there. Not a big deal for me, as I have skinned my Pda with Wisbar, which has a wifi icon.

Re: Odie
MOHDWADEA said:
Your query confirmed. The Wlan manager icon from the today screen goes as a side effect of installing the cab. Wifi still works but the Icon in today is not there. Not a big deal for me, as I have skinned my Pda with Wisbar, which has a wifi icon.
Click to expand...
Click to collapse
Yes it happened to me as well, but i prefer BT Voice Command Activation than WLAN icon
Thanks for the info

BT activation doesn't work for me...
For some reason the activation through BT headset doesn not work for me.
I'm using WM5 TuMa 1.3 ROM.
The BA_WM5_Voice_Dialer_2.cab doesn't install on my device (permission violation), so I copied the files manually to the Windows folder.
The reg files also don't import to my registry when double-clicking, so I made the changes manually.
It still doesn't work.
Now, when I hit the button of my BT headset (Moto HS-810), the standard dialer is activated (instead of the voice command app) and I hear hissing sounds in the headset.
I tried it both with Cyberon and MS apps. Both don't work.
Did anyone encounter this problem? Anyone solved it?
Thanks.

anyone knpow how to do this with voice command on 2003se?

Just upgraded to TuMa 1.3 and have found a MUCH more simple way of doing it.
1) Install Microsoft Voice Command
2) Download Total Commander (http://www.ghisler.com/ce.htm)
3) Using Total Commander change the read only tickbox for \windows\sddialer.exe so that there is no tick (1 press just greys it out, i needed to press twice) <- browse to \windows in TC and right cick (hold down) on sddialer.exe, and click properties.
4) (you don't need TC for this) Copy %install dir%\voicecmd.exe (where %install dir% is the directory you installed voice command to) to a temporary location and rename it to sddialer.exe.
5) (using TC) 'Right click' on your new sddialer.exe (previoult voicecmd.exe) and select 'cut to clipboard' then navigate to \windows\ and 'right click' and select 'paste from clipboard', when propted overwrite the origional file.
6) press the button on your headset and test it!
the only thing we need now is for some clever person to work out how to route the voicecmd audio through to the headset instead of the load speaker (to my knowledge it uses the microphone on the headset allready (at least it works when i speak quietly from the next room )

it works like a charm
cheers

Do what Midlet says?
If I do what Midlet says- will I still need the 2 files that mohdwadea has posted? Is Midlet's process a complete stand-alone process... or is if preceded by more steps?

Re: Do what Midlet says?
sgrbhtngr said:
If I do what Midlet says- will I still need the 2 files that mohdwadea has posted? Is Midlet's process a complete stand-alone process... or is if preceded by more steps?
Click to expand...
Click to collapse
Have not investigated midlets way of installing as Mine is working. However i suggest that if you check your registry and see if the reg keys i posted within the zip are there. If his way works fine, if it does not i suggest you import the keys into registry and see if that helps. I also strongly suggest you make a note of the keys and where they are imported too, as if it does not work you can remove them.

It worked
Mohdwadea,
Your method worked! This time I performed a soft-reset after the installation and also re-connected the headset. I did not have to go he registry-entry route because the cab-file installed on my device.
This will help me a lot on the road in business. God bless you.

Just glad its working for you!

voice not sending
MOHDWADEA,
I am using this fix a lot on the road. It works very well... expect for in one situation! I can initiate voice dialing by the record button on my device and it accepts voice dialing commands through the bluetooth headset and teh call goes fine.
However, if I initiate the voice dialing using the button on my blueooth headset (Cardo Scala 500), it initiates the voice dial app just fine, accepts commands and conencts the call.... but the other party cannot get my outgoing voice through my bluetooth headset, rather it gets the voice from the mic on my phone. Also, the incoming sound can be heard in my bletooth headset but ALSO on the phone.
Any suggestions?
Thanks!
Sagar
I-mate PDA 2K
WM5 TuMav1.3

BT Audio Streaming + Voice Command

Just sorted BT voice dialing on my TRINITY witha Jabra BT250 all working fine
using the infor here:
http://forum.xda-developers.com/showthread.php?t=281977
I've also mastered using BTAudioOn.exe in the registry in place of the voice dialer to give me Audio Streaming
Only problem is, as the article in the forun suggest it disables the voice commands!! I can live with this as I only want to stean the TOMTOM voice when using the satnav while walking or on my bike.
What I had in mind was a a couple of icons, one to make the registry changes for the BT Audio streaming and the other icon to toggle back (ie change the registry back to voice comand via the BT headset). As far as I can see (once BTaudioOn.exe is copied to my Trinity) the only difference between turning my Jabra BT250v into an audio streaming headset and a phone headset are the two registry changes; and then change them back to give me a Phone headset again.
Can anyone tell me if this is possible to use a .REG file?
Can it be written on a PC and then copied to the Trinity so that it runs?
Will reg files run the same on a PDA and they do on a PC?
Thanks in advance

Try to use SKSchema software, it can put any values in registry depends of any window or process runing on the device. It watch & if you made a rule to put in registry key voicecommand with launcheAppEnable zero as window of TomTom appears u can get a continiusly sound in handsfree if also it put long value in Duration option.

Where do I fond the software please

Also... could you please explain a little better a I don't understand what you have written...sorry!

http://pocketgear.com/software_detail.asp?id=20385
& read help in windows directory after install

Summarized procedure for getting MSVC 1.6 to work with Kaiser

No attempts to claim credit for inventing this process (the PTT fix is in the Wiki, and the Cyberon bit has been around since the Wizard days), but this could be the first time it's been completely posted in one place.
Cheers!
-------------------
Step 1. Disable Cyberon
- Delete SDDaemon.lnk in \Windows\Startup
- Delete the Voice Dialer shortcut from \Windows\Start Menu\Programs (or whatever submenu folder it might be in)
[NOTE: if you don't delete the shortcut and accidentally click it (or launch the program directly from File Explorer), you may have to repeat the ENTIRE procedure]
- In each of these registry locations:
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Extensions \ ContextMenus \ Contacts \ Main_ContextMenu
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Extensions \ ContextMenus \ Contacts \ Main_Tools
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Extensions \ ContextMenus \ Contacts \ Summary_Tools
----> Remove this key entirely: {2C0E9904-F32D-4f53-875F-479F5CA81E18}
- In this registry location: HKEY_LOCAL_MACHINE \ ControlPanel
----> Remove this key entirely: VoiceTagCPL
Step 2. Disable PTT and Enable PTT Button
----> Remove this key entirely: HKEY_LOCAL_MACHINE \ Services \ PTT
From HKEY_LOCAL_MACHINE \ Software \ Microsoft \ Shell \ Keys
- Add a new key called "40C6"
- Add a string under the key called "Name" with the value "Button 6"
- Add a new key called "40C7"
- Add a string under this key called "Name" with the value "Button 6 (hold)"
Step 3. Install MSVC 1.6
- Be sure to use the latest build, which can be found at http://www.sendspace.com/file/f48smf
< File Name: MSVC_US_PPC 1.6.17913.CAB Size: 3MB >
NOTE: this is licensed software; you should only download this update if you already have a licensed copy of MSVC 1.6
Step 4. Remap MSVC to PTT button (optional)
Step 5. Pair your headset
You should now be able to initiate MSVC from your BT headset and receive prompts thru its speaker. Finally, I can leave my phone in the case when I want to!
Enjoy!

BT button VC1.6 Activation
I have a HTC branded TytnII and there is no PPT reg entry. Also the keys
From HKLM\Software\Microsoft\Shell\Keys
- Add a new key called "40C6"
- Add a string under the key called "Name" with the value "Button 6"
- Add a new key called "40C7"
- Add a string under this key called "Name" with the value "Button 6 (hold)"
already exist. So..
this didnt work for me. If i push the button on my BT headset it redials the last number.
Button 6 is the Voice command button near the wheel so i cant see how the BT headset button is going to work??
any help would be great as this is then only function missing from a great device.
cheers

Should have mentioned that this has been tested by me only on a Tilt with AT&T stock ROM...
You shouldn't have to worry about the PTT-related steps on a TyTN II (nothing there to disable).

goestoeleven said:
Step 1. Disable Cyberon
[/B]- Delete SDDaemon.lnk in both \Windows\Start Menu and \Windows\Startup
- In these registry locations:
----> Remove this key entirely: {2C0E9904-F32D-4f53-875F-479F5CA81E18}
Click to expand...
Click to collapse
So this seems to be a very straight forward process, easily followed by anyone that has any right to be mucking about in a registry. However, ()SDDaemon.lnk does not exist in \Window\Start Menu it does exist in \Windows\Startup
Also, Remove this key entirely... Where the hell is it?
All other steps work fine..
Russ741

well sort off...
The PTT is now maped to VC, very cool works good.
However VC is still not working properly, I can issue commands, (dial, call, time, etc) but the system will not announce calls or appointments. I used the same CAB I have used on previous installs that worked fine before.
Any ideas anyone?
Russ741

the fix
If anyone else is having issues with call announcements look here for the fix.
http://forum.xda-developers.com/showthread.php?t=333260
Mine is now 100% and I can go back to my real job!
Russ741

Griffy wiffy said:
I have a HTC branded TytnII and there is no PPT reg entry. Also the keys
From HKLM\Software\Microsoft\Shell\Keys
- Add a new key called "40C6"
- Add a string under the key called "Name" with the value "Button 6"
- Add a new key called "40C7"
- Add a string under this key called "Name" with the value "Button 6 (hold)"
already exist. So..
this didnt work for me. If i push the button on my BT headset it redials the last number.
Button 6 is the Voice command button near the wheel so i cant see how the BT headset button is going to work??
any help would be great as this is then only function missing from a great device.
cheers
Click to expand...
Click to collapse
I use a plantronic BT head set. To use VC on the tilt I hold the main button down on the head set until I hear the VC chime in. Takes about 4-5 of holding it down until VC kicks in. I hear about 3 or beeps during that time.

Russ741 said:
If anyone else is having issues with call announcements look here for the fix.
http://forum.xda-developers.com/showthread.php?t=333260
Mine is now 100% and I can go back to my real job!
Russ741
Click to expand...
Click to collapse
I can confirm that with the procedure in #1, along with the update CAB from the above link, I'm now getting incoming calls announced, too!
Procedure in #1 has been updated accordingly.

goestoeleven said:
I can confirm that with the procedure in #1, along with the update CAB from the above link, I'm now getting incoming calls announced, too!
Procedure in #1 has been updated accordingly.
Click to expand...
Click to collapse
@goestoeleven: did you not put in the registry change?
4. Lastly, you must modify this registry entry in order to use your Bluetooth headset with Voice Command:
HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand Path = "\Program Files\Voice Command\VoiceCmd.exe
That's from your posting and I am pretty sure that is what really fixed my issue. I was using the older ver of MSVC with my wizard and it worked fine. So, unless there is something really different about the OS build on the Tilt, updating the MSVC may have improved on things but I still believe this reg key is what did it.
BTW: I loaded the updated MSVC before I tried the reg change and this ver of MSVC does NOT make that change for you!
I recommend you update post1 to include this step.
Great job on finding that key by the way! THANKS!!!!!!
Russ741

Russ741 said:
@goestoeleven: did you not put in the registry change?
4. Lastly, you must modify this registry entry in order to use your Bluetooth headset with Voice Command:
HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand Path = "\Program Files\Voice Command\VoiceCmd.exe
Click to expand...
Click to collapse
This key is not necessary with MSVC 1.6 (it was with MSVC 1.5). I'm running just fine without it.

i still can not initiate voice command from my headset. everything else works fine. i hear announcements, i can answer and hang up phone calls (the voice quality is still horrible), i get reminders, etc. but when i press the button to activate, it just opens the phone app.
is there something missing?

goestoeleven said:
This key is not necessary with MSVC 1.6 (it was with MSVC 1.5). I'm running just fine without it.
Click to expand...
Click to collapse
Interesting, I tried a couple different copies of MSVC 1.6, including the CAB I used on my Wizard and didn't get announcements. It wasn't until I loaded the latest ver and put in the reg patch did it start working 100%. I admit I didn't test between the latest ver and the reg change (yeah I know I should have) so I can't say for sure which one did it.
Russ741

diar said:
i still can not initiate voice command from my headset. everything else works fine. i hear announcements, i can answer and hang up phone calls (the voice quality is still horrible), i get reminders, etc. but when i press the button to activate, it just opens the phone app.
is there something missing?
Click to expand...
Click to collapse
That's very odd, normally the part that fails (for me at least) is the announcements or ring tone to the BT.
Can you initiate calls from the MSVC mapped key on the phone? That will narrow down if the prob is with the BT, MSVC or the phone itself.
Russ741

yes...i push PTT and VC functions just fine. i'll try that final reg change again and i'll soft reset and see what happens.
EDIT: i still can't initiate calls from the headset, however, this change does seem to have solved the low volume problem for me. just got a call, i heard the caller loud and clear and they heard me no problem.
so one problem down, one to go.

M$ VC still not working properly
I followed step in posting 1 to the letter and everything worked perfectly including caller ID voice announcement over bluetooth. But,when I soft reset or turn my phone off, I do not get voice announcement over bluetooth anymore. HELP!

Thanks! I like this concept ... I'll try it on my AT&T Tilt Rom.

Inconsistent results on various BT devices
Works great on my Jabra BT500.
On my Parrot CK3100 I get the "button only works once" behavior described in another thread - everything is great the first time I initiate VC from the car kit, but after that the phone's speaker and microphone are the only things active.
Next time the phone and car kit connect I get one more button push that works.
Argh. I'll search that other thread again, but I don't recall a fix for the folks that had these probs w/their headsets. (Any pointers are of course welcomed!)
Richard

Thanks a lot. This worked perfect for me. I am using an AT&T Tilt with helmi_c's Kaiser AKU.0.7.0 Cooked ROM and a Plantronics Discovery 655 headset.

VC with wired headset
I have a wired headset (HTC brand) and installed Voice Command, but cant get it to work from the headset button...does anyone know how I can activate from the button on headset?

i guess its safe to say you went into MSVC SETTINGS AND CHANGED the settings to wired headset? there has never been an issue with wired headsets just BT

FM-radio volume enhancement/hack

i friend of mine told me, the f**king fm-radio isn`t loud enough.
i remembered me, that i saw a reg key ("Volume"=dword:0000a8fc)
-----start of fmradiovolumehack.reg---------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\Software\HTC\FMRadio\FMPlayer]
"Band"=dword:00000000
"SupportWheel"=dword:00000001
"Volume"=dword:0000ffff
-----end of fmradiovolumehack.reg--------
Supportwheel to enable the yogdial
Band for switching frequencies, japan (1), europe(0)
for german diamond users, change band to japan to hear
POLICE, FIRE DEPARTMENTS, AMBULANCE
is there no function available in your fm-radio version,
change "Band"=dword:00000000 to "Band"=dword:00000001
scan 85-88 Mhz, and enjoy
listening to police radio is not illigal in germany!
to present it or to talk it to other people is illegal!
i had some ideas to enhance the radio application with a signal (or noise) level controlled muting function, to increase the feeling while listening
(hearing without headache ) and some other police radio related ideas.
http://forum.xda-developers.com/showthread.php?t=407617
have phun!
DOMin8or aka DERd!rk

Unfortunately I cannot change the Volume Setting. My dword is 43260, and I changed to 53260, and 33260, and 0, but the Volume does not change. A Volume"=dword:0000ffff I cannot set. Any solutions? Thanks...

i`ve not testet it by my own. but he says, it works.
he changed the parameter with pocket controllers registryeditor
on the fly. i will verify it immediatly.
edited
---test---
first test, i changed to FFFF, after starting, stopping fmradio, i have taken a look
into my registry, now its F168. now i try to set to FFFFF. the change to
FFFF was not noticeable louder.
changes to FFFFF will take no effect. after closing application, the registry contains $F168
(the limit???)
okay, forget it. i`ve set it to 0200,, very quiet. but no changes. volume is the same.
i will kick this threat in 20 minutes. its useless.

the radio doesnt runs the normal signalpath, like other applications.
audioverbesserung (htc eqalizer) cant take tone control of fm-radio nf signal.
(to enhance the volume)

i can`t find the kill threat function from the forum.
no otpions, under edit post/advanced otpions.
how can i kill this threat?

Did anyone find a way to increase the lower fm radio volume level?

software issue with MS Voice command

I have the Fuze. Has there been a fix for the following issue?
If you enable "announce incoming caller" my phone will say the name if it's in my address book, or the number. When I answer the phone via BT headset, I cannot hear the caller, but the caller can hear me. If I transfer to my phone, I can now hear the caller. If I turn off the announce, then everything is working again.
Just a heads up, my phone when I first got it, would work fine, then it stopped announcing the caller. All you would hear is a "beep" in the headset. Then I was shown a regedit that got the voice to com back, but can't hear the caller.
I know this was a ongoing issue months ago, but was there ever a solve for this?
Oh my Fuze is stock.
ms voicecommand version: 1.6.19971
rom version: 1.95.502.5 wwe
rom date:10/20/08
proto version:52.39c.25.22h

@starstreak:
I'm latching on some additional URL's to help us troubleshoot the issue.
MS Voice Command on the Fuze
http://forum.xda-developers.com/showthread.php?t=445204
The Definitive Guide to Microsoft Voice Command (MSVC) 2.1
http://www.winmo-experts.com/viewtopic.php?f=11&t=2
Da_G's Simple ROM Kitchen Solutions (Fixes)
http://forum.xda-developers.com/showpost.php?p=3467110&postcount=503
http://forum.xda-developers.com/showpost.php?p=3462813&postcount=489
http://forum.xda-developers.com/showpost.php?p=3592035&postcount=644
Da_G's Simple ROM Kitchen Reports
http://forum.xda-developers.com/showpost.php?p=3455841&postcount=470
http://forum.xda-developers.com/showpost.php?p=3457239&postcount=471
http://forum.xda-developers.com/showpost.php?p=3460626&postcount=480
http://forum.xda-developers.com/showpost.php?p=3460665&postcount=481
http://forum.xda-developers.com/showpost.php?p=3460972&postcount=483
http://forum.xda-developers.com/showpost.php?p=3462787&postcount=488
http://forum.xda-developers.com/showpost.php?p=3617314&postcount=709

Few questions:
1) What file is the BT Audio Gateway pointing to:
HKLM\Software\Microsoft\Bluetooth\AudioGateway
BTAGExtModule =
2) Is there a BT Headset Call Announce key, what are the values:
HKCU\ControlPanel\Sounds\InCallPoliteBeep
3) Is there a Call Announce key, what are the values:
HKCU\ControlPanel\Sounds\TTSAnnounce

1) What file is the BT Audio Gateway pointing to:
HKLM\Software\Microsoft\Bluetooth\AudioGateway
BTAGExtModule = oemagw.dll
2) Is there a BT Headset Call Announce key, what are the values:
HKCU\ControlPanel\Sounds\InCallPoliteBeep
catagory incall
script as5p
sound application data\volatile\\ttscallerid.exe
3) Is there a Call Announce key, what are the values:
HKCU\ControlPanel\Sounds\TTSAnnounce
catagory voicecommand1
script as5p
sound application data\volatile\\ttscallerid

That happened to me with the stock 6.1 & MSVC, but, since I flashed to RRE's 6.5 V4, which uses MSVC 1.6.21234, that problem disappeared.
It would do the same thing yours did, you'd answer your BT, they could hear you but you couldn't hear them. I tried it with several different BT headsets, made no difference.

@p51d007:
If you can spare a moment, would it be possible for you to post up the registry for the BT Audio Gateway?
@startstreak:
Those registry entries don't look right (ex: point to ttscallerid.exe, extra back slashes, etc). Here are my entries:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
REG_SZ: BTAGExtModule = \windows\VCBTHAG.DLL
[HKEY_CURRENT_USER\ControlPanel\Sounds\InCallPoliteBeep]
REG_SZ: Script = as5p
REG_SZ: Category = InCall
REG_SZ: Sound = \Application Data\Volatile\TTSCallerID.wav
[HKEY_CURRENT_USER\ControlPanel\Sounds\TTSAnnounce]
REG_SZ: Script = as5p
REG_SZ: Category = VoiceCommand1
REG_SZ: Sound = \Application Data\Volatile\TTSCallerID.wav
Cheers,

hilaireg- I remember where those extra "//" came from. It was from another regedit that was on this board.
I redid your settings on mine. Wow. I can now hear my caller. I tried it around 8 times with different phones. 2 times, my phone vibrated (I have it set to vibrate&ring at the same time) but nothing sounded on my headset untill the phone killed the call to goto voicemail. At that split second, I heard my ring tone in my ear for like less than a second. So I'm not sure if that is a new issue.
I am happy for your help. Since I got the fuze when it first came out, I never had my MSVC working this well. Thanks!

I'll post ONLY the ones that vary from yours...
Hope this helps.
[HKEY_CURRENT_USER\ControlPanel\Sounds\InCallPoliteBeep]
REG_SZ: Script = p <<<<<THIS IS DIFFERENT
REG_SZ: Sound = Alarm1.wma <<<<THIS IS DIFFERENT
[HKEY_CURRENT_USER\ControlPanel\Sounds\TTSAnnounce]
REG_SZ: Category = InCall2 <<<<<THIS IS DIFFERENT
hilaireg said:
@p51d007:
If you can spare a moment, would it be possible for you to post up the registry for the BT Audio Gateway?
@startstreak:
Those registry entries don't look right (ex: point to ttscallerid.exe, extra back slashes, etc). Here are my entries:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
REG_SZ: BTAGExtModule = \windows\VCBTHAG.DLL
[HKEY_CURRENT_USER\ControlPanel\Sounds\InCallPoliteBeep]
REG_SZ: Script = as5p
REG_SZ: Category = InCall
REG_SZ: Sound = \Application Data\Volatile\TTSCallerID.wav
[HKEY_CURRENT_USER\ControlPanel\Sounds\TTSAnnounce]
REG_SZ: Script = as5p
REG_SZ: Category = VoiceCommand1
REG_SZ: Sound = \Application Data\Volatile\TTSCallerID.wav
Cheers,
Click to expand...
Click to collapse

starstreak said:
hilaireg- I remember where those extra "//" came from. It was from another regedit that was on this board.
I redid your settings on mine. Wow. I can now hear my caller. I tried it around 8 times with different phones. 2 times, my phone vibrated (I have it set to vibrate&ring at the same time) but nothing sounded on my headset untill the phone killed the call to goto voicemail. At that split second, I heard my ring tone in my ear for like less than a second. So I'm not sure if that is a new issue.
I am happy for your help. Since I got the fuze when it first came out, I never had my MSVC working this well. Thanks!
Click to expand...
Click to collapse
As I see it, you have a few options:
1) Continue to debug the issues
I've a feeling that the MSVC install on the ROM has been messed up. I'm not sure if it's only the registry part or if some of the exe/dll are impacted as well. If it turns out exe/dll's are also a problem, we will quickly run out of options.
In the interim, I can post up the MSVC registry file so that you can compare the settings against those in your device registry.
2) Follow p51d007's recommendation
IMHO, I recommend this approach. Drop the ROM you are using and flash a working ROM.
Alternatively, make an inventory of the applications on your device, and then look at the 6.1 Kitchen in the Raphael ROM Development thread - there's text files listing the applications in the kitchen/pack. Compare it against your list to make sure that all the applications you use/have are present and cook your own ... provides *way* more control.
* EDIT *
Posted registry and post-MSVC configuration.

I was thinking about upgrading to 6.5 if it was stable. If I had to cook.

I wouldn't call it an upgrade; it's still pretty much unreleased code.
That said, Da_G (and others) have done a fantastic job with the 6.5 code they've managed to locate.
If you need to rely on device functionality, you may want to look trying a 6.1 ROM - or cooking your own. That way, you can try WinMO 6.5 on the weekends ...

Text Messages
Voice Command on my tilt read messages and I could hear them. I realize the Fuze has had issues with Voice Command. Has anyone gotten this feature to work? Saved time from having to pick device up from desk.

try flashing back to stock and then going back to a ROM. Try out NRGZ28's Energy ROM. Working great very little bugs. on an older version but i'm sure the new one is just as stable.

It Works...
If you go to the voice command icon in settings, highlight messaging (don't just put the check mark in the box, highlight the word messaging) then push the options button. You will go to the Voice Cammand: Messaging Options and take the check out of the High priority messages only box. This should work. I have had Energy Roms anda few others, like right now I have RRE's and my messages read after doing this. Everytime I flash a new rom I have to go and do this. But it works afterwards.

Muchas Gracias
I did as you suggested, unchecked High priority massages only. Works like a charm, thanx