Android Auto’s music controls are still skipping two songs with one press

Steering-wheel buttons are supposed to make controlling music easier while driving, but some Android Auto users are finding that a single press can send their playlists two songs forward or backward. It’s a frustrating problem that has been around for months, and fresh complaints suggest it isn’t going away anytime soon.

The issue first gained attention earlier this year, when owners of the 2026 Toyota RAV4 reported that pressing the next or previous button on their steering wheels registered two commands instead of one. The behavior affected multiple music apps, including Spotify and YouTube Music, across wired and wireless connections.

Eight months later, the complaints are still coming, and Toyota owners aren’t alone.

In an October 25 report, a driver with a 2011 Acura TSX and Pioneer AVH-2550NEX stereo described the same double-skipping behavior while using Tidal on a Samsung Galaxy S26 Plus. Interestingly, the problem disappeared when switching to a Galaxy S23 Plus using the same stereo and app versions. Reinstalling apps, clearing caches, and resetting Bluetooth connections made no difference.

Another user joined the discussion this week, reporting identical behavior with a Galaxy S23 Plus and a CONVOX EVO-810 head unit. Both Spotify and YouTube Music were affected, while the head unit’s native music controls worked normally.

A fresh complaint from another 2026 RAV4 owner shows the problem persisting on Android Auto 18.0. In this case, pressing the steering-wheel controls twice effectively caused YouTube Music to seek 10 seconds instead of changing tracks. Ordinary Bluetooth playback and Android Auto’s on-screen controls worked correctly.

Google hasn’t ignored the complaints entirely. An Android Auto community specialist contacted the Acura owner by email on October 27, with another specialist confirming this week that the issue had been forwarded to the team.

Thanks for reporting this issue. We’ve forwarded your issue to the rest of the team.

Thanks,
The Android Auto team

Those responses suggest Google is looking into the complaints, although there’s no confirmed fix or explanation for what’s causing the behavior. It’s also unclear whether all affected setups share the same underlying problem.

We’ve reached out to Google for clarification and will update this article if we hear back.