Ok, thank you for trying!
I guess i will build a little amplifier circuit that can handle it.

@granderjoree
In retroarch you can adjust the fullscreen width and height, this will change the resolution of the app, It may help none in performance. The aspect ratio is the part that scales the emulators output, to fit in your screen, you can do whatever you want with it, pressing the start button on an option sets it to its default value, you can save options for individual games, in the games quick menu and then under options, save game options.

The run command when you start an emulation gives you some control of the hdmi output, you can change to Monitor modes, or HDMI, some of the modes will not work, You can even change to a 50hz refresh rate.

There are additional configurations for individual emulators outside of retroarch, in these config files you can usually change the emulators rendering resolution. You can access the configs through the network share, if you set-up samba on the PI.

If you look into your gamelist.xml that was freshly created, does it show all games? If yes, do the path look right for all of them?

This is an old issue but, I have something to add. The button response, is only accepted right after the dialog/launching.png disappears. There is it seems, either a huge delay, or joy2key won't trigger until the end of the script. I'm guessing this could be fixed, its worth fixing. Additional features should be added to run command as well, though I can't think of any good ones right now.

Bump. Ran into this minor problem as well

Hi, they connect just fine when I turn it off and back on if I need to reboot my pi. I just liked the way they always turned off immediately on a reboot using retorpie 4.3. The little hack for connect on boot would reconnect my controllers every time on a reboot without me having to turn them off and on again. But with 4.4 there is some type of delay sometimes that causes them not turn turn off immediately when I reboot (therefore causing problems with the boot "hack").

I just didn't know if there was some kind of script (if that is the right term) that could help assist with the killing of the bluetooth signal when rebooting under 4.4...?

@KnightZ87

Have a look at this article about hdparm! There are many settings you can tweak!

Tune Your Hard Disk with hdparm:
http://www.linux-magazine.com/Online/Features/Tune-Your-Hard-Disk-with-hdparm

You could also set the sleep/standby timer to a longer time!

Change hard drive's sleep/standby mode timer to reduce power consumption:
https://linuxconfig.org/change-hard-drive-s-sleep-standby-mode-timer-to-reduce-power-consumption

Spin Down and Manage Hard Drive Power on Raspberry Pi
https://www.htpcguides.com/spin-down-and-manage-hard-drive-power-on-raspberry-pi/

@Charlie-Scheib

Is there no way within the drive settings itself to keep it spinning on the RetroPie/Pi settings?

I haven't tested this but this might work!
You'll need to do most of this from the command line (difficulty: medium)

There are a couple hard drive power management programs that can be used on the Raspberry Pi to control how long before the hard drive spins down to save power and the life of the hard drive.

I wonder if the program hdparm will work for you. You could set the 'spindown_time =' to something like an hour (720) or 2 hours (1440). You basically find out how long you want measured in seconds and take that number and divide it by 5. So 2 hours is 7200 seconds (7200sec / 5 = 1440).
https://www.htpcguides.com/spin-down-and-manage-hard-drive-power-on-raspberry-pi/

@mitu @cyperghost

I sent an e-mail to RetroFlag the other day describing the issue and from looking at the photo of the wires I sent, they said the colored wires were in the wrong position. They apologized then gave some directions on how to take the wires out and what the proper color order is.

I tried taking them out of the black plug but it seemed a bit of a hassle. Fortunately a replacement case arrived from Amazon today and the colored wires in the replacement case are in the correct position. I rebuilt my RetroPie and the shutdown and reset worked right away :). Thanks again for the help.

tldr: Original case wires were messed up, replacement worked.

@zuuzuu
Hello guys.
I've encountered the exact same problem with ALL f1 games for ps1. 2001 version is unplayable, and others get stuck in the first screen, right after "ea games challenge everything..." Did you guys manage to fix or at least identify the problem?
I tried also an android emulator and got the exact same result.... That's sad, I have plenty of ps1 games on my raspberry, and they all work great...

@mattrixk lol yeah man I'm having fun with it all, made one theme already but working on anither now just couldn't get rid of that text so I could add my own.

I will have to upload my first theme to share soon.
Thanks again.

Wow, that was fast!

Thank you @mitu

Thanks folks for your great advice and quick response. Making the keyboard change in raspi-config worked like a charm. By the way, I highly recommend this nespicase+ case. Thanks again!!!

@D39 Have fun with RetroPie !

@brunozero I have not noticed any issues with exiting mupen64plus on my pi. Please read and answer the questions so we can help you:

https://retropie.org.uk/forum/topic/3/read-this-first

@mitu

You forgot to ask me an important question, "Is there a copy of that image?"

The answer is yes!!! I am now back in business. This time I will pay close attention to what the heck I am changing. This was a great learning opportunity, however, so thank you very much for your support. =)

I have two cards for the sake of clustering, in case you were wondering.

@webodan

EDIT: OK, so I double-checked the md5s of the bios files that i have downloaded BEFORE and AFTER sending them to the pi (just in case they would get corrupted as they were sent or something) they matched on winmd5 just fine.

lr-pcsx-rearmed can use only scph5501.bin from the list of BIOS files you have, and that file has a wrong MD5 in your screenshot - it's not what's in the docs or what the core expects.

Unfortunately I can't get a copy of the game to test, but can you just get a RetroArch log file and put it on pastebin.com - enable Verbose logging in the Runcommand launch menu, run the game for a while, then upload the /dev/shm/runcommand.log log file to pastebin.com and paste the URL here.

@krullbeast said in can udev read i2c and hardwired GPIO buttons simultaneously?:

do you think it is possible to read the i2c data and also the A and B buttons inside of retroarch?

Not an expert on this, but I think RetroArch doesn't read directly from GPIO (I2C or otherwise), instead it uses an established input driver (udev/sdl/etc.) - https://github.com/libretro/RetroArch/tree/master/input/drivers.