AudioRelay Not Working | Fast Fixes For PC Phone Audio

Why Connections Fail In AudioRelay

AudioRelay links your PC and phone over Wi-Fi, USB tethering, or the local network to stream system audio or use the phone as a mic. When a link fails, it’s usually one of four buckets: firewall rules blocking traffic, devices not on the same route, missing or muted audio devices, or a server-client version gap. Fixing the baseline removes most headaches fast.

If your search is “audiorelay not working,” start with the basics. Confirm both apps are current, the Android app sees the Server, and your PC shows a normal audio device in Windows. If the phone lists the server but won’t connect, a firewall or network profile is often the blocker. If you connect but hear nothing, the output device or stream settings need a look.

Quick Checks That Solve Most Connection Issues

• Restart Both Ends — Reboot the phone and the PC to clear stale sockets and drivers.
• Update Server And App — Install the latest Windows server and Android app to avoid version mismatches.
• Same Network — Put both devices on the same LAN; avoid guest Wi-Fi that isolates clients.
• Private Network Profile — On Windows, set the current network to Private so discovery rules apply.
• Firewall Allow — If connection works only with the firewall off, add explicit allow rules for AudioRelay and then re-enable the firewall.
• Try USB — If Wi-Fi is flaky, switch to USB tethering for a clean, wired path.

When discovery fails, tap Search and enter the server’s IP address. Use the PC’s IP from ipconfig or Windows network settings. If the manual entry works, auto-discovery was filtered by guest isolation or a strict router mode.

Fix AudioRelay Not Working On Windows

Temporarily disable the firewall to test. If the link succeeds, add inbound and outbound rules for the AudioRelay server, then turn the firewall back on. On Windows, pick a Private profile so discovery works. Reinstalling the server with the “Add firewall rules” option ticked also helps when rules were skipped during setup.

Third-party antivirus often has its own firewall. Add AudioRelay to its allow list as well. Some suites only trust apps once they have run during a learning window; a reinstall can refresh those entries.

If you connect but hear silence, confirm a valid output device exists and is unmuted in Windows. Run Troubleshoot sound problems from the taskbar menu to have Windows re-enable disabled devices. Then return to AudioRelay and select the correct output. Toggle the output once to refresh the route.

If the server refuses to open, end lingering tasks in Task Manager, then launch again. Conflicting instances can block a clean start. If it still stalls, reboot once to clear file locks.

Corporate Wi-Fi and university networks often block peer discovery. At home, routers may isolate clients on “guest” SSIDs. Use the main SSID or a wired PC connection to keep packets on the same segment.

Work through Windows in a simple order: test with the firewall off, connect once, then create the allow rules and turn the firewall back on. If you run a security suite, repeat the allow step there. Finally, switch the network profile to Private and try a manual IP connect. That sequence confirms policy blocks before you spend time on cables or routers.

Windows Firewall Steps That Work

1. Open Windows Security — Press Start, type Windows Security, and open it.
2. Allow An App — Click Firewall & network protection > Allow an app through firewall.
3. Add AudioRelay — If AudioRelay is missing, click Change settings > Allow another app, browse to the server executable, and add it.
4. Tick Private — Ensure the Private box is selected so discovery works on home networks.
5. Reopen The App — Close and relaunch the server and the Android app, then connect again.

Third-party suites: If you use a security suite with its own firewall, mirror the same allow steps there. Many suites quietly block new apps until you approve them once.

Mic Feature Not Working

• Pick The Right Input — In the Windows sound settings, choose the AudioRelay virtual input as the Default or select it inside your calling app.
• Grant Mic Permission — In Windows Privacy & security > Microphone, allow desktop apps to access the mic.
• Reconnect After Change — Disconnect in the Android app, then reconnect so the new device path is applied.

Network Profiles And Guest Isolation

Home routers often run separate “guest” networks that block device-to-device traffic. If one device sits on the guest SSID and the other on the main SSID, discovery breaks and streams can be filtered. Put both on the same SSID or use USB.

• Same Band — Lock both devices to either 2.4 GHz or 5 GHz to avoid band steering quirks.
• Disable Isolation — If your router exposes an AP isolation toggle, turn it off on the SSID you use.
• IP Check — Confirm both devices share the same subnet (e.g., 192.168.1.x); if not, they’re on different segments.

Manual IP Connect, Step By Step

1. Find The PC Address — On Windows, open Settings > Network & Internet > Status > Properties and copy the IPv4 address.
2. Enter In The App — On the phone, tap Search, pick manual entry, and type that IP.
3. Test Over USB — If the manual entry fails on Wi-Fi, try again with USB tethering enabled to rule out wireless filters.

Power And Performance Tweaks

• Disable Battery Savers — On the phone, turn off battery saver during streaming so background processes aren’t throttled.
• Keep Screen Dim — If audio cracks only with the screen lit, lower brightness or let it sleep while listening.
• Prefer Wired Earphones — When testing, use wired headphones first to remove Bluetooth lag from the equation.

Stutter, Delay, Or No Sound: Stable Streaming Settings

Choppy audio points to Wi-Fi congestion or too little buffer. Reduce noise by placing the phone near the router, using 5 GHz, or plugging the PC into Ethernet. If Bluetooth introduces interference, disable it during streaming. For the player, increase the buffer on the receiving side when possible to smooth spikes in latency.

• Prefer 5 GHz — Use a 5 GHz SSID when available; it handles short bursts better than 2.4 GHz.
• Move Closer — Shorten the distance to the router and keep walls to a minimum.
• Wire The PC — Connect the computer by Ethernet to cut wireless hops in half.
• Switch Output Mode — In the Android app, try AudioTrack if the default mode crackles; it may trade a little delay for stability.
• Raise Buffer — A higher buffer steadies playback when your network spikes.
• Screen Off Test — If audio only breaks when the screen is on, test with the display off to confirm power-related throttling.

Lower buffers feel snappy, but the player won’t go below its internal minimum. If you set a tiny max and it jumps back up, that’s the app protecting stream quality.

Streaming Android-to-PC and PC-to-Android use different paths. If only one direction fails, focus on the receiver. For example, if PC audio won’t reach the phone, check the Windows output device, then try USB. If the phone’s audio will not play on the PC, raise the buffer in the PC player and retest on 5 GHz.

AudioRelay Connection Not Working — USB Tethering Fix

USB tethering creates a direct link from phone to PC and bypasses crowded Wi-Fi. The server appears as a new entry you can select inside the app once tethering is active.

1. Connect By Cable — Plug the Android phone into the PC with a data-capable USB cable.
2. Enable USB Tethering — On Android, open Network & Internet > Hotspot & tethering, then toggle USB tethering. Wait a few seconds for Windows to configure the link.
3. Select The USB Server — Open AudioRelay on the phone and tap the fresh server entry that appears for the USB interface.

If the app keeps asking you to turn on tethering even after you did, tap the in-app shortcut again; it’s only a shortcut to the settings, not a status indicator. After Windows finishes installing the adapter, hit Search in the app and connect.

Toggle tethering off and on again, swap the cable, try a different USB port, then reopen the app. Windows needs a moment to add the network adapter the first time.

USB also avoids router quirks and keeps latency steady. It may use carrier data if your phone plan treats tethering as mobile sharing, so prefer Wi-Fi only mode when possible. On first use, Windows installs a network adapter; give it a moment before tapping Search.

Connection Symptoms, Likely Causes, And Fast Fixes

Symptom	Likely Cause	Fast Fix
Server shows but won’t connect	Firewall rule or Public network	Allow in firewall; switch to Private profile
Connects but no sound	Disabled or wrong output device	Run Windows sound troubleshooter; pick correct output
Lag, pops, hiccups	Wi-Fi congestion; low buffer	Use 5 GHz or Ethernet; raise buffer; try AudioTrack
Phone never sees server	Different subnets; client isolation	Use same SSID; avoid guest Wi-Fi; try USB tethering
Server won’t open	Stuck background process	End tasks in Task Manager; relaunch

When Nothing Works: Clean Reinstall And Useful Logs

Uninstall AudioRelay on the PC and phone. Reboot both. Download fresh installers, then install the Windows server with firewall rules enabled and the Android app from the store. This resets rules, drivers, and permissions in one sweep.

If the app drops the link or fails at the same step, capture a quick logcat. Install ADB, enable USB debugging, run adb logcat > log.txt, reproduce the failure with USB tethering, then stop the capture. The log helps pinpoint blocked ports or device errors.

Stable Setup Tips

Favor one stable path and stick to it. If Wi-Fi is busy at home, make USB your default. If Wi-Fi is fine, keep both devices on the same 5 GHz network name, mark the Windows network as Private, and leave the allow rules in place. If you ever bump into “audiorelay not working” again, this base setup narrows the cause to cables, ports, or a single app update.

• One SSID — Use the same SSID band for both devices; avoid mixed 2.4/5 GHz hopping.
• Router Channel — Change the channel if neighbors crowd yours.
• Startup Order — Open the Windows server first, then the Android app to shorten discovery time.
• Short Cable — For USB, use a short, known-good data cable to avoid random disconnects.