Friday, 25 August 2017

Samsung TVs hit by killer software update


The curse of TV software updates has struck again. Unlike most recent update problems, though, this time it’s owners of Samsung rather than LG televisions who have been affected.
As initially reported by The Guardian, it appears that following a firmware update rolled out last Thursday (August 17), ‘thousands’ of owners of multiple models of Samsung TVs are reporting significant issues. For some of those affected, their Samsung TV either gets stuck on one channel and won’t reply to remote control commands. For others the TV just gets stuck on the home screen, or else their TVs just won’t turn on at all. TVs reported as affected include various models from the 2017 MU6, MU7, and MU8 ranges. So far as I can see, there haven’t yet been confirmed issues with any older generations of Samsung TVs, or any of Samsung’s 2017 QLED TVs.
It also seems that, strangely, the problems are only affecting European models; there’s no widespread chatter about similar issues on forums or Samsung community boards in other territories. Nor does it seem that the update problems are affecting every MU set; searching through other MU owner forums reveals plenty of people with MU models yet to experience any post-update problems. Moderators on the European Samsung community boards have fed back, however, that Samsung is aware of the issue, and have also suggested that a fix has already been discovered. However, it seems at the time of writing that this fix requires an engineer visit, rather than being something that can be pushed out automatically.
As well as being inconvenient to customers already frustrated by not having a functioning TV for more than a week now, if the problem really can only be fixed by an engineer visit then sorting out everyone affected could potentially take some time. Reports on Samsung’s European community forums also suggest that the first engineer visit designed to address the problem ended in failure, with the engineer having to take the TV away for further analysis.

No comments:

Post a Comment