Support

Installing the watch app

Getting inDepth Blue or inDepth Pool onto your Garmin is covered step-by-step on the install help page, including what to do when the desktop installer can't see your watch.

Pairing and syncing

My watch doesn't appear in the app

inDepth Apnea Sync reaches your watch through Garmin Connect Mobile, so that app must be installed and your watch must already be paired inside it. Once it is, tap ＋ Add a watch in the app's top bar. That is what the watch status chip shows until you have told the app you own one of the watch apps, and it opens Settings → Your gear. If your chip is already a plain sync icon, tap it instead and the same card opens as a sheet. The Connect your watch card at the top of that screen is where you pair: on Android use Refresh, which re-scans. On iPhone the button says Pair in Garmin Connect instead, which hands you over to Garmin Connect's watch picker. Either way, tap through to Garmin Connect and come back. Apple's Connect IQ SDK cannot list already-paired watches on its own, so inDepth only knows the watches that picker last handed it.

I paired another watch and it doesn't show up

On iPhone, tap the watch status chip in the top bar to open the connection sheet, then use Refresh. It reopens Garmin Connect's watch picker, which is the only way inDepth can learn about a watch you paired after setting the app up. Check all of your watches there, not just the new one: the picker's answer replaces inDepth's whole list, so leaving one out drops it (run Refresh again to bring it back). On Android Refresh simply re-scans.

Sync fails or finds nothing

Open the inDepth app on the watch and leave it open for the whole transfer. The watch app has to be running for the phone to talk to it. Keep the watch within a few meters of the phone, and make sure Garmin Connect Mobile is running in the background. If a sync stops partway, run it again. Transfers resume rather than starting over, and nothing is lost by retrying.

I have two watches and the wrong one syncs

Tap the watch status chip in the top bar to open the connection sheet, then pick the watch you want from the paired-watches list. The choice is remembered until you reinstall the app.

Some of my dives are missing

Each watch app keeps only a rolling buffer of recent sessions: the last 5 on a Fēnix 5 / 5S, where memory is tightest, and the last 50 on every other model. Once that fills, the oldest session is overwritten whether or not it has synced. If you dive a lot between syncs, sync often. On a Fēnix 5 or 5S, sync after every few sessions.

Your dive data

I deleted something by mistake. Can I get it back?

Not from the watch. Deleting is phone-local, and the watch never re-sends a session it has already handed over, so anything deleted after it synced is gone. If you deleted it before the watch's next sync, it will come back on the next one. Restoring from a backup is the reliable route (see below).

How do I back up, or move to a new phone?

Settings → Back up all data writes a single .json file containing everything: dive sessions with their depth profiles, pool sessions, workouts, names, tags, notes, annotations and your unit preferences. Save it somewhere safe, then on the new phone use Settings → Restore from backup. A backup made by a newer version of the app cannot be restored into an older one, so update first.

Can I get my data out as a spreadsheet?

Settings → Export all dives (CSV). This is a one-way export for spreadsheets and analysis. It cannot be re-imported, so use the backup file if what you want is to move between phones.

Where is my data stored? Do you have a copy?

On your phone, and nowhere else. There is no account and no server, so we hold no copy of your dives and cannot recover them for you. See the Privacy Policy.

Reporting a problem

How do I send you a diagnostic report?

Settings → Pull diagnostics from watch. It gathers recent log lines from the watch and the phone into a .zip and opens the share sheet so you can email it to us. It contains no dive data. The watch clears its log buffer once the phone collects it, so pull soon after reproducing the problem, and keep the watch app open while it runs. A pull can take up to about a minute over a slow link.

The app is empty on a fresh install

That is the expected first-launch state. inDepth Sync is a companion app: it displays dives your Garmin recorded, so until a watch running inDepth Blue or inDepth Pool has synced, there is nothing to show. Tap ＋ Add a watch in the top bar to get started: it opens Settings → Your gear, where the Connect your watch card pairs your watch and runs that first sync.

Depth readings look wrong or capped on my watch

On some Garmin models the firmware limits the depth range it reports to Connect IQ apps, so recorded depth can be capped well short of your actual depth. This is a device-side restriction we cannot work around. It affects the Fēnix 7 / 7S / 7X, the Descent Mk2 / Mk2S and the Descent Mk3 / Mk3i (43 mm and 51 mm), which stop reading at about 3 m, plus the Descent G2, which nobody has tested but which the app treats the same way. On those eight watches inDepth Blue therefore offers only the surface-rest models computed from dive time, 2× / 3× Dive Time and Manual, default 2×, because a clamped reading is what Adaptive (AIDA), Taravana and Molchanovs were already being fed there, and all three came out at plain 2× regardless. Nothing about that makes your rests shorter. The mode name simply matches the number now. If one of those three is stored on your watch it is left in place and reads as 2×. The Fēnix 5 / 5 Plus and Fēnix 8 families are unaffected and keep every mode. Those watches are there on different evidence: the Mk3 is measured on instruments, the Fēnix 7 is inferred, the Descent Mk2 / Mk2S is reported clamped at ~3 m by a diver, not instrumented, a report from 2026-08-06 that replaced the earlier "never dive-tested, so unverified" position, and the Descent G2 has no test of any kind behind it — no figure is published for it and the app plays it safe on family expectation alone. The per-model figures and the evidence behind each one are on the help page.