Search the Community

There are two issues. One is a new feature on amazon's firetv. They added a feature for long press to get up another menu. I've tried to get in touch with Amazon for over a year, their team disbanded, and I'm trying to make a new contact. I got in touch with someone from another department last week, and they are trying to put me in touch with someone. I don't have a timeline for that because I don't know what the issue is. I need Amazon's assistance. The second issue is a new firmware feature long presses. Which will allow you to assign another button to an existing signal. Press the button quickly, get one command, long press it, get another. That's a firmware feature that will come on the new hardware and a release will most likely be ready before the end of the year. I've done a lot this year, and I've had regular blog updates that talk about my accomplishments. I even have a new status board page to create transparency: https://flirc.tv/status_board If I miss something, take @hamptonhills approach, be nice about it. But I work 7 days a week, and can't afford to hire someone. I do the best I can, being an asshole about it doesn't help anyone.

I also tried on Linux now, and this is the output of the GUI during attempted firmware upgrade: fabian@gauss ~ $ Flirc Can't load 'test.ini' [DEVICE] Uploading [D] lib/libflirc/bootloader/bl_3.3.c fl_ver_upload_fw(387): invalid image, incorrect sku [D] lib/libflirc/bootloader/bl_3.3.c fl_ver_upload_fw(388): File Device [D] lib/libflirc/bootloader/bl_3.3.c fl_ver_upload_fw(389): ---- ------ [D] lib/libflirc/bootloader/bl_3.3.c fl_ver_upload_fw(390): Flirc 2.0 [dori] Flirc 2.0 [dorir [D] lib/libtransport/transport.c _dev_send_cmd(243): Command error: 128 [D] lib/libflirc/bootloader/bl_3.3.c bootloader_enter_app(197): Image CRC mismatched [D] lib/libflirc/flirc_driver.c fl_upgrade_fw_ext(1087): upload firmware failed [D] lib/libflirc/flirc_driver.c fl_major_version(391): something bad happened [D] lib/libflirc/flirc_driver.c fl_minor_version(381): something bad happened [D] lib/libflirc/flirc_driver.c fl_patch_version(401): something bad happened [D] lib/libflirc/flirc_driver.c fl_major_version(391): something bad happened [D] lib/libflirc/flirc_driver.c fl_minor_version(381): something bad happened [D] lib/libflirc/flirc_driver.c fl_patch_version(401): something bad happened It appears, that somehow the Device responds with "Flirc 2.0 [dorir" instead of the expected "Flirc 2.0 [dori]". Strange... fabian@gauss ~ $ flirc_util sku product sku: Flirc 2.0 [dorir

Dear Developer, because I can not found a solution to use my FlircSe receiver to switch on/off from S5 Mode and I can not found a answert in "General Questions". I think it is possible Streacom FlircSE Hardware has problem whis some Hardware. For my new HTPC I board last week 2 new Mainboard whis Intel Z270 base Chipset. The Mainboard has SGX (Software Guide Extension) switch on. When I try to configurate my Flirc SE receiver for switch FlircSE from S5 mode to Switch On, it will not work. My old Hardware "AMD FM2 " I had not problem to configurat the S5 Mode. Whis the new Hardware I have following problem when I will determine the Power On/Off Button for S5 Mode. When I open the command interface programm and start "flirc_util.exe" whis Software" Flirc Software 1.35 RC2" whis following proceed. I can not configurate the S5 Shutdown and start Function and I got the following "Error" messages and is does not work: Example: ------------------------------------------------------------------ Flirc Version 1.35 RC2, firmware 3,60 ------------------------------------------------------------------ Microsoft Windows [Version 10.0.15063.250] -----------------------------------------------> Home Version x64 (c) 2017 Microsoft Corporation. Alle Rechte vorbehalten. C:\Windows\system32>cd C:\Program Files (x86)\flirc flirc_util.exe record power Then I got the following Information from "flirc_util.exe" Warning: cannot open USB device Press any button on the remote to link it with 'power' When I now press the "Power Button" on my Remote control "flirc_util.exe" give me the message Succesfully recorded button and the "Power On/ off " funktion will not work :-( ------------------------------------------------------------------------- Flirc Version 2,39/2.60-> Firmware 3,9 -------------------------------------------------------------------------- The problem is Equel: Operation System is: _____________________ Microsoft Windows [Version 10.0.15063.250] -----------------------------------------------> Home Version x64 (c) 2017 Microsoft Corporation. Alle Rechte vorbehalten. C:\Windows\system32>cd C:\Program Files (x86)\flirc C:\Program Files (x86)\Flirc>flirc_util.exe record power [D] lib/libtransport/libusb.c libusb_dev_open(143): can't open usb device Press any button on the remote to link it with 'power' Succesfully recorded button My question is now: - Give it currently problems whis "Intel" based Mainboard whis Z270 Chipsat that not work whis FlircSE Remote controls? - What is the reason for the Information Warning: cannot open USB device Press any button on the remote to link it with 'power' - >all other Remote function currendly work well - What can I do to fix the problem? Please help me by this problem. I am not shure what is the problem because on my old HTPC Flirc works fine. Best regards, Edited Thursday at 04:26 AM by MediaCenterOwner

Hi; Thanks for the great help around here. I have tried to setup Flirc and my Harmony One without success. I have read many installation procedures and I am confused. I have programmed FLIRC with keyboard layout but keys needed to be pressed twice to work, and even though the delay to execution was huge (so I canned that one). Next, I programmed MCE Keyboard and MCPC in the remote and linked them with an action to launch XBMC automatically using WIN-7 command and then use the keyboard layout i programmed. That did not work either... WISH LIST: Have XBMC as a command in remote When pressed a) I need TV on and HDMI 3 selected B) XBMC launched on the PC then control from there with a keyboard layout. ASSUMPTION: A second TV profile would not work since I need my TV to switch to HDMI 3 and so on... is this correct? I realize that this list might be a bit pretentious but I would like the convenience this offers. QUESTIONS Is this possible to do If yes, what is the best way to program it Thanks in advance

Let me ask again! Any idea why the LG TV Remote (not the harmony) turns on the tv AND the htpc if flirc is plugged in ? Yes the flirc has learned the power off command from its flirc and kodi device in myharmony. Isn´t it strange?

https://flirc.gitbooks.io/flirc-instructions/content/command-line-interface-guide/location.html This will put it in your path so you don't need to go into the applications directory. cd /Applications/Flirc.app/Contents/Resources/flirc_util cp flirc_util /usr/local/bin/ flirc_util settings Also, make sure the GUI is closed. Can't open it with the cli and the gui at the same time.

I feel so dumb. Sorry to trouble you with this stuff. I *used to be* a programmer, but the older I get the more I forget! I got the program to run, but this is what I see ... Kens-2015-iMac:Applications kenjacobs2$ ./flirc_util -version device disconnected, can't run command ????

Thanks for the explanation. I guess I understand now. as to Flirc_util, I did a Show Package Contents and successfully opened the Flirc_util executable from Finder. And when I do it shows the Help info. But I can't seem to figure out how to actually run the utility itself from the command line. Thanks again!

@Park City Ken Flirc doesn't keep the information about the controller used when recording a button. Most controllers are just layers on top of the full keyboard controller - keys on them are just predefined keyboard shortcuts. For example, on Kodi controller, the Info key is just the "i" key on the keyboard. So most of the time, only information that can be displayed is a keyboard key combination assigned, not a specific controller function. The hex codes which are used by Flirc won't tell you anything useful. They are generated from IR signal using a proprietary hashing algorithm and are Flirc specific. You wouldn't be able to copy IR hex codes from some remote control related forums or websites and enter them into Flirc without having actual remote. Also at this moment there's no option to add a key with IR hash manually at all. You need the remote to do it. Regarding the flirc_util, to run specific command you call it like this: flirc_util keys

I made the same suggestion today, before finding this forum. Sorry for the duplication. I like the idea of highlighting buttons that have codes. Even though you can't display the user-sensible key easily, the hex code would be helpful. I'd use a right-click to retrieve or store the HEX code for any given button in the GUI. Sometimes I don't have the remote, or I'm copying codes obtained from elsewhere, like Global Cache's Control Tower. As long as I'm at it ... it would be handy if the Flirc menu had an option to "Save Configuration in Display Mode" (or some such). It would produce a user-readable file, with the name of the controller, the name of each button that had a code (since it knows both while in the GUI, I assume), and the associated hex code. By the way, I tried to run flirc_util on Mac Sierra, and never figured out how to do so. It runs, and automatically shows the help, but I can't find a way to submit command-line (Terminal) commands to the utility. Thanks for a VERY cool little tool.

for my new HTPC I Board last week 2 new Mainboard whis Intel Z270 base Chipset. The Mainboard has SGX (Software Guide Extension) switch on. Whisout SGX I have not tryed becaus I need this Function. When I try to configurate my Flirc SE receiver I will not work. My old Hardware "AMD FM2 " Hardware I have not problem to configurat the S5 Mode after I know the way. Whis the new Hardware I have following problem when I will determine the Power On/Off Button for S5 Mode. When I open the command interface programm and start "flirc_util.exe" whis Software" Flirc Software 1.35 RC2" whis following proceed. I can not configurate the S5 Shutdown and start Function and I got the following "Error" messages and is does not work: Example: ------------------------------------------------------------------ Flirc Version 1.35 RC2, firmware 3,60 ------------------------------------------------------------------ Microsoft Windows [Version 10.0.15063.250] -----------------------------------------------> Home Version x64 (c) 2017 Microsoft Corporation. Alle Rechte vorbehalten. C:\Windows\system32>cd C:\Program Files (x86)\flirc flirc_util.exe record power Then I got the following Information from "flirc_util.exe" Warning: cannot open USB device Press any button on the remote to link it with 'power' When I now press the "Power Button" on my Remote control "flirc_util.exe" give me the message Succesfully recorded button and the "Power On/ off " funktion will not work :-( ------------------------------------------------------------------------- Flirc Version 2,39/2.60-> Firmware 3,9 -------------------------------------------------------------------------- The problem is Equel: Operation System is: _____________________ Microsoft Windows [Version 10.0.15063.250] -----------------------------------------------> Home Version x64 (c) 2017 Microsoft Corporation. Alle Rechte vorbehalten. C:\Windows\system32>cd C:\Program Files (x86)\flirc C:\Program Files (x86)\Flirc>flirc_util.exe record power [D] lib/libtransport/libusb.c libusb_dev_open(143): can't open usb device Press any button on the remote to link it with 'power' Succesfully recorded button My question is now: - Give it currently problems whis "Intel" based Mainboard whis Z270 Chipsat that not work whis FlircSE Remote controls? - What is the reason for the Information Warning: cannot open USB device Press any button on the remote to link it with 'power' - >all other Remote function currendly work well - What can I do to fix the problem? Please help me by this problem. I am not shure what is the problem because on my old HTPC Flirc works fine. Best regards,

@yawor is correct. There are a list of tables built into flirc. They don't ever get deleted. If you disable them, they get passed over when searching for a stored command. You can record 'over' them basically by re-assigning these keys into the user area. If the key exists in the user area, it uses this over the built in table. Yes, I need to work with logitech to add stuff. They are pretty good if something is missing or needs correcting.

Hi, I've just purchased a Flirc and should be receiving it today. I've tried searching for the answer but couldn't find it. Does Flirc have the ability to learn a remote command (via Harmony) and assign it to a keyboard key, in turn assigning it to the Flirc itself?

Selecting profiles in the advanced section is very new since it appeared only recently. Excuse me to maybe being more detailed but i want to understand fully the concept and iam sure a lot of other users, too. So that means if i select a profile under the advanced section flirc clears the configuration and loads a keyboard defintion for example matching the kodi layout. OK but what does it to the keys not defined in the kodi layout of flirc? Kodi has some keyboard macros to control lets say full screen in the pvr part (Key H) which is not part of flircs kodi defintion. So thats why i have chosen the Microsoft Keyboard Controller to learn that key to flirc. The Flirc definition inside logitech harmony is a super feature. Only thing here is that it is missing most of the keyboard keys for example H, I, J, K and so on which are in use by kodi or can be used. Learning 50 keys was simply to much.... So thats why i avoided the flirc definition here as well and only learned the power off command from there.

Ok. I try this. Does Flirc recognizes this command? My Shield is hidden ;)

Hi! I am thinking to purchase the flirc remote but before i do this i have a few questions. I will use flirc with XBMC build around minumal ubuntu (no GUI fo OS). 1. So what i am interested in is if flirc can execute the script .sh if XBMC freezes. So something like 'irexec' which is a seperate deamon in lunux which listens for command. So basically even if XBMC freezes you can still execute f.e. reboot.sh command to restart the HTPC not dependent on XBMC. 2. Can flirc be programmed on windows and then be used on linux? tnx

The dmesg is pasted below, is there any way to do the ir debug from the CLI? I don't have X on this machine and I don't think it's realistically possible to get it up and running on openelec... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.30 (stephan@buildserver.openelec.tv) (gcc version 6.3.0 (GCC) ) #1 SMP Mon May 29 09:51:09 CEST 2017 [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt:Machine model: Raspberry Pi 3 Model B Rev 1.2 [ 0.000000] cma: Reserved 8 MiB at 0x2e400000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] On node 0 totalpages: 192512 [ 0.000000] free_area_init_node: node 0, pgdat 80c34400, node_mem_map ade20000 [ 0.000000] Normal zone: 1504 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 192512 pages, LIFO batch:31 [ 0.000000] percpu: Embedded 14 pages/cpu @aefa7000 s25804 r8192 d23348 u57344 [ 0.000000] pcpu-alloc: s25804 r8192 d23348 u57344 alloc=14*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 191008 [ 0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1360 bcm2708_fb.fbheight=768 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet root=/dev/ram0 rdinit=/init BOOT_IMAGE=/kernel.img usbcore.autosuspend=-1 [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 742728K/770048K available (7168K kernel code, 212K rwdata, 1408K rodata, 2048K init, 490K bss, 19128K reserved, 8192K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xaf800000 - 0xff800000 (1280 MB) [ 0.000000] lowmem : 0x80000000 - 0xaf000000 ( 752 MB) [ 0.000000] modules : 0x7f000000 - 0x80000000 ( 16 MB) [ 0.000000] .text : 0x80008000 - 0x80800000 (8160 kB) [ 0.000000] .init : 0x80a00000 - 0x80c00000 (2048 kB) [ 0.000000] .data : 0x80c00000 - 0x80c35080 ( 213 kB) [ 0.000000] .bss : 0x80c37000 - 0x80cb1910 ( 491 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 32. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns [ 0.000008] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns [ 0.000020] Switching to timer-based delay loop, resolution 52ns [ 0.000286] Console: colour dummy device 80x30 [ 0.000306] console [tty0] enabled [ 0.000328] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.00 BogoMIPS (lpj=64000) [ 0.000342] pid_max: default: 32768 minimum: 301 [ 0.000472] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000480] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001356] Disabling cpuset control group subsystem [ 0.001429] CPU: Testing write buffer coherency: ok [ 0.001878] CPU0: update cpu_capacity 1024 [ 0.001886] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.001937] Setting up static identity map for 0x100000 - 0x100034 [ 0.003993] CPU1: update cpu_capacity 1024 [ 0.004002] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.004668] CPU2: update cpu_capacity 1024 [ 0.004675] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.005276] CPU3: update cpu_capacity 1024 [ 0.005283] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.005360] Brought up 4 CPUs [ 0.005370] SMP: Total of 4 processors activated (153.00 BogoMIPS). [ 0.005375] CPU: All CPU(s) started in HYP mode. [ 0.005378] CPU: Virtualization extensions available. [ 0.005977] devtmpfs: initialized [ 0.016416] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 [ 0.016680] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns [ 0.016697] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.017221] xor: measuring software checksum speed [ 0.050049] arm4regs : 922.800 MB/sec [ 0.083456] 8regs : 562.800 MB/sec [ 0.116858] 32regs : 685.200 MB/sec [ 0.150270] neon : 550.800 MB/sec [ 0.150276] xor: using function: arm4regs (922.800 MB/sec) [ 0.150287] pinctrl core: initialized pinctrl subsystem [ 0.151223] NET: Registered protocol family 16 [ 0.153344] DMA: preallocated 1024 KiB pool for atomic coherent allocations [ 0.170343] cpuidle: using governor ladder [ 0.183710] cpuidle: using governor menu [ 0.184290] Serial: AMBA PL011 UART driver [ 0.186026] bcm2835-mbox 3f00b880.mailbox: mailbox enabled [ 0.186508] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe [ 0.294598] raid6: int32x1 gen() 96 MB/s [ 0.351117] raid6: int32x1 xor() 73 MB/s [ 0.408041] raid6: int32x2 gen() 116 MB/s [ 0.464720] raid6: int32x2 xor() 93 MB/s [ 0.521976] raid6: int32x4 gen() 114 MB/s [ 0.578389] raid6: int32x4 xor() 78 MB/s [ 0.635540] raid6: int32x8 gen() 101 MB/s [ 0.692421] raid6: int32x8 xor() 71 MB/s [ 0.749057] raid6: neonx1 gen() 348 MB/s [ 0.805886] raid6: neonx1 xor() 315 MB/s [ 0.862657] raid6: neonx2 gen() 546 MB/s [ 0.919497] raid6: neonx2 xor() 433 MB/s [ 0.976400] raid6: neonx4 gen() 633 MB/s [ 1.033248] raid6: neonx4 xor() 476 MB/s [ 1.090057] raid6: neonx8 gen() 386 MB/s [ 1.147008] raid6: neonx8 xor() 288 MB/s [ 1.147013] raid6: using algorithm neonx4 gen() 633 MB/s [ 1.147017] raid6: .... xor() 476 MB/s, rmw enabled [ 1.147021] raid6: using intx1 recovery algorithm [ 1.147176] bcm2835-dma 3f007000.dma: DMA legacy API manager at af80f000, dmachans=0x1 [ 1.149495] SCSI subsystem initialized [ 1.149779] usbcore: registered new interface driver usbfs [ 1.149852] usbcore: registered new interface driver hub [ 1.149936] usbcore: registered new device driver usb [ 1.153634] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-05-15 17:01 [ 1.153741] Advanced Linux Sound Architecture Driver Initialized. [ 1.155265] clocksource: Switched to clocksource arch_sys_counter [ 1.155514] FS-Cache: Loaded [ 1.166949] NET: Registered protocol family 2 [ 1.167773] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 1.167895] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 1.168079] TCP: Hash tables configured (established 8192 bind 8192) [ 1.168165] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 1.168207] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 1.168406] NET: Registered protocol family 1 [ 1.168781] RPC: Registered named UNIX socket transport module. [ 1.168786] RPC: Registered udp transport module. [ 1.168790] RPC: Registered tcp transport module. [ 1.168795] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.280720] workingset: timestamp_bits=30 max_order=18 bucket_order=0 [ 1.293437] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 1.293872] FS-Cache: Netfs 'nfs' registered for caching [ 1.294502] NFS: Registering the id_resolver key type [ 1.294525] Key type id_resolver registered [ 1.294529] Key type id_legacy registered [ 1.294545] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 1.299364] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 1.299373] io scheduler noop registered (default) [ 1.299379] io scheduler deadline registered [ 1.299409] io scheduler cfq registered [ 1.305208] BCM2708FB: allocated DMA memory ee510000 [ 1.305242] BCM2708FB: allocated DMA channel 0 @ af80f000 [ 1.338075] Console: switching to colour frame buffer device 170x48 [ 1.358750] bcm2835-rng 3f104000.rng: hwrng registered [ 1.358850] vc-cma: Videocore CMA driver [ 1.358856] vc-cma: vc_cma_base = 0x00000000 [ 1.358861] vc-cma: vc_cma_size = 0x00000000 (0 MiB) [ 1.358866] vc-cma: vc_cma_initial = 0x00000000 (0 MiB) [ 1.359050] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB) [ 1.373000] brd: module loaded [ 1.373159] loop: module loaded [ 1.373443] usbcore: registered new interface driver rtsx_usb [ 1.373659] MACsec IEEE 802.1AE [ 1.374700] libphy: Fixed MDIO Bus: probed [ 1.376007] tun: Universal TUN/TAP device driver, 1.6 [ 1.376012] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [ 1.376324] usbcore: registered new interface driver cdc_ether [ 1.376409] usbcore: registered new interface driver smsc95xx [ 1.376469] usbcore: registered new interface driver net1080 [ 1.376527] usbcore: registered new interface driver cdc_subset [ 1.376585] usbcore: registered new interface driver zaurus [ 1.376675] usbcore: registered new interface driver cdc_ncm [ 1.376703] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.376708] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.376726] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [ 1.602782] Core Release: 2.80a [ 1.602793] Setting default values for core params [ 1.602833] Finished setting default values for core params [ 1.803211] Using Buffer DMA mode [ 1.803216] Periodic Transfer Interrupt Enhancement - disabled [ 1.803220] Multiprocessor Interrupt Enhancement - disabled [ 1.803226] OTG VER PARAM: 0, OTG VER FLAG: 0 [ 1.803240] Dedicated Tx FIFOs mode [ 1.803581] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xae504000 dma = 0xee504000 len=9024 [ 1.803606] FIQ FSM acceleration enabled for : [ 1.803606] Non-periodic Split Transactions [ 1.803606] Periodic Split Transactions [ 1.803606] High-Speed Isochronous Endpoints [ 1.803606] Interrupt/Control Split Transaction hack enabled [ 1.803613] dwc_otg: Microframe scheduler enabled [ 1.803661] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8055dc88 [ 1.803670] WARN::hcd_init_fiq:460: FIQ ASM at 0x8055dfac length 36 [ 1.803681] WARN::hcd_init_fiq:486: MPHI regs_base at 0xaf878000 [ 1.803736] dwc_otg 3f980000.usb: DWC OTG Controller [ 1.803772] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 [ 1.803805] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000 [ 1.803850] Init: Port Power? op_state=1 [ 1.803854] Init: Power Port (0) [ 1.804028] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.804039] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.804048] usb usb1: Product: DWC OTG Controller [ 1.804056] usb usb1: Manufacturer: Linux 4.9.30 dwc_otg_hcd [ 1.804064] usb usb1: SerialNumber: 3f980000.usb [ 1.804800] hub 1-0:1.0: USB hub found [ 1.804836] hub 1-0:1.0: 1 port detected [ 1.805562] dwc_otg: FIQ enabled [ 1.805566] dwc_otg: NAK holdoff enabled [ 1.805570] dwc_otg: FIQ split-transaction FSM enabled [ 1.805583] Module dwc_common_port init [ 1.805799] usbcore: registered new interface driver usb-storage [ 1.805935] usbcore: registered new interface driver usbserial [ 1.805987] usbcore: registered new interface driver usbserial_generic [ 1.806038] usbserial: USB Serial support registered for generic [ 1.807107] mousedev: PS/2 mouse device common for all mice [ 1.807402] i2c /dev entries driver [ 1.808655] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer [ 1.808912] bcm2835-cpufreq: min=600000 max=1200000 [ 1.809358] sdhci: Secure Digital Host Controller Interface driver [ 1.809361] sdhci: Copyright(c) Pierre Ossman [ 1.809656] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe [ 1.811850] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe [ 1.812027] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.823161] ledtrig-cpu: registered to indicate activity on CPUs [ 1.823257] hidraw: raw HID events driver (C) Jiri Kosina [ 1.824237] usbcore: registered new interface driver usbhid [ 1.824240] usbhid: USB HID core driver [ 1.824673] vchiq: vchiq_init_state: slot_zero = 0xae580000, is_master = 0 [ 1.833086] NET: Registered protocol family 10 [ 1.833669] NET: Registered protocol family 17 [ 1.833720] Key type dns_resolver registered [ 1.833959] Registering SWP/SWPB emulation handler [ 1.835573] Btrfs loaded, crc32c=crc32c-generic, integrity-checker=on [ 1.836126] Key type encrypted registered [ 1.836283] vc-sm: Videocore shared memory driver [ 1.836288] [vc_sm_connected_init]: start [ 1.839437] [vc_sm_connected_init]: end - returning 0 [ 1.843058] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2 [ 1.843929] sdhost: log_buf @ ae507000 (ee507000) [ 1.895276] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) [ 1.897317] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0 [ 1.897322] mmc-bcm2835 3f300000.mmc: DMA channel allocated [ 1.948645] console [netcon0] enabled [ 1.948647] netconsole: network logging started [ 1.948731] of_cfs_init [ 1.948789] of_cfs_init: OK [ 1.948937] ALSA device list: [ 1.948939] No soundcards found. [ 1.952010] Freeing unused kernel memory: 2048K (80a00000 - 80c00000) [ 1.957830] mmc0: host does not support reading read-only switch, assuming write-enable [ 1.960161] mmc0: new high speed SDHC card at address 0007 [ 1.960567] mmcblk0: mmc0:0007 SD8GB 7.47 GiB [ 1.963096] mmcblk0: p1 p2 [ 1.971775] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 1.973315] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.974837] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.977578] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 2.008694] Indeed it is in host mode hprt0 = 00021501 [ 2.020106] random: fast init done [ 2.063426] mmc1: new high speed SDIO card at address 0001 [ 2.181946] usb 1-1: new high-speed USB device number 2 using dwc_otg [ 2.182029] Indeed it is in host mode hprt0 = 00001101 [ 2.372081] usb 1-1: New USB device found, idVendor=0424, idProduct=9514 [ 2.372089] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.372508] hub 1-1:1.0: USB hub found [ 2.372554] hub 1-1:1.0: 5 ports detected [ 2.651937] usb 1-1.1: new high-speed USB device number 3 using dwc_otg [ 2.742066] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00 [ 2.742072] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.744434] smsc95xx v1.0.5 [ 2.793921] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:2e:73:7c [ 2.998604] usb 1-1.2: new full-speed USB device number 4 using dwc_otg [ 3.093280] usb 1-1.2: New USB device found, idVendor=20a0, idProduct=0006 [ 3.093285] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.093291] usb 1-1.2: Product: flirc [ 3.093295] usb 1-1.2: Manufacturer: flirc.tv [ 3.096647] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-3f980000.usb-1.2/input0 [ 3.102516] input: flirc.tv flirc as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.1/0003:20A0:0006.0002/input/input0 [ 3.158839] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-3f980000.usb-1.2/input1 [ 4.268630] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities [ 4.269407] EXT4-fs (mmcblk0p2): couldn't mount as ext2 due to feature incompatibilities [ 4.305924] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 4.721105] systemd[1]: System time before build time, advancing clock. [ 4.741884] systemd[1]: systemd 233 running in system mode. (-PAM -AUDIT -SELINUX -IMA -APPARMOR -SMACK -SYSVINIT -UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL -XZ -LZ4 -SECCOMP +BLKID -ELFUTILS -KMOD -IDN default-hierarchy=hybrid) [ 4.742264] systemd[1]: Detected architecture arm. [ 4.742376] systemd[1]: Running with unpopulated /etc. [ 4.742459] systemd[1]: Set hostname to <OpenELEC>. [ 4.744233] systemd[1]: Initializing machine ID from random generator. [ 4.837862] systemd[1]: Populated /etc with preset unit settings. [ 4.893035] systemd[1]: Created slice User and Session Slice. [ 4.893419] systemd[1]: Listening on RPCbind Server Activation Socket. [ 4.893763] systemd[1]: Created slice System Slice. [ 4.895318] systemd[1]: Mounting Variable Directory... [ 5.137981] fuse init (API version 7.26) [ 5.144634] systemd-journald[192]: Received request to flush runtime journal from PID 1 [ 5.615068] random: crng init done [ 6.247947] Console: switching to colour dummy device 80x30 [ 6.325724] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000 [ 6.806221] usbcore: registered new interface driver brcmfmac [ 7.017503] uart-pl011 3f201000.serial: no DMA platform data [ 7.052168] brcmfmac: Firmware version = wl0: Aug 29 2016 20:48:16 version 7.45.41.26 (r640327) FWID 01-4527cfab [ 7.639956] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup [ 7.666532] 8021q: 802.1Q VLAN Support v1.8 [ 7.777676] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 7.777694] brcmfmac: power management disabled [ 9.235114] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1 [ 11.969904] Bluetooth: Core ver 2.22 [ 11.969967] NET: Registered protocol family 31 [ 11.969970] Bluetooth: HCI device and connection manager initialized [ 11.969983] Bluetooth: HCI socket layer initialized [ 11.969989] Bluetooth: L2CAP socket layer initialized [ 11.970008] Bluetooth: SCO socket layer initialized [ 11.985965] Bluetooth: HCI UART driver ver 2.3 [ 11.985977] Bluetooth: HCI UART protocol H4 registered [ 11.985983] Bluetooth: HCI UART protocol BCSP registered [ 11.985987] Bluetooth: HCI UART protocol LL registered [ 11.985993] Bluetooth: HCI UART protocol ATH3K registered [ 11.985999] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 11.986096] Bluetooth: HCI UART protocol Intel registered [ 11.986160] Bluetooth: HCI UART protocol Broadcom registered [ 11.986163] Bluetooth: HCI UART protocol QCA registered [ 11.986166] Bluetooth: HCI UART protocol AG6XX registered [ 11.986168] Bluetooth: HCI UART protocol Marvell registered

well, I let it sit for a couple hours, and this time wasn't as bad as sometimes (only took maybe 20 secs or so to become fully functional)...but here's the log from this one. I'll let it sit for several more hours and then see if the log looks any different. TV:~/flirc-2.5.6 # ./flirc_util device_log <1>malloc_addblock(49): Heap Block: 0x20001708 - 0x20002FFF (6k) <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges <3>ir_finished(55): too many edges TV:~/flirc-2.5.6 # ./flirc_util settings flirc_util version v2.5.6 [v2.5.6] Firmware: v4.1.5 [0x14C40FA3] Settings: sleep detection: NA noise canceler: NA inter-key delay: NA seq. modifiers: NA variant: Flirc builtin profiles: NA Memory Info: NA [D] lib/libcmds/cmds.c run_cmd(275): could not find command 'sku' Recorded Keys: Index hash IK ID key ----- -------- --- -- --- TV:~/flirc-2.5.6 #

Hey, I 've been using Flirc on my PC to control various media apps like mpc and foobar and it has been working great (mapped as a full keyboard). What I wanted to know is if there is a way to emulate an alt+tab on windows so that I can switch between windows. Mapping alt+tab to a key obviously doesn't work as well as it will emulate both key presses each time, hence there is no sane way to actually select the window you want to switch focus to. I've tried mapping alt and tab to separate keys (by mapping alt via the command line utility) to no avail either. Any ideas? Or perhaps a possible enhancement?

This is a flirc gen2 feature, the feature is done, and I'm doing some final testing on the firmware. You'll need firmware v4.2.x (attached). The SDK is also published here: https://github.com/flirc/sdk/tree/master/cli I'm missing a windows library, I'll be adding that in the next couple of days. It's implemented in a very basic form. Basically with my latest version of software/firmware/device, you can capture the raw signal from a remote, a comma delimited list of edges. The api looks like: flirc_transmit_raw(uint16_t *buf, uint16_t len) My commandline utility has been updated to send a command with the output directly from the GUI. It parses the comma delimited list, puts it into a buffer, and calls the api, which can be seen in the SDK here: https://github.com/flirc/sdk/blob/master/cli/src/cmds/ir_transmit.c An example of the using the commandline: http://cl.flirc.io/lrs8 The transmitter in flirc is not the greatest, you'll need line of sight, and it's limited to about 6-8 feet. The IR LED is only like 2mm big. I'm exploring other options but it'll mean a new hardware update/sku. There is a lot to do with this, but I'll be moving on for the time being for a few other promised features. nemo.release-4.2.0.bin dori.release-4.2.0.bin

OK, I found there is a command line utility in your software package, I thought maybe I can run it in my Kodi box to debug the issue. No go. My Kodi box has no 32-bit support and the executable is 32-bit. Amen. The only OS I can run it on is my VBox Linux Mint. Every freakin' flash utility I've used in my life offers old firmware backup in case the new one has a problem. This is the first case I experience downgrading the firmware is literally denied. Your software, your policies. For me it is time to look for a different solution, methinks. Getting frustrated, yes, sorry.

I don't think that was mean---I did show steps for others to use as a workaround until the repos are fixed. Clearly it's been an issue for some folks for over a year. For what it's worth, I have a close friend who had similar issues with the RPM packages. He told me he had a dialog with you via direct email, where he offered to help re-package your RPMs and fix your repos. You agreed to the help; he said, "OK, what next?" and you never replied. Point is, you did have an opportunity to have a team. I appreciate that you are busy. But my opinion remains: I am completely sympathetic if you don't have time to make the Linux experience as polished and turn-key as on Windows, but you owe it to your customers to advertise accordingly. As a 20-year Linux user I am used to this: with much hardware, Windows support is a given, and Linux support varies from "not at all" to "best-effort" or "community support only". But the way FLIRC is currently advertised, it comes across as Linux support being the same as Windows: you have both deb and rpm repos, and a failsafe distro-independent/statically-linked Linux failsafe program. According to my friend, the RPMs are broken; clearly the apt repos are broken for at least some of us; and the failsafe is not working for me either (see above). Anyway, in your example above you are doing an upgrade, which implies you already have a working flirc package on your system. Can you apt-get remove flirc, then comment out the line in your sources.list file, and then run "apt-get clean"? The latter will clean out your apt/dpkg cache. At this point I believe your system should be in a state similar to what mine is: effectively no knowledge of the flirc software. Now un-comment the line in sources.list, and just run "apt-get update". This command will just refresh the package index/cache. I suspect this should fail the same as it did for me and others in this thread. On the other hand, if it works, then I suspect it is a nuanced difference between various distributions' apt repository requirements. Can you tell me exactly what distribution and version you are using? I am guessing Linux Mint... I'm going to install 18.2 XFCE 64bit in a virtual machine and see if the repo works for me. Edit: I just did a fresh install of Linux Mint 18.2 XFCE 64bit. I added "deb http://apt.flirc.tv/arch/x64 binary/" to my /etc/apt/sources.list file. When I ran "apt-get update", I got the same error I posted above. I now have more confidence that if you do as I suggested above (remove flirc, remove flirc repo, clean your apt cache, then re-add the repo), you'll be able to reproduce this.

That happened to me on the first Flirc I used, but programming it from the command line on a Linux system seemed to help (although in the end it did turn out that my first Flirc was faulty). I don't know if you've got a Linux box to test from or woud like to try testing from Windows command prompt, but it may help isolate the problem.

I'm using Flirc with a Sharp Aquos. I've disabled the FireTV's CEC support, so it shouldn't be getting a press from that. However, every time I press left or right (unless I'm extremely gentle), I get two presses instead of one in that it moves two to the left, two to the right. The advanced section of the GUI is grayed out and everything is disabled. I set the interkey delay via the command line, but the change isn't persistent or doesn't appear at all: flirc_util version v2.3.9 [v2.3.9] Firmware: v4.0.24 [0x80CA1DDF] Settings: sleep detection: NA noise canceler: NA inter-key delay: NA seq. modifiers: NA variant: Flirc builtin profiles: NA Memory Info: NA Recorded Keys: Index hash ID key ----- -------- -- --- 0 01DE8DAD 04 right_shift ! 1 C417B814 04 right_cmd ! 2 D90898D4 01 up 3 417CC92D 01 right 4 A7684222 01 down 5 2F05736D 01 left 6 E72C4D7B 02 left_ctrl+left_alt+left_cmd+right_alt+right_cmd ! 7 7F40EE94 02 left_ctrl+left_shift+right_ctrl+right_shift+right_cmd ! 8 1453333B 02 left_alt+right_ctrl+right_shift+right_cmd ! 9 A76299ED 01 ! 10 21D7FE21 01 ! Any ideas?

Hmm...but disabling HDMI CEC on both the TV and the FireTV should prevent the FireTV from responding to the TV remote (without Flirc), correct? I experimented with this last night, but the results are inconclusive. What appears to be happening is that the remote continues to pass the same commands when you press the circular pad (for navigation) no matter what mode you're in. I'm not sure if this is tied to the manufacturer code I tried to use to program it or something else. Two questions: 1. Would you please consider a debug mode for advanced users which would show two things each time a button is pressed: the code received by Flirc from the remote control, and the key sequence Flirc will send? (I think you can get the latter currently via the command line and "flirc_util settings" 2. If I decide the remote is the problem, what is a good universal remote you'd recommend for use with Flirc in the US? The Harmony remotes look nice but are very pricey. Thank you.