Android auto mutes spotify's own songs and no one knows why
Your phone still hums the tune, your car stereo stays stubbornly silent. Since late April, a quiet purge has erased locally-stored tracks from Spotify playlists the instant Android Auto takes the wheel. The files sit untouched on the handset, yet the head unit behaves as if they never existed. Drivers first noticed it on Reddit, and every new reply confirms the same ghosted queue: ripped demos, Bandcamp downloads, white-label promos—anything not streamed straight from Spotify’s cloud—simply vanishes from the car interface.
The bug that only strikes at 60 mph
Reboot the phone, wipe the cache, re-pair the head unit: the checklist fails every time. Worse, album art is slipping too, leaving gray placeholders where cover art once loaded. Engineers on XDA have traced the hiccup to a metadata handshake inside the Android Media Browser Service; local files now return empty URIs when Android Auto requests a playlist snapshot. Translation: the car asks for a song path, Spotify answers with silence.
Neither Google nor Spotify will claim the mess. Spotify’s last Android Auto code change shipped in March; Google pushed a new Media API in April. Finger-pointing is pointless when both firms keep quiet. Meanwhile, the support forums read like a roadside pile-up: Pixel 9, Galaxy S26, OnePlus 13—same blank rows, same frustration.
This lands at a cruel moment. Android Auto 16.0 already broke steering-wheel seek buttons for some users, and Bluetooth dropouts on the latest Samsung flagships have turned commutes into glitch art. Stack those on top of the local-file blackout and the platform feels held together by firmware spaghetti.
Charlotte Gibson has spent nights dumping traffic logs between her Pixel and her VW Golf’s MIB3 unit. The pattern is unmistakable: the moment the head unit requests a playlist, Spotify’s local-file server returns HTTP 404. A streamed track follows, no problem; a track pulled from internal storage gets redacted like a state secret.
For now, the only workaround is clunky: queue the playlist on the phone before plugging in, then pray you never need to skip. It’s a hack that defeats the core promise of hands-free audio. Until someone patches the pipe, your bootleg live recordings and private mash-ups remain hostages in your pocket, audible everywhere except the one place you actually want to hear them: the driver’s seat.
The silence is spreading. One affected user counted 47 missing tracks in a 180-song road-trip list; another reverted to a 2019 Honda head unit just to keep his unreleased demos alive. The numbers are still small, but the anger is exponential. When music disappears at highway speed, even a minority feels like a convoy.
Google Discover loves a breaking defect, and this one ticks every box: sudden, unexplained, disruptive. Spotify built its empire on personalization; Android Auto sells freedom from the handset. Together they have engineered the perfect contradiction: your songs, your data plan, your car—just not at the same time.
The next update cycle is weeks away. If the fix doesn’t land before summer road-trip season, expect more drivers to rip USB sticks from drawers and resurrect 2009-era MP3 folders. Progress, reversed by a single broken API call. Sometimes the future arrives with a spinning buffer wheel—and no soundtrack.