I built an IR receiver using an arduino pro micro that emulates keyboard presses.
It’s more responsive than the X96 X10 remote, but still not as sensitive as the proper MCE usb receiver.
@Portisch AV1 works using the nightly! Thanks!
Unfortunately Dolby Vision isn’t working now though.
On startup of CE, I got a message saying I needed to upgrade the kernel to 5.15.137 or over for Dolby Vision to work, so I started from emmc and checked for updates using the FOTA Update and System Upgrade apps, but both of them said I was up to date.
Is there any solution to get Dolby Vision to work again, or am I stuck waiting until X96 releases a kernel update?
@vpeter Can I ask what the process is if I want to update from the nightly to the latest nightly later on?
The Dolby Vision module is proprietary software, it’s the user’s responsibility to copy it to their device for DV playback.
If you aren’t satisfied with the IR functionality of the X10, buy a BT USB dongle for $5-10 as was previously recommended. IR is directional, and the receiver is what it is. Other devices have multiple receivers, receivers with lens, receivers that are exposed, etc. There’s a lot of reasons why IR responsiveness might be better. It’s a hardware issue, not a software issue, not much can be done.
Thanks a lot!
I will try the dovi.ko tonight.
Yes, I’m not going to use it. I was just mentioning it for people who might be considering an X10, just for their info so they are ready to use something else.
I have a BT G20s with a dongle that works and is better than the crappy X10 stock remote, but my preferred remote is a HP MCE Remote with a lot of extra keys, but to use that, I must use IR.
Did you try using the MCE remote with the X10 IR receiver? You’d need to delete the remote.conf file, then reboot. That will load the meson-ir driver, I think there’s an MCE profile.
Alternatively, plug in the HP MCE USB IR receiver and use that with the MCE remote.
I did try the MCE remote with the X10 receiver and it was very insensitive.
I haven’t tried the MCE receiver with the X10 yet.
Will try that later on, but I currently have it connected to my Linux HTPC that uses LIRC to run scripts to control the volume of my AVR over telnet using netcat, as normal volume control is super slow - 0.5dB per step, so I use the script to send three volume changes per button press.
If the MCE receiver works with CE then I will need to work out how to replicate this behaviour from CE.
Probably getting offtopic but if anyone can point me to some info how to run a custom script from an MCE remote connected to CE, I’d be eternally grateful.
I think there’s a way to run external scripts from Kodi, but not sure if that would work from CE?
edit: I’ll have a look at Physical button execute script and Keymap System.Exec(exec) problem - General Support - LibreELEC Forum tonight, looks like what I need.
Just plugged the MCE receiver in and it worked perfectly immediately.
My compliments to the devs!!
In CoreELEC, I use scripts to control my Home Assistant, which allows me to toggle lights, curtains, and more. It can also handle AVR HDMI signal switching via CEC. You can use the Keymap Editor plugin to assign functions to your remote buttons. For example, my power button (code: 61662) triggers the cec-movie.py script when pressed. This script first switches the input to HDMI1 (CoreELEC), then sends a ‘Movie Mode’ notification to my Home Assistant.
You can first map your desired remote buttons to any action using Keymap Editor , then locate gen.xml and modify the action commands to point to your custom scripts.
<keymap>
<global>
<keyboard>
<key id="61662">RunScript(special://skin/extras/cec-movie.py)</key>
</keyboard>
</global>
</keymap>
Thanks, it was a bit of a marathon but I got it working in the end!
X96 X10 8Gb, running CE nightly…
When I turn off the TV and the box gets suspended via CEC, when it resumes there is no HDMI output.
If I ssh into it and systemctl restart kodi, then the output comes back.
I’d rather not shut down the box because then it won’t come back via CEC.
Is there any way to get it to resume properly from CEC and reenable/refresh HDMI output?
Edit: and today it worked properly… weird.
Actually, it is unreliable resuming.
Today there was no HDMI output, I had to reboot the box to get it to come back.
CeC seems to be hit n miss with some boxes,CoreELEC/also your TV CeC settings can be a factor.
I have no issues power on /power off with TV remote
Or using Generic ir remote (cheepoo,with 4 year old remoteconfig),and default settings in CoreELEC CeC
With TV remote power on/powers on the X96X10, on HDMI 1,sometimes have to use source/inputto select HDMI port,or i use Google Voice/Hey Google go to HDMI 1,X96X10 power’s up.
With generic cheepoo power off /turns TV off,and X96X10
Power on /turns X96X10 and TV on
My experience with standby on any device is that it is never reliable. However I dop have the same experience as @freddy and my x96 x10 can power up the bootoeader by IR using the power button code on many generic NEC Amlogic boxes over the last couple of years. You can test your remotes by ssh to see if you have a matching IR.
systemctl stop kodi
systemctl stop eventlirce
ir-keytable -u
Protocols changed to irmp
Waiting for IRMP decode event. Please, press CTRL-C to abort.
Received IRMP code: remotewakeup='0xbf40fe01', decode_type='0x0', remotewakeupmask='0xffffffff'
1 Like
Thanks, I will check.
It does wake up from the IR remote or CEC, as I can connect to it by ssh.
It’s just that sometimes when it resumes, the HDMI seems to not be outputting anything. That is bad for WAF.
I haven’t tested yet, but I believe if I get it to shutdown instead of suspending, then it will not be able to turn back on by CEC. I’ll test that out soon.
Another slightly annoying thing is that on the times the HDMI doesn’t resume, when I connect by ssh and reboot or systemctl restart kodi, it turns the TV off! I presume the stopping of the kodi service automatically sends the CEC off as it would normally.
Is there any way to prevent it from sending the CEC off when you reboot or restart kodi from ssh?
I tried that last night.
I was trying to get the power button on my MCE remote to work to boot the X96 X10. I believe it shows up as KEY_SLEEP in kodi.log.
I renamed the remote.conf to remote.conf.disabled, then did that as you described and got:
Received IRMP code: remotewakeup='0x800f040c', decode_type='0x5', remotewakeupmask='0xffff7fff'
Then I did
cd /storage/.config
cp rc_maps.cfg.sample rc_maps.cfg
to disable meson-ir for the inbuilt IR receiver because I get double presses because I have a USB MCE receiver.
There’s no codes uncommented in rc_maps.cfg.
Then I put those codes into config.ini:
mount -o rw,remount /flash
vi /flash/config.ini
sync
reboot
But I can’t get it to boot from the MCE remote using IR. It does still boot from the original crappy remote and via CEC though.
What am I doing wrong?
Edit: actually, from reading coreelec:irwakeup [CoreELEC Wiki] , the S928X is not listed as having that BL301 blob, and the “IR Remote Power Code” option does not show up in the Coreelec menu, so I guess it is not supposed to work.
Is it actually possible to get the X96 X10 to boot from the IR power button on my MCE remote??
It’s not a big deal though. I am very happy with this box. It plays everything I throw at it and is quite fast.
Thanks so much to the CoreELEC geniuses!!
You can’t remap the x96 x10, the bootloader has a fixed IR code as you found out. You need to check to see if you have another remote that has it and if your MCE remote as any learning keys, use that. I gave up on the MCE remote years ago, there are too many good USB-HID and BT remotes with the same number of keys that don’t need line of site and have learning keys too.
Martin
1 Like
Unfortunately I don’t think the MCE remote has any learning keys.
It’s not really a big deal especially because CEC works. It just would have been perfect to be able to do everything from the one remote, and having to keep the crappy factory remote around only to boot it would be less than ideal.
If I really want to get complicated, I could make an arduino receiver to receive the MCE IR power message and use an IR LED to send the IR X96 remote wake up message.
Would be better if the box had a power button or I could use a GPIO to wake it up.
But if I can’t change the IR wake control, I don’t expect it’s possible to change it to wake from GPIO either.
Wake on lan doesn’t seem to work on my X96 X10 even though it’s listed as enabled in the coreelec menu, is there anything I can do to to fix it?
Of course the box is plugged into ethernet.
Working here from standby but not power off. I don’t know if the bootloader supports WOL or Ethernet.
That’s what I found too. Damn.
Thanks for testing.
It’s a little odd that it can wake from CEC but not wake on lan. I guess CEC is what consumers generally use though.