Do you have the 7″ touch display ? You probably had to configure the Pi to use the DSI output my modifying the bootloader configuration (the config.txt file on the boot) partition. To switch back to HDMI, you'll need to remove or comment the lines that enable and configure the LCD.
There might be a way to enable the LCD display only of HDMI is not detected through the use of conditional filters in config.txt, but you'll have to experiment and see if that's possible. If the LCD pannel cannot be detected at boot by the bootloader, then conditionally enabling/disabling it might not work.

Please add some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu , worked...thanks a bunch.

@catx
Please delete this File :

system.sh in : /RetroPie-Setup/scriptmodules/system.sh

and then in command line :

cd RetroPie-Setup sudo ./retropie_setup.sh

@lolonois and yet, it tracks their last-played date and even groups them into a last-played category if you enable it. As long as you have network access, you have an accurate clock I think.

@dankcushions thanks a lot!!!
Sorry, i read a lot of documentation over the years, but in this case i was too blind to have a look into the specific chapters...i only read the doc about "Configuration Editor", my fault!
Thanks a lot for your help & patience!

System apfm1000 is working :
https://retropie.org.uk/forum/topic/29682/development-of-module-script-generator-for-lr-mess-and-mame-standalone/634
https://retropie.org.uk/forum/topic/29682/development-of-module-script-generator-for-lr-mess-and-mame-standalone/650

@mitu Thanks - I thought it would be something easy, and it was that. All works now!

(Just in case anyone else sees this - the .desktop file is in /usr/local/share/applications )

You can see a configuration example here for Atari 2600; all games for that system will use the same overlay.

@mikeb said in Retropie does not work on pi4 with xbox one wireless controller:

following all the videos and articles

That could be your problem right there. "All"? You don't need any certification to post a video online.
Without knowing what you did, how can anyone help?

Regardless, it's probably just a driver issue. You may have inadvertently deleted a file which one of the videos told you wasn't important, but actually was. Maybe you bumped the keyboard while editing a config file. I don't know.

https://retropie.org.uk/forum/topic/28094/xbox-one-controller-detected-but-wont-pair/6

@mitu

This fixed the issue. I was under the false impression that a clean install from an imaged I downloaded would be the latest version.

Thank you for your help.

Press F4 in Emulation Station to go to the command console. Then enter:

sudo apt clean # clears the update cache sudo apt autoremove # removes installed packages that are no longer needed by other packages (so-called dependencies) exit # exits the console back to Emulation Station

@mitu Yes, it works with the select button, so it is fine, and defnitelly it does not worth to take so much of your time. Thank you very much for all that help.

All what I can say is for sure it used to work with the home button but since some update it stopped working anymore. I wonder if there is a difference between the xbox one controllers. The two controllers I have are the ones with the USB B connector, not the newest one with USB C.

But yes, I guess I can call it a day and use as it is. Thanks again!

I use a Pro Controller with the Pi thanks to those instructions. It works wired and wireless.

Did you have any error messages while installing either the HID module or the userspace driver?
How are the lights on the controller behaving when you connect the cable? Do they start blinking "side to side" quickly? If they do, did you press L + R to pair?

@vodkanakas I think the [A] means it's an alternative version

@sleve_mcdichael sorry yeah that's what I meant to ask but didn't word it properly lol I'll try this today and see how it goes, and I've no problem shaving a few GB off if it means saving my build lol

I have found the holy grail in this repo line:
https://github.com/meleu/RetroPie-joystick-selection/blob/master/jsfuncs.sh#L345

Basically in order to change the index, we should just edit /opt/retropie/configs/all/retroarch.cfg at this line:
input_player1_joypad_index = "some_index_number"

or whatever input player you want. NOTE: i didn't tested it yet, but this might work.

@louf Sorry for the late response, I am currently not maintaining Kodi packages since Kodi 19 does not support H265 HW video decoding on RPi 3/2, which are the ones that I still use for Kodi.
About your problem, I can't really tell, never happened to me and I never anyone complaining about something like that. Can you reproduce your problem and post a Kodi debug log? A photo/screenshot may also help.

Please provide some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

An EmulationStation crash, as you're experience it, usually means the controllers are disconnecting during the initial scan. Are all joysticks plugged in directly into the Pi ? Are you using a good power source for the Pi ?

How exactly did you check the memory? Fake cards report a bigger size than they actually are. You'll only notice it after you write more than their actual size to them, as the exceeding data will be lost, often without any error messages if the fake card was done well.

If you can boot to RetroPie's command line, you can try to install the tool f3 and test the card with that:

sudo apt install f3 # install the tool cd # change to home directory makedir test # create a test directory f3write test # write 1 GB sized test files until the card is full f3read test # read the files' test patterns rm -r test # remove the test directory

It will test the actual amount of data that can successfully be written to the card and read again.