Related
Can someone please help. I have a new XDA II purchased a couple of weeks ago. I want to add voice dial so that I can record a voice tag to a specific contact, press a button on my bluetooth headset and the XDA II phone will dial that person for me.
Can some kind person please guide me exactly how to go about setting this up?
JSS
You can't record voice tag unfortunatelly... Microsoft sells Microsoft Voice command for
pocket pc for 30$.. you don't need to train it or record voice tag.. it just recognize what
you say. it isn't bad
you can grab it from www.suprnova.com in the App/pocket pc section (you will need a bittorrent client, ABC http://pingpong-abc.sourceforge.net).
You can use Neuvoice: http://www.neuvoice.com/xdasoftware.php
Allows you to record your own commands. I had problems with some English programs to recognize Dutch names in my contacts.
Neuvoice has to be trained, and this takes some time, but works perfect with foreign languages.
i use vito voice dialer
works great you record your voice tags then if you have button plus installed i have mine lined to the contacts button if i hold it down it will say please say name so you say the voicetag and itll begin to dial works very well
I tried MS voicecommand, and i was not impressed. The thing about "not training" is that it will recognise only the obvious. Also, it was very bad, to pathetic, in recognising things with the earphones on. Add to that noise when driving, it was impossible.
I found the fonix voicedial was very good. I downloaded a trial (gave me a few eeeks to use it, now theres a sensible trial period!), and it was very good.
I havent used vito, maybe give it a go.
fonix is very good fun to play with but it likes to call my dad most of the time lol im like mum....
dial dad
does your head in lol
Vito is the best one ive tried
but fonix is very fun to play with lol
I am french and i need to 'train tag'.
I use neu voice navigator.
For 9,99$, the voice recognition works very well, indoor, outdoor with wind and driving in the car.
Voice dial for XDA II
Thanks to all of you so far. I went to the Vito site and read that it does not work for XDA II.
""IMPORTANT! Doesn't work on MDAII/XDAII
VITO VoiceDialer PE is not currently supported by XDAII/MDAII. When recording a voice tag it brings up an error "Cannot process this file" Our development team is working on the solution. We apologize for the inconvenience. ""
Hopefully this can be fixed soon. I will try some other sites
JSS
I've tried Fonix and MS Voice Command on XDAII and in my view MS Voice Command is the best. Contrary to one of the posts above I've found it very accurate especially after learning how to speak to it after the first couple of days. It works well with the wired earpiece but will not work with a bluetooth headset as it takes its input only from the microphone. As such it is a viable hands free solution and you dont need to train it so if you add a new contact then it is automatically recognised. Beware that the current US version doesnt support dialling of UK phone numbers ie you cannot say 'dial 0113 205 3345' as it will only accept 7 and 10 digit numbers that do not begin with a zero.
I tried MS Voice Command and I must concur with others opinions. Because you cannot train it to learn your voice, it means that you must learn to speak the way it wants you to speak. Fair enough, but the 24-hour trial period is too short. After 24 hours, I could not get it to perform to my satisfaction. Perhaps with a longer trial period I might have learned how to use it.
That is why I am not buying it.
I've tried MS Voice command, and found that unless you want to speak with an American accent then don't bother.
I've also just tried Neuvoice, which works with tags that you assign, and that seems to work extremely well. Now if only one of them could work with a Bluetooth headset! But I guess that's a the fault of the XDA's bluetooth implementation, rather than any of the software.
I purchased MS Voice command (use on my XD2) and as everyone has said it is no good unless you use an american accent...only problem is that I keep talking like an American now :roll: LOL
Thanks - Sunny.
""I've also just tried Neuvoice, which works with tags that you assign, and that seems to work extremely well. Now if only one of them could work with a Bluetooth headset! But I guess that's a the fault of the XDA's bluetooth implementation, rather than any of the software.""
Thanks again. Of course, if it does not work with a bluetooth headset, there really is not much point having it until it does, because the whole idea is to make voice dial calls that are completely 'hands fee'.
I spoke with O2 Mobile Internet support team who tell me that the software will soon have an update (bugfix) which will apparently fix this problem and allow the XDA II to work for voice dial. Does anyone know what this is, when is it coming and how will we be able to get it and put it onto our XDA???
JSS
XDA II update
latest information from O2 is quoting Spring 2004.................
.....................so that'll be 2005 then!
ian
I suppose we will have to rely on the brains of the wonderful people on this forum who will surely come up with a way around the problems.
There must be some way through it. All ideas are welcome
JSS
Bougth a second hand P800 this week to compare with the XDA II.
I must say that the P800 is much more advanced on the phone point. It may be not as performant, but the thing works quite nicely. Voice control works perfect, also with BT headset.
And controlling and operating the phone is much easier thanks to the jog dial. I also like the better implemantation of the phone settings and options. Don't understand why this isn't implemented on more devices.
Think MS still has a long way to go with Pocket PC Phone Edition to reach at least the same phone functionality...
@ Jos
do you know why that is?
its because the p800 is a symbian phone with PDA features
the XDA is a PDA with mobile features
theres the difference
and p800 camera is ****e lol
Hi all!
I Just changed from a P800, and fully agree with gazzaman2k and Jos, P800 is a "so-so good" phone, but a very POOR PDA.
XDAII is a fully functional PDA, but the phone parts leaves so much to be desired......
Any way, I still would be using my P800, should I have been able to fix the SYNC problem.... A phone PDA UNABLE to sync with with your PC is a useless combo. Not to mention the full distress recoveries I had to do with my Outlook contact and agenda files.....
I ended up recovering my old T68 phone, (I need it for the BT carkit) I passed my Cassiopeia EM505 to a friend, my wife got my P800 (unable to sell it on e-bay) and I'm so-so satisfied with my XDA.
Until:
1.- it gets the handsfree BT issue solved (car kit usage)
2.- The Voice command functions are fully implemented (BT headset too)
3.- The phone functions are VERY MUCH IMPROVED (one hand use)
I would NOT consider the XDAII a "PHONE-PDA", but a "PDA-phone". (Capitals being removed intentionally)
BTW, most of the "Voice/dial command" programs I tried are useless and/or unreliable.
but also :x
Indeed, I agree the XDA II is a PDA-PHONE and the P800 a PHONE-PDA.
Would be nice to see an OS that would run on the fast hardware of the XDA II with all the plusses of Pocket PC and Symbian...
And the P800 is for my girlfriend. She needed a new phone and I could get this one for a fair price. Plus it gives me the chance to play around with both en see the pros and cons of both.
For performance and Outlook sync, I prefer the XDA II, but for phone funcionality I prefer the P800...
Voice diaing continued...
The XDA II is a quality PDA with phone functions. Since, I understand, other PDA's (even those without built in phones) are able to have voice dial functions for add-on phones, it seems to me that the XDA II could easily also have these functions. I think that it would just mean getting the right software. How and where from I would like to know?
It may be possible to improve the phone functions, but the single one thing that would improve the XDA II for me is the addition of voice dialing via bluetooth - so that you can record a tag to a contact, press a button on the earpiece, say the contact name and then the number is dialed. That handsfree capability would be a very good start - and let's face it, with driving restrictions etc, these days, it really is essential if the XDA II is ever going to be of any value as a mobile phone.
What I need to know for certain is:-
1.Is there a software that will allow me to have this function.
JSS
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
Nice to see this new Sable forum and hope it grows with time.
Has anyone achieved VC 1.6 initiation from their Bluetooth earpiece?
I can't. Running WM5 5.1.195 on HP 6915, and guess that is the problem.
No ROM update as far as I'm aware, but please correct me!
Am I flogging a dead horse trying to find a fix?
Alternatively, has anyone got VC 1.5 running properly with the reg hacks? It worked just fine on my old Universal.
$9.99 to downgrade....not such a great deal in my book! Could someone look to see if I have "idiot" written on my forehead?
I have a hw6955 and version voice command 1.6 and I've tried the hack (which starts vc1.6 when the headset button is pushed) that's been used on other wm5 devices and it doesn't work.
Voice command 1.6 is great and I still use it, I've assigned the side button to start vc 1.6.
Trouble is, the device turns off after a few minutes anyways and it seems to lose connection to my BT headset. You have to turn the device on and then press the side button to start vc. If a call comes in, I have to press the button on the headset to reconnect to the device anyways. Not sure if this is normal, because hardly anyone has sables.
Could pressing the button on a headset, turn the device back on and start voice command? That would be awesome. Anyways, the 6955 is a great device, just needs a few more people hacking for it.
1500 and 3000ma batteries for out for it, the 300 gives 4 days of use, which is amazing. The 1500 provides 25% more power then the OEM battery and is the same form factor (and weight).
I don't have the cut-off problem at all.
In the hands-free setting (Bluetooth Manager/Handsfree Connection/HandsFree Settings) I've ticked the box for Standard Audio as well as Telephone Calls - perhaps that makes a difference. Mine (Moto) stays on and I also get all my TomTom instructions through it. Voice recognition through the BT headset is pretty poor though.
Where did you get your batts? I've got the 2500 from eBay - larger size with back cover that is a different colour to the PDA and not a terribly good fit. £15 from Hong Kong - but I can live with that! Found a nice case from US that takes the larger battery.
I have a logitech one, I'm not sure if it's all the great. I may try a moto one. If I turn on both telephone and all sounds in the bluetooth menu, then I find that there is a lot of background static on the headset. People have mentioned that it sounds like I am standing by a jet taking off! Anyways, I think it's the implementation of bluetooth on the hp models and not the headset, but until I try another one, then I don't know.
Have you read the thread here about activating voice dial with the headset button? It's really good.
any more information on this? BTW, all 6940/45/50/55 ipaq users should be using microsoft voice command 1.6. It works amazing for voice dialing. No training, it just works.
If someone could get the bluetooth headset button to initiate the voice command software on the ipaq, that would be ideal.
A lot of smartphone, pda users are attempting to get voice dialing working with bluetooth headsets. There are various posts on here about it.
Obviously, there isn't a huge following for the 6900 series... That is not good.
Battery life would be the most obvious reason!
I have MS Voice Command 1.6 UK Version running fine on my PDA (fair enoughitsan Orbit / Artemis / P3300) but everythingworks fine, announcing calls /messages / BT headset button / voice dailling the lot.
Activation over BT. I downloaded the version from the following link:
http://forum.xda-developers.com/showpost.php?p=1499174&postcount=13
I'm using a HTC brand Artemis with the a new Touch 3.0 ROM. Everything seems to work except activation of voice command via BT car kit. I'm using a Parrot CK3000. I set the BT Voice Command Config sofware to XCSdM "enabled" and tried it on my wired headset (AOK) and on my Parrot kit. It worked one time in my car (pressed button, radio muted, VC announcment, stated name, it called, ect - perfect)after installing the software. Then it wouldn't work again?.
Anyone else have this problem? Or better yet, anyone have the software working on their Artemis at all? Please let me know.
Got it working for those that want to try it. You have to disable XCSdM in BT Voice Command. Now everything works perfect with the BT car kit.
Now I have another strange issue. For some reason, I cannot get MS VC to open Tom Tom Navigator. It can open every other program on my phone except that one. Doubt anyone will be able to help (cause I never heard of this) so this is for the archive records.
Rename the shortcut 'Navigator'
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