@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.

We could improve on this: Press UP to go to the Quit menu. You know, wrapped-around menus?!?

It works. Thanks

@crazydude2 Wow awesome! So have fun...

Following the link from @Zigurana above, I took the brave step (for me) of soldering cut down headers to the reset connections on the pi itself today. It now works a treat to restart from sleep, just got to fix a momentary switch onto the case next:)

@crookie333 yup i would say it is a bad card.

@petrockblog There's a update to the code! Version 1.59 --- I update forst posting! Version 1.58 Introduced a method to kill child processes via PPID @cyperghost Version 1.59 is a code polishing done by @meleu

Can you post the output of the quick installation commands from https://github.com/petrockblog/ControlBlockService2#quick-installation here, please? There is also a video that shows the "good case" installation.