When a problem is hard to pin down, the team will often ask you to enable debug logs before reproducing the bug. Recalbox and the emulators then write far more detail into the files in share/system/logs, which is what makes tracing the root cause possible.
Debug mode is not a fix: it repairs nothing, it documents. It is the diagnostic tool, not the solution.
START to open the MAIN MENU.ADVANCED SETTINGS.ACTIVATE DEBUG/VERBOSE LOGS.The switch takes effect immediately: no reboot needed, go straight on to reproducing the problem.
recalbox.confThe same setting can be written in the recalbox.conf file:
emulationstation.debuglogs=1
Set the value back to 0 (or comment the line out with a ;) to return to normal. A change made directly in the file requires a reboot to be taken into account.
share/system/logs — the \\RECALBOX\logs network share gives you direct access (see File management).The most useful files are frontend.log (the interface), es_launch_stderr.log and es_launch_stdout.log (the last game launched) and recalbox.log (the system scripts). Each one is described on the Troubleshooting page.
Rather than sending files one by one, generate a support archive: it holds the logs and the whole hardware and software context.
Remember to disable debug mode once the diagnosis is done: permanently writing detailed logs can degrade the performance of some emulators, MAME in particular.