[fritsch]

 Because this was merged Oct. 27th: https://github.com/xbmc/xbmc/pull/14701

EDIT: the solution is simple: just whitelist the refresh rates you really need. In general those are only 23.976, 24, 50, 59.94, 60

Just to be clear - you're suggesting the whitelist change is responsible for the mouse cursor appearing?   

No, I said that the whitelist change is responsible for having two resolution changes instead of one. That is the first error that shows in the log. This can easily be fixed by a whitelist that lacks 25hz. We never selected a 25hz mode in earlier version. It could be an issue related to that, I don't know. A new debug log with with this whitelist might tell more. 

The root cause is: kodi is not able to differentiate 50i and 25 hz on stream start. Also this has nothing to do with whitelist as the whitelist is NOT changed at all. The code you mention is only triggered _if_ the whitelist is empty AND user has enabled Adjust Refreshraterate in this combination.

So in short:  In order to workaround kodi shortcomings differentiating 25p and 50i content on playback start, you should not whitelist 25 hz modes oder 29.97 hz modes or 30 hz modes.

For the single case: User has Adjust Refreshrate enabled BUT no whitelist at all - I removed all those "half refreshrates" from the internally auto generated modelist.