Database Users

How to switch on automatic telephone answering

In the setting of "telephone"is the opportunity to set the device to automatic answering after 1-15 rings. That would be ideal when you are having a BT headset, because you would not have to press on the headset button. However, this does not work. Is there a setting in the registry to make this work?

press the green phone button then go into tools>options
then click on the more tab and youll see Automatic pickup
if not on your wm2003 then get a registry editor and go to:
HKEY_CURRENT_USER>ControlPanel>AutoPickup
change the Auto Pickups value from 0 to 1
and Ring to what ever you want (mines set to 3)
hope this helps u
gaz

Thanks for your advice. I already performed the actions and in the registry it is all set. However, on my XDA II it does'nt work. I also tried to use the wired headset, because I know from my regular phone that there it only works when you have the headset attached, but nothing , nada.
Any other suggestion?

aint got a clue then mate sorry

As far as I know this option has never worked, its a OS bug.....
It didn't work on my XDA with 2002 and 2003, and it doesn't work on my MDA II with the latest MDA update. Maybe somebody has worked out this thing, in that case I would be very happy to hear about it because I agree, it's a shame we cannot use it.

It seems that an auto pickup is possible ONLY if the wired earphones are plugged in. So maybe it's possible to simulate such situation with some kind of software, or registry changes, but without swiching off the phone speaker and microphone?

Summary: Voicecommand via Bluetooth [STILL UNDONE]

After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.
Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!
WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.
PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.
PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)
This problem can be solved by changing a key in the registry:
Code:
HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)
Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.
PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)
There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/
I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)
PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.
PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?
PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?
And last but not least: Will you still be able to use your phone as a "phone" then?
Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto
Regards, Licht

Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.
Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.
Would LOVE to have a fix that would let me use with all headsets.
How does the jetware stuff work? I heard it screws up some other things?

Cause of "works only once" problem discovered?
I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:
All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.
I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").
Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.

Changed over to Tytn... works perfectly without any hacks

here's my FWIW answer:
After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)
Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.
Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.
Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.

BTAudioToogle for Hermes

Hi,
i can't use the BTAudioToogle Tool for my XDA trion.
Someone the same problem ?
or better:
Someone with a solution here ?

Same for me. I have enabled BTaudiotoggle, I can hear the headset (Motorola HS850) go live but the audio either from WM player or TCMP still comes from the speaker and not the headset.
Hope someone comes up with the answer soon.
Rob

Got the same problem. No sound from BT.

Had something similiar to this with my old unit, to fully enable it I would hit the headset button (which now starts up voice command, let it time out, and then play whatever music i wanted to. I would verify that now but i am at work, and don't think they would appreciate the music blaring if i am wrong on this one

When I hit the button on the headset, it starts the Voice Dialer, the audio cuts in for a second or two, then drops back to the device speaker.
It nearly works, hope someone can hack this soon, just whats needed for podcasts and the like. No good for music tho!
Rob

I would also be very interested in a solution to this problem as I used to use BTaudiotoggle to listen to Tomtom commands in the car (normally have the music too loud to hear the commands through the loudspeaker ).
Worked great with my XDA Mini S but doesn't work with my new MDA Vario II and I didn't really want to have to buy stereo headphones, just wanted to be able to use my standard mono bluetooth headset like before.
If there is no way of using this program, are there any other programs that will send all audio to a mono BT Headset?

yep would really like an updated version of BTaudio too so i can listen to some audio books via my mono headset

You should test the trial version of bluemusic from teksoftco.
www.teksoftco.com . It gives ou a full help file on how to use the software and you have 30 sec to test that it working. I know that it works on the devices having TI Omap processors so it should work for all of you guys.
Cheers,
Raul

Just tried it out. It does the same thing that the other sotware does, mainly enable the headset where you can hear a hiss out of it, but still kees playing out of the back speaker.

My experience is a rassah's. All the Bluemusic software appears to do on my Vario II is cause the bluetooth headset to hiss slightly (whilst sound is still blasted out of the phone's speaker).
Also FWIW the teksoftco site doesn't appear to work too well on the PIE browser - defaulting to a no frames version with just a login box as far as I can see.
Needless to say I have uninstalled the software again.
Rufus.

@RufusA and @rassah guys you should check if you don't have the same problem as ulischultz in this thread :
http://forum.xda-developers.com/viewtopic.php?t=61739
We already tested the software with him on his treo device and as you can see in the thread " after pressing the button on the headset, the sound was redirected". This is mentioned in the help section of the software. ( on the universal/exec for example this step is not needed)
@RufusA - thanks for visiting the ppc version of the webpage (which is still under construction) - even though the subject is irelevant in this topic. I will send you a PM when its finished and tell me your opinion then (even though you have to admit that not many companies have a ppc version of their website - not to mention the smaller ones like ours).
If the problem still persists there is an opened thread on the forum :
http://www.teksoftco.com/forum/viewtopic.php?t=162
Please submit all the malfunctionality and we will fix them.
Cheers,
rain

I downloaded the trial too and had the same problem as before unfortunately.
I did get a little further in so much as, if I pressed the call button on my BT Headset as per the instructions, I could get the music/audio transferred to the headset for approx. 5 seconds but then it would revert back to the phones loudspeaker. I couldn't get the 30 seconds that the trial software advertises
Fingers crossed someone will be able to work out a fix for this soon.

Thanks Nicky for the input. As i see the problem of bt headset being disconnected after 5-10 sec is a general one (and unfortunatelly is a problem in the RUU). We are trying to find a workarround with ulischultz but wouldn't want to get to driver level as clearly it will be fixed by HTC in the next RUU release if they don't want this devices smashed to their heads.
I will keep you updated if we find a solution for the interrupt issue.
Regards,
Raul

Solution
I have identified a solution to this which is working nearly perfectly for me. However, if you do use this then using the BT headset to trigger the voice dial/voice command/voice commander will no longer work.
Acquire a copy of of the BTAudioToggle software inc. BTAudioOn.exe
Copy this to a location on the phone.
Using a registry editor amend the following entries from
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Path = location of BTAudioOn.Exe
e.g. Path = \Program Files\BTAudio\BTAudioOn.Exe
VoiceCmdDuration = 86400 (DEC) = 24 hours
This says for how long (in seconds) the audio will be passed to the headset for before timing out.
This however, will timeout earlier if no audio is coming through. I am not sure what will happen if something like TomTom is running but not speaking for a while. I have not performed timings as yet.
To activate audio through headset, press the main control button of the headset as if answering call/activating voice command etc. To deactivate, just press the button again.
Voice control apps will still work, but must be triggered from the phone itself, but voice will be picked up by the BT headset.
There appear to be some small bugs with this, such as after a phone call, using headset or not, the audio will stop being passed after hangup.
Please let me know if this work for you!

Looks an interesting solution. I've installed BTAudioOn on my storage card, and changed the VoiceCommand Path entry.
However I couldn't find a VoiceCmdDuraion entry under
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
so I've added a new DWord of that name with the value 86400.
Yet this doesn't appear to have made a significant difference i.e. Pressing talk button on Jabra headset produces 10 secs of sound before "timing" out.
Have I made a mistake, or do I need to have something else installed to get this to work?
TIA - Rufus.

I was going to try and make the suggested changes to the registry but I don't know how and am not sure what program I need to do it.
Could someone please let me know what program I need to install to be able to change the registry?
Thanks

Vs1979:
IT REALLY WORKS!!!!!!!!!
I can't tell you how happy I am!!!!
I did it the way you described it. However I also did not have an entry "VoiceCmdDuration" I created the DWORD-entry and it works now!
Great!
Thanks very much for that great solution!

@RufusA
As i gave you the link to the other thread you're not the only user experiencing this. There are several others complaining about this RUU bug.
@Nicky
You need to install a ppc 2005 regeditor (for example Resco Explorer has one built in, or you can find one on buzzdev site).

RufusA said:
Looks an interesting solution. I've installed BTAudioOn on my storage card, and changed the VoiceCommand Path entry.
However I couldn't find a VoiceCmdDuraion entry under
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
so I've added a new DWord of that name with the value 86400.
Yet this doesn't appear to have made a significant difference i.e. Pressing talk button on Jabra headset produces 10 secs of sound before "timing" out.
Have I made a mistake, or do I need to have something else installed to get this to work?
TIA - Rufus.
Click to expand...
Click to collapse
Hi,
Did you Soft reset your device?
I made the registry change only, have not installed BTAudioOn and all my Voice command Audio etc... now comes through the headset and does not time out after a few seconds. I did find though that decreasing this value to lets say 60, would actually time the audio feed out even if not in use so I have stuck in a huge figure, will still need to do more testing to see if drains the battery any quicker and see if I can find another stirng which will do more for me.

Hi,
it work not for me
i have changed the path to \xx\BTAudioOn.EXE
i have add the VoiceDuration = 86400 (DWord DEC)
but it is the same problem, after 2 seconds the sound goes back to PPC.

Widcomm Bt Stack On Wizard - Howto

Hi!
In the last some days i read a lot and found the following :
1. download the widcomm stack from axim site : LINK
2. install it + do a soft reset
3. get a registry edittor (Resco, CECMD etc.)
4. change these values :
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BtConfig\SerialTransport]
BaudRate=115200 (Won't start at higher rate.)
Device=COM
FlowControl=0
Parity=0
Port=1 (This is the most important thing!)
-soft reset
-at the today screen you will find a BT icon, click on it and have fun
TESTED FEATURES
-BT FTP, tested with : SE K750i, hx4700.
-ActiveSync : NOT WORKING
KNOWN ISSUES
-unable to control from comm manager
-blue led not flashing, easy to forget
-a2dp not tested
-tested on aku3.2 and aku2.3 roms, others maybe ok.
-other devices can't download bt services list, but the services works well.
-maybe unable to remove, not tested yet
-turns off, when you trun off your device, that maybe a problem with BT headset.
DO IT ON YOUR OWN RISK

Great news! Posted an announcement to the SP & Pocket PC Mag Expert Blog too!

Problems!!!
I've just installed the bluetoth stack in my phone. I've not yet tested it but i've found two showstop problems:
- activesync doesn't work anymore
- i cannot start the comm manager anymore (when i press the comm manager button in the upper left corner i can see only a small dialog with wifi and bluetooth power levels)
This is what i've done (maybe i did something wrong):
- copied the cab to storage and ran it (installed in device)
- soft-reset (required by the installer)
- edited the registry according to the first post
- soft-reset
I'm using an aku3.2 rom
-----EDIT--------------
Comm manager is working again. I had to reassociate it in Start-Settings-Buttons
Still no activesync (over USB at least)
bye
bye

Has anyone else tried this then? Has anyone tried the hermes cab install found in here...
http://forum.xda-developers.com/showthread.php?p=1072292#post1072292
There has been reports that it works on the trinity as well, so it may work on the Wizard.
Edit: No it doesn't. I have just ried it and it gives the memory error.

took the plunge and tried it
Bluetooth works and I can connect my itech S35 to it. The A2DP profile is detected and can connect... problem is, the signal is too weak to maintain a connection, in other words, I just heard 2 seconds of music and that's it... Another problem is my speakers now don't work... must do more reading...
It's hopeful though...
I am using a Dopdo838...

new2city said:
Bluetooth works and I can connect my itech S35 to it. The A2DP profile is detected and can connect... problem is, the signal is too weak to maintain a connection, in other words, I just heard 2 seconds of music and that's it... Another problem is my speakers now don't work... must do more reading...
It's hopeful though...
I am using a Dopdo838...
Click to expand...
Click to collapse
Did you try tweaking the BT params (for example, lowering the bit speed) to see whether it would work at lower bit speeds? See my related articles.

got look out for the links to your tips and tricks again
Hi Menneisyys,
Surrendered on Widcomm stack almost 2 months ago, now have to look again for the links for your tips and tricks for the Widcomm stack again...
Any idea on how to restore audio to my speakers... still dead at the moment... sigh... don't want to restore my back up yet...

i found that you don't really need to remove the shift* keys. if you already removed it, download the BTSpeedSwitcher from the download link, and set the speed to 921600bps. that may help.

Got it working fine
Thanks, but now I am a bit unclear, but will clear things up later. I used the speedswitcher as you suggested and but I had to disable audiogateway before it could work... now I am stuck as I put my wizard into standby and now it won't come back.... on... doh!
Well, one thing I can confirm, you can put it into standby and the bluetooth is still on.......
will feed back more when I get a clearer picture of what happened.... The sound quality is great..... just skipped for a second but is not back to normal again...
My wizard has now a nice quality A2DP sound without the high pitch noise...
went to http://forum.xda-developers.com/showthread.php?p=1073003&posted=1#post1073003
and used the files from Superdave... all is well now... look at my reply at the hermes thread.. Now I will just back up this "working configuration" and retry these settings on the cab from Aximsite... All the same, thanks to the legendary Mikelspikel
Just wanted A2DP to work so bad.... and it does now. nicely..

new2city said:
Got it working
Click to expand...
Click to collapse
Okay, when you get time can you stick up how you got it all working? Many Thanks!
Ive installed the Superdave BBS_HERMES_03.CAB file and then modified the registry to use the above settings but every time i do the soft reset, the registry settings go back to the original values. Im stuck here.
Oh and i am using the last T-Mobile UK rom. (2.0 i think)
Edit 2: Now got it working. I had to kill voicecmd and cprog for it to load without giving the memory issue!

new2city said:
you can put it into standby and the bluetooth is still on.......
Click to expand...
Click to collapse
as it should - BT is on on PPC PE devices in standby mode, unlike on plain PPC's.

peetking said:
-unable to control from comm manager
Click to expand...
Click to collapse
It looks like comm manager is just an HTML document in the /windows directory. (Should be simple to redirect the button)

Leaskovski
sorry for the late reply but had a few setbacks during the night(I am in Malaysia)..
Got A2DP running all night and by mid morning... suddenly all went to hell..
1) No skipping with your suggestion of using MikelSpikel's speed switcher.
2) While trying to put it to standby to test if BT still works and it hung at first attempt. Something must have happened here as I recovered using the reset button and then suddenly I could get it to revert back to built in speakers and headset without issue. I thought, cool, it is like complete solution...
And then, I decided to backup this "complete solution" with SPB backup.. and after the softreset, I lost the ability to switch between headset and speakers. Then during the night while I sleep and use the headset, at around 3 am... the skipping came back...
and then... I restored the backup and now... got to tackle the skipping again.. never mind the muted speakers..
What linespeed(I use 320 dec), Blocks(16) and subband(8) do you use? I followed MikelSpikel's settings which work ok... last night...
back to the drawing board..

Right, i installed the superdave 03 version and then opened up the registry to make sure the settings matched the ones above. I had to kill cprog and voicecmd to start it without the memory error.
I have tested it now and although it is loading up ok, my headset connection is just not working properly. Its paired ok but nothing is getting routed through. However, my gps bluetooth device paired okay and is working fine with iGO 2006 after doing a detection. Damn shame about this headset! I am using a parrott ck3000.

redo..
Re-installed everything again and now I got a working version, some things to note though on my wizard..
1) I must overclock to 260mhz(battery status method) before I get skip free music.
2) Leaskovski, I had the same problem too in the beginning, where there is no audio getting through. Did you go to Bluetooth Manager and check the status of your headset? i went to mine(ItechS35) and I can see that the Wizard is sending data through successfully but there is no sound coming out of the headset. I solved this(that time, I don't know why it worked but it did) by going to Bluetooth services and removing the Check box for audio gateway enabled, and then music started coming through. I know, does not sound logical but it worked... that time..
Now hoping to find a way to redirect audio back to speakers when bluetooth is not used..
not tonight though.. its 10.46 pm now where I am...

This doesn't look promising for how i though the BT audio might work with this stack. I was hoping for something like the following...
"A good example of this is MS Voise command running on the MS BT stack. The two devices are paired and connected, however there is currently no streaming. You then receive the text message and MS Voice command reads the message back to you. Just before the message is read, the connection between the devices is made live, and thus the message gets read over the BT headset."
I was hoping that this was going to work for all applications like media player and iGO. I can reproduce what it is doing at the moment using the BTAudio programme that is available on these boards. I just wanted to get around this 'constant' streaming of silent noise.
Damn shame.

Okay for anyone wanting to play with this, here is how i installed and got it running...
1) Download from this thread post http://forum.xda-developers.com/showpost.php?p=1072773&postcount=72 the file BBS_HERMES_03.zip.
2) Install onto your wizard and soft reset when asked. Upon the reset, the device will moan at you about not having enought memory to load the drivers. Click ok to close this.
3) Load up your registry editor (i use FDCSoft Task Manager) and make the following mods as stated in the first post...
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BtConfig\SerialTransport]
BaudRate=115200 (Won't start at higher rate.)
Port=1 (This is the most important thing!)
If you only want audio routed to headset when there is audio to route then make this reg edit...
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\Plugins\handsfree]
Audiohandling=21
4) Do not do a soft reset yet.
5) Now fire up your Task Manager (i use FDCSoft Task Manager) and kill any memory hungry tasks. The ones i kill which then allow me to start the stack is voicecmd.exe and cprog.exe.
6) Now click on the BT icon in the system tray and turn BT on.
Obviously there must be some memory leaks some where in the wizard because a couple of people have said that later in the day, if you try to turn BT on again it wont start due to memory requirements. Anyway, the best thing i can think of is to leave BT on after you have turned it on.
Currently, the blue led will not flash when BT is one. Try not to use the Normal Comms Manager to turn BT one as well as i think this trys to turn the MS stack on which won't work (probably due to memory requirements! )

new2city said:
I solved this(that time, I don't know why it worked but it did) by going to Bluetooth services and removing the Check box for audio gateway enabled, and then music started coming through. I know, does not sound logical but it worked... that time..
Click to expand...
Click to collapse
I didnt get this to work in the end by the way.

I tried your idea to leave BT all the while but some problems pop up..
1) If turn off the headset without disconnecting it(BT still left on and the phone goes on standby, sometimes it won't come back.. a poke at the reset button is the only way..
2) I left BT on and disconnected the headset properly. Great BT is still on... BUT after a few hours, I can still connect the headset, but audio is not going there anymore... ??? but goes into internal speakers?

new2city said:
I tried your idea to leave BT all the while but some problems pop up..
1) If turn off the headset without disconnecting it(BT still left on and the phone goes on standby, sometimes it won't come back.. a poke at the reset button is the only way..
2) I left BT on and disconnected the headset properly. Great BT is still on... BUT after a few hours, I can still connect the headset, but audio is not going there anymore... ??? but goes into internal speakers?
Click to expand...
Click to collapse
Hmm, i dont have those issues. I am using it with my carkit, so when i turn the engine off and remove the keys, the kit turns off. I haven't had to reset the device apart from when i have turned BT off and then tried to turn it back on again at a later stage (then giving me the memory issue).

MSVC 1.6 notifications - help (Microsoft Voice Commander)

I used to use MSVC 1.6 on the Tytn2 on WM6.5 (see sig) and the confirmation notifications when you called someone always used the bluetooth headset. Since running it on the Leo MSVC seems to use the loudspeaker on the handset instead of the bluetooth headset even though every setting is marked as "Announce notifications using Bluetooth hands free only"
Anyone else having this issue as I did a search and couldn't find anyone.
Edit: Just had it working once but then the other end couldn't hear me when the call connected. Then I tried again and it had reverted back to not working.
I went to Bluetooth settings, Advanced, Audio and ticked the box then rebooted the phone...

I have this same problem! Its annoying... you want to make a call and the prompts/confirmation come from the phone... Please, can someone figure this out?

Bumping thread as it should be resolvable

Starfury said:
Bumping thread as it should be resolvable
Click to expand...
Click to collapse
IT isn't... I have done more research..
The Leo (and the TouchPro2) use a Widcomm BT stack as opposed to the usual MS stack. Sadly, this means the BT won't play nice with a lot of different apps/equipment. This isn't something that can be swapped out easily as NRG has pointed out. Touch Pro 2 users are still facing the same problems even though that phone was released much earlier. Some however have reported some success when using certain custom ROMS... how its working with some ROMS and not others is still a mystery it seems
I would watch the ROM Development thread carefully to see if a ROM what works with our MSVC shows up....

Hello,
Is there a workaround... ?
Thanks in advance for any info,
Jean-Jacques

I have the same problem. I'm using an old phone when I need to use hands-free. After spending a lot of money on my HD2, I'm not impressed.
I there a particular combination of headset and software that does work, especially for voice dialing?

have you tried this?
I would, but I don't know if I even have voice command on my phone.
http://forum.xda-developers.com/showthread.php?t=634494

DrATty said:
I there a particular combination of headset and software that does work, especially for voice dialing?
Click to expand...
Click to collapse
Does not work with my helmet bike with scala-rider Q2, but does with does with Philips SH9000 stereo headset...
Mono/Stereo seems to matter.
Any workaround would be veryyyy appreciated
Jean-Jacques

Workaround
Hi,
for this following workaround seems the only way to get it runnin:
My BT-Headset has the ability to be set as a Stereo-Device. When I establish a connection to this Stereo-Device, I can use it (my BT Headset) to give Commands and recieve "answers" from the VC. In case I want to start a phone-Call, my headset changes the connection automatically from "Stereo-Device" to "Handsfree-Device" and back, after finishing the Call.
This may be the Reason, why someone here already got it running with a BT-Stereo-Headset.?
Sorry for my bad english...