Hey all,
I picked up an Alexa remote to use with my Mi Box since it has IR volume control. In order to get it working, I had to pair it with a fire stick, configure the remote, then pair it with my mi box. It connects and recognizes the remote and most things work right away.
Major issue was that the center buttons on the alexa remote is NUMPAD_ENTER (keycode 160) whereas on the mi box remote it's DPAD_CENTER. It's basically unusable until the you resolve this because the mi box OS doesn't know what to do with NUMPAD_ENTER. So you can't used the button.
No big deal. I download Button Mapper and remapped NUMPAD_ENTER to keycode 23 (DPAD_CENTER) using the keycode service I activated via an adb shell. There are two methods to remapping a key to pass on a keycode in Button Mapper.
Method one needs the keycode service running. Everything works perfectly in this scenario EXCEPT there is 2 seconds of lag when you push the button before anything happens on the screen.
Method two doesn't need the keycode service running (not sure how it does this?) and there is NO LAG between press and action. BUT, you can't use the onscreen keyboard when this method is employed. It just blinks when you try to input a letter. If you do it enough, the entire OS locks up and needs to be rebooted.
Very strange. Does anyone have any ideas?
I think the solution lies in the method that does not require the keycode service to run. There is no lag using that method. I just can't figure out why you can't type using the on-screen keyboard.
Thank you in advance!
Paging /u/flar2.
Uhm, that's a strange issue for method 2.
Trying installing a different keyboard and report back: https://play.google.com/store/apps/details?id=org.liskovsoft.androidtv.rukeyboard
Method 1, that could just be a limitation of that method with button mapper. Try this other mapper app: https://play.google.com/store/apps/details?id=io.github.sds100.keymapper maybe it goes about the problem more gracefully.