Why does the Insta360 Android app get stuck detecting forward direction when I try to add Garmin stats to an X4 video?

Short Answer

In short, this looks less like a Garmin data problem by itself and more like the Insta360 Android editor getting stuck while preparing a Stats overlay for an X4 clip. The key caveats are whether the clip was shot in a Stats-supported mode, whether the Garmin activity has fully synced to Garmin Connect, whether the camera and activity timestamps line up, and whether the current Android app build is misbehaving on your foldable phone. The breakdown below gives you a clean troubleshooting order before you discard the edit or rebuild the clip elsewhere.

Insta360’s own documentation says Stats can use Garmin data, imported FIT or GPX files, phone GPS, or a GPS remote, but it also says some capture modes are not suitable because GPS data cannot be synchronized accurately. That matters because the spinner appears before you can choose the Garmin source; the app may be trying to infer motion direction from the clip and telemetry before it unlocks the dashboard controls.

What To Check First

Start with the source video. If the clip was shot as Timelapse, Starlapse, TimeShift, Slow Motion, or Bullet Time, do not spend hours debugging Garmin. Insta360’s Stats guidance excludes variable-speed modes because the exported video timing no longer matches GPS time in a simple one-to-one way. A normal 360 video or flat action clip is the better candidate for speed, route, altitude, distance, and direction overlays.

Next check the activity data. Garmin Connect should show the exact workout with a GPS track, not just a manual entry or wellness summary. If you can export the activity as the original FIT file or as GPX/TCX from Garmin Connect, that is a useful sanity check: it proves the activity exists as timed route data instead of only summary stats. If the workout has no map, no GPS points, or a start time that is off by a timezone or device-clock issue, the overlay may never align cleanly.

Then check the camera clock. Insta360’s mobile Stats instructions recommend connecting the camera to the app before shooting so the camera can receive accurate time from the phone. That is not just a convenience step. For overlays, the editor has to line up video time with activity time; if your camera clock, phone timezone, or Garmin activity start time drifted, the editor may be trying to infer too much from movement instead of matching the obvious activity.

Why Direction Detection Matters

It feels reasonable to expect the app to match timestamps and ignore direction, but action-camera dashboards usually do more than place numbers on screen. A Stats overlay can include route, speed, heading, tilt, acceleration, gradient, and direction-style elements. For a 360 clip, the editor may also need to understand the direction of travel so the dashboard and reframing behavior make visual sense.

So the phrase “detecting forward direction” is probably not asking Garmin where north is. It is likely part of the app’s attempt to infer how the camera moved through the scene and align that movement with the telemetry track. If the process never finishes, treat it as a failed preprocessing step: update the app, restart the phone, clear only temporary cache if needed, and test the same clip on another device or in the desktop workflow before assuming the Garmin activity is broken.

For content publishing, avoid making the stats overlay the only version of the video. Export one clean clip without the dashboard, then make a second version with stats once the telemetry path works. You can draft the clips in YumCut for hooks, captions, and platform-specific versions, but keep the Garmin/Insta360 telemetry overlay as a manual quality-control step because wrong speed, route, or timestamp data can make an otherwise good ride clip look careless.

Practical Fix Order

Use a small test clip first. Record 10-20 seconds in a normal video mode, connect the camera to the Insta360 app before recording, start a Garmin GPS activity, stop both, wait for Garmin Connect to finish syncing, and then try Stats. If that works, the problem is probably the original file, mode, timestamp, or a one-off app state. If it fails the same way, you likely have an app/device compatibility issue.

On Android, do the low-risk cleanup before destructive steps. Update the Insta360 app from Google Play, restart the phone, force close the app, and clear the app cache. Be careful with “clear storage” because it can remove app data and login state. If you do clear storage, make sure your camera files and exports are backed up outside the app first.

If the spinner still blocks the UI, try a second path: export the Garmin activity from Garmin Connect and test whether the current Insta360 Studio version can import the file for Stats. Insta360 says newer Studio versions support manually imported GPX/FIT data and Garmin-generated Stats, while time correction remains app-only. That means desktop may help confirm whether the telemetry file is valid, even if final sync adjustment still needs the mobile app.

Publishing Workflow

Once you can add Stats reliably, make the overlay serve the story instead of covering the whole frame. For a cycling, skiing, driving, or running short, the first two seconds should still show the moment: the climb, pass, jump, descent, or speed change. Use stats as proof, not as the hook itself. Viewers usually need a clear visual payoff before they care about altitude, speed, heart rate, or route shape.

A good workflow is: export a clean master, export a stats version, trim the strongest 6-15 second segment, then test two captions. One caption should lead with the physical moment, and one should lead with the metric. You can test the workflow in YumCut for short-form pacing and multilingual captions, then keep the final telemetry review manual before posting.