A third GPS Thread... why not? COM4 is the Intermediary Driver

[bigflavor]

Hey all,

I figured this was worthy of a new thread.

I noticed that the stage is set for everyone to begin investigating GPS on the Wings.

I also noticed that there appears to be a misconception about the internal GPS being active, but reporting only one satellite. This would be the GPS on COM4.

The issue is that, this is not a GPS, but the GPS intermediate driver; aka the GPSID. It's got some data in it, hence appearing to be one satellite.

Check out the Microsoft GPSID Settings tool (http://forum.xda-developers.com/showthread.php?t=358482). This discounts the whole GPSID_QCT.dll (http://forum.xda-developers.com/showpost.php?p=1807718&postcount=23) (or any other QualComm files/reg entries).


Just wanted to clarify this. If I'm wrong, tell me so.


Thanks,

Matt

[jockyw2001]

Check out the Microsoft GPSID Settings tool (http://forum.xda-developers.com/showthread.php?t=358482). This discounts the whole GPSID_QCT.dll (http://forum.xda-developers.com/showpost.php?p=1807718&postcount=23) (or any other QualComm files/reg entries).


Just wanted to clarify this. If I'm wrong, tell me so.

You could be right. Once I've recovered from this bad flu I will do an in-depth analysis of GPS on my kaiser and compare it to Wings.

[10332007]

The AGPS driver found in the restetry has a value called "enable GPS" with a value of 0.

[NoNco]

Iv looked at this before. When i run it it gives me...

Program Port:
COM4

Hardware Port:
(None)

Hardware Port Baud Rate:
300

Manage Automatically is " ticked "

????????

[bigflavor]

The AGPS driver found in the restetry has a value called "enable GPS" with a value of 0.

uh huh

Iv looked at this before. When i run it it gives me...

Program Port:
COM4

Hardware Port:
(None)

Hardware Port Baud Rate:
300

Manage Automatically is " ticked "

????????

It allows you to configure the intermediary driver for gps. It allows mutliplexing of a GPS signal to provide multiple programs with GPS (if you use just the hardware COM port, you can only use one program to connect).

[NoNco]

ok, so what would the correct setting be for this then?

[bigflavor]

ok, so what would the correct setting be for this then?

There is no "correct setting."

http://blogs.msdn.com/cenet/archive/2005/06/10/427814.aspx


Here's the MSDN registry settings (http://msdn2.microsoft.com/en-us/library/bb202035.aspx), just to clarify my original post.

[butzchan]

With GPS Test, I have gotten 3 satellites at once before...no fix, all were weak signals...but 3 satellites.

[bigflavor]

With GPS Test, I have gotten 3 satellites at once before...no fix, all were weak signals...but 3 satellites.

Interesting... does the tool you use display the NMEA data? If so, check out the syntax (http://www.sparkfun.com/datasheets/GPS/NMEA%20Reference%20Manual1.pdf) and see what the NMEA data you see means.

I'm getting data but it's related to the GPSID, no useful data.


The point of this post was just to discount whatever COM port the GPSID (GPS Intermediate Driver) is configured on. I just used HTC GPSTool to test all 14 COM ports. The only two active were COM4 (for which I have the GPSID configured), and COM5 (for which I have the outgoing port to my bluetooth GPS receiver configured). The meaning of this is very important.


The internal GPS hardware device/chipset is not configured on a COM port. It, most likely needs to be found and installed on a device level.

Here's what I would do next / I wish I knew how to:
1) Dump my ROM (so that I could have a total backup that I can restore after testing; my phone is critical for my job so I can't be screwing around irreversibly)
2) Load the pre-prod rom
3) Run the HTC GPS Tool
4) Test all COM ports for valid NMEA data
5) Find which COM port the GPS hardware device/chipset is configured, not the GPSID.
6) Find the driver (related files and registry keys)
7) Figure out how to install the driver and attach it to the hardware device/chipset. (completely unfamiliar)
8) Dump the driver files and registry keys related to configuring the hardware device/chipset


I'm more of an IS bent logician than a programmer or hacker (I'm into networking), or whatever you want to call some of these XDA folks. So, the above is a general plan; if anyone with the specialized skills (such as driver-level programming, or an understanding of Windows Mobile device interfaces) can take on the above tasks; we will have an answer. For instance, hannip (http://forum.xda-developers.com/member.php?u=312382), who extracted the Bluetooth stack from the Treo 700wx (http://discussion.treocentral.com/showthread.php?t=137462) and made a CAB available for installation on the Treo 700w and 700wx, would be able to perform pretty much the same exact thing on the s730 and come out with results.



Anyone? Anyone?

[butzchan]

No NMEA data. This is the app:

http://classic.pocketgear.com/software_detail.asp?id=24687&associateid=9

[bigflavor]

No NMEA data. This is the app:

http://classic.pocketgear.com/software_detail.asp?id=24687&associateid=9

The HTC GPS Tool (previously attached) gives you the NMEA data. You can look at the data more closely, and refer to the syntax, which is described in the above linked PDF, to figure out what you're looking at.



Regardless, if someone has flashed their Prod s730 with the pre-prod ROM, and they are able to get a fix with the internal GPS; following the above procedure (http://forum.xda-developers.com/showpost.php?p=1810648&postcount=9) to begin to figure out where the drivers are, and how the device is configured to use the drivers, will allow us to make progress.


I'd be glad to specifically help, but I need to know how to dump and restore my ROM (reasonably) flawlessly, before I go and flash my phone with the pre-prod rom, etc etc...