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.
It would make sense (perhaps) if Samsung do use some kind of TV security that sets them apart from other brands of TV. It would explain why most other brands are not affected by the recent updates. Anyhow I’m fairly sure that Sonos/Samsung will resolve the issue at some point, going forward, and hopefully that will hapoen sooner, rather than later, for those customers who have encountered these issues.
edit: Oh and I would personally wait, rather than disable any security settings, as that may invalidate any Samsung warranty/support etc.
Just use the Optical-to-HDMI adapter for the time being - very little is lost between Atmos and Dolby Digital 5.1 surround sound.
i talk also today again with the technical department of samsung i sent them an email and they got back to me.
they told me that the problem is with Knox security protcol that all the samsung tv from 2018 have. and the change that sonos made from 15.8 in some of their speakers affect the connection when turning on the tv.
sonos have to fix that issue.
i working on a temporary solution with a friend to disable the Knox security in the service menu of the tv. i hope that we will succeed to do that.
I always thought that was the security platform for their mobile devices🤔… a list of Samsung products that use knox are shown here:
https://www.samsungknox.com/en/knox-platform/supported-devices
i talk also today again with the technical department of samsung i sent them an email and they got back to me.
they told me that the problem is with Knox security protcol that all the samsung tv from 2018 have. and the change that sonos made from 15.8 in some of their speakers affect the connection when turning on the tv.
sonos have to fix that issue.
i working on a temporary solution with a friend to disable the Knox security in the service menu of the tv. i hope that we will succeed to do that.
15.9 frimware didn’t fix the 15.8 beam 2 connect issue. let’s hope that in the next update version it will happen.
Perhaps also keep an eye out for Samsung firmware updates too, just in case the fix is perhaps due to come from their side of things here.
i talk also with samsung and they investigate this issue and tell me that sonos make a change to the HDMI behavior from 15.8 frimware that effect samsung tv and the fix for that have to come from sonos.
and to strengthen this issue i take today from my friend a beam 2 with 15.7 frimware and connect it to my samsung tv. everything work fine and the beam 2 connect to the tv every time i turn on the tv without any problem.
Update to version 15.9 did not help.
15.9 frimware didn’t fix the 15.8 beam 2 connect issue. let’s hope that in the next update version it will happen.
Perhaps also keep an eye out for Samsung firmware updates too, just in case the fix is perhaps due to come from their side of things here.
15.9 frimware didn’t fix the 15.8 beam 2 connect issue. let’s hope that in the next update version it will happen.
15.9 is here i update my system i hope this update solved the problem.
Same problem, sonos beam gen 2 (sw15. 8) +Samsung TV QN85BA
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.
today i talked with sonos support and they told me they were delaying the 15.9 update until they finish to work on solving the issue.
i hope that 15.9 solved this issue and we won’t have to wait to the next update from sonos.
What TV? Which settings?
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.
Tried any possible settings, e-Arc, Arc, cec, cec+, Auto, non-auto (PCM), passthrough.
Both App and HDMI source affected. If it's not connected, then its not connected, only power cycle of Beam helps. TV power-cycle don't resolve issue, so has to be Beam firmware related. Can provide diagnostic code.
+17
What TV? Which settings?
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.
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.
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.
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.
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.
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?
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.
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.
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.
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 also talk today with sonos and they told me the same thing. they are working on a solution to the problem and the cause of that issue is 15.8 frimware.
thank you very much for this update its the first time that i hear that sonos recognize the problem. i said from the beginning that the 15.8 frimware is cause that.
Be careful taking an anonymous post on a forum as an official company statement. They could have misunderstood, they could be making it up to stir up dirt, or they could be an irate customer that a frustrated support person tried to pacify, all of which have happened before.
My Arc suddenly stopped receiving audio from my Samsung tv. My tv wasn’t connected to the internet, so only the 15.8 firmware was a possible root cause. I spoke to Sonos support today which confirmed that there is an issue with certain Samsung tvs caused by the 15.8 firmware. They said their engineers were working on it with Samsung. Hopefully here’s a fix soon. Luckily I was able to find the optical audio adapter in the meantime...
thank you very much for this update its the first time that i hear that sonos recognize the problem. i said from the beginning that the 15.8 frimware is cause that.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
