Update verizon PRI and Sprint AGPS

[taidan]

Sorry for the double post

[taidan]

Originally Posted by fredcatsmommy

I've been told it's very dangerous to use another carrier's prl file. I finally got locks in seconds this afternoon, after making a couple of changes. First, in the registry I changed the SUPL AGPS/ServerIP value from 95.207.101.126 to 172.25.8.100. With that change I noticed that I picked up more satellites, but still no lock. (I have an extra non-sprint vogue that I've been experimenting with so I was able to compare my xv6900 with the changes to the alltel without the changes). Then I added the files that I've attached in the .zip file to the Windows directory. Once the files are in \Windows, just click on 1_SP_AllowCertificateInstall.cpf and 3_SecurityOff.cpf. With 2_SdkCerts.cab, click on it and it will install itself. Soft reset. After that I had locks instantaneously on the device, whereas with the other that I hadn't made those changes, no locks. These files were posted on ppcgeeks shortly after the alltel upgrade, and worked to make the gps work. Obviously use at your discretion, but I've not had a problem.

Thanks man ill try that out.

30 sec to lock is slow, sprint users are getting 5 to ten second ones...

[taidan]

Hmm, I followed them to the t, still no 5 to 10 second locks. I gave up after alittle bit. Does my data connection need to be active? what are you using to prime? any other settings that you might have changed? and last is this 5-7 seconds after a longer initial cold lock?

thanks for your help

[scuccia]

Originally Posted by fredcatsmommy

I've been told it's very dangerous to use another carrier's prl file. I finally got locks in seconds this afternoon, after making a couple of changes. First, in the registry I changed the SUPL AGPS/ServerIP value from 95.207.101.126 to 172.25.8.100. With that change I noticed that I picked up more satellites, but still no lock. (I have an extra non-sprint vogue that I've been experimenting with so I was able to compare my xv6900 with the changes to the alltel without the changes). Then I added the files that I've attached in the .zip file to the Windows directory. Once the files are in \Windows, just click on 1_SP_AllowCertificateInstall.cpf and 3_SecurityOff.cpf. With 2_SdkCerts.cab, click on it and it will install itself. Soft reset. After that I had locks instantaneously on the device, whereas with the other that I hadn't made those changes, no locks. These files were posted on ppcgeeks shortly after the alltel upgrade, and worked to make the gps work. Obviously use at your discretion, but I've not had a problem.

Who's AGPS server is 172.25.8.100?

[fredcatsmommy]

Originally Posted by scuccia

Who's AGPS server is 172.25.8.100?

don't know but I noticed an immediate difference in finding satellites when I made the change. It did not, however, fix the no lock problem. the other changes I described above did. Maybe it's a fluke since another ppcgeeker didn't get the same results.

[scuccia]

Originally Posted by fredcatsmommy

don't know but I noticed an immediate difference in finding satellites when I made the change. It did not, however, fix the no lock problem. the other changes I described above did. Maybe it's a fluke since another ppcgeeker didn't get the same results.

Just found that it's Bell's AGPS server.

[fredcatsmommy]

Interesting - just got a hold of the registry settings for SUPL AGPS from a sprint vogue, and in addition to have a different ServerIP (195.207.101.126), it also has a Dword value that I didn't have: "EnablePDEIPFromNV "=dword:00000001.

[windorabug]

Quote:
Originally Posted by fredcatsmommy
I've been told it's very dangerous to use another carrier's prl file. I finally got locks in seconds this afternoon, after making a couple of changes. First, in the registry I changed the SUPL AGPS/ServerIP value from 95.207.101.126 to 172.25.8.100. With that change I noticed that I picked up more satellites, but still no lock. (I have an extra non-sprint vogue that I've been experimenting with so I was able to compare my xv6900 with the changes to the alltel without the changes). Then I added the files that I've attached in the .zip file to the Windows directory. Once the files are in \Windows, just click on 1_SP_AllowCertificateInstall.cpf and 3_SecurityOff.cpf. With 2_SdkCerts.cab, click on it and it will install itself. Soft reset. After that I had locks instantaneously on the device, whereas with the other that I hadn't made those changes, no locks. These files were posted on ppcgeeks shortly after the alltel upgrade, and worked to make the gps work. Obviously use at your discretion, but I've not had a problem.

These changes did nothing to improve my GPS. If anything its made it worse.

I am using OMJ6.1 gps/rev-a and xv6900

[taidan]

Originally Posted by windorabug

These changes did nothing to improve my GPS. If anything its made it worse.

I am using OMJ6.1 gps/rev-a and xv6900

I second that.

[fredcatsmommy]

Originally Posted by fredcatsmommy

Interesting - just got a hold of the registry settings for SUPL AGPS from a sprint vogue, and in addition to have a different ServerIP (195.207.101.126), it also has a Dword value that I didn't have: "EnablePDEIPFromNV "=dword:00000001.

I added the EnablePDEIPFromNV to my registry and changed back to the Sprint ServerIP, and it is sweet. Locks inside my office in seconds- something that hasn't happened before. I did some reading online and apparently for aGPS to work a PDE ip address is needed. I don't claim to understand this stuff, but it seems to be working for me.

update: just made the same registry changes to the alltel vogue, which stopped getting locks after I had cooked the files into a rom last night. Locks on five satellites after a soft reset after making the registry changes.