Stop background processes after bluetooth device is disconnected

Feature requests
1

Feature description:

It would be nice to have an option that the app will close itself after BT device is disconnected.

Problem solved:

I’m experiencing a problem where I always need to expand my phone menu, go to “Active Apps” and press Symfonium to Stop the app. It’s exhausting to do these four or five more finger swipes after each music listening session. I get it this stays here to be able to easily play music, but it would be great to be able to choose if the app should close itself after listening.

However, doing so doesn’t destroy the BT Auto play function, it always works perfectly. My routine is:
I get in my car > Bluetooth connects to my phone > Symfonium automatically resumes my queue > I get off my car > Bluetooth disconnects > Symfonium pauses > I manually expand phone menu, go to Active Apps and press Stop.

When routine repeats itself, Symfonium resumes the queue perfectly fine after my phone connects to bluetooth device.

One not-so-working ‘workaround’ is to automate it with Tasker and execute MEDIA: STOP, but it closes my queue completely. Pressing Stop in ‘Active Apps’ through Android’s UI no only stops Symfonium background processes, but the queue is untouched too. I want to clarify that I’m not talking about the Force Stop option after you go to android settings > apps, but the option that is shown after you swipe your finger to the up shown on Stock android since A13.

Brought benefits:

I think having such feature could bring less issues complaining about battery drain, which are a ton of on the forum, I checked almost every one of them. Most people are listening to music on their smartphone while are connected to headphones or other device. And I think, more people would benefit from having such feature since they open the app to start listening to music than pressing play on an notification menu.

Other application solutions:

 
In YouTube Music, when you pause music, the app immediately changes its state and is not shown as an active app (is not shown in Developer options > Running services) and it’s still shown on notifications menu, with the option to resume the playback.
 

Additional description and context:

 
I’m talking about this menu:

 

Screenshots / Mockup:

    

2

Closing app is counter productive on Android.

There’s no known battery issues. The services stop itself after some times as expected and does not use any battery.

3

The app is shown as actively running in the background and eating up 200MB of RAM in the Running services option in dev tools. And I can confirm it does not stop itself for me and drains the battery.

4

Then open an issue and show that ?

The service stop being foreground after some delays depending on Android version. And then is killed of necessary by the OS.

And when paused, there’s no battery usage..