timusus
Queue resets when clicking the play button on the widget
Shuttle version:
v2.0.10
Device, OS:
Nokia 6.1, Android 9 (stock)
Description of bug:
I have a shuttle 2x4 widget on my homescreen which I use to quickly start playing the queue. But lately I've noticed that sometimes clicking on the play button resets the queue in a wierd manner. It always starts playing a specific song (in this case 24k Magic by Bruno Mars) and turns shuffle on.
Steps to reproduce:
- Add the widget on home screen
- Select a queue to play
- Pause and play music from the widget
Expected outcome: The running queue should continue playing wherever it was paused or atleast on the same song.
Observations/Actual Result:
It only happens sometimes and not necessarily if the app was closed long time ago or recently. I earlier thought since the app hasn't been used in a while its been unloaded from the memory and its not able to resume back but that's not the case. Sometimes its resets just after pausing and playing again.
+1 Ditto
This happens to me as well. The queue is erased and the app starts playing the first alphabetic song. It sometimes happens after a while and it sometimes happens immediately after pausing and playing again, but only when the app is in the background (i.e. with the widget or with a Bluetooth play/pause button).
So I'm using a Nokia device and apparently its one of the worst brands in terms of killing background apps. I was looking into some other problem and its solution was to Force stop an app "Power saver". Ever since I did that, I'm not getting queue resets either. It seems that the app kills a service or something that Shuttle needs to resume the queue.
I found this information on dontkillmyapp.com. If you have a device listed in their list, you might want to try their solution.
I'll leave it upto the authors if they want to close the issue or look into it further.
I think the bug here is that even if the app is killed, by the system or by the user, the app should retain the queue, the currently-playing song, and the playback position in that song, such that when the user either re-opens the app, or pushes play in a widget, the app will continue playback where it left off. It seems like this works just fine if the user opens the app itself after it is killed, but if the user pushes play on the widget after the app is killed but before opening the app proper, the queue information is lost.
