@neeeeb thanks, that worked for me.. Problem solved

@substring Yeah, no problem, I just wanted to keep it at max anyway. I just thought that the games had no sound since one of my cables from my TV to my sound system had become unplugged. In-app volume settings are probably only necessary on hand-held/arcade devices anyway. Thanks for the help.

@tavernylol2-tavernylol i'd remove the mupen64 folder in share\system\configs, reboot, and try again

@chris-broughton the pi0w is fully supported wifi AND bt

@32vk

Hi,

this is normal, you can't get working both usb sticks at the same time.
I don't know any way to do this.

@sylvester

Well, if you did not scrape, then ES displays the rom name, so I'm afraid you're gonna have to edit every rom name manually to remove the region tag...
My soft allows to change infos from the xml only, not the "real" rom name...

@rockaddicted I cannot follow the last steps to enforce my own root password as @frankie842 managed to do.
I've even tried changing the recalbox-config.sh file in raspbian to set password lenght '-w8' to a greater length . 12 and 15. Both were ignored and in the recalbox graphical interface it still shows its small 8 character password.

@stigzler I mean /usr/bin/python /recalbox/share/system/fanControl.py & so that the process goes to background in multiprocessing. Otherwise you just lock the init script and never give the hand back.

What is your python script ? you should, for debug, run your script in custom.sh like /usr/bin/python /recalbox/share/system/fanControl.py 2>&1 | recallog & and see what the recalbox.log mentions

I have the same problem
But...
Formating without the "quick format" didn't solved my problem...

@quenbo on last 17.12.02 you can also switch on gliden64 core

@bautidj it is not possible to upgrade from 4.0, simple as that. reinstall from fresh

@srato if it's only kodi, no

héhé 😉

and it not 4.1 17.12.02 but only 17.12.02.
As explained if these posts, we changed our release name and we are using a semantic way based on released date.

https://www.recalbox.com/blog/en/post/blog-2017-11-01-recalbox-17.11.02/
https://www.recalbox.com/blog/en/post/blog-2017-10-15-after-4.1/

Same to me, the settings of my Joypad don't get saved after all - same to all the other menue settings (running at a fresh install of 17.12.02 here)

I have the same issue with a fresh installation of the latest Recalbox from today. The settings were not saved, the SD Card storage is "n/a" and my XBOX controller isn't working either.