Long Songs Restart at ~75% and then skip to next song

App version

Production

Issue description

When playing longer songs (10+ minutes) via Android Auto almost every song will restart at about 75% complete in the song, however once it reaches the full playtime of the song the next song plays.
Example:
Elder - Reflections of a Floating World (album)
Track 1 (11:14) plays starting at 0:00, around 9:15 (imprecise hard to pin down exact) the track jumps to 0:00, then around 2:00 Track 2 starts to play at 0:00.
The same thing happens on track 2 (11:13).
This also happens for many other albums (Tool - Fear Inoculum, Elder - Through Zero, Iotunn - Kinship, really any album with track lengths of 10m+)

I can scrub past the 75% mark and hear the end of the song (not usually viable from the Android Auto experience while driving though).

Device type

Phone

Media provider

Navidrome

Steps to reproduce

  1. Enqueue album with long songs on Android Auto
  2. Play
  3. Note song jumps back to 0:00 around 75%
  4. Note next track plays after final 25% of song runtime is played (0:00 → 25%)

Additional information

Navidrome 0.62.0
All files FLAC
Only happens in Android Auto same songs stream fine directly on phone (both using cellular-data only).

In Debug mode saw slightly different behavior than I see in non-debug.
For Tool Fear Inoculum first track after 8:20 track continued but no audio played (silence but did not scrub back to 0:00)
For Elder Reflections of a Floating World first track jumped back to 0:00 around 9:15 (didn’t spot exact time) but then never jumped to track 2 just kept playing track 1 again.

I searched existing issues first

on

I understand that logs are mandatory

on

Log upload name / description

tebriel

2026-06-23 10:30:59.018 Error MusicPlayer  DataSource: Error reading source (0/10/false), retrying [m74: h3a: stream was reset: PROTOCOL_ERROR]

As most duplicates on this, your proxy cut the connection in http/2. You can disable http/2 in settings or check your proxy settings to increase the values.

Thank you! Could you link me to a duplicate? I searched but I guess my search terms weren’t appropriate to find this error. Might help me next time I have an issue avoid filing if it already exists!

@toloriq

The more I think about this the more I I’m confused as to why http/2 is the culprit here. Why is http/2 only a problem when using android auto?