This program listens in the background for gamepad inputs. If a special button combination is getting pressed,
the provided command line will be invoked. It runs a command once defined buttons were pressed. It was developed for Raspbian and PS3 wireless controller but should work everywhere with udev
and joystick support.
I have a Raspberry Pi. The installed operation system is raspbian. The Kodi package runs pretty well as a media center. The remote control is an App on a smartphone. So no other controller is needed.
After couple of month I found this great RetroPie project. There is also another great one which brings it on a software level instead making a boot image. It's called EmulationStation. The setup with my preferred PS3 controller and the configuration went well and it worked fantastic. The game console works perfectly fine and brings me back to the good old jump'n'run 90s but now with big screen and cool wireless controller!
But one thing was an issue. I wanted to use the same hardware and don't miss my system (raspbian). Dual boot is not cool and takes too long. So basically what i needed is some kind of trigger to end any X11/Kodi processes and start EmulationStation ... and of course vice versa.
In my configuration Kodi runs as default. Media center is still the primary usage. But the idea was to take the PS3 controller press some button combination and the EmulationStation will apear. After I played enough, just press this buttons again and media center will apear and I can put the PS3 controller back.
After searching the internet, I found nothing really interesting. Kodi addon will not work because gamepad support is still missing. EmulationStation addon might work but than ... Kodi solution will be missing. So I had to go one level up to the OS. But even here I found nothing really easy to setup or working. So I decided to write this program. It runs as a daemon in the background and listening in nonblocking mode to /dev/input/js* devices. To make it hotplug capable, it's monitoring the udev signals if no device is present.
cd /tmp
git clone git@github.com:workinghard/jslisten.git
cd jslisten
echo "Building jslisten binary"
make
echo "Moving jslisten binary to executable path"
sudo mkdir -p /opt/bin
sudo cp bin/jslisten /opt/bin/jslisten
echo "Copying default config; you will need to modify this file for your use case."
cp /etc/jslisten.cfg ~/.jslisten
echo "Adding jslisten support at boot"
sudo cp utils/jslisten.service /etc/systemd/system
sudo systemctl daemon-reload
sudo systemctl start jslisten.service
sudo systemctl enable jslisten
You will need to modify your ~/.jslisten
config file based on your own requirements.
Following example for Raspbian. Should work for many other distributions almost the same way.
make
to create the binary/opt/bin
cp etc/jslisten.cfg /etc/jslisten.cfg
/etc/jslisten.cfg
or as ~/.jslisten
jslisten
that is configured for your use case.jslisten --device /dev/input/js[*]
[*]
is your deviceID (ie /dev/input/js0
)sudo cp utils/jslisten.service /etc/systemd/system
ExecStart
to change joystick devices (defaults to /dev/input/js0
)sudo systemctl daemon-reload
sudo systemctl enable jslisten
sudo systemctl start jslisten.service
sudo systemctl stop jslisten.service
sudo systemctl status jslisten.service
jstest /dev/input/js0
Left Shoulder
+ Right Shoulder
+ SELECT
. I'm pretty sure I will not need to press this buttons at the same time for any games.jstest
(or any other similar program)/etc/jslisten.cfg
or ~/.jslisten
) and maintain the button ID's and the program which you want to run.Note that it calls a custom shell script /opt/bin/modeSwitcher.sh
. You will need to define something like this for your use case.
[Generic]
program="/opt/bin/modeSwitcher.sh"
button1=10
button2=11
button3=0
button4=
/dev/input/*
events. For X11 you can add an exception in /usr/share/X11/xorg.conf.d/10-quirks.conf
but Kodi is ... nasty ... As long as they don't implement a nice unified unput support, my workaround is to revoke the kodi group rights to the input devices. :(--loglevel debug
option when starting the binary (either manually or adding to the systemctl
[reference above] call) and check syslog.You can have different key sets to run different programs:
[Generic]
program="/opt/bin/modeSwitcher.sh"
button1=10
button2=11
button3=0
button4=
[Fun]
program="/opt/bin/haveFun.sh"
button1=0
button2=3
button3=
button4=