Queue sometimes lost when switching bluetooth devices

Issue description:

(While playing music)

  1. Disconnect from one bluetooth output
  2. Connect to another bluetooth output

Expected result: music should be paused and present ready to resume the queue

Actual result (sometimes): queue/now playing/notification player disappears. Usually it will pop back up again and I can resume where I was. Sometimes this doesn’t happen.

In the log I uploaded (I am so sorry it is so massive. I kept it running to try and capture this. It will be at the end), the above happened. I tried to resume from the notification area (the only thing that was displayed was the song and the play button, no progress bar or forward/back buttons.) When I clicked the play button, the notification/media player activity disappeared and was replaced with something that just said Symfonium I believe. I opened the app to try and resume, and the now playing was not present, and did not load. In this instance, when I swiped it away from the recent activity and reopened, the queue/now playing loaded and I was able to resume correctly.

This is using the latest stable version. This did not used to happen, but I can’t tell you which version it started, I feel like it was in the last few versions but don’t take my word as fact on that.

In general it feels like Symfonium is very quick to unload from memory when paused compared to other players, which can be seen when the notification area player changes. I guess this is what is happening but the queue is getting lost.

Logs:

Upload description: tobyburton96

Additional information:

 

 

Reproduction steps:

 

 

Media provider:

Local device

Screenshots:

     

See https://dontkillmyapp.com/ and all battery optimisation settings.

I have no control over the app being killed when not playing.

All battery optimisation settings are off. I realise you can’t prevent that. But the app losing the queue is a new issue

The issue I’m reporting is about the queue disappearing and not always coming back. Not the app being killed