-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Stops playing #66
Comments
I haven't been able to duplicate this, can you tell me if it happens only when you press next on your bluetooth device or on the notification/in the app's Now Playing screen as well? Also, what subsonic server are you using and could you check the logs there to see if there are any errors reported from the time period where this happened? |
When I press next on the bluetooth device (ie steering wheel of car) it just displays the song name on the car's HUD. It just forgets to play after skipping a few times. It seems if I press play on the lockscreen of the phone again it works. I will try to find a way to replicate this 100%! I was using Gelli as a player and Jellyfin before and this didn't happen so can rule out the car and or phone in this regards perhaps. |
How do I find logs? I've discovered Subtracks stops playing after two or three songs on Android without any bluetooth devices. I've set the battery to unrestricted but the issue remains that (on my end), the player will not play more than 2 songs consecutively. :( |
There are no logs currently, though I'm thinking about adding some now. I have experienced this now very rarely on my phone, but not on an emulator yet where I can see debug logs. Going to try this on a couple other phones soon though to see if I can get a better repro. |
Just noticed when in the car and connected to BlueTooth.
If I press skip track once, Subtracks will play next song.
However if press more than once, a few times, I find that Subtracks will skip forward but will not actually play the track.
While driving, I have to turn the screen on and press play via the notification.
The text was updated successfully, but these errors were encountered: