Commit Graph

8 Commits

Author SHA1 Message Date
082b8d8fa3 msm8974-common: Update GPS config for S
XTRA_SERVER has been changed to LONGTERM_PSDS_SERVER in framework so we follow suit here.

Change-Id: I0a15782e49b1c530f2f0fd8ff991ebb9e1da1403
2022-08-19 09:30:25 +02:00
Kevin F. Haggerty
eb088711d4
Revert "msm8974-common: Move XTRA_SERVER entries to overlays"
* Even though the stock gps_debug.conf says that you put
  customization in fw/b overlays, Q doesn't look to those anymore.
* With XTRA_SERVERs in those overlays you get:
  GpsPsdsDownloader: No PSDS servers were specified in the GPS configuration

This reverts commit 399e9af90a.

Change-Id: Id392cf4a9b91a63a4400e546bc9ba4c32b656ef4
2020-04-25 09:55:35 -06:00
Gareth Kitchen
d3810f950a Localise NTP to improve GPS TTFF
Testing response times to time.android.com from around the globe reveals
in ms:-

Europe			 <30
Middle East		 <68
North America		<150
Johannesburg		 183
Buenos Aires		 220
Tokyo			 226
Sydney			 276
Hong Kong		 285
Brisbane		 295
Mumbai			 349
Beijing			4691
Shanghai		4906
Russia			 n/a

Whilst time.android.com is NOT used for GPS NTP, North American time servers
are, by specifying north-america.pool.ntp.org as default in the framework,
to align with pixel devices.  I am assuming similar response times to these
servers from around the world.

Great for North America and it appears Europe but it does not address the
global issue. Also, the pool.ntp.org project forbids both hardware and
software vendors from using these default zone names.
http://www.pool.ntp.org/en/vendors.html

It makes sense, therefore, to leverage the ntp.org's existing 'android' vendor
name to make the default ntp server for GPS purposes:
1.android.pool.ntp.org this will return a random but accurate NTP server in
close geopraphic proximity to the device.

Testing on my own build in the UK seems to improve hot and cold TTFF
considerably.

Change-Id: I144af45757efa35b32daf034eece6e046d2bde79
2018-07-17 19:28:25 -06:00
Kevin F. Haggerty
399e9af90a msm8974-common: Move XTRA_SERVER entries to overlays
* XTRA_SERVERs are important, right? Like to get the almanac data
  necessary for aGPS. Without the XTRA download, the chip needs to
  collect sufficient navigation messages from the birds to compute
  where they are in order to make sense of the ranging signals.
* Well, it seems that O doesn't like reading these entries from the
  gps.conf file.

  When in gps.conf:
  GpsXtraDownloader: No XTRA servers were specified in the GPS configuration

  When in overlay:
  <that noise doesn't exist>

* This seems to, finally, return GPS fix performance to what we had
  in N.

Change-Id: I70679835ec5dea053c5aa3750acee628906d6390
2018-03-07 06:44:43 -07:00
Kevin F. Haggerty
772578a15a msm8974-common: gps: Import configs from klte-common
Change-Id: I92fbf38ecac658fa69191b89890b79e82e05acec
2018-01-18 04:37:20 -07:00
Kevin F. Haggerty
9433f7ab16 msm8974-common: gps: Import CAF HAL
* https://source.codeaurora.org/quic/la/platform/hardware/qcom/gps
* Tag: LA.BF.1.1.3_rb1.13

Change-Id: Ied5197b459ccc51c8b7c8288a8b1d4a6839685e4
2018-01-18 04:37:20 -07:00
slayher
d9bf9d68f9 Let the specific devices handle GPS. 2014-05-22 21:21:56 -04:00
Christopher R. Palmer
f2767f1956 msm8974-common: Add gps from hlte
Change-Id: I0a3d0df72ac2652ad1d320b31c08b260bcfa5b1c
2014-05-19 20:19:41 -04:00