WiiM Home App v3.3.8 Update – Sep 30, 2025

Please review the app update release notes below. If you encounter any issues, feel free to reach out to us.

* The iOS app is available on the App Store, while the Android app is currently under review by Google Play.

What’s New:

1. FAQ Access: Quickly access help articles on key features such as EQ, RoomFit™, and Subwoofer setup from their feature pages.

Bug Fixes:

1. Room Correction:
- Refined the tuning algorithm to deliver results based on the full frequency range.
- [Android] Improved layout compatibility for foldable phones.
3. [iOS] Preset: Fixed an occasional crash issue when using Presets.
4. [iOS] Mac App with Apple Silicon (M-Series): Fixed an issue where the app incorrectly displayed a “No Wi-Fi” message when connected via Ethernet.
5. General Performance: Stability improvements and behind-the-scenes optimizations.

 

[hgo58]

What is new with "FAQ Access"? It has always been there.

 

[Djinn206]

What is new with "FAQ Access"? It has always been there.

I think the question marks in the top right corner haven't been there before in the mentioned settings above (EQ, RoomFit, Subwoofer) where you can quickly jump to the related FAQ-article.

 

[WiiM Team]

What is new with "FAQ Access"? It has always been there.

We have improved the release notes writings; help articles for key features like EQ, RoomFit™, and Subwoofer setup can now be quickly accessed from their respective feature pages.

 

[Djinn206]

Original post hast just been edited for clarification.

 

[hgo58]

We have improved the release notes writings; help articles for key features like EQ, RoomFit™, and Subwoofer setup can now be quickly accessed from their respective feature pages.

Ok, good idea.

 

[Burnside]

Before @QuarryHunslet says it, nothing for me in this update

 

[Smartplug]

Before @QuarryHunslet says it, nothing for me in this update

If that was related to dlna he would be interested.

 

[QuarryHunslet]

Before @QuarryHunslet says it, nothing for me in this update

If that was related to dlna he would be interested.

It seems like you both know me so well now.

 

[stokholm]

Refined the tuning algorithm to deliver results based on the full frequency range.

What does that mean? Does it disregard the frequency range I select or how/where does it differ from the previous version?

 

[EddNog]

What does that mean? Does it disregard the frequency range I select or how/where does it differ from the previous version?

I would need to reconnect my WiiM to test this, but likely this is a fix for their original, erroneous method of applying, "Cut-only," mode where the entire target curve would simply slide down so that the highest portion was below the reference level, completely disregarding the actual frequency range for the correction. The right way to do it is so that only filter adjustment values below zero would be generated.

-Ed

 

[slartibartfast]

What does that mean? Does it disregard the frequency range I select or how/where does it differ from the previous version?

I think it means the target level is set based on the full frequency range but the corrections only cover the selected frequency range. Previously it was only considering the selected range and disregarding everything else meaning the target level was often inappropriate.

 

[Pecka]

I have trouble with auto-sensing of line in now, don't know if it is because of the new app.

 

[lempogi]

I think it means the target level is set based on the full frequency range but the corrections only cover the selected frequency range. Previously it was only considering the selected range and disregarding everything else meaning the target level was often inappropriate.

Looks like this is the fix that we are waiting for right? I'll re-measure my unit tonight if time permits and will post the result here.

 

[lempogi]

I would need to reconnect my WiiM to test this, but likely this is a fix for their original, erroneous method of applying, "Cut-only," mode where the entire target curve would simply slide down so that the highest portion was below the reference level, completely disregarding the actual frequency range for the correction. The right way to do it is so that only filter adjustment values below zero would be generated.

-Ed

I think that fix is the problem found out by @slartibartfast:

S

Post in thread 'Room Mode + Speaker Anechoic Measurement Correction'

Aug 27, 2025

That looks very good to me, especially for a first attempt - really great work!

The only minor issue that stands out to me is the dip just under 100Hz in the left channel, but I don't see any obvious reasons for it from the picture. Could its woofer center be around 80-90cm from any walls, floor, or ceiling?

Second question, how did you come to the 8ms delay for the mains?

And most importantly - how do you like the sound after correction?

What stands out to me is that the yellow target level is not the same for both channels. The target for the left channel is around 3dB...

• slartibartfast

• 

 

[slartibartfast]

Has anyone received the Android version yet?

 

[Erebus]

Has anyone received the Android version yet?

Not for me yet in Australia. Still on 3.3.7

 

[dalesman]

Nothing yet in the UK.

 

[Lorenzo6685]

Nothing yet in Belgium too, still on 3.3.7 on my Xiaomi phone and tablet.

 

[bl1nkmast3r]

None yet in SE Asia