I installed WM6 (nbd.v9.0) on my HTC Wizard (it used to be a T-MOBILE MDA)
When I install IGO, it connects to 1 satelite max. And mostly it doesn't find any at all.
I use a GPS mouse from KEOMO which is connected to gate 7.
I have all settings as it used to work with WM5.
Has anyone got any experience or idea how this might be caused?
If you cant reply here, please reply to [email protected]
Thanks on forehand!
Related
Why is it that the Holux driver does not appear in the Tomtom list of available drivers. Can't seem to install anything from the CD driver supplied with the GPS receiver. Does anyone have any ideas?
Thank you in advance.
I got this from the tomtom website and posted it here a few weeks ago.
If you are thinking of buying TOMTOM 3 please read this from the TOMTOM website.
Compatibility
- Not compatible with Holux GPS Receiver
- Not compatible with Integral Compact Flash Cards
- Not compatible with CF Type II cards (Microdrives)
- Not compatible with TomTom II Maps
I got mine working with tomtom 2 by downloading bluetooth tools patch but havent tried it with tomtom 3.
I decided to give it a try. if you have the gps already bonded make sure you delete the bonding first. Download and install the latest bluetooth tools from here
http://bluetooth.i-networx.de/index_e.html
Set bluetooth to discoverable mode, choose "new", it will find the gps, enter code, mine is 6268, when you ok it, bluetooth tools should pop up, I chose serial/com4. Once complete, make sure bluetooth mode is "on".
Go to tomtom, choose "gps", go to the lower box where you should now see your holux gps listed, choose this then tick the large box on the left. You should now have a working tomtom3 system despite what it says on the tomtom website about it not working. :shock:
cruisin-thru said:
Once complete, make sure bluetooth mode is "on".
Go to tomtom, choose "gps", go to the lower box where you should now see your holux gps listed, choose this then tick the large box on the left. You should now have a working tomtom3 system despite what it says on the tomtom website about it not working. :shock:
Click to expand...
Click to collapse
howdy.
ive got myself a holux gr230 which of course isnt listed as a supported device, but once bonded its visible in the lower box, but it wont connect. what should i select in the upper box?
im also having probs with tomtom activation. it says its activated, but when i try to go into uk maps it just says that "this activation code is not valid for Great_Britain" but the majour roads of europe version seems to work fine. ne ideas?
Cheers.
Smiley
I am using the DCONNEX DC-230 BT GPS, which is in fact a rebadged Holux GR-230.
Flawlessly.
I use Rom 1,72 with native BT stack.
Just bond the GPS, say YES to questions on assigning a COM port
In TomTom select NMEA Bluetooth and COM5
Only issue is that TomTom alsmost hangs the MDAII when it cant find the GPS (ie. GPS off, BT off, GPS out of reach).
Still looking for a solution for that . . .
I have the same problem that TOMTOM hangs. This is very annonying as sometimes I would like to check the Map in TomTOm without having my Holux Mouse with me. I then have to use TomTom Wizard to uncheck the little box in gps setting and then change to simulator :?
Before I was using BluetoothTools and TomTOm worked also fine without a GPS Mouse for a Map, but Bluetooth Tools introduced a considerable lag (looking for bluetooth headset) of the XDA when taking a call, this was also very annoying as I use the XDA2 primarily as a phone, and the phone has to work perfect ....
Greetz
WELL I'M USING 1.60 ROM ON MY XDA 2, BT TOOLS, AND I BONDED ON COM 4...BUT ALL TOMTOM 3 SHOWS IN LOWER BOX IS:
COM 2,9bt ON COM 6, AND bt GPS.....
NOTHING OF THEM WORK...
PLEASE HELP ME...
@RDKAY:
Great to hear I am not the only one suffering from the TomTom hanging without GPS connected.
BTW: What ROM are you using?
I put bluetooth in discoverable mode, it finds the holux gps, it asks "do you want this device as a serial device" answer yes. Switch bluetooth to on, in tomtom, the top box reads tomtom wireless gps, the bottom box reads com 5, it works perfectly.
Im sure you all have latest opdate from tt..or? had the same problem activating major roads, opdate solved this problem..why use wizard changing gps? uncheck recieve all incoming beams in connections, go to programs/tomtom gps change gps to any serial gps..(not uncheking gives an error message: can not open com 1: port does not exits. rom 1.66.00).
Jensen
@edsub
I am using the Imate 1.72 Rom on my T-mobile mda2... don't think it is a rom issue although...
Im sure you all have latest opdate from tt..or?
Click to expand...
Click to collapse
I think it might be true that updating TT would do things better but:
I have bought TT with maps for Germany, Austria and Switzerland. And I just needed a Spain Map also which you cannot buy individually (TT just told me to buy also the Westeuropean package... :evil: ) so I got the Spain Map from Emule. :twisted:
Now when I do the TT update the Spain map doesn't work anymore, so I cannot do the update....
.why use wizard changing gps?
Click to expand...
Click to collapse
Because with opening directly TT Gps its hanging my mda2 completly, I have desactived incoming beams although :roll:
But anyway phone and TomTom work fine more or less, so "never change a running system" :wink:
Cheers
Rainer
Its looking more and more towards a rom issue.
People without the issue all have iMate roms
I have Qtek rom
What is your Rom build?
Mine
Version 1.72.00WWE
Date 03/15/04
Radio 1.14.00
Protocol 1337.24
ExtRom 1.72.901 (my own)
I know that Garmin said that there GPS 10 is not compatible with 9100.
But I manage to make some settings so i could pair the units together.
Only one problem.. when I try to install basic map and other maps my computer wont find the device.
It says that the unit is not connected...
My Qtek S100 workes directly.. but I have just upgraded to 9100 and would like to get it to work..
Any suggestions?
Not much for help here with me, buddy.
I found that most of the gps software I had tried would not allow me to use my BT GPS...finally, Pocket Streets allowed me to set the com port to what I was able to set as the outgoing port on the 9100...it works fine....
I have a lot of useless mapping software now, and Pocket Streets isn't all that I would hope, but it will do for now...
I've heard rumors, on here, I think that TomTom will work, but I don't have that kind of money...
If you can get them to pair, that's great, but the software you use will need to be able to see the GPS at the outgoing port that you create on the 9100...
hope this helps a little.
Have spent a long time trying to get my tomtom5 navigator working on my mda and now have it all going lovely - however I cant get my bluetooth reciever to be seen by tomtom. It is one of the BT-77 one that you see loads of on Ebay - did used to have it working with my old phone but not this one?
Any ideas - cant give up now!
Thanks
ROger
I have the same problem with an xdalls with a BT338 bluetooth gps.
I can get it to pair up. Tomtom5 does not see it though. Been thru all the settings that i can thing of.... i have the blue light flashing fast and then just logs off.
Paul
I have the BT-77 (also from ebay) and it works perfectly with the TomTom 5.21 software...
I had trouble with it initially too- it's to do with setting the right COM ports.
To get things working, I downloaded and installed Pocket Bluetooth Tools:
http://www.bluetooth.jazztel.es/ Download version 1.0.1.2
Delete any existing pair that you may have with the GPS receiver...
Re-pair the device with the above software installed, and now you will get an iconic menu, use the serial port option and select an available COM port. Complete pairing procedure as per on screen instruction.
Now start up TomTom and go to GPS options in preferences- select 'other bluetooth device' and now you should see the something called 'BT on COMx' x being the port you assigned earlier of course. Complete configuration.
Wait for the receiver to get a fix and you should be ready to go.
I've used the Pocket Bluetooth Tools many times on different variants of the Magician and has work everytime.
Hi
thanks for the info - but still nothing
cant cope anymore
will buy a whole new system i think!
Thanks anyway
Roger
HELLO!
Well at last it works - not really sure why?
But I dont care it works!
thanks for the help
Roger
Hi!
Just registered to try and find out how to get my MDA II working with a bluetooth GPS and I find this thread. Thank you for the link to the bluetooth tools it seems to have worked a treat.
Cool. Glad it is working for you guys.
The software also works well with using Bluetooth and ActiveSync.
Hi All
I have the above setup and am having a nightmare trying to get the bluetooth GPS to work. I have tried every setting I can find and even upgraded the ROM to 1.90.96 to see if that helped but still no joy. Basically whichever COM port I assign 0,4,5 or 8 (the only options allowed) it shows up in the "Other Bluetooth GPS receiver" catergory in TT6 but it will not connect. I have also noticed that the only time the BT LED on the Holox device flashes is during the initial pairing with the jasjar, before the device default password "0000" is added. Once this function has been completed tthe light remains solid and tt6 does not recieve the gps signal.
I know the Holox unit and the TT6 is working fine as I have tried it on an old HP 1940 with wm2003 and it works perfectly.
Has anyone got any ideas, suggestions or experienced the same problems
When you set up the Pairing with the GPS receiver use COM0 and select the serial port. Once this is done, set up a new outgoing COM port and make sure that the "Enable secure connection" box IS NOT checked. My Exec never works with any BT GPS receivers if this box is checked.
Then in Tomtom set use other BT GPS receiver and select COM0.
Pug.
Hi Pug
No joy I'm afraid. Have tried this more times than i care to mention but TT^ will not recognise the gps device.
Sounds like a problem with your BT stack then. If it worked on your other device then it's obviously a problem with the Uni. Seen as this isn't a common problem, might be some problem with your setup. Thinking about it now, Tomtom overwrites some BT files during install, as you seem to be using an AKU3.2 ROM which will have updated BT stack, try deleting these from the windows folder.
ttn6bt2003.dll
BtCoreIf.dll
BtSdkCE30.dll
If it doesn't work, you can always re-install TT6
Big G said:
Hi All
I have the above setup and am having a nightmare trying to get the bluetooth GPS to work. I have tried every setting I can find and even upgraded the ROM to 1.90.96 to see if that helped but still no joy. Basically whichever COM port I assign 0,4,5 or 8 (the only options allowed) it shows up in the "Other Bluetooth GPS receiver" catergory in TT6 but it will not connect. I have also noticed that the only time the BT LED on the Holox device flashes is during the initial pairing with the jasjar, before the device default password "0000" is added. Once this function has been completed tthe light remains solid and tt6 does not recieve the gps signal.
I know the Holox unit and the TT6 is working fine as I have tried it on an old HP 1940 with wm2003 and it works perfectly.
Has anyone got any ideas, suggestions or experienced the same problems
Click to expand...
Click to collapse
Try reading here:http://forum.xda-developers.com/showthread.php?t=283253
That should sort it.
Mav
Still No joy with Jasjar, Holox BT-321 GPS & Tomtom 6
Hi All
I've tried all fixes for the above problem suggested by pug and mavrik64 earlier on this thread but without success. This is a little frustrating to say the least. The Jasjar has had clean install with nothing loaded other than the default programs included with the latest ROM build 1.90.96 from Jwrightmcps, the UK 'O2' setup and TomTom 6. As I know the software and Holox unit work fine on my old HP1940 running on wm2003, I'm convinced it is something in WM5 that is giving me the problem. I have read other forums were other people appear to have similar problems.
Please note; the main reason I flashed the ROM from that previously installed 1.30.76 was to try and find a fix for this problem. The older version gave me exactly the same problem.
Anyone got any ideas
I am using Ivans Beta 15 and no problems, try flashing with that.
You have a new PM in a few moments as well.
PUG
Any idea where I can get hold of a copy of Ian's Beta 15 ROM. I've trawled round this site but can't seem to locate it
Big G said:
Hi All
I've tried all fixes for the above problem suggested by pug and mavrik64 earlier on this thread but without success. This is a little frustrating to say the least. The Jasjar has had clean install with nothing loaded other than the default programs included with the latest ROM build 1.90.96 from Jwrightmcps, the UK 'O2' setup and TomTom 6. As I know the software and Holox unit work fine on my old HP1940 running on wm2003, I'm convinced it is something in WM5 that is giving me the problem. I have read other forums were other people appear to have similar problems.
Please note; the main reason I flashed the ROM from that previously installed 1.30.76 was to try and find a fix for this problem. The older version gave me exactly the same problem.
Anyone got any ideas
Click to expand...
Click to collapse
Sorry to hear this didn't work. I am using JCs current rom with TT6 and Holux GPSlim 236 and it works like a charm.
Good luck
Mav
I would appreciate any help offered,
I have searched the threads but have not found much applicable
My problem is that I cannot get My Universal to talk consistantly to the Rikaline 6033 GPS the BT link will not stay up.
I am using a T-Mobile Universal with the excelent
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship Rom
The only way I have found of getting the GPS to talk to the Universal BT
is to install "Virtual Earth Mobile",
get it to pair with the Rikaline GPS
and then run TOMTOM 6
TT 6 will then recognise the GPS on COM0
Every time I switch it off and back on I loose the conection and have to go through the whole rigmarole to get it to go again.
I have tried opening the other comms with WM5GPSfix but it doesn't seem to help
If someone has managed it and can let me know I would be very grateful
TIA
A side issue,
What is the reason that the first connection with AS 4.2 takes so long?
Thanks