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)
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
Hi there!
I've recently got a M500 and I have a cellink BTG-7000 Bluetooth GPS Reciever.
I can pair the M500 & Reciever but when I go into the Tom Tom Navigator it does not find the Reciever when I go to Preferences. (there are com ports there but no matter what port I select it doesnt find it)
Any ideas why?
Hi,
I had simular probs. after pairing with another BT device. Just paired with the GPS & all was fine, so
- make sure the GPS is the last paired device
- create a com port for the GPS
- try upgrading radio
- get another BT stack
I'm having the stack from here http://forum.xda-developers.com/viewtopic.php?t=33532 but can't say it solved it or not. But it works & I can use the BT GPS & a BT earpiece at the same time.
Good luck, M
How do I create a com port for the GPS? I dont seem to have that option.
My BT stack asks me whether to create a com port for it when I pair with my GPS. Also under the BT connection settings I've got a tab which read 'COM ports'.
Cheers, M
Mine doesn't have any of these options, strange?!
I guess thats the problem, it seems my M500 doesnt let you manually assign a port.
Any ideas on a fix then?
I am on radio 1.12 & got those options from radio 1.11 on. You can try the updated BT stack from the thread 'O2 mini new BT stock'
Maybe that helP as well, otherwise upgrade your radio.
Cheers, M
Take the wired gps, baudrate 9600 en after that test some comports. It takes a while when TT detects the receiver, so hold on a bit. Most of the time it is comport 4 or 5.
what version are you using, i had similar problems,
I found that if you install version 5.1 or 5.2 straight on then it will not find the gps.
i installed the original 5.0 from cd. then got GPS working. TomTom may ask you to reset the device to configure gps [it did for me].
i then upgraded to 5.1 then 5.2 and everything works perfectly.
what version are you using, i had similar problems,
I found that if you install version 5.1 or 5.2 straight on then it will not find the gps.
i installed the original 5.0 from cd. then got GPS working. TomTom may ask you to reset the device to configure gps [it did for me].
i then upgraded to 5.1 then 5.2 and everything works perfectly.
I initially had the same problem with my BT GPS device and tomtom 5.0, but pairing them just before loading up tomtom and setting it to COM 5 and then waiting a while seemed to solve it!
Good luck!
Got-it!
Duh!
I must have missed something here, so I'm posting this for the few people who are thicker than I must be;-
When setting the BT com port under 'Bluetooth settings', the outgoing com port selection window is blank.
HOWEVER, choose 'settings>system>bluetooth setting' and voila!, that is where you see that COM5 is pre-chosen. (Why there needs to be a double-entry is another matter?)
Hope this saves someone some time.
HI all!this is my first post on the forum and i am glad to be here!
the problem is i cannot connect the holux 236 to the s100 or magician.
rom version is 1.12.00WWE.I tried pocket bluetooth tools but no luck.
the gps viewer gets nothing and also the destinator pn shows that no gps is available...
please help in any way...a walkthrough would be welcome since i am a newbie with ppc...
thanks in advance and keep up the good work!!
Hi, have you had any success with any other gps reciever opr is this the first one you try?
Suppose you have tries to enter the sw program and then configure the reciever with your magician? Is this where the trouble is?
this is the first one to use.
s100 gives com 5 to the gps but still no luck with ddestinator.states that no gps is present.
maybe a bluetooth stack problem?
could use all the help i can get..............
Ive just ordered a Holux 236 from Fleabay, should be here in a few days, will post my settings if I get it working ok
is the holux 236gps mini actually compatible with the QTEK S100??????????
Hi
Switch on Bluetooth and Pair the device using pass key 0000
Then DO NOT connect the device
Enter GPS Viewer 1.5 and select (Bluetooth) COM Port 6 (may be something else on your device). Select Open GPS and you should start getting data...
Hope that helps
The whole problem is that I cannot get my Qtek 9100 to show the spp slave service. This seems to be a qtek problem because none of my other BT devices will show it either. They showed fine with my old HP 6365. :?
I am not sure in that case... I cannot remember but does it use Widcomm Stack or M$?
I'm not sure what stack they use. I don't think it's Widcomm, because my HP BT keyboard won't connect and the reason is that it says there is no Widcomm stack. Go figure.
if thats the case,how do we solve it?third party software?change bluetooth stack?and if yes how.........?and i thought it would be plug n play...
OK, I have this BT receiver, works perfectly with my mini. Have you added any bluetooth stacks in addition the default ? When you search for devices does the Bt find the Holux? Is it switched on and charged? Don't know how new you are to bluetooth devices, but bear in Mind that a brand new Bt device out of the box may take up to 30 minutes to get a fix for the first time.
no new stacks added,device is charged.
gps pairs with s100,asks if it should create a port,i reply yes and i press finish.in the bluetooth menu at the com ports i press new outgoing port and i am asked to choose a device.i select holux,press next and nothing happens....so whats the deal here?in the bluetooth serial port setup i check the outbound com port:com 5 beforehand.so please tell me what am i doing wrong this time....is there something i didnt do or something i did...?
Ok, so the pairing came up fine. Thats one thing out of the way.
Now, forget selecting outgoing or incoming ports, its completely useless, doesn't work. I have TOMTOM and have selected "Other Bluetooth Device" and selected COM5, it works fine. Could be your com port is being occupied by other bluetooth such as Activesync.
Delete all paired devices, Go to Start, Settings, Bluetooth Setting and check that "Outbound COM port: COM5" is ticked only, click OK then try pairing your Holux and try again. It does work with the mini, I promise!!
I got a 236 slim and no problem with MS BT stack.
try to connect as explained by moghisi101, it should work
WELL i did try,trust me!at what point should the orange led light up???it should first communicate with the gps viewer and then start blinking or something?cause so far the orange led has not shown its colors........is this normal or do i have a faulty gps?????????????
Hmmm sounds like a faulty unit. Ive had my 236 for a couple of days now and it worked first time with Tomtom, just selected 'Other device' and 'Com5'
Im really impressed by this unit, even gets 5-6 satellites indoors !
When you turn the unit on the orange LED should be on all the time (searching) then after about 45 secs it should start to flash indicating that it has locked onto satellites. If you arent getting any light from the orange LED it does suggest a faulty unit
HTH
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