Evolution-x/hardware_interfaces
1
0
Fork 0
mirror of https://github.com/Evolution-X/hardware_interfaces synced 2026-02-01 16:50:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify HAL doc of full tracking

Browse Source 
Bug: 257549183
Test: doc update only
Change-Id: I35a0736c0939033a588aa28e77f9186e3d59ce6d
This commit is contained in:
Yu-Han Yang
2022-11-22 21:30:28 +00:00
parent e2f39c9ca5
commit 5d0550c572
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
gnss/aidl/android/hardware/gnss/GnssData.aidl
View File

@@ -104,7 +104,7 @@ parcelable GnssData {
* True indicates that the GNSS chipset switches off duty cycling. In such mode, no clock
* discontinuities are expected and, when supported, carrier phase should be continuous in good
* signal conditions. All non-blocklisted, healthy constellations, satellites and frequency
* bands must be tracked and reported in this mode.
* bands that are meaningful to positioning accuracy must be tracked and reported in this mode.
*
* False indicates that the GNSS chipset optimizes power via duty cycling, constellations and
* frequency limits, etc.

6
gnss/aidl/android/hardware/gnss/IGnssMeasurementInterface.aidl
View File

@@ -36,9 +36,9 @@ interface IGnssMeasurementInterface {
* If true, GNSS chipset must switch off duty cycling. In such mode no clock discontinuities
* are expected and, when supported, carrier phase should be continuous in good signal
* conditions. All non-blocklisted, healthy constellations, satellites and frequency bands
* that the chipset supports must be reported in this mode. The GNSS chipset is allowed to
* consume more power in this mode. If false, API must optimize power via duty cycling,
* constellations and frequency limits, etc.
* that are meaningful to positioning accuracy must be tracked and reported in this mode.
* The GNSS chipset is allowed to consume more power in this mode. If false, API must
* optimize power via duty cycling, constellations and frequency limits, etc.
*/
boolean enableFullTracking;