Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Samsung Q990D unresponsive after 1020 firmware update

us.community.samsung.com

Post reply on HN
Print view View original

141–150 of 580 posts

Re: Samsung Q990D unresponsive after 1020 firmware update

#141

Post by [deleted] »

JimDabell wrote: post #106
tomstokes wrote: post #18

Two important features I insist on for products I develop: 1. Staged rollout of firmware updates. It’s common practice for apps and software but for some reason it’s less common with firmware. Rolling out to 1% (or less, depending on scale) of devices and waiting a day is cheap insurance. Side note: Build a good relationship with customer service people so you hear about these things immediately. 2. A failsafe firmwa…

Reverting to factory state seems riskier than last known good state. You could run into things like TLS root authorities not being recognised, deprecated cipher suites, etc. Just because that version worked a decade ago, it doesn’t mean it’s compatible with the world today.

[deleted]

Re: Samsung Q990D unresponsive after 1020 firmware update

#142

Post by JimDabell »

tomstokes wrote: post #114
JimDabell wrote: post #106

Earlier quoted context omitted.

Reverting to factory state seems riskier than last known good state. You could run into things like TLS root authorities not being recognised, deprecated cipher suites, etc. Just because that version worked a decade ago, it doesn’t mean it’s compatible with the world today.

> Reverting to factory state seems riskier than last known good state. Reverting to factory state is the last resort. You don't have users do it unless there is no other good state to return to on the device. > Just because that version worked a decade ago, it doesn’t mean it’s compatible with the world today. That's why I said you have to include this in your test procedures. When you're planning for the long term y…

> > Just because that version worked a decade ago, it doesn’t mean it’s compatible with the world today.

> That's why I said you have to include this in your test procedures.

You can’t test the world. Even if your servers can correctly respond to requests from old software, it doesn’t mean that the network between you will too.

Re: Samsung Q990D unresponsive after 1020 firmware update

#143

Post by gr4vityWall »

davkan wrote: post #86
MiddleEndian wrote: post #49

Earlier quoted context omitted.

>That point has practical issues, because most consumer electronic customers are technically dumb. It's a speaker that worked fine until Samsung unilaterally broke it. I don't think the customers are the dumb ones here.

Customers will gladly use an outdated browser or OS with known exploits to access their most sensitive information. Automated updates are necessary evil. Even a smart speaker with a vulnerability could end up as part of a botnet.

Then we should strive to improve computer literacy. I think technological solutions should still ultimately empower their users.

Re: Samsung Q990D unresponsive after 1020 firmware update

#144

Post by mschuster91 »

koolba wrote: post #136
ChuckMcM wrote: post #119

Earlier quoted context omitted.

This doesn't get enough attention, waaaay too many of these issues are traced back to the vendor trying to "prevent" someone from using their product in a way that they don't like.

Why else would a soundbar need updates anyway? It either performs its well defined functions when you bought it or they sold you a device that doesn’t input/output sound. Updates for these types of things always fall into three categories. Either they’re gimping some unanticipated usage, they’re trying to insert ads, or they’re trying to gather more usage data.

> Why else would a soundbar need updates anyway? It either performs its well defined functions when you bought it or they sold you a device that doesn’t input/output sound.

Unfortunately there are soooo f..ing many devices out there that don't follow the specs, no wonder given how long and complex alone the Bluetooth specifications are, and HDMI/HDCP (which a soundbar with ARC support needs...) is even worse, and don't even try to get me started on CEC because that is an even bigger pile of dung, or stuff like GPUs that run HDMI over DVI, MHL or USB-C in DP mode and god knows what else people expect to "magically work" with a 5 dollar adapter they got off of Alibaba. And no, "audit products to follow the specs" isn't a foolproof solution either. That means that everyone has to deal with everyone else's quirks and at least the most popular devices and their manufacturers have to supply firmware updates to react upon reports of quirks.

Re: Samsung Q990D unresponsive after 1020 firmware update

#146

Post by Lanolderen »

grishka wrote: post #34
mcs5280 wrote: post #16

Earlier quoted context omitted.

Probably some new AI/tracking/ad delivery features

It's a speaker system. It plays sound. Why could it possibly have AI, tracking, or ad delivery?

Use the speakers as a microphone! WE HAVE THE TECHNOLOGY!

Re: Samsung Q990D unresponsive after 1020 firmware update

#147

Post by greesil »

tomstokes wrote: post #18

Two important features I insist on for products I develop: 1. Staged rollout of firmware updates. It’s common practice for apps and software but for some reason it’s less common with firmware. Rolling out to 1% (or less, depending on scale) of devices and waiting a day is cheap insurance. Side note: Build a good relationship with customer service people so you hear about these things immediately. 2. A failsafe firmwa…

Also a dev or dogfood population of devices used by employees

Re: Samsung Q990D unresponsive after 1020 firmware update

#148

Post by mrbonner »

I just snapped after 2014. Used to be a Samsung consumer with their TVs, galaxy phones, security cams, etc... Their hardware wasn't that bad. It was the software update either buggy or bricking my devices that threw me off. I swear never to allow another Samsuck (my little girl coined that) device in my home and family lives again.

Re: Samsung Q990D unresponsive after 1020 firmware update

#149

Post by liendolucas »

tomstokes wrote: post #18

Two important features I insist on for products I develop: 1. Staged rollout of firmware updates. It’s common practice for apps and software but for some reason it’s less common with firmware. Rolling out to 1% (or less, depending on scale) of devices and waiting a day is cheap insurance. Side note: Build a good relationship with customer service people so you hear about these things immediately. 2. A failsafe firmwa…

The important feature here I would insist on is to let the user decide when to do a firmware update. Not the other way round. That's the way to build a good consumer relationship.

Why on earth a sound bar needs to update its firmware? Why firmware needs to be in a couple of tweeters and a woofer? It should basically output audio from an input source.

Post reply on HN