My Rides

Everything you’ve recorded and everything you’ve imported lives in one list, reached from the menu under My Rides. From here you can put a ride back on the map, read its numbers, colour it by how hard you were riding, share it, or set off along it again.

Importing a GPX

Import GPX at the bottom right opens your phone’s file picker. The picker shows all your files, not only GPX — Android has no reliable file type for GPX, and a picker filtered to one would hide exactly the files you’re after, including anything downloaded from Gmail. So NavForge checks after you choose instead: pick something that isn’t a GPX and you’ll get Import cancelled or file unreadable and nothing is imported. Import is a premium feature — the button carries a padlock and turns amber when your subscription isn’t active.

Two things can happen before the import finishes:

• You’ve imported it before. The app compares the first coordinate of the incoming file against what you already have, so a file renamed by your browser or arriving as an email attachment is still recognised. You get Track already imported with Cancel and Replace.
• The route is outside your downloaded maps. You get Map not downloaded naming the region and its size. Choose the download and you’re taken to the download screen; choose Cancel and the import is thrown away.

Opening a GPX from another app

You don’t have to start from the picker. A GPX file anywhere on your phone can be handed straight to NavForge: tap the attachment in Gmail and choose Open with, or use Share from the Files app, Drive or anything else and pick NavForge from the list. The file is imported on the spot and a confirmation appears at the bottom of the screen — Imported: followed by the ride’s name. If the file turns out not to be a readable GPX, it says Could not read the shared GPX file instead.

What the three dots offer

• Show on map — draws the ride over the map in green. Where a recording had auto-pause breaks, the stopped sections are drawn in grey so you can see where you sat still.
• Navigate this route — ride it again, covered below.
• Full stats — the numbers for that ride.
• Analytics overlay — the colour version, covered below.
• Export GPX — hands the file to Android’s share sheet, so it can go to email, a messaging app or your cloud drive.
• Plan for a date — pins it to a date on the calendar so you can load it on the day.
• Delete — confirms first.

The same seven actions follow the ride wherever it appears — a ride’s card on the calendar carries the identical set. The one that comes and goes is the analytics overlay: it needs the lean and speed readings, so it only appears on rides NavForge recorded itself and on imports of NavForge’s own exports.

Import, navigate, export, plan-for-a-date and the analytics overlay are all premium. Each carries a padlock in the menu when your subscription isn’t active.

Riding a saved route again

Tap Navigate this route and a card appears first, showing the trip and working out where you’re standing relative to it. The buttons on the card change with your position, so you’re choosing what happens rather than being guessed at:

1. At the start of the ride

   Start Navigation follows the recorded line exactly — the same corners, the same dirt detour, the same wrong turn you decided you liked. Nothing is re-planned, so nothing gets smoothed onto the nearest sealed road. If the ride is a loop that starts and ends where you are, the button reads Start loop.

2. Away from the start — beyond about half a kilometre

   Start Navigation gives you road guidance to the start of the ride first. Once you’re within about a hundred metres of it, the app swaps over to the recorded line by itself and carries on. You don’t need to stop and tap anything again.

3. At the far end of the ride

   The card offers Reverse the trip — the recorded line flipped end to end, so you ride it home the way you came. No re-planning here either.

4. Somewhere along the middle of it

   You get Pick up from here, which joins the ride at the closest point to you and follows the rest of it, or Route to trip start if you’d rather be guided back to the beginning and ride the whole thing.

Cancel on the card closes it and nothing else happens. If the route worked out to reach the start is much longer or much shorter than the ride itself, you’ll see Route differs from track explaining the two distances, with Navigate anyway if you’re happy. A file with fewer than two usable points gives Track too short to navigate.

The analytics overlay

This one needs the lean and speed readings that only NavForge writes, so it appears on rides NavForge recorded — and on imports of NavForge’s own exports, which carry those readings with them. Files from other apps don’t have them, so it isn’t offered there. It redraws the ride in three colours:

• Green — under 15° of lean and under 60 km/h.
• Amber — 15° to 35° of lean, or 60 to 100 km/h.
• Red — over 35° of lean, or over 100 km/h.

A warning marker is dropped at every hard-braking event, and a panel over the map gives you max and average lean, max and average speed, the number of hard brakes, total climb, the hardest braking force and the ride duration.

Speed alone can turn a section red without you leaning at all, so a stretch of motorway shows up the same colour as a hard corner. Read the two numbers together rather than treating the colour as a score.

Tidying up

The tick-list icon in the top bar — or a long press on any row — puts the list into selection mode. Tick as many rides and logs as you like and the top bar offers Delete (3), with a confirmation that spells out what’s about to go. It cannot be undone.

Underneath your rides you may see a GPS DEBUG LOGS section. These are plain text files the app writes for itself — a fresh one each time you open NavForge, whether or not you record anything. They are what makes a problem report useful, so if something went wrong on a ride, the log from that session is the thing to send. Share CSV sends one on; deleting them doesn’t touch your rides.