[jespertt]

Nah - that's just not true. We've pushed this update to tens of thousands of units over the past week - and we have not seen this issue reported before gHuntleys post, and then subsequently in the comments to his post in our community.

Previously, i mentioned the notion of it being a data corruption issue. We have integrity verification, so this is extremely unlikely, but as it is an easy check, we recommend trying this out. If you try to re-upgrade, and it skips the “transferring” step and goes directly to “Ready to patch”, it means that the previous upgrade had been successful with no corrupted data and that you have had the correct firmware on your speaker. (In this case it will be a very fast process) If however, it started to transfer files, it is worth to wait until the transfer step is completed to make sure you have the right firmware. In the meantime, we will continue to investigate internally in SOUNDBOKS, and try to figure out why some users are experiencing this, when we are not experiencing it ourselves, and it has not occurred in any of our testing.

Again, thanks for your engagement.

[dpratt]

I find it fishy that you haven’t connected the dots between “firmware update meant to mitigate speaker cone damage under specific power delivery circumstances” and “user experiencing unexpected power reduction at all power delivery circumstances”.

Blaming the user here is not endearing you to the community.

[sitkack]

Where is the blame? I see a lot of dog piling on a person who is genuinely trying to fix a problem.

[dpratt]

It’s probably because a bulk of his replies have been along the lines of “the update transfer was probably corrupted, you must have misapplied it. Can you try again?”

[Bjartr]

At least one person in this thread alone mentioned reapplying the firmware update fixed it for them. "Try it again" is a common troubleshooting step for a good reason. There's no reason to assume malice from the presence of such a suggestion.

[Aeolun]

If trying again (and downloading a new payload) after the issue is revealed magically solves the problem without the company admitting they pushed a fix, I’m a little bit dubious.

[Bjartr]

Maybe it was actually what they claimed about it being a corrupted update then? And considering the issue is still an active fire they're putting out, I'm l is give them the benefit of the doubt. They seem to be genuinely scrambling, so their comms are going to suffer. If, in a couple days, things haven't changed, then there's reason to question the intentionality of missing followup communication.

Also, if they pushed a fix that worked reliably, they'd be shouting that loud and clear as THE solution, not merely suggesting to try updating and to see if it might help.