Jump to content
Flirc Forums

Recommended Posts

  • 3 weeks later...
  • 1 month later...
Posted
On 2/3/2018 at 4:21 PM, arabesc said:

I have an issue with Kodi - if there is a fast sequence of press/release actions for a  button, Kodi sometimes treats it as a long-press action and does something that I don't need.
Can it be a consequence of that new feature?

Only if the button you are using is recorded as a long press. Otherwise, because Kodi also supports long press, you can try increasing their long press hold time requirement.

Posted
2 hours ago, jason said:

Only if the button you are using is recorded as a long press. Otherwise, because Kodi also supports long press, you can try increasing their long press hold time requirement.

Do you mean that Kodi interprets fast successive key-presses as a long-press action? I don't understand where that long-press action comes from.

Posted

kodi supports a second function assigned to the same key

flirc also supports this feature

The two can conflict.

Have you specifically recorded a long press with flirc?

Posted
10 hours ago, jason said:

Have you specifically recorded a long press with flirc?

No, there is standard Kodi layout in Flirc and standard key layout in Kodi, nothing special. There should be no long-press actions (e.g., for navigation keys) but they are.

Posted

@arabesc I have few questions regarding your setup:

1. Which Flirc model do you have?
2. What remote are you using? Is it an universal remote? If yes, what profile have you selected?
3. If you have new Flirc model (the metal one), please open Flirc GUI and open Device Log in File menu. Then select enable IR debugging and press few buttons on your remote which you're using with Flirc. Please save it to a file and attach it here.
4. Save your configuration and attach it here.

Posted (edited)

1. It's a FLIRC-SE.
2. One For All URC 6440, it's an universal remote, and I've selected a profile for some LG TV that uses all of the keys and doesn't use alternate codes for successive presses.
3. I don't think that it's a new model.
4. it will be done later.

Edited by arabesc
Posted

If it's Flirc-SE then it's a 1st gen model. You can try changing the interkey delay value in advanced settings. Try decreasing it by 1 and do some tests. If not enough, then lower it again. This controls the time window within which the next received signal is treated as a repeat signal instead of releasing and pressing again. This value will also affect the ability to detect actual signal repeats.

The new, 2nd gen model doesn't have that setting anymore as it records the actual signal delay value for each recorded button.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...