Meanwhile I found that the option to limit color range to 16-235 was active. I am quite sure I never activated it - but I guess I did.
Oh I have done this a number of times.
Posts by HypnoToad
-
-
Firstly, no issues with h265 with the official rasp pi 4 build.
I have been using the retroarch version from here. Release 2019-08-23-RPi4 · magicseb/LibreELEC.tv · GitHub
Everything runs better than expected, but the only issue is h265 files that run on the other build don't run on this one.
Log files: http://ix.io/1uio -
I managed to get a few cables and can conclude my issue was with a years old cable I had since 2010ish.
So I have an assortment of regular micro HDMI to HDMI, little adapters that convert to just normal HDMI to HDMI. They all seem to work.
Something else to look at is testing all the HDMI ports in your TV.
I had one set to Game Mode on my samsung, which was the main port I was using. The other ports which didn't have game mode set connected to the CEC without an issue.
I would recommend trying to reset your TV to factory defaults and just testing ports and settings.
I am using an old Samsung Series 5 LED TV. -
Added libssl and libcrypto, still hitting a snag.
-
Oh and you might want to get backups and switch over to the Rasp Pi 4 build.
Raspberry Pi 4 – LibreELEC -
I had more success with fstab permission settings as default.
By the looks of it you only have the uuid and the filesystem type.
[SOLVED] fstab - make default file permission 755
I had to do this because I installed samba and drives had issues with permissions with the programs I was using.
Hope this helps. -
CEC works on my earlier Pi's, and I've never had CEC connection issues with my samsung, beside buggy stuff that can be fixed or worked out.
My micro hdmi cable is old though, so I will look into buying a new one in the coming weeks. -
I have 2 rasp pi 4's. 2GB and 4GB
The 4gb one has issues with the same micro hdmi cable I have used to setup both of them.
The color test screen will come up, but then if it's moved slightly the main OS doesn't load with it's default resolution, as if the cable has been unplugged while it was loading.
I don't get this connection issue with the 2GB model, I can also move it around without any connection issues.
The OS's I am using are libreelec pi 4 build and raspbian, and it all seems like a hardware disconnection and not a software one. Because if I can get it into a good position I can use the device just fine.
I am afraid that I may have accidentally broken something when I've treated this device in particular with great care because it was the first one I got.
Your issue seems on the surface much like mine where the hdmi is not detecting the cable being plugged in. If you move it around do you get any artifacts or images, you might have to do what I am planning on doing and looking into other micro hdmi adaptors -
Another Samsung owner having this issue registering interest.