I took a backup, did a fresh install with the latest .img, restored the backup, and it's happening again.
Hi, probably in your old setup it's something that not compatible with the new version. I would try to make a fresh install, add the addons and settings, and from backup to use only the other stuffs, like media files.
That Radxa Dragon Q6A hardware looks pretty nice. Qualcomm 8 core CPU, Adreno GPU, onboard M2 NVMe (2230) slot, "normal size" HDMI connector... Would be nice to have LE for it in the future. Could be a good alternative for Raspberry.
Hi, I think this needs enabled in the config.txt:
# uncomment to enable analog audio output
#dtparam=audio=on
#audio_pwm_mode=1
CRTs have better motion clarity than any "flat display" because of the way it refreshes the image (electron beam). Certain things just look objectively better on a CRT (mostly retro games but also some TV shows if they were released with an interlaced format).
I know well those CRT displays, I repaired enough decades ago. The phosphorescent layer make the image softer, but the quick movements often looks "washed" because this.
Telling a CRT user to switch to a current HD display is like telling someone who plays Doom to upgrade from Win95 to Win11 because Win95 is "outdated" when Windows 11 doesn't even have a DOS mode anymore. Certain things were meant to be used in a certain way.
I have no problem with people who like the CRT displays. And usually isn't a problem to connect a CRT to an old video source (like Doom with Win 95). When you want to connect a CRT to a "new" video source, it's another story. Needs "things" to be able to connect (like that vga666 project - GPIO pins with 6 bit resistive DAC to get some kind of analog RGB), resolution incompatibilities. Usually workaround exists, sometimes good, sometimes barely working...
The EDID "explain" what resolutions are supported by the display. If in the settings would be added some other (possible unsupported) resolutions, for other users could lead to blank screen and a lot of complains. At the other hand, if these resolutions it's added in the settings or coming from a modded EDID, probably wouldn't change anything. Instead of this, you should provide more informations about your "audio issues", maybe can be solved in other way, or check that modified "Player" and "System/Display" settings.
my PI is still in version 10
Hi, it's RPi, the SD card can be swapped in seconds. If your RPi it's working well with the LE10, remains the question if you want or need to upgrade or not. Otherwise you can grab an another card and try the new LE. It's need some time till all settings and addons resolved, but if you have the old setup on another card, anytime you can switch back to the old the version.
With TVhead it is complicated...
I seen here how can be moved the TVheadend 4.2 setup to TVH4.3, didn't tried. Otherwise a fresh setup is always better, and to spend some time once after few years, I don't think to be a too big sacrifice.
The same setup works when connected to a PC Monitor via HDMI.
Hi, to simplify that "EDID" story. The EDID data is a small amount of data written usually in a small memory chip in the display. This data "explain" the display what type of image can handle. If with same video source (your RPi4B) and HDMI cable, another display working (and in the Kodi display settings do you see few different resolutions), the EDID issue (if exist) probably is in that "Toyota Sienna display". Even for this could be a workaround. If that display support any kind of "standard" resolution (you mentioned the 1280x720), check if your another (working) display have the same mode available. If yes, connect the "working" display, run in SSH the "getedid create" command, set the resolution to be compatible to the "Toyota" display and try it. If you ar lucky, and till the resolution will remain unchanged (should use the video mode white list to enable only that) you will be able to use it.
And why sometimes the diplay "working" even without EDID data? That depend on how is programmed the video source device to handle the missing EDID, maybe will provide a low, standard resolution (and most of the displays will display something) or just disable the output...
"I wanted to upgrade my LibreElec to the latest build (from build 10.0.0.4 / Git:19.5-Matrix) to: LibreELEC 12.2"
Hi, sorry for off topic, but maybe could be useful.
When somebody downloading the LE image, to be raised a big warning window. Something like to have a backup before update and the successful upgrade between versions isn't guaranteed and recommended.
Maybe would be less complain after a hasty upgrade.
Even the 3 wire solution seems to come with a whole heap of SW issues to get it working its doesn't just seem like plug and play.
I'm using this type of IR receiver for years and didn't had any problem. Your remote looks like it's a MCE RC6 one, that code is the default supported by LE. So for that remote to work with RPi, you need the "3 wire solution" and in the config.txt enabled the line with "dtoverlay=gpio-ir,gpio_pin=18". That's all.
Hi, if you have a bit of experience in electronics (or know somebody), you should use google to search for "RPi IR receiver". A single cheap component, 3 wire, and no more problems with the USB receiver.
Hi, you should look here: kodi wiki smb
"When SMB v1 was deprecated by Microsoft due to security reasons, it was no longer possible to browse SMB shares. Instead it required you to add the specific IP Address or Device Name followed by the path to access shares. (detailed in the next section)"
Ok.. any suggestions as to the device to reprogram it to?
I've never had or used a MCE remote, and the MyHarmony software is looking for a manufacturer/device combo
I'm using HP MCE remotes for all my RPi+LE devices, like this: HP Remote if this could help you.
Audio always on HDMI1 but video on demand, either HDMI 1 or HDMI 0 .
Hi, Looks like you should use an external HDMI switch. Isn't the best solution... but if no other solution...
You understand me correctly, but I don't want to switch my daily driver to the nightly version for two reasons: One, I want to use the stable branch so that I don't have to deal with stability problems, and two, I think it's useful to keep debugging this so we may identify the bug, and stop it from popping up again later.
I'm using LE nightly builds for years, am my experience, the fixes are includes more quickly in the nighlyes. I don't update the nightly at every new version, just after few weeks maybe, and feel more stable than the "stable" release. For me that's only a label. 
Your choice, wait till this will be fixed in the next "stable" build, or use the LE 13 nighly where already it's working well...
Still want me to test?
If I understand correctly, the LE13 nightly working for you without issue. In that case why you don't just switch to that?
Hi, probably isn't the best solution, but if nobody else with anything better...
As your device is a miniPC, you could try to boot a live linux from USB and backup your data (will be on an ext4 partition, and look for the "userdata" folder, or anything else if you have). In this way you can check the hardware too.
Run the LE from USB (select "live" at installer screen), so maybe you can try first if the newer versions of the LE working on your device... If working in the live mode, try to install it and use the files from backup to restore your data.
Hint: if you don't want to rewrite many times your USB stick for different installers, check the Ventoy project. Working even with the LE image (I tried in "live" mode), just unpack the LE "img" file somewhere to the USB stick after the Ventoy installed.
The cable is the same one that worked for years in the same Rpi4.
Every hardware fault start with "till yesterday works well"... Just try with a minimal setup: new image without any modification, HDMI cable connected to directly to display. If you can, try with another cable, display.
It's a very large number of people (including me) using their RPI4 and LE without sound issue.
My current workaround is to have both 2.4 and 5 GHz networks configured for autoconnect. So after ungraceful shutdown, the first one to connect to will fail and LE will then just connect to the other one.
Few things you should try (if didn't yet):
Router without encryption (just for test), only WPA2 (AES and CCMP) encryption. Avoid WPA3 or mixed mode. Maybe is encrytion modes that isn't fully compatibile with iwd in LE.
If you or somebody near of you have a USB-wifi dongle, disable the onboard wifi (in config.txt) and try it with that.
Increase the wait for network time in the LE settings.
