[garbear]

Here's something to try. Can you remove the hold entry from the keymap? Then try launching a ROM by holding enter and see if the same behavior happens.

I've thought of another solution to the problem. This isn't exclusive to A, if you launch a game then for the next ~1s any buttons pressed will be interpreted by the GUI. This has an easy fix, when you launch a game we start capturing keypresses and button presses immediately.

However, sometimes launching a game *requires* the GUI. e.g. if no emulators are installed, Kodi will give you a list of compatible ones and ask which to install. This takes time, and this check is part of the reason why it takes as much as a second to launch a game. If we do capture input as soon as a game is selected for play, then we might have to have a way to temporarily release input again so that the GUI can receive input.

Such is the complications of the input system.

I'm focusing on some architectural problems now, so it'll be a week or two before I return to UX stuff. Still, your UX input is valuable. I've added this to the list of bugs in the OP. Thanks for reporting!

EDIT: Also the UX bug where the notification covers the subtitles has been fixed. The fix will appear in beta 4.