Database Users

Widcomm Phone Edition stack working - get it here!!!

Hi Guys: I have got the Widcomm Phone edition stack working on my unit.
It seems to be fine but I have not fully tested all aspects of the software - so if any little bits don't work, let me know...
You need to install the official widcomm 1-4-1-59 version
Then you can upgrade it using the cab file I have made.
The 1.4.1.59 version file I got from the following topic
http://forum.xda-developers.com/viewtopic.php?p=57550#57550
thanks go to mamaich for the file.
the upgrade file consistes of the PE edition files and the required registry entries.
Let me know how you all go on with it - but I am not really a hacker so any serious probs I will not be able to fix...
if anyone else can improve on the installation be my guest

any news about which profiles it support that ms or the old one dont support ?

I hope unintall won't mess up my volume as in case of original bluetoothgps.cab

I can't garauntee it works perfectly, so I suggest everyone make a backup of their system before use.

has anyone tested any BT headset with this new stack?

I've got it installed and it all seems to work well exept for the handsfree/headset profile, I have set up my headset ok it is discovered and bonds fine but when I try to connect from the xda2 the connection fails after "waiting for device" for some time. tried with a motorola hs 810 and a neovoice usb, same with both. Anyone got any ideas?

BT headset
I have a 6315 and an XDA 2, I haven't tried the BT Stack on the XDA 2 yet but I found when I bondeded my HBH-30 to my 6315 once it made the connection my BT Headset shut off for some reson. This caused the bonding to fail, but as soon as I turned my headset back on (while it was trying to discover services) it completed the process and worked on my 6315. I'm not sure if this will be the same, but it's worth a shot.
Brandon

Test results
Hi fellows
Here is little bit of my testing of this new BT Stack, which we all awaiting for..
Proc…
1. Installed as per instructions 1.59 without any problem. During installation was prom to override .dll files – agreed to do that. For good or for bad – will see later.
2. Installed .cab file provided by icarusbop (big thanks to him for doing this) without any problem. Screen shots will be attached below.
3. Reset it as requested upon installation and got Widcomm BT working instead of MS BT..
4. Paired it with my BlueTrek G2 within 3 seconds (which took usually 10 sec with MS BT)
5. BT recognized G2 as device with Headset/Hands-Free profiles and asked to use as default… I said yes…
Here comes Cons part ;(
1. Unfortunately even after paring – my I-Mate can not get connected with G2 (see screen shot)
2. As you can see in another screen shot – there is Hands Free menu – it can not be accessed, or can be accessed ONLY while connection is established.
3. AND the last L … So, this new BT is not working now… I decided to go back to MS BT… SURPISE!!! I am getting message that BT HARDWARE IS NOT INSTALL ON THIS UNIT…. L Assumption - .dll files were overwritten (see Proc 1)
Here is my 2 cents in this jorney… I am hoping that described problems can be fixed and we can make it working (without doing hard reset on my device )
Paul

thanks guys! for testing hands-free/headset profile. by now everything seems to work fine with this new stack except for hands-free/headset profile.

New comments to my testing
1. I tried what NeoCole recommended - didn't work for me
2. As soon as new BT is OFF - MS BT is working fine .....uf
LETS FIX THE HEADSET PART PLEASE

I posted this is another thread - but in case someone does not read that thread . . . it is relevant here as well.
If the intent of this is to get voice dialing without touching the device, that is by only pressing a button on the headset to initiate a voice-dial program to make the call, there is no evidence this works with this BT stack either.
I have been reading other forums with people who have the H6315 already (mine is in the mail to me now) and none of them have been able to make this work. Nor is there any mention of this capability in any of the literature and/or documentation for this device. It seems that if this was a feature of this phone, it would be prominently displayed!

Voice Command
Okay.. on my 6315 I press the headset button, it beeps, sound and voice is now transfered to the headset. I do this before I initate voice command. Now all I do is press a button that activates Voice Command on the PPC and walla, I'm speaking and listening through my BT Headset. This is a huge step forward from using the MS Stack, and I feel that since the Phone Edition of the Widcomm is 1.0.0 I'm sure that they'll associate a hardware button with the headset button in future releases. Anyhow.. I think that the functionality of the Widcomm BT Stack is well worth the work. The XDA 2 would be a lot better device if the BT Stack worked 100% of the time and was fully compatibile.

I also have not got it working.
the Hp 6315 is well know to still require a hardware button press (not on the headset) to activate voice command. They can still not do with any nokia or SE phone can do easily.
Surur

VoiceCommand
That would be correct... One press of the HW Button does it all on a Regular phone.
The 6315 has brought it closer to allow you to interact with programs using your BT Headset, but yes you must still activate the programs on your handset before you can use them with your headset.
So.. to sum it up...
1. You can't interact with Voice Command using MS BT Stack on an XDA 2
2. You can interact with Voice Command using Widcomm Stack on 6315, but you have to activate the headset first, then start VoiceCommand on the PPC by using the HW Button.
Hopefully through this thread we'll be able to give the XDA 2 the same functionality as the 6315.
And maybe if Widcomm provides an update to allow the headset to activate a HW button, we'll be to the one step solution.

I do not want my comments to be read as stating that this is not a worthwile endeavor. I simply meant to make sure that someone does not go to the trouble of installing this new stack (particularly those who might be considered novices) with the mistaken impression that by doing so they will have that "one step" voice dialing solution.
This is by all means a worthwile endeavor, but it is merely a step down the road . . . not the final destination.
Y'all are doing good work - keep on blazing that trail!

hm.. I would think that it is more of MS Voice Dial functionality than BT - to recognize signal sent from headset as request for voice dialing.
When MS released first version of Voice Dialing they did not expect new functionality to have BT headset with hands-free profile connected to the device.

paired with my Jabra 250 = ok
connected to my Jabra 250 = failed

No luck with Moto headset
Eveything else seem to be working. No problems with detecting and working with BT access point

rehman said:
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
Click to expand...
Click to collapse
Hi Rehman,
i tried to install and uninstall, for the very first time i didn't have to get a Hard-Reset done. the volume didn't disappear. so i believe trying it wont be a harm, but yet i would recommend to get a full Backup first.

Trying to figure this out
Okay, I looked through the whole registry. I can't find anything out of the ordinary. Only thing I can think of is the sound driver. Does anyone know what DLL that is? I bet it's a different version.
If someone that knows more about which DLL does what. Let's get all the DLL's that could pertain to Sound and Phone and compair the 6315 DLL's with the ones on the XDA2.

Voice Dialing --> Anyone else had any joy?

Hi
Anyone found any software that offers reliable voice dialing? The MDA Pro comes with somet called "Voice Speed Dial" Its sh1te!
Has a habit of trashing the voice tags of its own accord, and often does not respond when I press button on bluetooth headset.
When the device is closed and off and you press the button on headset nothing happens (PPC is starting up etc) several presses are usually required before you can actually call the contact.
I just tried a trial version of microsoft voice command 1.5 (this I believe is what imate is shipping) unfortunately it cannot understand a word I say!! (could be the devonian accent).
I said 'call work' it said 'calling 999' I managed to hit it with a brick before it actually did call 999 !!!
Anyone suggest something that actually works (flawlessly). I dont mind training it if that means its gonna work!
Nigel

"microsoft voice command" all the way.
Thing is that it doesn't support dutch, but it does support english, german and american, so if you speak any of these languages you will have to get this program.
Dunno about the trial version, but the full version requires you to pronounce right. You can test this by letting someone call you first so you can hear how the program expects you how to pronounce it. (I have dutch names and they are completely different when pronounced by the voice command)
Hope this helps.

I've flashed my MDA Pro with the I-Mate JASJAR rom, and the standard voice dial on that works like a charm!
It even work from my Jabra BT800!

Grrrrr
I'm a native English speaker and it dont ruddy understand me!!
Sounds like many people here have gone for the JasJar rom on their devices. I guess I will give this a go - I just dont want to end up with a useless brick.
Nigel

MS Voice Command - works for me on my jas jar via my moto BT headset even in the car when driving (i.e. with plenty background noise).
If you follow the tips on the MS VC website it makes it even more reliable.

The HTC voicedial program works great for me, and complies with my HS810 headset without any issues whatsoever. In fact it's even recognised my commands with music running in the background. I've tried MSVC in the past on other XDA's and found it to be rather cumbersome.
Ant

I found that Microsoft Voice command when started via bluetooth headset does not turn the link off when it's finished.
The way i got this to work with BT was to replace the file sddialer.exe in the windows folder with the voicecmd.exe file from MS VC.
Does anyone else know a better way of doing this to allow for the BT headset to be turned off automatically once listening is finished ?

Voicedial works, I just find it really slow. It is 100% reliable on the recognition front though.
What I noticed with voice command was an instant response. Press the button and speak, no wait of any kind for the 'beep'.
Voice command simply sticks an icon on the task bar, it does not have to load some monster gui before you can speak. Ditching the gui would be a step forward for the built in voicedial.
Nigel

steverae said:
I found that Microsoft Voice command when started via bluetooth headset does not turn the link off when it's finished
Click to expand...
Click to collapse
Hi
How did you get voice command to respond to the bluetooth headset in the first place?
With VC installed, the button on my BT headset is still starting the old HTC voicedial software.
Is there some registry setting somewhere to tell it what to launch?
Nigel

Yes there is a simple registry hack, it's posted else where in these forums but here it is again
Install Voice Command to the default location.
Fire up a registry editor
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Modify the string marked "path" from the default \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
This works for me and everyone else who has tried it AFAIK

Hi
How did you get voice command to respond to the bluetooth headset in the first place?
With VC installed, the button on my BT headset is still starting the old HTC voicedial software.
Is there some registry setting somewhere to tell it what to launch?
Nigel
Click to expand...
Click to collapse
I simply replace the file sddialer.exe with the voicecmd.exe and renamed the voicecmd.exe to sddialer.exe. After a softreset that's it.
Still can't fathom out a way to close the BT link though without doing it manunally from the headset.
Also does anyone have Fonix Voice Central installed on their Universal, i always get an error saying unsigned program or summit like that when i try to install the trial.

voicedial
I am italian mother tongue. Cyberon voicedial works incredibly well. I tried vito's program in the past. Average it could recognize 10%.
The cyb's software is awsome. I use it with a Jabra BT800 headset and recognize voice even in noisy environment.
Must tell that I am very satisfied with my JJ. Absolutely no problems in any way.

Installing unsigned apps on WM5
Trying to install Fonix Voice Central 3.0 Trial on my new Universal but keep getting an error stating unable to install as it is from a untrusted source or is an unsigned program.
Please help

Hi
OK, so its more reliable when using the bluetooth headset - it even understands devonian! BUT and this is a big but... why the heck does it not work when the device is closed (screen inside) and switched off??
Nuts... I get the beep from voice command after pressing button on the headset, but it ignores what I say. Performing the same thing with the screen open laptop or pda style (with device switched off) works fine, but not with the ruddy screen closed.
Anyone else experienced this?? Screen closed it how my device stays most of the time.
I see what people have been saying about it leaving the bluetooth channel open after as well - mad!
Nigel

Voice command does not respond when unit closed
Hi
Voice command not responding when unit closed (screen inside), and using button on BT headset.
Has no-one else found this, and if it works for them can they post rom versions. Certainly does not work on MDA Pro shipped rom!
When unit open, or screen folded outside PDA style, VC does respond to BT headset fine. Just not when its closed.
Nigel

I have imate JJ italian rom.
Works perfectly with Jabra BT800 and device switched off (screen closed down).
No problem at all!

Thanks - looks like a bug in the ancient MDA Pro software.
I was holding off flashing it with imate roms case I heard a rumour that t-mobile are about to release a new rom soon which may be newer again I suppose.
Nigel

Well, I put the imate rom on there and that did not solve it. Voice command does not work from bluetooth headset when unit closed. It gives me the beep prompt to say its listening, but it never responds. Open screen and all is well.
Save me some money anyway, no point in buying Voice Command if it does not work properly!
Nigel

veletron said:
Voicedial works, I just find it really slow. It is 100% reliable on the recognition front though.
What I noticed with voice command was an instant response. Press the button and speak, no wait of any kind for the 'beep'.
Voice command simply sticks an icon on the task bar, it does not have to load some monster gui before you can speak. Ditching the gui would be a step forward for the built in voicedial.
Nigel
Click to expand...
Click to collapse
Ive just been using the bog standard voice recognition. No problems at all, even works with background noise.
Im guessing that some people havent read instructions properly

The HTC software that comes with the device does work (reliably) its just too slow to be of any use.
10 secs to respond when unit is off/closed. If I dont get a prompt response i'll press the button on the headset again which seems to confuse the hell out of it.
This is my reason for trying voice command... Response time from voice command (from unit off) is 2 secs max. Unfortunately it does not ruddy well work when lid is closed (no matter whether unit is on/off).
Nigel

MS Voice Command works only once with BT

Hallo...
I have serious problem and till now I don't know how to fix it. I change the registry to allow the Bluetooth Headset to activate the MS Voice Command, when I click the button on the BT the Voice Command starts fine, but if I want to use it agin, the VC doesn't work anymore, I hear only a "peep" but the programm doesn't respond. I have Qtek 9100 with the last official ROM .
Any idea or solution to fix that ?
I appreciate any comment.

Thomas voicecommand and bluetooth has some issues. Basically, when you use VC the first time it opens the channel with the device, once you have then used it you need to hold the button down on your bluetooth device to close the channel. Then pressing BT again should open voicecommand. There's a number of posst for this problem but hopefully I've given you the basic issue

Thanks for your reply... But no, closing the Voice Channel doesn't solve the problem.. I have tried all that before I post my question, it really works only once and no more, only after restarting my device it will work again for once.
I am starting losing a hope that it can be fixed.

Thomas1234: I started trying to come up with solutions to this a while back but never had time to work on it further yet. Anyways what I came up with so far can be found here. It's not perfect but may work with your headset and make it useable for the most part.
http://forum.xda-developers.com/viewtopic.php?t=49255&highlight=
Note: Scroll down to the bottom of the above thread to get the latest version and you have to be logged in to see the file.

Hi shoey5!
Thanks for trying to help me, but it doesn't work, and it looks like that this file damaged the connection between BT headset and the Voice Command or any Voice calling, even the one by default ( voice calling ) doesn' work anymore now.
I was able before at least to do the voice calling, but now it doesnt work after I changed the registry to default to read from the sddialer.exe file.
Can you please explain me what did the file change so I can change it back if i is possible ?
I did softreset alot, but doesn't help.

Thomas1234: It doesn't modify or change anything, all it does is run resident and resets the Audio Gateway Service after a call has ended if there is a bluetooth device active. Removing it from your startup folder and resetting your device will get rid of it completely.
Are you sure you haven't modifed something else before or after that may have affected your problem. I know this sounds silly but is your volume up, can't tell you how many times I sit there pushing the button and wondering why I don't get anything only to realize my volume is off
BTW, Try this. Leave the program in your startup folder, power off your headset and reset your device, then power on your headset and see if it works from that point on. I've noticed this happens to me with headsets that exhibit this problem the odd time.

Thank you anyway..
I ended up to do a hard reset, because softreset didn't help... It has been worse, I even couldn't dial a number using the BT headset, well I won't say it is 100% because of your file, but I am sure I didn't do anything with the device that can cuse this problems before I applied you file, all this happened just after I installd your file.
I'll use the default Voice dialer then with my BT Headset till maybe Microsoft update its program.

this "ms voice command running only once" happened to me too, with Nokia HS-12W headset.. try using JETware Hands-free Extension for Windows Mobile phones, http://www.jetwaremobile.com/ , and activate ms voice command from its advanced settings.. it worked for me. unfortunately it's not free and it doesn't supply caller names to my hs. hope this helps..

Thanks ozkaya, the program looks useful. I'll try it and see if it does the job correctly.

PDAVIET Wing ROM and Bluetooth Headset...

Sorry for the cross-post...but I originally posted this in the general Herald forum...but since it involves an upgrade per say...thought I'd throw it in here too.
Fairly new here...got my Wing about a week ago.
I installed the PDAVIET Wing ROM with no issues (thx to everyone here on that long thread to get it going).
I have the Wing paired up with my car...no probs as the car has it's own voice recognition and simply dials the phone, etc.
My problem is this....
I have a Motorola H700 earbud. It paired no problem. Using the Wing directly, I have the right side button trigger the voice activated dialing. I than just speak and it dials whatever number I have associated. All good.
When I have my earbud on...and I press the talk button...it brings up the dial pad on the phone...NO voice recognition. I can manually press the button on the Wing...speak my number and it will dial....however that defeats the purpose of true hands-free.
When I press the call button on by earbud...how can I get the phone to jump into the voice recognition dialing instead of the regular manual keypad? I would love to be able to press the talk on my earbud...than the phone jumps to the talk mode...and I speak my saved voice dial. Otherwise, the bud is deemed useless b/c I don't want to have to touch my phone.
I hope that is all clear and that someone can help me out.
Thx in advance for any help.
PS. I went to the Bluetooth options for my H700 earbud...and the only option is what communications the earbud supports...which is only "hands-free". I was expecting a more thorough layout of earbud key mapping, etc. I thought I could trigger the voice recognition dial when I hit the talk button on the bud. None such luck.
HELP.
Cheers...B.

help...bump

I just upgraded to this and I am having the same problem with my H700.
Did anybody find a fix for this?

Ok so I was having the same issues. My bluethooth was not being initiated by the button on the earbud. This was from another thread, I did it and it works fine now. Hope it helps........
Originally Posted by nextpimp
My Contribution....Since people dont want to find it out their own.... Voice Speed dial Over Bluetooth ...
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
Itje ... Awesome Rom... All I gotta do now is unmap Voice Command from the hold funtion on button five.... Its not listening to me in the settings so gotta go to the reg... Help would be appreciated as the registry really isnt my strong point.

Getting MS Voice Command to work

I have had the Sprint Touch for 2 weeks now and really miss MS Voice Command.
Anyone have it working and what are the steps ?
Scott

anywhereanytime said:
I have had the Sprint Touch for 2 weeks now and really miss MS Voice Command.
Anyone have it working and what are the steps ?
Scott
Click to expand...
Click to collapse
Just install it. MS Voice Command 1.6 works just fine

no problem with call anouncement,or voice confirmation over BT?

imradar said:
no problem with call anouncement,or voice confirmation over BT?
Click to expand...
Click to collapse
No prob with my Motorola HT820 and my S9. Call anounce works just fine and even reads my text messages

Thanks for the replies ... I just bought a Blue Ant Z9 and will report once I install it.

I really miss MS Voice Command also, there are three major issues.
1. Any speech or announcements from Voice Command via BT (Bluetooth) have very low volume.
2. Bluetooth dialing confirmation when confirming a number to call is not recognized most if not all of the time.
3. After pressing the button to start voice command, many times you will not hear the beep over the phones internal speaker or over bluetooth. It seams that the phone delays opening up the sound channel a second or so, and the beep is never heard.
I would love to see workaround or fixes to these.
Only #2 has a work around by disabling confirmations.

Blue Ant Z9
Today I played with my new Blue Ant Z9 headset - GREAT headset.
Using the Z9, VC understands the initial command whether it's dialing, help, start, etc. But, when VC repeats the command, VC times out.
Where do you turn notifications OFF - I could only see under the VC menu where you could chose either Bluetooth or wired/device speaker ?
Anyone using a Z9 successfully - I have firmware v3.0
I contacted Z9 tech support and they will be monitoring this thread to see if they can help find a solution ... but it's probably VC itself.
Scott

Uninstall the Cyberon Voice Dialer
I recall reading on either the Titan/Mogul thread or the HTC Elf/Touch thread something about the bluetooth "voice command" path being directed to the Cyberon and that it must be changed somehow to allow VC to work properly?
I disabled the Cyberon Speed Dialer, but can't find how to remove it. Does anyone know how to remove the Cyberon "Dialer" software?
Scott

VC 1.6 WORKS - but NOT with Bluetooth
Today I played some more and VC 1.6 definitely works over the speaker and built-in mic - VERY COOL - BUT, NOT with bluetooth (we are using the Blue Ant Z9)
SAME PROBLEM reported across many threads - when VC 1.6 "confirms" the command, it then hangs up (turns off listening)
This seems to be a common problem across many HTC devices, so I searched quite a lot and found this under the Hermes thread.
http://wiki.xda-developers.com/index.php?pagename=Hermes_Utils
ANY EXPERTS OUT THERE to give this a try and report back ??
--------------------------------------------------------------------------
How to make Microsoft Voice Command 1.6 work (WM5 & WM6 tested!).
(caution, this MAY disable all incoming call notifications over the speaker and obviously doesn't route the notifications to the headset - that's a MS stack problem...)
NB The 'Program Files' directory mentioned several times below, may be different on non-english language versions of WM (see below).
Install VC 1.6 (make sure it is in Main memory)
Download Bluetooth Voice Command 0.9f.cab here - related forum thread
Download ?BTVoiceCommand.exe here - related forum thread
Download replacement btagext.dll here (Unknown if this works with WM6?) - related forum thread
Run .9f Hack
Create the Folder \Program Files\Bluetooth Voice Command (should be created during the .9f cab install)
Copy ?BTVoiceCommand.exe and btagext.dll into this folder
Go to newly created BT Voice Command config (in Programs) and tick the check box "Enabled"
Set command duration to 30 (or more - check by experiment when set up)
Set or check that the following registry keys are set (I had to manually change Path to ?BTVoiceCommand.exe.)
HKLM\SOFTWARE\OEM\?VoiceCommand\Path = "\Program Files\Bluetooth Voice Command\?BTVoiceCommand.exe"
HKLM\SOFTWARE\OEM\?VoiceCommand\?VoiceCmdDuration = 30
HKLM\SOFTWARE\Microsoft\Bluetooth\?AudioGateway\?BTAGExtModule = "\Program Files\Bluetooth Voice Command\btagext.dll"
a. (For reference: http://forum.xda-developers.com/showthread.php?t=283412&page=7 )
*Go into the registry (HKLM\SOFTWARE\OEM\?VoiceCommand\) and set ?LaunchAPEnable to 1 (I wasn't sure if this was necessary...but it's working now)
Soft reset device
Delete Headset Pairing
Recreate Headset Pairing.
*NOTE: first time you invoke voice command using BT headset button, you may get the "run this program yes/no?" option on your screen. You have to QUICKLY hit "yes" or your phone will have to be soft reset to exit the prompt.
Set Side button to ?VoiceCommand (if desired for backup when using Mortscript described below)
You may also need to create the directory \Program Files\Bluetooth Voice Command and move the files over if you live in a different country and MS installs everything to something similar - like Programme...
WM6 specific:
If using the .09f file downloaded from the link above, the registry key should look slightly different:
HKLM\SOFTWARE\OEM\?VoiceCommand\Path = "\Program Files\Bluetooth Voice Command\BTVCBasic.exe"
You may still encounter a problem where approx 15 s after initiating a call using MSVC from your headset button, the sound is routed back to the handset. A subsequent press on the button usually reroutes the sound to the headset, but sometimes disconnects the call instead. We are hoping for a fix for this.
--------------------------------------------------------------------------

Today I played some more and VC 1.6 definitely works over the speaker and built-in mic - VERY COOL - BUT, NOT with bluetooth (we are using the Blue Ant Z9)
SAME PROBLEM reported across many threads - when VC 1.6 "confirms" the command, it then hangs up (turns off listening)
This seems to be a common problem across many HTC devices, so I searched quite a lot and found this under the Hermes thread.
http://wiki.xda-developers.com/index.php?pagename=Hermes_Utils
ANY EXPERTS OUT THERE to give this a try and report back ??
---------------
Gave it a try tonight. The hack does still work, but doens't give us anything more than what we already have. While it will launch voice command, it still has a problem with confirmations. I am thinking that the BT stack on the touch is having a problem with this. It beeps, waits for input, then responds, then waits for input again. Somehow with this 2nd input something goes wrong. I have not had confirmations work once for me over bluetooth.

I am waiting on my Touch to get there and this is very important to me.
If confirmations are turned off, does it work properly?

fowen said:
I am waiting on my Touch to get there and this is very important to me.
If confirmations are turned off, does it work properly?
Click to expand...
Click to collapse
Please read message #6. Other than those issues it functions.

Anyone get VC 1.6 to work with a Blue Ant Z9 BT headset yet ??

I have the vogue and the Jawbone with VC 1.6 - sametime out problems as listed before, however, when you go to settings>VC>phone and turn confirmation off it works absolutely perfectly w/o a hitch. I hit the button, it plays through the headset - I name the perp - it announces the name and dials...no issues what so ever. I think this is an acceptable fix and if the name does not come through you can just hang up quickly and try again... I'd rather do this then hack it given there is no confirmation that it works.
So yes... VC 1.6 work through BT w/ confirmation set to off.

jessiethe3rd said:
I have the vogue and the Jawbone with VC 1.6 - sametime out problems as listed before, however, when you go to settings>VC>phone and turn confirmation off it works absolutely perfectly w/o a hitch. I hit the button, it plays through the headset - I name the perp - it announces the name and dials...no issues what so ever. I think this is an acceptable fix and if the name does not come through you can just hang up quickly and try again... I'd rather do this then hack it given there is no confirmation that it works.
So yes... VC 1.6 work through BT w/ confirmation set to off.
Click to expand...
Click to collapse
I tried it with my Blue Ant Z9 and it does not work without a hitch - the volume is very low and it does not seem to get the perp correct even most of the time. I will do some more experimenting and contact Blue Ant tech support.

I got my Blue Ant Z9 working ... there is a delay when you press the Multifunction button of several seconds and I had to watch the screen to see whan VC came on.
The dial and call "work" only the first time - if you say Call Jack and there are multiple numbers for Jack, VC asks Call Jack at Work or Mobile (say there are both). If you respond and say Call Mobile - VC hangs up just like before the turn off confirmation.
However, if you say Call Jack at Work, VC correctly calls the number.
Are you able to go multiple levels of recognition on the Jawbone ??
I'll take what I can get for now.
Oh, yes when someone calls me that is in my contacts I get NO notification or Caller iD - is that one of the things that still doesn't work ??

I recently saw this on the Titan thread - anyone know if the Sprint Touch and Sprint Mogul are the same ?
Anyone get the caller ID announce to work yet ??
http://forum.xda-developers.com/showthread.php?t=352638

Hi,
I still cannot get it to launch with my Jawbone BT headset...
I tried the instructions...
Anyone have anything to help me further?
LIP

Motorola H500 with MSVC1.6 is fully funtional even on confirm call, mobile/home etc