PPCGeeks

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   HTC Vogue (http://forum.ppcgeeks.com/forumdisplay.php?f=48)
-   -   Verizon GPS not working anymore (http://forum.ppcgeeks.com/showthread.php?t=61493)

Humpa 03-22-2009 01:18 PM

Re: Verizon GPS not working anymore
 
Quote:

Originally Posted by Rangerdave (Post 789429)
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

One simple way to see the IP of a web address is to open a cmd prompt and "ping www.agps.com" (insert web address).

jmichalakjr 03-22-2009 02:08 PM

Re: Verizon GPS not working anymore
 
Nice job guys, after a soft reset, all is good :)

Rangerdave 03-22-2009 02:45 PM

Re: Verizon GPS not working anymore
 
Quote:

Originally Posted by Humpa (Post 789448)
One simple way to see the IP of a web address is to open a cmd prompt and "ping www.agps.com" (insert web address).

I don't think it matters weither it's input as ip or web address. I use net tools to see the info. I have input the information as a web address and it still works fine. I guess the ppc registery can translate it over without issues.

RD

denasqu 03-22-2009 03:14 PM

Re: Verizon GPS not working anymore
 
Quote:

Originally Posted by Humpa (Post 789349)
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. :D

Didn't help for me. Made it worse. But I'm not using Valhalla. Does the Valhalla setup use the QPST fix? (EDIT: never mind. I read gc14's tutorial again and realized Valhalla does not use QPST) I wonder how those QPST settings affect my registry changes? Cuz' they were certainly different.

Maybe it would helpful if everybody involved with this thread shared their relevant setup info and what kind of results their getting. Here is mine.

I get consistent locks outdoors in under 30 seconds. Nada' indoors.
ROM: DrEllisdee v2.1
Radio: Bell 3.42.50
PRI: 1.37_002
Valhalla fix: NO

QPST settings:
PDE IP Address: 66.174.95.132
PDE Port Number: 8888
PDE Transport: IP
Position Calculation: PDE

Registry settings:
[HKEY_LOCAL_MACHINE\Software\HTC\SUPL AGPS]
"ServerIP"="66.174.95.132"
"ServerPort"=8888
"GPSMode"=1
"EnablePDEIPFromNV"=0
"EnableAGPS"=0
"EnableGPSSmartMode"=1
"QosPerformance"=89
"QoSAccuracy"=50
"TimeBetweenFixes"=1
"NumberFixes"=999999999

wmnoobie 03-22-2009 03:23 PM

Re: Verizon GPS not working anymore
 
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

Here is a site that will convert IP to hex or decimal
http://www.kloth.net/services/iplocate.php

denasqu 03-22-2009 03:24 PM

Re: Verizon GPS not working anymore
 
Hmmmm... this post at XDA would indicate that QPST settings override any registry settings. I will be testing this with the Telus setttings later.

Rangerdave 03-22-2009 03:32 PM

Re: Verizon GPS not working anymore
 
1 Attachment(s)
Quote:

Originally Posted by denasqu (Post 789698)
Didn't help for me. Made it worse. But I'm not using Valhalla. Does the Valhalla setup use the QPST fix? I wonder how those QPST settings affect my registry changes? Cuz' they were certainly different.

Maybe it would helpful if everybody involved with this thread shared their relevant setup info and what kind of results their getting. Here is mine.

I get consistent locks outdoors in under 30 seconds. Nada' indoors.
ROM: DrEllisdee v2.1
Radio: Bell 3.42.50
PRI: 1.37_002
Valhalla fix: NO

QPST settings:
PDE IP Address: 66.174.95.132
PDE Port Number: 8888
PDE Transport: IP
Position Calculation: PDE

Registry settings:
[HKEY_LOCAL_MACHINE\Software\HTC\SUPL AGPS]
"ServerIP"="66.174.95.132"
"ServerPort"=8888
"GPSMode"=1
"EnablePDEIPFromNV"=0
"EnableAGPS"=0
"EnableGPSSmartMode"=1
"QosPerformance"=89
"QoSAccuracy"=50
"TimeBetweenFixes"=1
"NumberFixes"=999999999

As far as I know if your running a cooked rom you need to use Gc's cab. Valhallas is for stock.

You might want to reset your registery settings then install this cab. See what happens then go from there.

RD

denasqu 03-22-2009 03:47 PM

Re: Verizon GPS not working anymore
 
Quote:

Originally Posted by Rangerdave (Post 789734)
As far as I know if your running a cooked rom you need to use Gc's cab. Valhallas is for stock.

You might want to reset your registery settings then install this cab. See what happens then go from there.

RD

Thanks but that CAB just changes my registry back the way it was and I know that doesn't work anymore. My GPS is satisfactory now and I don't want to make any drastic changes. The Geek in me is just looking for that amazing aGPS service that I had a week ago. ](*,)

Rangerdave 03-22-2009 03:50 PM

Re: Verizon GPS not working anymore
 
Quote:

Originally Posted by denasqu (Post 789759)
Thanks but that CAB just changes my registry back the way it was and I know that doesn't work anymore. My GPS is satisfactory now and I don't want to make any drastic changes. The Geek in me is just looking for that amazing aGPS service that I had a week ago. ](*,)

I just noticed soemthing verrrrryyyy odd.
The ip I had in there was NOT the verizon ip it should be. it was 195.207.101.126. That ip belongs to somewhere in the Ripe network. Unless I'm looking at the wrong things..

But when I changed the ip to the Verizon ip posted in the list above, it works very strong..

No geeks here..!

RD

denasqu 03-22-2009 05:03 PM

Re: It's back baby!
 
Well that was a nice Sunday afternoon surprise. Now if Missouri just beats Marquette this will be a pretty darn good day!

I get locks inside within 15 seconds and I've pulled the battery a couple times to make sure it's not a fluke. Works fine with Google Maps, Live Search and TomTom. No priming crap.

I first tested the Telus settings with QPST and it didn't work out, plus I started getting date connection PPP errors. So I changed the PositionCalculation to PDE (from "Mobile") with QPST and it's all good. I did have to enter my username and password for the data connection though. Not sure what that was about it and I'm not sure that they were in there before, but data is fine now.

To summarize:
I'm using a custom ROM, no Valhalla, Bell 3.42.50 radio.

I re-ran the QPST fix with these settings:
PDE IP Address = 216.198.139.92
PDE Port Number = 8889
PDE Transport = IP
Position Calculation = PDE

I brought the registry in line with these settings:
[HKEY_LOCAL_MACHINE\Software\HTC\SUPL AGPS]
"GPSMode"=4
"EnableAGPS"=1
"EnableGPSSmartMode"=1

UPDATE: these registry settings are irrelevant. I flashed a new custom ROM and GPS worked immediately without these extra registry entries.
"ServerIP"="216.198.139.92"
"ServerPort"=8889
"EnablePDEIPFromNV"=1


All times are GMT -4. The time now is 02:57 PM.

Powered by vBulletin® ©2000 - 2024, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0