Serenity relies on the video player to report the end time or if playback completed normally itself (i.e. the video played all the way through). If the player for some reason is not reporting the correct playback time or how video playback ended, then Serenity can't update PMS correctly.
Yes, I know. But it's not just the player itself which is responsible for this, as it can only work with the data present in the stream sent to it by PMS. So if PMS has in any way messed up the stream that could make the player misinterpret the playback length info.
Also, Serenity should detect if playback went greater than 90 percent, then it should mark the whole thing as watched. I've seen some situations where Serenity from older versions had left some dirty progress information and it messed up the playback positioning. Usually in these cases a toggle to Unwatched status resets things, and future updates work as expected.
If you mean future updates for the same episode, that's not a very useful workaround, as it will usually be a VERY long time before I want to watch the same episode again. If you mean future episodes of the same show, then you've got me confused, as I don't see how or why progress info for one episode would influence the next.
Haven't had a chance to go through all the scenarios but will try this evening.
I'll write up a wiki page about the testing for this as well, and will probably open it up for people to update the page as well to add further test cases.
That will be useful, so we can agree on the most meaningful tests for such issues, best optimized for exposing their causes.
One last item, please make sure MX Player Pro is selected as Preferred External Player in the Settings. This will make sure that Serenity is passing the correct information and looking for the return information from MX Player as well.
It was so selected for all of my reported tests.
That is how I normally use it.
Btw:
About 'MX Player Pro' I have to say that I'm a bit disappointed with playback results on my OUYA.
While it does stutter less than the internal player of the OUYA does, it's still far from perfect.
I get 1-2 seconds of stutter in the startup of appx half of my show episodes and in appx half of the cases there is also a second or two of stutters somewhere in the middle of the episode. This is probably due to the fact that they haven't made any OUYA-optimized codec package, so I have to use the one for the closest related phones/tablets, this being the one named "MX Player Codec (ARMv7 NEON)". (At least I think that's the best one. I also tried one without the NEON tag, but it didn't work well at all).
Best regards: dlanor