Verizon GPS not working anymore

[prsmithx]

Notes on IP addresses:
0xC3CF657E is 126.101.207.195 which is the default IP address in the gpsOne chipset. You won't get aGPS with this.
0x845FAE42 is 66.174.95.132, which is the Verizon aGPS server which was working until recently.

I was getting locks in 20-30 seconds with 8-11 satellites. Now it take longer to get a first fix (2-8 minutes), with fewer satellites. Sometimes it was taking even longer; once, I let it sit for an hour without getting a lock while Holux GPSViewer was reporting seeing 6 satellites. I disabled aGPS by setting the registry key \HKLM\Software\HTC\SUPL AGPS\EnableAGPS to 0 and now I get a lock with the performance I was getting before I got AGPS working. It's like the AGPS server is not just not working, but is interfering with getting a lock.

Verizon VX6900
Alltel ROM 3.10.671.1
Radio 3.42.30
Stock Alltel ROM reset before customization and installed dcd's Verizon carrier cab.

[Rangerdave]

What I don't get is why don't some people just change the agps server for the mean time? I did and it seems to have given the trick.

Now I did spend soem 2 hours on google looking "agps server" information up and then over at xda and found a registery edit that turns the agps off.
I figured well lets just change the server and the port if need be and there it is.
I'm not so sure about posting the agps server addresses (2 in all) that I found that work on line, such as mokia and obvious others, beceause they will most likely see the data hits and lock it out even further..
RD

[spetrillo]

Originally Posted by Rangerdave

What I don't get is why don't some people just change the agps server for the mean time? I did and it seems to have given the trick.

Now I did spend soem 2 hours on google looking "agps server" information up and then over at xda and found a registery edit that turns the agps off.
I figured well lets just change the server and the port if need be and there it is.
I'm not so sure about posting the agps server addresses (2 in all) that I found that work on line, such as mokia and obvious others, beceause they will most likely see the data hits and lock it out even further..
RD

So what is the consensus on what needs to change? I have tried several things but to no avail. I am not running Valhalla.

Steve

[Humpa]

Originally Posted by Rangerdave

What I don't get is why don't some people just change the agps server for the mean time? I did and it seems to have given the trick.

Now I did spend soem 2 hours on google looking "agps server" information up and then over at xda and found a registery edit that turns the agps off.
I figured well lets just change the server and the port if need be and there it is.
I'm not so sure about posting the agps server addresses (2 in all) that I found that work on line, such as mokia and obvious others, beceause they will most likely see the data hits and lock it out even further..
RD

Yeah, but screw that ... lol
Here is a list of IP's and ports I found with a quick google search. This is from HoFo:

Telus:
PDE IP Address = 216.198.139.92
PDE Port Number = 8889
PDE Transport = IP
Position Calculation = Mobile

Bell:
PDE IP Address: 206.47.201.75
PDE Port number: 8888
PDE Transport: IP
Position Calculation: Mobile

Alltel: (use this for USCC)
PDE IP Address = 205.142.19.100
PDE Port Number = 8888
PDE Transport = IP
Position Calculation = Mobile

MetroPCS:
Server IP Address = 198.17.1.0
Server Port Number = 3425
PDE Transport = IP
Position Calcultation = PDE

Sprint:
PDE IP Address = 68.28.31.49
PDE Port Number = 5017
PDE Transport = IP
Position Calculation = Mobile

Verizon:
PDE IP Address: 66.174.95.132
PDE Port number: 8888
PDE Transport: IP
Position Calculation: Mobile

The Telus one worked for me.
And 216.198.139.92 will be 5C8BC6D8, and the port is 8889
I set my Valhalla mode back to 2 and the HTC enable agps back to 1. Reset and agps appears to work again like normal.

Thanks RangerDave
... BTW, I found that on page 1 of a google search for "agps server ip address"

[denasqu]

Originally Posted by Humpa

... BTW, I found that on page 1 of a google search for "agps server ip address"

Me too. But I'm glad you tested them. Now let's keep this quiet okay.

[joshkeller77]

Originally Posted by spetrillo

So what is the consensus on what needs to change? I have tried several things but to no avail. I am not running Valhalla.

Steve

The problem is this, if Verizon is now using some form of server side authentication it doesn't matter what we do.

Changing the IP address won't do a thing if the new address implements the new firewall, and changing to someone else's aGPS settings doesn't cut it, I have tried Alltel and Sprint to no avail. You are more than welcome to try too.

I am not sure what needs to happen now, but someone with the ability to analyze the packet information using a phone that is using vznav legitimately would be my guess. It would be nice if we knew someone that worked at VZW that really knew something.

I don't know for a fact that any of this is true, I just know that aGPS is broken for a few devices now.

Edit: Will be trying Telus... funny that one would work as it is UK service, right? Thanks for the lead.

[Humpa]

Originally Posted by joshkeller77

The problem is this, if Verizon is now using some form of server side authentication it doesn't matter what we do.

Changing the IP address won't do a thing if the new address implements the new firewall, and changing to someone else's aGPS settings doesn't cut it, I have tried Alltel and Sprint to no avail. You are more than welcome to try too.

I am not sure what needs to happen now, but someone with the ability to analyze the packet information using a phone that is using vznav legitimately would be my guess. It would be nice if we knew someone that worked at VZW that really knew something.

I don't know for a fact that any of this is true, I just know that aGPS is broken for a few devices now.

I have agps working again.

Put all regedits back to the way they were when you had Valhalla and Verizon agps working.

Then just change these and Soft Reset:
HKLM\Software\Valhalla Legends\GPSServer\Mode=2 (the original value)
HKLM\Software\Valhalla Legends\GPSServer\PDEAddress=5C8BC6D8
HKLM\Software\Valhalla Legends\GPSServer\PDEPort=8889

Not sure if any of the other IP's I just posted will work. I didn't try.

[joshkeller77]

Originally Posted by Humpa

I have agps working again.

Put all regedits back to the way they were when you had Valhalla and Verizon agps working.

Then just change these and Soft Reset:
HKLM\Software\Valhalla Legends\GPSServer\Mode=2 (the original value)
HKLM\Software\Valhalla Legends\GPSServer\PDEAddress=5C8BC6D8
HKLM\Software\Valhalla Legends\GPSServer\PDEPort=8889

Not sure if any of the other IP's I just posted will work. I didn't try.

Yup, I think this may be the fix. It is difficult to say until it can have a true cold start after 5 or 6 hours but this is the best it has been for weeks. I am running a Titan BTW not a Vogue and no Valhalla

Humpa, I posted this at XDA too and gave you credit.

[Humpa]

Originally Posted by joshkeller77

Yup, I think this may be the fix. It is difficult to say until it can have a true cold start after 5 or 6 hours but this is the best it has been for weeks. I am running a Titan BTW not a Vogue and no Valhalla

I hadn't used gps since yesterday, and I only tried that Telus IP/port, because the HoFo post I found mentioned that the Telus one worked. I soft reset a few times before I even tried it. And I had only done 2 regedits previously that I had to undo. I only had to fix the Valhalla mode=2 and the HTC supl_gps and set that to enabledagps=1. I never bothered with any of the other regedits because they were irrelevant with agps off.

I got a fix in 4 seconds.

[Rangerdave]

Originally Posted by Humpa

Yeah, but screw that ... lol
Here is a list of IP's and ports I found with a quick google search. This is from HoFo:
The Telus one worked for me.
And 216.198.139.92 will be 5C8BC6D8, and the port is 8889
I set my Valhalla mode back to 2 and the HTC enable agps back to 1. Reset and agps appears to work again like normal.

Thanks RangerDave
... BTW, I found that on page 1 of a google search for "agps server ip address"

I guess I was reading up on what agps "is" so much I missed that one on the first page. The ones I found aren't listed as ip's, just direct web addresses. It prolly dosen't matter. I wonder if you can just set the server to msn.com and it would work..?

Mines working right now I don't wanna try it.

RD