Phone app guide
Troubleshooting and contacting Litro
Litro suggested the wrong vehicle
Open the trip in Activity and correct Vehicle used. Check that the car's Bluetooth device is linked to that profile in Litro and that nearby-device access is available. Linked describes a saved association, not a live connection. Motion-only detection cannot identify a particular vehicle. Connecting to a car now does not establish which car made an older trip.
A trip is missing, starts late or has gaps
Check Activity's period, vehicle and type filters. Then check automatic recording and the setup actions in Settings → Automatic trip recording. Location, background activity and other required access must be available.
Poor reception and operating-system limits can leave gaps. Bluetooth or a saved-place name cannot recreate missing route readings. Avoid clearing data or reinstalling as the first step. Manual recording is available for future drives when location access works.
An old notification cannot open its trip
Wait for the trip to load. If loading fails, use Try again. If the record is no longer available, return to Activity and check the period and filters. Opening a notification does not itself save or change a review.
Two driving legs belong to the same journey
Open either leg in Activity. Use Combine with previous trip, inspect both vehicles, categories and totals, then confirm. Different vehicles or categories need correction before combining. Undo combine restores separate legs; Split at this stop separates a journey at a chosen stop.
Short stops are grouped automatically within the selected window, including motion-only detection. A saved review, End trip, an overnight boundary or a saved journey-end place keeps drives separate. Incompatible vehicle choices, categories or location evidence also prevent grouping. See trip recording.
Back or the keyboard makes editing difficult
Back closes the current sheet before returning to its parent. Dismiss the keyboard to inspect the full form if needed. A cancelled trip start leaves the Activity vehicle filter unchanged. If a problem persists, keep your draft and describe the screen and phone model in Contact; avoid repeated Save taps.
A maintenance reminder is due unexpectedly
Inspect the due date and/or odometer condition in its editor. A mileage-only reminder uses its mileage threshold, not its creation date. Mileage comparisons depend on usable odometer information. Mark work completed only after doing it.
Prices or route results look wrong
Check region, fuel grade, units, observation time and endpoints. The lowest total cost accounts for the comparison assumptions; it is different from the unit pump price. Expand cost details on a route result to inspect its basis. Report an incorrect price from station details.
No available forecast means no predictive direction is published. It does not predict unchanged prices. Use Contact for an app behaviour problem.
A notification did not arrive
Check that the alert or reminder is enabled, then check notification access and the phone's quiet/background settings. Android parking reminders may also need alarm access. Station alerts have delivery limits; a favourite alone does not enable one. Saving a setting does not guarantee system delivery.
Backup or import did not finish
Cancelling the file picker or replacement preview leaves local data unchanged. After sharing a backup, verify the file in the destination you chose. A prepared Android safety copy is local; Litro cannot verify an upload or system restore. Use Retry if preparing the local copy fails. See backup coverage.
Contact Litro
Open Settings → Help → Contact us, or Contact from a relevant help topic. Check the suggested category, enter the required contact fields, and describe your steps, expected result and actual result. App version/build, phone model and an approximate trip time can help; avoid unnecessary private addresses.
Technical diagnostics is optional and can be inspected before sending. It covers app/device and permission information, not private routes or vehicle details. Review your typed message separately. If sending fails, keep the text and retry when connected; do not assume support received it.