Remote "Double-Clicks" Following April 2019 Update

#1

Hello. Immediately following updating to v18 via the April 2019 update, one press of any button on my remote results in two or three “clicks” in OSMC. I had no remote issues prior to the April 2019 update.

I am running version 18.2-RC1 using a FLIRC remote. I made no changes to the remote or the FLIRC during the update. Operation using a keyboard is not affected.

Dan

1 Like
2019 April upgrade - issues (menu, Harmony bluetooth multi-keypress, CEC steal input)
Key Press Repeat Crazy
#2

Having the same issue following the update yesterday, although I find some of the other issues more annoying. e.g. Subtitle options now missing when you press Enter whilst playing something, recent programmes or films on main menu don’t react to Enter button.

#3

I should have added that this problem causes OSMC/Kodi to jump over menu items making it impossible to use.

#4

Kodi v18 uses a new input method for devices that expose themselves as a keyboard (i.e. don’t go through an LIRC socket).

The repeat filtering is different. You may need to adjust this on the FLIRC.

#5

sam_nazarko Thanks. The inter-key delay on my FLIRC is already set at ‘7’ which is the maximum setting.

Is there a setting within OSMC Kodi v18 to adjust the repeat delay?

#6

Unfortunately not – this is part of libinput and is configured at build time

Sam

#7

Is there any way this can be fixed in an update? I depend too much on the Flirc and it still works on the newest Libreelec, I prefer OSMC as it feels more stable and less buggy.

#8

Does the FLIRC support firmware updates?
I don’t know why it’s sending repeat presses – ideally this needs to be fixed there.

Has anyone raised this via the FLIRC support?

Did you try with LE v18? I assume you’re running it on an embedded device like Pi (and not x86_x64) which would use X11.

If you can compare a debug log of LE v18 vs OSMC v18, I may be able to help if the device’s input layer is being handled differently.

Sam

#9

I’ve logged it on the FLIRC forum, hopefully they can support for a fix.

Link here: http://forum.flirc.tv/index.php?/topic/2953-flirc-on-latest-kodi-is-broken/

#10

Thanks - that’s great.

#11

I tested FLIRC this morning after updating both the FLIRC GUI and FLIRC firmware. The maximum inter-key delay is still ‘7’, and it still sends double key presses.

#12

Same issue here after the latest April update. My IrDa remote which worked fine befoer the update now results und multiple key presses while my Logitech wireless keyboard works fine. A solution would be much appreciated.

The below is what I get on a single press of the left key on the remote:

2019-04-26 11:30:40.155 T:1916294704   DEBUG: Keyboard: scancode: 0x6a, sym: 0x0113, unicode: 0x0000, modifier: 0x0
2019-04-26 11:30:44.871 T:1895822048   DEBUG: CLibInputKeyboard::ProcessKey - using delay: 250ms repeat: 33ms
2019-04-26 11:30:44.871 T:1280258784   DEBUG: Thread Timer start, auto delete: false
2019-04-26 11:30:44.901 T:1916294704   DEBUG: Keyboard: scancode: 0x69, sym: 0x0114, unicode: 0x0000, modifier: 0x0
2019-04-26 11:30:44.901 T:1916294704   DEBUG: HandleKey: left (0xf082) pressed, action is Left
2019-04-26 11:30:45.139 T:1916294704   DEBUG: Keyboard: scancode: 0x69, sym: 0x0114, unicode: 0x0000, modifier: 0x0
2019-04-26 11:30:45.139 T:1916294704   DEBUG: HandleKey: left (0xf082) pressed, action is Left
2019-04-26 11:30:45.165 T:1916294704   DEBUG: Keyboard: scancode: 0x69, sym: 0x0114, unicode: 0x0000, modifier: 0x0
2019-04-26 11:30:45.165 T:1916294704   DEBUG: HandleKey: long-left (0x100f082) pressed, action is Left
2019-04-26 11:30:45.198 T:1916294704   DEBUG: Keyboard: scancode: 0x69, sym: 0x0114, unicode: 0x0000, modifier: 0x0
2019-04-26 11:30:45.198 T:1916294704   DEBUG: HandleKey: long-left (0x100f082) pressed, action is Left
2019-04-26 11:30:45.207 T:1280258784   DEBUG: Thread Timer 1280258784 terminating
2019-04-26 11:30:45.215 T:1916294704   DEBUG: Keyboard: scancode: 0x69, sym: 0x0114, unicode: 0x0000, modifier: 0x0
#13

Same problem here with two Vero units both with an FLIRC - both units are now unusable :frowning:

#14

Could someone kindly explain to me what is the advantage of using FLIRC instead of the build in IR reciever of the Vero?
Not that this is a solution to your FLIRC issue but I would like to understand the reasoning of the FLIRC usage?

#15

Flirc you can easily program your remote buttons to any function from any remote. Using the built in IR receiver, im guessing your limited to the Vero remote.

#16

No, there is no relation between the Vero Remote (which is RF) and any IR codes that a IR Remote sends.

#17

I have been using FLIRC since my RPI days. When I moved to Vero 4K, I just moved them over as they worked and were setup on my Harmony. However, I have just pulled them out, reconfigured Harmony to OSMC, Vero 4k and everything is now working - no double-clicking etc. :smile:

1 Like
Key Press Repeat Crazy
#18

Same here… I use an old Sony universal remote with FLIRC, and I’ve found that if I’m extremely quick with my button presses I can get it to only register a single press.

I wouldn’t be opposed to switching to the OSMC IR receiver, but I don’t see my remote in the list of remotes in My OSMC. Could someone point me to a post or wiki page that explains how to create a new lircd.conf file for my remote? Or… I guess it might be easier to set the universal remote to emulate one of the existing remotes in the list, then use keymap editor to fix any irregularities (?)

Thanks

#19

I guess you might find one here
http://lirc-remotes.sourceforge.net/remotes-table.html

Most likely it’s the easiest to do that.

#20

Hopefully we get an update on this soon.

Sam