NO: VIM3 - playback does not start

I have a somewhat weird issue with my Khadas Vim 3, where playback does not start.

To be precise, this only appears when a delay after display mode switching is set. In my case, I need to set a delay of about 2s to mitigate problems with audio not playing. (LPCM and passthrough)

Starting playback with a delay set in the settings results in a stuck image (the first frame of the file) until “something” changes on screen. This can be a small movement of the cursors or a key press. It does not matter what content (1080p/4k/sdr/hdr) is used. It happens with all of them.

When having debug logging on with the info on screen, everything works, so the changing debug info overlay text on screen is enough to trigger a change, so playback starts.

I’m only seeing this problem with my VIM 3. I also have an X96 X10 Pro, where I also have a delay of 2s set. Everything works fine there, no keypress etc necessary… So this must be a VIM3 /A311D issue.

I created a Kodi debug log (loglevel 1 through advanced.xml) and also the dmesg output.

It would be awesome if this could be fixed! Thanks! Please let me know if there is something needed…

kodi_vim3_bug_debug.log (730.6 KB)

dmesg-out-1.txt (80.7 KB)

device: Khadas Vim3 Pro

version: 22.0-Piers_nightly_20251017 (not specific to this version)

##Edit:

After further looking into this issue, it seems that somehow the driver does not send a correct vsync signal, and Kodi is stuck at CVideoPlayerVideo - CDVDMsg::GENERAL_PAUSE: true

Is this an issue with Kodi or really a kernel/driver issue? Who (regarding the CE team or the Khadas guys) can/is able to fix this?

There is no error in log to find.

So you maybe need to try to flash a newer Android on VIM3 first and then try again with latest CE-NO nightly.

1 Like

May I ask if someone could take a look at this issue (a potential driver bug, I guess?) with my Khadas VIM3? => NO: VIM3 - playback does not start

Or is this something I should post in the Khadas forum?

Thanks for your reply! I will try a newer android and retest. May I ask how a newer android should help?