-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
Audio that can't be paused due to lack of controls #1104
Comments
Might be related to #1053. |
Hi @DC7IA which phone do you have? Maybe the android system is trying to claim resources that are currently not used (e.g. playback stopped) and thus it destroys the playback service. I'll try to investigate this some more. Thank you for the report. |
Pixel 3a running CalyxOS. |
@DC7IA There are fixes related to podcast control visibility in the latest release can you double check if this issue still exists? |
I think is fixed, but it might take a few hours to notice if it still persists. I will re-open if the issue is still there. Thanks. :) |
Player controls still disappear when pausing / unpausing occassionally. Position in the podcast is not saved, so I have to start from the beginning and seek my last position. |
Hello.
Having another app in foreground makes the audio controls disappear while audio continues.
When switching back to Nextcloud News there is no way to stop the audio, or restart it if it stopped by tapping the audio controls in the notfication area. This only happens from time to time.
Also, sometimes the audio controls seemingly disappear for no reason when looking at other posts of the feeds. This means that there is no way to stop audio other than force-closing the app or rebooting the device.
When I play another audio file I then have two files playing simultaneously. Pausing that pauses both. Resuming resumes both. The only way to continue with a single audio file seems to be rebooting the device or waiting for one on them to end.
Version: 0.9.9.75 from F-Droid (though the issue has existed for a while now)
The text was updated successfully, but these errors were encountered: