Plex Android client -- unable to resume from the middle and jump forward

I have a curious case where in Android client, occasionally, for some files (mixture of .mkv and .mp4 formats) the client wouldn’t allow me to jump forward in playback nor to resume playback from half-way thru. It always resets to the beginning of the video file.

Just now, I’ve tried to resume the file in a Wen client and it worked just fine without the hitch. Started happening about a month or so ago, but you know, holidays season so I didn’t get to post it until now.

I’m on Plex client 6.12.0.3239 (5ffd4fab) on LineageOS 14.1 and Plex Server 1.10.1.4602-f54242b6b on Linux 4.4.0-103201712311231-generic (#0+mediatree+hauppauge-Ubuntu SMP Sun Dec 31 21:15:04 UTC 2017).

Anyone else has this issue? Anything I can try to remedy it?

Thanks!

So no one else has this issue and it hasn’t been reported before?

I’ll try to capture logs next time it happens (it happens randomly and I’m not always in the position to capture logs right then) in the mean time if anyone has any suggestions – go ahead.

Just saw this thread. We don’t officially support non AOSP version’s of Android so your issue could be related to running LineageOS. We do try to support these other versions but can’t guarantee they work, since we don’t officially test with these other OS’s. If you manage to get logs when this happens, we can definitely take a look.

@“MovieFan.Plex” said:
We don’t officially support non AOSP version’s of Android

Just to clarify – as in you don’t support any of the CAF-based ROMs or you don’t support any of the AOSP forks?

If former, I don’t think the specific build I’m running has any CAF code in it. If the latter – what is the “officially supported” tablets list, just Nexi and Pixel C?

Sorry, that wasn’t quite clear or correct. I really mean that we only test on devices using the original ROM that they come with. This can include other versions of Android. We do test on things like One Plus devices and their Oxygen OS. But if you take your Pixel and install some sort of custom ROM, whether it is AOSP based or not, we make no claim as to how the app will work, since we do not test these scenarios. If you have a device and our app doesn’t work on the official ROM that comes with that device, we can take a look and try to reproduce if we can get a hold of that device. If you are running a custom ROM, we are not going to install that ROM to test our app. We can try to blindly make a fix if there is info in the logs to help indicate what might be the problem, but we make to promises.