Quoted further below is my original post. Here is what you're likely wanting to know since you're on this thread:
I HAVE GPS!
Thanks to the folks on this thread and to the ones who contributed to the following threads, I have fullow working GPS that locks in ~10 seconds (depending on the GPSMode of course).
Here is a brief summary of what I needed to do and why.
I WAS running radio 3.42.50 which has updated my PRI to 3.02.002. I believe this happened because I applied the MR1 update at some point.
Some of the links in the following threads worked, and some didn't. As of the time I'm writing this, following are WORKING links to all the software you'll need.
- For the first set of steps to recover radio, pri, and prl
- For the second set of steps to modify QPST and make final changes to get GPS working for your current ROM
To fix this, I hahd to follow the these two sets of instructions.
1)
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS (This fix will COMPLETELY reset your radio, PRI, and PRL to a condition which will allow for GPS and aGPS under Verizon)
2)
http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix (This set uses a tool called QPST to make changes to firmware in the phone that must also match registry settings from what I gather, in order to use aGPS)
I learned a few things that weren't quite obvious as I did this.
- The Vouge and Titan appear to use the same WModem drivers for Windows. These drivers are required for QPST to talk to the DIAG ports of your phone.
- As my edits to the Wiki in step 2 should indicate, launch DIAG mode using ##3424# and NOT the Diag shortcut which might be included in the "Phone Codes" OEM. The main reason for this is to keep the diag screen up and active. If your phone drops back to the Today screen, you'll likely have to pull up the DIAG program again, disconnect, and reconnect the USB. This should only be needed to get far enough for QPST Configuration to see the DIAG ports and recognize your phone on one of them. After that point, DON'T mess with the connection.
- I run USB2PC on my ROM and found that disabling that service (using dotFred Task Manager) helped get my USB connection stable enough for QPSP to recongize my phone.
- For the same reason as USB2PC, I also stopped "Windows Mobile" related services on my PC while I was doing the QPST bit of this process.
- You will need QPST 2.7 BUILD 301 (not BUILD 215).
If I think of anything else I'll be sure to edit this post.
Quote:
My Vogue had wonderful GPS locking speed previously, but now doesn't appear to get a single bit of data even though COM4 is detected as a GPS device and at the least, accepts commands.
I'm on a custom 21500 ROM, 3.42.50 Radio, I've set the "accepted" reg keys (GPSMode 4, AGPSEnabled=1, port 8888, etc..).
My next troubleshooting step was to go through the QPST process in DIAG mode. I've found Vista64 drivers that recognize both the "HTC Modem" and additional com port, QPST 2.7.301 will see these ports (though I have to uncheck "Show Serial and USB/QC Diagnostic ports only" which seems ominous), but under the phone column I only get "No Phone" or N/A (COM2). This prevents me from moving forward to the "SERVICE PROGRAMMING" step of the process.
I've tried a couple different downloads for the WMODEMDrivers and saw no change. I've tried QPST 2.7.295 (pretty sure it was 295 anyway) and it recognized the ports without me having to uncheck the option mentioned above, but it still showed "No Phone". I'm using \Windows\DMRouter.exe /DIAG to launch diag mode.
Something else that strikes me, but I'm not sure is significant, is that I can list devices in .Fred Task Manager and find $device\GPS1(GPS1 , status unloaded, and if I try to load it I get "The system cannot find the file specified" [VIRSER_GPS.dll]. This seems too obvious though and I'd expect to have heard from others by now if this was the issue. Anyhow, I wouldn't know which dll to try if this was the problem.
I hope you can see that I've researched this pretty thoroughly and I'm dead in the water so to speak. Anyone have a suggestion as to how I should proceed from here in order to get my GPS working again?
|