EQ setting not being applied when contecting to Android Auto

Issue description:

When contecting via Bluetooth to AA, whilst the correct profile is being used, the EQ settings are not being applied. They do seem to work for a split second but are then not used. To make it work, I either turn off and on again Eq or do the same with the processing engine and then the settings work on AA.

Logs:

Upload description: Buzzdudde

Additional information:

it seemed to start about 3 weeks ago, only seems to affect AA. I’ve been trying to trouble shoot the problem, by reinstalling, restarting the phone, changing settings, recreating the EQ settings, but nothing fixes the problem.

Reproduction steps:

1. phone contebts to AA via Bluetooth

  1. Music starts to play.
  2. Volume is higher for a split second then reduces.
  3. Open up symfonium app, go to setting>playback>playback>eq DSP> turn off processing engine, then turn back on again. Can also to the same with the equaliser slide switch.
  4. Settings are applied , as music is noticeable enhanced.

Media provider:

Local device. Emby. Files are cached locally.

Screenshots:

Settings / Playback / Advanced / Restart player on device change.

Thanks, Option was already on, I have toggled off and on. Reconnecting to AA between toggles, but it has not effect.

The joy of AA and Samsung :slight_smile:

Did you get an AA or Samsung update 3 weeks ago ?

Yep. Looks like I did.

And to make matters worse, AA updated last night and the QUEUE button has gone again, and music is stopping, so I have bigger problems now. :zany_face:

Ive sorted out the AA update today. Just a Bluetooth connection problem, my phone was connecting via Ford sync and not the car. It’s back on the cars connection. So I’m back to the original EQ problem.

Unfortunately not much I can do, in the logs all is done properly. Why the OS internals stop acting and needs a second manual reset is not something I can do much about specially without the same phone to reproduce.

Ok thanks. I have tried another samsung, s22 and it works fine, so it maybe just me. Ill keep playing with settings and hopefully will fine what happened.

Not just you, but probably a Samsung bug as often. I guess the s22 is not on Android 16 and so not the same level of patches and so not with that bug.