Anyone "in the know" on what is going on with Microsoft Voice Command?
For those not up to date heres the brief bio:
Microsoft released a rocking WM program that offers true voice recognition on pocketPCs and smartphones. If it didn't come with your carrier's build, it's a $40 upgrade, and well worth it. The latest version is 1.6. Unfortunately, it's been fraught with little issues, mostly related to Bluetooth headset compatibility, but most people still find it indispensable in spite of these challenges. I'm one of those people. The dial by number, and recognition of any name in the address book is invaluable to me, and a "must have" app for my 6800, no matter how badly it works.
The program is at version 1.6, and hasn't been updated in 2 years now.
What's the skinny?
jtg
I agree. I have had the same problems and have searched the net for any info about an update. Like you, I have not been able to find anything about a projected release of a new version. I guess that is just the microsoft way...only 2 years..
I heard a rumor that it was goint to be built into the next version of Windows mobile, but I hope that's not true.
If that happens, hoppefully it will be DCD to the rescue with a port for use all!!!
The real deal:
Ok, to those who haven't been following:
Microsoft DID update the VC software, but it was never released. It seems the Windows Mobile version went to the back burner since they made a deal with Ford Motors to start including the VC technology in the new Ford in-dash stereo systems (que up your mp3's, make calls via your bt phone, etc).
However, there was a test rom floating around for another WM device that had a greatly improved new VC version, which fixed 99% of the problems everyone was having.
This version was extracted and made available as an OEM to load into a kitchen to build into your ROMs.
There is NO .cab installation that I've seen for this version, so you're stuck with either cooking it in, or just replacing the files (there's a zip floating around here somewhere of the files u need to replace to make it the new version, but I don't recall where I saw it).
The OEM can be found in the excellent new PPCGeeks kitchen (ppckitchen.org), which incidentally supported Titan roms now.
For you DCD fans, it seems he hasn't made his rom compatible with the new kitchen GUI, but its relatively simple to make it a basekit. If enough of you push dcd, he might consider doing it... otherwise, you can always copy the OEM directory into DCD's kitchen OEMs.
Try Dutty's Voice Commander
This works for me, it is the best of both versions I have seen of the voice software. There are a couple versions out there, this is the most recent I have found. It is a cab.
I've got VC almost completely working. I cooked it into the DCD ROM. One reg key needs to be changed to get the button on your headset to work. The part I don't have working is the prompt and confirmation comming to the headset. The prompt and confirmation come out of the phone. It takes commands fine through the headset, just no audio until the call is started. Anyone know how to fix that? I'm using a Jawbone.
Dishe said:
Ok, to those who haven't been following:
Microsoft DID update the VC software, but it was never released. It seems the Windows Mobile version went to the back burner since they made a deal with Ford Motors to start including the VC technology in the new Ford in-dash stereo systems (que up your mp3's, make calls via your bt phone, etc).
However, there was a test rom floating around for another WM device that had a greatly improved new VC version, which fixed 99% of the problems everyone was having.
This version was extracted and made available as an OEM to load into a kitchen to build into your ROMs.
There is NO .cab installation that I've seen for this version, so you're stuck with either cooking it in, or just replacing the files (there's a zip floating around here somewhere of the files u need to replace to make it the new version, but I don't recall where I saw it).
The OEM can be found in the excellent new PPCGeeks kitchen (ppckitchen.org), which incidentally supported Titan roms now.
For you DCD fans, it seems he hasn't made his rom compatible with the new kitchen GUI, but its relatively simple to make it a basekit. If enough of you push dcd, he might consider doing it... otherwise, you can always copy the OEM directory into DCD's kitchen OEMs.
Click to expand...
Click to collapse
i prefer the functionality of dcd's kitchen over ppcgeeks.... except for the splash screen thing... but it's all opinion
serfboreds said:
This works for me, it is the best of both versions I have seen of the voice software. There are a couple versions out there, this is the most recent I have found. It is a cab.
Click to expand...
Click to collapse
Does this version require you to set tags for contacts?
Thanks
roninld said:
Does this version require you to set tags for contacts?
Click to expand...
Click to collapse
No, it doesn't require you to set tags, but provides that as an option. The tags are useful for frequently called numbers as they should reduce errors somewhat.
This version also works properly through my bluetooth headset including confirmations.
-dwdoc
ok, here is what I did to get it working with DCD:
1. Take the voice command folders from ppckitchen and put them in the OEM folder. There are two folders for the newest version
2. Cook your rom
3. Change the button assignment to VC if you want (settings -> buttons)
4. HKLM\Software\OEM\VoiceCommand change "path" to "\windows\voicecmd.exe"
5. HKLM\Software\Microsoft\Bluetooth\AudioGateway change "BTAGExtModule" to "vcbthag.dll"
Hope that helps you guys!
P.S. On the handset the initial voice prompt beep doesn't work.(the first time you press the button)NOT USING HEADSET
When you dial by the headset the little dial tones come out the handset.
This also lets the phone send ring tones to your headset when it is ringing.
Dishe--thanks for the tip, I googled and found a cab--I have voice command 1.6.17913, and it is a significant improvement over the one I purchased. I can now use my BT headset like I did with my old 6700!! Can anyone confirm this is the most recent build?
jtg
1.9.19209 is available as an OEM in the PPCGeeks Kitchen, but I don't know if there is a CAB of it anywhere.
JimSmith94 said:
1.9.19209 is available as an OEM in the PPCGeeks Kitchen, but I don't know if there is a CAB of it anywhere.
Click to expand...
Click to collapse
I just went through the Kitchen process described above and I get a version number of 1.6.19209. Perhaps just a typo?
whbell said:
I just went through the Kitchen process described above and I get a version number of 1.6.19209. Perhaps just a typo?
Click to expand...
Click to collapse
The Tip in option.xml for this version says, "Microsoft Voice Command - Latest version from kaiser". No2Chem shows as the author, so maybe he will chime in.
JimSmith94 said:
The Tip in option.xml for this version says, "Microsoft Voice Command - Latest version from kaiser". No2Chem shows as the author, so maybe he will chime in.
Click to expand...
Click to collapse
This is what I see also.
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Microsoft Voice Command" group="Voice Control" checked="True">
<Tip>Microsoft Voice Command - Latest version from kaiser</Tip>
<Guid type="p">410788f1-acd5-457b-b9ea-df86ac7f990e</Guid>
<OEMDate>3/30/2008</OEMDate>
<AppVersion>1.6.19209</AppVersion>
<AppAuthorURL>http://www.microsoft.com/windowsmobile/</AppAuthorURL>
<ButtonType>GroupRadioNone</ButtonType>
<OEMAuthor>No2Chem</OEMAuthor>
<Require>93f31b6d-078b-4dae-a335-8ea8c3b22c97</Require>
</Item>
</Items>
I believe it was just a typo and he meant a newer build of 1.6. I have the 1.6.19209 installed from the kitchen and can not seem to get voice dialing to work when I dial by name though. It recognizes the command and will ask me if I want to dial work, home, cell, etc. However, when I confirm it never actually dials. It will work fine if I tell it to just dial a number though. Anyone else experiencing this and know of a fix?
djlenoir said:
I believe it was just a typo and he meant a newer build of 1.6. I have the 1.6.19209 installed from the kitchen and can not seem to get voice dialing to work when I dial by name though. It recognizes the command and will ask me if I want to dial work, home, cell, etc. However, when I confirm it never actually dials. It will work fine if I tell it to just dial a number though. Anyone else experiencing this and know of a fix?
Click to expand...
Click to collapse
There are 3 olders in the PPCKitchen. Voice Command 1.6 (which is the 1.6.17 version), VoiceCommand (version 1.6.19), and VoiceCommand_Lang_0409 (supports files for 1.6.19). I threw the VoiceCommand_Lang_0409 into the SYS folder in DCD kitchen, and VoiceCommand into the OEM. Cooked with no problems.
Have no issues with VC not dialing a contact.
roninld said:
There are 3 olders in the PPCKitchen. Voice Command 1.6 (which is the 1.6.17 version), VoiceCommand (version 1.6.19), and VoiceCommand_Lang_0409 (supports files for 1.6.19). I threw the VoiceCommand_Lang_0409 into the SYS folder in DCD kitchen, and VoiceCommand into the OEM. Cooked with no problems.
Have no issues with VC not dialing a contact.
Click to expand...
Click to collapse
Sorry, which kitchen? I can't find those files...
88fingerslukee said:
Sorry, which kitchen? I can't find those files...
Click to expand...
Click to collapse
After you install the ppcgeeks buildos and update, there is a kitchens folder. In there, PPCGeeks_OEM.rar has these folders.
Related
Hello all. I'm not sure if this has been posted here, but thought I'd post again. I take no credit for this fix. Voice Command works well on my Mogul, running dcd 1.67, but incoming calls were not being announced.
This fixed my problem:
http://forum.xda-developers.com/showpost.php?p=1548114&postcount=5
yeah, I found this before but forgot where it was. Thanks for pointing it out again.
Too bad this still doesn't fix the verification prompt issues
Hi,
Im having a hard time opening the vociecommand file on my desktop. How do I install the file to my mogul (Sprint)
emillz615 said:
Hi,
Im having a hard time opening the vociecommand file on my desktop. How do I install the file to my mogul (Sprint)
Click to expand...
Click to collapse
UNZIP IT! (winzip,winrar,windows xp uncompress utility)
Disable Voice Command before you attempt this
Overwrite your existing (on your mogul) 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.
I need voice announce to work on the T-Mobile Dash 3G
OK. Hi. My name is Chris. I am totally blind. NO seriously I mean it. I have a program on the phone that reads the screen to me called Mobile speak, from www.codefactory.es. Any who, irrelavent as that is, LOL! Basically, here is what I found from talking to HTC. I won't squeel on the lady who told me this, as she said she's not supposed to tell me this, however she felt real bad due to my unique situation with blindness. Basically, the eal is: No matter what phone you use, if it has WM 6.1, this MSVC regardless what hack you use, isn't gonna work with announcing calls. There apparently, was a hotfix that MS did not include in WM 6.1 that was meant to be in there but wasn't. Without this hotfix, htc says hack or not, rom update or not, older/newer version of VC, isn't gonna fix things. They wanna give us the update, but they can't even make it themselves till A, that hotfix is emplemented, or B, W6.5 is released. I can't use the cooked 6.5's as they don't work well with Mobile Speak. Plus the start menu doesn't work period with MSpeak. I got the zip file up here, quit msv, replaced files, restarted, no go no show. still no announcing of calls. She reads everything else fine, but not that. So I present you all with a couple questions. Can I please get the Dash 6.0 version of Windows Mobile from someone with a US Dash 6.0, and put it on here? Yeah 3G won't work any more, and some other things won't either, likely, however, if you all think in theory it would work, I'd be willing to try it. I already unlocked with spl my phone, so, that's all good. If this doesn't work, can you all get me a program as an alternative to VC that will audibly announce calls? I need this as due to my blindness, I can't read the caller ID with MObile speak while phone is ringing as it's drowned out by ring tone. if I turn ringer down, that works except, caller ID only is spoken by MS once, so if I'm outta the room, well, yeah... good luck. you're officially screwed. This unlike you all is not a wanted feature, due to my disability, it's a need, so please! can someone help me. Even if we have to really go a pain in the effin arse's way really round about? I've been reading you all's threads here both related and unrelated to this. Yall're awesome, so surely I say: someone up here's gotta! have some idea. I can't wait for 6.5, then longer for Code Factory to do their magic to get Mobile speak working. I'm sorry, that's just not satisfactory.
Please E-mail me with any help.
[email protected]
Voice Command Call Announce issue
I tried copying the files from the Zip, could only get 3 of the 4 into my phone, made it freeze, had to uninstall and reinstall VC. Still cannot get incoming calls to announce on a newly upgrade ROM.
Here I go again with my upgrading issues. I recently upgraded my ROM to PK Black thanks to olipro unlocker, the whole athena project, HeartofDarkness, and ITXDA. THANKS FOR A GREAT ROM and all your help.
My new issue......I need a voice dialer that works. The dialer that was in the shipped ROM of my 7501 was great. Is there a place that I can get thdialer in CAB to re-install to my device? I am currently using VOICE_Tri. It does work but only when the phone is actively on/unlocked. So if my phone is in my pocket and or locked, I cannot dial. The original dialer worked when my phone was locked or not near me. I really want this back. Can anyone suggest a dialer that works that I don't have to buy? Can I strip it from the HTC ROM?
Thanks in advance.
http://vitotechnology.com/en/products/voicedialer.html
Try this! You might have to purchase this one though!
You're welcome, really.
Do you remember what you used prior to upgrading ?
Heavyweights are:
- Microsoft Voice Command (doesn't need training);
- Cyberon Voice Dial (requires tagging).
Both are commercial products, but since you rightfully own a device that was provided with either, there shouldn't be much problems if you did bit of searching on the forum or googling and found workable archives...
HeartOfDarkness said:
You're welcome, really.
Do you remember what you used prior to upgrading ?
Heavyweights are:
- Microsoft Voice Command (doesn't need training);
- Cyberon Voice Dial (requires tagging).
Both are commercial products, but since you rightfully own a device that was provided with either, there shouldn't be much problems if you did bit of searching on the forum or googling and found workable archives...
Click to expand...
Click to collapse
The voice dialer I was using previously was included in the shipped firmware on my 7501. I have no idea who made it or if it was simply part of the ROM. I did try the one offered on mahmood's site and it seems to be working well enough for now. I will use this latest one until I find another. I did have Microsoft's version when I had other devices but I often had trouble using it with a BT device. There was one that I read about that announces your incoming calls and other little neat things, but with all my reading, I forgot its name. So, long story short, I am ok for now, but still always on the prowl for biger, better, faster, smarter, easier etc.
So keep me in mind if something surfaces that is a dowlaoad (pref. free) that I can try.
BTW, do you know how to get PocketCM off of my device?
Kenjari said:
http://vitotechnology.com/en/products/voicedialer.html
Try this! You might have to purchase this one though!
Click to expand...
Click to collapse
Looks like it would one to try, but do you know if it is unistallable once it's on. I still trying to get Pocket CM out of my device.
you might have to use a registry delete on that one. some how it installed in your registry...thats why you cant easily remove it. try resco registry. you should be able get in and delete it with that software.
BTW...that link to that Voice dialer...yes it removes once you go into settings and Remove Programs. I dont think however, that it gives you the option to save your settings. But who cares.... Good Luck buddy!
Kenjari said:
you might have to use a registry delete on that one. some how it installed in your registry...thats why you cant easily remove it. try resco registry. you should be able get in and delete it with that software.
Click to expand...
Click to collapse
I have never used a registry editor. How does it work? What do I do?
Hello!
I would like to get a copy of DCD's kitchen for his rom 3.2.0 and 3.2.2 (or the closest one to that).
The reason for that is that I want to compare what has changed between the two and hopefully locate the file that makes it so that skype 2.1.0.66 hasn't been working anymore since 3.2.x versions.
Somehow, DCD's site is down and I can't locate those files I need.
Any help?
Thanks!
i have the rom on my hard drive and 3.2.2 as a kitchen. if google dosnt find it i can send them to you
stanelie said:
Hello!
I would like to get a copy of DCD's kitchen for his rom 3.2.0 and 3.2.2 (or the closest one to that).
The reason for that is that I want to compare what has changed between the two and hopefully locate the file that makes it so that skype 2.1.0.66 hasn't been working anymore since 3.2.x versions.
Somehow, DCD's site is down and I can't locate those files I need.
Any help?
Thanks!
Click to expand...
Click to collapse
Here's a link to the last several Kitchens.....
http://dcd1182.n715dp.com/titan/kitchens/
stanelie said:
the file that makes it so that skype 2.1.0.66 hasn't been working anymore
Click to expand...
Click to collapse
is msxipkernel\nk.exe
Thanks DCD.
Is there an adverse effect in replacing that file in your newer rom? (aside from making skype work?)
Hum...
NK.exe is THE kernel...
Switching it might be a bad idea I guess, it might break lots of things?
Stuck on 3.2.0 until skype fixes their software I guess...
stanelie said:
Thanks DCD.
Is there an adverse effect in replacing that file in your newer rom? (aside from making skype work?)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2426507&postcount=46
Since dcd knows which file causes the issue and hasn't found a decent workaround/replacement for the file, I'd be willing to bet it isn't a "plug-in the file from a different WM version" fix. As I recall this was a pretty hot issue when WM6.1 surfaced and I believe the post below might say it best.
http://forum.ppcgeeks.com/showpost.php?p=434875&postcount=52
It seems Skype isn't interested in supporting our phone and they have the resources of eBay. If they wanted to support us (and a vast number of other phones,) they could..... but they don't. That's called a "marketing decision" when big corporations do it..... specifically, a "poor marketing decision."
I've seen services called "iSkoot" and "Nimbuzz" mentioned as alternatives.
Well,
I just tried both : Nimbuzz does not hear anything from my Titan's microphone and iSkoot wants to call their gateway with a regular phone call, which is long distance for me, so, it's out of the question.
I also do not get any audio with fring on my phone.
Any other ideas before I flash back to DCD 3.2.0?
imo, this was due to an idiotic/crappy/lazy slap wm6.0 code into wm6.1 platform builder move by HTC ... It worked, with some weird side effect on code that uses critical sections it seems... well, not all code... mainly multimedia apps (such as tcpmp). Unfortunately, until HTC fixes the kernel with the correct code, we are out of luck.
3.2.1 and above also broke SRS WOW
it seems the kernel update broke a few media apps...specifically the ones the tried to interface with the audio or mic
no2chem said:
imo, this was due to an idiotic/crappy/lazy slap wm6.0 code into wm6.1 platform builder move by HTC ... It worked, with some weird side effect on code that uses critical sections it seems... well, not all code... mainly multimedia apps (such as tcpmp). Unfortunately, until HTC fixes the kernel with the correct code, we are out of luck.
Click to expand...
Click to collapse
the kernels are device specific? i thought they're coded by microsoft and deployed by the manufactures like windows for PCs...that's news to me.
anyone seen this on the PCD website, an MR2 upgrade? whats it do? any ideas?
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Changes from MR1 to MR2:
Radio:
3.37.75 to 3.37.78
Imgfs:
OEMDrivers\msm7500usbfn.dll
OEMDrivers\gpsid_qct.dll
OEMDrivers\oemgpsone.dll
OEMApps\62d9d90d-ce88-4d26-80bf-501516399504.rgu
XIP:
OEMXIPKernel\nk.exe\S000
The XIP change just updates the build date. The rgu change adds this:
[HKEY_LOCAL_MACHINE\Software\HTC\PhoneInfo]
"FixedERIDestination"="ERI/00004"
DCD, I may have it wrong but you don't seem to be a guy who appreciates the 'mushy' moments. Warning, mushy moment ahead...
Welcome back DCD! We missed you!
...end mushy moment.
Did you get your computer fixed then?
dcd1182 said:
Changes from MR1 to MR2:
Radio:
3.37.75 to 3.37.78
Imgfs:
OEMDrivers\msm7500usbfn.dll
OEMDrivers\gpsid_qct.dll
OEMDrivers\oemgpsone.dll
OEMApps\62d9d90d-ce88-4d26-80bf-501516399504.rgu
XIP:
OEMXIPKernel\nk.exe\S000
The XIP change just updates the build date. The rgu change adds this:
[HKEY_LOCAL_MACHINE\Software\HTC\PhoneInfo]
"FixedERIDestination"="ERI/00004"
Click to expand...
Click to collapse
I appreciate the help DCD, now can you please explain in slightly simpler terms whether you think I should install this or not? currently on the MR1 rom and the GPS unlock, and I have been pretty happy with my 3.37.75. I dont know what the imgfs stuff you said is about. Thanks and im honored you repsonded to a post of MINE!!!! LOL THANKS.
tmanner said:
I appreciate the help DCD, now can you please explain in slightly simpler terms whether you think I should install this or not? currently on the MR1 rom and the GPS unlock, and I have been pretty happy with my 3.37.75. I dont know what the imgfs stuff you said is about. Thanks and im honored you repsonded to a post of MINE!!!! LOL THANKS.
Click to expand...
Click to collapse
I think the radio gets updated from 3.37.75 to 3.37.78 and there are three newer files, msm7500usbfn.dll, gpsid_qct.dll and oemgpsone.dll. He says the XIP change just updates the build date and the .rgu file changes the registry key
[HKEY_LOCAL_MACHINE\Software\HTC\PhoneInfo]
"FixedERIDestination"="ERI/00004"
Looking at the new files, msm7500 is the chipset so it looks like this might be an updated usb driver. The other two files deal with the GPS chipset. The registry change though I'm not sure what the FixedERIDestination key does but it looks like it has to do with the phone.
This is mostly speculation though and if I'm wrong, I apologize for the misinformation.
I do wonder if the MR2 has to do with Verizon's change of stance on locking out 3rd party GPS apps. Anyone try this update?
I tried it (getting a new 6800 tomorrow as the slider is dead on this one). 24.6 meg at start up. NO GPS. Will use DCD on my new one tomorrow.
The 'readme' included with the update says:
Some of the primary enhancements with this upgrade are:
• Enhancement to VZNavigator performance.
• Voice calls performance improvement on Motorola network.
Too bad they did not provide any other information....
I'm tempted to install this to see if I can get better call quality at home. Is there any way to determine if a particular location is 'on Mototola network'?
can't get GPS work with tomtom 7 after upgrade to MR2
wet back to dcd 4.1.2 cuz no GPS lock
I'm running the MR2 ROM and my impression is that it feels and works very similar to the MR1 ROM (no real surprise given the tiny change log) The GPS fixes I'd been using on MR1 work just fine on MR2.
I dont use many programs, but the stuff I run seems to work great
* BAF's GPSToggle
* Skywing's GPSServer
* Live Search
* Mochasoft 5250
* Outlook
* Internet Explorer
* ArcSoft MMS
* Cyberon Voice Recognition
Memory at boot:
Total: 46.92
Used: 22.20
Free: 24.72
FYI, .NET 3.5 will not install on this new ROM.
I contacted Verizon, waiting for a response
i recently have the MR2 on my tp2 but im gettin a notification when i send a mm message. the message i get is" Connect- in order to send/download MM messages, the currentactive connectionmay be closed (this may affect other applicationsin use). do you want to continue" and it will not send unless i select yes and it get the same notification when receiving MM messages also. does anyone know how to get this thing off, anyone else gettin this notification on there screen. im with verizon
gmm6797 said:
FYI, .NET 3.5 will not install on this new ROM.
I contacted Verizon, waiting for a response
Click to expand...
Click to collapse
Worked fine for me, I used the same CAB that I'd used on the MR1 ROM. I think GPS Weather Radar and maybe WiFiFoFum use .NET, both work just fine.
horbeme said:
i recently have the MR2 on my tp2 but im gettin a notification when i send a mm message. the message i get is" Connect- in order to send/download MM messages, the currentactive connectionmay be closed (this may affect other applicationsin use). do you want to continue" and it will not send unless i select yes and it get the same notification when receiving MM messages also. does anyone know how to get this thing off, anyone else gettin this notification on there screen. im with verizon
Click to expand...
Click to collapse
I'm getting this too, I found a CAB that claims to disable this but it makes a whole lot of other "tweaks" that I don't want. I suspect there's a registry setting but don't know what or where. Hopefully somebody will come up with a fix.
.NET CF 3.5 is required.
UPDATE (3/29/10): Version 0.10 Released - See Post 77 for Change Log.
UPDATE (3/11/10): Version 0.9 Released - See Post 67 for Change Log.
UPDATE (3/8/10): Version 0.8 Released - See Post 63 for Change Log
UPDATE (3/3/10): Version 0.7 Released - Only changes are some registry settings that I missed earlier. With this, both Caller ID Announcements and Voice Dialing should work with this installer.
UPDATE (3/3/10): Version 0.5 Released - See Post 55 for Change Log - Device List below updated ... Updated v0.6 with auto start on device boot attached ... If you are using v0.5 (or v0.5_autostart which I screwed up ... sorry), uninstall it and install the v0.6.
Device List (Updated 3/8/10)
Known Working Devices
HTC Titan
HTC RhodiumW (Touch Pro 2)
HTC Rhodium (Tilt 2)
NOT Known Working Devices - If anyone uses a device listed here and my app, please let me know if it works.
HTC HD2 - I think this is similar to the TP2 - Should work, but I need someone to confirm this
Sony Ericsson XPERIA X1 - I have no idea ... Does this device use the WIDCOMM Bluetooth stack? Can someone test the latest app?
If you install this app, and have problems, uninstall msvcFix and install "revert_msvcFix.cab"
UPDATE (8/11/09): I have fixed the native app (now referred to as v0.3) and attached. I will leave the v0.1 attached as well.
UPDATE (8/10/09): Sorry, but there is something wrong in the native v0.2 ... I have posted the orig v0.1 in the mean time.
Not sure what devices this effects/fixes, but on my Titan, Voice Command incoming caller ID announcements don't work correctly. The work-around I use is ...
To enable caller ID announcements:
Set HKCU\ControlPanel\Sounds\TTSAnnounce\Category to "Ring"
Set HKCU\ControlPanel\Sounds\RingTone0\Category to "_Ring"
Set HKCU\ControlPanel\SoundsCategories\Ring\initVol to 15
To disable caller ID announcements:
Set HKCU\ControlPanel\Sounds\TTSAnnounce\Category to "_Ring"
Set HKCU\ControlPanel\Sounds\RingTone0\Category to "Ring"
Set HKCU\ControlPanel\SoundsCategories\Ring\initVol to 5
I have written a program to address these "fixes". My program checks the MSVC "Announce incoming caller ID" option, and checks to see if bluetooth is paired and headset service is active. If all these checks pass, I set the "enable" registry settings ... If not, set the "disable" registry settings.
Currently, the default interval is 5 seconds. I intend to make the interval a setting in the registry in the next version. Attached is a CAB install for version 0.3. The CAB will install the EXE to \Program Files\dj13241\ and create a shortcut in \Windows\Startup\ (it will auto-run on device boot). Version 0.1 was written in VB .Net, and took up to ~1.5 MB after running for some time. This version (v0.3) was written entirely in native C and compiled with cegcc-mingw32ce-gcc on Linux, and takes up 32 KB! Quite a memory improvement!
Feedback anyone?
Anyone have any feedback on this? Should I spend the time to improve it? Any feature requests? Anything?
Tilt2
Tried it on Tilt 2 and does not work. Caller ID still gets announced thru handset speaker
I am interested in your success...
186227 said:
Tried it on Tilt 2 and does not work. Caller ID still gets announced thru handset speaker
Click to expand...
Click to collapse
I think I know what the problem is ... I don't have my earpiece with me to test it though. Are you comfortable using a registry editor? If so, please post the values for the following keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModule" =
"Capability" =
Also, please look in your \Windows\ directory for a file called "vcbthag.dll" ... You will have to check off 'Menu->Show all files' in order to see dll files.
Thank you for the constructive feedback!
howdykeith said:
I am interested in your success...
Click to expand...
Click to collapse
Good to know that someone is!
Do you use this on your phone?
I too, am interested in your success.
dj13241 said:
If so, please post the values for the following keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModule" =
"Capability" =
Click to expand...
Click to collapse
Here are the values requested:
"BTAGExtModule" = BTRilProxyOEM.dll
"Capability" = 0x65 (101)
I am VERY interested in getting incoming caller ID to announce over BT on my Tilt 2. If you get this, you are officially the ruler of the universe!!!
I'm interested, will give it a try on my HD2
Hi and thanks for all the great info.Please forgive me (newby) to winmo,i installed ms voice commander and installe the Voice Command Announcement Fix and it still wont announnce the caller calling.Has anyone got any insight to the problem.
Thankyou
Sorry, not working on HD2 either
pity.. does not work on xperia x1 either..
I'm on it ...
I have a Touch Pro 2 and with some registry mods (quite a hack job at this point), I got it to the point of announcing Caller ID without playing a ringtone, but it announced from the phone's external speaker and my earpiece played its internal ringer. It looks to me like a timing issue ... VC creates a file \Application Data\Volitle\TTSCallerID.wav which is the caller ID announcement ... I think that the delay involved with creating that file is causing the issue, and by the time the file is created, my earpiece is already ringing with its ringtone.
On another note, my original program is (apparently) dependent on a different Bluetooth stack that the TP2 (which uses the wildcomm stack) ... If anyone knows how to check for a BT headset via native API, I would love to know!
I will be editing the first post when I have some time later tonight ... I will add "known working" and "known not working" phone lists ... Looks like the "not working" list will be longer for now
Thanks for all the feedback so far.
The Tilt 2 also uses the Widcomm BT stack. We've been blaming everything on the Widcomm stack, but I've begun to suspect that the aging MSVC software is really more to blame as it doesn't know how to play nice with newer software. Of course, I remember all of us soundly denouncing MSVC a few years ago about not being very compatible with the MS BT stack either!
I think you are definitely on to something. Yes, the hacks you have may be a bit kludgy but accurate. A suggestion: forget the checks to see if BT enable or not for the time being; leave BT enabled and do all reg changes, etc with the assumption that BT is enabled and connected. Forgive me if that sounds condescending -- I lost all my programming skills about the time Turbo Pascal died, if anyone here even remembers that from the early 80s -- but sometimes an outside view can make a small difference.
Always willing to try any hacks you suggest to see how they work on my stock Tilt 2; feel free to PM fi there's anything I can do to help.
Hi,
I have a TP2 with Stock ROM and have no problems with announcing phone calls, but..
You may already know about the bug when an "unknown caller" calls. VC does three things choosing randomly:
- 1. Does not announce anything, phone does not ring
- 2. does not anonunce anything, phone rings for a sec.
- 3. does announce the LAST CALLER - and this is really annoying, when you think you have a call from a friend or something, and it turns out VC just scammed you badly.
So my question is can you fix at least the 3rd behavior?
mydexterid said:
Hi,
I have a TP2 with Stock ROM and have no problems with announcing phone calls, but..
QUOTE]
So your TP2 announces your incoming caller ID over your BT headset? Really?
Click to expand...
Click to collapse
jlmwrite said:
mydexterid said:
Hi,
I have a TP2 with Stock ROM and have no problems with announcing phone calls, but..
QUOTE]
So your TP2 announces your incoming caller ID over your BT headset? Really?
Click to expand...
Click to collapse
I have a wired headset.
Is this thread only about the BT headset bug? Then the title should be modified. It is not really clear from the title/1st post that what announcement fix is this.
Click to expand...
Click to collapse
mydexterid said:
I have a wired headset.
Is this thread only about the BT headset bug? Then the title should be modified. It is not really clear from the title/1st post that what announcement fix is this.
Click to expand...
Click to collapse
Its good to know this info though ... Do you have a BT headset you could try it with? Has anyone else tried with a stock ROM, or is everyone using custom ROMs?
I'm going to dump the stock ROM registry and compare it to what I am running (which is a ROM built from Calkulin's 1.5 Beta Kitchen with a few of my own MODs).
Nope. The device itself gives me enough radiation I don't need more from a bluetooth device
dj13241 said:
Its good to know this info though ... Do you have a BT headset you could try it with? Has anyone else tried with a stock ROM, or is everyone using custom ROMs?
I'm going to dump the stock ROM registry and compare it to what I am running (which is a ROM built from Calkulin's 1.5 Beta Kitchen with a few of my own MODs).
Click to expand...
Click to collapse
For inspiration on MSVC you could also read my thread