Odometer is always 0.0, except in one rare case.

[irjayjay]

Your Environment

• Plugin version: 4.15.3
• Platform: Android
• OS version: 13
• Device manufacturer / model: Samsung Galaxy S20 / Nexus S emulator with Android API 34
• Flutter info (flutter doctor):
• Plugin config:

  bg.BackgroundGeolocation.ready(
    bg.Config(
      desiredAccuracy: bg.Config.DESIRED_ACCURACY_HIGH,
      distanceFilter: 1.0,
      disableElasticity: true,
      stopOnTerminate: false,
      startOnBoot: false,
      allowIdenticalLocations: false,
      foregroundService: true,
      logLevel: bg.Config.LOG_LEVEL_OFF,
      preventSuspend: true,
      heartbeatInterval: 5,
      autoSync: true,
      debug: kDebugMode,
      showsBackgroundLocationIndicator: true,
      notification: bg.Notification(
        title: APP_NAME,
        text: "Background location tracking active",
        color: "#ff0000",
        channelName: "Location tracking",
        sticky: true,
      ),
      backgroundPermissionRationale: bg.PermissionRationale(
        message: '$APP_NAME collects location data to enable task allocation'
            'and driver tracking even when the app is closed or not in use',
        negativeAction: "Cancel",
        positiveAction: "Open Settings",
        title:
            "$APP_NAME only works correctly if it can access your location all the time.",
      ),
      persistMode: bg.Config.PERSIST_MODE_LOCATION,
      enableHeadless: true,
    ),
  );

Expected Behavior

Odometer should update to a new value whenever location changes and the new value should be returned when doing either BackgroundGeolocation.getCurrentPosition() or inside the callback for BackgroundGeolocation.onLocation().

Actual Behavior

Odometer doesn't update, whether really moving a real device, or using location spoofing(Lockito), or android-emulator location spoofing. Setting distanceFilter to 1 and disableElasticity to true does not help this. In fact, onLocation() very rarely fires.

In fact, onLocation only fires when onLocation callback gets registered. I can see updated locations if I do a BackgroundGeolocation.getCurrentPosition() inside the onHeartbeat, but even this won't update the odometer. I'd expect any latest location fetch would update it.

The only workaround to get the odometer to record anything is to turn a location spoofing app (Lockito) on and off, which triggers an update onLocation too.

Steps to Reproduce

  bg.BackgroundGeolocation.onLocation((bg.Location location) {
    debugPrint('===ODO: ${location.odometer}');
    debugPrint('===mock: ${location.mock}');
    debugPrint('===coords: ${location.coords}');
  });

  Future.delayed(Duration(seconds:3)).then((){
    bg.BackgroundGeoLocation.setOdometer(0);
  });

  Future.delayed(Duration(seconds:30)).then((){
    bg.BackgroundGeoLocation.odometer.then((odometer) {
     debugPrint('=== odometer: $odometer');
    });
  });

Context

Trying to record the odometer readings of a driver at the end of a trip.

[christocracy]

Go outside and test on a real device.

[irjayjay]

If you read what I posted, you'll see that I did. In fact, I drove all the way to the shops and back and the odometer ended up on 0.0.

In another issue on here you told the person that this library is compatible with location spoofing, so it's interesting that you're telling me to go outside now.

[irjayjay]

I just tried again. Walked with my laptop and phone connected in debug mode. I could hear the debug audio prompts from the geolocation library, every few meters of movement. It made that iPhone message sound, to indicate movement about 5 times. Finally I triggered to fetch the odometer and it was 0.0 again.

I have a breakpoint set on setOdometer, it never triggered, so it's not that it gets set to 0.0.

I don't understand how the library is getting location updates, yet the odometer doesn't update.

[christocracy]

I suggest you fetch the logs and have a look at them.

see api docs “.emailLog”

[irjayjay]

I figured something out. I tested with a distanceFilter of 3.0 yesterday. But disableElasticity was false. Later I disabled elasticity and it still didn't work, because at that time I think distanceFilter was 10.0.

I had this all work for me with elasticity enabled and distanceFilter 10.0 the other day, but I don't know how. I was walking at a normal pace and according to the calculations, only if I walked faster than 2.5m/s, then it would round up to 5m/s, which would count as 1 x distanceFilter meters travelled. So any time I travel less than 2.5m/s, it's like I'm not moving.

I'd say it should start off with 10.0, then add 10.0 for every 5m/s of speed from there on, otherwise you'll only record something when running or in a vehicle.

So I hit the sweet spot where no location updates would happen. Still weird that I could hear location updates earlier this morning, yet odometer stayed on 0.

Hope this helps future travellers.

[github-actions[bot]]

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