yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Apps and Games] Mach2003:
@Crescendo Xenomorph

Please turn on logging using the EnableLogs Registry Key set to 1.

Run your GPS until you get a lock plus about five seconds, then close it.

Copy the GpsModLog.txt file from the root of the PPC, and send it to me. If you post it here, everyone who reads it will know your exact location :).

You can email me using the link in my profile here, or get my email addy from the donate link below (no need to donate, just click the link).

Keep an eye on the fix time, I suspect that you just had a fix already when you ran the test. GpsModDriver does little to effect fix time, other than correcting the bad messages from the GPSID driver.

@sandervanzijl

Install the driver, Set the registry only if required. Note the GpsComPort and Index registry values are critical: GpsComPort MUST match the port under settings,system,External Gps. Index can be any free port on your phone.

In TomTom, set it to use the "Index" port (COM6) at any baud rate (115200).

You should be good to go.
[Windows Mobile Apps and Games] Crescendo Xenomorph:
Thank, I'll start logging and will send it to you after this. :)

Umm, no. In fact I turned off the A-GPS feature and power my device off, remove the battery for a while (to completely clear the RAM) and start my PDA, open GPS Tuner. It lock the sats in about 1 minute. I never had a lock in such short time like that. Usually 3 minutes++.

And I tried it several times. The lock time varies from 20 to 100 seconds, which is AWESOME.. :cool:

But yeah, the Lat coord is weird. It missed one coma I think.. Supposed to be 8.10 but it read 81.00...

Thanks for the answer and it'll come from x3n0m0rph@live.com... ^^
[Windows Mobile Apps and Games] Mach2003:
version 0.5 at first post. Fixes lats < 10, and lons < 100, by inserting the required leading zeros. Thanks to Crescendo Xenomorph.

If you don't travel to (or live in) these zones, no need to update yet.

I notice many downloads, but little comments, can everyone who tries this driver report working or not and what device you are using it on?
[Windows Mobile Apps and Games] someotherguy:
This confirmed working on CDMA Touch Pro?

I'll be sure to donate if you can get the Garmin XT Patch automated after each reboot, so all I have to do is launch XT and go.
[Windows Mobile Apps and Games] Mandragore:
Nope. Why don't you try it and give us your feedback?

Although, you have read the first post, haven't you?
[Windows Mobile Apps and Games] Mach2003:
I'm wondering if the CDMA units use the default COM6, for something else, and the other two users just did not change it. Is there a lurker out there with a CDMA Diamond? Check to see if COM6 is free.
[Windows Mobile Apps and Games] shmilson:
Effect on battery?!

Great job there Mach2003! Installed it on my TP2 and it really does wonders to the GPS precision. It did "look" like it was draining more battery though. (didn't have really time to test it, so it is only based on a "feeling"). So the question is, does the driver keep polling GPS port all the time or is it event driven?

Anyway, GREAT idea and implementation. Will try it installing new 0.5 again (was 0.3 when tested) and will be back with some more feedback asap!

Thanks!
[Windows Mobile Apps and Games] Mandragore:
Sorry, didn't get around to it yet. Tried 0.3 yesterday for about 10 minutes on a highway, driving a steady 100 km's/hr. When I had Mobile Navigator 7.3.4 zoomed all the way in, the pointer was a little bit jumpy. And when we neared or passed an off-ramp, it showed us taking the off-ramp for just a second or two, before returning us to the highway. Uninstalled 0.3 and installed 0.5 just now. Tomorrow I'll drive my own car and hope to do some serious testing.
[Windows Mobile Apps and Games] Mach2003:
Battery Drain

My driver opens the default com port, when your application opens My port, it polls the port using the Time set in your GPSID registry. It closes the default port when your application closes My port. During the time My port is closed, nothing is happening with my driver at all.

Bottom line, unless another application has the default port open at the same time, my driver should not keep the GPS active any longer than the default port would.

Try your battery drain, without opening My port at all. Then try after opening and closing My Port.

I have run my driver on my Diamond for while now, and have no battery drain issues what so ever.
[Windows Mobile Apps and Games] SOHKis:
just installed 0_5 on my cdma diamond and no problems here. seems to be working great.

i would be happy to check port 6 if you want to instruct how this is done
[Windows Mobile Apps and Games] Mach2003:
Good news on a CDMA Diamond working now!!!

Well, first, did you leave GpsModDriver at the default COM6?

Use registry editor, search from HKLM\Drivers\Active for string COM6, if you find it, then it exists. Of course you will find it if you have my driver installed on COM6 :).
[Windows Mobile Apps and Games] SOHKis:
left everything as is, searched and all i found was this:

[HKEY_LOCAL_MACHINE\Drivers\Active\16]
"Hnd"=dword:00052E90
"Name"="COM6:" <~~~
"Key"="Drivers\\BuiltIn\\VirtCOM_CMD"
"BusParent"=dword:00032DD0
"InterfaceType"=dword:00000000
"BusName"="BuiltInPhase1_0_23_0"

*after a soft reset the phone hung on boot, pulled the battery after a few minutes, powered up & the phone had hard-reset
[Windows Mobile Apps and Games] Mach2003:
Thanks for looking, So for CDMA Diamond DO NOT USE the default Index value of 6, I have no idea what the VirtCOM_CMD port is, but two devices can not use the same port!!!

Search active devices for "COM", and find one that is free, anything unfound will do, then set the Index value under Drivers\Builtin\Serial5 to the "unfound" value, and then soft reset.

GSM DIamonds (well mine anyway), use COM7 and COM8 as well as COM4 for the GPSID port.

You could tell others here what index you found to use.

Edit: a quick search shows this:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\VirtCOM_CMD]
"Dll"="VIRSER_ATCMD.Dll"
"Tsp"="Unimodem.dll"
"IoBase"=dword:AE100000 ; FFUART
"Irq"=dword:13
"IoLen"=dword:24
"DeviceArrayIndex"=dword:0
"Prefix"="COM"
"Order"=dword:2
"Index"=dword:6
"DeviceType"=dword:0
"FriendlyName"="RIL on COM6:"
[Windows Mobile Apps and Games] SOHKis:
looks like 4, 6, 7, & 9 are in use from searching the registry after the hard reset. maybe i'll give 8 a try.

garmin seems to keep defaulting back to com4 for some reason when enabling COM8: Gps Mod Driver. im open to any suggestions
[Windows Mobile Apps and Games] Mach2003:
Thanks for the report.

Since the GSM Diamond uses COM8 for USB, I'll change the default port to COM3, should work for both GSM and CDMA Diamonds at least, anyone else have a choice?

Garmin is a pain in the A**, I used to set the Registry as noted a few posts above, but since I flashed to 23071 it only works 25% of the time!!! You do know this is a Garmin XT problem right, it refuses to use the port we set it to?

I'm still working on a solution, I might make a stub application for starting MobileXT, setting the registry before it starts, and setting it back once it stops.
[Windows Mobile Apps and Games] ATT-Half:
CDMA touch pro won't boot with port 6 had to hard reset lol

lucky i have backups

anyways i tested this on port 8 boots fine

google mobile maps & IGO are reporting maybe half block ahead of current location while moving.

this is happening on highway and in the city " when on the move"

in the city when i was doing a left turn google mobile maps reported my location half way down the next block while i slow down to turn but after the turn it would correct the heading

on IGO8 it would pass exit ramps to my right before i had actually pass them again I would say about half a block ahead.

(overpasses also reported me passing them before i actually did)

"standing still it would report my location correctly" both google maps and IGO8

like it's guessing little to far ahead

on pic both turns i had green light so didn't have to come to complete stop before turning

i used GpsModDriver0_5.CAB
[Windows Mobile Apps and Games] Mach2003:
Great news, so the in-use port (Com6) is the CDMA issue :SOLVED:

You can reduce the LagAdvance reg value to find the number of milliseconds you need to "look" ahead.

I might have defaulted the EnableLogs reg value to 1, everyone should reset that to 0, so that your ppc does not waste time and space writing a log file. The file on the root of the phone GpsModLog.txt can be deleted, once Enable Logs is zero, and the port is closed.

Version 0.6 will be posted soon, with the default port set to 3, plus some other tweeks.
[Windows Mobile Apps and Games] Mach2003:
Garmin Mobile XT

EDITED - Current QueStub is on first post to this thread

This seems to be working, try it...

UPDATED: MUST use RC1 version with RC1 or newer driver version

- Added v1.3, just changes log file location and content. (it does use the enable logs flags from GpsModSetup)

Type 1) You have Garmin Mobile XT properly installed to main memory:

- Copy QueStub.exe to \Garmin from the attached zip

- Rename the existing Que.exe file to Old.exe

- Rename QueStub.exe to Que.exe

- Run Garmin Mobile XT, normally, from the previously installed shortcut, do not try and run que.exe, Old.exe or QueStub.exe. Your existing shortcut runs Garmin Mobile XT.exe, as it should.

Type 2) You have copied Garmin Mobile XT to a card, or another location, other than \garmin, but did not install it. Or you are running XT from another program (QuePPC.exe for example):

- Add or Edit this registry key pointing to YOUR exe

[HKLM\Software\Garmin\Que] QuePath REG_SZ {path to YOUR exe}

"\Internal Storage\Garmin\Apps\WM\QuePPC.exe" for example

- Copy QueStub.exe to the location where YOUR exe is found.

- Rename YOUR exe to Old.exe

- Rename QueStub.exe to the same name as YOUR exe used to be.

- Use your existing shortcut to start the application, it will now start the renamed QueStub.

- If you do not have a shortcut, run the (renamed) QueStub.exe (it wil be the same name as YOUR exe used to be)

You only do Type1 OR Type2, not both.

PS, Type 2 can be used for any application, not just Garmin Mobile XT. Use it if your application insists on opening the GPSID port, even when set to use GpsModDriver port.

QueStub will read the key to determine where your renamed QueStub.exe is located, or default to "\Garmin\Que.exe"

QueStub changes the GPSID reg to point to ModDriver and then runs Old.exe instead of Que.exe, QueStub stays in memory (about 5kb), and restores the Reg back to the original values when Old.exe exits.

There is automatic recovery in GpsModDriver and QueStub in case of soft reset while QueStub is running.

Do not rename 'Garmin Mobile Xt.exe', as it just runs que.exe, and terminates, restoring the reg to the defaults too soon.

Run Garmin Mobile Xt normally, but do NOT touch the "External GPS" control panel at all while Mobile XT is running. Select the Mod Driver Port in XT.
[Windows Mobile Apps and Games] p50kombi:
0.60?

Looking forward to trying this today...

However, only 0.5 is on your startup post...

Or am I too fast :-)

Guess my gps anti-lag is way of the chart...

Could you post version0.6?

Thanks buddy.. this looks very interesting.

Will report back after using 0.6 today on my gsm touch-pro
[Windows Mobile Apps and Games] Mach2003:
Try to increase DeltaDistance for the profile you are using (Driving, I presume).

There may be some kind of little bug in there, because I had a few cases where my heading was a little off this morning on the way to the office... I have not looked into it yet, though. If DeltaDistance does not fix the problem, try also smooth off.
[Windows Mobile Apps and Games] Mach2003:
I found the bug in setup.dll, fixed.

Garmin dislikes 1.35, it does not like to wait a few seconds for first GPS data.

1.36

- Changed to send up to five seconds worth of LastKnownGood data on initial un-fixed or missing GPS data, but then never agaiin on the same connection. Will give a quick fix to apps that just read a single position and then exit (bing for example).

- Fixed bug in UninstallExitEnd

- Added more flags and tests to Install/Uninstall setup.dll

- Unload driver now tried two different ways. Should avoid even more stuck uninstalls

- Prevented smooth from being exported when LastKnownGood data is sent.

I'd like to hear some test results of people who want to try and break the Uninstall/Install/Upgrade. You can enable logging(enhanced) from the GpsSettings app (or the reg directly), and then look at \Mach2003\ModSetup.txt to see what is going on. Be warned that some things in the log file *Should* report fail (like opening the device key, on the init_exit steps. You should even be able to uninstall while the port is open now. If you can break the uninstall, post the ModSetup file here or email it to me (there is no identifiable (gps position) information in ModSetup).

Also, remember that "Uninstall" uses the setup.dll from the last install, not the one you are trying to install, so clean uninstall first, and then test with the new cab.

Attached cab is beta...
[Windows Mobile Apps and Games] Mach2003:
I have the default value for DeltaDistance at 2.0 meters, a little small for the driving profile, set it up closer to 50 (5 meters).

I'll update it for the next release.
[Windows Mobile Apps and Games] tcchuin:
with the newest questub,and 1.36,garmin can't use post comm 1.i don't know why.
[Windows Mobile Apps and Games] NKTA:
I guess....

I guess that u mean going with file explorer to "My Device", and delete the folder Mach2003 and the file inside it.

Will give a try to 1.36 ... and check back something.

I installed 1.32 version, now trying 1.36, but it seems it can't uninstall the previous one. Unistall from Remove Programs.

Also deleted GSModSetup from Windows directory. Any solution for this besides Hard-reset, any more files that i should delete ? Or i should try to install on top of 1.32 build ?

This post its now linked to this post of HTC Touch Pro

Thx for your developing.
[Windows Mobile Apps and Games] Mach2003:
I use 1.36 with QueStub and Garmin, no problems.

Is GopsModPort available to another program (HTCGpsTool)?

Do you use (type 1 or Type 2)? You can enable logging and then look at both QueStub.log and ModDriver.log in \Mach2003 to get an idea what is going on.

The file(s) in \Mach2003 are only log files, they have no effect on running or (un) installing the driver. Delete anything there that you are not debugging with at any time.

SKTools removes a stuck un-install (even in demo-free mode). Once an uninstall is stuck, it seems it never becomes un-stuck.

Other than looking into 'why' it gets stuck, you can still most likely install a newer version, just ignore the 'installation failed' message. Worst case disable driver with GpsSettings/System, soft reset, and then just copy the raw dll from post1 to \windows, and then re-enable the driver using settings.
[Windows Mobile Apps and Games] tcchuin:
it's available and i'm using type 2..
[Windows Mobile Apps and Games] Mach2003:
Ok then the driver is loading and running great!

I assume you had this working with an earlier version, right?

So what does XT do with 1.36? Does it open Com4 instead, or just no data from Com1 (GpsModDriver)? Does the GPS data screen show varying bars for each sat it sees?
[Windows Mobile Apps and Games] tcchuin:
it shows gps intermediaye driver no matter port 1 or port 4 is selected..
[Windows Mobile Apps and Games] Mach2003:
Soft reset your device, and then double check the External GPS control panel item (start/settings/system). Make sure COM4 is selected and 'Manage GPS Automatically' is checked.

Use GpsModSettings, leave it running until you get fixed position data. Exit GpsModSettings, and then run Garmin Mobile XT right away.
[Windows Mobile Apps and Games] tcchuin:
the gps program comm port is 4,but gps hardware port is "none",the 'Manage GPS Automatically' is checked.

do i need to change gps hardware port?going to try the way you said.
[Windows Mobile Apps and Games] Mach2003:
The hardware port page is useless, ignore it, neither the hardware port nor the baud rate have any effect on our devices.
[Windows Mobile Apps and Games] tcchuin:
i tried,and it's still showing gps intermediate driver..
[Windows Mobile Apps and Games] pfonck:
On the Samsung Omnia the driver does not close the GPS port after exiting the client software (in my case TomTom).

Must say I've only tried 1.2 and not likely to try other versions because uninstalling is a pain and not looking forward to another hard reset/backup/restore.

The Omnia in combination with TomTom doesn't suffer from lag anyway but I saw it as a lightweight alternative to things like GPSgate/proxy.

It does the job for that matter but the battery drain problem makes it unsuitable.
[Windows Mobile Apps and Games] Mach2003:
If you are interested:

Try the 1.36 Beta version posted here. It does not have multi threads, if TT closes COM1, driver will close COM4.

I'd sure like to see the ModDriver log showing the port still open. Enable extended logging, run tomtom, close tomtom right away. Email me a copy of \Mach2003\ModDriver.txt

If the GPS port is still open, after you close TT, then don't try an uninstall, untill you SoftRest. If the port is still open after a soft reset, disable GpsModPort in GpsModSetup/system, SoftReset, Uninstall.

As mentioned many times here, SKTools will uninstall without a HardReset.
[Windows Mobile Apps and Games] Mach2003:
I'm lost! Try any or all of the following...

1) Have you changed any settings? Try SoftReset, Uninstall (No to save Settings). Softreset. Re-Install CAB. Run GpsModSetup, select default button on both profiles (change DeltaDistance on driving profile to 50), save. Select Profile 'Driving', wait for fixed position data. Exit. Run Garmiin.

2) Double check, In your Garmin folder, Old.exe should be large size (4.8Mb), QuePPC.exe shound be small (7.5Kb). Double tap QuePPC.exe (actually QueStub.exe you renamed). Does Garmin connect to COM1 now? While Garmin is running, switch to start/settings/External GPS. Is the port COM1 now?

3) Enable Extended logging (GpsModSetup/Settings.Both top buttons/Save/Save), start Garmin wait for gps connection (to what ever port), and then exit. Send me the ModDriver.txt and QueStub.txt file from \Mach2003 on the device. You could paste them here, but your Gps Position is in ModDriver.txt. Don't forget to turn off logging.

4) Try an earlier version of the driver (1.32 from the first post).

I have attached a re-built QueStub.exe here, but there has been no code changes from the one on the first post. I have re-tested this copy on my Garmin just now, it still works...
[Windows Mobile Apps and Games] Mach2003:
QueStub Cab

I have a working copy of an installer cab for QueStub in test now.

Does anyone have Que.exe (QuePPC,exe...) in another location other than these?

"\\Garmin\\Que.exe",
"\\Internal Storage\\Garmin\\Apps\\WM\\QuePPC.exe",
"\\Internal Storage\\Garmin\\WM\\QuePPC.exe",
"\\Storage Card\\Garmin\\Apps\\WM\\QuePPC.exe",
"\\Storage Card\\Garmin\\WM\\QuePPC.exe"

The idea is:

Search for Que.exe (in this order);

Read reg path [HKLM/Software/Garmin/Que] REG_SZ QuePath.

Search the above paths top down.

If we find a valid file, use it, and write it to the reg for future use. If not found, error exit from installer. Warning popup may be issued to manually rename the files.

Test size of file < 25kb, if it is then it is already a QueStub (renamed)

If not then it is an original file.

Cab installs QueStub.exe to \Mach2003, leave it there so uninstall will not fail.

If it is original file: Do the rename to Old.exe and copy QueStub, rename QueStub.

If it is already a QueStub, Just copy and rename the new one.

Uninstall Searches for file as above, tests size, if file < 25K it is a QueStub. Then Delete the found file. Rename Old.exe to Original name. Windows will remove \Mach2003\QueStub.exe.

I could optionally install a shortcut, but I think everyone who uses Garmin will already will have a valid shortcut in place.

Any comments?
[Windows Mobile Apps and Games] illi:
Can you put \Mach2003 to \Storage Card\Garmin\Mach2003? I like my SDCard to be clean and organised.

Thank you.
[Windows Mobile Apps and Games] Mach2003:
There is little reason why the QueStub cab can not install to Storage Card. (only that the correct card would have to be inserted for Uninstall to function).

There is a reason it should not install to \Garmin\Mach2003 though because the card and device paths must be the same. Some users have no such folder tree on the device.

Would you be ok with "Storage Card\Mach2003"? You could do this by just selecting card install instead of device install.

By the way the log files still will go to device:\Mach2003 and not card, because the log files may be accessed during driver install/startup/uninstall, possibly before the card is ready for use.
[Windows Mobile Apps and Games] illi:
It's ok.. Just a suggestion and I understand the constrains.:)

Thanks anyway.
[Windows Mobile Apps and Games] hottmeeel:
Request for additional functionality

Hi, I'm using your apps on my HD. It works great in Tomtom and iGO. However, I notice when speed is low your extrapolation of the course becomes more uncertain with a larger error in it (which is to be expected). When speed is zero the map turns around and often ends up in the wrong direction :). Is it possible to add an option to stop calculating the course when speed drops below an user-specified value (kilometer per hour or mile per hour)?

Thanks!
[Windows Mobile Apps and Games] L_o_k_i:
@hottmeeel

see http://xdaforums.com/showpost.php?p=4941778&postcount=390
[Windows Mobile Apps and Games] dampam:
March2003

Thanks again for the great piece of work. The display on my HD in 3D mode is still laggy (about 2 to 3 seconds behind. Changing the lagadvance did not seems to help) but the voice is now spot on. The lag however is gone in 2D mode but the screen will (quick frequently) show patches of grey blank areas.

I wonder if this is due to the very slow graphic performance of the HD. Is there anyway to overcome this ? Anyone else has this issue ?
[Windows Mobile Apps and Games] gsmdb:
I don't think the HD has slow graphic compared to my old Diamond I. You must squeeze on the parameters to optain your satisfaction

Delta dist. min 50

Delta speed min 30

My data

delta dist. 50

delta speed 50

delta time 8000

lag advance 1000

speed fix + average

smooth disabled

"dead" accuracy on every next position w. Tomtom
[Windows Mobile Apps and Games] ATT-Half:
hello

is there anyway to change the defualt gps port to another port and have Gpsmoddriver use the original port to force sprint navegation to use gpsmoddriver since u can't change what port it listens too?
[Windows Mobile Apps and Games] Mach2003:
I don't have Sprint installed, and have not tested this but...

You can swap the ports, use the GpsModSettings app. But I think your app will just use the 'new' port anyway (it probably reads the port from the GPSID reg)

You might want to try QueStub. Follow Type2 instructions, but substitue the exe for sprint in place of Que.exe. You still need to edit the reg at software\garmin\que though (assuming you don't have Garmin Mobile XT installed as well).

QueStub will change the GPS port reg to point to ModDriver, run Sprint, and change it back when sprint exits.
[Windows Mobile Apps and Games] private69:
FOR MAch2003

Hello,

I have a problem with my samsung omnia 2 like all the people lol who want to use tomtom navigator 7.

So Tomtom work with a third soft like gpsgate.

Yesterday i found you'r soft on xda, and i try it, with 132 version is no ok, but with you 135 version its very good !!!

Can you make a special version for omnia 2 ? this version just only redirect ports without all specificity : like GPSGATE ? or say me whats the value i write in this case :

Delta Distance

Delta Time

Delta Speed Lag Advance

And Toggle Fix

Course Fix

Dop Fix

Averaged

Averaged

Can i post on other forum you'r direct links for dowload you'r soft for all omnia 2 users ?

Thanks in advance.

Private69

@+++