CoreELEC (official): 9.0-nightly_20190201 (S912.arm)
CoreELEC:~ # ls -l /flash
total 150484
-rwxr-xr-x 1 root root 154009600 Feb 3 00:19 SYSTEM
-rw-rw-r-- 1 root root 16919 Dec 8 23:57 boot-logo.bmp.gz
-rw-r--r-- 1 root root 44286 Feb 3 22:20 dtb.img
drwx------ 2 root root 16384 Jan 14 2018 lost+found
-rwxr-xr-x 1 root root 3257 Jan 14 2018 remote.conf
CoreELEC:~ # ls -l /storage/.config
total 80
drwxrwxr-x 2 root root 4096 Feb 2 01:59 aacs
-rwxr-xr-x 1 root root 47 May 9 2018 autostart.sh
-rw-r--r-- 1 root root 3 Feb 3 23:27 boot.status
-rw-rw-r-- 1 root root 284 Jan 14 2018 hosts.conf
drwxr-xr-x 2 root root 4096 Feb 2 01:58 hwdb.d
drwxrwxr-x 2 root root 4096 Feb 2 01:58 iptables
drwxr-xr-x 2 root root 4096 Feb 2 01:58 logind.conf.d
drwxr-xr-x 2 root root 4096 Feb 2 01:59 modprobe.d
drwxr-xr-x 2 root root 4096 Feb 2 01:58 modules-load.d
drwx------ 2 root root 4096 Feb 4 21:56 pulse
drwxr-xr-x 2 root root 4096 Feb 2 01:59 pulse-daemon.conf.d
drwxr-xr-x 2 root root 4096 Feb 2 01:59 rc_keymaps
-rw-r--r-- 1 root root 63 Jan 26 10:35 rc_maps.cfg
-rw-rw-r-- 1 root root 720 Feb 2 01:59 rc_maps.cfg.sample
-rw-rw-r-- 1 root root 3726 Feb 2 01:59 samba.conf.sample
drwxr-xr-x 2 root root 4096 Feb 2 01:58 sleep.conf.d
drwxr-xr-x 2 root root 4096 Feb 2 01:58 sysctl.d
drwxr-xr-x 2 root root 4096 Feb 2 01:58 system.d
drwxr-xr-x 2 root root 4096 Feb 2 01:58 tmpfiles.d
drwxr-xr-x 2 root root 4096 Feb 2 01:58 udev.rules.d
CoreELEC:~ # fdtget -t s /flash/dtb.img /meson-remote/ status
disabled
CoreELEC:~ # fdtget -t s /flash/dtb.img /meson-ir/ status
okay
I can see remote.conf right there on /flash. Rename it or delete it and try again.
That’s interesting… I have the same problem.
The remote was working on the previous version of CE (sorry I don’t remember the exact version) and after one manual update to 8.99.1.1 stop working.
More or less the same situation, no dtb.img at /flash, with one remote.cfg. Like @anthonws, I not made a clean install, was an update.
My current status:
CoreELEC:~ # ls -l /flash
total 147864
-rw-r--r-- 1 root root 40775 Feb 4 23:31 dtb.img
drwx------ 2 root root 16384 Dec 18 2016 lost+found
-rwxr-xr-x 1 root root 151355392 Jan 1 2015 SYSTEM
CoreELEC:~ # fdtget -t s /flash/dtb.img /meson-remote/ status
disabled
CoreELEC:~ # fdtget -t s /flash/dtb.img /meson-ir/ status
okay
CoreELEC:~ # ir-keytable
/sys/class/rc/: No such file or directory
No devices found
CoreELEC:~ # cat /proc/device-tree/le-dt-id
gxl_p212_1g
—UPDATE—
Fixed after copy the dtb.img to flash, remove the remote.conf from flash and force a Re-Update as described in this other post.
@CGarces No need to reapply the update, just delete the file or rename and reboot.
@anthonws you clearly have a remote.conf file in /flash, follow the instructions above
1 Like
Hi, CoreELEC team. I’ve been using kszaq’s LibreELEC 8.2.2.3 community build for the Amlogic S912 on my Beelink GT1 Ultimate for quite some time. I recently formatted my memory card to do a clean install of CoreELEC 8.99.2. The remote.conf support appears to be somewhat problematic, however, because the file that I’ve copied-and-pasted below does not fully work in CoreELEC despite working fine in LibreELEC. To be more specific, multiple keys such as those associated with TAB, HOME and MENU do not respond when pressed. Can you please investigate this issue?
#amlogic NEC remote
factory_code = 0x7f800001
work_mode = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay = 20
debug_enable = 1
key_begin
0x51 31 = S
0x4d 113 = MUTE
0x40 15 = TAB
0x53 102 = HOME
0xbc 23 = I
0x26 103 = UP
0x28 108 = DOWN
0x25 105 = LEFT
0x27 106 = RIGHT
0x0d 28 = OK
0x1b 1 = ESC
0x49 139 = MENU
0x4e 115 = VOL+
0x56 114 = VOL-
0x54 38 = L
0x52 164 = PAUSEPLAY
0x41 104 = PAGEUP
0x42 109 = PAGEDOWN
0x31 2 = 1
0x32 3 = 2
0x33 4 = 3
0x34 5 = 4
0x35 6 = 5
0x36 7 = 6
0x37 8 = 7
0x38 9 = 8
0x39 10 = 9
0x30 11 = 0
0x44 14 = BACKSPACE
0x58 24 = O
key_endYou could check here kodi shortcuts
https://kodi.wiki/view/Keyboard_controls
For Home use KEY_HOMEPAGE code
For MENU KEY_C code (or KEY_M, check hotkeys)
For TAB I don’t know action what you need, Fullscreen is not used. (check hotkeys)
Key codes are here:
1 Like
Thanks, boot2k3. I’ll try out your suggestions. The TAB (full screen) key is useful for an add-on such as USTVNow Guide which has a picture-in-picture mode so that a user can access the program guide and watch the current channel simultaneously.
Actually, with meson-ir you are not limited to any protocol (lirc should know all major ones). I am using existing home remotes (VHS, DVD players, etc.) whole time since first use OpenELEC.
I have zero experience with amremote (I skipped Kodi 17 as it wasnt mature enough), but I am using lircd for years, and - at least with Odroid C2 - meson-ir implementation is in quite good shape, it works without hickup the same way as with lirc-rpi overlay @Rpi. So I am glad its default method.
But I really glad CE devs does good work to implement another IR option and most importantly allows users to set which they prefers 
@XRNote5 where are you saving your remote.conf?
Can you paste the output of /tmp/remote.conf, thanks.
Sorted! Thank you all for the support!
1 Like
@anon88919003 I copied my remote.conf file to the “Configfiles” folder through the CoreELEC Samba share and then restarted CoreELEC for the changes to take effect. Is the file at the location that you’re asking about accessible through Samba as well?
UPDATE: I formatted my memory card again tonight and did another clean install of CoreELEC 8.99.2 followed by some further testing with my original remote.conf file as provided above. It appears that the MENU key is the only one that’s actually unresponsive. The HOME key appears to function but TAB results in something that is not the full screen function but possibly ESC or BACKSPACE instead. I found this post at the LibreELEC forum which describes the TAB key issue in more detail.
Yes, however I can not help you further without the information I asked for previously.
The key codes have changed in Leia as opposed to Krypton as @boot2k3 explained in his post above, it is relatively easy to correct your remote config.
ie, change 0x53 102 = HOME for 0x53 172 = HOMEPAGE
I’ll need some time to figure out how to access the remote.conf file in the /tmp folder because doing so seems to require a more technical method such as SSH which I’m not very familiar with. If you can post some specific instructions here for me to try with PuTTY, that would definitely help me out.
@anon88919003 I figured it out. Here are the contents of the file that you asked for.
CoreELEC:/tmp # cat remote.conf
#amlogic NEC remote
factory_code = 0x7f800001
work_mode = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay = 20
debug_enable = 1
key_begin
0x51 31 = S
0x4d 113 = MUTE
0x40 1
0x53 172
0xbc 23 = I
0x26 103 = UP
0x28 108 = DOWN
0x25 105 = LEFT
0x27 106 = RIGHT
0x0d 28 = OK
0x1b 1 = ESC
0x49 139 = MENU
0x4e 115 = VOL+
0x56 114 = VOL-
0x54 38 = L
0x52 164 = PAUSEPLAY
0x41 104 = PAGEUP
0x42 109 = PAGEDOWN
0x31 2 = 1
0x32 3 = 2
0x33 4 = 3
0x34 5 = 4
0x35 6 = 5
0x36 7 = 6
0x37 8 = 7
0x38 9 = 8
0x39 10 = 9
0x30 11 = 0
0x44 14 = BACKSPACE
0x58 24 = O
key_endThe two changes which you’ll notice are the automatic substitution of the HOME key with HOMEPAGE and the TAB key with ESC (the second of which is the bug that the user on the LibreELEC forum mentioned in the link I provided).
That’s not a bug, it’s done by design, upon booting non-working keycodes are rewritten, as you have discovered it has been that way for a long time.
Please do not say something works in LE and then not in CE when that is clearly not the case as demonstrated in the link you pasted.
I sincerely apologize for the confusion in that regard. I should have mentioned in my original post that I was able to get the TAB key to work properly in LibreELEC only after using an autostart.sh file that contains the following code:
#!/bin/bash
(/usr/bin/remotecfg /storage/.config/remote.conf)&
exitWhen I use the same autostart.sh file in CoreELEC, I’m noticing that the TAB key no longer functions as ESC. I’m going to make the simple remote.conf changes that you and boot2k3 suggested and put this to rest.
That would make sense as you are then configuring your remote with the original remote configuration file that has not been remapped by our scripts.
1 Like
Yes, exactly. Thank you for your quick responses and clarification. It’s been a learning experience for me.
So today i had time to check why my remote again did not work and discovered this thread.
I am glad that amremote works again because there you can use two remote controls (means the original remote control and a better one with more buttons) at the same time and with meson not.
Unfortunately i still had a remote.conf in my config but with different settings (for the previous configuration of my harmony remote control) and it was used suddenly again it seems.
So i have to reprogram my remote control again to be able to use all keys and poweron/poweroff because the poweron/poweroff ir signal is hardcoded to the original remote control in the bootloader but if you want to use another remote control it has another ir code for poweron/poweroff.
I hope this will not be changed in the next update again.
Thanks for the ongoing support of amlogic s9* based tv boxes !
How so? You can use include statement within lircd.conf, and include more remotes by clean and nice way