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
Change sf early phase offset for 90hz to be early=6.1ms,
early_gl=9ms to give the same ~16ms and ~13ms they had on 60hz.
Bug: 130191039
Test: launch app and observe systraces, frame drop 1.83% -> 0.37%
Test: scrolling on photo with force GL compos and observe systraces,
frame drop 1.61% -> 0.84%
Change-Id: Icbd734d9fa217333741bd625e715eae973a3e368
CNE Hals moved to Factory Hal implementation. Removing
the Hal entries for the same.
CRs-Fixed: 2295302
Change-Id: Ifd7b605e3b9824951e111108c664ec0cde37fe83
- Removed HAL 1.0 entries from manifest as they
are not supported.
- Added Default A2DP HAL 2.0 entry to manifest.
CRs-Fixed: 2472010
Change-Id: Id8da896c99ab0904158715dcf9a74ccf73b77895
Add JNI and libqti_vndfwk_detect module name to product_packages
to specify module to be installed to device. Here explicitly
specify both the core and vendor variant in PRODUCT_PACKAGES.
CRs-Fixed: 2372775
Change-Id: Ic64f5ac0cfbbe9e105a6b48b5bc7687c8d23d7e8
* That way video recording apps will choose
16-bit PCM by default instead of 24-bit
one which happens to have quite low volume
on this device.
Change-Id: I2130c6a759afcd50a985b2f034b5c0b5374287af
(1) runtime enable/disable TUNC
(2) runtime enable/disable PACE
(3) runtime enable/disable constellations
(4) delete all aiding data
(5) config lever arm
Change-Id: I6cffd08e4c6fa45ff8d62bfef2da1156f3b61956
CRs-fixed: 2497326
The gmtime library function is outputting
corrupted UTC time as this function is
not thread safer.
CRs-Fixed: 2571035
Change-Id: Ieed088392e3094eb20fa9b526931a3a89d4f231c
Remove this assigning in gnssSetPositionMode. We shouldn't
assign preferredAccuracyMeters to minDistance, because if
preferredAccuracyMeters is larger than 0, GnssAdapter
will start distance based tracking which is not expected.
Change-Id: I2c2acedd121e02bf9da1136540cc34b9257197fd
CRs-fixed: 2566229
