I'm on Android 14 (Galaxy S24U), but I've noticed these issues for about a year now, even with the S22U I had. It seems like the standard Android music player code is bugged, such that the app will occasionally bug and not let me resume or pause my music through the buttons on my headphones or through the notification bar on the lock screen. Every other media player app (TIDAL, YouTube, etc.) will appear properly and pause and resume properly, but ARC just glitches sometimes, a really big annoyance if I'm listening to music on the go, someone says something to me, and I need to pause the music to hear them. I currently use the WF-1000XM5's, but I've had this issue with Galaxy Buds2 Pro's. The issue has persisted across reboots, across app updates, and across reinstalls.
Describe your network setup
I often have ARC set to offline mode and playing downloaded music as my computer that runs the server is off (going to build a little homelab at some point to run Roon 24/7), though this has happened regardless of the status.
When my machine is online and I have offline mode disabled, the setup is:
Custom built computer (2.5Gbps NIC, though the cable maximizes at 1Gbps) -> 5 port Ethernet switch -> Comcast Router -> (whatever else it goes through) -> my phone
Hi @GarbageGamer,
Thanks for writing in to ask about this issue. I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
@daniel (sorry for making it a ping, I forgot to originally make the post a reply)
Just happened right now (11:37am ET) while I was listening to music remotely on my phone with my Roon Core on. The track no longer appears within the media player section like it normally does.
Edit: A minute later (after pausing the track to write this), I went back into the app to resume the track again. Now it appears properly, as shown below:
Hi @GarbageGamer,
Are you using NextDNS anywhere? We’re having trouble fetching logging from your ARC installation. That has previously been caused by NextDNS.
@daniel (I swear I keep forgetting to hit reply, I’m sorry lol)
I’m not using NextDNS, though I realized that I didn’t add ARC as a split tunnelling app on my VPN. I’ll add that now and let you know when (or if) the issue happens again
Edit: literally right now, it happened. I added ARC to the split tunnelling list yesterday (and forgot to reply till now) and the issue is occuring.
The use of VPNs is outside the scope of our support, and it is likely that this configuration is preventing diagnostic information from your Arc remote from reaching our servers.
If you’re able to temporarily bypass the VPN setup and reproduce the issue, please let us know so we can investigate further. We apologize for any inconvenience this may cause and appreciate your understanding!
While we appreciate your update, we’re still not seeing any traces of Arc logs related to your installation, so there seems to be some additional blockage occurring between your device and Roon’s upstream servers.
Without being able to see logging, we’re unable to review what might be occurring behind the scenes.
Do you only see this issue when using your headphone buttons or lock screen controls? Do you ever run into this issue with using Arc normally?
This could potentially be causing you some issues, do you ever see this issue when your server is powered on and connected to your network? Note that Roon Server was built around the idea of it being online with a constant network connection. Anything outside of this may lead to odd happenings.
How long do you go between periods of your server being powered off, and using Arc with offline content?
If you could, please completely disable your VPN or any other network blockages that could be preventing us from further reviewing additional Arc diagnostics. This will likely be the only way we’ll be able to help you further. Thank you for your understanding and cooperation.
That may stem from my phone having AdGuard DNS on; I just remembered that. I can disable the private DNS server temporarily while running Roon ARC so the logs can transfer properly.
It’ll happen when I try using my headphones buttons or lock screen controls; they both use the Android media player API or whatever it’s called. I’m not really sure what you mean by using ARC “normally”, since I feel this constitutes as normal usage.
For the past 3 or so weeks (at least since I started this thread), I’ve kept my computer on when running ARC (and just 24/7, disregarding the occasional restart or two). I plan to build a proper homelab server to put Roon onto so I can have a more permanent solution, though that’s a project that I’ll have to tackle a different time.
Thank you for your continued patience and for supplying the team with the necessary diagnostic events. We have what we need to proceed with engineering.
If there’s a fix to the interruption manager released that will resolve this behavior, we’ll give you a ping here before it goes into Early Access. Otherwise, we’ll let you know the results of what we find and any next steps required to mitigate the behavior.
