Car Thing shows nothing playing

[TechGeek01]

Describe the bug
When playing music, after resuming from being paused for a while, sometimes the Car Thing does not recognize there is music playing. Restarting the server, as well as rebooting the Car Thing do not fix this issue. The fix seems to be to close and reopen Spotify.

To Reproduce
Steps to reproduce the behavior:

1. Play music
2. Pause music, and be idle for some time
3. Resume playback
4. Occasionally, when resuming playback, the Car Thing doesn't recognize the lack of idle state, and still shows idle.

Expected behavior
The Car Thing should detect the media playback, and behave accordingly

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 11 Pro for Workstations, 23H2, build 22631.4391
• GlanceThing version: v0.0.6

[BluDood]

Could you check the logs (%appdata%/glancething/glancething.log), and see if there are any errors about refreshing the Spotify token?
On another note, I have noticed that sometimes Spotify fails to send an idle status when nothing has been playing for a while, could be fixed by sending a request every minute or so to update it

[TechGeek01]

Sure thing! Relevant bit at the end of the logs is this bit

[19:53:18] INFO <GlanceThing>: Welcome!
[19:53:18] INFO <Storage>: Loaded storage file
[19:53:18] INFO <adb>: Using downloaded ADB from path: "C:\Users\[user]\AppData\Roaming\glancething\platform-tools\adb.exe"
[19:53:18] INFO <WebSocketServer>: Started on port 20111
[19:53:18] INFO <adb>: Found CarThing: [redacted]
[19:53:19] INFO <Client Webapp>: Downloading...
[19:53:21] INFO <Client Webapp>: Downloaded!
[19:53:21] INFO <adb>: Installing app...
[19:53:24] INFO <adb>: Installed app!
[19:53:30] INFO <Spotify>: Refreshing token...
[20:17:22] INFO <GlanceThing>: Welcome!
[20:17:22] INFO <Storage>: Loaded storage file
[20:17:22] INFO <adb>: Using downloaded ADB from path: "C:\Users\[user]\AppData\Roaming\glancething\platform-tools\adb.exe"
[20:17:22] INFO <WebSocketServer>: Started on port 6059
[20:17:23] INFO <adb>: Found CarThing: [redacted]
[20:17:39] ERROR <Spotify>: Failed to go to next track
[00:34:05] WARN <adb>: CarThing no longer found
[00:34:21] INFO <adb>: Found CarThing: 8557R285Q316

That last bit was when I restarted the Car Thing, but the last, and only error was the "failed to go to next track" bit.

[BluDood]

That's weird. I should probably print a more detailed error when one comes in, since it's pretty hard to diagnose the issue from here. How long approximately does it take for this to start happening?

[TechGeek01]

I've had it happen a few times. Maybe once every day or 2 or so. Usually after leaving it idle for a while.

I do have the screensaver enabled, but it never does anything, despite the idle detection working (and showing the "nothing playing" bit properly. Computer itself has a screensaver, but is basically always on, never goes into sleep mode. Not sure if that's related or not.

[BluDood]

I've had it happen a few times. Maybe once every day or 2 or so. Usually after leaving it idle for a while.

I do have the screensaver enabled, but it never does anything, despite the idle detection working (and showing the "nothing playing" bit properly. Computer itself has a screensaver, but is basically always on, never goes into sleep mode. Not sure if that's related or not.

Yeah, the screensaver is only automatically enabled when the desktop app is disconnected, can be manually enabled in the system menu. Screensaver on your computer shouldn't matter. I'll try to replicate the error myself, and at least implement some better error logs :)