![]() ![]() I tend to agree that a GPIO IR receiver is the preferred way of using a remote with a Pi / Pi 2 - not only are they cheap they are very flexible in that they will work with practically any remote, and even if there isn’t already a profile for the remote you can learn it with irrecord. To find out we would need a full set of debug logs when the receiver is plugged in. If the remote doesn’t work at all this most likely means there is no udev rule matching the USB ID of the receiver, thus eventlircd doesn’t get called into play. USB receivers would typically be recognised directly by the kernel and then depending on udev rules will be sent to eventlircd to handle and then forwarded on to kodi. lib/libflirc/common/flirc_libusb.c _fl_open_libusb_btldr(76): Bootloader v2 not found: PID: 0x0002įlirc symptoms.Typically a USB receiver (especially if the remote emulates a keyboard with “mediacenter” buttons) will not go through lircd - therefore the setting in the My OSMC remotes section will do absolutely nothing, as it only configures lircd profiles. lib/libtransport/transport.c dev_open(80): no device found lib/libflirc/common/flirc_libusb.c fl_open_libusb(147): trying to open bootloader device lib/libflirc/common/flirc_transport.c fl_open_hid(136): no device found lib/libflirc/common/flirc_transport.c _fl_open_libhid_app(94): no hid device found lib/libtransport/hid.c hid_dev_open(330): Device 20A0:6 not found lib/libflirc/common/flirc_transport.c _fl_open_libhid_app(92): trying to open 0x20A0, 0x0006 lib/libflirc/common/flirc_transport.c fl_open_hid(130): trying to open main device lib/libflirc/common/flirc_transport.c _fl_open_libhid_btldr(56): no hid device found lib/libtransport/transport.c dev_open(88): no device found lib/libtransport/hid.c hid_dev_open(330): Device 20A0:5 not found lib/libflirc/common/flirc_transport.c fl_open_hid(124): trying to open bootloader device gui/Flirc/src/mainwindow.cpp checkHardwareStatus(335): checking status Gui/Flirc/src/mainwindow.cpp display_fw_version(307): no device connected gui/Flirc/src/device_log.cpp update_fields(139): updating fields, present: 0 gui/Flirc/src/advanced_window.cpp update_fields(296): disabling all the menus gui/Flirc/src/mainwindow.cpp device_disconnected(268): Device disconnected gui/Flirc/src/mainwindow.cpp stopCurrentOperation(1375): got to the end lib/libflirc/flirc_driver.c fl_get_sku(1443): pointer to handle is invalidn gui/Flirc/src/mainwindow.cpp stopCurrentOperation(1361): stopping current operation gui/Flirc/src/main.cpp main(222): Operating System: Windows gui/Flirc/src/main.cpp main(221): flirc_util version v3.20.4 gui/Flirc/src/main.cpp main(218): -START OF MAIN. On the flirc log I can see some errors here, namely about a bootloader which i don't see defined anywhere: ![]() I've reinstalled the drivers at least three times. I've also tried Zadig to set the driver to libsublk as I find written on the support pages, all to no avail. I've downloaded the latest application from and ran as Administrator. Flirc is still working but the GUI is not. I'm using Windows 10 Professional after I've upgraded from Windows 7 Professional where all was fine. I have Flirc SE and my GUI also says Disconnected.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |