Moving the discussion here from this reddit post:
Elan asked me to share the logs when this happened; here is a link to my logs:
The latest log has this, which means there’s nothing to resume.
Oct 23, 2022 11:55:03.458 [Javascript] INFO - Player: Initializing with state {}
Before that:
Oct 23, 2022 10:52:51.997 [Javascript] INFO - Audio Route: Switched over to player SHIELD (volume: undefined).
...
Oct 23, 2022 11:37:13.058 [Javascript] INFO - Player: Sending state changed [A] Plain White T’s - Airplane (125000/138475) in state paused with artwork true.
Oct 23, 2022 11:37:13.060 [Javascript] DEBUG - [PlayerModule] Got state event paused (local: false).
So it appears you were casting and then walked away or something like. If the player is remote, Plexamp can’t continue the queue unless you bring it back to the phone before stopping playback (by selecting “This Device” in the case menu).
Is this behavior something that could be addressed in the future? I often just turn off my TV or stereo and then get into the car. Or vice versa. It would be a pain to manually change the connection on the phone all the time. (needing reading glasses to read it makes it an extra pain).
We’ll think about how we could improve, but the app doesn’t really know you’ve done that per se, vs just walking out the door and wanting it to stay playing.
Thanks for considering this. I’ll admit I don’t fully know how casting works, but I would think that if the playback status and queue could remain in the phone memory somehow, it wouldn’t matter if you turn off the stereo? It’s been a while since I’ve used Google play music, but I’m wondering if it had similar issues (I didn’t have Android Auto at the time, so not sure if it worked that way).
Anyway, thanks for all your hard work so far. Issues aside, Plexamp has been a game changer for me!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
