Posts: 292
Joined: Mar 2011
Reputation:
0
HansP
Senior Member
Posts: 292
map the OK key to Enter and Back to backspace !
that should do it ...
Posts: 67
Joined: Apr 2011
Reputation:
0
map the OK key to Enter and Back to backspace !
how i do that?
for the other keys I had not done anything they've worked
Posts: 1,275
Joined: Oct 2006
Reputation:
5
you have to edit the keymap
Posts: 7,256
Joined: Nov 2008
Reputation:
121
You need to find out what signals your remote is sending to XBMC. Depending on how the remote works, it might be using LIRC or it might be emulating a keyboard. If you enable debug logging the log file will tell you what is going on.
Enable debug logging from System settings, System, Debugging, then press the OK button a few times, then press the Back button a few times, then disable debug logging again. Now look at $home/.xbmc/temp/xbmc.log. You can either switch to a console or use putty if you prefer. Put a copy of the log on pastebin.com and paste the link here. From the log I shoud be able to tell you what you need to configure.
JR
Posts: 67
Joined: Apr 2011
Reputation:
0
is Linux /home/<username>/.xbmc/
i see in Debugging this code home/amen/.xbmc/temp/xbmc.log. on top of the screen
i try this but same error
Posts: 7,256
Joined: Nov 2008
Reputation:
121
The remote is generating the log entry:
DEBUG: SDLKeyboard: scancode: 182, sym: 0, unicode: 0, modifier: 0
Did you press both the OK and Back buttons? If so they are both generating the same log entry. The remote is emulating a keyboard, which is very common for the cheaper remotes, but it's producing a very odd keypress. The scancode, i.e. 182 (hex 0xB6) identifies the key that was pressed, but I can't find any documentation for scan code 182. None of the lists of keyboard scan codes I can find mention it.
Basically your remote is generating a keyboard press that doesn't exist.
JR
