Slide left or right to access other remotes.įurther detail on the app can be found in the user guide. Long pressing will send the complete IR pattern repeatedly. Tap on the buttons to send their IR patterns. Run mode is where to use the remotes you have created. Or just use the list to find and select the remote you wish to use.Īlso create, duplicate and delete remotes (only in creator mode). Organise, your remotes in this screen, by dragging them about in a list. This is where remotes are edited, by creating or selecting buttons, dragging them to their desired location, changing their design and assigning IR codes to them. Remotes can be loaded or saved to the keuwlsoft/ir-remotes/ directory within the documents folder on your device, or downloaded from a web link. Tap on the disk Icon for load and save options. The ' i' button brings up the user guide. This post has a way of enabling any IR port based on the device that is plugged into it using a Udev rule.Tapping on the cogs button brings up the settings screen where mode, sound, vibrate and more options can be set. One problem with this approach is that if the USB port the IR device is plugged into changes, then enabling that port specifically does not help. Now happily wake your PC from your USB device. Make this change persistent across reboots: $ sudo nano /etc/rc.localĪdd the following lines after the comments and before 'exit 0' # Enable Wake on IR for USB bus 3 port 13.Įcho enabled > /sys/bus/usb/devices/3-13/power/wakeup Test your device, does it wake the system? |_ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480Mīus 3, port 13 matches the bus/port returned by grep (3-13)Ĭheck if wakeup is enabled: $ cat /sys/bus/usb/devices/3-13/power/wakeupĮnable wakeup on port: $ sudo sh -c 'echo "enabled" > /sys/bus/usb/devices/3-13/power/wakeup'Ĭheck if wakeup enabled: $ cat /sys/bus/usb/devices/3-13/power/wakeup : Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |_ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M : Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |_ Port 14: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |_ Port 14: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |_ Port 13: Dev 2, If 0, Class=Vendor Specific Class, Driver=mceusb, 12M This indicates my device is plugged into bus3, port 13. Grep /sys/bus/usb to find the port your device is plugged into: $ grep 5168 /sys/bus/usb/devices/*/idProduct In the above example my device ID is 5168. (Fintek) F71610A or F71612A Consumer Infrared Receiver/Transceiverīus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Instead, enabling wakeup on the USB port my IR device was connected to was was enough.īus 002 Device 002: ID 8087:8001 Intel Corp.īus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 001 Device 002: ID 8087:8009 Intel Corp.īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 003 Device 003: ID 13ba:0018 PCPlay Barcode PCP-BCG4209īus 003 Device 002: ID 1934:5168 Feature Integration Technology Inc. In the end, however, despite many solutions suggesting this was required I did not need to enable USBs in ACPI. I had the same problem and was also stumped by my USBs not appearing in /proc/acpi/wakeup. I can copy from browser to xterm using Shift Insert, and can copy from one xterm to another xterm screen using control shift c and Shift Insert.
0 Comments
Leave a Reply. |