Does any one else have this setup...
Im finding that as i end a phone call the gps reciever stops comunicating.
it starts again if you make another call but stops again the minute i hang up.
if i go into the gps driver page and turn off then back on the gps (using the tick box) then its fine again untill i make then end the next call.
Any comments, help or suggestions appreciated.
could possibly be the gps driver corrupted, try reinstalling just the gps driver part from the cd and see if that helps, i've had a similar problem before, but not with a serial gps, i always use bluetooth
tomtom 2 xda 2 this might help..
goto settings - connections - beam once here untick the beam default and then retry you device ........... this solved a similar problem on mine !!! post back youre findings please...
:lol:
Its not the recieve all beams check box unfortunately...
I have to have that unchecked to connect the gprs on com1 anyway...
thanks for your suggestion though - keep them comming...
I have logged a support call with tomtom - no reply as yet...
Is your car kit fully wired including radio mute etc ?? I have the same problem but I also have to disconnect the GPS from the cradle otherwise I cannot carry out a conversation on the phone. Please post if you get your problem resolved.
I didnt fully wire the car kit - i just use the supplied external speaker.
I havnt had any problems making phone calls though.
I just cant get round the fact that the gps is disconnected on terminating the call.
The only work around i have is to turn the device off then on again after each call to re-instate the serial connection to the gps receiver...
I bought my car kit from dashmounts.co.uk the backup from them is S__T It seems that audio is the problem with alot of car kits looking at forums I have emailed tomtom and will post any solution however small they may give
I have tried searching the forums and can't find much Info.
Is anybody here using the above system for telephony & GPS; If so how do they intergrate/do they work well on the XDA II (I have ROM Version 1.72 with Radio1.17)
I Know about the headset profile probs not giving full functionality of the Handsfree use of the car kit but this doesn't bother me to much as long as I can Make and receive calls.
Thanks in anticipation!
I was going to get a CK3100, but heard so many problems regarding build quality, and lack of support, I got a HCB 30 instead.
It did not help when I tried to e-mail parrot for advice and 3 different e-mail adresses bounced back.
Works Perfect!
Just had the CK3300 installed today and it works perfectly - I Knew some of the functions didn't work because the XDA2 only supports headset profile but once you have transferred your contacts to the kit via bluetooth it works well.
Also the GPS works well with CoPilot 5 live; it picked up the signal straight away ; well pleased with this set up!!
same to me have the ck3300 tested with qtek2020 - works fine. problems with 9090 but after bluetooth update now it works fine. No tests with S100 at this time.
tested GPS with destinator 3 and map&guide fleet navigator and mobileobjects fleet management system.
don't use bluetooth tools after Rom 1.66 :!: CK3x00 didn't work aber installation of this
Set up
Just had the CK3300 installed today and it works perfectly - I Knew some of the functions didn't work because the XDA2 only supports headset profile but once you have transferred your contacts to the kit via bluetooth it works well.
Also the GPS works well with CoPilot 5 live; it picked up the signal straight away ; well pleased with this set up!!
Click to expand...
Click to collapse
Any tips on setting up the CK3300 with my XDA2?
Just had the car kit fitted - i need both nav and handsfree functions - but i am not sure that i have got the phone and ck3300 to bond properly. So everything is 'greyed out' on the parrot.
Using ROM 1.72.00WWE (1.72.181) and radio 1.17.00
Thanks for any help received.
If everything is greyed out then it isn't bonded properly!
Step 1
Delete the pairings you have from XDA2 and car Kit;
Step 2
On the car kit turn the control knob untill settings appear- then scroll to 'Advanced Settings' - 'pairing a telephone' - 'windows CE device'
Step 3
Now search for devices using your XDA2 and the car kit should be shown.
Step 4
Enter passcode 1234 and accept headset and serial profiles when shown.
PAIRING COMPLETE
to access your phonebook you need to transfere the contacts via bluetooth to the car kit.
Hope this helps
XDA2 CK3300
Managed to get the GPS set up (fiddling with COM ports - even imbeciles strike lucky sometimes)
Some items are now in black. However, I am not sure that I have done it right as I cannot get it to use my phone to make calls or receive them. Which is exactly why I bought it in the first place.
So, please (please please) can you tell me how to exchange my phonebook?
I am going to sit in the car right now and have a go at your bonding advice...maybe all will become clear (but that is not often my experience!)
Thanks again for your help.
You need to bond the phones in the manner I described or it will not work ; this is clearly ststed in the Parrot instructions and on their website.
(I have noticed a strong correlation between people who do not read instructions and complain things do not work!!) - Joke
You also need to make sure your headset profile is active on the XDA 2 for it to work. Again reading the instructions for the phonebook - you tap and hold a contact on the XDA2 and select 'beam contact' - 'via bluetooth' the bluetooth search then comes up and the car kit will be found you then 'tap to send'
Now i have the opposite problem!
Believe it or not, I have now got the XDA2 and the CK3300 bonding automatically so I can make and receive calls whilst driving. It works pretty well (occasionally makes an awful noise, but only occasionally). I am impressed.
However, once I had done that, the GPS is undetectable. I have tried all sorts of combinations. I have checked the instructions - and selected the long code (ends in 9600) but I am not certain that I am using the right com port. I have tried most of them without success.
Oddly, this is the one thing that WAS working before I got the car kit to work (for calls). Somehow, either I have lost the right settings OR the XDA2 won't do both (although I read somewhere that it would) OR my ROM needs updating (uh?)
Please help.
BTW, I am due a phone upgrade - I love the xda2 but would consider getting another phone if necessary, if anyone can recommend one that is fully CK3300 and TomTom compatible.
I don't use Tom Tom myself but from reading these forums I think you need to install the patch on their website to allow Tom Tom to use the correct Port .
Your Car Kit also needs it's software updating if it makes a noise like you say. On the Car Kit go to > settings-advanced settings-information and you will find the software version (sounds like 4.03) if it makes a noise. The latest on the Parrot website is 4.10b and this will fix the noise issue.
If you need help installing this let me know.
The best Phone is surprisingly the Old Fashioned Nokia 6310i - it has a good bluetooth stack and uses the handsfree profile rather than the headset so contacts sync automatically but if you require live traffic info best stick with what you got as the Nokia will not pair with the XDAII and the car kit at same time.
Which COM port?
For the moment, I have a temporary solution.
However, I have updated the TomTom Navigator software and the GPS, but still don't know which port the GPS in the CK3300 should be connected to.
Any ideas?
And, thanks Nikpro for the excellent help so far - you are a true altruist and a star!
The outbound port on the xdaII is port 5 by default
On XDAII go to Settings - System tab - Bluetooth settings and make sure you check the tick box for outbound COM port.
There is also a chance you have deleted your serial port profile so tap on the bluetooth icon in the Today Screen and go to bonded devices. Select the CK3300 and delete partnership (do not delete pairing from car kit end!)
Then search for new devices from the XDAII and the CK3300 will again come up; create a new partenship and everything should be good.
Still having problems
Oddly, I still cannot use the GPS on the CK3300.
I am using my old TomTom at the moment for GPS and the CK3300 for headset - which works fine, but I wanted the CK3300 to do both.
When I try and reset the GPS to the (series of numbers ending in 9600) as stated in the info and the instructions (Nikpro, take note - I have read them - but your comment made me laugh), the TomTom just 'freezes'. Wait - and wait - and wait - and when it reincarnates itself, no GPS at all.
I am using the 1.72.00WWE rom and radio 1.17.00
I think that I have tried every permutation for the COM port.
Has anyone any ideas? Please?
When you initially pair your XDA to the car kit do you get a message about serial connection show on the screen? The problem must be with the tom tom software as with copilot and mapopolis it works fine? or the way you are pairing the two!
What software version is the car kit? PLEASE DESCRIBE HOW YOU ARE PAIRING THE DEVICES??
Hi all, 1st post and all that.
Have you tried falshing the parrot with the newest rom, mine picked up enough to make and recieve call, but i flashed my xdaII with 2.02.T1WWE this morning and it works even better.
Hope you get a result
nikpro said:
I don't use Tom Tom myself but from reading these forums I think you need to install the patch on their website to allow Tom Tom to use the correct Port .
Your Car Kit also needs it's software updating if it makes a noise like you say. On the Car Kit go to > settings-advanced settings-information and you will find the software version (sounds like 4.03) if it makes a noise. The latest on the Parrot website is 4.10b and this will fix the noise issue.
If you need help installing this let me know.
The best Phone is surprisingly the Old Fashioned Nokia 6310i - it has a good bluetooth stack and uses the handsfree profile rather than the headset so contacts sync automatically but if you require live traffic info best stick with what you got as the Nokia will not pair with the XDAII and the car kit at same time.
Click to expand...
Click to collapse
Use Bluetooth tools www.bluetooth.jazztel.es
and edit the registry under hkey local machine, builtin, BTIBserial, rename BTIBserial.dll into BTIOBserial.dll
and go Start, Settings, System, Bluetooth settings and check both inbound and outbound.
Delete ALL paired devices, reboot, and re pair them.
You will now have an option for two serial ports, one for each device.
This is the only way to do it if you have two devices that need a serial port. If you have a third, you are SOL.
Normally, the stupid programmers who made the MS BT program, made it so it only had one dynamic port for BT. Some people would experience having to reboot before switching BT devices, most would have to re pair every dam time.
The new 2005 does not have this problem but it has other bugs.
They smart people at MS changed the databases so Mapopolis and other third party programs can not read the contacts or have other bugs with them. Plus the 2005 version here limits your memory.
The 2.02 - 2.06 will NOT work with Hands Free and most car kits need it and if you have caller ID via BT, you are SOL too.
The 2.20 is a stable and a good OS and the Hands free works much better. The down side is, when I get a call on the call waiting, even if I did not answer, it would disconnect the BT headset and no sound through the phone too. I would have to, click on Tools, Hands Free off, tools Hands
Free on before it would work. I have lost many clients this way.
I decided to disable call waiting in the phone settings and it only has a few bugs now like I have to turn off and then back on the BT headset after ever call or it would revert to Headset mode.
The caller ID will not display if the call is in the history of my BT headset or if it is in my contacts database.
I mention my BT headset because it is like a car system when used in Hands free mode.
Good luck, let me know if you have any trouble now.
Parrot 3100 with XDA II
Hello,
I have just put in a Parrot 3100 and it works fine as a handsfree phone.
is there any way when I am not in the car though to use my Jabra 250v headset without rebonding and selecting it as the preferred headset device?
I can't seem to switch between the Parrot and the Jabra when the other one is not in use without repairing.
Thanks for any advice
BT
Try turning of one and turning on the other and soft reset..
Ok, I have just spent my entire weekend trying to get my Qtek 9090 to communicate to my newly installed Parrot CK3300 (with GPS). I have read the manual about 3 times from beginning to end, know the whole website parrot.biz by hard (ugly site BTW), and have tried about everything in configuring, but with no success so far.
Initially I had the 2 devices paired to each other, but after I installed Tom Tom 3, it is impossible for me to get them to pair again. Nevertheless, the 2 devices "see" each other (when asked in "Linked devices"), but they can not get to communicate. From all the stuff I have read on forums and sites, it seems that I need to upgrade my Bluetooth version, but I have no idea how and where to start this procedure.
Can anyone help me out here ?
Any tips are welcome !
I am using Garmin navigator (street Pilot 2820 / BMW Navigator III) and paired it with my WM5 phones without any problems.
Now I updated to WM6 and the pairing never ends properly. Since I am not the only one with WM6 and Garmin pairing problems I would like to ask here for a solution. Garmin is usually very very slow with updates and I use it daily for commiunication on the motorbike.
The phone connects to the Garmin and the Garmin sends it to the BT headset in my helmet.
What happens now:
Initiate pairing, devices find each other, giving the passcode, device connect for 30 secs, then the Garmin disconnects and starts the pairing proces again.
Usually when I am still setting the WM6 device to click on headset profile.
It doesn't matter on which device I start the pairing, they quickly connect.
When pairing I see 2 profiles on the WM6 device: headset and serial port. Headset gets automatically selected.
I have tried with and without authentication (passkey required) selected.
It seems the moment they make a connection and the WM6 device is figuring out what profile to use, the connections fails, the Garmin tries again, fails etc.
I have done a hard reset on both devices to make sure there were no 'left overs' but it did not help either.
Is there anyway to downgrade the BT driver on the WM6 device to get this working again? (I don't use the BT for anything else.)
My current devices 2x HTC Artemis /P3300 with different (latest)ROMS but I got also reports about the same problems with Garmin Zumo and WM6 (Qtec)
Thanks in advance!
Bastiaan
Hey Guys,
Apologies if this is a noob problem but this is my first delve into new roms and WM6.
I have an SPV M5000 to which I have installed Jwrightmcps Crossbow ROM Update 2.12.06 WWE for Orange.
The installation went well and everything but bluetooth is working perfectly. Basically the problem seems to be between the PDA and my Parrot CK3300. Before installing the new ROM the PDA and car kit worked perfectly every time.
So after updating the rom I paired the PDA to the car kit. All went well and I was happy. At the end of the day I left work and noticed that the PDA was not connecting to the PDA. I opened up the PDA and noticed the bluetooth notification that the car kit was trying to connect. I clicked on Yes to allow the connection. It then asked for the passcode and then set the services. It appears as if the PDA had forgotten that it was paired with the car kit. I then tried to connect the two but it failed. So I soft booted the PDA and the same thing happened. I repaired the device and this time it worked, and continue to work for the rest of the journey.
So I then leave for work the next day and the exact same thing has happened. It's as if the PDA is forgetting that it was paired to the car kit. After a little messing around I can get it talking again, but it's a real pain in the bum.
Anyone have any ideas why this would be happening ? Previously I would just jump in the car and drive off knowing that the PDA and car kit would automatically connect. Now I need to spend 5-10 minutes every trip re-paring them.
Any help appreciated.
I tested every WM6 rom and always went back to old WM5 because of bluetooth problems
Hello,
In my car I have the Parrot CK3000 evolution car kit installed.
I can pair it with my nexus without problems.
After pairing incoming and outgoing phone calls should be routed through the handset but that doesn't happen.
My wife's htc hero, after pairing with the same handset, easily allows to establish the connection beetwen the hero and the handset long pressing the "parrot 2.51C" item in bluetooth settings and clicking the "Connect" item.
Long pressing the same item on my nexus shows a popup menu where the only option available is unpair.
Did anybody manage to make this handset work with nexus one?
For your information my parrot car kit has software version 2.51C and restarting the phone, resetting parrot memory, unpairing and pairing again didn't make any difference.
Regards,
Francesco
have a look at:
http://www.parrot.com/forums/english/viewtopic.php?pid=25879#p25879
Although this is for a ck3100.
I have this kit too. I'm at work so I can't test the link you put up but I don't think it will work. The nexus actually pairs with the device, it just won't connect. and the 3100 has an lcd screen so it runs completely different software
I used Parrot CK3100 with HD2. Everything was good! The sync was working very good with tons of rom. I tried with Acer Liquid. It was good. But when I tried with Nexus One original rom and Cyanogen rom I had a big problem with number. I always store the mobile phone number the following form: +36XXXXXXXX. All other phone managed it perfectly but N1 not.
I can sync the number with Parrot but the number was the following format: 36X-XXX-XXXX
It is WRONG!! I can't call the number without "+" I tried with the latest Desire (A10) rom and everything is fine!!!! Like with HD2!!! But the pairing is horrible with the A10. So I use Desire rom now.
I'm talking about a CK3100 here, but I had a problem when I first tried to pair it yesterday, it said it paired successfully but it didn't connect at all, no matter how many times I tried. The solution procedure for me was (maybe some step are not necessary at all but that's how I got it to work)
1. Unpair and delete the reference to the Parrot unit from the phone
2. Turn off phone bluetooth
3. Turn off car bluetooth (keys off until the Parrot turns the screen off)
4. Turn on phone bluetooth and enable visibility
5. Turn on car bluetooth
6. Pair from the Nexus One to the Parrot, enter pin
7. A request to access the agenda apeared on the phone, accept and you're ready to go.
I don't think it matters but just in case, I'm on stock rom (update1) and rooted.
PS: It's a total pain in the ass to have to re-record all the Parrot voice tags whenever I change my phone...
I managed to connect my CK3000 with N1 using the procedure that danimar1 describes.
No luck in copying my contacts to the parrot :/
Did anybody have success with this task?
F.
I've experienced this on other carkits too - it'll pair, but audio never transfers. Obviously a bug in the N1. I hope they fix it soon
In my case routing phone calls between parrot Ck3000 evolution and nexus one works.
The thing that I'm not able to do is to transfer my contacts.
Francesco
the ck3000 doesnt support contact syncing i dont think. that is the one bummer about android phones and bluetooth, no voice tag support. with my bb, it could use the phones voice recognition to voice dial from the car kit
danimar1 said:
I'm talking about a CK3100 here, but I had a problem when I first tried to pair it yesterday, it said it paired successfully but it didn't connect at all, no matter how many times I tried. The solution procedure for me was (maybe some step are not necessary at all but that's how I got it to work)
1. Unpair and delete the reference to the Parrot unit from the phone
2. Turn off phone bluetooth
3. Turn off car bluetooth (keys off until the Parrot turns the screen off)
4. Turn on phone bluetooth and enable visibility
5. Turn on car bluetooth
6. Pair from the Nexus One to the Parrot, enter pin
7. A request to access the agenda apeared on the phone, accept and you're ready to go.
I don't think it matters but just in case, I'm on stock rom (update1) and rooted.
PS: It's a total pain in the ass to have to re-record all the Parrot voice tags whenever I change my phone...
Click to expand...
Click to collapse
when you unpaired, did you delet the phone from the parrot memory also?
doalittledanse said:
when you unpaired, did you delet the phone from the parrot memory also?
Click to expand...
Click to collapse
No I didn't, everything was done from the Nexus One. But if you have problems connecting maybe it would be a good idea to do so.
danimar1 said:
No I didn't, everything was done from the Nexus One. But if you have problems connecting maybe it would be a good idea to do so.
Click to expand...
Click to collapse
and what firmware is your ck3000 on? im assuming thats an issue for me because ive never updated mine and its still at 2.10 i think
I'm sorry I have a CK3100, but anyway I never updated it. I got it a little more than 2 years ago, so I don't think it would be a firmware version problem.