Hi all, having playback issues when playing music from the server on my android Pixel 4a. Playback often stops on its own between playlist tracks, when opening the app it will show playback paused. Occasionally (less frequently) this happens mid-song. Does not seem to be caused by notifications or screen going to sleep etc.
This did not happen with my previous android phone (Pixel 1). Saw several similar posts but none seemed to be the same issue.
Feels like a buffering / network connectivity issue, but I can’t make sense of the logs. Help appreciated!
(note logs will say server version 1.22.x, I’ve since updated - still happens)
Server Version#: 1.25.3.5409 - OpenSuse Leap 15.2 x64
Player Version#: 8.28.0.30077 (241173d0) - android 12
Today tried disabling our secondary AP (wired to main router), no change. Also made sure “background data” is enabled for the Plex app.
Earlier playback stopped mid-song, then the app crashed. And just now it again paused between tracks.
On these pauses, it will show the name of the next track on the “Now Playing” screen, but not actually do anything. The playback bar seems to show that the entire track is buffered (it’s light grey). Pressing play (or skip) resumes playback, but the playback bar will not update or be out of sync.
It finally seems to be working okay now - thank you for all the suggestions - but like you I am not too sure which one solved the problem! I think it was either or both:
enabling files and media access in the Android App Settings (just in case it was needed for the downloaded files) and/or
disabled battery optimization (allow background use of battery) in Android settings, like you recommended.
I am leaning towards the battery optimization as the culprit as I did some testing before disabling by running the app and keeping the screen on and the Plex app open on screen (so it wouldn’t go into background mode); didn’t seem to have any issues with continuous play when I ran it like this, but the issue restarted when I re-enabled the screen timeout (before disabling the battery optimization).
Anyway seems all good now - and FYI for any other users having a similar issue.