Always flush batch before stopping
There doesn't seem to be any reason not to flush locations before stopping a batch. This is extra location information that has been collected anyways. Test: presubmits Change-Id: I058d9eeefcf70be55b035e4469eb729826ac28da
This commit is contained in:
@@ -1184,6 +1184,7 @@ public class GnssLocationProvider extends AbstractLocationProvider implements
|
||||
mAlarmManager.cancel(mBatchingAlarm);
|
||||
mBatchingAlarm = null;
|
||||
}
|
||||
mGnssNative.flushBatch();
|
||||
mGnssNative.stopBatch();
|
||||
mBatchingStarted = false;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user