Speaker output is tuned to input power and is probably stored in a file. Somebody grabbed a wrong file for the ‘speaker calibration curve’ while building the new update patch. Shouldn’t happen/doesn’t happen - we have seen internet infrastructure going down due to bad updates on routers - this is not entirely implausible.
That’s entirely possible, but then they shouldn’t explain their fix as: “You might have done something wrong during the upgrade process, please try again and if it starts downloading it should be fixed after.”
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.
The suggestion to re-upgrade suggests that you have silently replaced the problematic firmware update with a different package.
Don't you see how not providing changelogs and explanation looks suspect? Can't you admit a mistake, if it's only a forgivable case of not testing far-fetched usage scenarios properly?
I do work with audio stuff in auto industry.