Mpv Media Player core closes randomly and unexpectedly when trying to open a file

When trying to open a media file (.mp4 or .mkv) using the mpv core, the core often closes unexpectedly (drops back to the content explorer). Sometimes the core displays and/or plays a split-second of the media file (video+audio) before closing unexpectedly.

It always closes before playback or after the start. If there’s at least 1sec of playback then the rest of the video plays successfully regardless of what I do – until I close the video and return to the content explorer. This does NOT guarantee the next attempt(s) to watch the same video afterwards will be successful.

Playback with the ffplay media player core is always successful.

The device in question is a 35XXSP v2 with washers added to the d-pad membrane.

NOTE: This is a recent occurrence after a partial disassembly that required disconnecting the battery (after the device was turned off) and inserting small thin nylon washers. I cannot rule out a hardware issue, but cannot confirm it: the bug seems to occur regardless of the button press or the flip screen’s position, and all other cores and apps seem to function without any issue whatsoever – including performance-heavy ports such as Stardew Valley.

Current failure rate is approximately 4 out of 5 playback attempts.

Issue tested on SanDisk and Silicon Power SD cards of different sizes (all formatted in exFAT) with no noticeable correlation.
Issue tested at different internal temperatures (immediately after start, after 1hr of Stardew Valley playback etc) with no noticeable correlation.
Issue confirmed to occur with all mpv-compatible sources I know of – including playlists, webradio streams and IPTV streams.

Here’s an example /MUX/log/[data]_ext-mpv.log where the file successfully played on the second attempt, played only for a split-second during the last and second-to-last attempt, and immediately closed unexpectedly on all other attempts:

|[ 47.21] [e[38;5;33m*e[0m] CORE      |ext-mpv-general|
|---|---|
|[ 47.21] [e[38;5;33m*e[0m] Content Launch|DETAIL|
|[ 47.21] [e[38;5;33m*e[0m] FILE      |/mnt/union/ROMS/video/bill wurtz/9 8 7-(360p30)_10-33.mkv|
|[ 47.22] [e[38;5;33m*e[0m] NAME      |9 8 7-(360p30)_10-33|
|[ 49.49] [e[38;5;33m*e[0m] CORE      |ext-mpv-general|
|[ 49.49] [e[38;5;33m*e[0m] FILE      |/mnt/union/ROMS/video/bill wurtz/9 8 7-(360p30)_10-33.mkv|
|[ 49.49] [e[38;5;33m*e[0m] Content Launch|DETAIL|
|[ 49.49] [e[38;5;33m*e[0m] NAME      |9 8 7-(360p30)_10-33|
|[ 56.20] [e[38;5;33m*e[0m] CORE      |ext-mpv-general|
|[ 56.20] [e[38;5;33m*e[0m] Content Launch|DETAIL|
|[ 56.20] [e[38;5;33m*e[0m] NAME      |9 8 7-(360p30)_10-33|
|[ 56.20] [e[38;5;33m*e[0m] FILE      |/mnt/union/ROMS/video/bill wurtz/9 8 7-(360p30)_10-33.mkv|
|[ 58.08] [e[38;5;33m*e[0m] CORE      |ext-mpv-general|
|[ 58.08] [e[38;5;33m*e[0m] NAME      |9 8 7-(360p30)_10-33|
|[ 58.08] [e[38;5;33m*e[0m] FILE      |/mnt/union/ROMS/video/bill wurtz/9 8 7-(360p30)_10-33.mkv|
|[ 58.09] [e[38;5;33m*e[0m] Content Launch|DETAIL|
|[ 61.43] [e[38;5;33m*e[0m] Content Launch|DETAIL|
|[ 61.43] [e[38;5;33m*e[0m] FILE      |/mnt/union/ROMS/video/bill wurtz/9 8 7-(360p30)_10-33.mkv|
|[ 61.43] [e[38;5;33m*e[0m] CORE      |ext-mpv-general|
|[ 61.43] [e[38;5;33m*e[0m] NAME      |9 8 7-(360p30)_10-33|

Cannot attach the diagnostics archive here but ready to provide it via Discord upon request.

Thank you in advance!

Further testing has showed the problem to be exclusively software-based. Fresh SD1 install proved to be bug-free with both the regular SD2 and a brand new SD2. Custom mpv config seems to have no influence on the bug – restoring the old config did not fix the bug, putting my custom config on the new install did not introduce the bug.

Not sure what may have introduced the bug. Chances are I did not follow some part of the proper power discipline before and after unit disassembly.

TL;DR – Fixed with a fresh Pixie install.

Old install info and logs are still available upon request for at least a day, should you need them!