Jump to content
Flirc Forums

yawor

Administrators
  • Content count

    774
  • Joined

  • Last visited

  • Days Won

    50

yawor last won the day on July 6

yawor had the most liked content!

Community Reputation

57 Excellent

2 Followers

About yawor

  • Rank
    Forum Support
  • Birthday 03/03/1983

Profile Information

  • Gender
    Male
  • Location
    Warsaw, Poland

Recent Profile Visitors

4,318 profile views
  1. Basic Concept on Defaults

    As I've mentioned in my previous post, built-in means built-in. To be more precise, the definitions are built into the firmware itself and don't need to be present in the configuration section to work. By switching checkboxes in the Advanced settings you only change a flag in the Flirc that tells the firmware whether to use that specific built-in table or not. So by changing these settings nothing is being erased from your own configuration. If you have your own keys recorded in the Flirc then you won't loose them. The logic works (more or less) like this: 1. Flirc receives the IR signal and pre-processes and coverts it to a hash value. 2. Then Flirc tries to match the hash value to buttons recorded by the user. 3. If user's recorded buttons don't match the hash value, Flirc then goes through enabled built-in profiles and tries to match the hash in them. This means three things. First, you don't need to record the keys that are in the built-in profiles for them to work. Second, you are always able to overwrite the built-in definitions by re-recording the buttons that already have built-in function and assign your own function. Third, you can record additional keys besides the ones in the built-in profiles and add missing keys. As for the keys missing in the Kodi profile, it's something @jason would need to add to the firmware and ask Logitech to update profiles available in MyHarmony to support new keys. But given that the Flirc is fully programmable, you are able to add missing keys on your own by recording them in the Flirc software.
  2. Basic Concept on Defaults

    The built-in profiles are, as a name suggest, built into the firmware. In the latest version you are able to enable or disable each of the built-in profiles individually in the Advanced settings in Flirc GUI. To use them, you just add a Flirc/Kodi profile on your Harmony remote using MyHarmony software. You may have some issues with built-in profiles though, related to the keyboard layout. The built-in profiles are only compatible with US QWERTY or compatible keyboard layouts. If you use different keyboard layout then the built-in profiles may be messed up.
  3. Fire TV Stick

    You need to disable ADB over USB to enable USB Host feature in the Fire TV stick.
  4. aezrty qwerty mismatch

    It's a known issue. For now you need to use a workaround:
  5. Ability to learn remote commands

    There's no option to pass-through the IR directly to PC. If you want to control your mouse with Flirc then you need to assign direction buttons to some keyboard combinations and then use some software solution that will capture the keys and control the mouse instead. It depends on your OS in the HTPC. For Windows, you can enable mouse keys: https://support.microsoft.com/en-us/help/14204/windows-7-use-mouse-keys-to-move-mouse-pointer It's not ideal, but it's built into the system. You can also use software like EventGhost. For Linux you would need to do some research. There's also a chance that Flirc will add a mouse control sometime in the future. I'm a big proponent of that feature myself.
  6. Ability to learn remote commands

    Well, if the original remote is not incompatible with Flirc (there are some that cause some issues) and Harmony is able to correctly learn the signal and replicate it on some button, then you should be able to record it in Flirc (by pressing the button on the Harmony when asked by Flirc software) and assign it to some keyboard key combination. But it's hard to tell unless you do it. With learning remotes like Harmony, it's not always possible to 100% correctly replicate the signal from the original remote. With Flirc it should still work to some degree because Flirc doesn't try to decode the data in the signal, but uses signal timings to calculate a hash value it then uses internally.
  7. Ability to learn remote commands

    I don't understand what you mean by saying "ability to learn via Harmony". Using Flirc software you can learn signals from almost any IR remote control and assign them to keyboard keys. That's the main feature of Flirc.
  8. Sleep do not wake up

    Flirc should wake your PC only when a known signal is received. Anyway, you can record a wake/suspend key (in Media keys in the GUI). After that only that key should be able to wake your PC.
  9. I think it's going to be added back to Flirc v2 eventually. I don't know if @jason has any plans on whether the profiles could be enabled/disabled individually or not but it could be a nice feature.
  10. From what I understand, that app uses ADB to emulate a mouse input, so ADB needs to be enabled for it to work. On the other hand, for Flirc to work you need USB Host (or OTG) to be active. When ADB is turned on, the USB Host is deactivated. So for Flirc to work you need to have the ADB turned off. So it seems you can't use both Flirc and mouse toggle at the same time.
  11. Flirc with fire tv stick

    If you have a working OTG cable, then it should work. You need to turn off USB debugging otherwise the OTG won't work.
  12. Hi, The firmware is embedded in the GUI. It should offer you firmware upgrade after starting up GUI and plugging in your Flirc.
  13. @jason I've never used LIRC. I've googled lirc hid input and got some results but maybe I've jumped too fast to conclusion that this is possible. On the other hand, EventGhost (on Windows) is 100% capable of using any generic HID device as a source of events.
  14. @jason, I think LIRC can also work with HID input. So instead of trying to implement such advanced mode using serial port emulation I would much rather like to see Flirc sending a custom HID report containing 4-byte hash it is calculating from IR signal. It could do that for any unrecognised (not recorded) button. That would not need any drivers to work. It would be usable with LIRC and on Windows with apps like EventGhost.
  15. Disable Long Press functions?

    You can look at this thread on Kodi forum: https://forum.kodi.tv/showthread.php?tid=260736. It shows how to disable long press by adding your own keymap file. You may try using Kodi Keymap Editor add-on: http://kodi.wiki/view/Add-on:Keymap_Editor. I'm not using it so it's up to you to find out how to use it. You can also look at this xml: https://github.com/xbmc/xbmc/blob/master/system/keymaps/keyboard.xml. This is a default keymap file. If you look for word "longpress" you'll see that it is used as a key modifier. That way you can find all buttons that are long press capable and also disable them if you use them with your remote (there's no need to override if your remote doesn't use them).
×