28-12-2018 06:26 PM
Hi, I have a samsung K series tv - bought in 2017 and a Samsung hw-j355 bought at the same time. Up until recently the sound connect has been working flawlessly but it has now stopped turning on the the sound bar. Once on it connects and it responds to the tv remote with no problems. Why would it have stopped working?? I’ve tried removing it from the tv and re-pairing it. I’ve tried a factory reset on the tv but it hasn’t worked. I’m kind of out of ideas! Any suggestions would be welcome!
Solved! Go to Solution.
14-03-2019 07:30 PM
The fix is simple. Just roll back the update to the previous version. I really don't know why they are taking so long to do this as it's so simple
14-03-2019 07:55 PM
14-03-2019 08:16 PM
No Samsung do not allow users to do it themselves
15-03-2019 12:19 AM
No kidding!
16-03-2019 05:26 PM
I have a HW JW7500 curved soundbar which has now been rendered useless. It is attached via the HDMI Arc and has functioned perfectly since I got it in 2016. Now the Samsung UE65MU6400 says there is no signal coming from it at all although it recognises a connection. It doesn’t turn on or off with the television. I cant even tell what firmware it has as I have nothing to read it on. Infuriating.
17-03-2019 12:01 AM
17-03-2019 08:46 AM
You can't roll it back yourself Samsung need to do it for us.
17-03-2019 08:59 AM
It's probably the firmware in the TVs that's changed, as a bluetooth phone will enable the soundbar, but the TV won't.
18-03-2019 08:43 PM - last edited 18-03-2019 08:44 PM
I found a workaround which let me turn the soundbar with my TV, also using the remote controller with an AppleTV for volume (as opposed to D-IN which made me use the soundbar remote controller for that).
Just connected the soundbar HDMI output to the SmartTV ARC HDMI port. Didn't use the soundbar input, no hdmi cable attached to this port. Then, select the Soundbar (HDMI) as sound source.
Automatically turns ON with my TV and it lets me use the TV Remote control with all available sources.
19-03-2019 10:38 PM - last edited 19-03-2019 10:44 PM
Same issue here....waiting Samsung....