When using ROON ARC with my Bluetooth earbuds, Sony's WF-1000XM5 (on a Samsung Galaxy S24 Ultra phone), music does not pause and resume automatically correctly when one of the earbuds are removed and placed back in my ears. Specifically, music on ROON ARC pauses (most of the time but not all, after a brief delay) when an earbud is removed from either ear, but music on ARC does not resume playing when the earbud is placed back in my ear.
This auto-pause upon earbud removal feature of these earbuds works correctly on numerous other media apps I have tried on the same phone.
Additionally, ROON ARC seems to mishandle the pausing of music when these earbuds' speak-to-chat feature is triggered. This feature should pause the music being played while allowing in ambient noise, such as during a conversation. A few moments after the speaking ends, the music then resumes and noise cancellation is resumed.
While using ROON ARC, when speak-to-chat is triggered by talking, the music briefly pauses but resumes about a second later, even if I am still talking.
To troubleshoot, I have ensured I am on the latest versions of ROON ARC, my ROON ROCK server, the phone's software, and the firmware of the Sony Bluetooth earbuds. I have also uninstalled and reinstalled ROON ARC from my phone.
Thank you for the report. We want to confirm the event we’re observing in ARC diagnostics matches the issue you’re describing. Can you please provide the name of a track that was playing when this specific symtpom below last occurred?
Thank you for the follow-up. We’ve captured the event in diagnostics and are passing to development - please stand by and we’ll have an update as soon as possible.
Are you still experiencing this on the most recent ARC build? There have been numerous bug fixes to interruption management in ARC and we’d like to see if there’s additional work for this particular endpoint.
Please provide an approximate timestamp of the auto-pause handling event, if so. Development will investigate promptly.
The last several ARC builds have contained incremental changes and improvements to connectivity and interruption handling. Is this symptom still present on the latest release?