This is indeed part of a safe shutdown circuit. This pin needs to be HIGH while the raspberry pi is on and not change its state before shutdown process completes, because it drives the mosfet that provides power to the pi. Thank you, I will try your script although I don't understand it.

Success!!! After a bit more testing, a lot of head scratching and a little kicking myself I found the problem and fixed it. The moral to the story is not to make assumptions. The circuit is connected at the junction marked below - usually I'd expect this to be marked differently so assumed it wasn't connected. Adding a small link to the circuit as below and it works like a charm. Now I can move on to building this into other projects. For anyone else looking to do this then at least I've validated the above circuit diagram so you don't have to. If it's any help I can post the Eagle files for my little prototype circuit - just let me know.

@robhubbard86 https://retropie.org.uk/forum/topic/3/read-this-first and give us more info about your system

Awesome. I will check out that link. Thank you.

@mitu Nearly forget that there is a WIP PR ;) I think this can be a usefull addition to our installations now.

@DrSubsonic said in Updated Packages and now system shuts down before launching retropie: @mitu the seller sold me the arcade system.. just came with retropie installed thats all. If RetroPie came with the system, it was sold with the system. @DrSubsonic said in Updated Packages and now system shuts down before launching retropie: ran sudo raspi-config and it did not ask for a username or password... That is normal in RetroPie. It's less secure than in most other Linux systems, but I guess it's just a compromise for convenience. guess i need to do a full flash of a fresh install That may be the best course of action if you neither can fix it by yourself nor get support from the seller.

@mitu said in Modify Power Button Behaviour to 'Hold for three seconds'??: You can increase the bouncetime from 2sec to something larger. Even as it is now, just a single quick push will shut the software down - i dont have to hold the button at all. Perhaps I need to use a different script that relies on the button being held.

@mitu i have another respberry pi2 , I will check it and update

All right. I took a look into the sources of the ControlBlock driver. The same issue that caused the slow shutdown for the PowerBlock also existed there. I have fixed that now.

Try a NESPI+ case ... properly set up, it has a real working power button that triggers shutdown script and actually turns power off to the Pi. For your own playing, it is not necessary. But if a retropie/kodi/other setup is in a common area / family / kids / etc. it makes things much easier.

@cmscss Yes... the multi_switch.sh script always provides safe shutdowns. Deepsleep happens if after shutdown the red LED still glows. So you need a power device that cuts power after shutdown. But no script can change the behaviour without the hardware parts. But deep sleep is a very cheap alternative to those power devices. You may try it out ;) Just connect any switch to GPIO3 and ground (it's pin 5 and 6 on the Pie header) only this GPIO enables a repowering after shutdown ;)

@tr33x0rs Yeah, about that - I've looked again and the shutdown command is not used anymore, instead there's an external script that does the shutdown/reboot/restart/quit. For Windows, there's no such script, so unfortunately you'll not be able to use that menu.

@drakaen391 About your posted codings.... Does the wait command works in your case? @mediamogul and his while-loop by monitoring PID status is imho better ... wait can only be used on child processes out of the own subshell

@rbaker The kit from adafruit comes with a boost converter that converts the 3.7V up to 5V.

@totallyice Please re-read my previous message. Your system is stuck in a reboot loop so you're not going to be able to access the command line to make any modifications to fix the problem. In order to fix this error, you'll need to delete/disable the Controlblock service, but you'll either need a Linux computer to read the card's Linux partition (won't work from Windows/macOS) or you can try booting into 'safe mode' on your PI system to have a command line to make modifications. See https://retropie.org.uk/forum/topic/672/a-stop-job-is-running-for-lsb-controlblockservice-init-script/13.

I had a problem with 4.3 - every time I played something from Kodi, the screen would go black after playback. I would have to reboot to restore the GUI. I couldn’t find a resolution so the only way to solve it was to roll back to 4.2 where I have no problems with the screen going black after playback. Unfortunately I have this other issue that I’ve not encountered before. Worth noting that I ran Kodi 17.3 before and had the option to reboot/shut down.

Just for clarification as well, @Zigurana 's Kiosk mode also does exactly that (well, not changing the labels, but only keeping those options, yes).

Yup, confirmed. Don't install the Control Block module from the Drivers list if you're not using it and updating with Retropie 4.3.5, because it looks for it and if not detected, initiates the shutdown sequence.