[HD2 Android Q&A, Help & Troubleshooting and Genera] Jaiy:
File contents

AngelDeath,

First, thanks for doing this work, it certainly helps for me.

But, I'm a bit concerned about the contents of the file you're pushing out to everyone. It contains some errors, and I think it works by accident, rather than by good design.

My first comment is that using specific NTP servers is not a good idea because you are then dependent on that server being available. The whole point of [0123].region.pool.ntp.org is to give users a way of choosing NTP servers near to them without the dependency on specific named servers. In addition, the use of specific named servers may be restricted by their terms of service to people associated with those organizations. I strongly suggest that you remove all the specific named NTP servers and list only the four pool.ntp.org servers for each country/region file you're publishing.

Second, the SUPL entries. SUPL is the A-GPS (assisted GPS) Secure User Plane Location protocol.

The entry:

SUPL_HOST=FQDN

is rubbish! The characters FQDN stand for

F

ully

Q

ualified

D

omain

N

ame and should be replaced by an actual domain name (or IP address) of a SUPL server, as is the case in the two entries below this one. Leaving the letters FQDN there means you're configuring nothing. Now, I am not clear whether having this broken entry there would be ignored or, since it's the first SUPL_HOST entry, it would disable the use of SUPL.

Next, the entry:

SUPL_HOST=lbs.geo.t-mobile.com

is also of dubious value. That server is not accessible to me from a non-T-Mobile address, e.g., when I am on Wi-Fi. I suspect that it may be valid only to users on the T-Mobile data network. When I'm on Wi-Fi, and when other non-T-Mobile users use this, they get no SUPL data. This may be why it works for some folk and not for others. Some get the T-Mobile A-GPS SUPL data, others don't. And, I suspect it is working for those who don't get the T-Mobile SUPL data. See below for why.

I suspect that both the above SUPL_HOST entries should be removed from the file. However, doing so would revert folk to just the third SUPL server entry, the one for supl.google.com which is the same as the original file contents. While the supl.google.com server does respond, receiving the SUPL data seems to be the cause of the GPS non-locking problem. It seems that the Gingerbread SUPL handling code is broken which is the cause of this problem in the first place. When you receive A-GPS SUPL data, either from google.com or from t-mobile.com, your GPS doesn't lock. When you DON'T receive A-GPS data, your GPS works in non-assisted manner and it does lock. When everyone is reporting so-called cold lock times of a minute or two and so-called warm lock times of just a few seconds, that is a good indication that their GPS is working non-assisted, i.e., it didn't receive A-GPS SUPL data. I think what is happening is that your accidental inclusion of the two non-working SUPL entries causes A-GPS SUPL to be disabled which causes the GPS to work in non-assisted manner and therefore actually work properly. So, while your first two SUPL_HOST entries should be removed, I suspect the third supl.google.com one should be, too.

On to the SUPL_TLS_HOST entries for the secure SUPL server. You have the same invalid configuration there!

SUPL_TLS_HOST=FQDN

also does nothing. Since you have no valid secure SUPL host configuration entry, you're not using secure SUPL. The CERT file entry therefore also does nothing.

Next, you've added C2K configuration. C2K is another A-GPS protocol, an alternative to SUPL. But... the host c2k.pde.com doesn't exist!!! So, you've configured a non-existent C2K server. Which means this also does nothing.

I think you'd do just as well reducing this file to merely:

NTP_SERVER=0.north-america.pool.ntp.org
NTP_SERVER=1.north-america.pool.ntp.org
NTP_SERVER=2.north-america.pool.ntp.org
NTP_SERVER=3.north-america.pool.ntp.org
INTERMEDIATE_POS=1
ACCURACY_THRES=5000
CURRENT_CARRIER=common
DEFAULT_USER_PLANE=TRUE
REPORT_POSITION_USE_SUPL_REFLOC=1

with the north-america replaced appropriately for each country or region that you publish.

Anyone care to test this simplified file and report back?