Odometer Accurate on Emulator but Inconsistent on Real Device

[AnasEspl]

Required Reading

• Confirmed

Plugin Version

4.19.0

Mobile operating-system(s)

• iOS
• Android

Device Manufacturer(s) and Model(s)

Vivo v29e

Device operating-systems(s)

Android 15

React Native / Expo version

0.71.8

What do you require assistance about?

The odometer value is accurate on the emulator (Extended Controls), but on a real device it sometimes shows incorrect Odometer readings.

[Optional] Plugin Code and/or Config

await BackgroundGeolocation.ready({
      reset: false,
      debug: false,
      logLevel: BackgroundGeolocation.LOG_LEVEL_OFF,
      desiredAccuracy: accuracy,
      distanceFilter: 10,
      stopTimeout: 5,
      locationAuthorizationRequest: 'Always',
      autoSync: true,
      maxDaysToPersist: 14,
      stopOnTerminate: false,
      startOnBoot: true,
      enableHeadless: true,
      notification: { title:'', text:'', channelName:'SilentTracking', channelImportance:0, priority:-2, sticky:true },
    });      


 BackgroundGeolocation.getState().then(state => {
        setIsTracking(state.enabled);
        setOdometer(state.odometer || 0);
      });

[Optional] Relevant log output

[christocracy]

It's not surprising that results vary with real dirty, world data vs clean, simulated data.

[anasSheikh2]

However, I’m still seeing significantly inconsistent odometer values on real devices in normal outdoor conditions (open sky), compared to the expected driving distance. Sometimes the odometer under-calculates or over-calculates distance even when GPS accuracy values seem good.
I'm already using:
DESIRED_ACCURACY_NAVIGATION
distanceFilter: 10
stopOnTerminate: false
startOnBoot: true
persist: true and getOdometer() approach
The behavior improves on emulator and occasionally on real devices but not consistently.
Could you please guide if there are any specific settings, recommended best practices, or diagnostic steps to reduce drift/error in real-world odometer calculation?
Also, is there a preferred way to reset and use odometer for trip-based tracking so real-environment error is minimized?
Thank you — any suggestions would be appreciated.