Related
I am not able to use the receiver with Autoroute 2004(pocket streets). The manual suggests that I ensure a virtual COM port is established before connecting the receiver, which I am not able to get around. I am lost and stuck with an expensive receiver. Can some help, please? ASAP
Daz, when you try to run the program does it give the option to choose your gps/com port?
no, nothing came up on the screen. Fortunately I have been able to resolve the problem. Need to disable to incoming beam option in connection setting
I currently have the same problem with rakaline 6031-x7 and tomtom navigator. I use to connect the gps reciever via blutooth manager as slave and then set it up in tomtom on my ipaq. now I can't find any options in bluetooth settings on my xda2. Any chance of a little help?
:?
gavcha, the xda2 is braindead where bluetooth is concerned, are you running the latest gps 2.09 from tomtom? If you are using that and it still isnt working, download towas patch, remove the gps from the bonding on your bluetooth, install towas patch, run tomtom wizard, gps manager in discoverable mode, add device in bt manager by choosing "new", choose the gps, ok everything, towas patch should then come up and give you the serial option, choose that. When finished go to tomtom gps, choose tomtom bluetooth and in the second drop down your gps should be available, choose that and it should work.
Cheers mate. me being the impatient ba£$%rd that I am found this site
http://bluetooth.i-networx.de/index_e.html
Very usefull, up and running in no time. Seems to be in the same vein as your suggestion. Thanks for all your help I am slowly getting use to this xda milarky! Finaly I can sell the Ipaq!!!!
Cheers again.
Good to know it works, when O2 release the update it should get better, by the way that link you posted has been a pain in the ass for me, I have clicked that link in numerous posts and NEVER been able to connect, I have the patch now but does anybody else have problems linking to the above link.?
yeah i had problems going back to it when i was checking it to put it in my last post. try googling xda2 bluetooth manager. thats what took me to another forum with the link to this. worth a try. :idea:
Previously i had TomTom3.0 with BTHTools and a Holux BT GR230 GPS
and it worked fine.
I recently upgraded to ROM 1.72.00 WWE so i no longer needed BTHTools and it still works fine.
EXCEPT : When the GPS receiver is not found (BT turned off or GPS off or out of range), TomTom freezes or slows down terribly. This didn't happened with my previous rom/BTHTools)
upgraded to TT Navigator 3.03 and TT GPS 3.03 but that didn't help.
I found others reporting the same problem in other threads,( see Kim71 in http://forum.xda-developers.com/viewtopic.php?t=3341&start=350 ) but this specific problem was lost in the mainstream of those threads.
anything usefull will be greatly appreciated
The only way I found to get over this was to deselect the gps in tomtom before closing down each time, it would then need selecting if you wish to use bluetooth gps. If this wasnt done and bluetooth gps was switched off when starting tomtom the pda would slow to a crawl, I know it isnt a perfect fix but seemed to work ok for me.
the problem is you have selected the wrong com port in the gps setting (i have 3 to choose from on mine!) first uncheck the box on the left. then drop the menu and select 'bluetooth gps'. Then turn on the receiver and the check the box again
that should sort it.
Regards
The Pilgrim
Right now i have NMEA 0183V2 Bluetooth / COM5:
Tried to uncheck : OK
Tried choosing Bluetooth GPS : OK
Tried to check : NOK it simply will not check :?
is the reciever switched on?
As I have posted earlier in other threads and other sites, I have the exact same issue.
However there seem to be people that have got it to work without any extras installed.
Only port to get TomTom to work with my DConnex DC-230 (=rebadged Holux GR-230) is COM5.
I cant tick the blue box with 'Bluetooth GPS' in the lower combo=box.
To get by for now by I digged into the registry.
I created 2 CAB's that do the following:
Set the registry value of TomTom GPS to enabled or disabled.
By starting one of these CAB's I can easily enable of disable the GPS. Would be nice to have a Today Plugin that toggles the TomTom GPS Enabled value (any volunteers???)
BUT I see this solution only as a work-around.
The solution MUST be in selecting 'Bluetooth GPS' instead of 'COM5'.
The task is to find out on how to achieve that.
Any help appreciated.
Hi
i still have rom 1.66.00wwe. and BTTools installed
i run the latest tt gps v3.3 (?) and a fortuna bt clipon.
I can check the box with 'bluetooth gps' without any problems.
You might want to visit www.pocketgps.co.uk
The forums are excellant
i hope this is of use
Regards
The Pilgrim
Pilgrim,
I allready noticed the excellent forums on pocketgps.co.uk, but until now I only got the advise to select Bluetooth GPS instead of COM5. And that is just what is not possible with my 1.72 rom . . .
:idea: Like I said: any suggestions are more than welcom, as is an offer to creat a small program (Today plugin!) that toggles the Enabled registry value of TomTom GPS.
If anyone wants to write that pgm, he might consider simultaneously turning bluetooth on / off.
State 1 : Bluetooth on / TT GPS enabled
State 2 : Bluetooth off / TT GPS Disabled
even better: Make that configurable (via registry setting or whatever lean & mean) for both states
I have been investigating this annoying issue with "ronald2oo2".
He does not have any issues like we do with his 1.72.00WWE ROM.
We did notice some interesting differences between his and my device-behaviour. Also the registry settings between him and me are quite different.
The biggest difference between the two devices is the origin of the OS rom. He uses the iMate based rom, I use the Qtek based rom.
Could anyone with 1.72.00WWE OS ROM, BT GPS and TT3 please post:
1. If (s)he has the possibility of checking the blue--ish box in TomTom GPS when the post is set to 'Bluetooth GPS': YES / NO and with what protocol (NMEA, SiRF, GPS specific)
2. What the origin of the 1.72.00WWE (OS!) rom is: QTEK, IMATE, T_MOBILE beta, . ....
I experienced the same problem for several months now and hoped that it would dissapear when I upgraded to TT3.07 and TT GPS 3.07 but it still didn't work.
Then I came across this post and started playing myself with these settings and found a solution. I can now use TomTom Navigator 3.07 with a bluetooth connection with my Rikaline 6030 GPS receiver
I have a Qtek 2020 with 1.72.00WWE OS ROM and Rikaline 6030 BT GPS and TT3.07
I was able to check the blue-ish checkbox with Bluetooth GPS setting after choosing 'NMEA 0183v2 Bluetooth' in the drop down list above 'Bluetooth GPS' and after unchecking 'Outbound COM port: COM5' in my Bleutooth Settings (Start -> Settings -> System).
I hope I am helping a lot of people who have the same problem as I did for months and didn't find a solution for it.
Cheers,
Gino
The sentence: 'I can now use TomTom Navigator 3.07 with a bluetooth connection with my Rikaline 6030 GPS receiver' should read 'I can now use TomTom Navigator 3.07 with a bluetooth connection without my Rikaline 6030 GPS receiver'
Or without bluetooth turned on at all. Sorry for the confusion. Must be getting tired
Gino
Did you have to delete the existing bonds?
Because i tried your solution and it still won't let me choose "Bluetooth GPS". Am i doing something wrong? or is it some else different between our xdaII?
I don't know exactly where the bluetooth drivers come from. Can you check if you have OEM_WWE_04071402.sa.CAB in your ExtROM?
or another OEM_WWE_04???????.sa.CAB.
No I didn't have to remove the existing bond(s). I just first unchecked the Outbound COM5 setting in Bluetooth settings, then I removed the checkmark in the GPS Settings so I could select the NMEA 0183v2 Bluetooth option and then I selected Bluetooth GPS. Checked the check box again and closed all open windows and everything was working fine with or without bluetooth/GPS receiver .
Regarding your other question, where can I find this info about the OEM_WWE_04??????.sa.CAB file. I remember looking in the extROM but I forgot where to find it. I'll do a quick search to see if I can find it again.
Cheers,
Gino
you have to install extendedromunlocker
http://forum.xda-developers.com/viewtopic.php?t=8422&highlight=extendedromunlocker
and then unhide it, and then you would be able to see what's in there.
I also have OEM_WWE_04071402.sa.CAB in my ExtROM. I remember that my Bluetooth connection was not turned on when I tried to change the settings.
Gino
I have Radio version 1.14.00. Is this different from your version? I see that in your profile you pur 1.12.00 but I have noticed that 1.14.00 is not available.
I allready heard from 'ronald2oo2' that he is able to choose the Bluetooth GPS 'port' in TomTom GPS. I went thru all the options with him but still I cant select the 'Bluetooth GPS'. Also TomTom could not provide me with an answer, they eventualy offered to test my MDAII, but thats not an option since I rely on my MDAII.
BUT: I ams till using TomTom GPS 3.03. I will try the update tomorrow since maybe this version has some changes specific for Himalaya . . .
I am hoping someone can help me through this Smile
I have both TomTom and iguidance on my PPC and both are doing the same thing.
Here are my steps
1) Pair up the device properly, and set an outgoing port to COM8
2) GPS in Control pannel, program set to none, hardware com8, 4800, last page, manage automatically unchecked
3) run program and configure, works fine
4) turn off BT gps, turn back on, run program
5) MS BT application pops up saying my BT GPS receiver wants to connect, should I add it to the list, if I say yes and put in the pass key, nothing will happen, and if I go back into my BT manager, the GPS is gone.
Please help!
i have a Qtek 9000 but still what to use some of my programs from my WM5
does this work?
Exchange Mail support
TOMTOM
TOMTOM Bluetooth GPS
Bluetooth
and Sync with Outlook from XP or Vista
if any can confirm this works with WM6 than i´ll go for it
i never use Video calls so that does´t matter.
Can any recommend a ROM for me?
Yep they all work.
Except if you are going to use Direct Push mail with Exchange, with a constantly active connection, you will probably have issues with your data connection hanging. The only way to resolve it is to enable/disable the radio (sometimes works) or soft reset.
To stop it happening in the first place, selecting GSM only (ie not 3G) in the Radio options does the job..
We all know the Tilt's GPS is slow, uses a lot of battery, and often continues to use battery after exiting all programs using it unless you soft reset. So I use my bluetooth GPS.
Works great, for programs which have a com port setting. There are some which do not, some are on the todo list, but some other programs are no longer under development.
What I'd like to be able to do is to 'fool' any program into using the Bluetooth's com port. I have GPSGate listening to the bluetooth GPS and outputting to com1 so that I can run whatever number of programs using the GPS data on com1, but I can't get several Wifi scanners to use com1, can't get the camera's GPS feature to use com1, etc.
I've tried a few things like messing with the built-in GPS settings and changing them to com1 hoping programs might then access com1, tried setting GPSGate to com4 to see if programs would access it instead of the built-in, but I think when programs access the built-in device they don't access it on com4, they access it on GPD4 or such.. Anyway.
So again, how to make programs which you cannot specify a com port use GPSGate's com port? Or another program if necessary..
Thanks!
Bumping in case anyone missed it.
Thanks!
SOLVED! But not for the faint of heart.
The developer of BasicGPS pointed me to this URL when I was asking him if he could implement selecting the com port for the GPS, since I use GPSGate with a Bluetooth GPS, not the built-in one:
http://msdn.microsoft.com/en-us/library/bb202089.aspx
From this, following these steps, I was able to make the Intermediate Driver use COM1, therefore using GPSGate/Bluetooth! So far this works in BasicGPS and I'm pretty sure it works in the camera too, so probably works in every program! Good news for people who hate the built-in GPS as much as I do!
Here are the basic steps, but you'll want to read the URL above. It's really written for developers, which I am not, but it made enough sense for me.
I used Resco Explorer to browse into this registry key. I made a copy of the whole key, then browsed in.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers
There is a key named CurrentDriver, which was set to GPSOneDevice, which is apparently my built-in GPS. So I made a copy of the whole GPSOneDevice registry key, named it GPSGate. Then went into that key, changed the InterfaceType from POLL to COMM and added a string called CommPort and set it to COM1: where GPSGate outputs its info. I also modified the FriendlyName to "GPSGate Bluetooth". Finally, I changed the CurrentDriver to reference my new GPSGate registry key, and voila!
I'm not 100% sure it's working, as the built-in GPS is warmed up and would respond fairly quickly, but in a few days I'm going to try the camera in GPS mode and see if it immediately gets a fix from my Bluetooth unit vs 5+ minutes with the built-in GPS.
That said, I've tried GPSTest, BasicGPS, camera, etc, all get a fix immediately and update with the Bluetooth GPS on. If I turn the Bluetooth GPS off, they all stop getting updates. Previously when I was trying to figure out how to do this, I would discover the built-in GPS was still being used because I'd turn off the Bluetooth GPS and programs would continue to get new GPS data. So this tells me it's working! I'll follow up again in a few days to say for absolute sure.
Yay!
Just a followup here.. I think it's working, but if I monitor the data on COM9 (bluetooth) or COM1 (GPSGate re-distributing COM9 data), the data streams in at a reasonable pace.. Perhaps 6k of data in 10 or so seconds.. I didn't measure it closely.
But when I monitor data on COM4 the data is very fast, after about 10s it was up to 60k and when I left a few different programs open for a while they either crashed, never got a real lock, or locked up.
So not sure why, but the string of bluetooth->gpsgate->intermediate driver is causing a LOT more data to be produced.
I wasn't planning on using the intermediate driver for applications, I am still going to use the COM1 port for that when possible, but I wonder about the stability of using the camera and/or other programs which can't change the com port with this configuration.
Oh well! So far the camera seems to pick up a coordinate very quickly and probably disconnects from the GPS, so it's probably fine.
I suppose if I were truly curious I could capture the NMEA data and compare between the two. If anyone can do that who is also curious, I can do it and attach the data. I wouldn't know what to look for.
Hi,
ok, perhaps I know the Problem why my intermediate driver doesn't do his job. I can find this key in my reg:
Code:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers
But that is all. This key hasn't any values or subkeys. But why?
I'll try to find out the default Settings...
So. I've created following settings:
Code:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver
CurrentLogFile="\Temp\gps.log"
IsEnabled=dword:00000001
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers
CurrentDriver="TestFile"
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers\TestFile
File1="\Temp\test.nmea"
FriendlyName="File Test #1"
InterfaceType="File"
After creating settings I "rebooted" my device. Then I start my GoogleMaps-App and configured it to use "managed GPS".
Result: GoogleMaps didn't get data from test-file and I cannot find the log-file in Temp-Folder. What the hell is going wrong here?
YFI: If I configure GoogleMaps to use GPS an COM4 (115200 Baud) then all works fine.