Anyone having problems with VE bluetooth and WM6 phones?

[Janus]

As the title says I was wondering if anyone else is having trouble with PDA's and phones running Windows Mobile 6 working correctly with the VE bluetooth.

I have a iMate JasJam and have used it with my Calais V since I got the car, about 9 months now, without a problem. I synced it in and it worked every time I got in without a problem.

iMate then released an update for the phone from WM5 to the newly released WM6. I installed the update and resynced the phone with the car, as the reformat deleted the partnership between the two. However, when I sync the phone I get the "voice in" displayed on the center screen but then it stays there no matter what I do, where as before it would go back to the radio and the phone was not in use. I have tried all the buttons on the center and the steering wheel but none of them make a difference. The only way I can get it to go back to the radio is to turn off the bluetooth and wait for it to time out the connection.

A couple of days ago my father got a new HTC TyTN II which runs WM6 and I have the exact same problem when syncing it to the car.

It is really annoying as I like the bluetooth function and that was one of the reasons my father updated his phone as the old XDA2 that he had was not compatible with the VE bluetooth stack.

As it used to work for me running WM5 and does not work for both my father and I running WM6 I am assuming that it is a problem between the car and WM6.

I was wondering if anyone else running a WM6 device was having the same problem or if anyone could suggest a way of fixing it.

Or does anyone use a WM6 device and have no problems at all? Which would suggest that something is wrong with the bluetooth in my car.

[vasyd]

A quick search on google revealed that the problem is not just with holden bluetooth. Have look at this thread on whirlpool.net.au.

http://forums.whirlpool.net.au/forum-replies-archive.cfm/740831.html

[nickelgts]

Hi Janus

I'm new here. I've been looking at the forum for some time, but decided to join to see if I can help you.

Your problem is one I had over Xmas. Up until Xmas, I had an XDA II mini (Pocket PC 2003 SE - so older than your JasJam), which had no problems with being recognized by my car. I also had Windows Voice Commander 1.5 installed on the mini. Calls came through no problem. The calls were not announced through the speakers as version 1.5 of Voice Commander didn't support bluetooth. But calls could be made by using the hard button on the phone and saying the name. It would then connect through the speakers no problem. Calls coming in were also fine (but announced by name only on the phone, not through the speakers, although the music did stop and the phone rang).

At Xmas, I treated myself to a TyTn II. Great device!! At first I couldn't get it to work with my car. I was pretty upset, as one of the reasons for upgrading was to get Voice Commander version 1.6 installed so that I could make calls by pressing the button on the steering wheel (and have satnav included instead of being charged $2,000 for the privilege). Eventually, I deleted the previous pairing, and re-paired. (This shouldn't be necessary, as the car is supposed to be able to be paired with more than one phone - and no doubt can). I'm not sure what I was doing wrong the first time, but after re-pairing it - it now works. I can press the button on the steering wheel and make calls.

Your father should get Voice Commander 1.6 if he hasn't already. It's great. You can press the button on your steering wheel and ask it to dial anyone in contacts. It will also read your sms messages to you as they are received. It will interrupt your music to play them to you. It will also interrupt your music to read you any reminders. All through the speakers !!! (Switch it off if there is someone else in the car who shouldn't be hearing them!!) The only problem with 1.6 at the moment is that on TyTn II, it won't announce the call. But hopefully they'll fix that.

If I were you, I would try re-pairing again. I had to look closely at my manual (the car manual, not the phone manual), as I think I wasn't doing it properly the first time.

Mind you, whatever I wasn't doing right was not causing the screen to hold the "voice in" message. It just didn't recognise my device.

If you are still having problems, let me know, and I'll see if I can help any further.

Love the forum. I'm still stock at the moment, but will look at mods very soon. Had a few problems with my first GTS accelerating on its own, so I'm a bit wary of making any mods until I'm sure the car is okay. Had to sue over the first car, but love the GTS so bought another one. And Mike Kennedy at City Motors is a lovely bloke, so I went back to him. Not his (or the dealer's) fault that the problem occurred. Anyway, it's all sorted out now. Great value for money and it still puts a smile on my face!!!

Cheers.

Sorry, I should have said Microsoft Voice Command 1.6. Voice Commander is a program that is already installed on the TyTn II, but is nowhere near as useful as Voice Command.

[Janus]

Thanks for the advice guys. Will definitely read through the Whirlpool page and see if there is anything useful. I will also try resyncing the phones as suggested but I don't think it will help as I have tried this before with the same result.

I think I will show the service people when I have to take my car in yet again sometime this week, if the parts they need for my other problems have come in, and show them this, although I doubt they can do anything. They always just make up some excuse as to why they have no idea about how the electrics etc work.

Thanks again, would appreciate any more info in people have it.