OSMC remote mapping on KodiBuntu

h4rri · 24 June 2016 11:43

Hi,

I am currently setting up Kodibuntu on a Dell 7010 i5 using Kodi 16.1 with Ubuntu 14.04.4 as the base OS.

I am currently trying to map the OSMC remote [from the store] and having problems with the context and information buttons. Using Keymap Editor I have attempted to map the buttons in the following locations but the actual keypress isn’t being recognised.

Global/Navigation - Show Info & Context Menu
Videos/Navigation - Show Info & Context Menu
Video OSD/Navigation - Show Info & Context Menu

I don’t have the config for the remote so can’t use LIRC and irrecord to check the button code and create a custom remotes.xml file.

Can anyone offer any assistance please? I love the simplicity and feel of the OSMC remote and don’t really want to have to replace it.

sam_nazarko · 24 June 2016 14:30

Does your version of Kodibuntu use systemd? If so this is quite trivial, as our OSMC x64 remote packages can be used, and I can give some simple instructions on this

h4rri · 24 June 2016 14:40

Thanks.

It does indeed, your help would be appreciated

sam_nazarko · 24 June 2016 15:28

Run the following commands:

wget http://ftp.fau.de/osmc/osmc/apt/pool/main/a/amd64-remote-osmc/amd64-remote-osmc_1.2.1_amd64.deb
wget http://ftp.fau.de/osmc/osmc/apt/pool/main/a/amd64-lirc-osmc/amd64-lirc-osmc_0.9.0-5_amd64.deb
wget http://ftp.fau.de/osmc/osmc/apt/pool/main/a/armv6l-eventlircd-osmc/armv6l-eventlircd-osmc_1.2.0_armhf.deb

Then run:

sudo dpkg -i amd64-*.deb
sudo apt-get -f install

Now the remote should function normally. However I note that you wish to change keys. You can do this by editing etc/eventlircd.d/osmc_rf.evmap.

Please tell me what changes you make to your remote button mapping. I am interested in making the experience better for other users.

You may also wish to subscribe to our Newsletter and be the first to know when OSMC is ready for PC.

Sam

h4rri · 24 June 2016 15:45

Thanks.

I have run the above with the following messages:

dpkg: error processing package amd64-remote-osmc (--install):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
Errors were encountered while processing:
amd64-remote-osmc

And

root@Kodi:~# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
libafpclient0 libftdi1 libhdb9-heimdal libkdc2-heimdal libntdb1
libshairport1 python-ntdb python-support setserial
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
amd64-remote-osmc
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 1,488 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 162589 files and directories currently installed.)
Removing amd64-remote-osmc (1.2.1) ...
Removing 'diversion of /etc/lirc/lircd.conf to /etc/lirc/lircd.conf.distributed by amd64-remote-osmc

I assume the errors have resulted in non-installation of the required package.

h4rri · 24 June 2016 16:17

Right, apparently it doesn’t work on KodiBuntu but does on Debian:

# dpkg -l | grep osmc
ii amd64-eventlircd-osmc 1.2.0 amd64 eventlircd for OSMC
ii amd64-lirc-osmc 0.9.0-5 amd64 lirc for osmc
ii amd64-remote-osmc 1.2.1 amd64 Remote support for OSMC, achieved with lirc and eventlircd

So I will rebuild the box with Debian instead and see how that goes. I’ll report back ASAP.

sam_nazarko · 24 June 2016 16:48

Just read above about your Ubuntu version. 14.04 still uses Upstart, which is why you are having problems. You can build eventlircd manually, it is a bit tricky but probably easier than rebuilding your entire system.

I’ll probably write a more generic driver for Linux in the future

Sam

h4rri · 24 June 2016 16:50

Currently installing Debian so hoping this will solve the issues. I will report back.

As an aside, how do you get the unbroken effect in your code inserts? I have used the </> button but it’s all single liners.

sam_nazarko · 24 June 2016 16:51

Three backticks to open, then a newline. Then add code, then add three backticks on their own line to close

h4rri · 24 June 2016 18:11

Ok so clean install of Debian 8, installed Kodi Jarvis and the above listed files and now have no remote functions at all

h4rri@Kodi:~$ dpkg -l | grep osmc
ii  amd64-eventlircd-osmc                 1.2.0                                amd64        eventlircd for OSMC
ii  amd64-lirc-osmc                       0.9.0-5                              amd64        lirc for osmc
ii  amd64-remote-osmc                     1.2.1                                amd64        Remote support for OSMC, achieved with lirc and eventlircd

Any ideas?

sam_nazarko · 24 June 2016 21:21

Did you reboot post-installation?

I’d like to see a system log to show verification of the detection of the dongle and if any udev rules were triggered. This worked for another user under Debian Jessie.

udevadm monitor should certainly show activity hotplugging the dongle

Sam

h4rri · 25 June 2016 10:15

Hi,

I did reboot after install and just now. Same result.

The output of udevadm monitor is huge but it does note the removal:

KERNEL[292.432241] remove   /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.                           4:1.0/0003:2252:1037.0002/input/input4/event1 (input)

And re-insertion of the dongle:

KERNEL[301.393700] add      /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4 (usb                           )

The output of lsusb is:

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 2252:1037
Bus 001 Device 003: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 413c:2107 Dell Computer Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Last few lines of dmesg are:

[  301.546205] usb 1-1.4: new low-speed USB device number 5 using ehci-pci
[  301.647664] usb 1-1.4: New USB device found, idVendor=2252, idProduct=1037
[  301.647668] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  301.647671] usb 1-1.4: Product: USB Keyboard Mouse
[  301.647673] usb 1-1.4: Manufacturer: HBGIC Technology Co., Ltd.
[  301.652480] input: HBGIC Technology Co., Ltd. USB Keyboard Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:2252:1037.0004/input/input19
[  301.652747] hid-generic 0003:2252:1037.0004: input,hidraw1: USB HID v1.10 Keyboard [HBGIC Technology Co., Ltd. USB Keyboard Mouse] on usb-0000:00:1a.0-1.4/input0
[  301.657822] input: HBGIC Technology Co., Ltd. USB Keyboard Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:2252:1037.0005/input/input20
[  301.658144] hid-generic 0003:2252:1037.0005: input,hidraw2: USB HID v1.10 Mouse [HBGIC Technology Co., Ltd. USB Keyboard Mouse] on usb-0000:00:1a.0-1.4/input1
[  301.704786] input: eventlircd as /devices/virtual/input/input21

Thanks for your continued support.

sam_nazarko · 25 June 2016 15:57

Check

systemctl status eventlircd

Might need enabling with sudo systemctl enable eventlircd

h4rri · 25 June 2016 16:50

Comes back with:

systemctl status eventlircd
● eventlircd.service - eventlircd remote support
   Loaded: loaded (/lib/systemd/system/eventlircd.service; enabled)
   Active: active (running) since Sat 2016-06-25 11:07:07 BST; 6h ago
  Process: 854 ExecStartPost=/bin/sh -c for f in /var/run/lirc/lircd-*.sh; do if [ -e $f ]; then s=$(basename $f .sh | sed 's/lircd-//g'); systemctl start lircd_helper@$s; fi; done (code=exited, status=0/SUCCESS)
  Process: 570 ExecStartPre=/bin/mkdir -p /var/run/lirc (code=exited, status=0/SUCCESS)
 Main PID: 853 (eventlircd)
   CGroup: /system.slice/eventlircd.service
           └─853 /usr/sbin/eventlircd --evmap=/etc/eventlircd.d --socket=/var...

After a systemctl enable eventlircd:

systemctl status eventlircd
● eventlircd.service - eventlircd remote support
   Loaded: loaded (/lib/systemd/system/eventlircd.service; enabled)
   Active: active (running) since Sat 2016-06-25 11:07:07 BST; 6h ago
 Main PID: 853 (eventlircd)
   CGroup: /system.slice/eventlircd.service
           └─853 /usr/sbin/eventlircd --evmap=/etc/eventlircd.d --socket=/var/run/lirc/lircd --r...

Still no remote control

h4rri · 25 June 2016 17:09

An IRW gives:

irw
80 0 KEY_STOP linux-input-layer
80 0 KEY_STOP_UP linux-input-layer
66 0 KEY_HOME linux-input-layer
66 0 KEY_HOME_UP linux-input-layer
160 0 KEY_OK linux-input-layer
160 0 KEY_OK_UP linux-input-layer

So Debian is seeing the remote functions

sam_nazarko · 25 June 2016 17:19

Looks good. Just to confirm – you are loading Kodi with --lircdev /var/run/lirc/lircd?

Something like

./kodi.bin --lircdev /var/run/lirc/lircd

Sam

h4rri · 25 June 2016 17:27

Hi,

No I was using ‘kodi’ from console to start it.

The above resolved the issues fully. I shall be ordering another remote shortly

sam_nazarko · 25 June 2016 17:32

Great, glad to hear it.

I’m on holiday for a little bit, so not dispatching anything. But if you order in advance you will get a discount at the checkout

Sam