-
-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playback is stopped when swiping away Auxio from recent apps #866
Comments
If this were to be "fixed" I think there should be an option to have this be the behavior (like what vlc does). I personally believe that if I swipe away an audio player, I eould expect the music to stop playing, signifying that the app is actually closed. I don't want to go into the settings just to force stop the app when I don't want it using battery in the background while it is closed. |
Intentional behavior from #257. This is what the android system expects from Auxio and I so it's not really in the bounds of a setting (This is the same reason audio focus is non-configurable) #844 is probably also going to make some auto-timeout system where Auxio will naturally exit it's foreground state after some level of time, so @ego-lay-atman-bay's concern isn't going to be relevant soon I hope. |
Is this really the intended behavior? According to #257 (comment), if music is playing, then playback will not be stopped.
However, that is exactly what is happening on my device (playback is stopped even if playing). |
Can you send a screen recording @TL-P? The code explicitly checks for ongoing playback before it stops the current session, so I frankly have no idea what happens. |
screen-20240912-211125.mp4Recorded without audio, it stops as soon as Auxio is swiped away. |
Describe the Bug/Crash
Describe the intended behavior
Playback should continue (which still worked for me in v3.5.2)
What android version do you use?
Android 13
What device model do you use?
Xiaomi Mi 9T (PixelOS)
Provide a sample file
N/A
Bug report
N/A
Duplicates
The text was updated successfully, but these errors were encountered: