OK, I have a different HW so also the drivers may be different. I have no lirc.conf file. But I would check with the irw utility if your scancodes are mapped properly to commands. And if not, check the /storage/.config/rc_maps.cfg file and the mapping file which is the rc_maps.cfg pointing to.
If you don't have these files on your filesystem, then 
.
Some IR RC's are sending two different scancode numbers when you press the same key (check it with the ir-keytable -t command ).
This must be reflected in the key mapping file (to include both scancode numbers for the same action) otherwise you experience the described 2nd key press... So I would expect your keymapping file does not fully match your RC model and needs to be updated.
It may depend on Add-ons used. Try to discover the process which is eating memory, for instance with top command in SSH console.
I am using Tvheadend server which sometimes starts consuming memory quickly until terminated by OOM killer.
Yeah, wish config.txt would be stored / restored.
See this nice example: RE: How to make a backup of kodi?
So you can make your own backup script which looks like:
#!/bin/sh
# fullbackup.sh script
set -e
tar cf /storage/backup/$(date +%Y%m%d%H%M%S).tar \
--exclude=Thumbnails --exclude=.thumbnails \
/storage/.kodi /storage/.cache /storage/.config \
/storage/.ssh /storage/*.* \
/storage/picons/ \
/flash/config.txt /flash/cmdline.txt
# find /storage/backup -name "*.tar" -type f -mtime +15 -exec rm -f {} \;There are some additional folders / files added to be saved, like /storage/picons/ , /storage/*.* , /flash/config.txt and /flash/cmdline.txt .
For restoring you can use standard Restore Backup from Kodi's GUI menu Settings-LibreELEC-System-Backup
But currently you need to put the mount -o remount,rw /flash command to SSH console before restoring. Then the /flash/config.txt and /flash/cmdline.txt files should be restored as well.
I don't think so, see the post #3. Yes the original backup writes just some folders from parent /storage but if you make your own backup script, it's up to you. But the original restore can't restore to read only folders.
I have made an extended backup script which also stores the /flash/config.txt file.
The standard Restore Backup from Kodi's GUI menu Settings-LibreELEC-System-Backup works but the /flash/config.txt file is not restored as the /flash folder is mounted as r/o by default.
I believe it would be useful when the restore part of the official backup-restore script could contain the mount -o remount,rw /flash command before tar command (between lines 33 and 34).
Use an adhesive non-transparent tape... 
This most simple solution works with any LE version.
The same issue with LE 11 Nightly 20221113-ba9b18d with 6.08 kernel release.
After swapping the DVB-T2 sticks between RPis the issue also moved to second RPi.
So it really looks the old issue with MyGica driver is back ( https://github.com/raspberrypi/linux/issues/3809 )...
[94294.049273] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1
[94312.854527] rpivid feb10000.codec: rpivid_h265_stop
[94330.842402] usb 1-1.2.3: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110
[94332.972344] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94335.105740] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94337.239067] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94339.372393] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94341.505730] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94343.639086] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94345.772448] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94347.905776] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94350.039089] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94352.172489] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94354.305851] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94356.439164] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94358.572524] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94360.705877] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94362.839322] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94364.972578] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94367.105931] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94369.239271] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94371.372633] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94373.505960] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94375.639354] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94377.772695] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94379.905980] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94382.039373] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94384.172775] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94386.306125] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94388.439421] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94390.572768] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94392.706116] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94394.839450] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94396.972827] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
[94399.106261] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110
....
....
Thanks a lot for info, you are right. But now (with DRM Prime disabled) I am experiencing a temporary screen flickering after the switching live TV channel to another. But screenshot works fine now.
If the ir-keytable command does not return any output, it looks your IR receiver USB stick is not supported by kernel and appropriate driver is missing.
If that's the case, with RPi 4b you can easily use the gpio-ir overlay which allows to use any IR remote including yours (just a cheap IR sensor is needed instead of your USB stick).
BTW. I own the same-looking IR remote and the protocol is rc6_mce , FYI.
LE10 (stable) and LE11 (stable but still pre-beta) images can do everything that LE 9.2.8 can do.
Perhaps not an important feature for most users but the screenshot command still does not work in LE 10/11 (it does not save the screenshot picture like in release 9.x but only the active GUI screen).
Currently the second HW configuration works better, I think the last issue was encountered 9 days ago as reported here.
In the meantime also the EEPROM on both RPi's was updated to 2022-10-12 release.
It looks to me like the old issue with MyGica driver is back ( https://github.com/raspberrypi/linux/issues/3809 )...
I'll try to swap DVB-T2 sticks between RPis to see if there's any change / if the issue transfers (despite it's more dangerous for the configuration which boots from USB ).
The same issue with LE 11 Nightly 20221022-7fb1002
[101093.491670] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101095.625218] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101097.758675] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101099.892185] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101102.025683] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101104.159168] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101106.292724] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101108.426156] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101110.559630] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101112.693203] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101114.826629] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101116.960112] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101119.093620] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101121.227110] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101123.360567] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101125.494044] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101127.627568] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
[101129.761016] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-110
This issue makes the LiveTV unusable in my case. 
It happens most often after switching channel, often during Timeshift moving and sometimes completely randomly.
Thanks for the comment / shared experience. It looks to me like the internal player tries starting play the stream too quickly, before detecting the live stream's parameters safely / properly (at least regarding to audio and subtitle tracks).
I don't know if it really make sense from technical point of view but it looks to me it's like that. Because both described issues happen with live stream but not that bad with the same recorded stream.
I have no idea if it's possible to try some configuration changes in Kodi / LE to improve that behavior or not...
Thanks again for your time & analysis.
Yes I have both Tvheadend servers 4.2 and 4.3 installed, 4.2 disabled a long time ago and currently using 4.3 (despite the another issue with subtitles as reported long time ago in another thread). I supposed the 4.3 should be the release with active development progress (in opposite the 4.2 as developers usually stops development of older versions). Unfortunately my issues still persists.
The old stream samples / logs really had the transport errors due to weak DVB-T2 signal. This is not the current problem, the issue with "missing" audio stream happen even though the signal is perfect, just after switching the DVB-T2 channel to another one. Looks like some timing issue or whatever similar... Don't know how the stream parameters are recognized but for sure it's done just one time after the play start (or maybe again when the stream is interrupted temporarily). And this one-time detection of audio sometimes fails (at least in my case).
Yes if the signal is bad, the audio is sometimes lost during the LiveTV watching and sometimes can't be recovered for long time or ever (or until switched to another channel). But when the same (bad) stream is recorded, when I play the same recording, audio is recovered quickly (after the interruption point). The issue is with the live player (don't know / understand a difference between live and recordings play process). The same difference with subtitles that won't show on some channels during LiveTV watching using Tvh 4.3 but visible from recordings of the same channel (subtitles works on all live channels with Tvh 4.2).
Thanks for the feedback. Regarding to configuration - most info s in the post #1. There's Tvheadend server 4.3 running. Latest add-ons available installed.
I think it could be related with AAC stream (used in our country and perhaps it's not widely used around the world so maybe that's the reason why nobody else encountered the same issue) which is not always detected properly by the layer responsible for LiveTV stream play.
I don't plan to try testing with Tvheadend 4.2 as with this random issue it would be just time wasting.
I don't think the issue ever happened with stream recording so the stream itself should be OK (need to say I use recording in rare cases).
Why the hell the player can't sometimes detect the live audio stream properly?
The same issue with LE 11 Nightly 20221015-6352186.
Currently I see the issue most often after TV channel switch (even though the DVB-T signal is perfect) when some (working) audio streams are not detected at all.
