WiiM Amp Pro Firmware v5.2.726630 Update - Aug 18, 2025

Please review the WiiM Amp Pro update release notes below. If you encounter any issues, feel free to reach out to us. This firmware update is being rolled out in stages, with devices updating sequentially over the next few days.

5.2.726630 (In Progress)​

Release date:

8 / 18 / 2025

What's New:

1. Room Correction & EQ Integration: Room Correction and EQ now work together to provide an optimized listening experience. Learn More
2. Stabilized Wi-Fi Connection: Enhanced connection reliability, especially for mesh network environments.
3. Amazon Music: Bitrate information is now displayed when streaming Amazon Music Prime.
4. Sub Pro Intergartion: Improved pairing experience and overall functionality when using the Sub Pro.
5. YouTube Music: Native, seamless streaming support. (requires the upcoming app version 3.3.1).
6. Soundtrack SDK Upgrade: Under-the-hood improvements for a smoother, more consistent listening experience.

Bug Fixes:

1. Alarm Fixes:
   • Resolved an issue where weekly alarms occasionally failed to trigger.
   • Fixed a bug where only the default tone played for Pandora alarm.
2. Dolby Audio Fixes:
   • Fixed no-sound issues when playing Dolby audio in multiroom setups.
   • Corrected volume balance behavior for Dolby audio.
   • Corrected low volume when playing Dolby Digital content.
3. USB Output Fixes:
   • Resolved no-sound issues after reconnecting a USB DAC device when using Google Cast, TIDAL Connect, Spotify Connect, or Qobuz Connect.
   • Fixed audio stuttering when playing at 44.1kHz or 48kHz sample rates.
4. Playing Status: Corrected the playback status indicator when no music is playing.
5. Qobuz: Now displays the correct artist name in the app during playback.
6. Bluetooth Output: Fixed a no-audio issue after switching outputs.
7. NAS & USB Playback: Playback now correctly restarts from the beginning after the last track finishes.
8. Playback Speed: Resolved rare cases where songs played at accelerated speed.

 

[flxy]

I believe this bug does not affect _all_ Bluetooth connections, as otherwise there would have been an uproar from users.
It might happen under certain circumstances, non-matching version protocols..etc.

I went on holiday and if this bug isn't confirmed by the developers by the time I am back, I will send them the logs and will try upgrading OpenElec on my Raspberry Pi to a newer version. Even if it helps, though, the developers need to fix this issue, as it is a regression.