[nickr]

Look through your log for "OnKey" - they are all listed in my post. No volume buttons. Perhaps you have the wrong log?

[DFergFLA]

It is totally possible.  Last night was a confusing mess.  That is why I am going to do it again and be very, very careful and document what I do better.

[DarrenHill]

For reference you uninstall repos in the same way you do addons.

Your log so had the Colossus repo and some of its junk present, which you are recommended to remove.

[DFergFLA]

https://paste.ubuntu.com/25875835/

Here is what I did.  I used the remote the entire time I was in Kodi, all keypresses are from the RII i25.  I went to Music/Files/Artists/Afro-Dite and played Aqua Playa.  I then hit the volume up once, then the volume down once, then play/pause, back, forward.  then i exited that menu and went directly to upload the log.

[nickr]

Thing is I see no indication of you hitting a volume key. On my system I get (for example)

Code:

8:56:06.476 T:140053507127296   DEBUG: Keyboard: scancode: 0x15, sym: 0x003d, unicode: 0x003d, modifier: 0x0
18:56:06.476 T:140053507127296   DEBUG: OnKey: equals (0xf03d) pressed, action is VolumeUp
18:56:06.476 T:140053507127296   DEBUG: ------ Window Init (DialogVolumeBar.xml) ------
18:56:06.476 T:140053080250112   DEBUG: CAnnouncementManager - Announcement: OnVolumeChanged from xbmc
18:56:06.476 T:140053080250112   DEBUG: GOT ANNOUNCEMENT, type: 64, from xbmc, message OnVolumeChanged
18:56:06.556 T:140052038416128   DEBUG: Skin Helper Service --> Kodi_Monitor: sender xbmc - method: Application.OnVolumeChanged  - data: {"muted":false,"volume":100.0}
18:56:06.573 T:140052013238016   DEBUG: Skin Helper Widgets --> Kodi_Monitor: sender xbmc - method: Application.OnVolumeChanged  - data: {"muted":false,"volume":100.0}
18:56:06.592 T:140053507127296   DEBUG: Keyboard: scancode: 0x15, sym: 0x003d, unicode: 0x0000, modifier: 0x0
18:56:07.663 T:140053507127296   DEBUG: ------ Window Deinit (DialogVolumeBar.xml) ------

Therefore it is difficult for me to work out what is going on.

Here is a trick - ssh into the kodi machine and run

Code:

tail -F .kodi/temp/kodi.log

- then you can watch what happens when you hit various buttons.

[DFergFLA]

I will try that.  I can tell you the volume do go up and down when I hit them.

[DFergFLA]

@nickr

Can I get a recommendation for a remote just in case I can't get this to work right?  I bought this one because it was suppose to work with Kodi.  I need a wireless and I would love it to work "Out of the box" or at least be easy to get to work.

Thanks

[DFergFLA]

this is all I can see:

Code:

Keyboard: scancode: 0x40, sym: 0x0134, unicode: 0x0000, modifier: 0x100

I just don't think this one is going to work.  But i can't randomly buy remotes looking for one that does.

[nickr]

I think on Ubuntu and derivatives you need to look at some operating system tool that converts scan codes to key presses. I'll take a look when I am at my Ubuntu machine. In the meantime can you try libreelec from a USB stick and see if it works there?

[nickr]

Also, in your desktop (the one you run kodi on) have a play about with xev and evtest.

[DFergFLA]

will test libraelec today

[DFergFLA]

I got libraelec and the remote works fine there.  Whatever he problem is it seems to be on the ElementaryOS side.