Jivelite remote library code#
Jivelite remote library tv#

The logs look like this (stripped down): // UP ARROWДEBUG: CLibInputKeyboard::ProcessKey - using delay: 500ms repeat: 50ms And of course, the other buttons register, but nothing shows up in the log when I press the back button. I turned on debugging and started to watch ~/.kodi/temp/kodi.log while pressing different buttons. In some cases, it works like going back one level + pressing the Home key so it would take me back to the previous screen and move/scroll to the top of the list.

Jivelite remote library tv#

For example, if IвЂ™m in TV Shows > Friends > Season 8, pressing the back button takes me back straight to the Home screen on OSMC.Д«ut when inside Settings, some N levels deep, it acts like going back one level. In most situations it acts like going to the Home screen, no matter how deep you are in the library. On its own, it behaves differently depending on the context.

Jivelite remote library code#

When in the mode where you press a button to map it to an action, pressing the back button simply results in exiting out of that mode, and Keymap Editor doesnвЂ™t register any key code for that press - so nothing is mapped and you canвЂ™t even know what kind of code that button sends. Mouse button - unrecognized (it simply switches the remote between modes internally).The first thing I did was fire up Keymap Editor. doesnвЂ™t emit any code (at least I wasnвЂ™t able to catch any).So, the back button does work, as in, it does something, but unfortunately: Click it again and it switches back to being a remote/keyboard.) The problem (Pay no attention to the mouse button - when clicked, it simply switches the remote to a mouse mode, where you can use the arrows to move a cursor on the screen, etc. However, the back button (that bent arrow left to the home button) has wasted many hours of my day today. The home button worked like a Home key on a keyboard by default, which simply throws you to the beginning of a list/view youвЂ™re in, but this button can be easily mapped to whatever I like (e.g., going to Home screen on OSMC).The volume up and down buttons increase and decrease the volume.It even works with a longpress, which shows a context menu for an item on the screen. The OK button works as it should, depending on the context (selecting, entering a submenu, play/pause, etc).The up/down/left/right arrows works like they should, I can go up, down, left, right.The mute button works like a mute button.The power button works like a power button, invoking a menu with stuff like closing the system, restarting, etc.It works with OSMC out of the box almost entirely: