Database Develop

found a commercial car kit

HI everyone, been reading th eforum for a while now, and the questions if car kits keeps comming up.
I managed to find one today online, looks ok, but needs professional installation.
here is the link ( and no, before you ask, I am nothing to do with the company, just came across it while looking for accessories for my new XDA)
http://www.directmobileaccessories.com/product_info.php/cPath/161_162/products_id/585
hope it's good!
Thanks
John

Product not found!

Sorry about that, if you look under O2 in the same page you will see it. Ever so sorry about that.
damn links!!

This is the O2 xda car kit
I ordered the kit from directmobileaccesories.com and it arrived yesterday, it is an O2 boxed xda car kit.
Everything works fine - except - I removed my old Nokia 9110 car kit which had a radio mute kit that feeds the phone through the car speakers, and tried to connect the radio mute from the O2 kit to the radio mute lead used by the Nokia car kit. When I place the xda in the cradle it immediately cuts over from the radio to the phone, even before the phone part of the xda is activated.
I have a radio mute on the steering console so I have temporarily disconnected the mute lead and fitted the speaker that came with the xda car kit.
Any suggestions why the radio mute cuts over straight away ?

Try making a call
Hi,
I have seen the same behaviour, it looks like the mute works reversed. If you make a call the radio will swotch on.
If this is your problem it should be easy to fix by using a small relay or something similiar.
Francois

the problem has resolved itself
the problem I had with the radio muting all the time has resolved itself, it now works perfectly.

O2 XDA IIi Bluetooth with Bluetooth Car Kit Issues.

Hi Guys,
Recent got an XDA IIi after being with the older XDA II for over 16 Months.
But I have recently run into problems with my BT Car kit :
Motorola Bluetooth Car Kit HFW-8000.
Basically the problem is that it does not always connect to the Car Kit and when it does it will only from time to time connect and let me have a handfree conversation.
I have also used the Broadcom Bluetooth Cab file here in order to extend what Bluetooth Profiles that can be used but seems not to have any great bearing to stablize the issue.
So I went down the Hard Reset Road but again still intermittent issues, I then upgraded the ROM to the New one on the O2 Website the v 1.11.169 ROM.
I also had similar issues with the XDA II but it was resolved by using the Pocket Bluetooth tools, which was great and never once after installing it did I have any issues with the Car Kit.
http://www.bluetooth.jazztel.es/
One of my questions is, is there a similar programme to to above Pocket Bluetooth tools for the XDA IIi as I have tried it with the XDA IIi but does not work.
Or does anyone know how you would revert to have the XDA II radio or is there a work around for it.
Thanks Guys
Woody

Hi Woody_XDA,
I have had my XDA2i for a couple of months now and recently got a O2 blue headset for it, I had simular problems with the headset disconnecting and having to manually connect every time I switched it on. After browsing this wonderfull forum I decided to do a corperate install and get rid of the O2 active interface, since then no problems at all. I now use Pugs modified ROM version 162 with radio 1.04 and have no stability problems at all with no twice weekly reset. Hope this helps you and many thanks to Pug for his ROM.
Mace

Ditto, I also use the custom firmware with 1.04 radio and bluetooth works a charm. It still eats battery like nothing else, but it works with no problems. Also like the fact that the XDA can cope with my GPS receiver and my handsfree kit simultaneously, that's handy for in the car.

Cheers Guys for the information, took it on board and works great, did a great deal of stress testing in order to confirm it and works excellent..Thanks to PUG again and guys thanks for the info much appreciated and this is by far a great forum

Mace - you mention some bluetooth issues being resolved since you applied the custom ROM... I posted in the Alpine Applications forum here the other day a list of issues with bluetooth that I was wondering had been addressed - so far no reply - are these the symptoms that were cured for you??

Hi Bewlay Brother sorry, I missed your other post on Bluetooth issues, my original problem was that every time I switched on my BT headset , which is a O2 Blue, I had to open the BT manager and make the connection, the phone would then occasionally lose the connection and sometimes whilst still showing a connection refuse to transfer the call. This was using the official 162 ROM with the O2 active UI. I have since installed Pugs 162 ROM with radio1.04 and done a corporate install and BT seems to work perfectly, switch on the headset, it connects, never loses pairing and transfers calls.
Hope this helps you, and thanks again to Pug,
Mace.

Mace - what you describe sounds similar - my problems were essentially the loss of pairing with my Motorola headset a lot of the times when the XDAIIi switched off its display and went into stand-by mode, also if I closed the boom bike on the headset (to temporarily turn off the headset) it would fail to re-pair when I next opened the boom mike... the other issue was that I had to make sure the phone keyboard was displayed on the XDA once I had paired up otherwise the last number redial function on the headset would not work - if I pressed the dial button on headset and the phone display was not on the screen it would simply open the phone display function but fail to then dial the number - really crap. Also reception was poor to headset even over relatively short distances from the XDA. IF these areas in particular could be cured by the upgrade then I am eager to do it - I must admit I have read that this upgrade has not been without problems for some people here so it is going to be a tough call.

Just a thought, but have you done a personal or corporate install as I think the main fix with Pugs ROM was the upgrade to radio 1.04, which I don’t think affects the BT, so a corporate install with your existing ROM may make a difference.

Did a corporate install when it was new out of the box...

whats the difference between the corporate and personal install?

Corporate doesn't install ANY of the branded O2 interface - so no gubbins, nothing to slow down the phone, you just get a bog standard Windows Mobile 2003 SE installation, aside from the O2 GPRS and SMS settings. Bosh.

hi
i've been reading the posts and i have the same problem where can i get hold of pug's ROM if it's possible cos this seems to get rid of the problem

And then today, headset will not automatically connect, needing Bluetooth manager to be opened to make the connection. AARRRGH!

BT car kit problems
I have the 1.04 Radio, but it still won't sync with my 2003 BMW 325xi bluetooh or with my 2005 Acura MDX bluetooth.
Help!

Unstable Bluetooth Signal Strength - Samsung WEP200 Bluetooth Headset
Hi, I just got a Samsung WEP200 Bluetooth Headset. It would pair with my O2 XDAIIi but I cannot hear any voice in both incoming and outgoing calls. When I check the BT Manager, it shows a totally unstable BT strength that varies from very strong to very weak. The same headset worked well with other BT phones. My ROM version is 1.11.00 WWE, Radio version 1.04.00.
Any help would be greatly appreciated.

WM6, bluetooth car kit and incoming port problem

Hi guys,
I am at the end of my tether... I just bought a JVC head unit with on board bluetooth, so I can use it as a car kit. But I can't get my Treo 750 to pair with it! It just locks up after I enter the passkey... and the car kit just says "error" after a certain amount of time. I'm running a vanilla (extended ROM removed) version of the 3 Australia ROM.
So, I rolled back to Windows Mobile 5... same problem... UNTIL I went into the Bluetooth settings and setup an incoming COM port. Then it paired up perfectly and all was well.
So I've reinstalled WM6, but it doesn't have the option to create an incoming COM port. That's really annoying. I've googled a heap, and searched these forums a fair bit too, but haven't been able to find any sort of workaround. Is there a registry hack, third party program, or some other way I can tell it to allow an incoming connection from the car kit?
Thanks in advance!

Has anyone had any ideas on this? I have a real issue now, as I rolled back to a WM5 ROM which I found on these forums but I'm having awful problems with it - it drops calls all the time and sometimes they just go silent..... the call stays connected but I can't hear the person on the other end.
I really need to get either the original Telstra WM5 ROM, or a way of getting WM6 to work with my car kit! Any ideas... anyone??

Okay... now I really feel like I'm talking to myself but anyway.... thought I'd give an update.
After heaps of trial and error, I managed to install the Universal version of the Broadcomm bluetooth stack onto my device. And it pairs - hooray!
However... when I make a call, no sound comes through the speakers
No other version of the Broadcomm stack will run on my Treo, I just get the memory error that lots of other people have mentioned.
Chalk another person down who's royally annoyed with Palm for putting such a dodgy implementation of Bluetooth into these devices. It's my one and only bugbear to date.

I have exactly the same problem when pairing my WM6 Treo 750 to a Parrot MK6100 carkit. After entering the passcode on the Treo, the device just hangs. The carkit says it has connected succesfully, but nothing happens. After restarting it does not recognize the carkit at all.
Did you find a solution yet? I am also looking for a different Bluetooth stack that is guaranteed to work with the Treo.

Good to see I'm not the only one. No, I haven't found a solution yet unfortunately
The closest I've come is that hacked Broadcomm Bluetooth stack. My only hope is that some nice developer will help us develop something that works!

Hi Ben,
I solved my problem yesterday. I tried two suggestions.
1) Leave the passcode field blank (do not enter '0000') and press next
2) Install http://www.jetwaremobile.nl (fully functional 30-day trial)
After that pairing succeeded in a couple of seconds and all is working well. Let me know how it works out.

Thanks very much MattMax!
I had tried the Jetware software previously, and it didn't help. But I hadn't tried leaving the passkey field blank. Did that this morning... it popped up with a connection dialog asking if I wanted to allow the connection... went back to the passkey screen, I entered 0000 and away the sucker went. How simple was that!!
I just upgraded to the latest ROW2.23 WM6 ROM the other day, so I'm not sure if that made any difference either. But it's now paired and (seems to be) working well, just need to make and receive a few calls to make sure.
Thanks very much for your suggestion!

Good to hear that it worked out!
I had exactly the same experience, leaving the field blank, after that entering '0000' and it worked. I had just installed Jetware Mobile, but apparently that is not necessary for the solution.

TyTN II + Parrot 3200+ LS Colour

Hello,
I wonder if somebody can help me get to the bottom of this.
Basically, I have a TyTN II (branded as a T-Mobile MDA Vario III). I also have a Parrot 3200+ LS Colour car hands free kit.
Initially, I had a TyTN (branded as a T-Mobile MDA Vario II) and this worked fine with the Parrot. Problems began when I upgraded it to Windows Mobile 6 after an update was released by T-Mobile. What would happen is as I started the engine and the Parrot connected to the phone, it would say I was in a call even though I wasn't. It could only be resolved by rebooting the phone.
When I got the TyTN II, the problem became more frequent to the point where it was just annoying to use.
Now, this is where it gets interesting. Parrot are blaming Microsoft for this problem and aparently the problem *may* or *may not* get fixed in 6.1 which is some time off yet. It is a Bluetooth Stack issue aparently but I am not sure I believe them on this nor their attitude to if it will actually get fixed.
I am wondering if anybody knows anything more about this or any fix for it.
Best Regards,
Craig Brass

craigbrass said:
I am wondering if anybody knows anything more about this or any fix for it.
Click to expand...
Click to collapse
Install one of the 6.1 ROMs here and see if it helps?

I have this with my TyTn II and parrot 3300. It also used to happen with my Orbit.
I noticed that it only does it when a data connection is active. If I press the red button on the Parrot it clears and all is good.
Not sure if yours is the same issue.

I have a Parrot 3100, and have loads of problems! It randomly crashes, it randomly decides to want to call random people, it randomly decides to route the call through the Tytn II rather than the Parrot, and it randomly works without a problem. I emailed Parrot and got this response:
--------------------------------------------------------------------------
The HTC TyTn II is still undergoing compatibility tests with our products, thus is not listed as being compatible at present. We are currently also working closely with HTC to improve compatibility and functionality with new PDA devices running Windows Mobile 6.
I would recommend dialing out from the Parrot as opposed to using your handset as from experience this works best.
I would also recommend updating the software on your Parrot, the latest version is 4.16. To update you will need a Bluetooth enabled PC (preferably a laptop) and our Parrot update tool software. http://www.parrot.com/usa/support/downloads
--------------------------------------------------------------------------
Just noticed tonight that a new version is available for download, (4.17) so I have upgraded the Parrot and will give it a try tomorrow.
Cheers

so, was the upgrade succesfull? did it solve ur issue?
I'm also having issues using my tytn ii with the parrot ck3100. (standard firmware in it)

No, it hasn't completely. It has solved most of the problems, but it now decides to (randomly) mute incoming calls, and route the audio through the handset instead. It also decided to route the TomTom audio via the parrot! I didn't think that was possible???

I'm having some of the same sorts of problems w/ the Parrot CK3100 and my Tilt. Of course, I just go it installed last nite, so I haven't had a ton of time to play with it. I DID, however, do a long road trip today and here's what I've found.
When initiating a call from the phone, there's about a 50/50 chance that it will go thru the handset or Parrot.
One time, the Parrot locked up to a point that I had to get off at an exit and restart the engine to reset it.
I had to re-pair the phone and Parrot once, because the lost one another.
I'm running the latest AT&T ROM on my phone and latest firmware on the CK3100. I never had ANY of these problems w/ my Nokia CK-7W, but it had a REALLY annoying echo on the other end when used w/ anything but a Nokia phone.
Dan

Today, things got even stranger. As of this morning, the kit would try to initiate a phantom call every time the car was started and it connected w/ the phone.
Then, it was muting the radio for 1-2 seconds every 3 to 5 minutes - very annoying when listening to an audiobook.
As of this afternoon, both problems magically stopped. I have e-mailed Parrot tech support, but I'm not hopeful that I'll get a useful reply.

I have had so many problems with the 3200 that ,due to anger, I have broken the bracket and front screen. It mutes the radio even after the call has finished. Crashes too often. I have no audio at least half of the calls I make.
I must add that it also did this with my Trinity running WM6 but worked flawlessly with my SP5 smartphone.
I read "HTC and Parrot Announce Strategic Alliance" on the Reuters website.
How I chuckle.

Connecting to bluetooth car kit takes very long!

Hi,
my Diamond works ok with my Parrot bluetooth car kit. The only thing that is really anoying me, it takes veeeery long until the Diamond has established the connection to the car kit. I have to drive for several minutes! until the Diamond connects. Before I had a Sony Ericcson phone where I did not have this problem.
Any ideas? Is this just because the Diamond is a WM phone?? Or is there a way to improve this?
Thanks

I use my diamond with a Parrot CK3300 - not sure if that is the same as yours. I only use it for handsfree since I use the Diamond's own GPS receiver. I don't have this problem - it picks up and pairs within seconds.
Have you flashed the Parrot with the latest software? I found that improved performance considerably - automatic update of contacts, user name on screen rather than phone name etc.

I use the Parrot CK3100 and the pick is almost instant; I've barely got in the car and started it up and the Parrot has picked up my Diamond. It was just as quick on my Hermes device too.

I also have a CK3100 and here's somewhat the same problem.
It connects in a few seconds, and it's usable.
But the synchronisation takes forever.....
That doesn't bother me, becouse I'm quite long in my car when driving to work...
But:
The phonebook in my CK3100 starts with the numbers wich are saved on the SIMcard.
All my friends are saved on the internal memory of the TD.
So if i want to call 'Anouk': I press 'A' on the CK3100.
It starts with the 'A' from the SIMcard.
Then I have to use the turning wheel, to scroll BACKwards to "anouk'!
So this takes a lot of time.... and is very, very unpracticle.
Someone a solution for this?

As I said before flashing the latest software onto my Parrot made it much better for syncing contacts. But I only need do it once - after that it only checks for changes. It should not be syncing each time because the Parrot should store the contacts itself.

Yep, just check the Parrot website to see what the latest update is for your particular BT device and try applying it. Saying that, I've not updated my one from factory.

Unfortunately I was not able to update my Parrot so far. I have only a CK3000 Evolution, Firmware version 5.08C. I guess I would need this special serial flash cable...

@ swissly
i have the same problems fw months ago. you have to delete the partnership's on your CK3000. press the red and the green button for more the 3 sec. (Erasing in progress) if this is done you can create a new partnership. hope that helps.
\\yoshi

swissly said:
Hi,
my Diamond works ok with my Parrot bluetooth car kit. The only thing that is really anoying me, it takes veeeery long until the Diamond has established the connection to the car kit. I have to drive for several minutes! until the Diamond connects. Before I had a Sony Ericcson phone where I did not have this problem.
Any ideas? Is this just because the Diamond is a WM phone?? Or is there a way to improve this?
Thanks
Click to expand...
Click to collapse
Hello
For all of you who have a Parrot Bluetooth car kit listen up:
When you use any phone with any Parrot Bluetooth car kits please go to the Parrot support website to flash your car kit - http://www.parrot.com/uk/support/onlinehelpguides
This will update the device with the latest firmware and as Parrot continuly add new phones to their list it is must. I did it as soon as my HTC Diamond arrived and finds it pairs/syncs within 1 - 3 seconds of switching the car on. FYI I have a Parrot MK6100 device, which supports A2DP Bluetooth audio and is mint. Previous to this I had an SPV M700 and a Parrot CK3100-something, but same thing - update it and you will find it solves the problem(s).
- PLEASE HOWEVER READ THE INSTRUCTIONS ON FLASHING - IT AIN'T HARD BUT READ IT ANYWAY!!! -

Please correct me if I'm wrong, but I still think I CANNOT UPDATE my Parrot CK3000 Evolution WITHOUT THE PARROT SERIAL CABLE!

swissly said:
Please correct me if I'm wrong, but I still think I CANNOT UPDATE my Parrot CK3000 Evolution WITHOUT THE PARROT SERIAL CABLE!
Click to expand...
Click to collapse
You are correct AFAIK. Most other Parrots can be updated easily using bluetooth, but not that one. Probably why it was cheaper than the others.