V1Journey

Setting up your V1

The first ten minutes. Pairing takes one tap, and then there are three settings on the detector itself that decide how well any companion app can work. V1Journey checks all three for you and offers to fix the ones it can.

You need a Valentine One Gen2 (V1R2) with Bluetooth built in, and an iPhone on iOS 26 or later. Full requirements.

Pairing

1

Power on the V1, then open V1Journey

On first launch the app opens the “Connect Your V1” sheet by itself. It scans, shows what it finds, and connects when you tap your detector.

2

Tap your detector in the list

You'll see “Establishing ESP communication…” briefly, then “Your V1 is connected and streaming alerts,” along with your detector's model and firmware version.

3

That's it — it reconnects on its own

After the first time the app reconnects automatically when you start a drive. To connect again by hand, use Settings → Scan for V1. If you have a detector in each car, pair both; the app reconnects to whichever one is powered up.

Where it isn't

Do not pair the V1 in iOS Settings → Bluetooth. It is a Bluetooth LE device and the app talks to it directly, so it will not appear in that list. If you have been hunting for it there, that is why.

The three settings that matter

These live on the detector, not in the app, and they are the difference between a companion app that can act before you hear a false alarm and one that can only react after. V1Journey reads them when you connect and raises an advisory for each one that is working against it.

1. Logic Mode — V1Journey can fix this for you

Logic Mode is the only mode that tells the app about an alert before the V1 sounds, which is what makes filtering possible at all:

If you are in another mode, V1Journey shows a “Set V1 to Logic Mode” advisory with a Fix button that changes it for you. You will find it under Settings → your V1 → V1 Setup. More on the three modes.

2. Firmware — V4.1038 or newer recommended

Older firmware still works. Nothing is disabled: the app falls back to the older behaviour and shows a dismissible “V1 Firmware Update Available” notice the first time you connect, and it stays dismissed.

Two behaviours do need V4.1039 or newer: telling the difference between a mute the V1's logic mode applied and one its own Auto Mute applied, and clearing a mute that the V1's own Auto Mute is holding. On older firmware that second request can silently do nothing — a limitation in the detector, not something the app can work around.

Firmware updates happen in Valentine Research's own V1connection app, never from V1Journey. More on firmware.

3. Bogey-Lock tone, and Euro Mode for MRCD

Two more advisories you may see, both of which point you at the exact steps in the V1connection app because they cannot be changed over the ESP protocol:

How you'll know

You don't have to go looking for any of this. A yellow warning triangle appears on the map's status strip whenever the V1 is reporting a setting that fights the app. Tap it and you get the list: what the setting is, why it matters, a Fix button where the ESP protocol allows the app to change it, and the exact steps in V1connection where it doesn't.

We would rather tell you your detector is configured against you than quietly work around it and have you wonder why the app seems worse than it should be.

Then: location, once

The first time your V1 connects, V1Journey asks for background location. It is worth saying yes to, and worth understanding why: lockout zones can only silence a false alarm if the app knows where you are when you drive past it, low-speed muting needs your speed, and corridor shapes are learned from the track you actually drove. All three stop the moment your screen locks without it.

iOS shows that request once. If you decline it, the app tells you so on the status strip rather than quietly going half-deaf — but getting it back means a trip to iOS Settings. How background operation works.

Worth knowing on day one

Everything else is in the FAQ →