A Tasker event fires for each of my Bluetooth devices when they are connected. On connection it runs MEDIA_START, MEDIA_TYPE:playlist, ID:8L or 9L depending on device, RESUME:true. On bluetooth disconnection it runs MEDIA_COMMAND, COMMAND:stop. “Ignore remote sop command” is disabled. I haven’t seen any difference when it’s enabled. I also have tried COMMAND:pause, but I don’t like how it leaves a notification and keeps the “now playing” status in-app.
After further reviewing the logs, here’s what I found:
I can’t identify any log line that states simply “this song is beginning playback now”. I presume there is one, it just doesn’t include the track title on that same line. The closest analog I found is lines containing “PlaybackController: closePreparedForRendering”. This shows me the following playback sequence for the specific playlist in question (which is in my car during my short commute to/from work):
2025-04-07 14:45:15.562 file='Gore/A Bud That Never Blooms/03 - Babylon.flac'
2025-04-07 15:46:15.619 file='Gore/A Bud That Never Blooms/04 - Angels Like You.flac'
2025-04-07 15:47:29.058 file='Gore/A Bud That Never Blooms/05 - Heaven Is Above Me.flac'
Playback stops here, and resumes the next morning:
2025-04-08 11:45:19.296 file='Gore/A Bud That Never Blooms/05 - Heaven Is Above Me.flac'
2025-04-08 11:49:37.306 file='Falling in Reverse/Just Like You/01 - Chemical Prisoner.flac'
2025-04-08 11:49:50.741 file='Falling in Reverse/Just Like You/02 - God, If You Are Above....flac'
Stops here, and resumes later that day:
2025-04-08 16:01:05.027 file='Falling in Reverse/Just Like You/02 - God, If You Are Above....flac', title='God, If You Are Above...'
Stops here, and the following morning it resumes at:
2025-04-09 11:16:10.425 file='Falling in Reverse/Fashionably Late/15 - Rolling Stone [Remix (Shy Kidx)].flac'
This song is about 20 tracks earlier in the playlist. Now that I’m seeing it layed out like this, two things I remember that might be relevant. First, “15 - Rolling Stone [Remix (Shy Kidx)].flac” was skipped before the track ended (which happened before I enabled debug logging, probably some time last week). And second, the previous playback session starting at 2025-04-08 16:01:05.027 was paused for most of the drive while I was on a phone call. So that might explain why its position wasn’t saved, but shouldn’t explain why it would resume the next time 20 tracks behind.
Please let me know if there is anything else I can do to assist in debugging.