Uploaded another log today, unfortunately it only contains the resume event from this morning and not the point where the playback was stopped yesterday.
At 2025-08-21 12:26, playback resumes with “Kaddisfly/Horses Galloping on Sailboats/06 - The Painter.flac”. Playback yesterday ended about 60-70 tracks further down the playlist.
Here’s a new one. It spans from the 10th to the 15th. I did trim it significantly by removing lines containing Verbose/Subsonic: Insert andVerbose/QueryBuilder: Query: SELECT songs._id. I will provide the full file if needed.
At 2025-09-15 11:59:10, the playlist was resumed. It played Diamante/Coming in Hot/13 - War Cry.flac. That track was last played 2025-09-10 13:16:02. It was not paused or skipped to my knowledge, so it probably shouldn’t have had a resume point saved?
It should have resumed with Lydia/Illuminate/11 - Now the One You Once Loved Is Leaving.flac or thereabouts, which is where that playlist was last stopped at 2025-09-12 13:35:09.
I do have “Min play percentage before marking as played” on the max 99%, and “Min play time before saving resume point) on 0. If I understand correctly, that means that as long as the track isn’t stopped during the last 1% (which in this tracks’ case is 4 seconds), the resume point will be saved and that will be where it begins on the next resume. Statistically, I wouldn’t expect that to occur more than 1 in 100 times, but it seems more frequently that a playlist resumes elsewhere.
Do you mean that it’s a bug in Navidrome? A feature it doesn’t support? Or did the server just not respond on this particular occasion?
In any case, how can I completely remove the server from the equation? I want it to work fully offline for all playback purposes. I don’t want it streaming media from the server, I don’t want it scrobbling every song it plays, etc. The only reason I have the server configured in the app at all is for manually syncing of playlist tracks to the device cache (or semi-automatic in this case, by the playlist auto-caching rules). The app is advertised as offline-first, that’s what I want.
I’ve already listed the many reasons media queues won’t work for this scenario.
Uploaded another example. Playback stopped at 2025-09-16 15:26:23.262 while playing The Stowaways/Monroe/01 - Monroe.flac. It was next resumed at 2025-09-17 12:13:29.938 and it started playing Lucy Spraggan/Today Was a Good Day/12 - The Waiting Room.flac, which is about 110 tracks behind. If this is the same cause, how do I fix it?
The playlist was stopped at 2025-09-17 15:35:23.091 while playing Mae/(A)fternoon/07 - Communication.flac. When it was resumed at 2025-09-18 11:09:41.522, it started playing April Art/Pokerface [Deluxe]/06 - Warrior.flac, 67 tracks behind.
I don’t know why this is happening every day now, but only on this one particular playlist.
Stopped at 2025-09-18 16:19:52.137 while playing Illumishade/Eclyptic: Wake of Shadows/07 - Rise [album ver.].flac. Resumed at 2025-09-19 12:43:06.748 and it went back again to the song it resumed from erroneously yesterday, April Art/Pokerface [Deluxe]/06 - Warrior.flac.
This has only been happening on playlist ID #2 recently. The playlist with ID #1 has been stopping and resuming at the correct position.
Playback stopped on 2025-11-03 14:47:23 at or around track playlistPosition=1408, October Fall/A Season in Hell/09 - Keep It Comin.
2025-11-03 14:47:23.445 Verbose/QueryBuilder: Query: UPDATE playlists SET resume_file = ? WHERE playlists._id=2 (‘October Fall/A Season in Hell/09 - Keep It Comin’.flac’) [0 in 0.51ms (RAW/true)]
That looks like the resume point is properly set?
Resumed at 2025-11-04 11:42:03playlistPosition=1030 with track playlistPosition=1030, Lydia/Devil/01 - The Exit.