Krypton style IR remote configuration is back!


#23

I have a Sammix R95


#24

@boot2k3, apologies for the delay in getting back to you (traveling)

Here’s the output of those commands:

CoreELEC (official): nightly_20190125 (S912.arm)
CoreELEC:~ # ls -l /flash
total 150444
-rwxr-xr-x    1 root     root     154013696 Jan 26 07:08 SYSTEM
-rw-rw-r--    1 root     root         16919 Dec  8 23:57 boot-logo.bmp.gz
drwx------    2 root     root         16384 Jan 14  2018 lost+found
-rwxr-xr-x    1 root     root          3257 Jan 14  2018 remote.conf
CoreELEC:~ # fdtget -t s /flash/dtb.img /meson-remote/ status
Couldn't open blob from '/flash/dtb.img': No such file or directory
CoreELEC:~ # fdtget -t s /flash/dtb.img /meson-ir/ status
Couldn't open blob from '/flash/dtb.img': No such file or directory

Thank you,
anthonws.


#25

I’m trying to create a remote.conf from scratch using the link provided above, but I keep getting hung up trying to set the factory code.

I created the blank config file then change the factory code as instructed, but it doesn’t work. Here’s my output from ssh.

https://pastebin.com/vXmFLeWC

Do you notice anything I’m doing wrong?


#26

@anthonws your problem is you haven’t followed the installation instructions properly by not creating a dtb.img.

Couldn't open blob from '/flash/dtb.img': No such file or directory

The automatic remote switching only works if you have a dtb.img.

@the-dude try the following config here


#27

Thanks for searching for remote.conf files for me. Sadly that one didn’t work for me.

Somehow I got the remote to work though. I’ve been trying meson-ir configs, remote.conf files and at some point after a reboot a remote.conf file showed up in the /flash folder that works. I’m a bit confused how it got there, but I’m able to edit it on a Windows machine to my liking. The file was set up for three different remote codes and one then works great. I cleaned up the code and deleted the unused remotes code.

Maybe if I put my remote.conf file in that location in the first place it would have worked. I was using the /storage/.config location.


#28

Either folder will work fine with the same end result.


#30

Hi @adamg! Appreciate the reply. So, even though this was a “in-place upgrade” using the nightly channel, I still had to use the dtb.img? Because I did used that when I originally installed Libreelec (and then upgraded to Coreelec).

Cheers,
anthonws.


#31

I don’t know how you upgraded from LE to CE because it is not possible but from your previous post I can also see you have no device_trees folder so I can only assume that you deleted it.

You can use mount -o rw,remount /flash and copy the device tree for your device from /usr/share/bootloader/device_trees to /flash/dtb.img and it should resolve your issue.


#32

Does anyone know if there is an existing list of conf files out there to choose from? Thought I would ask before sitting down to figure this out. I believe my box is somewhat popular - MECOOL M8S Pro+


#33

remote.conf repository


#34

Exactly what I was looking for with no luck. Thanks!


#35

You can extract the remote.conf from the Android image for your device, it will be inside /system/etc.


#36

I’m trying to use my remote.conf from librelec but menu button doesn’t work in CE
I’ve put remote.conf to .config, reboot (rebooted twice as it should)
dmesg gives the same output in CE and LE:
[ 175.850831@0] remote: press ircode = 0x49,
[ 175.850874@0] remote: scancode = 0x008b,maptable = 0,code:0xb6497f80
[ 175.850922@0]
[ 175.966708@0] remote: release ircode = 0x49,
[ 175.966750@0] remote: scancode = 0x008b, maptable = 0,code:0x00000000
[ 175.966789@0]
but in CE nothing happens.
Do I need to use different codes in CE?


#37

Use KEY_C or KEY_M(don’t know what exactly action you need) instead
https://kodi.wiki/view/Keyboard_controls


#38

Thanks, KEY_C works.
What code could I use for Ctrl+Shft+O (for CodecInfo 2)?


#39

Hi @adamg, I did as you instructed, but the remote is still not working :confused: Any more ideas?

Cheers,
anthonws.


#40

Paste the output of the following commands please

ls -l /flash
ls -l /storage/.config
fdtget -t s /flash/dtb.img /meson-remote/ status
fdtget -t s /flash/dtb.img /meson-ir/ status

#41
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

#42

I can see remote.conf right there on /flash. Rename it or delete it and try again.


#43

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.