ANOTHER VZW GPS thread (read before assuming I'm a b00n)

[rainabba]

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
  • Coke 0.40
  • Sprint ROM for Vogue version 1.12.651.1 radio(?) 2.13.00
  • Coke 2.31 Unlocker
  • Verizon ROM for Vogue version 3.14.605.1 with Radio 3.37.77
• For the second set of steps to modify QPST and make final changes to get GPS working for your current ROM
  • aGPS cab to be applied once your final ROM has been flashed and QPST changes made

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.

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?

[spetrillo]

Originally Posted by rainabba

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?

Ok so now the obligatory questions:

1) When you were speeding along with GPS were you running the same ROM, or have you upgraded recently and GPS stopped?
2) What version of the PRI are you running?
3) Which IP are you using for the PDE server?

Steve

[rainabba]

Originally Posted by spetrillo

Ok so now the obligatory questions:

1) When you were speeding along with GPS were you running the same ROM, or have you upgraded recently and GPS stopped?
2) What version of the PRI are you running?
3) Which IP are you using for the PDE server?

Steve

1. I'm not positive when it stopped working (which of course makes this all the more difficult.
2. I'm running PRI 2.03_002 and PRL 51309 (in case that's relevant)
3. My Reg settings are as follows:

• ServerIP = 66.174.95.132
• ServerPort = 8888
• EnableAGPS = 1
• EnableGPSSmartMode = 1
• EnalePDEIPFromNV = 0
• GPSMode = 4

[ColoTouch]

Same boat. I am on WM 6.5 21202 with VZW. It seems like GPS stopped working on 6.1 OS about a week ago so it may not be ROM related.

IP: 66.174.95.132 (set with QPST as well)
8888
GPSMode 4
EnableAGPS 1

I have tried Tellus' IP, etc.

3.47.30 radio

[spetrillo]

Originally Posted by rainabba

1. I'm not positive when it stopped working (which of course makes this all the more difficult.
2. I'm running PRI 2.03_002 and PRL 51309 (in case that's relevant)
3. My Reg settings are as follows:

• ServerIP = 66.174.95.132
• ServerPort = 8888
• EnableAGPS = 1
• EnableGPSSmartMode = 1
• EnalePDEIPFromNV = 0
• GPSMode = 4

Ok so are you running the Valhalla cab? If not then I know exactly what is going on.

So your PRI is 2.03.002. This is the Verizon locked down PRI, meaning Verizon locked down GPS capabilities to everything except their VZ Navigator product. The Valhalla cab gives users running the locked down PRI the ability to somewhat circumvent this. Apps like Google Maps will work fine with this setup. Apps like iGo, or any app that relies on direct COM port visibility will not operate, since they cannot get the COM port to use.

You also have the VZW PDE server IP, which if you see the thread on VZW GPS not working it will tell you to use the Telus PDE server. I do not believe the VZE server has come back up yet, but I could be wrong.

Were you running the VZW stock ROM at one time?

Steve

[rainabba]

Originally Posted by spetrillo

Ok so are you running the Valhalla cab? If not then I know exactly what is going on.

So your PRI is 2.03.002. This is the Verizon locked down PRI, meaning Verizon locked down GPS capabilities to everything except their VZ Navigator product. The Valhalla cab gives users running the locked down PRI the ability to somewhat circumvent this. Apps like Google Maps will work fine with this setup. Apps like iGo, or any app that relies on direct COM port visibility will not operate, since they cannot get the COM port to use.

You also have the VZW PDE server IP, which if you see the thread on VZW GPS not working it will tell you to use the Telus PDE server. I do not believe the VZE server has come back up yet, but I could be wrong.

Were you running the VZW stock ROM at one time?

Steve

3.02 is locked down? I thought that was the working one? I will seek out and try the other IP, but that is for aGPS only right? I'm not getting ANY data even after being in clear skys outside for 5 minutes.

I was running stock when I first got the phone. It's been flashed MANY times since then.

Is ipstLab2 the replcement for PPST? How do either of these relate to GPS issues?

Where do I find an alternate/better PRI, and how are they typically installed?

EDIT: No valhalla cab. Not even familiar with it.

[rainabba]

I just found a thread that I believe addresses this very issue so until/unless I post here again, I suggest you check it out: http://forum.ppcgeeks.com/showthread.php?t=61493

[spetrillo]

Originally Posted by rainabba

I just found a thread that I believe addresses this very issue so until/unless I post here again, I suggest you check it out: http://forum.ppcgeeks.com/showthread.php?t=61493

Yes but this talks about using the Telus PDE server instead of the VZW PDE server. Actually it looks like the VZW PDE is back up now. Not sure how long it will last though.

I dont think this addresses your issue with the PRI. The PRI you are running is the VZW locked down PRI. Only VZ Navigator will run natively with this PRI. The Valhalla cab over at XDA by Skywing fixes this issue, but only allows apps that do not use the COM port directly, like Google Maps, to operate.

If you want to get back to basics and use the GPS without being restricted by VZW then you need to jump through a few hoops, of which I can you with that.

Steve

[jadesse]

I am Not running the Valhalla cab & my GPS works fine. However my phone is unlocked with 2.31 & running NFSFAN's 1.15 ROM.

Try this thread but it will void your warranty if aplicable.
http://wiki.ppchaven.com/index.php?t...IX_VERIZON_GPS

You can probably skip the last step in the process. Since you probably let the customizations run you'll have to go back to a pre-GPS radio to get the GPS working.

[spetrillo]

Originally Posted by jadesse

I am Not running the Valhalla cab & my GPS works fine. However my phone is unlocked with 2.31 & running NFSFAN's 1.15 ROM.

Try this thread but it will void your warranty if aplicable.
http://wiki.ppchaven.com/index.php?t...IX_VERIZON_GPS

You can probably skip the last step in the process. Since you probably let the customizations run you'll have to go back to a pre-GPS radio to get the GPS working.

This link actually does not work. Since you already have the 2.03 PRI you need a ROM that puts back the 1.37 PRI. I tried this last night. You need to add the Bell ROM flash at line 4 and move everything else down.