Also updated the following
- remove carrierFrequencyHz since signalType already includes it.
- update default implementation's mockMeasurement.
Bug: 173797017
Test: on cuttlefish
Change-Id: I60b11f51c5cf414b197ac9ca248a55c2dc1352a1
This CL introduces a new lshal debug command for GNSS HAL
location [lat=..] [lon=..] [ele=..] that allows changing
the mock location provided by GNSS HAL to clients
This can be used manually to configure a single mock location,
or in a scripted scenario to, e.g., supply a set of locations
from a GPX file to simulate a moving device
Bug: None
Test: set different locations via command line to Cuttlefish device, e.g.
$ adb shell lshal debug android.hardware.gnss@2.1::IGnss/default location lat=46.6317 lon=-114.0789
Change-Id: I7217c59f66f1ee7f5a9bd3f3dd3af7be4b43c024
In default implementation, both AIDL HAL and the v2.1 HIDL HAL services
are running in the same process. The HIDL HAL implementation is able to
interact with the AIDL HAL implementation.
Bug: 168111993
Bug: 150192654
Test: on cuttlefish
Change-Id: Ib2770780b62a939f6ca447dfb6a6ab888c526fec
According to the Q CDD, an Android Automotive OS device is not required
to support GnssMeasurements.
Bug: 161549048
Test: atest VtsHalGnssV1_0TargetTest VtsHalGnssV2_0TargetTest VtsHalGnssV2_1TargetTest
Change-Id: Idcd59f36ca2ea28925f6766a7abcdf7b6ad0f0ff
In the old logic, if /dev/gnss0 doesn't report location, it will fail back
to the default mock location. Now we change to only report default location if /dev/gnss0 is
not present.
Test: launch_cvd --start_gnss_proxy
Change-Id: Ie1026d5b4dd3e3c2ed1e2107232bcb94c3ba5079
Change-Id: I787b71d80be7875fc594d17b4296e7d28d9c2f5a
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: I0a5030cbeeb4bbc45000157414582117d8abbae9
Test: Added following kernel cmdline and tested on local CF
gnss_cmdline.serdev=serial8250/serial0/serial0-0
gnss_cmdline.type=0
serdev_ttyport.pdev_tty_port=ttyS1
Change-Id: I3766c31672aa91341403105759b2fd997e7f8879
- 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
-Moved GNSS callback event queue class from VTS 2.0 code
into common library that is shared with all GNSS VTS tests.
-Modified VTS 1.1 code to reuse GNSS callback event queue in
order to address potential issues noted in b/131869042 and
also to later extract common code from VTS 1.1 and VTS 2.0
into common library.
Bug: 136515339
Test: atest VtsHalGnssV2_0TargetTest
atest VtsHalGnssV1_1TargetTest
Change-Id: I9356e7653f9784a9149b2c2bd6307750e9cc56b3
