Bug: 151896491
Test: local build
Exempt-From-Owner-Approval: This CL update suite name vts-core to vts as
the suite name is updated. This CL won't change test logic or behavior.
Change-Id: I562b4dc50765e953800a814a8fd84a01c1b9352b
Merged-In: I562b4dc50765e953800a814a8fd84a01c1b9352b
- Rename recieverInterSignalBiasNs into interSignalBiasNs, which refers
to the sum of receiver ISB and satellite ISB.
Bug: 150724332
Test: atest VtsHalGnssV2_1TargetTest
Change-Id: Ifae15cb482bc12e793a481fec7847c817ef3c34d
Bug: 147504090
Test: atest VtsHalGnssV2_1TargetTest and manually injecting dummy
measurement corrections from GnssLocationProvider and verifying that
they are received below the HAL (on a cuttlefish implementation)
Change-Id: Ie6df224d63429193b39f06a6b60517f804fccbae
Test: End to end test: run "atest GnssAntennaInfoRegistrationTest" on cuttlefish and watch "adb logcat | grep -i GnssAntennaInfo". Other tests: atest GnssAntennaInfoTest, atest GnssAntennaInfoProviderTest, atest GnssManagerServiceTest, atest VtsHalGnssV2_1TargetTest, atest LocationManagerFineTest.
Bug: 124556515
Change-Id: Ia63a1f5022efdda52ed583a56a50f32807e83130
Test: matest VtsHalGnssV2_1TargetTesti and manually injected
dummy measurement corrections in GnssLocationProvider and
verified that cuttlefish implementation properly recieved
them below the HAL
Bug: 145963440
Change-Id: Ib5eb4f8c759c91b9fa2217ce6658319edd11bb27
VTS test VtsHalGnssV1_0Target#GnssHalTest.GetAllExtensions tests that
IGnss::getEnxtensionGnssDebug returns an actual extension. Make an
exception for automotive devices.
Bug: 143966170
Test: ran VtsHalGnssV1_0Target on Volvo IHU
Change-Id: I1588099a5be704c7869d6d5e8c0312d8b498bb95
- IRNSS was added in GNSS HAL v2.0, and its svid range was not specified
at that time. The existing client implementations wouldn't be broken
because they either don't support IRNSS yet or already use such a range
(specified in IRNSS ICD v1.1).
Bug: 147675678
Test: doc only and builds
Change-Id: If86555bf7d3019428d80299043c52ea81aa34bc5
Before setting constellation blacklist, the location report should
be stopped first. Otherwise, the sv status which contains blacklist
constellation is still reporting and may be counted in checking
SvList. According to the comments of this case, location should be
turned off as 2a step.
Also adding another test that a blacklist request that comes in
while tracking is started, takes effect after a stop/start cycle.
Bug: 144675840
Test: on device
Change-Id: I975d6036c742b8b825c742dca8fdcfe1dc1c1ee9
Merged-In: I04894426e8384d25f2b5e269961a9cf051cab40f
Before setting constellation blacklist, the location report should
be stopped first. Otherwise, the sv status which contains blacklist
constellation is still reporting and may be counted in checking
SvList. According to the comments of this case, location should be
turned off as 2a step.
Also adding another test that a blacklist request that comes in
while tracking is started, takes effect after a stop/start cycle.
Bug: 144675840
Test: on device
Change-Id: I04894426e8384d25f2b5e269961a9cf051cab40f
