Hacker News new | ask | show | jobs
by granos 1428 days ago
Crazy issues like that definitely do happen. But, this speaker output power issue being due to a file transfer error doesn't feel right. Do the perform any kind of integrity checking on the fw before installing it? Even an md5sum on the package seems like it would almost certainly have caught this. Either this wasn't caused by a file transfer problem, or their fw update process has some serious design issues.
1 comments
HelloNurse 1427 days ago
Even easier than file integrity checks: testing the loudspeakers with various combinations of output level, musical material and battery states. They would have noticed.
link
jespertt 1427 days ago
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 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!

link