[majerle9]

I would love that as well. I’m trying to figure out if there is a way to quit Emulationstation that doesn’t involve F4 or using the EmulationStation GUI menu.

[majerle9]

It’s working for me now. I used both methods just to be sure.

First I went to /opt/retropie/supplementary/runcommand/runcommand.sh and commented out all the lines that had anything to do with joy2key.

# if joy2key.py is installed run it with cursor keys for axis, and enter + tab f$
#__joy2key_dev=$(ls -1 /dev/input/js* 2>/dev/null | head -n1)
#if [[ -f "$rootdir/supplementary/runcommand/joy2key.py" && -n "$__joy2key_dev" $
#    __joy2key_dev=$(ls -1 /dev/input/js* | head -n1)
#    "$rootdir/supplementary/runcommand/joy2key.py" "$__joy2key_dev" 1b5b44 1b5b$
#    __joy2key_pid=$!
#fi

# check for x/m key pressed to choose a screenmode (x included as it is useful o$
#clear
#echo "Press a key (or joypad button 0) to configure launch options for emulator$
#IFS= read -s -t 1 -N 1 key </dev/tty
#if [[ -n "$key" ]]; then
#    get_all_modes
#    main_menu
#    dont_launch=$?
#    clear
#fi

#if [[ -n $__joy2key_pid ]]; then
#    kill -INT $__joy2key_pid
#fi

#if [[ $dont_launch -eq 1 ]]; then
#    exit 0
#fi

Then I went to /opt/retropie/supplementary/runcommand/ and deleted the joy2key.py file.

Before I did that, when I started a game it said:

Press a key (or joypad button 0) to configure launch options for emulator/port ($emulator). Errors will be logged to /tmp/runcommand.log

Now it says:

========================================

Thanks for all the help.

[majerle9]

add a shutdown and restart option under the retropie menu.

Can you tell me how to do this? I would love to be able to shutdown from the EmulationStation menu itself without having to hit Start and then use the popup menu. That would be a very easy way to childproof the system.

[majerle9]

I tried both methods listed. First I removed the lines from runcommand.sh, but nothing changed. Then I deleted joy2key.py and nothing happened then either. Now I’m not sure runcommand.sh is what runs this message. Has anyone actually tried this method and gotten it to work?

I’m desperately trying to childproof my retropie too and this is one of a few parts of the system that leave it open to damage from kids.

[majerle9]

Thank you asipsis for mentioning the 15 second delay. I just made two changes and now it seems like everything is working. Here’s what I did in case anyone else is facing the Can’t set scan mode on hci0: Network is down (100) error.

Step 1: Add a 15 second sleep command before EmulationStation starts.

cd /usr/bin/
sudo nano emulationstation

After the #!/bin/bash line, before the $es_bin, add the command sleep 15.
My script now looks like:

#!/bin/bash

sleep 15
es_bin="/opt/retropie/supplementary/EmulationStation/emulationstation"

nb_lock_files=$(find /tmp -name ".X?-lock" | wc -l)
if [ $nb_lock_files -ne 0 ]; then

Step 2: Change rc.local

cd /etc
sudo nano rc.local

Add the following 2 lines right before the “exit 0″ line:

hciconfig device up
hciconfig enable pscan

[majerle9]

asipsis,
Have you been able to get multiple controllers to pair on 100% of startups? I followed your ‘hciconfig hci0 piscan’ method and I’m only getting it to work about 70% of the time. When it works the dongle will turn on and start pairing when the splashscreen displays. The other times my bluetooth dongle fails to turn on so I can’t pair my controllers. I get the same error as quackwalks

Can’t set scan mode on hci0: Network is down (100)
[FAIL] startpar: service(s) returned failure: rc.local … failed!

I can’t figure out why bluetooth works sometimes but not every time. Is it possible that the splashscreen finishes too quickly before the dongle can turn on? Is there a way to extend the boot period when the splashscreen is running to give the dongle enough time to turn on?

Or am I wrong and the answer is something else entirely?

[Author]

Posts