Archive:MINIX A2: Difference between revisions
mNo edit summary |
mNo edit summary |
||
(5 intermediate revisions by 3 users not shown) | |||
Line 3: | Line 3: | ||
| [[File:a2.png|400px]] || [[File:back_face_a2.png|550px]]<br/>This is the MINIX NEO A2 Remote.<br /> | | [[File:a2.png|400px]] || [[File:back_face_a2.png|550px]]<br/>This is the MINIX NEO A2 Remote.<br /> | ||
It has a full QWERTY keyboard on the back, which allows the use of the '''Search''' function in KODI.<br/> | It has a full QWERTY keyboard on the back, which allows the use of the '''Search''' function in KODI.<br/> | ||
As much as we would like every button to work 'out of the box', we need to make changes to the | As much as we would like every button to work 'out of the box', we need to make changes to the keymaps files for several of the front facing buttons<br/> | ||
This task is necessary for the majority of RF remotes on the market.<br/> | This task is necessary for the majority of RF remotes on the market.<br/> | ||
<br/> | <br/> | ||
Line 122: | Line 122: | ||
</keyboard> | </keyboard> | ||
</VirtualKeyboard> | </VirtualKeyboard> | ||
.... | |||
== remote.conf example for amlogic boxes == | |||
/etc/amremote/remote.conf | |||
Example settings needed to map the power button (note - this only applies once the device has booted, the initial power on detection appears to be in hardware) | |||
.... | |||
factory_code = 0xfe010001 | |||
key_begin | |||
0x18 116 # power | |||
key_end | |||
.... | .... |
Latest revision as of 02:44, 10 September 2020
Customized MINIX NEO A2 mouse.xml
<keymap> <global> <mouse> <leftclick>Select</leftclick> <rightclick>Back</rightclick> <middleclick>noop</middleclick> <doubleclick id="0">noop</doubleclick> <longclick id="0">noop</longclick> <wheeldown>noop</wheeldown> <wheelup>noop</wheelup> <mousedrag>noop</mousedrag> <mousemove>noop</mousemove> <mousedragend>Select</mousedragend> <mouserdragend>Back</mouserdragend> </mouse> </global> </keymap>
Customized MINIX NEO A2 keyboard.xml (additions)
If there are multiple keymap entries for the same key name, the last entry wins.
I recommend placing manual entries at the end of the <keyboard> stanza inside <global>
This saves us the effort of finding and editing each original key assignment
.... <F2>NextSubtitle</F2> <home>AudioNextLanguage</home> <return>SendClick(8)</return> <F1>Stop</F1> <prev_track>PageUp</prev_track> <next_track>PageDown</next_track> </keyboard> </global> ....
keyboard.xml per Window customization
Another valuable tool when editing keyboard.xml: there are subsections which allow you to re-assign keys while in a particular 'Window'.
For example let's look this default entry:
.... <FullscreenVideo> <keyboard> .... <return>OSD</return> .... </keyboard> </FullscreenVideo> ....
While a video is playing (fullscreen) the <return> key will bring up the OSD, instead of executing SendClick(8) as assigned in <global>
If this behaviour is not desired, an additional manual entry is required in the relevant subsection.
keyboard.xml per Window customization, refining remote actions
Earlier I reassigned the <return> key within the <global> section of keyboard.xml.
This had one negative side effect: After manually entering text, pressing <return> would not submit the text.
The solution is to modify the action of the <return> key while in the VirtualKeyboard Window.
Add one line to the <VirtualKeyboard> section of keyboard.xml
.... <VirtualKeyboard> <keyboard> .... <return>Select</return> .... </keyboard> </VirtualKeyboard> ....
remote.conf example for amlogic boxes
/etc/amremote/remote.conf
Example settings needed to map the power button (note - this only applies once the device has booted, the initial power on detection appears to be in hardware)
.... factory_code = 0xfe010001 key_begin 0x18 116 # power key_end ....