You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since switching to an Samsung Galaxy S25 Ultra I habe the problem, that everytime I lock the car I am using the app, it does not only pause playback, but closes the player.
The annoying part is that to start playing again the phone needs to be onlocked and the play button needs to be pushed on screen, what is a mess while driving.
Is there any way to stop this behaviour and just keep the player open. Ideally also have it reopened with the last audiobook when the audiobookshelf app is started.
Steps to Reproduce the Issue
Play Audiobook connected to car (BMW) by bluetooth
Lock the car via key (Bluetooth disconnecting)
The app stays active but the player inside the app is closed.
What was Expected?
The app pauses playback, but the player stays active.
Phone Model
Samsung Galaxy S25 Ultra
Phone OS
Android 15, One UI 7.0
Audiobookshelf App Version
Android App - 0.9.79
Installation Source
Google Play Store
Additional Notes
No response
The text was updated successfully, but these errors were encountered:
What was the Problem?
Since switching to an Samsung Galaxy S25 Ultra I habe the problem, that everytime I lock the car I am using the app, it does not only pause playback, but closes the player.
The annoying part is that to start playing again the phone needs to be onlocked and the play button needs to be pushed on screen, what is a mess while driving.
Is there any way to stop this behaviour and just keep the player open. Ideally also have it reopened with the last audiobook when the audiobookshelf app is started.
Steps to Reproduce the Issue
What was Expected?
The app pauses playback, but the player stays active.
Phone Model
Samsung Galaxy S25 Ultra
Phone OS
Android 15, One UI 7.0
Audiobookshelf App Version
Android App - 0.9.79
Installation Source
Google Play Store
Additional Notes
No response
The text was updated successfully, but these errors were encountered: