React-native-background-geolocation: Stop location updates when device is stationary

[theebi]

We have a react-native app which drains a lot of battery in background. And I can see my application listed as high battery usage app in the settings. I can see an option saying stopOnStillActivity. I have set it to true but still client says his phone sends location updates when it's in the same place. I'm attaching my config with this.

desiredAccuracy: BackgroundGeolocation.HIGH_ACCURACY,
stationaryRadius: 50,
distanceFilter: 100,
debug: false,
startOnBoot: true,
stopOnTerminate: false,
locationProvider: BackgroundGeolocation.ACTIVITY_PROVIDER,
interval: 10000,
fastestInterval: 10000,
activitiesInterval: 10000,
stopOnStillActivity: true

[mauron85]

Sorry this incomplete report. Missing device info, OS info ... See issue template. Without it I can help.

[gokulanath]

We have using the stationary radius to prevent the number of coordatinates recorded for the device with in the radius. But even when stationary radius given, we are getting the more than one coordinates with in the stationary radius. This occurs mostly in android. Also it happens when we try to switching the app from background to foreground

Environment

• Plugin version: v0.5.0-alpha.32
• Platform: Android
• OS version: 8.1.0
• Device manufacturer and model: One Plus 5T

• React Native version: 0.55.4

  desiredAccuracy: BackgroundGeolocation.HIGH_ACCURACY,
  stationaryRadius: 100,
  distanceFilter: 50,
  notificationTitle: 'Background Tracking',
  notificationText: 'enabled',
  debug: false,
  startOnBoot: false,
  stopOnTerminate: false,
  locationProvider: BackgroundGeolocation.DISTANCE_FILTER_PROVIDER,
  interval: 10000,
  fastestInterval: 5000,
  activitiesInterval: 10000,
  stopOnStillActivity: true,
  maxLocations: 5000

1. 
2. 

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed, because it has not had recent activity. If you believe this issue shouldn't be closed, please reopen or write down a comment requesting issue reopening with explanation why you think it's important. Thank you for your contributions.