You are welcome.
Perhaps there's a typo and CTRL+C should be there instead of just +
So if everything is already working fine, please mark the thread as resolved.
You are welcome.
Perhaps there's a typo and CTRL+C should be there instead of just +
So if everything is already working fine, please mark the thread as resolved.
Don't try to do many unnecesary things...
It looks you did not use the -a parameter properly. After any change in mapping file ( /storage/.config/rc_keymaps/custom_remote ) do this to save the changes permanently:
systemctl stop kodi
systemctl stop eventlircd
ir-keytable -a /storage/.config/rc_maps.cfg -s rc0
systemctl start eventlircd
systemctl start kodi
Of course in your /storage/.config/rc_maps.cfg file you need to have this line:
gpio_ir_recv * /storage/.config/rc_keymaps/custom_remote
Test with
ir-keytable -t -s rc0
while pushing RC control buttons to check if you are receiving scancodes (need to have the appropriate RC protocols enabled, for example ir-keytable -plirc -pnec -pRC5 -s rc0 )
Then use
irw
to test the key mapping.
It looks that support for Stereoscopic 3D mode was added (a 'glasses' symbol in Kodi Player) but it makes trouble with some Live TV channels on my RPi 4B.
The issue was observed with one Live TV H.265 channel at 1280x720 px Video stream, 1.78 AR, 50.000 FPS which is flickering (never seen that before).
The same issue is also with H.265 1440x1080 px stream (The Display resolution is 1920x1080)
When I tried to play with 'glases' or 'wheel / Video' settings, the only change I could make was to achieve a black screen with audio. It was not possible to disable the 3D mode so the channel is not viewable.
Other channels (with H.265 streams 1920x1080, 960x544) are working fine.
Edit - it looks I have turned on the Stereoscopic 3D mode when I tried to stop flickering and it's not easy to get away the 'glasses' from the bar...
Nevertheless, so far I could not fix that annoying issue...
Edit 2 - When the issue happens (currently a black screen), one CPU is running at 100%. At random intervals, this 100% load moves to some other CPU, at that switch moment a picture snapshot is displayed for a moment and audio is interrupted for a moment.
I have also tried to record the stream and open recording afterwards - the same issue...
I believe with WinSCP client ( WinSCP :: Official Site :: Download ) the necessary file transfers between Windows and LibreELEC are also as easy as can be...
1) I would say NO, at least NOT the device you mentioned above because IrDA/USB Bridge purpose is 2-way data transfers between IrDA devices (mostly in past) and AFAIK in general it's a quite different protocol than any of IR remote control protocols. Maybe some IrDA devices can be also used as IR RC receiver but I don't have any experience with this and it may vary. See Infrared Data Association - Wikipedia versus Remote control - Wikipedia
2) On RPi 4B it's not a big difference between Raspberry_Pi_OS and LibreELEC (with the same or similar kernel release) regarding to IR remote control configuration, you just need to use the proper config files / config files paths in LibreELEC as some default files are in read-only filesystem and you need to put the files (that you need to edit) to override paths as described in wiki here: Infra-Red Remotes - LibreELEC.wiki
Everything is working fine on RPi 4B / LE 9.2.6 so just read carefully and follow the instructions.
The simple IR sensor can be used on RPi through GPIO pins.
The /flash/config.txt update you have done should be OK, although I would put a pin number there:
dtoverlay=gpio-ir,gpio_pin=18
You may change the GPIO pin, GPIO18 is a default when not specified.
Connect the IR sensor's data pin to GPIO18,, Vcc to 3,3V, GND to GND, reboot the RPi and use ir-keytable to configure / map keys in accordance to wiki examples. That's all.
Also don't forget to update the RPi's bootloader to some of recent versions (at least directly from LE 9.2.6).
In case you still won't get a reply from ir-keytable similar to example below, your LE installation is probably screwed up somehow and consider to start with a fresh LE 9.2.6 installation:
Found /sys/class/rc/rc0/ with:
Name: gpio_ir_recv
Driver: gpio_ir_recv
Default keymap: rc-rc6-mce
Input device: /dev/input/event1
LIRC device: /dev/lirc1
Attached BPF protocols:
Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm
Enabled kernel protocols: lirc nec
bus: 25, vendor/product: 0001:0001, version: 0x0100
Repeat delay = 500 ms, repeat period = 125 ms
At first, I would read here and try to follow the instructions: HOW-TO: provide bug-reports
In general, it's easy to make the IR receiver working on RPi 4B using GPIO and IR sensor.
At first, you need to enable it - put this line to /flash/config.txt file (read only by default, remount as RW before edit):
dtoverlay=gpio-ir,gpio_pin=18
You may change the GPIO pin, GPIO 18 is a default when not specified.
Then connect the IR sensor's data pin to GPIO18, reboot the RPi and use ir-keytable to configure / map keys as described here: Infra-Red Remotes - LibreELEC.wiki
Well, I don't think that Libreelec is a root of your trouble... Instead, it sounds like your USB multi-HDD box (in fact it's probably not a NAS, which means Network Attached Storage) maybe generates some high-frequency noise which may interfere with your WiFi network. I don't know how your device looks like exactly, it might be the external Power Supply of that box... It should have a metal shielding inside, under the plastic cover, but there are some cheap products that don't respect any construction rules... Don't know if it's the case but maybe yes... And it's possible it may change over the time due to parts degradation, especially capacitors... Also a different WiFi devices may have a different sensitivity to a noise or a too low power to overcome it..
Try to move the devices a bit or try to make a temporary shield to your USB box / box power supply using aluminium foil (carefully, I do NOT mean to open the boxes!) and check tf there's any difference.
I am afraid currently NOT, unfortunately.
AFAIK Kodi does not support a second display on LE / RPi 4B.
Tried already on LE 9.80 Nightly couple months ago (want to use a second display for camera stream) but failed... Only 1 of 2 HDMI ports can be used for video output, but audio can be switched between 2 HDMI devices connected at the same time.
I believe the upgrade from LE 8.0.2a should work to LE 9.2.6 stable but test at your own risk.
Don't forget to make a backup of your current installation first.
Then read here: Updating - LibreELEC.wiki
Use the proper file path to upgrade (file which is appropriate for your device).
Edit: OK, sorry for misleading, see the post of chewitt below... ;-/
Yeah, it's already back and working!
chewitt & all, thanks a lot for your quick reply & fix.
Not exactly what you are asking about, but... With a proper key mappings you can use for example something like:
kodi-send -a "ActivateWindow(Music,/storage/music)"
I like using irexec for a such cases so it should be possible to remap the KEY_YELLOW button.
Look here for examples: RE: Remote Control
I have just upgraded LE 9.80 Nightly from 20210116 to 20210117 with Kodi 19 RC1.
Unfortunately the PVR Tvheadend HTSP Client 8.1.2.1 was disabled as incompatible and can't be upgraded easily (No updates available | There are currently no versions available for this add-on).
It seems that PVR clients choice disappeared from All repositories list.
Should I be able to install the compatible version somehow (a search for an appropriate .zip file failed) or need to wait?
I would try to boot from an USB Flash key (or USB/SATA adapter) instead of SD card.
Make sure you have a fresh bootloader / VL805 firmware installed, you may also need to tune up the bootloader options.
Read carefully here (including all links published there): Raspberry Pi 4 libreelec not booting
I have alreay put an advice there.
Did you follow the link I have published and tried at least one from 2 solutions mentioned there?
It seems to be a bit complex and won't work in LE without modifications for sure.
Forget that and try this instead: RE: Shutdown on single button press
Read carefully till the end as there are more options to try.
Exactly. The current bootloader configuration should do what you requested. Just try and you'll see.
Well, I tried to make the description of the procedure as simple as possible above (including the commands which you just need to run) and I almost don't know how to do it even easier ...
Are you at least able to connect to your RPi / Libreelec via the SSH console?
If so, do it, then copy and paste these commands to SSH console and put the responses here:
rpi-eeprom-update
vcgencmd bootloader_version
vcgencmd bootloader_config