Has anyone installed MS Voice Command on their Tytn II yet? I'd really like to be able to initiate calls from the BT headset when in the car...
Just curious since I know the new version supposedly supports commands directly from the headset. If no one else has.. maybe I'll buy it and give it a shot.
sqadan said:
Has anyone installed MS Voice Command on their Tytn II yet? I'd really like to be able to initiate calls from the BT headset when in the car...
Just curious since I know the new version supposedly supports commands directly from the headset. If no one else has.. maybe I'll buy it and give it a shot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=998205&postcount=9
Works like a charm. Will post the link to get VC 1.6 to announce calls.
can you post the link please to get it to announce calls.
Its been great having VC 1.6 running with no hacks needed. It would be the icing on the cake to have it announce calls finally.
Can I just install it and it works? As in I can initiate calls with the BT Headset button? I hate having to fiddle with the phone.
If I can't do this, it's not worth $39 imho.
chrisnash said:
can you post the link please to get it to announce calls.
Its been great having VC 1.6 running with no hacks needed. It would be the icing on the cake to have it announce calls finally.
Click to expand...
Click to collapse
Here you go (found it after searching for hours don't remember from where)
***
Disable Voice Command before you attempt this
Overwrite your existing files from the zip. Make sure you can see hidden/system files
\Windows
VoiceCommand_PPC.cpl
\Program Files\Voice Command\
VoiceCmdRes_PPC.dll
VoiceCommandWMP.dll
voicecmd.exe
Enable voice command.
Let me know how it goes.
kavi said:
Here you go (found it after searching for hours don't remember from where)
***
Disable Voice Command before you attempt this
Overwrite your existing files from the zip. Make sure you can see hidden/system files
\Windows
VoiceCommand_PPC.cpl
\Program Files\Voice Command\
VoiceCmdRes_PPC.dll
VoiceCommandWMP.dll
voicecmd.exe
Enable voice command.
Let me know how it goes.
Click to expand...
Click to collapse
I downloaded the zip file but there are only 3 files inside. I am still missing VoiceCmdRes_PPC.dll - What went wrong?
So I installed Voice Command... But I can't seem to get it to work from my BT Headset Button?? Can anyone help me with this?
sqadan said:
So I installed Voice Command... But I can't seem to get it to work from my BT Headset Button?? Can anyone help me with this?
Click to expand...
Click to collapse
Please check post #2
h2ogun>>
As I said you should have windows display hidden/system files to see that. Check your windows explorer settings, all 4 files are there.
Thanks. That did solve the problem.
I can't seem to get Voice Command to announce my reminders. Is there any fix for this yet?
Amlethae said:
I can't seem to get Voice Command to announce my reminders. Is there any fix for this yet?
Click to expand...
Click to collapse
I also had the same problem but after the call announce fix it started to work.
kavi said:
Please check post #2
h2ogun>>
As I said you should have windows display hidden/system files to see that. Check your windows explorer settings, all 4 files are there.
Click to expand...
Click to collapse
I thought this was for VC 1.5 not 1.6??? I thought VC 1.6 was supposed to work natively with the BT headset? I'm not rying to be a pain - I just don't want to hack anything up if I don't have to.
sqadan said:
I thought this was for VC 1.5 not 1.6??? I thought VC 1.6 was supposed to work natively with the BT headset? I'm not rying to be a pain - I just don't want to hack anything up if I don't have to.
Click to expand...
Click to collapse
I have both but VC 1.5 won't even start on my Kaiser.
OK... So I added the suggested key to the registry - but Istill can't start Voice Command with the button on the headset... (Jabra x10 series II)
Any thoughts? I am assuming the regsitry key is a String Value:
Name = "Path"
and then the value being the path itself... is this correct??
sqadan said:
OK... So I added the suggested key to the registry - but Istill can't start Voice Command with the button on the headset... (Jabra x10 series II)
Any thoughts? I am assuming the regsitry key is a String Value:
Name = "Path"
and then the value being the path itself... is this correct??
Click to expand...
Click to collapse
Make sure you assign the voice command button as well
It seems to be working now... It takes two beeps on the headset to initiate VC. Well... We'll see how this works over the next week or so...
Glad you got it working.
BTW my JX10 works with one press.
kavi said:
Glad you got it working.
BTW my JX10 works with one press.
Click to expand...
Click to collapse
I have to hold the button until there are 2 beeps then i get the prompt...
Maybe the Series II works differently?
sqadan said:
I have to hold the button until there are 2 beeps then i get the prompt...
Maybe the Series II works differently?
Click to expand...
Click to collapse
Maybe... but if it works that's all that matters!
Are these steps working for other Kaiser users? VC 1.6 works fine after install for activation via an assigned button on the phone. No matter what tweaks I make in the registry or files I replace though, activation through the headset is just opening up the HTC phone applet.
Related
I know this has been beat to death in the Hermes forum but I have found a bit of difference with my Kaiser as compared to my Hermes.
I have quite a bit of experience with the TyTN hermes tweaks to get Microsoft Voice Command to work with the Hermes but not only will the Kaiser NOT work without the tweaks - I can't get it to work with the tweaks.
I followed the exact instructions like I always have listed in the Hermes Wiki section titled Utilities and Software Tweaks (including Bluetooth Voice Command installation and the Registry changes). However after the changes I cannot initiate a Bluetooth instruction via the Bluetooth device. If I initiate the call via the handheld it works great as far as stability and sound quality.
Any suggestions?
You don't have to do any tweaks on Kaiser! Just install VC 1.6. Assign Button 6 to Voice command. Soft reset. It should work. Works for me at least. The only think that doesn't work is a caller name announcement.
ID64 said:
You don't have to do any tweaks on Kaiser! Just install VC 1.6. Assign Button 6 to Voice command. Soft reset. It should work. Works for me at least. The only think that doesn't work is a caller name announcement.
Click to expand...
Click to collapse
Ditto,
My Kaiser does announce incoming callers on the internal speaker when the setting is on "use bluetooth if available". I only use bluetooth with my car so I do not know what the behavior with a headset would be.
Does it work so that you can push the button on your Bluetooth headset or Bluetooth car adapter and then give the Voice Command through the headset? Mine didn't work. That's why I did the tweaks.
Also can someone tell me that with just the Voice Command installed what does the following registry key have (or does it even exist)?:
HKLM\SOFTWARE\OEM\VoiceCommand\Path = ????
AND
HKLM\SOFTWARE\Microsoft\Bluetooth\AudioGateway\BTAGExtModule = ???
Also if you go to settings and click on Voice Command - what version Voice Command do you have? I have v1.6.4622.0
Thanks
GenesysLV,
Can you please check build number of your VC 1.6?
Thanks.
ID64 said:
Can you please check build number of your VC 1.6?
Click to expand...
Click to collapse
Not terribly related, but v1.60.4622.0 is what my copy reports as well - though I'm still on a Hermes. I believe that's the retail release, I've not seen any indication of another one....
Richard
ID64 said:
GenesysLV,
Can you please check build number of your VC 1.6?
Thanks.
Click to expand...
Click to collapse
I have the same version number. Is there a different place to actually check the "build" ?
jcrompton said:
I have the same version number. Is there a different place to actually check the "build" ?
Click to expand...
Click to collapse
If you go to VC settings, please go to about or something like that. There you will see full version number.
Thanks
yep
its the 1.6.4622.0 version
jcrompton said:
yep
its the 1.6.4622.0 version
Click to expand...
Click to collapse
Thanks Just to confirm: you can hear callers name over your BT car handsfree?
ID64 said:
Thanks Just to confirm: you can hear callers name over your BT car handsfree?
Click to expand...
Click to collapse
Hmm... Looks like I have build 1.60.4630.0
Hi, I have build v1.60.4622.0 and I noticed a fundamental difference when installing to my kaiser than when installing to my Uni; no registry entries get added to:
HKLM\Software\OEM\VoiceCommand
So this means that no bluetooth interaction would work. Therefore I added:
Dword entry: LaunchAPEnable (value 0)
and
String entry: Path (value \Program Files\Voice Command\voicecmd.exe
Rebooted and now voice command is initiated fine via bluetooth headset. Haven't tested notifications yet - I think there might still be a missing reg entry but I can't remember what it is!
Hope this helps someone....
Thanks. I'll try those registry changes. I hard reset last night to make sure that I got rid of all of the "tweaks" that had been done - the way I did for the Hermes.
I wonder where the other guy got version 30 instead of our version 22
I got mine from Handango - the Microsoft site doesn't have any updates except for version 1.5
ID64 said:
GenesysLV,
Can you please check build number of your VC 1.6?
Thanks.
Click to expand...
Click to collapse
No problem. v1.6.4622.0
I should have caught up on the thread first. Just to be claer, I do not hear the callers name through my car. I do hear it only on the Kaiser's speaker.
I'd love to get the announcements working over BT. It was sporadic on my TyTN with the registry hacks.
captainsensible2002 said:
Hi, I have build v1.60.4622.0 and I noticed a fundamental difference when installing to my kaiser than when installing to my Uni; no registry entries get added to:
HKLM\Software\OEM\VoiceCommand
So this means that no bluetooth interaction would work. Therefore I added:
Dword entry: LaunchAPEnable (value 0)
and
String entry: Path (value \Program Files\Voice Command\voicecmd.exe
Rebooted and now voice command is initiated fine via bluetooth headset. Haven't tested notifications yet - I think there might still be a missing reg entry but I can't remember what it is!
Hope this helps someone....
Click to expand...
Click to collapse
THANKS!
This needs to go into the Kaiser WIKI !!!
These registry changes are needed inorder to be able to initiate phone calls from your bluetooth device using Microsoft Voice Command. These registry changes worked GREAT and the initiation of calls from bluetooth work much better than with the Hermes and it's tweaks.
Of note, using Resco Registry editor, I had to put quotes aroung the Path entry to get it to work so my registry edit looked like this:
Path Value= "\Program Files\Voice Command\voicecmd.exe"
If anyone knows how to get attention to have this put in the Wiki please feel free.
Odd, I did not have to edit/add any registry settings and I can initiate calls/commands from my BlueAnt Z9 headset.
________________________
HTC TyTN II (Kaiser) / WM6
greg3d said:
Odd, I did not have to edit/add any registry settings and I can initiate calls/commands from my BlueAnt Z9 headset.
________________________
HTC TyTN II (Kaiser) / WM6
Click to expand...
Click to collapse
? using Microsoft Voice Command ??
I used several different headsets / devices and no luck until I made the registry additions. What ver of Voice Command do you have?
Can someone turn this into a CAB?
Thanks
jcrompton said:
THANKS!
This needs to go into the Kaiser WIKI !!!
These registry changes are needed inorder to be able to initiate phone calls from your bluetooth device using Microsoft Voice Command. These registry changes worked GREAT and the initiation of calls from bluetooth work much better than with the Hermes and it's tweaks.
Of note, using Resco Registry editor, I had to put quotes aroung the Path entry to get it to work so my registry edit looked like this:
Path Value= "\Program Files\Voice Command\voicecmd.exe"
If anyone knows how to get attention to have this put in the Wiki please feel free.
Click to expand...
Click to collapse
jcrompton said:
If anyone knows how to get attention to have this put in the Wiki please feel free.
Click to expand...
Click to collapse
Ummm, the whole POINT of a Wiki is that users can add to it themselves, so feel free to update the Kaiser section.....
Richard
GenesysLV said:
Ditto,
My Kaiser does announce incoming callers on the internal speaker when the setting is on "use bluetooth if available". I only use bluetooth with my car so I do not know what the behavior with a headset would be.
Click to expand...
Click to collapse
I have tried this option but does not seem to announce calls.
Hope someone can find a fix.
Thanks
I flashed my TMO Wing and now Im running TouchFlo v.2.3
When I hold down button 5 I keep getting an error about VoiceCmd.exe.
Heres the deal, I dont want Button 5(Hold) to launch VoiceCmd.exe. I want to map it to something else...anything else. I've tried some registry edits and I cannot seem to find a way to change Button 5(hold)'s function. Even when choosing another app under settings-buttons, it still tries to attempt to launch VoiceCmd.exe and again I receieve an error.
I've searched far and wide and I've come up short on this topic. Can someone share some brilliance with me?
To be more specific, I want to map Button 5(Hold) to activate Voice Speed Dial. Thanks.
I have had the same issue. I have tried to map the button to something else but have continued to get the same error I gave up!
Solved.
Ok ok... So I figured it out. The button I am gonna show you how to map is also called the "PTT" button. You need a registry editing program to do this. "Total commader" works for me.
With the registry editing program locate a file in the /windows folder called "Long_PTT". This file basically links whatever app you want to the Long press PTT button. Edit this file and change the shortcut path to whatever app you want and there you have it. No more annoying "VoiceCmd.exe" error message.
Also dont forget to go to "setting-buttons" to remap there as well.
Hope this helps.
Thanks for the info, Been looking to solve this for a while ..................... but you do not need a registry editor you just need a file explorer program that has the abiity to give you properties of that file inother for you to change the shortcut path. and Total Commander and Resco Explorer are such programs ................................ and Thanks again
Thanks works great!
wordizbond007 said:
Ok ok... So I figured it out. The button I am gonna show you how to map is also called the "PTT" button. You need a registry editing program to do this. "Total commader" works for me.
With the registry editing program locate a file in the /windows folder called "Long_PTT". This file basically links whatever app you want to the Long press PTT button. Edit this file and change the shortcut path to whatever app you want and there you have it. No more annoying "VoiceCmd.exe" error message.
Also dont forget to go to "setting-buttons" to remap there as well.
Hope this helps.
Click to expand...
Click to collapse
Thats awesome man, worked like a charm!
Voice command BT headset
I have MS voice command and have run the BT patch but for the life of me I can't seem to operate voice command with my Plantronics 520 headset.
anyone have any experience getting this to work??
thanks!
brad99 said:
I have MS voice command and have run the BT patch but for the life of me I can't seem to operate voice command with my Plantronics 520 headset.
anyone have any experience getting this to work??
thanks!
Click to expand...
Click to collapse
I am running Open Touch V1 and installed MS VOice Command. Working fine without any BT patches with my Moto H700 headset!
coolmen777 said:
I am running Open Touch V1 and installed MS VOice Command. Working fine without any BT patches with my Moto H700 headset!
Click to expand...
Click to collapse
what is open touch v1?
I installed open touch 2.4 and LOVE IT.. it makes windows mobile so much useful..
one thing i found problamatic was the bluetooth profile. The problem is when I press the call button on my bluetooth headset it doesn't trigger the voice speed dial. It just launches the dialler which shows the keypad.
That kind of defeats the purpose of 'hands free' if I need to press the voice speed dial on the phone and then use the headset.
Any solution ? Or any other package I can install to get the full functionality of voice speed dial with bluetooth.
I have the same problem, and it effects the ability for me to use MS Voice Command. I wish someone would help, but I made a post about this and got no replies.
beowolf said:
I have the same problem, and it effects the ability for me to use MS Voice Command. I wish someone would help, but I made a post about this and got no replies.
Click to expand...
Click to collapse
guys,
I'm working on v2.5 and will try to resolve this issue if possible.
I need more details as to what is happening.
Also,
I did not see any of this nature posted in the original v2.2 post.
Who else is having this issue?
hoolahoous said:
I installed open touch 2.4 and LOVE IT.. it makes windows mobile so much useful..
one thing i found problamatic was the bluetooth profile. The problem is when I press the call button on my bluetooth headset it doesn't trigger the voice speed dial. It just launches the dialler which shows the keypad.
That kind of defeats the purpose of 'hands free' if I need to press the voice speed dial on the phone and then use the headset.
Any solution ? Or any other package I can install to get the full functionality of voice speed dial with bluetooth.
Click to expand...
Click to collapse
Just to cover all basis, did you setup the button 5 options?
Remember that I left the 5th button free for people to choose either voice record or voice speed dial.
Going forward, please do not create new post, instead post your issues in the original thread.
Thanks,
I'm pretty sure that what your dealing with is a registry problem. When i switched to touchit 2.3 i had to reconfig to the following:
1 Use registry editor to edit the following entries on your Wing:
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: LaunchAPEnable, Value Data: 1
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: VoiceCmdEnable",Value Data: 0
2. Wait about 30 sec, then soft-reset
Try it and let me know how it goes. I dont get credit for this it is from a previous post. This did work for me tho. I can prompt the voice speed dial from the bluetooth.
ttran001 said:
guys,
I'm working on v2.5 and will try to resolve this issue if possible.
I need more details as to what is happening.
Also,
I did not see any of this nature posted in the original v2.2 post.
Who else is having this issue?
Click to expand...
Click to collapse
Thanks ttran for responding. I have great respect for you for putting together this great ROM.
The issue is..
I am pairing my bluetooth headset (motorola h850) with the phone. After paring, if I press the call button on my bluetooth, it is supposed to invoke the voice dial app in the phone and call the voice tag I spoke. However it just brings the phone dialler screen and does nothing.
My diagnosis
For an incoming call (when paired), I can pickup the call using bluetooth headphone's button. So I know bluetooth instrument is working.
Secondly when I directly invoke voice speed dial from phone (i mapped a hardware button to voice speed dial) it works fine too.
Only problem is I can not invoke voice speed dial from bluetooth headset.
Do not confuse this issue with the hardware button mapping since I am trying to invoke voice speed dial from bluetooth headset (not from hardware button on phone. that works fine)
Please let me know if you need any futher information. I will happy to provide any additional details.
BTW thanks again for putting together such a great ROM.
Hi,
Thanks for clearing that up.
Please try what mrmikemcguire posted:
1 Use registry editor to edit the following entries on your Wing:
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: LaunchAPEnable, Value Data: 1
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: VoiceCmdEnable",Value Data: 0
2. Wait about 30 sec, then soft-reset
And let us know if it works for you, I don't use blue tooth so I can not test it for you.
Also,
Let me know if it fixes your issue so that I can add it to the next release.
Thanks folks,
sorry didn't work for me..
Ok.... First, thank you mrmikemiguire . Now hoolahoous .. did we make progress? The Audio gateway should be opening now... Verify that the registry modifications are correct in your device, then power cycle..... there may be another piece to the puzzle but those changes should work.
Edit: Final piece... Verify HKLM,"SOFTWARE\OEM\VoiceCommand "Path" = \Windows\SDDialer.exe
Okay.. thanks for everyone's help.. I finally got it to work... One thing incorrect in above settings was
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
the default entry was VCBTHAG.DLL not OEMAGEX.dll , I missed that..
however when I changed VCBTHAG.DLL to BTAGExtModule.dll , it started working..
ttran001, maybe you can include these entries in 2.5.
I know you are not planning to include voice speed dial or voice command in 2.5, I personally feel that you should include atleast one of them. My vote would be voice speed dial since it works for everyone but voice command works only for subset of people. When I say work, I mean software being able to recognize what a person is saying.
but thanks to everyone including mrmikemcguire to get it to work for me.
hoolahoous said:
Okay.. thanks for everyone's help.. I finally got it to work... One thing incorrect in above settings was
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
the default entry was VCBTHAG.DLL not OEMAGEX.dll , I missed that..
however when I changed VCBTHAG.DLL to BTAGExtModule.dll , it started working..
ttran001, maybe you can include these entries in 2.5.
I know you are not planning to include voice speed dial or voice command in 2.5, I personally feel that you should include atleast one of them. My vote would be voice speed dial since it works for everyone but voice command works only for subset of people. When I say work, I mean software being able to recognize what a person is saying.
but thanks to everyone including mrmikemcguire to get it to work for me.
Click to expand...
Click to collapse
Hi,
That reg fix has been added to v2.5 and yes Voice speed dial is included but not voice command since it takes about 4mb of space.
hoolahoous said:
Okay.. thanks for everyone's help.. I finally got it to work... One thing incorrect in above settings was
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
the default entry was VCBTHAG.DLL not OEMAGEX.dll , I missed that..
however when I changed VCBTHAG.DLL to BTAGExtModule.dll , it started working..
ttran001, maybe you can include these entries in 2.5.
I know you are not planning to include voice speed dial or voice command in 2.5, I personally feel that you should include atleast one of them. My vote would be voice speed dial since it works for everyone but voice command works only for subset of people. When I say work, I mean software being able to recognize what a person is saying.
but thanks to everyone including mrmikemcguire to get it to work for me.
Click to expand...
Click to collapse
Yep sorry about that.. I realized that when i did it, same occurance, but forgot to mention it! Sorry about that, but at least you got it squared away. Glad I could at least point you in the right direction.
mrmikemcguire said:
Yep sorry about that.. I realized that when i did it, same occurance, but forgot to mention it! Sorry about that, but at least you got it squared away. Glad I could at least point you in the right direction.
Click to expand...
Click to collapse
Either way thanks for providing feed back so to help resolve this issue.
I am using 2.5 slim and cannot get audio from realplayer, skype, etc.
I push the button and all I get is some wrong application, try again later errors....
Please help.
It all worked perfectly with the Clean ROM so may be someone with know-how can look at the registry differences between them and tell me if this is fixable, or i have to install the clean again...
Thank You!
#13 said:
I am using 2.5 slim and cannot get audio from realplayer, skype, etc.
I push the button and all I get is some wrong application, try again later errors....
Please help.
It all worked perfectly with the Clean ROM so may be someone with know-how can look at the registry differences between them and tell me if this is fixable, or i have to install the clean again...
Thank You!
Click to expand...
Click to collapse
Is this with bluetooth or the actual headset, or headphones?
And is anybody else having this issue?
Yes, BT.
Sorry i didn't mention this important detail.
I asked this question in the general dev and hacking forum but i think i should've asked it here, so here it goes:
I am using NATF v3 ROM which has MVC (MS Voice Command) built into it, and MVC works well for voice dialing if your contacts have English names, which I don't have. So, i went ahead and disabled MVC (can't uninstall as it is built into the ROM) and installed Cyberon Speed Dial which allows me to use my own voice tags to do the calling.
everything is ok, but the only problem is that i can't find away to start cyberon by pressing the BT headset button. all solutions i found on this and other forums were for the other way around (using MVC instead of cyberon)
thanks for reading and will really appreciate your help
still trying to get this worked out, and it seems that "OEMAGW.dll" is missing from my ppc, if somebody is kind enough to find it under his/her windows directory and post it, that will be great
OEMAGW.dll, anybody?
i would really appreciate anybody sending me the file
This is it
AthenaLod said:
i would really appreciate anybody sending me the file
Click to expand...
Click to collapse
This is the file..i´ve copied this from the windows folder in my xperia WM 6.1..hope it helps, plase let me know..
Hi, Folks,
I'm searching for a software to read the incoming SMS like the Blue&Me® by Fiat/Microsoft do.
I've found this app (TellMeText 1.1.0), but it has only one language (US English), and the language file is compiled with the executable app.
Anyone knows a app to do this function and a way to use the Gabriela Voice (Pt-BR) from iGo or something like this?
Thanks in advanced
If you have Microsoft Voice Command (MSVC) on your phone, you can set it to read incomming text messages, voice announce who is calling, and more Just be sure you really want it to do that before you turn it on.. It can be embarassing when someone TXT's you something questionable when you are in line at the bank or something... There is a feature where it will onyl read it when you have a bluetooth headset connection.. that is what I personally do...
I agree with Teej. I used the free/busy toggle cab to work around this. If I am not at work or somewhere I wouldn't want certain messages read aloud, I leave it free. If at work, I set it to busy. MSVC worked very well for me.
yes, MSVC is good, but reads the msg soooooo fast that you can berly understand what is happening. and the MSVC voice is sooo ennoying.anyway to fix it?
bteljuice said:
yes, MSVC is good, but reads the msg soooooo fast that you can berly understand what is happening. and the MSVC voice is sooo ennoying.anyway to fix it?
Click to expand...
Click to collapse
I haven't used it in a while since I am flashing roms constantly, but I know there is a registry hack where you can slow it down. Just Google it or search here. You can also edit voice recognition so that it is easier for it to pick up what you are say. Its a nice program, just very picky about installation and stuff so people don't like to always deal with it.
i just searched it, didnt find anything. prob didnt type the right info in search.
Is it any trouble if you can guide me ot the right path( regarding slowing the voice and voice recognition)
Appreciate it tilt4life2
this in an idea I like the sound of. Have you looked at the complete MSVC guide on this forum? It may hold a referance to the slowing down of the voices. Im guessing searching MSVC guide should find it or it may be linked in the Kaiser Wiki. Good Luck!
There is also TellMeText by Blondiesoft here and it's totally freeware:
http://www.blondiesoft.com/software/mobile/TellMeText/
It even announces the message before your notification goes off with its regular message tone.
MACkjam said:
There is also TellMeText by Blondiesoft here and it's totally freeware:
http://www.blondiesoft.com/software/mobile/TellMeText/
It even announces the message before your notification goes off with its regular message tone.
Click to expand...
Click to collapse
it does not work on tytn II with WM6.1?
dont know why!
Doppler2008 said:
it does not work on tytn II with WM6.1?
dont know why!
Click to expand...
Click to collapse
Perhaps it has something to do with the threaded sms? I'm not sure. All I know is that it works fine on my TyTN II with WM6.0. In any event, I have decided to go with voice command instead.
tilt4life2 said:
I know there is a registry hack where you can slow it down.
Click to expand...
Click to collapse
Yes! the Kaiser Tweaks cab has the voice command settings in it. It's generically set to 4. Higher settings speeds the chick up, and lower settings slows her down.
Hope this helps.
You can search for Kaiser Tweaks in here to get the cab.
Cheers!
bteljuice said:
yes, MSVC is good, but reads the msg soooooo fast that you can berly understand what is happening. and the MSVC voice is sooo ennoying.anyway to fix it?
Click to expand...
Click to collapse
To change the voice's speed:
Go to "HKEY_CURRENT_USER\Software\Microsoft\Speech\Voices"
Change the value of "DefaultTTSRate" from between 1 (slowest) and 10 (fastest). Default is 4. Experiment to discover what is right for you.