Skip to main content

Hi

Had my arc just short of a year and tonight I turned on my xbox series x I use to watch bluerays, it was sitting on the dashboard and suddenly there was a loud bang and it was like the arc rebooted.

 

A quick Google suggested this may be a known issue but for my own sanity I ran a diagnostic report and contacted sonos for a health check on the arc.

According to the sonos agent they could see an amp fault 

"I see. I can see that your Sonos Arc is having an Amp Fault. And for this one, we just need to reboot the Sonos Arc. Just unplug it to the power outlet and plug it back in after 10 seconds. Then observe if the Arc is still producing the loud pop noise so we can further isolate the issue."

I rebooted the arc and sent another diagnostic and he said it was clear. But I'm know wondering if I have an actual hardware fault and I don't want to just leave it for it to eventually break.

 

Any advice welcome

 

The above seems to be a duplicate post - see this post in the main thread…

I suggest responding in the other thread.

Hi @Shaunpk 

 Good news! We are pleased to share that our team has identified a fix for the popping sound on Arc and it will be shipped to all customers as part of a software release today, Thursday Nov 16 at 09:30 ET, 14:30 GMT, 15:30 CET. Please note that some app stores may take an extra hour or two for it to become available.

During our investigation we uncovered a rare bug that impacts how Sonos Arc and Beam (Gen 2) in certain home theater configurations process Dolby MAT, a streaming technology which is used to deliver Dolby Atmos audio over HDMI. Occasionally a Sonos product will receive a corrupted audio segment from an external source and needs to filter out unwanted audio data. The bug we identified was allowing our Dolby decoder to play audible errors on certain home theater setups rather than concealing them. The solution we’ve built and tested improves our Dolby decoder so it better filters out corrupt audio data that can manifest as a popping sound. We’ll continue to monitor customer feedback closely after the fix has been released and ship additional updates if necessary.

We strive to deliver the best listening experience possible and work to address major issues that impact our customers. We apologize for the disruption this bug has caused and want to thank you for your patience while our team developed a fix.

We would also like to thank our community users for their detailed setup information and steps to reproduce the issue, which were helpful to us in uncovering the cause of the bug.

If you have any questions, please post them on the main related thread and I’ll do my best to answer them.

This thread will be closed to keep all queries in that one place.

 

 

 

Terms & ConditionsCookie settings