Enthusiast I

15.8 update is a nightmare

147 replies
8245 views
Translate All

i have samsung tv that connected to beam 2 by HDMI to Earc until yesterday every thing work fine.

after the update to 15.8 the beam refuses to connect to the tv. i talk with the support and we tried everything. the only way to get the beam to connect is unplug the power cable and plug it back every time i turn my tv this is the only way. since yesterday that what i do every time i turn my tv.

its a nightmare sonos have to fix this issue.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Pinned Reply By Corry P

Hi @orenhazan et al

There was a similar issue recently whereby Beams would have no audio when playing TV audio coming from certain Samsung TVs, which has now been resolved. As your TV and Beam seem to be losing the connection between them, however, this seems like a different issue. I recommend you get in touch with our technical support team who have tools at their disposal that will allow them to give you advice specific to your Sonos system and what it reports.

I hope this helps.

View in thread

Show previous replies

B

Bernzzz007

Lyricist I

Same issue with me guys. Every time I turn on the TV, I find out that the Sonos beam 2 got disconnected from my Samsung TV S95b. Same thing, I have to unplug the Sonos beam from power, then plug back in to make it work. Very frustrating! I hope Sonos solves this on their next update.

Translate

Airgetlam

This really sounds like a local issue, not one that is endemic across the board. Have you tried to call Sonos Support directly to discuss it?

When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your Sonos system and network.

Translate

Bruce

Ken_Griffiths

Same issue with me guys. Every time I turn on the TV, I find out that the Sonos beam 2 got disconnected from my Samsung TV S95b. Same thing, I have to unplug the Sonos beam from power, then plug back in to make it work. Very frustrating! I hope Sonos solves this on their next update.

I’ve now only seen this type of issue reported with some Samsung TV’s - I have personally seen LG, Philips, Sony and Sharp TV’s all working okay with the current Sonos build, so it appears mostly Samsung related (just some models, not all) - it maybe the case that Samsung needs to fix something here - so it might be worth speaking to their customer support desk too, as they’ve attempted to fix a few issues with their TV’s and soundbars in recent (September) firmware updates, which (apparently) some Samsung users have been complaining about online.

Translate

O

orenhazanAuthor

Enthusiast I

Same issue with me guys. Every time I turn on the TV, I find out that the Sonos beam 2 got disconnected from my Samsung TV S95b. Same thing, I have to unplug the Sonos beam from power, then plug back in to make it work. Very frustrating! I hope Sonos solves this on their next update.

don’t waste the time to talk with samsung support the problem is 15.8 update. sonos working on a fix to this issue and thay admitted that the problem is the 15.8 update.

thay told me that they hope that the issue will slove in 15.9 update.

the issue is only with samsung tv and especially the s95b. i have also this model of tv.

Translate

D

Daidalus

Lyricist III

The issue is happening on other TVs also ( i have neo-qled QN90B).

Its more than 3 weeks that we have an issue that practically makes our system unusable, and yet Sonos has done nothing to fix it. I mean, does the concept of hot-fix eludes them? How is this acceptable?

Translate

Ken_Griffiths

The issue is happening on other TVs also ( i have neo-qled QN90B).

Its more than 3 weeks that we have an issue that practically makes our system unusable, and yet Sonos has done nothing to fix it. I mean, does the concept of hot-fix eludes them? How is this acceptable?

You could perhaps go onto use the supplied ‘optical to hdmi’ adapter that came with the Sonos soundbar - that would be a quick fix until the issue is resolved by whoever is due to perhaps fix this issue.

Translate

O

orenhazanAuthor

Enthusiast I

The issue is happening on other TVs also ( i have neo-qled QN90B).

Its more than 3 weeks that we have an issue that practically makes our system unusable, and yet Sonos has done nothing to fix it. I mean, does the concept of hot-fix eludes them? How is this acceptable?

You could perhaps go onto use the supplied ‘optical to hdmi’ adapter that came with the Sonos soundbar - that would be a quick fix until the issue is resolved by whoever is due to perhaps fix this issue.

optical its only for dolby digital and not support dolby atmos.

Translate

O

orenhazanAuthor

Enthusiast I

The issue is happening on other TVs also ( i have neo-qled QN90B).

Its more than 3 weeks that we have an issue that practically makes our system unusable, and yet Sonos has done nothing to fix it. I mean, does the concept of hot-fix eludes them? How is this acceptable?

from the beginning of this issue this is what i ask myself.

Translate

Ken_Griffiths

You could perhaps go onto use the supplied ‘optical to hdmi’ adapter that came with the Sonos soundbar - that would be a quick fix until the issue is resolved by whoever is due to perhaps fix this issue.

optical its only for dolby digital and not support dolby atmos.

Which is still far better than having no TV audio due to it dropping out, was my actual point.

Translate

M

Mr.T.

Lyricist II

Same issue here, Samsung S95B, Beam is not detected by TV, even though it outputs sound together with TV at that time. Volume can be change using app only when that happens.

There is extra device connected to TV by CEC-less adapter, bought because of this issue, but it didn't help.

Also issue happens even when only Beam was connected. The only way to recover is to power-cycle Beam and If you have to do it multiple times per day its annoying and it's only temporary work around.

It has been working rather fine for past few months, after last update it broke. Sonos please fix this.

Translate

Show more replies

Sign up

Login to the community