[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.''

[mgsouth]

Q: Did the customer get exactly the same version with the re-update? Or was a patch or revert pushed in the meantime?

[notwhereyouare]

those are the weirdest bugs, everything seems to work as expected until it doesn't.

Glad a customer was able to try reupdating and it fixed their issue. I wish the team best of luck tracking down how the upgrade flow got busted