Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update wording about high GNSS accuracy applications

Browse Source 
Test: javadoc only
Bug: 199933846
Change-Id: I2517910db88df90d9cafcf0e07b9384a1e9e2ec4
This commit is contained in:
Yu-Han Yang
2021-11-08 11:25:34 -08:00
parent 7fc3b633cf
commit d43b242660
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
location/java/android/location/LocationManager.java
View File

@@ -183,7 +183,7 @@ public class LocationManager {
* <p>Locations returned from this provider are with respect to the primary GNSS antenna
* position within the device. {@link #getGnssAntennaInfos()} may be used to determine the GNSS
* antenna position with respect to the Android Coordinate System, and convert between them if
* necessary. This is generally only necessary if working with high accuracy GNSS results.
* necessary. This is generally only necessary for high accuracy applications.
*
* <p>The extras Bundle for locations derived by this location provider may contain the
* following key/value pairs:
@@ -1459,7 +1459,7 @@ public class LocationManager {
* <p>Locations returned from {@link #GPS_PROVIDER} are with respect to the primary GNSS antenna
* position within the device. {@link #getGnssAntennaInfos()} may be used to determine the GNSS
* antenna position with respect to the Android Coordinate System, and convert between them if
* necessary. This is generally only necessary if working with high accuracy GNSS results.
* necessary. This is generally only necessary for high accuracy applications.
*
* <p>When location callbacks are invoked, the system will hold a wakelock on your
* application's behalf for some period of time, but not indefinitely. If your application