Doppler effect explained (vehicle speed)

When a sounding object moves toward you, its pitch sounds higher; as it moves away, the pitch drops. That Doppler shift can be turned into a rough radial speed estimate if the emitted tone is steady enough.

The idea

For a source that emits a nearly constant frequency, the observed approach and recede frequencies (f1 and f2) relate to speed roughly by v = c(f1 - f2)/(f1 + f2), where c is the speed of sound. Temperature changes c. Geometry usually makes a roadside estimate a bit low versus true ground speed.

What trips up a phone

Engine roar is broadband. Gears change. Reflections arrive late. Clipping destroys pitch. A good app shows live estimates carefully labelled, saves only stricter final results, and explains rejections instead of hallucinating a speed.

Live vs saved in DecibelDock

A provisional LIVE · ESTIMATING number can appear during a pass. It is smoothed and not saved. The history entry uses a stricter final check. Continuous mode can keep listening for the next vehicle after an accepted pass.

Safety

Stand clear of traffic. Doppler in DecibelDock is educational, not enforcement and not a driving aid.

Choosing a pass

Isolated vehicles with a tonal component work better than packs of traffic. Stay stationary. Point the mic toward the path without standing in it. A single clean pass beats a long confusing recording.

Reading the app honestly

LIVE · ESTIMATING means provisional. History stores only accepted final speeds. Written rejection reasons mean the math did not have a trustworthy before/after pair — that is a feature, not a bug. Continuous mode is optional and still ends when you stop or leave the tool.

Units and expectations

Results may show mph or km/h based on your units setting. Treat them as ballpark radial estimates. A vehicle that passes far to the side, changes throttle mid-pass, or is buried in tire roar may yield no speed and a written reason — which is the correct outcome.

Do not use phone Doppler for tickets, arguments with drivers, or any safety-critical decision.

Putting it to work in DecibelDock

Open Doppler vehicle speed after you read this guide so the ideas attach to real controls. Use the same phone, the same weighting or instrument preset, and the same physical position whenever you compare two scenes. Prefer a blank reading, a held value, or a written rejection over a number that looks definitive but came from silence, clipping or chaos.

DecibelDock is built for exploration and relative checks on Android. It is not a calibrated or certified sound level meter, not a medical device, and not a substitute for professional instruments when safety, health or compliance are on the line. Direction, Doppler and Distance stay approximate and depend on your phone. The learn section exists to make those limits understandable — and to help the feature pages show up for the questions people already type into a search box.

When you are done experimenting, skim a related article below and the matching feature page. Internal links are intentional: each guide should send you somewhere useful next, not leave you on a dead-end paragraph.

If something in the app disagrees with this guide after a future update, trust the in-app How to use notes for that build, and treat marketing copy as secondary to what the screen actually shows.

Key takeaways

• Use the same phone and setup when you compare scenes.
• Prefer a blank or rejected result over a confident wrong number.
• Phone tools are for exploration and relative checks, not certification.
• Read the matching feature page for what the app actually shows on screen.