[Help Wanted]: What is the recommended, industry-standard configuration template to achieve with balance between battery optimization (no overnight idle drain) and pinpoint accuracy on-demand?

[leul-aura]

Required Reading

• Confirmed

Plugin Version

4.19.3

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

ALL

Device operating-systems(s)

ALL

React Native / Expo version

0.83.0

What do you require assistance about?

Question / Advice Requested

We are building application and want to achieve the absolute best balance between battery optimization (no overnight idle drain) and pinpoint accuracy on-demand.

Based on our recent Android Battery Historian logs, we noticed heavy background drain when tracking aggressively. We are planning to use a hybrid architecture: keeping the app in a low-power state by default, and escalating to high precision.

What is the recommended, industry-standard configuration template to achieve this with the SDK?

[Optional] Plugin Code and/or Config

{
  url: "",
  autoSync: true,
  
  // Buffering locations to save cellular radio tail-state drain
  autoSyncThreshold: 10, 
  batchSync: true, 

  // Default low-power background tracking
  desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_MEDIUM, 
  distanceFilter: 50, 
  stopTimeout: 3,

  // Background / Foreground state management
  stopOnTerminate: false,
  startOnBoot: true,
  enableHeadless: true,
  
  notification: {
    title: "Location sharing active",
    text: "Sharing location",
    channelName: "Location Tracking",
    sticky: true,
    priority: BackgroundGeolocation.NOTIFICATION_PRIORITY_LOW
  }
}

[Optional] Relevant log output

[christocracy]

There is no standard. When the SDK is in the moving state, it's consuming just as much energy as following a driving route in a Maps app.

HTTP requests consume more energy / second than GPS. If you want to reduce energy usage, reduce the number of http requests.

For example, Batched uploads can reduce the number of http requests your app performs.

distanceFilter controls the sampling rate of locations. The more locations you record, the more http requests will be performed.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.