Related
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 need to connect 2 bluetooth devices to my polaris, one to use as a phone handsfree and the other as stereo speakers.......
no problem there you say, but, they will both be identical devices with the same device names. and both capable of both headset and wireless speaker profiles.
does anyone see any problems with this?
i have connected many different bluetoth devices at the same time but never 2 of the same device.
given the way the simplest things can go wrong i was hoping that someone here might have already done this and could tell me if it worked ok or was a disaster!
thanks
I don't think this is a problem for the pairing. I once used an identical PDA for a couple of weeks. I restored a backup of the old PDA on it, so it had the same name. I hoped it would be paired to all my BT devices, but it wasn't. I had to pair them all again. So I think there is more identification than only the name.
thanks that sounds good.
does anyone use both headset and wireless speakers over bluetooth?
i am hoping that the phone will go to the headset and all other audio (TomTom, Mp3) would go to the speakers....... has anyone had this working ok?
also does ayone have 2 of the same bluetooth device that they can assign different profiles to?
i am concerned that although i set 1 as headset and the other as speakers as they are the same device they may swap roles depending on which connects first
i dont know if this is an issue but if anyone is able to test this for me it would be a huge help
lol ok strike that! just found out from the manufacturer that although the dongle has the wireless stereo profile its only wired for mono!
so can anyone recomend a good Bluetooth stereo reciever
Hi All
I have just had to send my orbit 2 back to be fixed.
My company gave me a Nokia for a couple of weeks in the interim and I love that when I switch on my bluetooth headset, a window pops up on the phone telling me it has connected my headset.
My connection remains until I switch the headset off, when another popup on the Nokia tells me it's off.
Does anyone know why w.mobile phones don't do this? Is there an app out there that can help. My headset drops all the time, and when I switch it on, it doesn't always connect to my orbit !!!
Any ideas
I suppose you HAVE applied BT patches from HTC?
Which type of BT headphone are you using? If it's Nokia, it's known that some of their models are not compliant with BT standard and use some proprietary stuff. Therefore they work good only with Nokia phones (and vice versa). But that goes for older models...
Thanks Bodisson - no, I haven't applied any patches and my BT headset is a Jabra JX10 Series 2.
Do you have a link to the patches at all (sorry if that sounds very lazy !!!!)?
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?
I've noticed these similar (and likely related) bugs in a lot of places and have been living with them for six months, but I have never seen a fix. Surely there are others with this issue that might be able to fix it.
Issue #1: When you connect a Bluetooth stereo headset to a Windows Mobile device, using the Wireless Stereo AND Hands Free profiles, the wireless stereo feature works fine, but when attempting to answer a call, hands free fails. The hands free icon shows on the Phone screen, no audio is heard, and after a few seconds the headset shuts off and the icon goes away.
Issue #2: When you connect a Bluetooth stereo headset to a Windows Mobile device using the Wireless Stereo profile and are watching video in Windows Media Player, if a call comes in, the program device.exe crashes and Windows Media Player will often need to be restarted. Device.exe will often crash at other times as well.
I have seen numerous reports of this problem, and near universal reports of it on the Dell BH200 Bluetooth Stereo Headphones. It seems to require A2DP, and be very common among HTC devices. I have had the same problem on the AT&T Tilt (Kaiser) and AT&T Fuze (Touch Pro/Rafael) under Windows Mobile 6. I can confirm the headset works as it is supposed to on Palm OS (Palm Centro) in headset mode, and that it was also able to work as a headset on the T-Mobile MDA (Wizard) running Windows Mobile 5 (which does not support A2DP).
In all cases, I am talking about devices using stock ROMs.
If you have seen the problem, please list the device, OS, and bluetooth device used. If you have a bluetooth stereo headset that does not exhibit the issue on devices that are known to have this problem, list that as well, so owners of devices with this issue can consider alternative headsets.
If you have any technical knowledge of what causes the issue, please share it. If you have heard of any workarounds, please share it.
Thank you all.
I have the Samsung i-640 running WM6 and have the same issue with The Dell BH200 not doin Hands free mode and the whole shut down of device happens too ..very Frustrating .
I tried using the Nokia BH 100 which does only Mono [Hands Free] and i get $hit loads of static noise but the Device doesnt Shutdown.
Heya, I have the AT&T Fuze and I also own the BH200. I have the same exact issue you have (issue #1). I have no idea why it does this but I've been trying to get support from dell for the longest time with no luck.
I think the problem lies in the MS BT stack. It does an automatic pin guessing thing which might cause the bh200 to not work properly. I have tested the fuze on the BT2020 (by Jabra) and it works perfectly. I just recently bought the moto s9 (still waiting for it to arrive) but I would prefer to use the dell bh200 if possible.
Check my sig for the information you're looking for.
Dell sends you to PC support when you try to get support on the device, since it's usually sold as an accessory with computers, but they refuse to offer actual support on the actual device, as though they knew nothing about it or how it works. I asked them if it was a rebranded version of another company's headset, and they wouldn't say.
I tried to get help from dell already, and they're as much help with it as telemarketers...
Similar problem
Maybe this is a stereo headset bug...
Maybe this is designed behavior, but it is typical of why people HAVE to hack the crap out of WM to be happy with it:
I have a ATT Tilt.
Behavior same under WM6 and WM6.1
I have a Jabra BT610s (stereo headphone with A2DP, AVRCP, handsfree, & wireless stereo profiles).
If the Tilt is paired with both wireless stereo & hands-free, then even if Win Media is running or playing, the hands-free profile is selected when powering on the headphones. Then, the stupid ATT Bluetooth settings are so buried that it requires about 30 secs of sylus picking, poking, and prodding to get it set to wireless stereo.
Is there a way to set the Tilt to default to wireless stereo, is there a helper app for quick-switching this?
Also, there are not infrequent dropouts in audio over bluetooth, even with the phone setting on the desk 24" away from the headphones as I type this.
All the remote control features DO work with this setup, but unfortunately there's no remote control function for profile switching.
Thanks,
I am using a stock ROM and I don't have the above problems. I am using a motorolla hb820 headset. I also use an LG Style i headset, and no problems either. I use Core Player and it plays fine even after a call. I only use WMP to play music and my X7510 haven't froze yet while playing music when a call comes in.
Hi
I am using Lg KE590 but I am not using the device so I have not gone through the problem. Is it for all the handset ?
John
Don Joao Resort
I have several configurations with problems to report below:
1) HTC P3600i (WM6 stock ROM) + Dell BH200 => issue #1 (never try issue #2)
2) HTC P3600i (WM6 stock ROM) + Dopod HS01 clip-on BT stereo headset => All functions work fine, no problem switching between profiles
3) Dopod S300 (WM5 stock ROM) + Dell BH200 => stereo music & phone call works but music switch back to the phone after end of a call
4) Dopod S300 (WM5 stock ROM) + Dopod HS01 clip-on BT stereo headset => All functions work fine, no problem switching between profiles
5) Nokia 5610 Xpress Music + Dell BH200 => All functions work fine, no problem switching between profiles
6) Nokia 5610 Xpress Music + Dopod HS01 clip-on BT stereo headset => All functions work fine, no problem switching between profiles
Summary: I tend to believe that the problem is specific to Dell BH200 and some of HTC's or WM OS combination as Dell BH200 works fine with Nokia phones and Dopod BT headphones always work with any phones we have.
Reporting in, Im using Motorola S305 Stereo BT. No above issues whatsoever with 2 devices HTC Kaiser and Touch Pro. Both with stock or cooked ROM. I have a strong feeling its related to hardware prob on Dell BH200.
I have a touch pro that refuse to play nice with my AVIC-D3 head unit...I must pick either headset profile or wireless stereo profile, but not both. I remember coming across a solution called a2dptoggle. It let you switch between the 2 easily (in wm agenda page), but try it out to see if that's a solution or not.
Issue #1 using HTC Touch Pro and Dell BH200
Because of that issue i can't use the hands free function at all.
Only way i can use my headset is:
If i uncheck Hands free from partnership settings, then an incoming call mutes headset, i take out the phone have my conversation manually, after hangup the music plays on.