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

Always call stopMeasurementCollection before startMeasurementCollection

Browse Source 
Bug: 253453668
Test: manual
Change-Id: I9f85c6be7a79540fd5fd8b851695c0de1742853d
This commit is contained in:
Yu-Han Yang
2022-10-17 23:37:09 +00:00
parent 2d054595f3
commit d30c1cea07
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
services/core/java/com/android/server/location/gnss/GnssMeasurementsProvider.java
View File

@@ -115,6 +115,16 @@ public final class GnssMeasurementsProvider extends
if (request.getIntervalMillis() == GnssMeasurementRequest.PASSIVE_INTERVAL) { if (request.getIntervalMillis() == GnssMeasurementRequest.PASSIVE_INTERVAL) {
return true; return true;
} }
// The HAL doc does not specify if consecutive start() calls will be allowed.
// Some vendors may ignore the 2nd start() call if stop() is not called.
// Thus, here we always call stop() before calling start() to avoid being ignored.
if (mGnssNative.stopMeasurementCollection()) {
if (D) {
Log.d(TAG, "stopping gnss measurements");
}
} else {
Log.e(TAG, "error stopping gnss measurements");
}
if (mGnssNative.startMeasurementCollection(request.isFullTracking(), if (mGnssNative.startMeasurementCollection(request.isFullTracking(),
request.isCorrelationVectorOutputsEnabled(), request.isCorrelationVectorOutputsEnabled(),
request.getIntervalMillis())) { request.getIntervalMillis())) {