commit ca9b857c915460896b34f1cbe9d99b689ef1ee53
author Gareth Kitchen <gkitchen@cookability.biz> Tue Jul 17 09:58:29 2018 +0100
committer Vishalcj17 <vishalcj@aospa.co> Thu Nov 05 20:04:48 2020 +0530
tree 221fae95c1e1469669f94d824da5922d99d990da
parent 1f41a06e6d8390cf0e07fdee817e42ef36f3e752

laurel_sprout: gps: 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