This page was last updated on Discover Kodi as a TV frontend. The drivers that are shipped with the kernel will not recognize the devices as keyboard-like devices anymore. Accordingly, the customization of the key names should be done via your own keytables. An updated version is available in our linux-media-dkms package. In general, yaVDR supports bluetooth devices that are recognized as input devices. The second option requires writing some udev rules to bind the devices to eventlircd.
Each Bluetooth device that shall communicate with yaVDR needs to authenticate itself first. To avoid dependencies to adimistration tools with a user interface, we suggest the tools from the package bluez-utils.
This package may need to be installed separately. The authentification for devices with a display may require a PIN entry for the pairing, which can be done via:.
For devices such as the PS3 Remote or other bluetooth remote controls and keyboards without a default pin:. Connect to the device for test purposes:. Remote Control. Your support is essential for the yaVDR project. Basic Principles [ 19 ]. Bug when using --uinput Sadly, recent lirc version are suffering from a bug when forwarding key presses in combination with --uinput.
All roads lead to eventlircd As shown in the graphics above, depending on the driver and the receiver device or DVB adapter, a keypress can be routed totally different paths until it is processed by eventlircd.
The advantages of eventlircd are: early availability of the lirc socket allows an earlier start of the VDR during boot time pre-configuration of several input devices Compatible with keyboards, rc-core and lirc devices A manual configuration by the user is not required anymore if remote control and receiver are already known to the yaVDR developers and support was added.
As with all great concepts, there are some "disadvantages": To take advantage of a eventlircd, a standard key assignment is required, that "normalizes" the keys from the different devices.
In consequence, the "learning" function of the VDR is not used anymore. Furthermore, lirc requires that the naming of all keys in the lircd. We suggest to use the key names of our standard configuration. Caution when changing the remote contol in the remote. When are evmaps useful? Gathering informationen about the receiver. Customization of the key layout of rc-core receivers The layout of receivers that are recognized as keyboards can only be changed via evmaps. Determine scan codes.
Creating a keymap. Comments in the keymaps ir-keytable does not accept pure comment lines. Complete specification of the keytable name and the used IR protocol Comments behind the key definition are supported. Loading a keymap. Corner cases Sometimes, it may not be possible to reliably determine the receiver exactly by vendor ID and model ID. LIRC Receivers. Serial receivers. Igor USB. Remote control settings in the web frontend! X10 Remote Controls. Changes by linux-media-dkms and the kernel 3.
Bluetooth devices. To the left. To the right. Digit 0. Digit 1. Digit 2. Digit 3. Many users had problems with that and the development was discontinued. Since then we concentrated on finding a new and better solution. I guess we now have one. October , hotzenplotz5 - yaVDR. A short notice: As some smaller bugs crept in at the last minute we decided to provide you with an updated ISO image called yavdr What has been fixed?
These corrections will of course also be made available as package updates. October , hepi - yaVDR. We are happy to announce the release of yaVDR 0. Best regards Rantzauer. Wow, very cool solution! Didn't know "apt-file" Gerald. Thank you! Hello That was super cool, thanks a lot. Then running dmesg I get this: [ Can anyone help with this. Could it be a firmware issue? If yes how do I load the right firmware?
0コメント