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 !
Related
Tom Tom Navigation is great just got it for the first time with my XDA 11 Car kit. It gets me places fine however If I make or recieve a call Tom TOm locks up and I have to exit the program and restart it, which is sometimes a bit dangerous on the motorway.
OK so I should know where I am but I like things to work.
Has anyone got any good ideas
I forgot to mention that it works in the background during the call but when I hang up it works only for a few seconds then stays in the same navigator window but frozen. I can get to the map view but the arrow doesn't plot my path.
all you need to do is hit the power button to switch off the xda and then switch it back on to restart the gps
I had this problem way back at the begining of the year...
check out this thread http://forum.xda-developers.com/viewtopic.php?t=7109&start=0&postdays=0&postorder=asc&highlight=
Im afraid there is no solution...
The xda disconnects the com port it is using to talk to the gps reciever as it disconects the audio for the call.
You will find the following things :-
1. If you make another call - your tomtom will work again whilst you are on the new call and then stop again when you hang up.
2. If you turn the device off then back on again this will also start the device talking to the gps reciever again.
Eventually the phone kit failed anyway - so i took it apart and disconnected pin 19 with a scalpel so that the device did not think it was in a car kit anymore. see here for a description of the connector http://wiki.xda-developers.com/wiki/Connectors
This then left me with a car kit that charged my xda ii, connected it to an external antenea, and connected to the gps reciever, Not to mention did a really good job of holding it.
I then went out and bought a parrot ck3100 bluetooth car kit to replace the lost car kit functionality.
Its a bit long winded and expenses but it all worked in the end.
If you dont have the money to go bluetooth or dont fancy trying to cut one of those tine pieces of pcb away then the best solution by far - is just to remember to hit the power button off then back on again after every call.
good luck anyway...
I eventually upgraded to xda iis - they dont even make a car kit for it yet and the bluetooth is worse than the xda ii - im praying for improvements in a future rom upgrade...
If you're running TTN3 then the latest patch (3.07) will also fix this issue.
From the TomTom Website....
What's new or improved in TomTom Navigator 3.07
Easy installation on a PDA that comes with Windows Mobile Second Edition.
TTN3 is unaffected by an incoming call on a MDA2/XDA2/QTEK2020 or an HP-h6300 (+ Bluetooth GPS) series PDA.
Click to expand...
Click to collapse
Hello folks,
I have the same problem with tomtom upgrade 3.07. Navigator screen is frozen after a call. I mentioned this to Tomtom support site. Their answer is that it is a com port problem. They will look into this matter.
Till I've a better solution, I dedicated the function "leave application" to a hard key. When there is a phone call I press the hard key and Tomtom is finished, next I answer the call. Then, after the call, I restart Tomtom. It has very fast your existing position because your serial GPS still keeps running.
Not the best solution but it works.
Greetings,
Jean
pickles the cat said:
If you're running TTN3 then the latest patch (3.07) will also fix this issue.
From the TomTom Website....
What's new or improved in TomTom Navigator 3.07
Easy installation on a PDA that comes with Windows Mobile Second Edition.
TTN3 is unaffected by an incoming call on a MDA2/XDA2/QTEK2020 or an HP-h6300 (+ Bluetooth GPS) series PDA.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Just letting people know that the Parrot CK3000 car kit works great with my XDA2. It only uses "headset" mode, so functionality is limited, but it routes the calls through the car speakers and mutes the stereo, so that's all you can really ask.
On my Alfa, I couldn't use the standard ISO connectors, as the car has a separate amplifier in the boot, but chopping the ISO connectors off and connecting the wires separately to the "telephone in" connectors on the back of the radio worked just fine. I can even adjust the volume of the phone call via the steering wheel audio controls!
There's a reassuring "beep" when I turn on the ignition to let youknow tha the devices have bonded and every few days, something goes skewey on the PDA and I have to do a soft-reset to make the bluetooth bond work again, but otherwise, it works fine.
I've put an icon on my PDA for the warm-reset, so that I can do it easily in the car if I realise that it hasn't bonded automatically.
The only real glitch I've found is that if you get to your destination whilst still on the phone, I can't find any way to transfer the call back to the handset without terminating the call - any help on that would be gratefully appreciated.
Good to hear it works, I have a CK3300 with the BT GPS Functionality on route for review.
In asnwer to your question, to hand over the BT headset call to the phone just tap the 'Headphone' Icon on the status bar of the XDA.
Darren,
Funnily enough, I was just outside in the car experimenting when you replied.
Sure enough, if you tap the headphone icon on the PDA, the call is successfully transferred back to the PDA and you can carry on the call directly on the PDA.
If you then press the green button on the car kit, the call will also transfer back to the car kit again.
But - Here's my last issue - If you get into the car with a call already in progress on the PDA and then turn on the car ignition, the car kit beeps to confirm that it has bonded, but I can't find any way to actually transfer the open call to the car kit....
Finally - I've come to the XDA forum for a break from Pocketgps.co.uk! I usually spend my evenings on your site. Tonight, for the first time in weeks, I thought that I'd go and seek other company. Who should be the first to reply to my post here but you!
You're going to tell me now that you also drive an Alfa and that you too frequent the alfaowner.com site as well aren't you!!!
Cheers Darren.
Ah well you see we obviously share a passion for gadgets but not Alfa's, current car is an X-Type shortly to be replaced by a Discovery and yes I spend time at both of their owners ites as well (Note to self, need to get out more!).
I think I'm correct in saying that you can't hand over an active call to a BT Handsfree be it headset or car-kit, I suspect this is a limitation of the XDA's BT Stack (thanks Microsoft NOT!)
I shall leave you in peace now, you've probably had enough of my ramblings back at home base ;')
Is this the same kit: http://www.expansys.com/product.asp?code=PAR_CK3000
There is also an upgrade http://www.expansys.com/product.asp?code=FLS-KIT but it doesn't say what you get for your £45.
Any ideas?
alfiejts said:
But - Here's my last issue - If you get into the car with a call already in progress on the PDA and then turn on the car ignition, the car kit beeps to confirm that it has bonded, but I can't find any way to actually transfer the open call to the car kit....
Click to expand...
Click to collapse
Hit the green button on the carkit, that should do it.
If not, install the XDA2 Bluetooth tool, and retry...
Nope - Green button is documented as being the way to do this for most phones, but it doesn't work with my XDA2....
I did try to install Bluetooth tools ut then couldn't get the devide to pair with the Parrott at all, so I hastily removed them.....
I'll think that I'll live with as it is, now that everything else is stable and works OK....
Well, this is not really a question or problem. But just a headsup that the Diamond works just fine with my Nokia CK-7W.
However it would also be nice to hear from you guys (and girls) as well, since I can't imagine I'm the only one with succes!
You might wonder "Why the hell do you post this?!". Well, that's simple because when I wanted to find out whether that Nokia carkit would work together with the Diamond I coulnd't find anything.
And since my experiences with Nokia carkits and HTC phones weren't all that good (read: BAD, lots of echo and weird connection problems) I was pretty anxious to give this a try.
After testing it on another CK-7W, which was already built in a car, I figured it worked perfectly so I took the plunge and got one for my car.
(Before you ask, why no parrot or other brand? I was able to get my hands on this one really cheap.)
The only problem I got was the first time I wanted to pair the device. Every time after entering the 4 digit passcode I got a message saying the passcode was incorrect. Instantly, not even trying to connect. After leaving it all alone for 10-15 minutes and I tried to connect again it suddenly worked without any problems. And it's still working with no issues at all.
ROM I use:
SWIFTBL WWE DIAMOND ROM V7.5
OS Version: CE 5.2.20755 (Build 20755 AKU 1.4.0)
Base ROM Version: 1.93.405.1 UK WWE
So.. more succes stories here? Or problems?
Hi
I have the same setup, Nokia CK-7W in my volvo s60 connected to my MDA Compact IV running swiftbldade 7.5.
It all works perfect.
I even have MS Voice command setup with it and it annonuces incoming callers and messages perfectly and voice dialling works perfect as well.
Call quality is very good as well.
Shaks
Hey - I've got my CK-7W working fine too, except I'd like to also enable wireless stereo... but the option doesn't seem to exist... I bought the CK-7W off a friend, and he was able to use wireless stereo, but I cn't - has anyone else had any success...?
Relly something I want for using TomTom, etc...
Hi i have CK-7W car kit and I am having problems getting my Diamond to pair can you please advise how you guys paired your ones?
Can't say anything more than I just used the normal way to pair, go to bluetooth settings, search for device and select the carkit + enter correct passcode.
I did however have some problems in the beginning. It would find the carkit but after entering the passcode it said pairing failed.
But when I tried later again it went without a problem, and it paired everytime without a problem ever since.
I dont think the ck-7w supports stereo audio. There are however apps that can route the audio over the carkit. BTAudio is one called if I remember correctly. That way you can have the tomtom over the carkit, but quality isn't that good really.
And some say that using that audio routing also gives 'problems' sometimes, as in it sometimes seems like there is audio (e.g. the car radio is muted) but you don't hear anything for a few secs. So that can be quite annoying.
hmmm??? My diamond wont even pick up the car kit during the search!
I had some problems pairing in the first place...
Don't try to search for the car-kit using the phone, just have your Diamond on BT visible to others, and the car-kit will try to connect automatically... I think you might need to hold the button on the car-kit down for like 10 seconds for it to search, but definately let the kit find the phone, not the other way around...
I fitted one of these to my brother in law's car the other day. Tested it with my diamond, but i expected it to be cross compatible.
Bit offtopic, but what's the advantage compared with a just as pricy parrot system?
Hi Y'all,
I am using my Diamond with the nokia CK-7W and it works fine as well. Paired up without much fuss....
Riel said:
Bit offtopic, but what's the advantage compared with a just as pricy parrot system?
Click to expand...
Click to collapse
Eh.. none? I find the quality better compared to my old ck3300 parrot carkit. However, this one doesnt have a small lcd display or something. Not that I missed the lcd screen though, but sure was a nice feature.
Best thing about the parrot was that it's possible to put a new firmware on it. Could make them a little bit more 'future-proof'.
Nokia CK-7W with HTC Touch Diamond2, VITO VoiceDialer
Pairing the device was easy. In coming calls are working. Push on the carkit button and I can answer the call.
The problem that I have is that I can't do a voice call. If I push on the carkit button nothing happens. I would have expected that the VoiceDialer app would be started and I could make a voice call. The VoiceDialer app works without bluetooth.
Has anyone an idea how I get voice dialing working?
Remark:
With my pervious cell phone Motorola L6 was this possible. Pushed on the carkitt button, wait on the beep, say the name, when recognized it repeats the name and the number was dialed by the phone.
My touch pro seems to have real bluetooth issues with my JVC KD-NX5000 stereo system. My kaiser worked flawlessly with it but with the touch pro it wont pair at times and when it does it wont let me use any of the many functions that the stereo offers (voice dialing, downloaded phonebook, etc) I assume this is a problem with the ms bluetooth stack and was wondering how tough of a job it would be to switch to a broadcomm stack or if anyone has thought about making a custom rom with the broadcomm stack. Just curious if Im the only one with issues with wm 6.1 and bluetooth.
i have the same problem with my diamnd anbd jvc car audio
Slightly OT rant:-
I had the opposite problem with pioneer + broadcom...
Pioneer only looks for handsets which identify themselves as phone or smartphone, and my device identified itself as a pda.
I actually told pioneer about the problem, and rather than forwarding on to the developers, I got a stock reply:-
"This phone is not on our compatibility list" (so we don't care)
So I went and got an MS based phone (you can change it to smartphone with a regedit).
Never buying pioneer again...
- Anthony
Similiar issue with my opel carkit.
Tried to make the broadcom stack working, but got a memory error when opening its blue tooth manager.
After uninstalling, bluetooth didn't work at all anymore, needed to perform a hard reset.
Has anyone successfully installed the broadcom BT stack on the touchpro/raphael?
I found that my Touch Pro would pair and then drop out when connecting to my Kenwood DDX5032 car stereo bluetooth adaptor. I couldn't dial from the Kenwood kit, couldn't use A2DP (wouldn't even connect), and really couldn't use any Headset Profile functions at all.
I persisted with pairing and unpairing in different ways (you can initiate the pairing from the Kenwood itself rather than the phone), but nothing really worked.
Then trinode's post about changing a registry setting sent me down that track and now everything is working fine
I found the relevant setting from http://forum.xda-developers.com/showthread.php?t=290871, which is [HKLM\Software\Microsoft\Bluetooth\sys\COD], and then changed the HTC TP default value of '5898764' (decimal), to the value from my old Dopod838Pro, which was '5374228' (in decimal).
I didn't even need to repair the Kewood to the HTC TP - it just worked straight away, as if it said "Oh, sorry, did you want me to work? I thought you wanted me to be in 'stupid' mode! My bad - everything will work now."
So all good, and thanks to trinode for pointing me in the right direction.
Codenix.
After hard-resetting my Touch Pro to fix another separate issue, now this problem has come back and this time changing the COD value hasn't fixed it. It would appear my previous post may have attributed my success to the wrong thing
The search for the answer continues!
I found a firmware update for my Kenwood's bluetooth adaptor which fixed the problem. I don't know why it ever worked at all before this update, but there you go!
I'll create a separate thread to share this with others in case anyone else out there has a Kenwood bluetooth kit and a Touch Pro or a Diamond.
Thanks.
The thread I created re the Kenwood is at http://forum.xda-developers.com/showthread.php?p=2835805
@ Trinode
Pioneer sent my unit back, but never told me that my phone was not supported. Where did you flag the smartphone in the registry? Did it fix the BT connection/unti reboot issue? I had a AVIC F500BT (sold it) now have a AVIC X910BT same issue as the 500 had.
@ Trinode. I found the hack , tried it, but it still doesn't resolve my issue. Are there any other mods out there for the BT Stack prob?
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.