Momentary pause in currently playing track after skipping either forward or backwards.
So, I decide to skip to the next track, there is a very short pause (1/10th sec maybe) before the currently playing track continues momentarily for a similar duration to the pause before the track changes. If I allow the track change to occur naturally, the issue does not happen.
The same can be witnessed when playing files locally.
Logs:
Upload description: #3 4ipqiaxm
Additional information:
Playing FLAC files on stock Pixel 6 using the AAC codec. The same files do not exhibit the same behaviour in alternative audio players.
I have tried a random majority of my library and each track has this behaviour regardless of whether an album is selected to be played or just playing random tracks from the album collection I have.
Reproduction steps:
Skip track either forwards or backwards and the issue is present.
Thank you for the feedback. I’m also seeing this on a Nokia 8 mobile (Android 9) and my Lenovo Tab P12 tablet (Android 14). Does this mean all three devices have broken device implementation of the EQ libraries?
Possibly, I know many have this, the EQ does not flush when it should in some cases.
The solution would be to fully destroy the EQ, but on some device this also generate unwanted sound and possibly at full volume if they have any negative pre amp, so a way worse result.
It is interesting to hear that when the track changes without intervention the glitch is not heard, the glitch is also not present when skipping forward by scrubbing to the end of the track with the seek bar.
Would playing via a buffer improve the situation? or maybe utilising a cross fade between tracks?
Is this primarily an issue with third party code you cannot control as I don’t recall hearing the glitch with alternative players. If the issue is from the code of other developers, who should I take this up with to get this resolved?
This is an OS issue with OS libraries, when disabling the EQ in some cases it still keeps a buffer. Then when enabled again it plays that buffer that it should not.
There’s no one to contact about this.
I’ll try again to workaround by fully unloading and restart it, hoping to find a workaround for the other bug related to that.