I’m using an old Philips LCD tv for which the RGB 8-bit color scheme needs to be used (or the screen becomes blueish/greenish).
Portish helped me with that (with a Beelink GT King) by suggesting to add
echo rgb,8bit > /sys/class/amhdmitx/amhdmitx0/attr
in the autostart.sh file.
It worked on the GT-King and on the GS-King as well.
Since I updated to firmware 905P0 and CoreELEC-9.2.4.2, it seems that the setting is somehow overwritten as the screen will get blueish/greenish from time to time (but not at boot) on my GS-King X.
Was something changed at CoreELEC regarding this ?
Some information:
CoreELEC:~ # dmesg | grep hdmitx | grep video
[ 0.000000] Kernel command line: init=/init console=ttyS0,115200 no_console_suspend earlycon=aml-uart,0xff803000 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 otg_device=1 reboot_mode_android=normal logo=osd0,loaded,0x3d800000 vout=1080p60hz,enable panel_type=lcd_1 hdmitx=,444,8bit hdmimode=1080p60hz frac_rate_policy=1 hdmi_read_edid=1 cvbsmode=576cvbs osd_reverse=0 video_reverse=0 irq_check_en=0 androidboot.selinux=permissive androidboot.firstboot=0 jtag=disable androidboot.hardware=amlogic androidboot.serialno=922H0H1000068 mac=c4:4e:ac:b3:ab:7b androidboot.mac=c4:4e:ac:b3:ab:7b androidboot.rpmb_state=1 BOOT_IMAGE=kernel.img boot=LABEL=COREELEC disk=LABEL=STORAGE console=ttyS0,115200 console=tty0 no_console_suspend hdmimode=1080p60hz logo=osd0,loaded,0x3d800000 frac_rate_policy=0 native_4k_gui=0 progress systemd.show_status=auto
CoreELEC:~ # cat /sys/class/amhdmitx/amhdmitx0/attr
rgb,8bit
I’m using the workaround described here: