Rii MX3 Pro remote

Help and Support
1

Just to jump in here. I’m having the same issue. I have confirmed that it is something in the Oct update that is causing it.

I have been running OSMC for years with. I am using it with a Rii MX3 Pro remote and the dongle is plugged directly into the Pi.
The remote has fresh batteries and I have tried all the usual checks.

My timeline goes like this. My OSMC was up to date with version 18.3 and working fine. The October update came along and I did it. I pressed the OK button on the remote to launch the update. The Pi rebooted and then when it came back on I could no longer use the buttons on the remote to control the Pi. I could hear the control sounds but no navigation would work. When you press the button you would hear several clicks, not just one.

I verified it was the update by doing a fresh install of the October build. Same issue present from the setup screen.
Did a fresh install of the 18.3 and the remote worked. Then did the October update on that fresh install. Again the remote issues.

Just yesterday, I did a backup of my build, ran the 18.5 update and the same error is occurring.

I can grab the logs if you like. What tests would be helpful to run to narrow down the issue?

2

I have moved your post to a new thread as it is quite clear to me from your description that whatever issue it is that you are having is not related to the issue from the other topic (Their remote was repeating in Windows as well so clearly not an OSMC update issue). Please provide full debug logs to allow us to best assist you. The most advantageous would be for you to enable debug logging in settings, reboot twice, then just navigate until the issue manifests, then upload logs with the MyOSMC add-on.

3

Yeah I see that in the middle of the thread now the part about windows.
I’ll get those logs tonight or tomorrow depending on when I have time to do backups on then do the updates again.

4

Ok. I have completed the testing. Here was my method and setup for each instance.

Pi 3B+ with a dedicated power supply, HDMI to the TV and a mouse plugged in for the initial setup. Pi connected to the local network via a network cable.
For each update I started with a clean install from the image files found here.

The steps I took were as follows

  • Completed the setup with mouse and then turned on the debug, event and notification logging functions.
  • Turned on SMB though MyOSMC->AppStore, so I could connect and download the log files.
  • Rebooted the system. Waited 2 minutes to ensure the setup was complete. Powered down the system.
  • Removed the mouse and plugged the wireless dongle for the remote directly into the Pi.
  • Started the system and then waited 2 minutes.
  • Pressed the navigation arrows on the remote to test for functionality.

captured the logs for each test and posted below with the results.
I was not able to use the usual log pasting tools as the logs were too big. I put the files in my google drive. Hope that is OK

OSMC_TGT_rbp2_20190808 - Remote worked as expected. Was able to use the arrow keys, OK and back without an issue.

OSMC_TGT_rbp2_20191107 - Remote did not work. When I tried to press any of the arrow navigation keys. It appeared to push to the left as the sub menu for video opened. Home, back, up, down. nothing seemed to do anything. Log got very big, very fast.

OSMC_TGT_rbp2_20191118 - Remote did the same as the October update. On the first button press, moved left and stayed there. The only on that seemed to work correctly was the volume keys.

Hope someone can help figure out what went wrong in the last update. Again this happens on a clean install or if I run the update in OSMC to update to the October or the November release.

5

Your remote is working but just not how you want it. Someone posted about this exact same thing a couple days ago. I assume your remote has a function to shift between acting as a mouse and a remote. Once they did this then their remote worked as they wanted. If it needs to be adjusted further then you can download the keymap editor to edit the keys. If you don’t have an option to switch to remote mode and want to disable the mouse behavior then you can disable the scrolling by making a custom keymap and adding a few arguments. Read through this thread…

Just as a FYI this had nothing to do with the update (there was not changed behavior in this system). I’m not sure why went the clean install instead of just actually updating your existing install. That kind of seems like a lot of extra effort.

7

Thanks for looking at the logs. I must disagree with your statement about it not being an issue with the upgrade and here is why.
You mentioned that you think it is an issue with the air mouse on the remote. Yes the remote does have an option to act as an airmouse. That feature was OFF on all the tests. As you can see from this section of the first log. There are 3 distinct button presses. Down, down and then select.

> 17:52:49.275 T:1915680304   DEBUG: HandleKey: down (0xf081) pressed, action is Down
> 17:52:49.389 T:1791984352   DEBUG: Thread Timer 1791984352 terminating
> 17:52:49.391 T:1915680304   DEBUG: Keyboard: scancode: 0x6c, sym: 0x0112, unicode: 0x0000, modifier: 0x0
> 17:52:49.581 T:1894773472   DEBUG: CLibInputKeyboard::ProcessKey - using delay: 500ms repeat: 50ms
> 17:52:49.581 T:1791984352   DEBUG: Thread Timer start, auto delete: false
> 17:52:49.608 T:1915680304   DEBUG: Keyboard: scancode: 0x6c, sym: 0x0112, unicode: 0x0000, modifier: 0x0
> 17:52:49.608 T:1915680304   DEBUG: HandleKey: down (0xf081) pressed, action is Down
> 17:52:49.693 T:1791984352   DEBUG: Thread Timer 1791984352 terminating
> 17:52:49.708 T:1915680304   DEBUG: Keyboard: scancode: 0x6c, sym: 0x0112, unicode: 0x0000, modifier: 0x0
> 17:52:50.126 T:1552925408   DEBUG: CWebServer[80]: request received for /jsonrpc?JSONRPC.Ping
> 17:52:50.134 T:1552925408   DEBUG: CWebServer[80]: request received for /jsonrpc?Application.GetProperties
> 17:52:50.141 T:1552925408   DEBUG: CWebServer[80]: request received for /jsonrpc?Player.GetActivePlayers
> 17:52:50.877 T:1894773472   DEBUG: CLibInputKeyboard::ProcessKey - using delay: 500ms repeat: 50ms
> 17:52:50.877 T:1791984352   DEBUG: Thread Timer start, auto delete: false
> 17:52:50.889 T:1915680304   DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
> 17:52:51.013 T:1791984352   DEBUG: Thread Timer 1791984352 terminating
> 17:52:51.051 T:1915680304   DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
> 17:52:51.051 T:1915680304   DEBUG: HandleKey: return (0xf00d) pressed, action is Select

No mouse, no scrolling, no wheel commands are seen. Updating to the Oct or Nov installs and doing the same thing, again the mouse function is OFF on the remote. We see lots of inputs that are not being pressed and in the case of the scroll wheel, not available on the remote.

19:06:34.560 T:1916028464   DEBUG: ProcessMouse: trying mouse action wheelup
19:06:34.561 T:1916028464   DEBUG: Previous line repeats 1 times.
19:06:34.561 T:1916028464   DEBUG: ProcessMouse: trying mouse action wheeldown
19:06:34.561 T:1916028464   DEBUG: ProcessMouse: trying mouse action wheelup
19:06:34.562 T:1916028464   DEBUG: Previous line repeats 1 times.
19:06:34.562 T:1916028464   DEBUG: ProcessMouse: trying mouse action wheeldown
19:06:34.563 T:1916028464   DEBUG: Previous line repeats 3 times.
19:06:34.563 T:1916028464   DEBUG: ProcessMouse: trying mouse action wheelup
19:06:34.567 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: up, event.button.x: 0, event.button.y: 0
19:06:34.568 T:1895822048   DEBUG: Previous line repeats 1 times.
19:06:34.568 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
19:06:34.568 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: up, event.button.x: 0, event.button.y: 0
19:06:34.568 T:1895822048   DEBUG: Previous line repeats 1 times.
19:06:34.568 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
19:06:34.568 T:1895822048   DEBUG: Previous line repeats 3 times.
19:06:34.568 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: up, event.button.x: 0, event.button.y: 0
19:06:34.583 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
19:06:34.583 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: up, event.button.x: 0, event.button.y: 0
19:06:34.583 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
19:06:34.584 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: up, event.button.x: 0, event.button.y: 0
19:06:34.584 T:1895822048   DEBUG: Previous line repeats 1 times.
19:06:34.584 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
19:06:34.584 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: up, event.button.x: 0, event.button.y: 0
19:06:34.584 T:1895822048   DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0

So something happened in the October and beyond update. No other changes were made but now all of a sudden the system is reading inputs that are not there. Perhaps some sort of incompatibility between OSMC and my particular remote is now present, unsure.
I will try disabling the functions of system that are spamming the input and see if that stops the unwanted behaviour as you are suggesting. That might fix the symptom, but the underlying issue would still be present I think.

P.S. The connection here is to slow to update each time I want to test something. The work connection is fast so I can just download the images and load them. Hence the fresh install instead of the update route.

8

I’m not sure how. The remote itself switches between sending commands as a remote or a keyboard and where your having issues is that it is acting as a mouse when you want it acting as a keyboard. If there is something that changed just with the select key that is causing the issue you can manually keymap with <leftclick>select</leftclick> to fix that. The only thing I see different with how kodi is loading the input devices is that the two that don’t work correctly have this extra device that the other one didn’t…

DeviceAdded - pointer type device added: Usb Composite Device Usb Composite Device Consumer Control (event1)

…but I don’t know exactly what that is or if it has anything to do with this remote or from something else you have plugged in.

9

No it is not the select key. I am unable to navigate at all. I can see what you are saying when you say it is acting like a mouse and not a keyboard. The weird thing is how fast it is putting the commands in. All the scrolls and mouse wheels happen in less than .1 seconds.

An extra device is strange. Like I listed in the initial trouble shooting steps, I removed everything except the remote dongle from the Pi. No mouse, no keyboard, no HDD nothing but the dongle.

Let me try another test once I have a chance. Should be the next day or two. I’m going to see what devices are detected if I plug the dongle in AFTER the whole system is booted and running. Maybe that will shed some light on what the dongle or the remote is doing.
Also going to try in with just a mouse and see what kind of inputs it sees. See if that is spamming or if it just the remote.

10

Have you made any headway with this problem? I have the exact same issue that has been plaguing me for a while (just now have had some time to revisit it). I have 2 of these remotes on pi’s that don’t get a whole lot of use. My dad also has one. All 3 are no longer working. He first complained about it around the holidays and I didn’t pay much attention (he has a habit of messing things up). Then I updated one of my Pi’s and found the same issue (it worked fine before saying yes to install the update). I re-imaged it with a backup I had from July '19 and it it went back to working fine. Ran the update again and it was back to not working. I tried it with the other pi and got the exact same behavior with the other remote, so I’m pretty sure it’s not a problem with the remote itself. Pressing the D-pad and OK buttons make the sounds like it working, but there is no navigation. Other buttons don’t do anything anymore. I tried some various fixes I saw for other problems such as creating a new keymap but that didn’t help. This is the only post I can find that sounds exactly like the problem I am having. I have another RF keyboard remote that is working fine that I am using for now, but the button placement isn’t as convenient. I’d love to get these others working again.

11

Is the air mouse function on? Does pushing the button on the remote that switches the mouse function on/off make a difference?

12

You might also check this thread…

If this remote is being picked up as a joystick and that is causing the issue I think you can discover this easist by going to setting>system>input>peripherals> and observing if your remote shows up there (you should probably only see a CEC adapter entry)

13

Thanks for the reply! Enabling/disabling the mouse function makes no difference. In fact, when it is enabled it goes a bit crazy and the tracking is totally unusable. So at this point the remote is a glorified paperweight, as I can’t use it in either mode. I did plug it in along with the USB keyboard (since I can’t navigate at all with the remote) and went to settings>input>peripherals, and like you mentioned, CEC adapter was the only entry.

I did see the thread you linked to, but I don’t see it registering as a joystick so I’m not sure the fix applies. Maybe I’m wrong, and it’s entirely possible since I’m no expert when it comes to this stuff, but when I do the dmesg after plugging in the dongle I get this which seems to indicate that it is registering as an audio device? I guess that partially makes sense since this remote does have the microphone button on it so apparently it does voice commands, but I’ve never once used that functionality (nor do I really want to) to know it if actually works.

[  256.625459] usb 1-1.5: new full-speed USB device number 4 using dwc_otg
[  256.771831] usb 1-1.5: New USB device found, idVendor=2319, idProduct=00b2, bcdDevice= 2.00
[  256.771851] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  256.771861] usb 1-1.5: Product: Usb Audio device
[  256.771872] usb 1-1.5: Manufacturer: Usb Audio device
[  256.783210] input: Usb Audio device Usb Audio device Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.2/0003:2319:00B2.0001/input/input0
[  256.783744] input: Usb Audio device Usb Audio device Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.2/0003:2319:00B2.0001/input/input1
[  256.845729] input: Usb Audio device Usb Audio device System Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.2/0003:2319:00B2.0001/input/input2
[  256.845994] hid-generic 0003:2319:00B2.0001: input,hidraw0: USB HID v2.00 Mouse [Usb Audio device Usb Audio device] on usb-3f980000.usb-1.5/input2
[  256.853297] input: Usb Audio device Usb Audio device as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.3/0003:2319:00B2.0002/input/input3
[  256.916203] hid-generic 0003:2319:00B2.0002: input,hidraw1: USB HID v2.00 Keyboard [Usb Audio device Usb Audio device] on usb-3f980000.usb-1.5/input3
[  257.011727] usbcore: registered new interface driver snd-usb-audio

This is getting a little above my wheelhouse so any other advice/things to try are much appreciated!

14

I have not found a solution to the issue.

I’ve tried it again on the latest update with the same thing. I have found that it is related to the touchscreen setting.

Whatever they have done with that section looks like the cause. If you turn off the touchscreen setting, the buttons will all start working except the back button. I’ve tried a remap of the key but with the touchscreen turned off, the button is no longer recognized by the system. I gave up and just turned off updates.

If you find a fix, let me know.