Leech FI

Half year later this problem still persists and is unaddressed by Klipsch. Did you guys trade your Fives away or still waiting for a fix?

I have the same version numbers except the app version ”subnumber” which I think is the build number. I have iOS client and perhaps you have android? App version: 1.11.0 (107) FW version: 1.6.9 HW version: 02.00.01 I verify that the EQ presets are not stored to the speakers (despite the app is indicating so) and would like to emphasize the Anttielei’s message; I also find plausible that the announced succesful saving verification is a false positive based on mistake of the observer. Without verification I continue to believe that every single owner of Klipsch Fives face the same issue. We know that the app is lying about the selected preset. This is a problem that should be addressed by Klipsch.

Thanks for this observation. I tested my fives and confirm this problem (using Klipsch Connect iOS app). The EQ settings are not stored on speakers and prior every use I have to use the app to re-select my custom EQ to cancel the boomy bass away. When the app says "Getting latest info" it skips the EQ settings. It will show the last user selected setting but in reality it has defaulted to "Flat" -setting (which in fact is not very flat at all). So the app gives you a false indicator. I think Klipsch made a good job featurewise with the new update, but a little more time spent on quality control would have paid off. I expect this bug to be fixed in the near future.

Thanks for this observation. I tested my fives and confirm this problem (using Klipsch Connect iOS app). The EQ settings are not stored on speakers and prior every use I have to use the app to re-select my custom EQ to cancel the boomy bass away. When the app says "Getting latest info" it skips the EQ settings. It will show the last user selected setting but in reality it has defaulted to "Flat" -setting (which in fact is not very flat at all). So the app gives you a false indicator. I think Klipsch made a good job featurewise with the new update, but a little more time spent on quality control would have paid off. I expect this bug to be fixed in the near future.