[jespertt]

Hi Ghuntley and everyone,

Jesper, CEO and cofounder of SOUNDBOKS here.

Ghuntley, I’m sorry to hear about you and other people’s issues after the latest update.

This is new information to us, and is definitely not something that is intended. Nor does it have anything to do with the batteries.

In the newest firmware update, there is no audio updates to the SOUNDBOKS Gen 3. I spoke to our engineers, and their best guess is that there is something in the filetransfer of the update that went wrong, and therefore that you should try reupdating the firmware.

You can do this by going into the updates section in the app, and pressing re-update. I'll keep an eye on this thread, so please let me know how it goes and i'll liaise with our development team.

Again, my apologies for the issues that you are experiencing.

Jesper, SOUNDBOKS - [e-mail]

EDIT: there was a note in the original post where one of our customer support team members had said that the update ''dampen their sound more than it should'' - a note is that this is where it gets a bit more technical; our support team member mistaked the speaker for SOUNDBOKS GO (our other version), where we have pushed out an audio update. In that audio update, there is implemented a tweeter protection mechanism, that limits the volume increase on the tweeter when it gets too hot. That can in some cases limit the dB a tiny bit (we're talking something that's not hearable), but in some cases there is a calibration error on the base temperature of the tweeter, making it think it is way hotter than it is - which can make it dampen too much. That is a bug, and we're working on fixing that - but again, that is on the SOUNDBOKS GO, and has nothing to do with the SOUNDBOKS Gen 3 that the author has.

EDIT 2: A few people have commented that my original explanation is not a likely answer when more people are experiencing this issue. I am currently liasing with our engineering team, and will get back as soon as i know more.

Thanks to everyone engaging! We're working on solving the issue for GHuntley and other customers as fast as we can.

[Aeolun]

How could a problem in the filetransfer of the update successfully update the system, and then reduce the output volume as a side effect?

I also seems like that wouldn’t make sense considering multiple people appear to have the same issue.

[gaius_baltar]

This just sounds as a bad excuse ... a corrupted fw update apply with no checks? Not even a MD5? And magically reduces output power with no other side effects? Should sounds funny but this seems just another case of IoS (internet of sh*t) devices being retroactively crippled by the vendor.

Also, no way to skip the update? Shady as usual.

Also also: why the hell connect a speaker to the internet? Extra shady.

Also also also: Coincidentally, forcing this update and dropping the problem to the users seems cheaper than fixing the reported problems in the battery and charger. Shady as a black-hole now.

[vertis]

Agreed, this explanation doesn't make any sense. It seems very unlikely that it's a (successful) bad update unless there are deeper problems with their update process that allow it to be a problem for multiple people.

The authors broader points are valid as well. Firmware updates should come with changelogs.

[iasay]

Crazy shit like this happens all the time. However assigning a cause is a little early.

Years ago I wrote a firmware loader for an industrial Z80 system. All it did was read a file over the serial port into RAM, jump into it and then overwrite the EEPROM. I got a page quantity calculation completely wrong. It didn't update all the memory pages. Because the changes were fairly small and the code was assembled rather than compiled and the test cases were fairly light, it was released to clients. It still worked absolutely fine but the status LED didn't work on the device in a specific situation because the update CALL never got executed because it was neatly in a previous page that didn't exist any more.

Of course this was reported as (1) hardware had completely failed (2) the LED had broken and (3) it only works sometimes. All of which weren't true. No one had even mentioned that they had recently updated it. So I can see how it happens.

Thus the tyranny of unexpected behaviour is a deep and dark passage lined with monsters, misinformation and bad assumptions. You have to tread very carefully and not say things too soon because it makes you look even more of an idiot when you have to backtrack later.

[HelloNurse]

Not the kind of excuses that a technical audience receives well.

[duxup]

If they knew that they probably would have more to say ;)

[stefan_]

While we are here, why is the firmware update said to take 1-2 hours? How many moon landers worth of data is that firmware?

[jespertt]

Alright, a quick update after speaking with my tech team.

A while ago, we realised we are seeing some failed tweeters in Gen3. The issue occurs when a. playing with the battery and the power on the battery is too low, or b. playing with only the charger on high volume. In those cases, there is a possibility that for a couple of seconds, a high-pitched sound comes out of the speaker and the speaker will shut down afterwards, resulting in damaging the tweeter.

For this very issue: We have changed the failure mode in a way that it will not damage the tweeter during that shut down. We also made a slight change in the signal processing for the tweeter which further protect the driver from these sudden peaks.

The two things I mentioned above are the main changes in the latest firmware (2.0.1 and 2.1.1) for Gen.3.

I would also like to mention a few notes regarding the latest firmware:

The sound profiles have not been changed at all. The playback time is exactly the same as before, i.e. 5 hours on max volume in Power mode. (confirming the SPL is the same) The settings for the woofers have not been changed at all. The contribution of tweeter sound pressure level is only a minor fraction of the total SPL for the speaker and since the woofers’ SPL has not been changed, the total SPL should stay the same as well.

As a result of the above, we have not seen any SPL change in our measurements post-upgrade, and are not sure as to why some users are experiencing this.

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 skip 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!

[jespertt]

Update: we now have a customer in our US Facebook Community saying that reupdated fixed his issue.

''My upgrade failed initially and impeded speaker output. Allowing the upgrade to run again resolved the issue without any further frustration or impact to performance.''

[loloquwowndueo]

So you’re saying everybody else on the internet who is experiencing the same problem somehow had the same exact bit flipped for mysterious reasons and there is no integrity verification in the update process to catch this kind of thing. Also, the “bit flip” doesn’t cause a random crash (as is usually the case when that happens) but changes the functionality in a way that correlates with the updates to the web page related to being plugged into mains power which conveniently appeared at the same time in the website.

Got it.

[stoltzmann]

From the article:

>Now, as a reminder - I own two speakers - both speakers have had their performance nerfed by this firmware update.

So even not counting everybody else on the internet with the same issue, I find it quite unlikely that there would be the exact same transfer failure on two separate units.

This definitely sounds more likely to be a software issue.

[vertis]

+1 for the CEO engaging

-10 for an implausible explanation.

[jespertt]

Fair point. As a note, it's definitely not all users that are experiencing the problem, but I will liaise with our engineers and revert!

[AshamedCaptain]

It could also be for example that when the firmware fails to check out at boot, the speaker enters a "safe mode" where the volume is limited for some lawyer-related reason. And that the update tends to frequently fail to apply, or actually always fails to apply.

Still, "firmware update meant to mitigate speaker cone damage under specific power delivery circumstances" is pretty damning, and it's not the first time I see this. Nokia also did the same kind of update to a device I owned, a couple decades ago. The excuse was practically word-for-word, and also claimed speaker damage could occur if you didn't install it.

I didn't install it and the device actually had speaker damage... about 5 years afterwards, and because instead of a cable or a proper solder job, they had used a spring to connect the speaker to the PCB and it had wore out. Totally unrelated to the speaker cone or any type of high volume issue.

[Wowfunhappy]

Please allow your customers to downgrade to an earlier firmware.

Bugs happen, and that's okay. However, users need the ability to roll back to a working configuration, so they can use the product as they bought it instead of a different one which was swapped in later.

[causi]

Why is there such thing as a mandatory firmware update for a set of speakers? Now I'm not an audio engineer, but frankly I would never purchase hardware that hostile to user agency.

[Jcowell]

I can see a mandatory update in the form of legal requirements. For example I think Apple had to implement headphone safety limits in some countries leading to very frustrated customers .

[pjc50]

Are firmware updates signed/authenticated/hashed? It would be tragically hilarious if this was the outcome of of a single flipped bit in the transfer.

[thedanbob]

I was going to say, if the speakers will happily apply a corrupted firmware update they’re doing something horribly wrong.

[capableweb]

From the customer support message the article author received:

> to dampen their sound more than it should

Wouldn't this mean that the update should have dampen the sound (so there was an update to the audio), but something went wrong so it dampened it too much?

[jespertt]

This is where it gets a bit more technical; our support team member mistaked the speaker for SOUNDBOKS GO (our other version), where we have pushed out an audio update. In that audio update, there is implemented a tweeter protection mechanism, that limits the volume increase on the tweeter when it gets too hot. That can in some cases limit the dB a tiny bit (we're talking something that's not hearable), but in some cases there is a calibration error on the base temperature of the tweeter, making it think it is way hotter than it is - which can make it dampen too much. That is a bug, and we're working on fixing that - but again, that is on the SOUNDBOKS GO, and has nothing to do with the SOUNDBOKS Gen 3 that the author has.

[dpratt]

This does not pass the smell test, and your response borders on user-blaming. If this was only one person experiencing the problem, it wouldn’t be an inappropriate response, but if you have wide swaths of your user base describing the same problem, it’s inappropriate of you to hand wave it away by essentially implying that the user has somehow incorrectly applied the update.

[brk]

What specific functionality was this mandatory firmware update meant to address? I do not see that in the article, or your response.

A mandatory update implies a critical fix, it would be helpful to understand what warranted this update in the first place, and how that might relate to SQ, SPL, etc.

[jespertt]

A while ago, we realised we are seeing some failed tweeters in Gen3. The issue occurs when a. playing with the battery and the power on the battery is too low, or b. playing with only the charger on high volume. In those cases, there is a possibility that for a couple of seconds, a high-pitched sound comes out of the speaker and the speaker will shut down afterwards, resulting in damaging the tweeter. For this very issue: We have changed the failure mode in a way that it will not damage the tweeter during that shut down. We also made a slight change in the signal processing for the tweeter which further protect the driver from these sudden peaks.