I was using the app normally for a long time on my Poco F5 phone until a little over a month ago when it started going silent if there was no sound from my PC for about 15 or 20 seconds. It’s as if it stops working in the background. If that happens, I have to open the app for it to work again. I don’t need to do anything else; I just have to open the app for it to continue playing the audio from my PC.
I tried the tips shared in another post with the same problem, but they didn’t work for me.
I just tested the latest version (1.0.0-alpha07) on both my PC and my Xiaomi phone, but the issue still persists.
If I pause the audio on my PC for a few minutes and then resume it, I get no sound on the Xiaomi device. However, the moment I open the AudioRelay app on the phone—even in the fraction of a second before the UI fully loads—the sound immediately returns.
Troubleshooting already performed:
Set Battery Saver to “No restrictions” for AudioRelay.
Disabled the “Pause app activity if unused” option in Android settings
One simple solution may be to add an option in the PC/Android app to emit a “silent noise” (inaudible pilot tone) at specific intervals or continuously when the audio is paused. I tested playing a very low-volume sound through a browser on my PC while the main audio was paused. With this constant stream of data, the connection stayed active and did not cut off. As soon as I stop the background noise and leave it in total silence for a few minutes, the Xiaomi device loses the connection again.
I tested it last night for a few minutes, but it seems the audio still cuts off after a few seconds.
Additionally, I’m experiencing an issue on PC: if I bring the app interface to the foreground to look at the settings, the application completely closes by itself after 10–15 seconds without any warning or error message, and I have to reopen it.
@hwf1324@Popescu.oge First, we should verify that AudioRelay correctly enabled the workaround on your end. Go to Settings → Audio → Regularly play an inaudible tone.
If that’s the case, then maybe the cutoff is more aggressive than on my test device. The OS kills the output after 1 min of silence on my end.
On my device, there are some clues about what’s happening in the OS logs. Would you mind sending them? (Not the app’s logs as they don’t contain the OS’ messages)