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
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....
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 cannot start using my navi kit for many days because of one problem: I leave BT GPS receiver outside for at least 20 hrs to initialise, connect to device regularly, run NAVIGON and get always the same message - "A GPS receiver has been detected, but a convinient GPS signal is not available. The reception is obstructed, or the receiver is being initialised."
Any idea what to do?
Slaven, it could be a faulty receiver, do you have a program for viewing the signal and number of sats being received? It maybe also that the settings are wrong for the gps, what is the model of receiver you are using and details please of how you set it up when bonding etc. Have you carried out a factory reset of the receiver also? One other thing, sometimes a gps reciver will work much better for initialising first time if it is mobile rather than static, put it in the car and see if you have any results after a mile or 2. Try this program to test the gps function.
Please check your PM I have sent one to you. thanks.
I`m using BT GPS receiver delivered in original kit with Navigon 4 (made by GNS). I`ve bonded them regularly (XDA II asked for code and I entered 0000 - as described in operation manual). I have not performed factory reset of GPS rec. because don`t know how to do that. I couldn`t find any possible way to do that, except to remove BT and TMC moduls and I have done so.
Thank`s for gpsdiag, but I don`t know hoe to connect BT GPS with my notebook (with built in BT) to test it. Only service available is to connect it to serial port, but couldn`t. As you can conclude, I`m not very experienced with this, so I need really DETAILED help! Thank`s in advance.
Sorry, I sent the wrong version of diag, I will pm you the proper file.
The BT version of serail port on qtek is not compatible with wildcomm BT (used by navigon) got to navigon website and download the wildcomm patch
this will solve your problem
I was using navigon with wired gps and then tried bluetooth which dropped signal and refused to reconnect, thanks for the link I will try it.
I have the Kenwood DNX8120 and it works fine with my Fuze (did have disconnect issues but just updated the Kenwood firmware which should take care of that) but the SMS feature on the radio doesn't work. I know only certain phones are compatible with this feature but on the Kenwood compatibility list there are several HTC devices that work. In any case, does anyone know how to enable SMS over bluetooth on the Fuze?
Thanks
I have the Kenwood DNX8120 in my car and have had no luck getting the Fuze to work correctly. It constantly drops connection. I updated the Bluetooth firmware and that only seemed to make matters worse. It will pair with the Kenwood, but either won't make a phone call or will take up to 60 seconds (or not at all) for the Fuze to recognize I it the call button on the radio. SMS, sent and received call history also do not work.
Have you had similar issues?
I can not get sms working. The only other issue I have is that after a call, it drops the connection. If I get another incoming call, it will reconnect and the radio will ring and handle the call. But, if I want to place a call, I have to either select "set as hands free" of something similar, in the bluetooth settings on teh phone and it reconnects and I can dial. I just upgraded to elite rc3 and the problem is still there. I havn't messed with it enough yet to know if it dials ok without having to bring the phone out of standby yet. I too have updated the bluetooth drivers from Kenwood and that didn't help. I also tried the jetware handfree extension and didn't see any improvement.
I called HTC about this, and they told me it only "officially" supports a hand full of car units. Mostly in the Audi and BMW. They don't "officially" support anything from Kenwood so they were absolutely no help on this. I've also noticed this phone drops all connections except cell and data when it sleeps. Wifi, GPS and Bluetooh all seem to go to sleep with the phone. This seems to make bluetooth pretty useless if the connection drops every time the phone sleeps and needs to be manually reconnected.
I haven't seen it drop the bluetooth connection during sleep. I see that the Kenwood supports some HTC devices but not this one specifically. The other wierd thing is that the first time it pairs it shows the battery indicator but after the next connect it doesn't show it. It shows the battery icon but shows it empty. The jetware extension however does fix that. I will play some more with it and report here.
After resetting my phone to AT&T's original setup, I am experiencing the exact same functionality as you. It now sync's my call history and phone book. No voice dial support or SMS yet. (These have never worked with any of my phones) It will disconnect after a couple phone calls and I have to set as hands free to reconnect. Also, mine still looses the connection to the unit when it goes to sleep. I'm keeping it on a car charger for now and turning off any sleep function when charging. That at least keeps it connected until I make a call. It's almost still not worth using with having to reconnect hands free. Maybe if a hands free quick connect shortcut could be created?
This is all really ridiculous that a phone with this kind of tech can't auto pair and be ready for a call. My LG Chocolate had absolutely no problems with the Kenwood. As soon as the Kenwood finished booting the LG would auto connect and be ready for a call.
I thought I found a workaround at
http://forum.xda-developers.com/sho...ghlight=bluetooth+connection+drops+phone+call
But, once installed an trying to run BT Restart I get an error saying that I need .net compact framework (version 1 or 2) installed. Not sure what to do now, cant seem to find a cab for this.
I've used this package from another post on the forum. It has many useful apps including the latest version of .net compact framework.
http://www.tyguy.net/_xchg/PPC/@essentials.rar
Let me know how it turns out!
I will take a look but I have 3.5 already installed. I guess that app needs the older version. Not sure I want to mess with downgrading it.
Not Kenwood
Hey Guys,
I drive a Jag XK8 and it has the same issues you are mentioning with your Kenwood, but its an Alpine unit, it drops calls, and after the first call connects the second call rings on the stereo but you can only answer on the handset.
I also recently had a new Jag XF for a week. It had a full integration to the phone. It also only showed the battery status when the phone first connected then the battery showed empty. It would drop bluetooth connections constantly on some days (every 90secs) and then somedays it would keep the bluetooth connected without issue. Very unreliable.
The reason I bring this up, is just to let you know these issues are not limited to the Kenwood.
Dave
Just an FYI. I have found it easier to just go into setup in the Kenwood and reconnect the bluetooth from there when the phone disconnects. It's under Setup/Bluetooth/Set, then just click on the device and hit connect. It seems easier than fiddling with the phone while your driving.