Dear Sir,
Thank you for your email dated September 17, 2005. To connect the (TOM TOM) GPS system to your device, you need to connect it as a device with navigation facilities and not as a headset. Once you have found the device via Bluetooth on your Imate, tap and hold on it to connect and then access the services. The services will be mentioned and then you need to click on “next” and proceed further with the configuration. After having done so, open the software for the GPS system and then try accessing the same.
Please find attached the Bluetooth Tools for enhancing the Bluetooth capability on your device. Please install the attached file by connecting your device to your laptop/ computer and simply running the file from the laptop itself which will automatically be taken on to your device. Pocket Bluetooth Tools adds the missing Bluetooth functions. This version includes:
· Support for Bluetooth Headsets and Car kits. You may use up to 9 devices at the same time and you do not need to bond the again.
· Support for the SSP profile (serial port), e.g. for GPS receivers or modems
· Support for ActiveSync (synchronization with Outlook and Internet connection)
· Switch Bluetooth on and off automatically
The "Today" screen
The icon on the left activates or deactivates Bluetooth. The clock symbol switches automatic power off for Bluetooth on or off. When activated (white background as in the picture) then Bluetooth will be switch off after 60sec of inactivity.
The two battery icons on the right side let you switch between two profiles for auto power off of the PDA and the back light. For example you may switch to the second mode and adjust the settings to "always on" and "never switch back light off". Thereby you can switch the PDA with one simple to "always on" when you are in your car and want to use GPS navigation.
However, please note that we do not guarantee the usability or functionality of any third party software/hardware with our device and the use is upon the sole discretion of the user.
Regarding the Clubimate user name, please note that this cannot be changed. Should you have any further queries, please do not hesitate to contact me.
Best regards,
Joyce D'souza
Technical Support Specialist
i-mate ™ by Carrier Devices
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Saturday, September 17, 2005 2:36 PM
To: Support and Contactus
Subject: Club i-mate Support Request : (Blue Tooth and Tomtom)
Received : 9/17/2005 2:35:55 PM
Blue Tooth and Tomtom
________________________________________
Subject : Blue Tooth and Tomtom
Name : michael
Message : Jasjar absolutely refuses to work blue with tomtom GPS. Any ideas on the continual Bluetooth disaster?
Hmmm, doesn't seem to do anything at all.
BT 1012
I agve not used these since XDA 2 days, way in the past, but you should have more options available to set com ports etc, and the icons should appear on your desktop, (Unless Clubimate reallly sucks)
Nothing on desktop. BT settings are exactly the same as they were before.
Not sure what they are on about TBH. The JASJAR already supports handsfree, BT serial and BT Activesync. :?
BTTools
Hi mikeycollins13 and rilot,
Agree with you both, I can´t see any diference after the install apart the option of choice a com port. Very sadly the com port don´t show to the other aplications. It worked on the XDA II. Hope that guy Tobias read this posts. He make the Bluetooth tools.
Regards
JoseF
same as xda2 install delete all pairing then soft reset and repair you should get a serial port when pairing the gps
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
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
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.....
I have purchased the i-Geo Polstar and having problems with the setup. I have and Motorola XDA2 and Running TomTom 6.00. The XDA2 bonds with the Polstar but registers No GPS Device on my PDA. I have it set at – OTHER BLUETOOTH GPS RECEIVER - and connected to BT on Com 6 I get this error - Please establish a Bluetooth Connection between your GPS Receiver and you device. For details, see the documentation for your GPS receiver and your device. I have followed the instructions to the letter but just get error saying NO GPS DEVICE. The device is in the bonded Bluetooth list. I have spent a day on this one now and it’s driving me mad!
Regards Danny Blue
I have read loads of threads re bluetooth and GPS most of which seem not so recent. Turned of and on incoming beams.
Have you PAIR the GPS device with the XDA before starting the TomTom, if not then close the TomTom and search the Bluetooth device from your XDA, once its been found, pair it with the pairing key (usually 0000), once pairing is done, then try the TomTom.
GoodLuck
Sidd
Yes It is paired with device, it shows up in bonded devices but not in TomTom
Important:: Start->Settings->Connection->Beam and Switch-Off (un-tick).
1. Make sure that your XDA's bluetooth is OFF mode before to start the TomTom.
2. Then select "Other Bluetooth device-->Com port 6 (once you click on ComPort 6 notice for the BLUE light to lit-up) now your TomTom should minimise and the Bluetooth Browser should open for you to select the already paired bluetooth GPS device".
3. Select your already paired device and TICK-ON "always use this selected device".
Try point 2 on "Bluetooth com 5" if com 6 doesnt work.
Let me know
Sidd
Sidd YOU are a Star!
Yes I followed your instructions and BINGO it came to life. It worked on COM 5 Many thanks and if I am appearing anywhere near you please email me and I will sent you a couple of tickets, Kind Regards Danny Blue
www.dannyblue.co.uk
Not a problem, GoodLuck Danny & enjoy your journeys, by the way I am living in London, Middlesex, Pinner.
Sidd
I have just purchased a Qstarz BT-Q818 GPS Receiver and I am attempting to use this with my Tmobile Vario II.
I do not appear to be establishing a BT connection.
I turn on the GPS receiver and then turn on BT on the Vario II and proceeed thru the pairing process. The Device iBT-GPS is found and I appear to pair to as the passkey of 0000 is recognised. I select "Serial Port" from the list of Services and then have selected COM8 for a New Outgoing Port.
At this point the Bluetooth icon on the receiver is flashing every 5 seconds implying it is in power saving mode. (is this no BT connection?)
I start GoogleMaps and select Track Location (GPS). A message appears "GPS Starting" and then I receive an error page stating the GPS Device cannot be found'.
I have re-paired the Receiver many times, the unit is fully charged. I have no other BT devices paired.
I've done a search and see that many people are successfully using a QSTARZ receiver with TomTom. is the issue with GoogleMaps or more basic with Bluetooth pairing itself.
Any help will be much appreciated.
It's Google Maps
I have just got the Qstarz BT-818 and am very happily usining it with TTN 5.21 on my Vario II. Very Very happy with it in fact - I get 8-11 Sats whilst the receiver is in my glovebox!!!.
I've never managed to get GoogleMaps to recognise my either Qstarz or my previous BT GPS.
One thing worth mentioning is that COM8 is the one the Wireless modem uses. So if you want to use the Wireless Modem pick any other COM (I use COM4).
Vodafone 1605 and iBT-GPS
Hi Mike,
Did you have any luck with the Bluetooth pairing ?
I just received my iBT-GPS receiver this morning and cannot get it to work at all. The Bluetooth side seems to be in sleep mode (1 flash per 5 secs). If I turn the iBT-GPS receiver off and then on again, it goes into permanent blue LED mode (no BLuetooth link established) and the GPS (orange LED) locks and starts to flash. If I turn on the Vodafone 1605 the blue LED starts to flash at the sleep mode rate (1 per 5 secs) and the GPS (orange LED) lock goes out and stays out. I never seem to get the Bluetooth active mode where the blue LED flashes at 1 per 2 secs. Yet the Vodafone 1605 says the iBT-GPS device is in the paired list ? Set at COM 0 both in BTS and in GPS Program Port on Vodafone 1605. Also set manually to 112500 bauds. The manual says that during pairing I should be offered an 'SPP Slave' option from the PDA device. With the Vodafone 1605 I am only being offered a COM Port selection. Is that the issue here ?
Anyone out there using the two devices working happily together ? The user manual refers to a piece of iBT-GPS GPS receiver test software - but says nothing about what it is called or where to get it. I somehow suspect the iBT-GPS receiver is working OK but there is some handshaking issue between it and the Vodafone 1605 - or Windows Mobile 6 Professional ??
Thanks,
Richard
It's now OK
No reply - so I'll reply to myself and maybe give some other user some help in the process.
It's now working. Seems that if I used 'auto configuration' of Com ports from within the GPS application software (GPS Tuner) and also used the 'Stop/Start GPS' from within the software, then it 'kicked' the receiver into operation.
All is now OK and the combination of Vodafone 1605 (running Windows Mobile 6 Professional) and iBT-GPS receiver works fine.
Hopes this helps someone out there.
Regards
Richard (zorpie)