Five apps talk to a Valentine One Gen2. Three of them navigate, and the same three run on CarPlay. So this page isn't about those. It's about what happens after you press Lock Out — and about the things V1Journey deliberately doesn't do.
Competitor details verified from public App Store listings and developer documentation on 24 August 2026. App Store ratings and V1Journey's release status re-verified 11 September 2026.
If you've been shopping V1 Gen2 apps, you already know that turn-by-turn navigation and CarPlay aren't rare any more. Dukes App does both, free. V1 Companion added CarPlay in August 2026. GPS lockouts, low-speed muting, alert history — every serious app in this category has all of it.
So V1Journey isn't going to tell you it invented navigation.
What it will tell you is this: when you press Lock Out, the apps that do this store a point. One shows you pins in a settings screen; another shows nothing at all. V1Journey draws the road, and puts it on the map where you can see it.
Verified 24 August 2026, ratings re-verified 11 September 2026 · "Not documented" means the app's public documentation doesn't describe the feature — not that it definitely can't do it.
| V1Journey | V1connection | V1 Companion | V1Driver | Dukes App | |
|---|---|---|---|---|---|
| Group A — What you get before you pay | |||||
| Price | Free · Pro $14.99/yr or $39.99 once | Free | $9.99 + in-app purchases | $11.99 | Free |
| Band, exact frequency, direction, signal strength — without paying | ✓ | Band, frequency, direction ✓ · strength not documented | Paid app | Paid app | ✓ |
| Turn-by-turn navigation without paying | ✓ | — | Paid app | Map view only | ✓ |
| CarPlay without paying | ✓ incl. Dashboard | — | Paid app | — | ✓ |
| Band and exact frequency on the car screen while navigating | ✓ Always | — | Not documented | — | Arrow + strength only |
| Group B — Lockout zones | |||||
| GPS lockout zones | ✓ Pro | — | ✓ | ✓ | ✓ |
| Zone shape | A corridor along the road you actually drove | — | Point-based (SpotLocks™) | Point-based | Coordinate-based, per developer docs |
| Created on the first pass | ✓ One tap, phone or CarPlay | — | Learned over time | Learned over time | Auto after a settable number of passes; manual instant available |
| Reshapes itself when you drive it again | ✓ Widens and extends | — | Not documented | Not documented | Not documented |
| Zone drawn on the map so you can see it | ✓ Phone and CarPlay | — | Pins only, no geometry | Not documented | — Nothing drawn |
| Lock out from the car screen | ✓ | — | ✓ | — | ✓ |
| Lock out something you drove past last week | ✓ Pro | — | Not documented | Not documented | Not documented |
| Nothing is muted if any live alert is unmatched | ✓ | — | Not documented | Not documented | Not documented |
| Group C — Knowing why it went quiet | |||||
| The reason for the current mute, always on screen | ✓ | — | Not documented | Not documented | — |
| A separate list of what was silenced, and why | ✓ Pro | — | Not documented | Not documented | — |
| Alert history with GPS track | ✓ 30 days, Pro | — | ✓ | Not documented | ✓ Sessions with map overlay |
| Zones and history reached from the map, not Settings | ✓ Live counters on the map, one tap each | — | In Settings | Not documented | In Settings |
| Keep an alert permanently, with your speed at the instant it arrived | ✓ Free | — | Not documented | Not documented | Not documented |
| Group D — The detector itself | |||||
| Tells you which of your V1's own settings are fighting the app | ✓ And offers to fix them | Programs the V1 | Changes V1 settings | — | — |
| Low-speed muting | ✓ Pro | ✓ eSAVVY | ✓ | ✓ Savvy emulation | ✓ |
| Detectors supported | V1 Gen2 only | V1 Gen1 + Gen2 | V1 — separate app per detector model | V1, DS1, R4, R8 | 8 models across 3 brands, plus AL Priority laser jammers |
| Group E — Coverage beyond the detector | |||||
| Crowdsourced police alerts | — By design | — | — | Receive-only | ✓ |
| Speed camera / ALPR database | — By design | — | Photo radar detection | Not documented | ✓ |
| Account or sign-up required | None — no account, no server | Not documented | Not documented | Not documented | None |
| Group F — Track record | |||||
| App Store rating | Live — too new for a public rating yet | 3.4★ · 70 ratings | 4.6★ · 97 ratings | 4.7★ · 575 ratings | 4.3★ · 13 ratings |
Every lockout in this category starts the same way: the app remembers where you were when the false went off. The difference is what it does with that memory.
A point-based lockout draws a circle. Make it small and it misses the same door opener on the next pass, when your GPS was two lanes over. Make it big and it covers the intersection, the cross street, and the shoulder where a patrol car sits.
V1Journey records your GPS track while the alert is open and builds the zone as a corridor along it — 30 metres to each side, extended 100 metres past both ends. It covers the stretch of road where the signal actually reaches you and stops at the edges of it.
Drive it again and the zone adapts. A matching signal off to the side — the far carriageway of a divided highway — widens the corridor. One coming from beyond the end, on the return trip, extends it. The zone only ever grows toward the road; it never narrows, and it never spreads sideways into places you haven't driven.
Automatic lockouts learn by repetition: a signal seen in the same place often enough gets silenced from then on. Dukes App lets you set that threshold, anywhere from a single pass upward. V1 Companion's SpotLocks™ and V1Driver's GPS lockouts both learn over time.
There is no setting on that dial that amounts to a decision. Set it high and the same door opener bothers you three or four more times before anything happens. Set it to one and the first thing you drive past is silenced permanently, before you've had a chance to form an opinion about what it was.
V1Journey asks you instead. A lock-out button appears whenever a lockable alert is live, on the phone map and on the CarPlay alert surface, and it stays for a few seconds after the alert ends so you get a real window rather than a race. Press it once and the zone starts forming immediately, with the V1 held quiet while it builds.
And it's frequency-anchored. The zone stores the band and an anchor frequency and only suppresses a signal that matches inside its learned window and falls inside its geometry. Locking out the garage door doesn't lock out a police car parked next to it.
One more rule worth knowing, because it's the one that lets you trust the whole system: if any live alert isn't matched by a zone, nothing gets muted at all. A real threat is never silenced because something else nearby happened to match.
The more aggressively an app filters, the more you have to take on faith. V1Journey's answer is to never make you.
The status card names the active mute reason at all times — Manual, Always Muted, Low Speed, Automute, Locked Out, K Out of Box, Auto-Snoozed. Not an icon. The reason, in words, on the screen.
And everything that got silenced goes into a Suppressed list, separately from your trip alerts, each row labelled with the reason it was quieted. A lockout-zone suppression links straight back to the zone that did it, so you can see the shape, see how many times it's fired, and delete it if it's wrong.
The two lists partition every encounter — never both, never neither. You heard it, it's a trip alert. It was silenced for you, it's in Suppressed.
CarPlay gives an app a fixed amount of room, and every radar app has to decide what happens when a maneuver card and a radar alert want it at the same time. That decision is invisible until you're navigating — which is exactly when it matters.
V1Journey's alert surfaces are drawn by CarPlay's own navigation-alert templates, so band, exact frequency, direction and signal strength stay at full size whether or not you're being routed.
You choose the presentation in Settings: a banner docked over the map that keeps the map visible, or a full alert list with one row per live signal. Either way the alert carries its actions, and a threat always outranks turn guidance on the Dashboard card, because at that size splitting the space produces two illegible halves.
Nothing about that is free. It's a decision, and it's the one V1Journey made.
Some of the most advertised features in this category aren't in V1Journey. None of them are missing by accident, and one of them we'd turn down again tomorrow.
Drive a road and the app works out which alerts are false and silences them for you. Dukes App builds a permanent lockout automatically once it has seen a signal on the same spot enough times — a threshold you set, adjustable all the way down to a single pass. V1 Companion's SpotLocks™ and V1Driver's GPS lockouts both learn over time. No tapping.
Every system like that is detecting the same thing underneath: a signal that shows up in the same place more than once.
That is not the definition of a false alert. It's the definition of a stationary, repeatedly-encountered source — which also describes, exactly, the officer who works the same pullout on your commute every weekday morning. Same corridor, same frequency, second pass, silenced. An automatic lockout is at its most confident precisely where a detector is most valuable.
Notice that the threshold doesn't rescue it either — it just picks which way you lose. Set it high and you're annoyed by the same door opener three or four times before anything happens. Set it to one pass and the first thing you drive past becomes a permanent zone before you've had a chance to form an opinion about it. There is no setting on that dial that amounts to a decision. It's a guess with a sensitivity knob.
The frequency doesn't rescue it either. US police K band runs on two spot frequencies, 24.125 and 24.150 GHz. Automatic door openers, motion sensors and older blind-spot radar share the same 100 MHz slice of spectrum — 24.075 to 24.175 GHz, the FCC's field-disturbance-sensor band (47 CFR §15.245) that covers exactly this kind of motion and door-opening hardware — which is why K falses exist in the first place. "Same band, similar frequency, seen here before" barely separates a garage door from a radar gun.
And then there's the source that was never stationary. A blind-spot monitor on the truck pacing you transmits K from a moving vehicle, but the app records the alert at your coordinates. Different truck, different day, same stretch of interstate — and a repeat-counting system now has two encounters in one corridor on one frequency, and builds a lockout on open highway where nothing was ever parked. That is the worst place on earth to have one.
The part that makes all of the above unfixable: you can't see what it built.
An automatic lockout is a decision the app made on your behalf. If it's drawn on the map, it's at least a decision you can inspect, argue with, and delete. If it isn't drawn anywhere, the only evidence it exists is a sound you no longer hear — and nobody notices a sound they don't hear. A wrong zone produces no symptom, no complaint, and no reason to ever go looking.
This is where the whole category is thin. Nothing else in it draws you the zone. One app shows you pins on a map in a settings screen; another shows nothing at all. A pin tells you a zone is somewhere near here. It doesn't tell you how far it reaches, which way it runs, whether it covers the far carriageway, or whether it's quietly sitting across the on-ramp.
So V1Journey draws it. Every zone renders as its actual shape on the map — on the phone and on the CarPlay screen — with its anchor frequency, when you made it, how many times it has fired, and one swipe to delete it. And it isn't filed away under Settings: the map carries live counters for alerts, suppressed alerts, and zones while you drive, and each one is a single tap into the list behind it. What the app is doing for you should be on the screen you're already looking at.
A filter you can't audit is a filter you have to take on faith, and this is not a category where faith is the right instrument.
What V1Journey does instead — you decide what gets silenced, the app works out where.
One press, first pass, phone or car screen. From there the automation is real and it's aggressive: the zone is built from the GPS path you actually drove, and it widens and extends each time you drive it again, adapting its frequency window as the source drifts. What never happens is the app deciding on its own that something you heard was nothing.
V1Journey does suppress automatically in one place. Auto-snooze quiets a K or X signature that's been continuously present for thirty seconds. But that's temporary and reversible — it never touches Ka, laser, or anything the V1 flags as priority, it un-snoozes the instant the signal surges in strength, and it never hardens into a permanent zone. It also shows up by name in the Suppressed list, so it's visible even while it's happening. Silencing something for a minute and silencing it forever are different decisions, and they get treated differently.
And frequency anchoring is a constraint on a zone, not a classifier. It stops a zone you created from swallowing a different signal that happens to share the same patch of road. It's never asked to decide whether something was a false in the first place. You already did that.
Dukes App carries community police reports. V1Driver receives crowdsourced alerts. Others add heat maps and risk scores for the road ahead.
Patrol cars move. That's the job. By the time a crowdsourced report is a few minutes old it's telling you where someone was, and you have no way to know whether they're still there, one exit up, or off shift. Fixed hazards crowdsource beautifully. Mobile enforcement is close to the worst possible candidate for it.
Heat maps have the opposite failure. They're accurate and unusable. A shaded map of statistical enforcement density along a route you haven't driven yet is not something anyone can read at 70 mph, and "be more alert along here" isn't an action you can take.
And there's the instrument already on your windshield. You spent $599 on a Valentine One Gen2 because it measures what is transmitting right now, in your direction, with a frequency and a bearing. That isn't a crowd's recollection of last Tuesday. V1Journey's job is to make that instrument's output livable — not to talk over it with guesses.
What V1Journey does instead: no account, no sign-up, no server, no report stream. Alert display and lockout matching are entirely local and work with no signal at all.
Dukes App and several others maintain red-light, speed and plate-reader camera databases.
The honest part first: cameras don't move, so this is the one place a database genuinely beats a sensor, and it's a fair reason to run one of those apps alongside V1Journey.
But a large share of what drivers want camera warnings for is photo radar — Gatso, MRCD, MRCT — and photo radar transmits, on K and Ka, which is precisely what the detector is for. The catch is that MRCD sits below the normal US K window, so a K filter tuned for American police radar can silence the very thing you wanted to hear.
V1Journey handles that geographically. In a known MRCD deployment area — New York City, Washington DC and Maryland, Chicago, New Orleans, Windsor Heights — it widens its K filter to 23.900–24.300 GHz on its own and puts your setting back when you leave. It also tells you to switch Euro mode on in V1connection, because that half of the job belongs to the detector, not the app.
Where V1Journey has nothing to offer is cameras that emit nothing at all — red-light cameras and plate readers. It won't warn you about those and it isn't going to. If that's your priority, an app with a database is the better tool.
Dukes App supports eight detector models across three brands plus laser jammers. V1Driver covers four.
Broad hardware support is a benefit to an app's market size, not to your drive. And it isn't free. An app that has to speak Uniden, Radenso and Valentine writes to what those detectors have in common — and a great deal of what makes the V1 Gen2 worth owning is not in common.
You can see the cost in the products themselves. Dukes App's K-Blocks, which push frequency windows down into the detector's own firmware, work on Uniden only. And Cracked Pixel arrived at the same conclusion from the other direction: it ships a separate paid app for the V1, the R4, the R8 and the R9 rather than one app that covers them all. Even the incumbent thinks one app per detector is the right shape. It just charges you again for each one.
V1Journey only has to be right about a single detector, and it spends that everywhere:
One detector. All the way down.
Valentine One Gen2 only. Not the original V1, not Uniden, not Radenso, and no Android.
No warning for cameras that don't transmit — red-light cameras and plate readers are invisible to any detector, and V1Journey has no database.
Live on the App Store, but too new for a public rating yet. V1 Companion has 97 ratings at 4.6 stars and that's earned. What you can check today is the work: every feature documented, including the ones that don't work the way you'd want.
V1 Companion has 97 ratings at 4.6 stars and ships an update roughly every week. V1Driver has 4.7 stars from 575 owners. Those are earned, and no comparison table changes it.
V1Journey doesn't have a track record like that yet — it's too new on the store to have one.
What you can check right now is the work itself: the app is documented feature by feature, including the things it can't do — laser can't be unmuted by any app, that's in the ESP spec; low-speed muting is band-agnostic and will quiet laser too, matching how the real Savvy behaves. Read the whole feature list before you decide.