|
||||
Sorry i was a little tired when i posted....
Quote:
Hope that clarifies, it specifically addresses the WM6 issue we are dealing with.
__________________
Are you one of us?...Or...Are you one of them! Only you can decide... http://forum.ppcgeeks.com/showthread.php?p=96301
|
|
||||
I installed with it tethered, I hear my BT headset come on when a call comes in but it won't ring or say who it is and I have set the settings according to what people have said to do.
It doesn't work but I will try the patch cab file when I get home, thx. |
|
||||
I couldn't get it to work -- couldn't get caller ID announcement work over the phone speaker or BT headset. I have up and went back to WM5 3.5 until I hear this is fixed.
|
|
||||
i tweaked the patches a lil bti and all and got it working with no problems at all on my mogul heres the link.....
http://rapidshare.com/files/54690459...LL_WORKING.CAB |
|
||||
I am also running wm6 with mvc 1.6 and have installed the previously described patch. The patch seemed to have fixed my ability to initiate voice dial via bluetooth, however I still do not get voice caller ID through headset. I found the following on Microsoft's and wonder if the problem has something to do with wm6 possibly not having the "Inband Ringtone" as referenced...but that is just a guess?
***Also the above link is not working*** Bluetooth audio routing is working except for Caller ID If you have a Windows Mobile 5.0 device prior to build 15097.3.0.0, you will not be able to receive spoken caller ID notifications through the Bluetooth headset. Windows Mobile with build number the same or higher than build 15097.3.0.0 includes support for Inband ringtone which is the mechanism that Voice Command uses for announcing caller ID information while the phone is ringing. |
|
|
|