[Atreyu]

I have downloaded your revised .evmap (checked it's in /storage/.config) and rebooted.
Turned on debugging and pressed the context button a couple of times.

I see the OnKey results for every key (for instance while browsing the power menu to reboot) but i don't see keypresses from 'context/F12/Playpause' at all.

\edit: Just retried just to be sure; no keypress for the context button is registered. All others are. Maybe someone else with this 'chinese' remote can confirm...

[wrxtasy]

Suggestion:

edit:

Code:

nano .config/xiaomibtremote.evmap

CTRL-O to save CTRL-X to exit

and remove the F12 line and reboot and try Kodi debug again to see if a different Context - OnKey result pops up.

[Atreyu]

Suggestion:

edit:

Code:

nano .config/xiaomibtremote.evmap

CTRL-O to save CTRL-X to exit

and remove the F12 line and reboot and try Kodi debug again to see if a different Context - OnKey result pops up.

Ok.
Just to check: you mean remove the complete line: KEY_F12 = KEY_PLAYPAUSE line from the file, right? Not just the first part.

Will do & report back

[Atreyu]

Result:

The .evmap looks like this:

KEY_POWER = KEY_MUTE
KEY_HOME = KEY_EPG
KEY_BACK = KEY_EXIT

Still no reference of the context key; all others (volume up/down/select) are registered.

\edit repeated it a second time just to be sure. I am beginning to believe there is nothing sent from the context key on the remote. That would void all our efforts unfortunately.


If there's something else we could try i will be glad to test.

[wrxtasy]

Please post up a http link log...when you are hammering the Home, Back and Context keys pls.

Code:

paste /storage/.kodi/temp/kodi.log

[Atreyu]

Off the a meeting right now.
As soon as i return i will test further and post kodi.log

[Atreyu]

OK, I think i got something this time.
I started Kodi, enabled debug mode and started mashing the keys ;-)

What i did was: press 'home' couple of times, then press 'back' a couple of times, then press 'context' a couple of times.

Here is the log: https://pastebin.com/FA0KTPM0

I noticed this is how the context button registers: yellow (0xe5) pressed, action is ContextMenu

Progress..?

[wrxtasy]

Thx.
This was the missing Remote - Context Button from the Kodi.log:

DEBUG: LIRC: Update - NEW at 26943:7f 0 KEY_COMPOSE devinput (KEY_COMPOSE)

Another one of these and a reboot and you should have success - Context button = KEY_COMPOSE which is remapped to Play/Pause:

Code:

wget http://wrxtasy.libreelec.tv/LE-Xiaomi/xiaomibtremote.evmap -O /storage/.config/xiaomibtremote.evmap

Unless you want the remote Home button as Play/Pause and the Context button mapped as a proper Context button ?

Play/Pause situated to the left of the Back button does not make a lot of sense layout wise IMHO.

You can try out that Alternate mapping here:

Code:

wget http://wrxtasy.libreelec.tv/LE-Xiaomi/xiaomibtremote.v2.evmap -O /storage/.config/xiaomibtremote.evmap

[Atreyu]

Tested both of your modified evmaps. Context menu key still unresponsive.

I noticed you say the context menu button would be on the left of the back button. It's not. It's on the right of it. On the left is the 'Home' key, which with your latest mapping now acts as the context menu button.
The 'hardware' key for context menu (on the right of the back key) does nothing with either v1 or v2 of the evmap file.

To answer your question for the exact mapping of the keys, i don't really have any preference other than have the button be configurable. So just have this button send anything would be perfect to me (although mapping the context menu function to its proper button seems most logical).

btw: the 'Home'key on the left with any mappping shows player process info during play. I would expect it to pause the movie with the 'v2' mapping (?). But that's fine by me; the key was/is configurable.

[Vlaves]

Tested both of your modified evmaps. Context menu key still unresponsive.

I noticed you say the context menu button would be on the left of the back button. It's not. It's on the right of it. On the left is the 'Home' key, which with your latest mapping now acts as the context menu button.
The 'hardware' key for context menu (on the right of the back key) does nothing with either v1 or v2 of the evmap file.
...

For em exactly the same. Context button right from the centered back button and not working at all.

[Atreyu]

I will see if i can fiddle with this some more when i find the time (travelling now).
If the context button is active it should be mappable.

Been using the remote as-is and it's great without this button already.

And big thanks @wrxtasy for teaching a monkey some tricks ;-)

[Atreyu]

Done some more testing with the KEY_COMPOSE value, assigning it to different functions.
It will not respond to anything, no matter what keymap is used. Seems the key on this type remote is just not mappable.

If anyone with the same model discovers how to make the context menu button work, congratulations & please post here :-)

[wrxtasy]

I've just discovered a bug, try this new .rules file:

Code:

rm /storage/.config/udev.rules/51*
wget http://wrxtasy.libreelec.tv/LE-Xiaomi/51-these-are-not-joysticks.rules -O /storage/.config/udev.rules/51-these-are-not-joysticks.rules

[Atreyu]

Tried the new '51-these-are-not-joysticks.rules' - file.
No difference (but thanks!)

[Vlaves]

I've just discovered a bug, try this new .rules file:

Code:

rm /storage/.config/udev.rules/51*
wget http://wrxtasy.libreelec.tv/LE-Xiaomi/51-these-are-not-joysticks.rules -O /storage/.config/udev.rules/51-these-are-not-joysticks.rules

no changes for me too, nevertheless thanks a lot for your effort

I guess you have checked the links here in the libreelec forum, don't really understand, but maybe its a way to get it running with all keys:
https://forum.libreelec.tv/thread/9319-8...#post63149
https://forum.libreelec.tv/thread/9763-n...#post61706