Why the volume creeps up

Tyre roar, wind and engine noise rise with speed, so the level you set at a standstill sounds thin on the motorway. That's what speed-dependent volume is for: the head unit adds gain as you go faster, and takes it back when you slow down.

It's why the volume drops back on its own when you pull up at a junction, and why so many drivers assume something's broken the first time they hear it. So what's doing the adjusting? The unit doesn't measure anything itself - it just passes along a speed value that somebody else produced.

What it's called depends on who built the car, because there's no shared standard here the way there's one for the radio aperture. Two neighbouring rows get confused with it as well: loudness adds bass and treble at low volume, and a maximum-volume limit caps the ceiling. People switch off one of those, hear nothing change, and conclude the whole feature is broken.

What it is called on your car

Here are the labels you'll meet most often. Don't treat the list as a dictionary, because names shift between model years and markets, and a translated menu can turn any of them into something stranger than you'd guess.

• SDVCSpeed Dependent Volume Control. The commonest label, across many Asian and American models.
• SCVSpeed Compensated Volume. Ford and GM-era decks often use this one.
• SVCSpeed-sensitive Volume Control. Honda-family menus.
• ASLAutomatic Sound Levelizer. Toyota-family menus. On some models the same name hides a tone curve.
• GALAThe Volkswagen and Audi version, short for a long German compound.
• Volume by speedWhat many retrofit Android units write, sometimes as Auto volume.

Where the switch actually lives

There are three places to look, and the order matters: the first one is two taps away, and the third hides behind a password.

Audio menu. If the factory radio's still in the dash, that's where the row lives. Press audio or setup, walk into the sound submenu, then look for one of the names above. On many Ford and GM-era decks the route runs Setup, Main, SDVC, then Off.

Normal settings. On a retrofit unit, open Settings and then Sound, though on some builds you'll find the same page filed under Car or Vehicle instead. You're looking for a row called Volume by speed, Speed volume or Auto volume, and on many units the control is a three-position level rather than a switch, so don't expect the word OFF anywhere on the screen. The universal retrofit units sold for older dashes follow that same layout.

Factory menu. This one's hidden behind a code, and plenty of retrofit units keep the speed row in there. Open Settings, then Factory or Car settings, and enter the password. Codes vary by platform, and you'll see 1234, 0000, 8888, 1617 and 3368 all in circulation on these boards.

On the WITSON builds we ship, the speed-volume row is usually in the sound menu rather than the factory menu, and on some platforms it's a level you drop to 0 instead of a switch you turn off. It follows the platform version rather than the car, so the manual for your own unit beats a screenshot from somebody else's build.

While you're in there, leave the protocol setting alone. Changing it to hunt for a volume row is a quick way to lose your steering wheel buttons, and finding the right value again isn't always obvious.

Low, Medium, High - or OFF?

If the jumpiness bothers you more than the idea does, the lowest level is usually the better answer. A low setting still adds a little gain at motorway speed, but the steps get small enough that you stop noticing them.

A low level beats OFF on the motorway, and OFF is what I'd set for everything else - that's a taste call, not a rule. Some units apply the correction to every source and some don't, so play the same track over Bluetooth at 50 km/h and again at 110 km/h. If the level moves on the tuner but not over Bluetooth, the compensation is wired to one input path, and you've learned something about how the audio chain is built.

If your menu offers no level and no switch, the feature may not be exposed on that build at all.

Where the speed value comes from

Here's the part most guides skip. The correction only works with a speed number, and there's more than one way to feed it to the head unit.

• Route AA CANBUS decoder box listens to the car's data bus and passes the head unit a set of values, wheel speed among them on the vehicles that publish it.
• Route BA dedicated speed pulse wire, sometimes called VSS, runs to the radio position. Some harnesses carry it, some don't.
• Route CNo wired input at all, so the unit works speed out from the GPS fix instead.

Route A is the usual one on modern cars. Fit the wrong protocol, or leave the decoder out of the loom, and the speed value may never arrive. Route B is common on older vehicles, and an unconnected pulse wire means an inert feature. Route C works, but it lags behind the car and drops out in tunnels, car parks and between tall buildings, so the correction you get is coarse rather than precise.

Which one have you got? Test it: set the feature to its highest level, drive two minutes above 60 km/h, then stop and listen. If the volume never moves, the unit likely has no speed value at all, and switching the feature off won't achieve anything.

That last case is the workshop trap. The row is there, the level sits on High, nothing happens - so the unit gets reflashed, or replaced. In our experience the usual suspect is a CANBUS box set to the wrong protocol for that car, or left out of the loom entirely, and no menu setting invents a speed value that never arrives for your car.

If your unit is already out of the dash, look at the harness connector for the speed pulse cavity. An empty cavity settles the question faster than hours of menu work. And before anyone reaches for the connector standard: ISO 10487 covers the speaker, power, ignition and illumination pins, and says nothing about speed data, which travels on the car's own bus or on a wire the standard doesn't describe.

When it isn't the speed setting

A volume that climbs on its own has other authors, and the speed row is what everyone blames first. Here's what we see on the bench, in the order we'd check it.

• It moves while the car is parked. The speed row can't do that - it only adds gain once a speed value arrives. Engine off, doors shut, phone unplugged: if the level still drifts, you're chasing a volume encoder that needs cleaning, not a menu that needs a setting.
• It jumps when you turn the wheel. This is the one that costs people an afternoon in the menu. A tired clock spring or a sticky steering-wheel button fires a volume command whenever the wheel moves, and no amount of menu work fixes it. Turn lock to lock while parked - if the level moves with the wheel, you're working on the column, not the settings.
• It only misbehaves over Bluetooth. Bluetooth runs its own volume negotiation, and some navigation apps duck the music to talk over it. Play the same track from a USB stick and see whether your jump survives the swap.
• It follows the source, not the speed. Auto gain and loudness curves sit in a different menu from the speed row, usually in the DSP app, and they colour the sound in a way that reads as a volume change from the driver's seat.
• Nothing happens on any level. Then no speed value is reaching your unit - that's the protocol question from section 04, and reflashing firmware won't put a signal on a pin that was never connected.

Work in that order, cheapest and most reversible first. Settings, then cables and connectors, then the unit itself, because ordering a new head unit over a dirty volume knob is a genuinely frustrating way to spend money.

Zhuhai WITSON Industrial Co., Ltd. - Tel: +86-756-8120312, 8120211, 8120212.

Frequently Asked Questions (FAQ)

Back to top