Kodi Community Forum

I have a 'new' issue that's suddenly occurring that I can't work out how to resolve. Recently (since 19.5 but maybe since 19.4) the OK button on my remote isn't actioning select until the second press. I'm unclear when this started happening as at first I thought it was a problem with the remote of the IR receiver in the PC but I've now confirmed it's specifically impacts only Kodi.

In the debug log snippet below I navigate to the location (scancode 0x50....action is Down) and then press OK (scancode 0x1c) which is ignored until I press it a 2nd time.

2023-02-03 13:16:09.061 T:29816   debug <general>: Keyboard: scancode: 0x50, sym: 0x112, unicode: 0x00, modifier: 0x0
2023-02-03 13:16:09.061 T:29816   debug <general>: CInputManager::HandleKey: down (0xf081) pressed, window 10025, action is Down
2023-02-03 13:16:09.293 T:29816   debug <general>: Keyboard: scancode: 0x50, sym: 0x112, unicode: 0x00, modifier: 0x0
2023-02-03 13:16:10.858 T:29816   debug <general>: Keyboard: scancode: 0x1c, sym: 0x0d, unicode: 0x0d, modifier: 0x0   <- 1st OK button press
2023-02-03 13:16:11.157 T:29816   debug <general>: Keyboard: scancode: 0x1c, sym: 0x0d, unicode: 0x00, modifier: 0x0   <- 2nd OK button press
2023-02-03 13:16:11.157 T:29816   debug <general>: CInputManager::HandleKey: return (0xf00d) pressed, window 10025, action is Select

It doesn't happen every time but also doesn't seem specific to a particular area within KODI. Hopefully someone can shed some light on what's happening and point me in the right direction to solve this?

PC: Intel NUC10i7FNH
OS: Windows 11 Pro 22H2
Kodi: currently v20.0
No recent changes to h/w or s/w other than Kodi

webby

UPDATE: the title of this post should read "RC6 Remote OK button sometimes *not* triggering action on first press (why can I edit it?)

(2023-02-03, 04:48)webby2019 Wrote: [ -> ](why can I edit it?)

Because you're a newbie account, so you don't yet have edit privs (it's a generic anti-spam measure implemented here from hard-won experience).

I've adjusted it for you.

Well, answering my own question it appears to have been the Infrared driver as reverting back to a previous version (under Windows rollback) has made the problem disappear.
Still get the duplicate scancode: 0x1c lines before the select action but that is apparently normal ¯\_(ツ)_/¯

webby