I wish Spotify on Android Auto would take this feedback.
Seriously, a rotary knob can switch focus to the next/previous UI control, so that additional push of tactile button on said rotary knob will activate the control, but they can't simply detect the rotation as 'next/previous', with the push button as 'pause/play' toggle?
Instead I have to rotate the nob and visually track the thin active element outline each time I enter or swap to the app just to get a single tactile 'forward' control. Or, I give up, and continue the process of memorizing the button location on the screen and building muscle memory through repetition to correctly press the same spot on the screen each time without looking at it. Then hope I never need to be in a different car or that nobody adjusts my seat's X/Y/Z axis to screw up that muscle memory.
I suspect it's Spotify's issue, and not Android Auto itself, but most of the Android Auto apps work that way and I don't know where the fault originates. But regardless of who can fix it, it's horrible to allow UX to be designed ignorantly when it is placed to have potential life/death impact.