Content
file, stream, radio, call, prompt, alert, or test signal
file, stream, radio, call, prompt, alert, or test signal
app, normalization, EQ, operating system, media session, projection
Bluetooth Classic, LE Audio, USB, Wi-Fi, analog, factory network
phone, head unit, receiver, factory system, interface, or computer
decode, resample, mix, audio focus, volume, DSP, routing
DAC, ADC, line output, speaker output, differential or balanced interface
DSP input, amplifier input, factory amplifier, or protected measurement load
phone, head unit or source under test
→ safe output measurement
→ optional Wondom or other DSP after its input range is verified
→ scope, analyzer or audio interface
→ downstream amplifier muted or disconnected during source characterization
Do not connect an earth-referenced scope ground to an unknown speaker output. Factory and head-unit speaker outputs may be bridged, floating, class-D, load-sensitive, or diagnostic-active. Use a verified differential or isolated measurement method.
List every source the finished system must support: AM/FM, local USB files, phone Bluetooth, Bluetooth calls, wired projection, wireless projection, analog auxiliary, native apps, factory audio, navigation, assistants, alerts, and test signals. Define the required channels, maximum level, acceptable latency, retained functions, and recovery behavior.
Use identical source content where the platform allows it. Streaming-service catalog versions, normalization, remasters, and app processing can otherwise invalidate the comparison.
app → PCM → codec → A2DP → sink decode → host processing → output
source role → LC3 → LE isochronous path → sink role → host processing → output
file system → head-unit decoder → mixer and volume → DAC or digital output
host mixer → USB stream → audio device → DSP or DAC
phone app and framework ↔ vehicle host → audio focus and volume groups → output
source DAC and volume → cable and ground → analog input → host processing
Record app volume, normalization, replay gain, EQ, accessibility processing, phone media volume, projection volume, head-unit source and master volume, loudness, fader, balance, sub level, factory volume group, DSP trims, and amplifier input sensitivity.
Do not choose a universal 75 or 80 percent source setting. Find the clean limit for the exact source and state.
A Bluetooth version number does not identify the active codec or prove audio quality.
Confirm controller, operating system, source and sink roles, profiles, services, LC3, and the active use case. Test unicast, multi-stream, or broadcast independently. Record fallback to Bluetooth Classic. Do not treat modern Bluetooth hardware as proof that LE Audio is active.
| Observed behavior | Possible role | Next proof |
|---|---|---|
| phone charges only | power-only or failed data session | port and cable data capability |
| head unit browses files | storage host | file systems, formats, index limits |
| projection launches | CarPlay or Android Auto session | framework and host audio path |
| audio interface enumerates | USB Audio Class or vendor audio | descriptors, sample formats, channels, clock |
USB-C is a connector and role system, not proof of one audio protocol.
Android Auto projection and Android Automotive OS are different architectures. Do not collapse them into one “Android radio” category.
For media, navigation, calls, assistants, alerts, emergency audio, and safety sounds, record whether the system pauses, replaces, ducks, mixes, or mutes. Measure attenuation, attack, release, route, and restored level. Spoken navigation over spoken media may require a different policy than navigation over music.
Level-match at the measured analog or digital boundary, not by display number. Compare response, noise, distortion, channel map, latency, transient behavior, and repeatability. A different loudness is not proof of better quality.
Test cold boot, accessory-to-run, engine stop-start, source lock, phone out of range, call end, app crash, cable removal, wireless drop, key-off, vehicle sleep, and wake. Record source, volume, mute, routing, and remote-turn-on restoration.
Save the maximum clean source setting, calibration state, maximum approved user state, call and prompt state, and any source-specific DSP or gain compensation. Avoid hiding large source differences with undocumented output trims.
Save source device, software, firmware, app settings, content, transport, codec or protocol, sample rate, volume states, measured output, noise, latency, interrupts, fallback behavior, approved DSP preset, and date. Recheck after major phone, app, host, or firmware updates.
| Finding | Do not assume | Measure next |
|---|---|---|
| Bluetooth sounds quieter | codec quality is lower | phone, app, normalization, sink volume, output voltage |
| USB does not play | the cable is bad | port role, host/device support, storage versus projection versus UAC |
| wireless projection drops | Bluetooth audio failed | session setup, Wi-Fi, Bluetooth control, phone heat, host firmware |
| navigation is too quiet | increase master volume | audio focus, prompt volume group, ducking, route, source state |
| higher-RCA-voltage unit is noisier | advertised voltage is false | clean output, grounding, output impedance, DSP input, gain distribution |
The core version, profiles, optional codecs, two-device support, negotiation, and active configuration are separate.
The connector can support many data and power roles, while the host must implement the required audio or projection protocol.
Volume scales and clean limits vary by source, processing state, device, and implementation.
They can use different profiles, volume groups, routes, focus policies, and restored states.
The complete 12-question data set is stored beside the lesson for future interactive use.