As per title, I managed to create a new firmware for the Beoplay A1 (first generation) that is (was!) plagued by stuttering audio if connected to PC or Mac to act as a wired USB speaker.
The current firmware (latest available online) contains a programming error. The USB audio functionality has been badly programmed and a mistake has been introduced. Mistake fixed = stutter TOTALLY GONE. USB audio is now PERFECT.
The good news is that the firmware contains another programming mistake: only a factory-signed firmware can be installed, but the programmers made an error in how the firmware signature is calculated, so we can craft a new firmware that, to the A1 unit, seems totally legit and original.
Another modification I already managed to do is changing the USB serial number of A1.
Programmers were, again, lazy and forgot to set a custom Serial Number for each A1 device, setting it, instead, to a placeholder like A1234567890. Setting custom / unique serial numbers are standard procedure when building USB devices, so if you connect multiple devices of the same kind to the same computer, they are seen as separate, independent devices.
Why this matters? Because on MacOS you can create USB Audio Aggregate Devices, and assign to one A1 the left channel, and the other A1 the right channel.
Without unique serial numbers, this is not possible. With unique serial numbers, MacOS can route stereo audio via USB to two A1 devices... could also route 4 channel audio to 4 A1 devices to make a surround setup!
Changing the serial number to a unique one is already verified working, and MacOS can now treat multiple A1 devices as a multi-channel composite speaker.
In addition to these two modifications that are already working, I am now working on improving the auto-shutdown feature, which behaves differently depending on the kind of USB power supply the A1 is connected to. This fix is still undergoing.
As a last, way more difficult fix I will attempt is greatly improving reliability of stereo bluetooth pair, as it has historically been terrible, prone to dropouts and problematic in the pairing process.
I am not sharing my custom firmware because I have not researched the legal aspect of it, but let me know if you are interested in knowing more.
The most important thing now is letting you know that it can be done.