Database Users

Bluetooth car kit and voice dialling question

Does anyone here use their MS Mobile 2003 “smart” phone with a Bluetooth car kit?
I wonder if you can help me…
With my old Nokia phone, it used to activate the connection to the car kit when I turned on the engine.
However, on the MDA Compact, I have to go to Bluetooth, select the car kit, and select “Set as Hands-free” every time I get into the car, witch is rather annoying.
Does anyone know how to make this automatic? Is there a third party utility perhaps that would monitor the availability of the car kit every so often, and connect to it automatically when it is available?
And another question, does anyone know of a good utility for voice dialling?
I tried Microsoft Voice Command 1.5, it is alright, more or less (apart from awful recognition of spoken numbers, even if spoken by upper class English people) it does recognise the contact names, witch is all that I need - however, I cannot get it to react when I press the action button on the car kit.
I still have to take the phone out of my briefcase, and hold it in my hand, witch is illegal whilst driving.
My dream application, would be something basic, that I can train for certain contacts that I call regularly (like with my old nokia phone, which appeal glows by the minute) – as this way, thick eastern European accents do not matter ;-)
Thanks in advance for any pointers!

I have the MDA Compact Working with the CK7W form Nokia.
Works good exept the voice dailing, You can thakeand disconnect a call with the remote controle.

But do you have to manualy connect to the car kit every time you get into the car?
Once it is connected, I can accept and end calls using the action button. so that is not a problem

No just hold the center button of the remote for 2 seconds, than it will connetct again

tbouman said:
I have the MDA Compact Working with the CK7W form Nokia.
Works good exept the voice dailing, You can thakeand disconnect a call with the remote controle.
Click to expand...
Click to collapse
Hold on a minute, I have the same Nokia car kit, and my Compact when connected suffers badly with reported echoes at their end, not mine.
Do you have this problem?
I was to believe that this was a common problem not resolved yet!
Mike.

I'm gonna test this tomorrow in my shop, I will place a list with phones(other than Nokia) that will work with the CK7W[/quote]

My car kit is CK-1W
I am generaly happy with it, apart from the fact that on the MDA I have to manualy connect every time I get into the car.
I used it with many different phones, and it works fine.
so I think that it is the bluetooth manager of the MDA that is to blame.
my compaq Ipaw bluetooth manager was the best!
but this one, I cannot even get the activesync to work...

For the manual connect you have 2 blame the BT manager in w2003se.
I have good results with:
Nokia CK7W:
Qtek 9090
Qtek S100
Sony Ericsson P910(I)
Sony Ericsson P700i
Samsung D500
HP6340

Are there alternative bluetooth managers?
or a reg. hack I can implement?
thanks

Hmmm, I Don't know...Anyone?

Apparently not…

I had the same problems with my mr handsfree genius car kit, and i thought it was the fault of the car kit.
Just upgrade your rom to 1.06 and all your problems will disappear most likely.
Which rom do you have?
Andre

I have an old ROM.
however, all my atempts at upgrading it failed.
my device ID is something like TMOB-005, not 001
cracked update exe file did not help, running the scripts to modify the ROM files did not help...
in the end I felt inept, and gave up ;-)

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.

Can bluetooth headset trigger auto answer?

Apologies if this is an FAQ, but I've had a quick look and drawn a blank.
I've just got my first Windows mobile phone (Vario II) and one of the things I really miss compared to my old Nokia, is that when I connect my bluetooth headset, I'd like the phone to switch to 'auto answer' and for the volume to be set to max. When I disconnect the headset, I'd like the phone to refert to a 'normal' or 'general' profile.
I require this because I use it on a motorcycle in conjunction with an intercom system, and I need the phone to auto answer after say 2 rings.
Is this possible on a smartphone?
Regards,
Glenn

Join the club mate......
I've been using the Vario2 in combination with a Nolan N-102 with the N-comm BT kit on it.....
I've been #$^&# with it for weeks now and I've made some progression...
First you need a program that allows you to select profiles like Nokia used to have...
I use PocketzenPhone but maybe there are some other(better) programs to do that.....
So then u can swith to a bike profile I've made and enable auto answer....
I've run the cab file to redirect BT sounds to my helmet in stereo (floats somewhere on this forum)
The only thing I can't do at the moment is enable Voicedial from the helmet...
If I press the button designed to start it ........f%ck all happens....
Still working on that but I'm running out of ideas....so any help would be appreciated...
Danny.

Pdanny said:
Join the club mate......
I've been using the Vario2 in combination with a Nolan N-102 with the N-comm BT kit on it.....
I've been #$^&# with it for weeks now and I've made some progression...
First you need a program that allows you to select profiles like Nokia used to have...
I use PocketzenPhone but maybe there are some other(better) programs to do that.....
So then u can swith to a bike profile I've made and enable auto answer....
I've run the cab file to redirect BT sounds to my helmet in stereo (floats somewhere on this forum)
The only thing I can't do at the moment is enable Voicedial from the helmet...
If I press the button designed to start it ........f%ck all happens....
Still working on that but I'm running out of ideas....so any help would be appreciated...
Danny.
Click to expand...
Click to collapse
Hi, the reason you can't activate voice dialing from your headset might be to do with the BT Audio cab you have installed to redirect sound through your headset. If the cab you have installed is the most common one floating around then this actually disables the launch of voice dialing in favour of being able to toggle between sound in the headset and sound on the phone (pressing and holding down the call button for a few seconds on your headset normally).
If you look in the registry HKLM>software>OEM>voicecommand, if launchapenable has a value of 0 then it is disabled. You can enable it again by changing the value to 1 but this will mean that your headset button will now not work as an audio toggle feature because it will launch the voicedial software every time.
Not sure if this is the answer to your problem but it sounds like it might be, hope this helps

Am trying as we speak....thanks for the reply....see wat happens...
D.

Well.....Ive got good news and bad news....
The good news is that I can trigger voicecommand now......
The bad news is that MS voice command 1.6 is not reconizing my accent...(dutch)...
So out of 10 tries it never called the number i wanted.....
So I tried the build in SDdialer.....and that one is doing a better job....
However I can't make the sounds to stick in my helmet........
I mean...
With MSVC by pressing the button on the helmet I could redirect the sound to the helmet and get a voicecommand tone at the same time....
By symply not speaking or saying '"cancel" it would cancel the voicecommand but the sound stayed in the helmet.....
With SDdialer following the same steps as above the sounds does not stay in the helmet but goes back to the speaker......
Any ideas????
BTW is there a dutch version of MS voice command?

If you go back into the registry, in the same location as before, check the value that is in VoiceCmdDuration (This is the amount of time the voice prompt stays active for in seconds) .. the audio cab file usually sets this to 86400 (24 hrs in seconds), if yours is low eg. 10, 20, 30 etc.., set it to 86400 and that may sort out the problem.

Duration is set fort 24 hrs....already..
Funny thing is that MSVC is not cutting out and the sddialer is...
Regsetting stay the same.....
By pressing the button on helmet I just change the exe file.....
Only option is to try and get MsVC to work and get use to my voice....
D.

Hmmm booking slow process.....tryed to call with MsVC and now 2 out 2....
Ordered to play media from helmet......worked..
This is only sitting in the livingroom with helmet on.....looks absolutely silly but thats besides the point
P$ssing with rain here so hoping for better weather to go for a roadtest...
So thing needed for me to get it to work...
-MsVC 1.6
-Bluetooth stereo cab
-Regedit from the MsVC topic..
-PocketzenPhone for designing profiles.....however thinking on removing that...and see how that works.....
D.

I am glad that you are at least part way there to solving the problem
I don't have Voice Command on my phone. On the rare occasion I use voice dialling I use the standard SDdialer program but my sound diversion does not revert back to the handset like yours.
I must have changed something on it to get it working but I am afraid I don't know what because, when I was trying to get it working, I tried absolutely everything and it was quite a while ago now so I have forgotten what I did
It sounds like Voice Command is going to be okay for you though so that is good.
By the way, Phonealarm is also another good profile switching program.

Thanks for the replies guys, but I think I may have accidentally discovered my own solution.
On my T-mobile vario II, if I go to the Phone->Settings and select the 'more' tab (need to scroll along the last tab at the bottom of the screen) there is an option to 'Automatic pickup' which will auto answer a call after x number of rings.
I had always assumed this would kick-in even if no headset was present. However, I've just done some simple testing, and it looks like the auto answer only kicks-in if the phone is currently in comms with a headset (I used a bluetooth one but probably the same for the supplied 'hands free' kit).
So this functions exactly as I want it to.
Oh, and Pdanny, for background info I'm using a Nolan 101 (no bluetooth) with speakers and mic installed. These connect to my 'Starcom' intercom (via an old fasioned curly lead) which allows me to hear directions from my 'TomTom' and also take phone calls via the starcom/phone bluetooth partnership. Down side is that the wife can also talk at me .
As I never want to initiate a call while riding, this setup works just perfect for me. I don't need to remember to change the phone setup either before or after mounting the bike. As soon as the bike ignition is turned on, the intercom partners with the phone. Then if I receive a call, it auto answers and I can take the call. Once the ignition is switched off, the phone reverts to normal non-auto answer.
In my research for this issue I came across an app called 'phonealarm' (from pocketmax.net), it was the manual for this that made me try the above experiment. This looks like a neat app and I may still end up installing it as long as it does not hog the processor.
[edit]OOps sorry Nicky, just noticed you already mentioned phonealarm. I'd be interested in any comments you have about this app, good ot bad [/edit]
Once again, thanks for the replies, and I hope this thread helps someone in the future.
Regards,
Glenn

Phonealarm......give that a try thanks.....
Im also going to test with the buils in auto pick up.....
I knew it was there but i assumed that it would ALWAYS auto pick up...
It seems that that is not the case therefore making the Pocketzenphone and possibly phonealarm obsolete.....
I also get all the sounds over BT in my helmet....incl TT
Also... I don't have a wife .......sounds like a perfect world hey???
Keep you posted on the outcome of the xperiment....
Grtz
Danny

Hi knnelg, glad you managed to sort your problem. I always knew the option for autoanswer was in the settings but like you, I had assumed that it would autoanswer all calls regardless of whether a headset was connected so it is handy to know that it only applies when in headset mode.
You asked about opinions on Phonealarm, I think it is a great program. I have used it on my Vario II and my last phone, an XDA Mini S, and it is has always worked fine, no problems at all.
I really missed having phone profiles when I switched to PDA style phones so Phonealarm was one of the first 3rd party apps I ever bought and I wouldn't be without it now Also, Bruce, the developer of phonealarm, is very good at listening to users input and if enough people make a suggestion about an improvement or tweak to the program, he will implement it in future versions which is really nice.
One of the other programs Pocketmax does, Alarmtoday, is useful too.

Bluetooth pairing diagnostics?

Hi all,
I am unable to pair my XV6800 to my Pioneer DEH-P980BT car stereo. The phone detects the stereo and requests the PIN, but fails after I enter the PIN with a 'Cannot Connect, connection failed or pin is wrong' error. I have used this stereo with my xv6600 Blue Angel for over a year (Can you say Widcomm stack?).
Anyway, I have been unable to come up with fruitful answers or even a next good step by searching the forums or general internet searching. I am wondering if there is some kind of Bluetooth tool that would allow me to determine what actual error is occurring?
Any help would be greatly appreciated.

I had the exact same problem with the same head unit. Here's what I did to correct it:
Code:
The vario II identifies itself as a PDA bluetooth device. The pioneer modules are searching
for a phone or smartphone, so it just ignores the Vario II.
Solutions:
Change the COD (Class of Device) from a PDA device to a smartphone device.
This can be done this way:
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.
That SHOULD work for you. Please let me know if does, because when I do it, the stereo finds the handset fine, but I can't hear any conversation coming out the speakers. It's like it is on permanent mute. This also happens with my BT headset - all controls work, but I can't hear anything nor can people hear me. Plus, my Mogul's speaker cracks and pops when I try using it with another BT device. I think it may be a bad unit. I want to know if you have better luck with the Mogul and 980BT.
I am using the newest ROM (2.17) and radio. The same thing happens to me with the older 2.09 ROM also.
sup191

Eureka!
It worked! I had tried this COD change before and had tried initiating pairing from the stereo, but had not tried both at the same time. I am able to connect the phone and bluetooth stereo simultaneously, and both are working with excellent sound quality. That's leap and bounds from where I was yesterday. Thank you very much!
Regarding your problems, I am not experiencing them at all. I can hear both sides of a conversation as can the other side. As it stands I think I will have to manually pair every time I get in the car (a pain, but I will work on it).
I am not sure what differences exists between the Hermes and Titan, but I would be happy to investigate for you wherever I can. My ROM is version 2.09 and my radio is version 1.30.
Thanks again. Feel free to post or PM me if I can help you figure your issues out.

Thanks for the offer to help. I think my first step is going to Sprint and showing them that BT is crap on my Mogul and see if they'll swap it for me. I'm also going to try pairing my headset there on the demo and see if it works. If it does, my unit it broken. I'll let ya know what happens.
sup191

Bluetooth Problems on X1

Hi,
hopefully anyone has an answer to the strange bluetooth behaviour of my X1.
The first device is a bluetooth headset from Sony. It works good, if bluetooth is activated. But after some time of not using the headset, the phone just switches off bluetooth. Sometimes after a few minutes, sometimes days after my last use of the headset. I tried all settings of the bluetooth-settings with no change. And it sucks if with the next phone call the headset cannot connect anymore because bluetooth was switched off.
The second device is a GNS TrafficBox Plus FM9BT-Y. Somehow MN7 does not detect the device directly, so I have to use the workaround with the serial port and outgoing connection on COM1.
The initial minutes the connection works fine, but then stops and is not restored.
Here as well trying different settings changed nothing.
How can I find out the address of the bluetooth devices?
Is there a tool to further test bluetooth connections (like what speed can be used, the address of the device, etc)
Regards
pt

Im using Itjes Touch 7 final & i have the same problem - infact i've had it with the last 3 of his roms with my blutooth to SEAT car. I'll be on a call in my car & it switches the blutooth off without warning. generally after about 10 minutes of actual call time. But it doesnt disconnect unless during a call ? There is no rhyme or reason to it, it just sometimes happens?
So any further info will be appreciated

Im using Itjes Touch 7 final & i have the same problem - infact i've had it with the last 3 of his roms with my blutooth to SEAT car. I'll be on a call in my car & it switches the blutooth off without warning. generally after about 10 minutes of actual call time. But it doesnt disconnect unless during a call ? There is no rhyme or reason to it, it just sometimes happens?
So any further info will be appreciated

I have Ra2generic DE with the 1.10 radio ROM on it.
At the beginning it was fantastic not having the bluetooth issue. Everything was working so extremely goood... no switching off, no disconnecting of and from the bt headset,, etc...
After a while the issue was here again...damn! So the bt became not very useful in its functionalities.... then I saw that it was not possible to see through my bt freespeech device in the car the last calls on the phone... hm, ok I said. There were lot of calls (incoming, outgoing, missed, etc) on the list...I erased them all...
Now it is working in a perfect way.... no disconnecting, no switching off..and this with the stock ROM and Radio ROM.
I tried it a few months before posting it here... now I'm cleaning up my calling list every 2nd day (I really call a lot) and I have no problems..
Hope it works for you..

i have the same problem, the bluetooth disconect without any reason, i have tried more than 10 Roms and i dont have any solution
¿is so dificult for Sony to repare this problem?

zagito said:
There were lot of calls (incoming, outgoing, missed, etc) on the list...I erased them all...
Now it is working in a perfect way.... no disconnecting, no switching off..and this with the stock ROM and Radio ROM.
I tried it a few months before posting it here... now I'm cleaning up my calling list every 2nd day (I really call a lot) and I have no problems..
Hope it works for you..
Click to expand...
Click to collapse
I hardreseted the device, installed the newest official firmware, deleted the calling list and with great expectations checked bluetooth behaviour.....nothing changed for me
But great it works for you and thanks for the tip

Come on people..... please someone help us with this

Bluetooth with clarion mind
Am having trouble connecting with my new Clarion MIND - is seems the phone does not see the profiles (very similar to the phone adding the older SE Bluetooth Watch, the 100). Has anyone built a .cab to sort this out?