Skip to main content

RideDetect – Troubleshooting

Available in: 📱 App

A trip wasn't detected at all​

The most common cause on Android: battery optimization or the manufacturer's own power-saving features kill the app in the background.

  • Set RideBase to "Unrestricted" in the battery settings, or exempt the app from battery optimization.
  • Samsung: Settings → Battery → Background usage → RideBase → "Unrestricted". Xiaomi (MIUI): enable AutoStart for RideBase.
  • Check the permissions: location "Allow all the time" and "Physical activity".

All steps in detail: Setting up on Android.

:::warning Take the in-app warning seriously If a requirement is missing, the RideDetect settings show a notice like "Missing for reliable background detection: …". As long as it's visible, detection is not reliable — fix the listed items via Grant permission or Open settings. :::

Also check under Profile → RideDetect that both Enable RideDetect and Automatic are turned on and no pause is running (otherwise the status badge shows Paused).

The first kilometers are missing​

This is normal and due to the system (iOS and Android): detection only kicks in a few minutes (typically 2–5) after the trip begins, so the first roughly 1–2 kilometers are missing. RideDetect is deliberately designed to save power — instant detection from meter zero just isn't possible that way. If every meter counts: start the trip manually via the Start trip button on the dashboard.

The trip ends too late or not at all​

  • The recording deliberately only ends after the vehicle has been stationary for a few minutes — traffic lights and short stops shouldn't tear the trip apart. A slightly later end is therefore normal.
  • Shortly before the automatic end, the notification "Trip will end shortly – tap to pause" appears — tapping it pauses the trip (e.g. on a ferry), driving on resumes it automatically.
  • In a traffic jam or at walking pace, the recording keeps running — that's intentional.
  • You can always end it yourself: open the live view → Stop recording → e.g. End and save.

Duplicate trips or phantom trips​

  • If the app detects a trip twice (e.g. in addition to an import), it's marked as a Possible duplicate under Unassigned Activities — hide it there via Mark as duplicate. The Data Sources settings also offer Automatically ignore duplicates.
  • If a trip was detected even though you weren't driving yourself (bus, passenger): choose Ignore this trip in the live view — or pause RideDetect beforehand (Today, by the hour, or Permanently), e.g. via Ignore today's trips right when ending.
  • Very short recordings (under roughly 300 m) are discarded by the app on its own.

iOS: trips are detected unreliably​

  1. iOS Settings → RideBase → Location → Always (not just "While Using").
  2. Enable Background App Refresh for RideBase.
  3. Check in the app: Profile → RideDetect → both switches on, no pause active.

Details: Setting up on iOS.

The trip was saved offline​

Without internet, the app reports "Trip saved … will be synced the next time the app is opened". The trip is safely stored locally — just open the app while connected, and it will be uploaded.

Nothing helps?​

Contact support at mail@ridebase.app. Helpful for the analysis: the app keeps diagnostic logs, which you'll find under Profile → Diagnostics → Logs — along with that, describe as precisely as possible when the affected trip took place and what you observed.