SquelchDuck phone and USB audio guide
SquelchDuck needs your phone to take audio from a USB interface (your radio) and play it out somewhere else (usually the car over Bluetooth). That combination works on many phones, but not all. Use this page before you spend money on gear.
What has to work
Three things have to succeed on your phone:
- USB host (OTG) — the phone must talk to a USB accessory, not only charge from a computer.
- USB Audio Class input — Android must list the interface as a USB audio input (not every “USB microphone” does this).
- USB in + Bluetooth out at the same time — for car use, the phone must capture from USB while playing to the car. This is the step that fails on some phones even when USB input alone works.
SquelchDuck never uses the phone’s built-in microphone or speaker for that audio path.
Gear you need
| Piece | Role |
|---|---|
| Android phone (8.0+) | Runs SquelchDuck |
| Powered USB OTG hub (recommended) | Hosts the audio interface and keeps the phone charging |
| USB audio interface | Turns the radio’s speaker/line output into USB audio |
| Cable from radio → interface | Often 3.5 mm or RCA from the radio’s external speaker / headphone jack |
| Car audio over Bluetooth (or Android Auto) | Where you listen |
A plain USB-C (or Micro-USB) OTG adapter can work for a short test, but for real driving use a powered USB OTG hub is strongly recommended. Continuous monitoring draws power; a bus-powered interface draws more. Without a powered hub, the phone often drains, and the USB audio device can brown out or drop when the phone’s port cannot supply stable power.
The hub must be data-capable (USB host / OTG), not a charge-only dongle — otherwise it cannot host the audio interface. Look for one that also supports charging or power delivery to the phone while peripherals stay connected.
How to test your phone (before you commit)
Do this with a returnable USB audio interface if you can. A plain USB headset mic that only lights up is not a good test — many of those never appear to Android as USB audio.
Step 1 — Does the phone see USB audio?
- Connect a class-compliant USB audio interface, preferably through a powered USB OTG hub (see recommendations below).
- Open SquelchDuck (or Android’s sound / input settings if you prefer).
- On SquelchDuck’s main screen, open the USB input list.
Pass: the interface appears by name (or as a USB audio device).
Fail: the list stays empty and Android never shows a USB input. The phone, cable, hub/adapter, or interface is not enumerating USB audio. Try a powered OTG hub, another cable, or a different interface before blaming the phone.
Step 2 — Can it play to Bluetooth at the same time?
- Connect your car stereo or a Bluetooth headset and select it as Output in SquelchDuck.
- Select the USB interface as Input.
- Tap Start, feed a steady tone or radio audio into the interface, and lower the threshold until the meter moves and audio plays.
Pass: you hear the USB input through Bluetooth while monitoring stays running.
Fail: USB shows up, but playback is silent, glitchy, or the session errors when Bluetooth is connected. That phone may not support USB capture and Bluetooth playback together.
Step 3 — Does music duck when the radio talks?
With music playing in another app, open the gate (raise the radio audio or lower the threshold). Music should get quieter or pause, then resume after the hold time. Some music apps and head units ignore Android’s focus request — that is a soft failure, not a USB failure.
Which USB audio interface to buy
Buy this kind of device
Look for a small USB Audio Class (UAC) / class-compliant interface that:
- Needs no special Windows or Mac driver (“plug and play”)
- Is bus-powered (powered from USB) — ideally through your powered OTG hub
- Has a line or headphone-level input you can wire from the radio (RCA, 3.5 mm, or 1/4 inch)
- Is stereo or mono, one or two inputs — you do not need a studio mixer
A good example of that category is the Behringer UCA202 (USB with RCA line in/out, bus-powered, no vendor driver).
Android’s built-in USB audio support targets USB Audio Class 1, PCM, mono or stereo. Fancy multi-channel interfaces often only expose the first one or two channels on a phone, or fail to enumerate.
Pair the interface with a powered USB OTG hub for your phone’s port so the phone stays charged and the interface stays powered. The hub must support USB data/host (not charge-only) and ideally charging or PD passthrough to the phone.
Radio wiring note
Use the radio’s external speaker, headphone, or line out into the interface input. Match levels with the interface’s input and SquelchDuck’s threshold/gain settings. A USB microphone pointed at the radio’s speaker will not work in practice — the loop through the car speakers creates feedback.
What we have verified
Phone and interface combinations are device-dependent. We publish pairs we have actually tested as we complete hardware validation. Until a combination appears here, treat any purchase as “test and return if Step 1 or Step 2 fails.”
| Phone | USB interface | USB input listed | USB + Bluetooth together | Notes |
|---|---|---|---|---|
| — | — | — | — | No full USB + car path published yet |
Preferred: when your setup is working, open SquelchDuck → Diagnostics → Report working setup. That emails us a diagnostic report (phone, Android version, devices, settings) pre-addressed to support — the easiest way to grow this table.
You can still email support@improvlabs.com manually for failures or odd cases; include the phone model, Android version, interface model, and a diagnostic report if you can.
Quick troubleshooting
| Symptom | What to try |
|---|---|
| Interface LED on, nothing in USB input list | Powered USB OTG hub; different cable; confirm the device is class-compliant |
| Phone battery drops while monitoring | Use a powered USB OTG hub that charges the phone while the interface is connected |
| Interface drops or crackles after a while | Powered hub / better power to the interface; check for loose OTG cabling |
| Listed as input, no sound on Bluetooth | Phone may not do USB + A2DP together; test with wired headphones; try another phone |
| Works then drops when the cord moves | Cable/hub strain; SquelchDuck will wait and reconnect when the same device returns |
| Music never ducks | Focus is best-effort; try another music app or focus policy in Settings |