Car navigation - speed alerts
Yes, the margin is yours to pick, and on a retrofit unit the row you need usually isn't in the head unit at all - it sits in the navigation app. One thing matters first: whether the unit hands the app a speed value at all. Get that sorted, then open the app's speedometer settings. Which app do you navigate with? That answer decides everything below.
Two different features share the name speed warning, and blending them costs you an hour. Inside the retrofit head unit's firmware there's often a plain over speed row - one number in km/h, filed under factory or car settings. It beeps and does nothing else, and it's running on whatever speed value the unit already has. The part you can genuinely tune - the margin above the limit that fires the alert - belongs to the navigation app.
That splits the job across two layers, and naming them kills most of the confusion. The head unit's just a box in the dash. Android Auto and CarPlay are links that put a phone app onto its screen: the phone does the computing, the dash only shows the result. The threshold lives with the navigation app, on the phone or inside the unit.
Waze's own help page says as much to its users: change the settings on the phone and they'll carry over to the car, and if you're on Android Auto or CarPlay, disconnect the phone first. Google Maps files its speedometer switch under Settings, then Navigation, then Driving options, plus a speed limits row where the feature's available in your region. A menu path remembered from somebody else's car is how people lose an afternoon.
So what can you actually change? Four things, and apps differ sharply on how many you'll get to touch.
Scroll sideways to see all columns.
| What you can change | Google Maps | Waze |
|---|---|---|
| Speed readout | Speedometer toggle under Driving options; Android path is Settings, Navigation, Driving options | Speedometer section: switch on Show speedometer |
| Posted limit on screen | Speed limits row, where the feature is available in your region | Show speed limit, with a choice of when it appears |
| How far over fires it | Not selectable - the badge changes colour once you are over | Speeding threshold, where you set what Waze counts as speeding |
| Audible alert | Varies by region | Alert when speeding, a switch of its own |
| Where you change it | Phone app; the car screen mirrors it | Phone app, and Waze's help page says to disconnect Android Auto or CarPlay first |
I'd leave the number on the sign alone - not one of those rows lets you rewrite it. The limit is data; what you pick is the margin. If you're comparing units rather than fixing one, the universal one and two DIN head units are the family this article covers: retrofit Android units that run the navigation app on your car screen.
Work through these in sequence, and watch what each step puts on your screen.
Then prove it. Drive a road you know carries a limit in the map data and watch the badge as you pass the sign. Number appears and the chime fires: done. Number appears and nothing sounds: the sound switch or the alert volume is off. Still nothing? Then stop changing thresholds and read the next section.
One thing to leave alone. If the unit's own over-speed row sits behind a factory or engineering code, don't go exploring in there. Anything that needs the dash opened or a meter on a wire is a job for the shop, not the driveway - and before you hand the car over, note the details listed at the end of this page.
Your speed and the posted limit reach the screen by two unrelated routes, and the faults sit on both. Which number is lying to you?
Your speed figure comes from GPS in most app-based setups: it's smooth and usually close, but it trails the car by a beat and drifts in tunnels and streets between tall buildings. Where the head unit supplies its own figure, it arrives off the vehicle bus or a speed pulse wire - quicker and steadier, but only if the decoder box or pulse wire was actually fitted and wired.
The posted limit is where the real trouble lives, because the app isn't reading the sign in front of you. It's reading map data. Commercial map sets carry limits across the classified network; community-edited sets are thinner, which is why an offline navigator shows no badge on a road you can see has a sign. Camera-based sign reading appears on higher-end systems, and it can still miss a sign that's dirty, angled or behind a lorry.
The rulebook's more forgiving than people expect. The EU's intelligent speed assistance requirements - Commission Delegated Regulation (EU) 2021/1958, which fills in Regulation (EU) 2019/2144 - verify a speed limit information function over a 400 km on-road route and ask for the right limit over at least 90 percent of the distance, with the number flagged when the system is inferring rather than reading a sign. If a system built to pass a type-approval test is allowed to be wrong one time in ten, a stale number on a back street isn't a bug you can clear from a menu.
A speed limit warning is a margin you choose, not a number you write. The number belongs to the map data.
Three complaints come up again and again, and in two of them the app's innocent. The common mistake is to start on the unit's over speed row, because that's the one with the obvious name. Ask instead where the alert is generated.
Sometimes you get nothing. A missing speed value is the usual suspect, well ahead of a broken app. Set the trigger to its lowest step, drive a road you know carries a limit in the data, and watch the badge. If no limit number appears, that road has no limit data and no threshold will conjure one up. If the number appears but stays quiet, the sound switch is off or the alert volume sits at zero. Photograph each screen as you work, because it beats half-remembered menu names.
A driver says the over-speed beep mutes the music and the radio doesn't come back. That isn't a navigation fault, and swapping a head unit to cure it is an annoying way to spend money. On plenty of builds the alert rides an alarm or system stream, and the unit's factory mixer's set to cut rather than mix - the music drops for the chime and nothing lifts it again. Look for a mix-versus-cut row in the driving settings, or a system volume and radio volume pair in the factory menu. Test it parked with the radio playing: if the station goes quiet and stays quiet, that's audio routing.
A driver picks a threshold and finds it back where it started next morning. If the warning comes through Android Auto or CarPlay, the phone is the source of truth and the dash saves nothing - change it in the app and reconnect. Where the row genuinely lives in the head unit, a battery disconnect or a reset wipes it, so write the value down before you pull a terminal.
One more, because it looks like a fault and isn't. Speed camera alerts are a separate switch from speed limit warnings, and they're the half with legal limits, so the camera switch gets misdiagnosed as broken every time someone crosses a border. France shows broad danger zones rather than exact positions, Switzerland doesn't map camera locations, and Germany restricts in-car warnings while you're driving. If your warnings vanish at a border, that's the app obeying local law, not failing.
Speed alerts live in the app on a retrofit unit, and app menus change faster than any printed manual. If your build never receives a speed value, or the chime and the radio are fighting, send us four things: the unit model, the build string, how the unit is connected - harness, CAN box or pulse wire - and what the screen actually does, with a photo or a short clip.
Ask our support deskThose four details are the ones we need to match the answer to your build.
Zhuhai WITSON Industrial Co., Ltd. - Tel: +86-756-8120312, 8120211, 8120212.
On the phone, if the alert comes through Android Auto or CarPlay. The dash mirrors the app and saves nothing of its own.
Blame your audio routing, not the app. Plenty of builds send the alert on an alarm or system stream and set the factory mixer to cut rather than mix, so the music drops and nothing lifts it back. Look for a mix-versus-cut row in the driving settings, or a system volume and radio volume pair in the factory menu. Then test it parked with your radio playing.
Not from the settings on the mainstream apps. What you change is the margin, not the number - the limit's data. A sign-reading camera, where the system carries one, can beat stale map data on a road it's seen recently. Updating the map package is the other lever.
It depends on the country, and the app usually adjusts by itself. France shows danger zones instead of exact camera positions, Switzerland doesn't map cameras, and Germany restricts warnings inside the car. Speed limit warnings are a separate switch and aren't affected.
Partly. A two or three km/h cushion takes the nuisance out of it, since the cluster and a GPS-derived speed rarely match to the decimal. Push it much further and you're just muting the feature.
