Database Info

OEMAGW.dll

OEMAGW.dll appears to be missing from my windows mobile 6 universal, i think its needed for voice speed dial to work over bluetooth... Im trying to switch back to voice speed dial as voice command doesnt seem to do anything (im guessing it needs training, but i cant see how to train it). Can anyone make this file available for me as I really need speed dial for my car's hands free headunit. Thanks in advance.

hotrodder said:
OEMAGW.dll appears to be missing from my windows mobile 6 universal, i think its needed for voice speed dial to work over bluetooth... Im trying to switch back to voice speed dial as voice command doesnt seem to do anything (im guessing it needs training, but i cant see how to train it). Can anyone make this file available for me as I really need speed dial for my car's hands free headunit. Thanks in advance.
Click to expand...
Click to collapse
Hi there,
I have uploaded the voice dial on the following thread:
http://forum.xda-developers.com/showthread.php?t=345256&page=7
I am not sure if this is what you are looking for!
KOR!

OK, thanks , im gonna give it a go, re-installing using that cab, and using the REG file... I was just after the dll for the OEM bluetooth audio gateway.
If i explain the problem i have maybe someone will have experienced it before. I recently flashed with JWRIGHT's rom (FANTASTIC BTW ) but it comes with voice command not just voice speed dial... which i cant get to work (pretty sure its me doing something wrong), anyway im quite happy with voice speed dial, so i want to just use that instead... I install it, apply a couple of REG fixes (just pointing to SDDIALER i think) and set it up on the button. When i press the button it works fine, but when i use bluetooth it appears to activate both voice speed dial and voice command at the same time. I get two seperate bleeps, one from speed dial and a different one from voice command, then if i dont say what its expecting it asks me to please repeat... they seem to conflict and as such it doesnt work. I think that its is something to do with the bluetooth gateway, so i just want to point the registry to the standard one... but i cant find it in the windows folder... The DLL is OEMAGW.dll .
Im hoping if i can get that and update the registry it will work... i could be wrong as im still new to playing with new roms and stuff.
Off topic a little, Im interested in trying to cook my own roms, but i dont know where to begin... im a programmer by trade but i dont really have any experience in this sort of thing. Any help or advice would be appreciated.

HTC Bluetooth Hot Fix

Hi,
HTC today posted a hot fix for bluetooth at their e-Club.
Description:
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Br,
Mads

Downloaded it from HTc.cOM
Installation instructions
Follow the instructions below to download and install the hot fix on your device:
Make sure you have Microsoft ActiveSync® installed on your Windows XP PC or Windows Mobile Device Center on your Windows Vista® PC. You can find Microsoft ActiveSync from this link or Windows Mobile Device Center from this link.
Connect and synchronize your device with your PC via Microsoft ActiveSync® or Windows Mobile Device Center using the USB cable.
To download thehot fix, first select the check box below. Next, select thehot fix and the desired FTP site then click Download.
Copy the hot fix, which is a cab file, to your device.
To install the hot fix, tap the cab file and follow the on-screen instructions.
Here is the file:
http://rapidshare.com/files/77588898/TyTNII_BT_Hotfix.zip
Enjoy,
Nadavi

Extracted madsnm's posted cab, which is the same as nadavi's. This is a replacement file for OEM\OEMDrivers\TIInit_4_2_38.bts (a.k.a. \windows\TIInit_4_2_38.bts for non-chefs).
I've re-attached it as the naked file (without the cab installer or the self-extracting exe installer).
Any decent chef should be able to figure out how to turn a single file into an OEM package
Edit: Forgot to add that there are no registry entries, as I've already created registry dumps before/after install...
Edit3: It *IS* the same as the one in the AT&T 1.60 ROM. I did a file compare and there are no binary differences.

Although I am not having any problems as mentioned in the fix log, but the idea of HTC releasing something for us is great .

taiseer999 said:
Although I am not having any problems as mentioned in the fix log, but the idea of HTC releasing something for us is great .
Click to expand...
Click to collapse
Thats right!
Waiting for WM6.1 ROM! or maybe new WM06 Full Touch rom from HTC....
Just my two Cents....
Nadavi

Nadavi said:
Thats right!
Waiting for WM6.1 ROM! or maybe new WM06 Full Touch rom from HTC....
Just my two Cents....
Nadavi
Click to expand...
Click to collapse
well, 6.1 ROM doesnt really looks appealing to me, i believe most of us would want our freaking D3D driver to improve our kaiser speed.
come'on HTC, give us our driver. We want our kaiser to work @ its full potential!
almost forgot, to the brothers at the top 3 post, THANKS for sharing!

Solved my "bad" connection to the BT carset - thx....

ruffruff said:
well, 6.1 ROM doesnt really looks appealing to me, i believe most of us would want our freaking D3D driver to improve our kaiser speed.
come'on HTC, give us our driver. We want our kaiser to work @ its full potential!
almost forgot, to the brothers at the top 3 post, THANKS for sharing!
Click to expand...
Click to collapse
OT but the driver is there. Look here for more info. There's also an XDA thread on this. We just need to tweak it out for general purpose acceleration.

Sleuth255 said:
OT but the driver is there. Look here for more info. There's also an XDA thread on this. We just need to tweak it out for general purpose acceleration.
Click to expand...
Click to collapse
It doesn't say much if they hacked something for Coreplayer, or it was a general fix from HTC for all Windows Mobile devices running the MSM chipset.
Would be nice if the Kaiser was as snappy as that dual-keyboard Pantech running WM6 Standard.
I'm at loss to say if all the UI (and general system) lag is from too much use of .NET, lack of hardware accelerated graphics drivers, or Pro just runs slower than Standard because of the touch-screen support.

Hmm...wonder why i didn't get an email from the e-Club about this. I log into the site and find the fix just fine but I thought I'm supposed to get a notification about it (i'm pretty positive that was my preference when signing up)
Anyway, does this hot fix help in pairing bluetooth with car kits and devices that had problems or were incompatible thus far.

I've never experienced dropped calls with my BT connection, but I do have another problem that is pissing me off.
I have two different Pioneer stereos in two different vehicles. The AVIC-Z1 and the Premier DEH-P980BT.
When I first try to initiate a call with the 980, the connection is made, but the audio is somewhere in limbo between the phone and car speakers. There is a BT connection, but it takes about a minute and a half to actually start sounding through the speakers. By that time, the receiving end has hung up.
Since it only happens for the first call of the ride, I've been getting in the car, calling my voicemail, and waiting until I can hear the voicemail prompts. After that, I can make and receive call normally until I shut the car off.
If this fixes the problem I'm having, I'll be ecstatic.

Hi,
I have no noticable problems with BT exept the sound quality. Will be anything better or maybe worst if I install this upgrade? Does anybody have experience on it?
Thx
Mikus

NuShrike said:
It doesn't say much if they hacked something for Coreplayer, or it was a general fix from HTC for all Windows Mobile devices running the MSM chipset.
Would be nice if the Kaiser was as snappy as that dual-keyboard Pantech running WM6 Standard.
I'm at loss to say if all the UI (and general system) lag is from too much use of .NET, lack of hardware accelerated graphics drivers, or Pro just runs slower than Standard because of the touch-screen support.
Click to expand...
Click to collapse
Sounds like they had to change something with the drivers. So they're there but poorly implemented. And sounds like they'll give us driver info once its released. I'll buy it if it fixes the D3D support!

Still garbled on my Tilt with an Infinity G35..now how do I deleted the Kai6492_HotFix from my Programs directory? I can't see to find it...yet the icon is still there. Any one know?

Flapjack said:
I've never experienced dropped calls with my BT connection, but I do have another problem that is pissing me off.
I have two different Pioneer stereos in two different vehicles. The AVIC-Z1 and the Premier DEH-P980BT.
When I first try to initiate a call with the 980, the connection is made, but the audio is somewhere in limbo between the phone and car speakers. There is a BT connection, but it takes about a minute and a half to actually start sounding through the speakers. By that time, the receiving end has hung up.
Since it only happens for the first call of the ride, I've been getting in the car, calling my voicemail, and waiting until I can hear the voicemail prompts. After that, I can make and receive call normally until I shut the car off.
If this fixes the problem I'm having, I'll be ecstatic.
Click to expand...
Click to collapse
here's what causes that issue on my phone:
hit the ms voice command button and hear the beep prompt.
now hold the button down till you get the cancel beep.
now make a call. you will get no audio either direction.
turn the phone off, and the sound starts working. turn it back on and it's gone again.
key the ms voicecommand button again and let the time expire instead of holding to cancel.
make another call, and the audio will be fine, except for a 5 to 10 second delay.
see if this is how your phone behaves also. if I don't ever cancel a ms voicecommand by holding the button down, everything seems to work fine.

After installing the "fix" I could no longer use voice dial with any of my bluetooth headsets. Uninstalling the fix fixed it.....go figure.....

I think that HTC really need to have more, serious, knowledgable beta testers to tryout this stuff with various software and hardware scenarios before releasing the device. Some of these "bloggers" that they send new, unreleased devices to are either cronies or don't know much, or will not test the devices thoroughly and/or report back to HTC what problems that they experienced. I am a Verizon and AT&T user. Have seen these anamolies between diferent devices for some time now. The Mogul and XV6800 don't have the same issues we have, however, I guarantee you they do have others such as the De-activated GPS flaw that happened recently in the Mogul.

Unfortunately my Kaiser didn't work still with this hotfix. I installed on my device few times, I rebooted the headset and nothing. Probably it's like that because my ROM is 1.83, it's original polish version of it. How can I resolve the problem of bt headset ?

The fix file is a CAB (download from HTC e-club)... I install the CAB and find a link under software menu... I tap it... and another installation is done... I must soft reset the device... and stop...
Okai... so I think in this way the fix is gone... but... I have yet the cab installed under Software CAB and Installed application... can I uninstall it? The trashes pissing me :-D

or for att users go here....
http://forum.xda-developers.com/search.php?searchid=8811535

Microsoft Voice Commander Not Working

When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?

I'm using 1.6.21040.
Gave an error during installation, but seems to be working as far as announcing calls and reading texts.

I have tried to installed version 1.6.21725 and it seems to work fine, but I tried to link to the key virtually using AE Buttons, everything collapsed. The lnk file just got deleted: any suggestion.
How did you guys use to assign to a key?

Was asking the same question. Install worked with one error message. The program works when I start it manually, but I cannot find a way to assign execution to a specific button press. Looking for ideas here.
Toby

i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way

I've switched to 21725 and used aebutton plus to assign it to long press windows key, all works perfectly now.

I dont want to use aebutton plus, so I tried to use the old Long_Send.lnk and had no luck, am I doing something wrong?
or is it a diffrent name in 6.5

MSVC
I got that error too but it has stopped for some reason and now works well.
Version is v1.6.21040
I tried to upload a cab for you but it wouldn't upload.
I use MSVC for text to speech, to announce calls, read emails to me and announce calendar reminders.
This version won't read text msgs.
I don't use it for voice commands, Cyberon Voice Speed Dialer is much better for that.
mallman said:
When i try to run Voice Commander I get an out of memory error. I am running version 1.6.19209 Anyone else tried this or gotten it to work?
Click to expand...
Click to collapse

mallman said:
i didnt link the button once i got the latest version installed and working. i jsut made a link and put it on the start menu instead and it works great that way
Click to expand...
Click to collapse
WHICH LINK DID YOU USE, THE SHORT OR LONG ONE??
Thanks!

I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.

MSVC cab
Oops!
Got it.
NotATreoFan said:
I got this error on the stock TP2 ROM as well. For me, it only occurred when I checked the box for announcing WMP selections.
Oh, regarding the MS Voice Command CAB, while it is not the reason the upload failed, XDA does not allow MSVC to be posted in CAB form since it can then be installed on devices that it is not licensed for.
Click to expand...
Click to collapse

So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.

bill340 said:
So was anyone able to get MSVC running with a bluetooth headset??
I mean initiating MSVC commands via the headset button and also get the commands itself in the headset?
I cannot get it run like this.
Click to expand...
Click to collapse
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.

I Think I've Found An Answer
If you go into the registry and go to:
\\HKLM\Software\OEM\VoiceCommand
and edit the value for VoiceCmdEnable to 1 (it was set to 0 on my HD2), then soft reset.
Now you should be able to get Voice Command working through BT, at least it's working for me at the moment.

It does not help fo rme at all...
No change!
Which version of MSVC do you use?

I'm not entirely sure, but in the Voice Command settings it shows v1.60.4622.0

weepatc said:
When I start MSVC, the command is repeated through the headset first time then it comes through phone speaker after that. Phone calls are directed through the headset ok. Strange.
Click to expand...
Click to collapse
In my case it is very similar, but when i activate voice command with the assigned button on my HD2 and not via the headset, everthing works as it should. Maby thats a indication how to get it worki`n the right way.

VoiceCommander Working
Hi,
Initially I couldnt get the BT to connect to VC (just got a BT disconnect beep in my ear).
Tried installing 2nd time (over the top), and seemed to 1/2 work but sometimes I would have to say name I wanting to dial through handset - then it would put call through BT - strange.
Finally, I noticed that if the BT headset was on when the phone was switched on (fluke that happened), it worked fine.
If the BT headset is switched on after the phone, it still plays up. Not tried turning BT on handset off and on whilst BT headset turned on yet - something to try tonight I guess.
Note : this only started working a day or so ago so not tested throughly yet.
My VC version is 1.6.4622.0.
I also noticed that on handango - a new VC version is available (updated 20/11/2009) which says works with Touch HD2 - but only USA voice at the mo so I'm waiting for the UK (hopefully released soon).
Hope the above helps.

Looks like I have an old version of Voice Command MSVC1.6.19214. How do I get a later version? Don't see why I should have to pay for it again when it is still 1.6.

Sorry, my bad - not working anymore. Worked for one day, then I get the same as everyone else

Bluetooth A2DP now on Jawbone ICON earpieces

So sweet. Jawbone now has an update for the Jawbone ICON which allows it to pair as an A2DP device. This means I can route all sound to it: music, movies, navigation, FartDroid, Robo Defense, etc.
There has never hasn't been a fix for this since the 1.5 ROMs. I'm on Fresh 2.0d
This awesome earpiece can be had for around $75 if you look hard enough.

Happy he posted... I am very happy, since I already have an ICON but didn;t know this

maybe not a big issue with people on this forum but this was a huge android issue in general. pissed a lot of people off.

HeroMeng said:
And, this was important enough to post a new thread about? Sorry, but it's cluttering up our tiny forum.
Click to expand...
Click to collapse
Holy ****. This just cluttered up this thread.
This was a huge deal with Android and Jawbone just solved it for me.

Good to know. Knew I got my Icon for something. Thanks for the info.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

Can the ICON connect to the phone and allow voice dial ? Thats one feature I miss. All the crazy advances and this is one feature that hasnt been fixed. Oh well. By the way the Q1 does the ad2p thing and also allows 8 presets that allow the unit to at least connect and call out which is handy. It also allows you to connect hands free with just your voice. Not too big of a deal if your driving but if your a biker it's a pretty awesome feature ;-)
I wonder how hard would it be to program an app to wait for the button press on a headset and set it to use the voice recognition on the phone that is used by google search/nav etc...

jcf304 said:
Can the ICON connect to the phone and allow voice dial ? Thats one feature I miss. All the crazy advances and this is one feature that hasnt been fixed. Oh well. By the way the Q1 does the ad2p thing and also allows 8 presets that allow the unit to at least connect and call out which is handy. It also allows you to connect hands free with just your voice. Not too big of a deal if your driving but if your a biker it's a pretty awesome feature ;-)
I wonder how hard would it be to program an app to wait for the button press on a headset and set it to use the voice recognition on the phone that is used by google search/nav etc...
Click to expand...
Click to collapse
Maybe it was a multi phone pairing issue, but I found that the Q1 didn't reconnect automatically if I walked away from the headset with the phone or vice versa. Also didn't like that the buttons were easy to press and hence a lot of pocket headset redials...
I am very stoked with the a2dp on the icon as that's the headset i had just before being convinced by someone else that the q1 was the way to go and since having gone back to the icon
Thanks for the info, I forget that the icon is updatable and haven't checked in a while...
r

seeing as this is a relatively active bluetooth-related thread, i was wondering if someone could answer a q for me.
im on fresh 2.0d and whenever I tried to play anything via A2DP in my car, the audio was sped up and always skipped about every second...has anyone else experienced this? if not, could you tell me which ROM you are using so I could give it a try?
appreciate any info anyone can offer...thanks

jcf304 said:
Can the ICON connect to the phone and allow voice dial?
Click to expand...
Click to collapse
Here's a bit of info on the Jawbone ICON website: "To encourage Google to support voice dial via Bluetooth on the Android OS, vote at Google product ideas or post a reply on Motorola's DROID forum."
I have found that the Voice Search app works a little better than the Voice Dialer app on the Hero. I just place a shortcut on my home screen. If I open the app and say, "Call Dennis at Home," it will dial home right away. Not quite "hands free" dialing, but as close as I can get for now.

[Q] ROMS that support BT Voice?

I just finished installing all the stereo parts in my car only to find out that my Captivate won't work with the voice dialing of the stereo. I guess it's the phone's fault as my wife's Focus works just fine as did my old HTC Pure. She won't trade phones with me so I'm stuck trying to find a ROM that has this.
With Samsung stating it will be fixed (added) in 2.2.1; does that mean only the 2.2.1 ROMS will have this feature? I'm currently running Cognition 4.3.1 and it does not have it; but would like to only try new ROMS that have it. What ROMS do have the feature?
Thank you for your input.

Firefly supports voice dialing. You have to start the Voice Dialling app and then say the command.

What I'm looking for is what the Droid Incredible has. I paired it to my stereo and when I hit the call button on the stereo; it launched what appeared to be a bluetooth voice dialer application that allowed me to speak into the stereo.
I just tried firefly and it did have that app, but it crashed as soon as I tried it. It also crashed the music app, failed to mount the storage drives, crashed when trying to put it in debugging mode and pretty much was unstable since it booted. I then tried to use one click odin and it went to a blue screen half way through the process. It'll be a fun night.

Probably not what you want to hear, but my BT in the car works great on my 'stock' set up. I think it has more to do with the kernel/ modem configuration than the ROM though.

dragon has this. many people are pairing it with choice dialer.

Dani897 said:
dragon has this. many people are pairing it with choice dialer.
Click to expand...
Click to collapse
I can't get Choice Dialer to work well at all. ONe example: "CAll Tom Jones", it says "CAll Tom Jones?", I say "Yes", it says "Try again". Argh...
ANd most of th time it just doesn't understand me at all.

I believe this is the apk you need. I know cog doesn't come with it. This is an old one so I don't know if there is a newer version available but when you pair your bluetooth and hit the voice command on your stereo or bluetooth set, make this the default app when the prompt shows up. It won't give you a voice prompt but if you wait 2 secs and then speak it should dial for you. Only problem is that your phone has to be awake but at least you can use voice commands from your bluetooth set. Just leave your phone plugged in and awake while your in the car. This is the only option I have found.

That worked.
Thank you for the apk. That works.

ewingr said:
I can't get Choice Dialer to work well at all. ONe example: "CAll Tom Jones", it says "CAll Tom Jones?", I say "Yes", it says "Try again". Argh...
ANd most of th time it just doesn't understand me at all.
Click to expand...
Click to collapse
It's not unusual to be called by anyone
It's not unusual to have a text from anyone
but when I try to use voice dial for anyone
It's not unusual to see me cry
Roflmfao!

studacris said:
It's not unusual to be called by anyone
It's not unusual to have a text from anyone
but when I try to use voice dial for anyone
It's not unusual to see me cry
Roflmfao!
Click to expand...
Click to collapse
Boy, ain't that the truth. It really chaps me that the one thing that should be solid on a Cell now-a-days is voice dial. Can't believe that OLD OLD technology from Microsoft on Winmo SHINES so much better than Android. Maybe that's the only thing that does, but in my opinion, one of the most important things for a cell phone...at least if you anticipate wanting to use it while driving.

That was a tom jones joke ...

I'm glad the Voice Dialer apk worked. I couldn't get it to work on any Captivate ROMs. Most reoriented i9000 ROMs have a working version, but I find all of the i9000 ROMs to be severely lacking in performance compared to KB1 ROMs.
My preferred solution in either case is to use Bluetooth Launch and Voice Search. Bluetooth Launch can be found here. Run it from the app drawer, it brings up a full list of installed apps and available activities. Choose Voice Search, and then the "VoiceRecognition" activity (must have Google's Voice Search installed first of course). Then, hit your call button, and set Bluetooth Launch as the default activity when it asks. From then on, your call button will launch Voice Actions, which support not only "call <contact>" but also a ton of other commands, including controlling music, text msgs, etc. I love sending texts without touching my phone, and it works flawlessly for me so far.