ARCHIVED FORUM -- March 2012 to February 2022READ ONLY FORUM
This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022
Hi all,
I have noticed a strange behaviour with my Beoplay M3 recently since it was moved to the kitchen.. I have created a listening mode (EQ) to add more treble, saved it and selected in the B&O app, but when the speaker’s unplugged for a while and subsequently plugged back, in the EQ appears to have been reset back to ‘optimal’ (the default) but the app still shows the saved listening mode as applied. It’s definitely not on the saved profile as I can select Optimal with no difference to the sound, then select my saved profile and the treble is restored.
I would be grateful if another M3 owner could test this same scenario to see if theirs behaves the same before I contact B&O support. I’m running firmware version 1.11.45906 on the M3.
Update - just discovered that my new M5 exhibits this issue too :(
Many thanks. Rob.
This has happened to me (exact same behaviour) with listening modes on my H9 3rd Gen.
Please feedback via the in-app feature after the power cycle, right when the custom profile is selected but it's actually using the optimal preset, and that will allow the B&O team to track what's happening in the app to they can fix it.
Of course, the more people report it, the better it is :)
Thanks for the reply. I’ve just submitted the support request reporting the bug.
Anyone with a Beoplay M3 able to test this out to see if it’s a widespread problem?
Many thanks.
matteventu: This has happened to me (exact same behaviour) with listening modes on my H9 3rd Gen. Please feedback via the in-app feature after the power cycle, right when the custom profile is selected but it's actually using the optimal preset, and that will allow the B&O team to track what's happening in the app to they can fix it. Of course, the more people report it, the better it is :)
Shamelessly bumping this up the forum to see if someone could possibly help me out here by seeing if their M3 also looses the "listening mode" setting after cutting the power too? Cheers! Rob.
In the meanwhile, I'm on the new firmware, and the EQ preset was remembered after updating. There is a reboot, though no power cycle.
I'll try it out later today and will report back.
Beolit 12 - Beolab 4 pc (dead now) - Beoplay H5 - Beolab 9 - BeoRemote One BT - Beoplay M3
crossbytje: In the meanwhile, I'm on the new firmware, and the EQ preset was remembered after updating. There is a reboot, though no power cycle. I'll try it out later today and will report back.
Thank you much appreciated. Yes I’m on the newest firmware too now (with Spotify) but it still has the issue. For me the app remembers the EQ mode but it’s not actually active on the speaker. Rob.
Silly question, have you tried to factory reset your M3?
Many times I’m afraid, through the app to trigger the factory reset. This morning I looked up how to do a manual reset, I removed the speaker from the app then held down the config button underneath the speaker for 5 seconds and set up again once completed. To test it I started the radio, set the sound to ‘clear’ ( high treble) then triggered a reboot. Once back on I played the same radio station again, went to listening mode where it still showed clear as active, clicked on optimal and no change to sound. I clicked on clear and the treble’s restored. Really weird as it remembers all other config but not this!
I just checked. The app shows the last used profile, but it's clearly not using it. You have to change it and select it back before it is actually used.
So there is indeed a bug in the software.
I wouldn't hope too much on the development team to correct this. I have a set of H5's which were remembering the sound profile as they should. Then suddenly, an update came and this function was broken. Ever since, there hasn't been any new update (I'm speaking of a couple of years now already). As the H5's are no longer sold, it's not their priority.
Unfortunately, there's no going back to the old firmware either, so I have to select the profile every time I use them. Simply going in standby is enough to forget :-(.
crossbytje: I just checked. The app shows the last used profile, but it's clearly not using it. You have to change it and select it back before it is actually used. So there is indeed a bug in the software. I wouldn't hope too much on the development team to correct this. I have a set of H5's which were remembering the sound profile as they should. Then suddenly, an update came and this function was broken. Ever since, there hasn't been any new update (I'm speaking of a couple of years now already). As the H5's are no longer sold, it's not their priority. Unfortunately, there's no going back to the old firmware either, so I have to select the profile every time I use them. Simply going in standby is enough to forget :-(.
Thanks for checking. I suppose that it's good that I am not alone - I suspected it was a software issue.. Please could you report the bug via the app as well, the more people that report it the better. Although now discontinued, there will be many still under warranty.
It would be great if others with the M3 could test theirs too and report this issue if they also have the same problem.
-> I sent them feedback on this bug.
crossbytje: -> I sent them feedback on this bug.
I’ve discovered my M5 behaves exactly the same and has the same issue!!