Had to send my early XDA11 back to O2 for repair and it came back empty and they upgraded the ROM(?) Re-installed Tom tom loads so slowly its unusable. Memory map navigator loads ok but takes 5 seconds to react to a screentap. Also, it can bond with Holux bluetooth GPS but cant see it in Tom tom wizard. It all worked fine before they got their hands on it.
This sounds to me like you have the wrong com port chosen for your gps. Remove bonds for any bluetooth, reset, then rebond the gps, it should ask if you wish to use the serial profile for the device, answer yes to this. I think gps should then be on com5.
Thanks for your help
Thanks for that. When I get to select serial profile I only get Com 7 offered. Com7 is not offered in Tom tom GPS setup. Previously I had "Holux on Com4" as a choice. I have no Bluetooth manager program as on the Ipaq but I have loaded BTHTools1100 from April04. Can I check Com port status somehow? Maybe old stuff is assigned to the serial port I need?
We have lift-off!
Unticked Com 4 as incoming Bluetooth port in Bluetooth settings. Now have "Hollux 230 on Com 7" as an option in tom tom GPS setup.
KeithR: IF your on ROM version 1.72 now, you better skip the BTH Tools.
Un-install them or do a hard-reset (yes, once more).
Just bond the GPS, select YES to create a com port.
The GPS will then communicate thru COM5
Assign COM5 in TomTom (and one of the NMEA protocols).
It will work then as expected.
BUT: Since you have a Holux GPS you miight encounbter the same slowness when starting TomTom and the GPS is not 'connected'(ie off or out-of-reach). This is an issue specifically for the combination Himalaya (or MS BT Stackin the ROM) and (some?) Holux and D-Connex BT GPS's.
It seems that this last issue is solved in WM2003 SE, but that seems less stable to me . . .
Thanks all
Now its running ok I'm going to leave it alone. (I doubt.) I'm tempted to get an XDAIIs to use with broadband and VPN at home but the MDAIII seems much cheaper. Thanks again, I'll check this site for info on it.
I've tried everything that I could find on the net but nothing helps... Maybe someone here have a solution for this problem.
I have installed TT on my Mteor and it (seams to) work fine. I have successfully paired my Mteor with a bluetooth GPS receiver (Holux GR230). But TomTom is not connecting to the receiver and sends a message 'GPS device not present'.
So... anyone? Some tips? Something that solves this problem?
Thanks!
Have you set an outgoing com port in the Bluetooth manager? - this is the extra step needed to get the serial port profile selected when using WM2005 devices.
In TomTom on the GPS status page what is the yellow / blue disk doing (top right of the screen) if its spinning it is communicating, if stationary you have a setting wrong. If it is spinning take it all outside and wait for upto 20 mins for the GPS receiver to achieve a first fix - after that it should be much faster - Mike
Which outgoing port number should I use?
One that's free to use, then select that port in tomtom.
Have just installed WM6 (JW 2.02.02 WWE) and everything appears to be fine except for the BT com port in TomTom Nav5. Have paired the BT GPS, set the outgoing port (COM0) but it doesn't appear in the list of ports available in TomTom.
Is this a known issue or have I got to set something else? Have also tried the External GPS manager in 'Settings' but that port doesn't show either.
Sheepdip said:
Have just installed WM6 (JW 2.02.02 WWE) and everything appears to be fine except for the BT com port in TomTom Nav5. Have paired the BT GPS, set the outgoing port (COM0) but it doesn't appear in the list of ports available in TomTom.
Is this a known issue or have I got to set something else? Have also tried the External GPS manager in 'Settings' but that port doesn't show either.
Click to expand...
Click to collapse
I've had the same problem.
What I've done about this, is I've added a Serial port profile for the GPS device. Then went into TomTom and the port was in the list. This port has worked fine.
Tried setting External GPS in the Settings/Connections, to share it, well - TOUGH, does not work.
So I have a working TomTom and I gave up for now about the sharing stuff...
Try setting port 8.
I'm not interested in sharing it (at the moment).
Can you explain what you mean by 'added a serial port profile'?
I've set up an outgoing com port in settings > bluetooth > COM ports but it's not seen by TomTom
tyl said:
Try setting port 8.
Click to expand...
Click to collapse
I must have tried all the ports that were available but none of them show. All I get is the standard TomTom list: -
QCT Data Interface
Serial Cable on COM1
COM7
RIL on COM6
Infrared Port
Ir on COM3
and of course non of those work either.
Sheepdip said:
I must have tried all the ports that were available but none of them show. All I get is the standard TomTom list: -
QCT Data Interface
Serial Cable on COM1
COM7
RIL on COM6
Infrared Port
Ir on COM3
and of course non of those work either.
Click to expand...
Click to collapse
Exactly where you wrote it, in COM ports.
Then I've selected "Other Bluetooth GPS receiver" as receiver type in TomTom 6, and here's what I have:
COM5:
QCT Data Interface
Serial Cable on COM1:
COM7:
RIL on COM6:
Infrared Port
Ir on COM3:
COM4:
COM5 is my attempt to share GPS which is failing so far, so disregard it for here (but I'll try COM8 later). COM4 is the Outgoing Bluetooth port and that's the one I selected.
I must admit that I honestly don't understand why this setup works for me. I expected to put Incoming port number (a common for all devices) there, but obviously didn't have it.
Hmmm, that's strange. What you have is exactly what I used to get in WM5 but it doesn't seem to work in WM6? I'm also on TT5 so that may be an issue?
From what I can see, the 'QTC Data Interface' is the GPS sharing port and is actually COM9, installed by the OS. But it doesn't work!
Frustrating............!
I'm also getting tons of memory leak by the looks of it.
SORTED!
Feel a bit stoopid. Checked the version of TT5 and it showed 5.0. Upgraded to 5.21 (which is what I thought I installed) and bingo! Com port shows and works.
Thanks to all who made suggestions.
Sheepdip said:
Feel a bit stoopid. Checked the version of TT5 and it showed 5.0. Upgraded to 5.21 (which is what I thought I installed) and bingo! Com port shows and works.
Thanks to all who made suggestions.
Click to expand...
Click to collapse
Man, my TomTom is version 6.010.
Just in case, it's available.
put in External GPS the program port on 8.
then you will see com 8 in TomTom.
connect it in TomTom and after that change the program port back to none and hardware port on 8.
problem solved.
I've had this problem on a Mini S, Exec, Vario II.
Some times just removing TomTom and re-installing it seems to work. On several occasions the correct COM port shows up in TomTom. I honestly don't know why. It seems a bit random.
Airax said:
I've had this problem on a Mini S, Exec, Vario II.
Some times just removing TomTom and re-installing it seems to work. On several occasions the correct COM port shows up in TomTom. I honestly don't know why. It seems a bit random.
Click to expand...
Click to collapse
I have seen some recommendation to not select Bluetooth receiver. I don't know, I thought it would be un-cool So I made it work with Bluetooth receiver.
EastExpert said:
Man, my TomTom is version 6.010.
Just in case, it's available.
Click to expand...
Click to collapse
I know, but the old TT5 maps won't work with 6 and I've got quite a few that don't come with the Europe disk.
solution to tt gps connection problems
hi everyone with this problem,
no matter what your setup is vario, xda, dell, tt5 or tt6, tomtom gps or other GPS try this method (it does bloody work) :
STEP 1 : INSTALL TOMTOM5 OR TT6
You do this by copying the CAB files from the CDROM using JasJar or using SD card o any other way
STEP 2 : UPGRADE (THIS IS NOT ESSENTIAL, ONLY DO IT IF YOU HAVE A NON-HOKY COPY OF TT)
http://www.htcclub.net/storage/ppcupd510.rar
or just overwrite patched version of main executable file over original
also having this install on some vario 2 may also help BTHTools1100.
STEP 3 : ACTIVATE THE GPS CONTROL PANEL
this is hidden option but if you use this wisely you will take control over your GPS but in many cases this is reson why tt sometimes works sometimes doesn't.
Fire up a registry editor (eg http://www.freewareppc.com/utilities/phmregistryeditor.shtml )
Go to: HKEY_LOCAL_MASCHINE\ControlPanel\GPS Settings
Delete the DWORD marked "hide"
Add a DWORD called "Group" and give it the value of "2" (dec)
The GPS panel will now show up in your connection settings.
STEP 4 : INSTALL TOMTOM
1. Establish a bond with your GPS and select the checkbox for serial access.
2. In BT, select the OUTGOING port to 8. (optional: make it non secure if available)
3. In the GPS control panel, select the GPS program to 0 and make sure that the hardware one, is set to None, also you should pay attention to 3 tab and allow windows to manage it - for now, you don't really want Bill managing things as it is recipe for disaster.
4. Start TT and the GPS settings, select another bluetooth GPS, and you will see COM 0 free. Select COM 0 and close TT5. (if you don't get the port go back one step and check 3 tab)
5. At the GPS control panel again, now select COM 8 (before we set it up at 0).
6. At BT: select OUTGOING port to 0.
7. Back again to GPS control panel and select NONE.(and now is the right time untick 3 tab option and stop auto managing)
8. Finally start TT and it should connect automatically. Wait for a couple of seconds and click the GPS settings and you should see it has connected.
Congratulations
well, in case something didn't go well start from scratch - reset your software restore your registry and reinstall as much as you can get back to factory defaults using hard reset and etc.
I know this is is in bits available elsewhere but this is more complete and little bit more up to date, but there is still hundreds of people looking for this.
THE SUMMARY
I've spent many many days looking for solutions, registry and web and all sort of tools to solve this, but this method works the treat - and it does make perfect sense - I suspect the reason why this is such a problem is timeout. windows is not a good platform - and it is locked by ms and all sorts of legacy issues. Obvious reason is tt doesn't load quickly enough and and detecting correct port seem to an issue so if you follow instruction you will see that sulotion is guiding your software to speak with 3party hardware having windows in the middle
good luck
Paulius - Excellent instructions and they work just great.
However....For me it only works one time. By that I mean after I turn everything off and then want to use it another time - it again cannot see the GPS device - and I have to do all of the above again.
Do you know why the settings are not retained? Note; I have unticked the the stop auto managing option already.
Hope you can assist.
Paulius - Excellent instructions and they worked fine but only the first time unfortunately for me.
i.e the next time I want to use tomtom - i have to go through all of the above again as it cannot find the GPS again.
Have you come across this before. Note: I have done exactly everything you have instructed above
Tomtom loses GPS settings
Paulius - Excellent instructions and they worked fine but only the first time unfortunately for me.
i.e the next time I want to use tomtom - i have to go through all of the above again as it cannot find the GPS again.
Have you come across this before. Note: I have done exactly everything you have instructed above
I had the same problem.
Luckily I had a backup of my TomTom installation.
It all comes up to the navigator.cfg file inside the Navigator folder. I copied the old one over and did not enter TomTom's GPS Setup menu anymore.
All I did after flashing was to just pair my BT GPS receiver and start TomTom. One needs to wait 5 seconds or so after the main screen opens, until the GPS is found. Do not try to select the receiver in the settings menu!
This happend on both my devices (BA and UNIVERSAL) after installing a WM6 firmware WITH the GPS Manager in the Settings.
Cheers,
vma
Thanks VMA - I understand.
Did you setup an outgoing port though in Bluetooth?
reply to nsm
hi nsm, sorry it took this long to respond, I didn't know the solution to your problem.
However, after few gliches with my pda's I think I can add to the list of thing to go wrong.
First is WM itself sometimes causes problems - so before you do anything else turn it of and on again - it did happen to me in the middle of london and I come from Lithuania well, it can be good fun navigating through canary warf without gps - aim for tall buildings :-D or away from them.
Second is once you followed my original instruction do not go back to gps settings menu, because after this you will have to start again from begining.
Third - is do allow minute or few for gps to lock onto satellites - especially if you are in doors or between buildings. Once in Crete it was quite hard to find satellite signal because of a mountains and I had clear sky view to one direction - but as you drive especially bigger cars, metal body will block signal.
Fullproof recipe is to have two units, if possible for one of them use bluetooth separate gps module as this will allow you to place both gps unit and pda screen in ideal locations for satellite signal and driver.
Fourth - this is boring and can take a lot of time, but may resolve lots of weird issues. Follow my instructions and then you set your tomtom to use data transfer baud rate 4800, 9600 and etc do try all the options - from low to high rate, this means that every time you'll have to start again instructions from beginning. TT6 on some of my pda's prefers 56700, tt5 - 4800 and so on. give this some time explore all the settings.
And finally if you have stability issues check your pda memory limits - try not to push it to 90%+ on unit or memory car, best is to leave plenty on both, this may cause settings not to be saved and all sorts of bugs.
the practical advice is to keep selling and buying pdas till you find one which will do the job for you, Try ebay , but do check descriptions and guides and most important sellers rating! All pda, mda and nokia simbion phones I tried with enough effort will work but many many of them have issues with stability or are difficult to setup.
Hope this helps.
Good luck
I have a bluetooth GPS reciever and i want to connect it on COM port 9 but in the bluetooth settings it only allows me to use 6 or 7, does anyone know how to change this?
Im using the HTC Vox if that makes a difference?
Thanks
When you say "Bluetooth settings" are you referring to the settings in the GPS software (TomTom, Garmin etc) or are you referring to the bluetooth settings in your phone settings?
When you first pair your device with the external bluetooth device, you need to set up and outgoing port (COM5 on a Himalaya, not sure what Vox would use) and also go to the advanced bluetooth settings and chose "serial connection". The com port should then appear in your GPS software bluetooth selection choices.
Let us know if this helps.
Ports :S
Thanks Jadel for the reply, i was referring to the bluetooth settings in the phone not gps software. i have paired it and and selected serial port and then it gives me a selection of ports to use: 6 or 7, but i already have things connecting to those ports and want to select another one to use? Any ideas?
http://www.geekzone.co.nz/content.asp?contentid=2417
the guide may not be using the latests wm version but still it should
give you a clear picture as to where on the PC you handle the activesync comports
rather then on the pda which dont use comports for activesync at all
So I picked up an external GPS receiver off ebay. It's the Globalsat BT-359C (http://www.usglobalsat.com/p-214-bt-359c.aspx). Turned it on, everything went fine as far as my fuze finding it. I'd goto add new device, it'd pull up "BT-GPS371D88", i'd select it, put it the four "0" 's, and it'd give me the message "your pocketpc is now connected with BT-GPS371D88". It comes up in the list but under disconnected. So i'm like eh whatever, and setup the outgoing com port to COM0 as per the instructions, and make sure its unsecure.
I go back to devices, highlight BT-GPS371D88, click it. Check off "Serial Port" in select services to use, and save. Then heres where everything goes wrong, I hit connect, and it gives me the following message "Your device did not connect with BT-GPS371D88. The connection failed or the passcode is incorrect." I've been tinkering with it all day, searching various forums to no avail. Even downgraded my 6.5 rom to 6.1 thinking it was maybe incompatible with something so new.
Now i'm stuck, I really want to get it working so i can use it for a trip thats coming up in a few days. Has anyone else had such a problem? is there like a quick fix that i'm over looking, or is it simply not compatible with the fuze? I managed to get it paired up and connected fine to my blackberry curve just to see if the gps unit was defective (did buy it off ebay). Any Ideas guys? Not sure where else to turn now.
Oh yeah btw my current rom that i'm using is
At0mAng Fusion Power V 5.X ROM Series
Windows Mobile 6.1 (Build 21051 1.6.4)
Located @ http://forum.xda-developers.com/showthread.php?t=537501
jimshepp said:
So I picked up an external GPS receiver off ebay. It's the Globalsat BT-359C (http://www.usglobalsat.com/p-214-bt-359c.aspx). Turned it on, everything went fine as far as my fuze finding it. I'd goto add new device, it'd pull up "BT-GPS371D88", i'd select it, put it the four "0" 's, and it'd give me the message "your pocketpc is now connected with BT-GPS371D
Click to expand...
Click to collapse
have a BT GPS for my Dell axim x51v, got some trouble too getting it to connect, but eventually did
here are some pointers:
1) Delete all pairings and com port pairings on the device
2) Pair the device (make sure that you put 'request authorization' or something... this ensures that you need to put the 0000 code to connect)
3) you need to set up at outgoing port on your device, to the BT GPS... COM 8 is norm
4) External GPS setting in the Start>Settings tab
hardware port is where you put the outgoing port in (3)
software port is where you put for your GPS software... COM4 is norm
third column where WinMo will manage GPS, say yes
This worked for me:
I have a Hermes (WM6.5) with a holoux bluetooth GPS, but the GPS was not connecting for me properly either. It seems to be a problem with the way WM6.1 pairs with bluetooth devices.
I managed to get mine to work without reflashing by downloading this alternative bluetooth manager:
http://forum.xda-developers.com/showthread.php?t=353774
Hope this helps.
Not trying to bump up an old thread for no reason, but I figured this info would be helpful for people utilizing searches.
After lots of research and frustration the past week I have gotten my external GPS (USGlobalSat BT-368i) to work with my HTC Fuze! Below are the steps I followed that have worked for me. Note that I still have the phone configured to use the internal GPS if the program is set to "Let windows manage GPS settings".
1. Pair the device using Bluetooth.
2. Under the devices tab select your external gps device, and check the box to use "Serial Port". Then choose Save.
2. Under the Bluetooth settings choose "COM Ports" tab.
3. Choose "New Outgoing Port", and then select your device and click next. Choose your port and preferred "secure" option. Then click Finish. (I have configured mine to use COM0 & Secure Connection)
The device will still show as "Disconnected", and you will not be able to connect it under the Bluetooth manager. It will give you an error saying unable to connect.
To use the external GPS device you can simply select the outgoing port you configured above in your program, and most likely you will use a baud rate of 4800. Once you enable the GPS in the program it should connect itself via Bluetooth to your device and begin using it.
You should also be able to configure it to automatically use your external GPS instead of the internal one under the "External GPS" settings, but my current ROM has the hardware portion of External GPS manager broken @ the moment. Therefore I have not configured this, and cannot confirm it.
Hope this helps someone!