GUI Bugs

I just got a FLIRC and updated, via the GUI, to v4.3 of the firmware. I then attempted to use the SDK available on GITHUB, Darwin version (libflirc.dylib.1), and received the following error to a fl_open_device(0x20A0, "flirc.tv") attempt: [D] lib/libflirc/flirc_driver.c determine_iface(226): unsupported fw v:4.3 Is the SDK out of date or perhaps some other issue? Thanks!

I just got a brand new FLIRC (the new with the metal case) and wanted to configure it (on Windows 10) I downloaded and installed the latest version 2.6.4. After successful installation the GUI detected the FLIRC and offered a firmware upgrade which I accepted. I suppose something went wrong here, cause it then showed "Invalid Device SKU". Everytime I now start the GUI it first shows "upgrading firmware" and then again "Invalid Device SKU". Any idea, what the problem is here? The Device Log shows nothing and the "Advanced" dialog is just gray. I also tried on Windows 7 and MacOS with exactly the same results. Please let me know, if you need more information …

I think this piece of hardware is very useful, and has a very good work behind, but today you're going to hate me a little more :-) I found some bugs in version 3.0.29 aswell in version 3.1.0 (using Windows) I have some suggestions too, to try to improve the behaviour of this little device. I will put them on the appropiate thread, later. flirc_util.exe bugs. Tested versions: flirc_util version v3.0.29 [v3.0.29] Firmware: v4.2.2 [0x5384F860] flirc_util version v3.1.0 [v3.1.0] Firmware: v4.2.2 [0x5384F860] - delete_index : does not work at all. It does not delete any command indexes shown by option "keys" or "…

Flirc has just updated GUI for Windows to version 3.1.0 in web. Downloaded and installed, and the GUI when running is 3.0.29. If checked via web for updates, it finds 3.1.0 and updates again. It downloads and installs, and the GUI keeps on 3.0.29, so it keeps saying that there's a new version (3.1.0), again, and again, and again...

hi, i just updated to the 2.3.9 package and noticed an extra generic man page being included in /usr/share/doc/flirc/Flirc.1. please see attached image of the formatted/rendered man page. seems a generic bit unintentionally included in the package. thanks, -matt

When Flirc is not connected, the program freezes every 1 second probably because its constantly checking if Flirc is connected. Can't you just have it search all the usb devices on startup then check only when new ones a plugged in to increase the speed? I was trying to demo to my friends what the software is like but i can't because it runs like it has cancer when the dongle is not plugged in.

Hello! I was unable to program a working power on button with my Flirc-SE. Using latest Windows 10 and Flirc GUI the software gave me the thumbs up and the button was bound because i was unable to assign it a second time, but pressing the button did not start the pc. After i changed the OS to LibreElec (latest stable Kodi 16.1) i installed the XBMC Flirc addon 1.0.3 and again, thumbs up after i programmed a second power on button but the PC did not boot using it. I did resolve this problem by using the flirc_cli still running LibreElec, did program a 3rd power on button with it and (only) this power on button does work. Also funny: running LibreElec and Kodi 16.1 i did pr…

Just updated to the most recent version (2.2.1). Now all my advanced settings are greyed out, and can't be changed. Tried to run as admin, tried to disconnect the device, and reconnect, tried restarting windows, tried reinstalling software. None of these things worked. I'm on windows 10.

I'd like to download v1.4.4 of Flirc, as v2.0.1 crashes immediately on my Windows 10 64-bit with the old model (clear plastic) of Flirc.

Just installed de Flirc SE edition in my HTPC running Windows 10. I downloaded and installed the latest installation software. In the Devicemanager under "libusbK USB Devices" there is a "flirc bootloader" visible, so the installation looks OK. However when starting the Flirc GUI the application appears, immediately followed by the message "Flirc.exe has stopped working. Windows is checking for a solution of the problem", and again immediately followed by a message "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available". The only button showing is "Close program", and when pressing this button bot…

As title says, I can't correctly map volume down key on ny remote. On notepade shows flirc mapped " ' " instead " - " key.

Hi, just tested Flirc 1.1.3 on a MacBook Pro (Mavericks), and the flirc_util command line utility fails to work as it tries to find a non-existent /usr/local/lib/libusb-1.0.0.dylib. It works (or at least it launches) if I copy libusb-1.0.0.dylib from Frameworks to /usr/local/lib, but if there's a way to make flirc_util find it in the app, that would eliminate one manual step (plus some confusion). Thanks, Ere

I just received the flirc today. Plugged it into my PC - running Win 10 Home x64 - and it showed up as an unrecognized device. Downloaded the gui and while that seemed to install ok, it showed my device was not attached. Tried deleting the device and plugging it back in, but same thing - device unrecognized. I tried updating the device driver and choosing both inf files from the installed driver directory, but that wouldn't work either. Finally I manually ran installer_x64.exe (or was it wdi-simple-64.exe - darn, I don't recall) as admin and then the device was recognized. So, my problems are solved but thought I'd let you know something isn't quite right with the install…

On a high dpi display, the gui is half sized (or original size), but the text is the size it should be... so the firmware version is not readable, and the instruction text is cut off. I could not attach a screenshot for some reason, so i put it on pasteall. http://www.pasteall.org/pic/88208

I've got a brand new flirc usb dongle (arrived yesterday). I connected it, downloaded the application, updated the firmware per Flirc's blog, and now the software crashes on launch. I tried manually updating the firmware as recommended in the sticky note of the firmware forum. That didn't fix it. http://blog.flirc.tv/library-version-history/ I uninstalled the driver and application completely, rebooted, and reinstalled. That didn't fix it. My brand new flirc is dead. Is there a fix, or do I just need to return it for a refund and find some other IR receiver?

OS: OSX El Capitan GUI: 1.4.2 Firmware: 3.7 Each time I open the GUI or plugin the flirc I'm prompted to upgrade the firmware. The blue bar at the top proceeds and the GUI shows blootldr 2.1, then the process exits with a message that it was successful when the firmware version still shows 3.7 I tried a forced upgrade, the dialog shows 3.8 is available but the same issue still occurs. Wondering what to try next.

Starting Flirc on my Ubuntu 14.04 32bit machine Segfaults Here is the output from running 'strace Flirc' munmap(0xb37bd000, 4096) = 0 open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 21 fstat64(21, {st_mode=S_IFREG|0644, st_size=121489, ...}) = 0 mmap2(NULL, 121489, PROT_READ, MAP_PRIVATE, 21, 0) = 0xb2922000 close(21) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/i386-linux-gnu/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = 21 read(21, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\16\0\0004\0\0\0"..., 512) = 512 fstat64(21, {st_mode=S_IFREG|0644, st_size=30560, ...}) =…

Just downloaded and installed today's version of the Windows software for the GUI. Plugged the flirc device into a USB 2 slot and it was recognized and drivers installed. Shows up as a Device and as a "libusbK USB device" in Device Manager. Yet, launching the GUI leads to a BSOD "Bad_Pool_Header" and a hard reboot. Would love to get a little further into using this thing. Thanks, Steve

Hello, I used to have a 1.2.6 (pretty sure) version and everything worked perfectly. I updated (sudo apt-get upgrade flirc) to latest 1.3.6 and GUI doesn't want to load. If I try to start it through command line, I get "Flirc: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory" I installed libusb (sudo apt-get install libusb-1.0-0-dev) and it didn't solve the problem. Please help! Need to map new remote. Thank you,

Hello, I've just received my third FLIRC with Firmware 3.6. When I tried to program it it acts like the keys are being programmed but when I tried using it with my remote, none of the keys worked. I am using an Hauppaug 45 button remote. I took the remote to a set already working and confirmed the remote worked with a FLIRC I already have. I then decided to upgrade the working FLIRC (my mistake) and now it does the same thing, acts like it;s programming but nothing happens. Hopefully the two devices can be "unbricked"

Hi, I've got a problem where the mac application advised me to update a while back, of which I did to v1.3.6. Unfortunately in doing so, it no longer connects to my flirc unit, which is running near original beta firmware from memory - app reports its running v153.0 - though marked as disconnected. I have tried contacting the help email previously, though received no response. Can someone point me to an archive section with older app / firmware so I can get this unit firmware back up to current specs and have the app see the device once again! Looks like all older stuff gets removed stable releases come about. Any help greatly appreciated. Thanks, Doug

I hace a rpm versión of flirc v 1.2.6 in fedora and a firmware v 1.3.6. When I start the gui, they say that the firmware is not compatible, and suggest upgrade the firmware. I try to upgrade the firmware un windows, but they say that last firmware versión is 3.6.

This is terribly frustrating. I am able to record keys, but only if I press the button requested VERY QUICKLY. I was able to get the arrow keys and enter before failing to program 'back'. Adding configuration for other keys is unbelievably annoying, since 80% of the time it says 'Operation timed-out' before I can hit the correct key. I'm using the Flirc dongle, I'm on OpenElec + Kodi, using the XBMC plugin from your repository, and programming with an INT-422-1 Inteset remote.

I ordered flirc because I've heard a lot of positive things about it. Got it today. Unfortunately I'm having many issues. First, flirc software (1.3.6) asks to connect flirc despite the fact that flirc is connected. I tried it on two different pc's and in several usb ports. I installed flirc as admin. Win 7 (64) says that there's something wrong with the drivers. See jpegs below. and motherboards of my two pc's are asrock h77m and asus p5q pro. I updated the usb drivers of asrock motherboard but that didn't do the trick. Despite of those issues, flirc dongle seems to be receiving data since I can control kodi with harmony remote. I have harmony ult…

I have been attempting to install drivers for my device and have not been able to get it resolved. I have tried the Manual Installation which failed saying there is an error. I have also tried using the Zadig installation process, but they always ends with an error message saying 'Driver installation cancelled by user.' even though I did not cancel. I have continually made sure that I am running all programs 'as Administrator' and disabled my AV. Without the driver, I can't update the firmware and I can't program the device. I have tried all the USB ports on my computer. Any additional help or advice would be helpful. I am running Windows 8.1. J