The page and config.xml send a reader two ways to find a dead remote button: the
InputReader:D logcat filter while the button is pressed, and the getevent Linux
scancode into settings_key_scancodes. On a Google TV 14 PEAQ "AI PONT DE"
(#853) both came back empty for the same button, so it read as never delivered:
InputReader logged no key line at all, and the MSC_SCAN getevent printed
(0x000c009f) is an evdev code, not the scanCode the framework reports, so both
spellings of it (159, 786591) matched nothing. A temporary Log.d at the top of the
helper's onKeyEvent named the delivered values (keyCode=83 scanCode=240) and
settings_key_keycodes = [83] then opened the TV's Settings.
So the note gains the route that works, the reason the other two can fail, and
the fact that a getevent code matching nothing is not proof the press never
arrived. No separate device note: the finding is about finding the number, not
about the set, and it belongs where a reader looks for a keycode. The same two
caveats go into the settings_key_scancodes and settings_key_keycodes comments a
customiser reads before the page. PROMPT.md carries the same half-truth ("read
the scancode with getevent -lt") and is left for the maintainer.
