My trips aren't recording

Automatic trip recording depends on the phone's location and motion permissions staying on in the background. Here's what to check, in the order worth checking it.

Available onDriveCruiseTurbo— including the free plan

Can't find this in your app? Your business owner can switch the Logbook module off, which hides it for everyone — there's no message when that happens. An owner or admin can turn it back on in Settings → Business settings → Active Modules.

Almost every case of missing trips comes down to the same thing: the phone stopped letting the app see location while it was in the background. Both iOS and Android are aggressive about this, and both do it quietly.

Axlerun now watches for the commonest cause. If location isn't set to Always, or motion access is off, a banner on Home says so and tells you which setting to change. If you've dismissed it, it comes back when the situation changes. No banner doesn't prove nothing is wrong, though — work through the steps below if trips are still missing.

Work through these in order. The first two fix the large majority.

1. Location permission must be "Always"

Background trip recording needs location access all the time, not just while the app is open. "While using the app" looks like it's granted, and it is — but the moment the driver locks the phone and puts it in the cradle, recording stops.

  1. iPhone: Settings → Axlerun → Location → Always. Turn on Precise Location too.

  2. Android: Settings → Apps → Axlerun → Permissions → Location → Allow all the time.

iOS sometimes downgrades this on its own after an update, or prompts the driver with "keep allowing?" and quietly takes it away if they don't answer. If trips stopped after a phone update, check this first.

2. Battery optimisation (Android)

Android's battery saver will freeze background apps to save power, which stops recording mid-trip. Axlerun needs to be exempt.

  1. Settings → Apps → Axlerun → Battery.

  2. Choose Unrestricted (some phones call this "Don't optimise" or "No restrictions").

Samsung, Xiaomi, OPPO and Huawei phones add their own layer on top of Android's. If you have one, also look for a "protected apps", "auto-start" or "sleeping apps" list and make sure Axlerun isn't in it.

3. Motion & fitness

Trip detection uses the phone's motion sensor to notice driving has started. If motion access is off, recording can be late or miss short trips entirely.

  1. iPhone: Settings → Axlerun → Motion & Fitness → on.

  2. Android: Settings → Apps → Axlerun → Permissions → Physical activity → allow.

4. Ask us to check

If the permissions above all look right and trips still are not recording, we can see what the operating system is actually handing the app, which is not always what the settings screens claim.

Open the Support menu and choose Report an issue. That sends us the diagnostics with your report, so we can tell you which permission is the one causing it rather than asking you to work through them again.

Still nothing?

A few less common causes:

  • The driver has no vehicle allocated. Trips need a vehicle to record against. Check the driver has one assigned.
  • Low Power Mode / Battery Saver is on. Both suspend background location.
  • The trip was too short. Very brief moves may not register as a trip.
  • Tracking schedule. If your business uses schedule-based logging, recording only runs inside the windows you've set — trips outside them are ignored by design.

If none of that explains it, send us the vehicle, the driver and roughly when the trip happened, and we'll look at what reached our end.

Trips that were recorded but landed on the wrong vehicle aren't lost — they can be moved. See A trip is missing or on the wrong vehicle.

Last updated Sat Sep 19

Still stuck?

Email us and a real person will answer — Mon–Fri, 9am–5pm AEST.

Contact us