I've been having a discussion with TomTom support over the last few days regarding a problem with getting my Mini S to talk to a BT GPS Receiver and a BT HF kit at the same time. Tomtom have basically told me this won't work and that whilst Tomtom is installed - not even running, the phone will not work with a BT HF device....!!!! :?
Anybody else experience this? Are Tomtom saying that their software basically renders the phone useless with handsfree??? :shock:
I've included the conversation from Tomtom below :-
Note the entries are in reverse order.
Response 06/07/2006 01.34 PM
Dear Mr. Kirby,
Since your PDA does not have any physical serial interface, a wired GPS-receiver (which runs through a serial interface) will unfortunately not be possible.
To further clarify our statement, your PDA seems to have difficulties sharing the same BT connection port and/or profile between multiple devices or services. This has nothing to do with our software, this is hard-coded into the operating system and hardware your PDA runs on. The binding of a BT serial port is a PDA function, not a software function.
We sympathise with your situation, but as we are not the manufacturers of your PDA or your carkit, there is very little we can do to assist you.
Kind regards,
The TomTom Customer Support Team
Customer 05/07/2006 10.01 PM
Does this mean that if I use a wired GPS receiver then this will work? Or, are you telling me that once I install the Tomtom software on a PDA phone that I will loose the ability to use any other Bluetooth devices until the Tomtom software is removed? If this is the case then I can hardly see how you can claim compatability with the XDA series of devices, at least without notifying potential customers that they will loose all handsfree functionality via Bluetooth once you install the software?
Response 05/07/2006 02.12 PM
Dear Mr. Kirby,
Our earlier correspondence was unfortunately not entirely clear. What we mean is that there is an internal conflict between our software, which is bound to the PDA Bluetooth Serial Port by the PDA hardware and underlying Windows OS), and your BT Carkit, which attempts to pre-empt the BT Serial Connection bond. This bond is enforced whether or not the program is actually active, and the ability to share a bound serial port concurrently is something that is enforced by your operating system.
This is unfortunately not something we can do anything about, since this is both hardware- and Windows-based (in the sense that multiple programs cannot access the same serial port concurrently), and also because we cannot provide technical support for a problem that is outside the purview of our software.
Kind regards,
The TomTom Customer Support Team
Customer 04/07/2006 10.10 PM
Your answer makes the assumption that the problem only occurs when the Tomtom software is running. This is not the case. Before Tomtom was installed on the device it would connect to the carkit and work correctly. Following the installation of Tomtom it will no longer remain connected for more than 15-20 seconds, regardless of whether Tomtom is running or not. If Tomtom is running and communicating with the BT GPS receiver it does still not function correctly with the carkit, however, if the Traffic function is activated then it will maintain a connection.
I therefore suggest that your previous explaination is not accurate - I could possibly accept an issue with Tomtom running and it then disconnecting from the carkit however, even with the BT GPS receiver removed from the paired devices and switched off it will still not remain connected.
Response 04/07/2006 01.29 PM
Dear Mr. Kirby,
Since we do not support the usage of third-party carkits (Bluetooth or wired/serial), we are only able to offer a technical theory as to your problem.
As your carkit is connected with a (virtual) Bluetooth serial connection, there is most likely an internal conflict with regards to the serial connection. PDA's support multiple Bluetooth profiles (methods of connecting), but typically bind the serial port to one device. Seeing this, the most likely culprit is the fact that the PDA keeps on switching focus between the two devices that use the serial port: Your BT GPS-receiver and the BT Carkit. When Navigator 5 is running, it pre-empts the serial port connection for the GPS-receiver, which forces the connection to stabilise.
Though we cannot offer you a solution to your problem, please try changing the settings of your BT Serial connection (removing the Authentication and Encryption options).
Kind regards,
The TomTom Customer Support Team
Response 03/07/2006 08.25 PM
Dear Mr Kirkby,
The incident you reported is escalated to our 2nd Line Support Technicians for further research. We will notify you immediately when they have resolved the incident.
Thank you very much for your understanding.
Kind Regards,
The TomTom Customer Support Team
Auto-response 02/07/2006 11.25 PM
Title: What is GPS?
Link: http://service.tomtom.com/cgi-bin/uk.cfg/php/enduser/popup_adp.php?p_faqid=3250&p_created=1119876697
Title: How to check the status of your order?
Link: http://service.tomtom.com/cgi-bin/uk.cfg/php/enduser/popup_adp.php?p_faqid=993&p_created=1120286100
Title: How do I install NAVIGATOR 5 Software and Maps of Western Europe on my Pocket PC?
Link: http://service.tomtom.com/cgi-bin/uk.cfg/php/enduser/popup_adp.php?p_faqid=4164&p_created=1139482444
Title: Will NAVIGATOR 5 (and previous Navigator versions) work with Windows Mobile 5?
Link: http://service.tomtom.com/cgi-bin/uk.cfg/php/enduser/popup_adp.php?p_faqid=3447&p_created=1128340851
Title: Why should I sign up with MyTomTom?
Link: http://service.tomtom.com/cgi-bin/uk.cfg/php/enduser/popup_adp.php?p_faqid=2411&p_created=1102928847
Customer 02/07/2006 11.25 PM
GPS Driver 1.2, MAP Great_britain_Plus-Map v571, English UK
Windows Mobile V5.0 OS 5.1.195 (Build 14847.2.0.0)
ROM - 2.21.4.1 WWE
ROM 3/9/06
Radio 02.07.10
Protocol 413.1.03
ExtROM 2.21.4.101
I have recently upgraded from a O2 XDA II to an O2 XDA Mini S. The product has been working perfectly for a number of days with my Vauxhall(Opel) Vectra Bluetooth car kit. The phone will pair with the unit, the contacts are downloaded etc and the phone will remain paired and make/receive calls via the bluetooth unit until switched off.
Yesterday I installed TOMTOM (Details above) onto the main memory and the GB maps onto the storage cards. The software was activated and my Plus subscription reset for the new device.
TomTom works OK on the device and the traffic information is updated as expected. With TOMTOM running, a route active and traffic information active the phone will maintain a connection with the bluetooth car kit. However, if a route is not active and therefore the traffic information is not active, the phone will connect to the bluetooth carkit and then disconnect after around 15-20 seconds. If the carkit is forced to reconnect it will but once again it will disconnect after 15-20 seconds.
If tomtom is not running, when I go to the phone dialer screen, when I force the phone to connect the headset icon is visible again for 15-20 seconds but then disappears when the phone disconnects from the carkit.
Presently the only way I can keep the phone connected to the carkit is to ensure that tomtom is active with a route and traffic updates switched on.
As stated previously this behaviour only started when tomtom was loaded on the XDA Mini S. Presently there is no way to keep the phone connected via bluetooth unless tomtom is running as above. I am using a Mk I Tomtom bluetooth GPRS receiver.
Tomtom was patched using the updated software as downloaded last week.
I have tried various combinations of resets/ re-pair/ delete device etc on both the carkit and phone. The problem still remains.
Strange, I am using TOMTOM and a Samsung HF kit and it works fine. Automatically cutting the sound from TOMTOM when I make and receive a call and then turning it back on when the phone is not in use.
The only, very minor, glitch is that on call termination there is a maybe 2 second loss of satellite signal.
I am using the Qtek Rom BTW, and the latest TOMTOM GPS drivers.
IIRC you ned to be using 5.21 versions of TOMTOM and drivers.
I have to say, I understand what TomTom are trying to say and agree. Because you've got the COM port set up in Windows, it doesn't matter if TomTom is open or not. I guess you could try deleteing the COM port in the Bluetooth settings and seeing if that solves the problem; then you will really know if it's a Windows problem. It's interesting that trevor.austin's car kit works fine; again seeming to point towards the fact your car kit has some problems with the way Windows handles having a com port set up.
How would I delete the com port? Do you know if there are any cabled GPS receivers about for the XDA Mini S - I guess then I would only be using bluetooth for the car kit?
Hi akirkby,
I also have a BT Carkit. I have the Parrot CK 3100.
I paired BT Carkit and the Emtac BT GPS.
With the BT GPS i need to assign the ports. With the carkit i didn't needed.
He recognized the carkit as a headset.
I think TomTom is right and i think the problem is in the Carkit
When i start TomTom, bluetooth also start automatic and then he nicely connect to mine BT Carkit. And when i shutdown TomTom he also disconnect.
What carkit do you have?
Did you check the IR module? If "allow incoming beams" is on?
You sometimes get some trouble when it on.
When i installed TomTom for a friend that was the problem.
When it was on it wouldn't connect to the wired GPS.
Maybe you should also check the site of your BT Carkit is there is a software update.
The Parrot CK3100 has software to flash your carkit over bluetooth.
Maybe your carkit support that als well.
Can you tell me what carkit you have?
akirkby said:
How would I delete the com port? Do you know if there are any cabled GPS receivers about for the XDA Mini S - I guess then I would only be using bluetooth for the car kit?
Click to expand...
Click to collapse
No, unfortunately there are not any wired GPS recievers compatible with the Mini S... That I know of.
Delete the COM port to test by going to Comm Manager -> Settings (Right hotkey) -> Bluetooth Settings -> COM Ports -> tap and hold your GPS COM Port -> Delete.
There does not appear to be a COM port in the list. Under Bluetooth ports all I have are "New Outgoing Port" and "New Incoming Port" - nothing else?
Try setting outgoing port 6 to BT GPS and then tell TomTom to use port 6, make sure that your TomTom is 5.21.
akirkby said:
There does not appear to be a COM port in the list. Under Bluetooth ports all I have are "New Outgoing Port" and "New Incoming Port" - nothing else?
Click to expand...
Click to collapse
That's interesting. What GPS are you using?
Its the Tomtom GPS unit - not the latest one, about two years old.
TomTom
If you have "New Outgoing Port" - then create one - try tapping and holding - you should have the options..... it will probably create an outgoing com port on Com6..
You are probably only missing this step..
Also, check that the name you have for your GPS actually ends in "GPS"
Charlie Grillo
[email protected] - the carkit is a factory fit option supplied by Vauxhall - I can't find much info about it on the web :-(
I've added a new outgoing com port - it did suggest com 6. I'll try this and let you know what happens.
Ah that makes sense. When you have a standard TomTom GPS, it doesn't need a COM port, I think TomTom does that for you... which is probably the problem. If you pair the GPS and the phone, create the COM port as you have done, and set TomTom to use the "other bluetooth gps" on the COM Port you set up, it might well work, and not kill your other bluetooth connections.
I paired the BT GPS before Tomtom was started - during pairing it says that the device has a serial port - do you want to use it. I tried saying Yes & No at this point and then adding a new outgoing com port.
Both times it will fail - Tomtom is configured for 'Other' BT receiver on COM 6.
Not sure what to do now.... is this the fault of the Car Kit Manufacturer, XDA or Tomtom? Effectively as soon as Tomtom is loaded on the device then it can no longer be used handsfree...
it should work as use a bt headset and a bt gps all the time with mine and have set up numerous othe miniS's for freinds at work .
have you tried com7 as the outgoing port the handsfree will use a bt profile
it could be a compatiblity issue with the hf car kit as not all bt protocols are the same.
Hello,
paired with a CK3100 parrot and a globalsat GPS works like a charm
Set the outgoing COM7 to the GPS MOUSE!!! and then it works!! dont ask me why!
SO com6 in and com7 out using the GPS mouse bluetooth as the device!!!
Let me know...
Hello,
paired with a CK3100 parrot and a globalsat GPS works like a charm
Set the outgoing COM7 to the GPS MOUSE!!! and then it works!! dont ask me why!
SO com6 in and com7 out using the GPS mouse bluetooth as the device!!!
Let me know...
Tried both com 6 and com 7 as outgoing ports. Port 7 worked until I stopped tomtom - restarted it and then the carkit stopped working again.....
Related
Hi there guys, its been a while since posting but I have some great news regarding using multiple bluetooth devices in the car.
A few weeks ago I purchased a Navman 4410 GPS unit for my XDAII. With the new "72" rom the Navman worked perfectly with my XDAII straight out of the box over bluetooth.
Today I installed a Sony Ericsson HBC-30 bluetooth hands free carkit (Which also worked perfectly out of the box). I was interested to know if I could have the GPS unit operating and have the handsfree carkit working at the same time.
I was simply sitting in the carpark, with the GPS connected and onscreen, then I used my other phone to call my XDAII... the call came up on screen (interrupting the GPS screen) I pressed the "answer" button on the Sony Ericsson handsfree kit, and the call came through perfectly!
Once finished with the call I pressed the "hangup" button on the handsfree kit, and then a few quick taps on the screen returned me to the GPS navigation screen.
Certainly not perfect, however it appears that the bluetooth issues are finally getting resolved, and allowing us to begin using the XDAII as it was intended.
Hi Colonel, thanks for your update, it is comforting to know that they are finally sorting out BT problems.
Is there any way to get the phone screen to automatically close after finishing a call? so I don't have to manually close it to get back to my GPS screen?
No I dont think you can. Not without altering the GPS software to continually make sure its "on top" of other windows... but then you'd have a problem with seeing the "incoming call screen" as the GPS software would try to jump on top of it.
I'd be so happy simply if I could make HCB30 and Blutrek G2 headset work side by side on my Qtek...
points are:
1-where coul i get that da***n 1.72 rom for my xda 2
2-where could i get the g2 HS in italy(even worlwide...) or all over the web at reasonable price
help a newbie...
Kolonel,
I can confirm your experience as far as BT GPS is concerned.
I however still have one issue to solve: When the MDAII (=XDA2) can't connect to the GPS (BT off, GPS off, GPS out of reach) and I start TomTom3, TomTom3 keeps searching for the GPS which results in a almost freezing MDA2.
Using rom 1,72 from Qtek I bonded the BT GPS and confirmed the question about assigning a com port.
In TomTom I assigned this (COM5) com port.
All works fine except for the issue mentioned.
Does this sound familiar?
Clues?
BTW in the BT settings screen there is nothing shown about the assigned com port (just free space next to the two lines that should indicate the in- and outbound com ports). I found COM5 to be assigned to BT by trial and error . . .
edsub said:
Kolonel,
I can confirm your experience as far as BT GPS is concerned.
I however still have one issue to solve: When the MDAII (=XDA2) can't connect to the GPS (BT off, GPS off, GPS out of reach) and I start TomTom3, TomTom3 keeps searching for the GPS which results in a almost freezing MDA2.
Using rom 1,72 from Qtek I bonded the BT GPS and confirmed the question about assigning a com port.
In TomTom I assigned this (COM5) com port.
All works fine except for the issue mentioned.
Does this sound familiar?
Clues?
BTW in the BT settings screen there is nothing shown about the assigned com port (just free space next to the two lines that should indicate the in- and outbound com ports). I found COM5 to be assigned to BT by trial and error . . .
Click to expand...
Click to collapse
edsub,
Are you using "Bluetooth Tools"? Because I am not, i'm using the native bluetooth stack only.
I am using "Outbound" Com port 5 ONLY for my GPS. My 1.72 rom is the IMATE rom.
Im afraid that i'm not familiar with tomtom. So I cant help you there, sorry.
I am deliberately only using native MS bT stack.
I am only using COM5 for GPS too
What does the BT Settings show under
"Bluetooth Serial Port Setup"?
With me:
"Outbound COM port" checked, but after the colon is a "<not present>" shown.
"Inbound COM port" UNchecked, after the colon is a grayed-out "<not present>" shown.
Like i said I AM able to use the GPS via COM5.
Maybe this issue is a pure TomTom issue, I think your answer could clarify that.
edsub said:
I am deliberately only using native MS bT stack.
I am only using COM5 for GPS too
What does the BT Settings show under
"Bluetooth Serial Port Setup"?
With me:
"Outbound COM port" checked, but after the colon is a "<not present>" shown.
"Inbound COM port" UNchecked, after the colon is a grayed-out "<not present>" shown.
Like i said I AM able to use the GPS via COM5.
Maybe this issue is a pure TomTom issue, I think your answer could clarify that.
Click to expand...
Click to collapse
Edsub, thats really weird... mine is:
"Inbound COM port:" UN checked, and after the colon is a grayed out "COM4"
"Outbound COM port:" checked, and after the colon is a black "COM5"
bluetooth
hi guys
im using imate 172 and tomtom 3 with a sony ericsson hb35 it works first time all the time with the standard stack. it works that good i even went and sold my carkit and just got a hold instead :lol:
@Kolonel Klink: I guessed it's strange. What ROM are you using exactly (OS & Extended).
I use the 1.72 Qtek rom with my own Extended Rom (wich is based on the Qtek ExtRom to which I added T-Mobile Nl customisations). I am sure there is nothing regarding Bluetooth in my ExtRom.
I heard from someone who uses the iMate 1.72 OS Rom (with his own cooked ExtRom) that he has the same results as you have.
Just trying to find to cause of this. Maybe I have to reflash to the iMate 1.72?? (shouldnt make a difference as both iMate and Qtek OS ROM's are the same 1.72.00WWE . . . .)
@freelockuk: Most interesting is the origin of your ExtRom. Arent there any Bluetooth enhancements in that ExtRom (like there were in the 1.60.36 T-Mobile NL ExtRom) that maybe make your 1.72 work better than mine concerning Bluetooth?
addition to prev post:
I noticed that there were two BT registry settings missing to get the assigned COMport show in BT Settings.
Also noticed another interesting value:
[HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dun]
With me this one is:
"port"="BSP9:"
In prev versions it was:
"port"="BSP4:"
Can anyone with a 1.72 ROM that has a BT GPS mouse working via SPP AND who can start Tom Tom without the BT GPS mouse 'connected' post their setting of this key??
Okay, i've not cooked my own extended rom. I'm using the stock standard one from iMate.
I did find something odd today. I went into an IT expo and I turned flight-mode on. When I was finished I left and turned flight mode off. Then got in my car. I tried to make a call and it didnt go thru the handsfree kit.
Weird! I had to repair the device. So I did... and it all worked fine again. So I turned flight mode back on then off, and I ended up with the same result. It appears to lose the pairing when you turn the flight mode on.
Very odd!
I still have not found a solution to the behaviour where TomTom locks up the MDA with is isnt able to connect to my BT GPS.
Today I found out that this same behavious accurs on devices (not just MDA, HP too) that use a serial (wired) GPS when they take the current off the GPS . . .
That means:
1. TomTom Navigator can't cope with the situation where it cant connect to the GPS that is installed
2. With me TomTom navigator is not able to use the Bluetooth protocol on its side to cope with the (for Bluetooth GPS quite usual) unavailability of the BT GPS.
Again: Can anyone post me some info on this :?: :?:
Especially the registry items under
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\SerialPort]
[HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dun]
[HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dcn]
are of interest
@ Klink
Thanks for sharing your experiences, I'm watching them with interest.
Just wanted to as you about using your navman and the headset at the same time.
In your first post to this topic, you mentioned your 'carpark' test. I assume you weren't moving at the time, so the navman wasn't trying to give you directions.
What happens when you're driving along, getting instructions (ie. "turn left in 300m") from your navman, and the phone rings? Does the navman stop giving directions while you are talking on the phone using your BT handsfree? When you hang up does it resume giving directions again?
Thanks,
Hooligan
Emtact Trine BT GPS, Bluetrek G3 BT Headset
Like all of you my exprience is that it all works together.
But I've one problem. When navigating with TomTom and there is a incoming phone call and when I accept the call with my headset TomTom continues navigating but the sound of my QTEK2020 is muted during the call. So the instructions of TomTom cannot be heard.
I'm using plain MS BT Stack.
Regards,
Mark
This behaviour seems not the be dependent of the use of a BT headset. I have a carkit and during a call TomTom stays active in background. Sound of TomTom is muted however, which I find nice.
When the phone call is ended, TomTom starts talking again.(also nice)
first of all my nevigation program works great with the jabra 250 bt , it also mutes the program during a call is madeqreceived but :
there is anothe program that is called "ontime" that sends trqaffic status to the imate, using the gprs andthen calculates the fastest root( from junction to juction) and the problem is:
if i want to use buth progtams with royaltek gps bt rbt1000 they both need the com5 port fot bt.
to solve this problem one can use a prog called: "gpsgate" which makes a virtual port for the programs to use so u can use several program with one bt device.
for some it works only with bt tools, for others it doesnt work at all, gos knows why?!
but - if any1 needs a solution - here is one.
have a nice day , spark
QTEK 2020 - 1.72.00 WWE - 1.06.01
Back Pack - jabra 250 BT- royaltek rbt 1000 GPS BT - DESTINATOR3(LIKE TOM TOM 3) - soon will recieve sd 1gb*40
Spark, where did you get 'gpsgate'??
here is the link
http://franson.biz/gpsgate/download.asp
When I first tried installing this stack (see here: http://forum.xda-developers.com/viewtopic.php?t=33532 ) my exisiting bluetooth devices - a Jabra BT200 headset and Ambeon GPS both worked, just like that - without re-pairing, the latter with TomTom3.
However, in order to make stereo over A2DP to work I had to hard-reset and reinstall everything. Glad to say A2DP did work! However took opportunity to upgrade from TomTom3 to TomTom5.
Now I've re-paired with the GPS using the new stack, during which it asks if I want ti install a serial port. But it doesn't seem to be recognised by TomTom. And, if I go to the COM tab, and try and add a new port there is nothing in the drop down.
Any ideas?
The BT outgoing port on my magician is fixed at Com5. Maybe because I am using GPS Gate (a program to create virtual Com port so that U can open 2 or more GPS program at the same time), I don't have any problem before and after installing that BT stack.
Maybe U can try GPS Gate too. Just open Com5 in GPS gate and create an virtual port Com6. Then ask TT to connection to Com6.
Thanks but it's all OK
I used this great little free program
http://www.teletype.com/downloads/tty.zip
to test whether the GPS box was actually connected (but not recognised by TomTom) and it was - on COM5!
So I pocked around with TomTom some more, and found that it could pick up a signal on COM5 but if a signal was not there it reported that 'No GPS device' rather than 'No valid GPS signal.'
upgrade tomtom 5 to tomtom 5.1 :wink:
GideonS, did you get BT outgoing port to show up? If so, how? Like you, when I try to select one, it comes up with a blank selector box.
(Maybe I missed something in the thread, but the GPS Gate surely relies on diverting an existing port?)
thanks in advance!
Re: Thanks but it's all OK
GideonS said:
I used this great little free program
http://www.teletype.com/downloads/tty.zip
to test whether the GPS box was actually connected (but not recognised by TomTom) and it was - on COM5!
So I pocked around with TomTom some more, and found that it could pick up a signal on COM5 but if a signal was not there it reported that 'No GPS device' rather than 'No valid GPS signal.'
Click to expand...
Click to collapse
my tt5 5.21 (5430) + iberia plus 6.3.2 don't recognize my Socket GPS (http://www.socketcom.com/product/GP0820-521.asp)
i used that program you mencioned and it receives data on COM8 as defined by me
i'm at home and i never get a fix inside so i can't test if it's the same situation of the error messages switch
when i do, i'll post the result
Hi all,
Just go the xda through work, and even though i have got the new version of tom tom of their website (5.2) for ppc, when loaded and docked in my cradle, it cant sem to get the GPS to receive!?!?! anyone else had this problem?
I have an O2 XDA Exec and its working fine with the TomTom 5.2 software. I got some very useful info from http://www.pocketgps.co.uk/modules.php?name=Forums&file=viewforum&f=6 ..... basically a post on there advised setting up an outgoing com port to the BT GPS device (I used Com0) ... this is found under Start>Settings>Connections>Bluetooth>ComPorts (after you have paired the BT device of course).
In TomTom you then select "Other Bluetooth GPS" in the GPS options screen, select the Com port set previously, and away you go.
I hope this helps
I bought a 32-channel QStarz GPS receiver from eBay, cracking little thing it is. I had problems getting it going though initially - what I had to do was setup a pairing, which was a little tricky as TT didn't want to behave.
Basically, TT tries to establish a serial connection whenever I open it. As TT loaded, just before it went into the TT interface, It showed a dialog box with all my serial connections in - I think it might've been the device pairing screen, but I've not been able to find it again... What I did was pick the gps receiver's serial port device entry I'd previously set up, select it, check the box to tell TT to always connect to this device by default, and then hit enter - all before TT managed to load into the interface. It took me a couple of goes, and I'm sure there's an easier way to do this (I don't think I was even supposed to see this dialog screen ) but now it works perfectly. I don't have to establish the Bluetooth connection to the GPS receiver, TT does that (and it'll even turn the Bluetooth on and off if it's not already on for me). However, I did have to choose Other NMEA GPS from the device options, and then tweak my COM port settings (I found a scant piece of information regardingthe fact that it should be something like COM5 for incoming data and COM6 for outgoing data, you would do well to doublecheck the TomTom site's FAQs for this info). There's a couple of seconds lag whilst TT correctly detects the device and begins to latch onto GPS sats (it says "No Compatible GPS Device Detected!", and then changes to something like "No GPS Signal Detected"... And then starts picking up sats.
This is all with TT5.0, by the way.
This document will be very useful.. principal is the same for most GPS Receivers..
http://www.parrot.biz/ressources/CK3400_Help_Files/Imate JASJAR - TOMTOM Mobile 5 - 2.01.pdf
Not sure if you are trying to receive through a Bluetooth GPS receiver - if you are, this worked for me (first poston the page);
http://forum.xda-developers.com/vie...ostorder=asc&highlight=tomtom+5+gps&start=100
Thanks for your help guys, but i meat to say i am using a wired GPS the small square official Tom Tom one, hard wired in to my cradle.
I can open the software and everything, but it just says, cant find GPS, the green light flashes on my GPS, but thats all it does.
Help!
Ok, so you're using a wired receiver.. That helps to know. You should be able to choose TomTom Wired GPS or Other Wired GPS, and it should just... work. If it doesn't, choose the nearest chocie to your receiver, and go into the Advanced settings (if the option button is available) - if so, doublecheck what your COM port settings are.
Where did you buy the cradel from, I just got ripped off to the tune of £48 off ebay due to the cradle not actually passing the srl connection through, all it does is provide power for a Bluetooth GPS Receiver out of the port on the side.
I think I've heard othe rpeople saying that wired GPS receivers will not work with the Universal. Can anyone confirm this?
What you have heard is correct the mini USB on the Exec WILL NOT accept a GPS connection, you need a bluetooth device for this to work - Mike
Tony B - that sounds like the cradle i am using - jasjar or jamjar something like that!
I have put my wired GPS straight in to the side, and nothing!!
think you might have got it mate!
hi there
i am using the wired gps with mda pro tomotm car cradle
tomtom software working like i can start the tomotm and see the setting etc
now when i connect the tomtom wired gps via rj11 in cradle but i can not recieve gps signal
device says "no gps device"
please help
Regrads
Gugi
Hello All,
I have today noticed a problem with my XDA Mini S following the installation of TT 5.21 - Before the software was installed the phone would pair and remain connected with my Vauxhall, factory fit, bluetooth carkit. Calls could me made and received, phonebook info would sync with no problems - all 600 entries!
Following the installation of TT5.21 the phone will now disconnect after 15-20 seconds from the carkit unless TT is running with an active route and the TT Traffic updates enabled!!!
Trying to make a call without TT running means that it only presents on the phone and does not go though to the car kit. Even with tomtom running, unless you have a route planned and TT traffic active then it will still disconnect from the carkit...
I have posted a question to tomtom technical support regarding this and will also try O2 tomorrow to see if they have seen this before...
Anybody else seen anything like this?
Andy. :?
Silly question - is the bluetooth on constantly on the Mini S? If not you need to do this.
TomTom switches bluetooth on automatically if it isn't on already, if you have a BT receiver selected, which I assume you have.
Its not a silly question - I thought that this was the problem to start with but even with Tomtom running and talking to the GPS receiver, it still disconnects from the car kit unless tomtom traffic is active and you have an active route... :? :?
No updates from TT Support yet :roll: - i'll post when I receive something.
Tomtom support came back today with the following response - reading it, it is obvious that they have not understood the problem...I have written back to them pointing out the fact that it also disconnects even when Tomtom isn't running - Only way to get it to work is to have tomtom traffic running - maybe something in that... ;-)
Since we do not support the usage of third-party carkits (Bluetooth or wired/serial), we are only able to offer a technical theory as to your problem.
As your carkit is connected with a (virtual) Bluetooth serial connection, there is most likely an internal conflict with regards to the serial connection. PDA's support multiple Bluetooth profiles (methods of connecting), but typically bind the serial port to one device. Seeing this, the most likely culprit is the fact that the PDA keeps on switching focus between the two devices that use the serial port: Your BT GPS-receiver and the BT Carkit. When Navigator 5 is running, it pre-empts the serial port connection for the GPS-receiver, which forces the connection to stabilise.
Though we cannot offer you a solution to your problem, please try changing the settings of your BT Serial connection (removing the Authentication and Encryption options).
Kind regards,
The TomTom Customer Support Team
Hi,
I seem to be having a problem with GPS bluetooth related connections with my Dopod 838 Pro.
Ive paired my Globalsat BT338 receiver and setup an outgoing serial port on my Dopod, and I can use Destinator 6 and TomTom 6 fine (for the time being).
The next day/time when I try to start the GPS applications, both programs report that they cant find the GPS signal/receiver even though its been correctly configured to work previously.
I then have to enter the Bluetooth settings to change and assign another outgoing serial port and reconfigure the GPS applications to the new serial port to work.
The programs and the GPS receiver worked fine with my old iPAQ hx4700 so its not a receiver or program issue.
I'm at my wits end and would appreciate any info on solving this problem.
Thanks in advance.
Delete / unpair your GPS
Make a new pair, and when you assign an outgoing COM port, use a NON secure COM port.
(Deselect the checkbox)
This should work
Rik_053 said:
Delete / unpair your GPS
Make a new pair, and when you assign an outgoing COM port, use a NON secure COM port.
(Deselect the checkbox)
This should work
Click to expand...
Click to collapse
Hi,
Ive been through this unpair / pair scenario more than a few times and Ive never used a secure com port connection.
try destinator PN 6
also make sure you pair BEFORE starting Destinator PN; I spent a whole two days before I Got this to work ... then once it worked .. the answer was actually quite logical
sorry cant remember how i did it as it was months ago when I got and paired my tytn; now I use destinator pn 6
njay22 said:
try destinator PN 6
also make sure you pair BEFORE starting Destinator PN; I spent a whole two days before I Got this to work ... then once it worked .. the answer was actually quite logical
sorry cant remember how i did it as it was months ago when I got and paired my tytn; now I use destinator pn 6
Click to expand...
Click to collapse
Hi,
The pairing has been done before any program was launched.
Im trying with both destinator 6 and tomtom 6
Bluetooth GPS Woes...
Is it the Bluetooth connection you are having problems with or getting a GPS signal. I have this exact setup working fine. What I notice is that often it will take a few minutes for the BT-338 to find enough satellites to provide a GPS signal (green light flashing). The bluetooth should connect immediately regardless of whether the GPS signal is available yet. The blue light on the BT-338 should flash twice as fast as when you first turn it on to tell you that it is connected to a Bluetooth device.
I am using TomTom 6 and it will say no GPS signal or GPS signal lost XX seconds ago. Is this similar to what you are noticing?
clearwave1 said:
Is it the Bluetooth connection you are having problems with or getting a GPS signal. I have this exact setup working fine. What I notice is that often it will take a few minutes for the BT-338 to find enough satellites to provide a GPS signal (green light flashing). The bluetooth should connect immediately regardless of whether the GPS signal is available yet. The blue light on the BT-338 should flash twice as fast as when you first turn it on to tell you that it is connected to a Bluetooth device.
I am using TomTom 6 and it will say no GPS signal or GPS signal lost XX seconds ago. Is this similar to what you are noticing?
Click to expand...
Click to collapse
Hi,
Both the bluetooth reciever and the software work fine and obtain a fix.
the next time the software is started it cant find the reciver and i have to unpair, repair and set a new comm port for it to work.
the gps reciver obtains a fix but the pda cant see it.
Destinator PN has an automatic reconnect tick box on the GPS Settings page. I don't know if D6 or TT have a similar thing. If so, make sure this box is ticked.
I use D PN with a Parrot CK3300 combined handsfree and GPS receiver, and after major stuffing around trying to get D PN set to the correct port initially, it has worked fine since.
Ive sorted the issue out and hopefully this will help others experiencing the same problem.
The problem was that although an outgoing serial port was setup, for some reason it was not mapped to the bluetooth device.
It just specified "COM9" instead of having the bluetooth device "BT338(COM9)" under the bluetooth COM Ports setting.
This seems to be the reason why when the device was unpaired/paired and a com port setup it worked for the time being. After the bluetooth device was disconnected the settings mapping to the device were not retained.
Rambler76,
I am looking to get a GPS unit for my Dopod 838Pro. Which of the two, Destinator or Tom Tom, do you like best?
I know where to get Destinator 6 in Sydney, where does one get Tom Tom 6?
Rambler76 said:
Hi,
the next time the software is started it cant find the reciver and i have to unpair, repair and set a new comm port for it to work.
QUOTE]
Can I ask, with a new com port being asssigned each time you have a problem, when you run out of ports what happens?
Are you able to regain the use of these once assigned ports ? by resetting any settings ?
Does this make any sense?
Thanks for any input ..
Click to expand...
Click to collapse
killabeezz said:
Rambler76 said:
Hi,
the next time the software is started it cant find the reciver and i have to unpair, repair and set a new comm port for it to work.
QUOTE]
Can I ask, with a new com port being asssigned each time you have a problem, when you run out of ports what happens?
Are you able to regain the use of these once assigned ports ? by resetting any settings ?
Does this make any sense?
Thanks for any input ..
Click to expand...
Click to collapse
hi,
what i mean to say is that i switch com ports.
the issue was resolved by mapping the com port to the bluetooth device.
Click to expand...
Click to collapse
Yes I understand what you have done but can I ask again :-
Are you able to regain the use of these once assigned ports ? by resetting any settings ?
Thanks,,
Tom Tom Woes
Hi,
I had the same problem until recently.
To fix I did the following:
Delete pair with GPS receiver,
Create new pair with GPS receiver (put in passkey 0000)
Tick the box for Serial Port
The in Bluetooth Settings -> COM Ports tab, I clicked 'New Outgoing Port'
Selected the GPS unit, and selected Port 4 and unticked the 'Secure' checkbox
Now open TomTom, Select Change Preferences, then Show GPS Status, then Configure, then Other Bluetooth Receiver, then Select COM 4.
Now TT works as it should - turning on and off Bluetooth on Open/Close, and no problems with needing to re-pair.
Previously I had always paired the BT GPS on COM 0 with Secure ticked. This worked the first time only, and I had to re-create the same pair each time I wanted to run the app.
Hope this helps some of you.
(btw I was using TT6 when I found the solution, but I imagine it would have worked for 5 too)
dopod bluetooth problems
Guys I have the same problem with my bluetooth and my dopod. It connects then disconnects.
I have also noticed that the systems unchecks the turn on bluetooth check box and the make this device discoverable to other devices.
Does anyone have any ideas?
Guys I just read this at another forum.
"The Dopod 838 pro and WM5 have chronic problems with the bluetooth stack, which is why everyone is waiting for the new ROM to appear, which will hopefully be WM6. HTC (manufacturers of Dopod 838 pro) announced that the new ROM will fix all of the known problems"
This I learn after having a car accident (minor) in my car playing with the bluetooth and trying to get it to work. Hutchison 3g should only be selling these with a warning.
I assume there is also a problem with the JasJam as they are the same phone.
Knight__Mayor said:
Hi,
To fix I did the following:
The in Bluetooth Settings -> COM Ports tab, I clicked 'New Outgoing Port'
Selected the GPS unit, and selected Port 4 and unticked the 'Secure' checkbox
Click to expand...
Click to collapse
Have to concur with Knight_Mayor. Was having trouble getting a signal/satellite fix using a Holux GPSlim236. Then I set it to COM9 with the "Secure" box unchecked. I had barely closed the window and my M3100 had a fix from inside my house! (tomtom 6 had been running in the background whilst the adjustments were being made)
dabs1 said:
Have to concur with Knight_Mayor. Was having trouble getting a signal/satellite fix using a Holux GPSlim236. Then I set it to COM9 with the "Secure" box unchecked. I had barely closed the window and my M3100 had a fix from inside my house! (tomtom 6 had been running in the background whilst the adjustments were being made)
Click to expand...
Click to collapse
yeah i recon its the screwy MS bluetooth stack, im interested to hear from anyone running tomtom on hermes with the widcomm bluetooth
Tomtom And Gps
I have found that the best cure for gps woes and pocket pc is to use GPS Gate. It make a virtual com port and will always be the same. I have used it always and never have problems connecting.
G