Posts by chewitt

RPi4 does not support 4K H264 hardware decoding so bad (CPU decoding) results are expected. It supports 4K only with HEVC.

I'd suggest reading this https://wiki.libreelec.tv/configuration/4k-hdr to ensure the whitelist and other settings are optimal. I would remove force_turbo and hdmi_enable_4kp60 as 99% of 4K HEVC media in circulation is 4K@30 or [email protected] and thus 4K60 which forces the SoC to run permanently in a more resource-demanding mode is not normally required.

I run an RPi4 as the family daily-driver without any real-world issues. It's miles more reliable than other devices I have.

I suspect you've followed the legacy image style of boot configuration (renaming files to dtb.img) instead of following LE instructions which are different. GXL boxes are all rather similar and except for user-error, it's unusual for devices to not boot.

Rainbox screen normally means "wrong image" so that does explain.

The dice-roll is always whether the box is a real Tanix box, or a clone of the Tanix box with minor component differences. And the only proof or it using an H6 chip is opening the box up and visually checking. All the main Android box brands are widely cloned, and some even ship with a completely difference SoC inside.

Are you sure it's an RPi2B and not RPi1B?

Kodi has a calibration function that you can use to (re)align the edges with the screen.

ping knaerzche ^

Larsen most boxes will boot from a USB, but usually only one specific port on the box. All boxes should boot from an SD card though. It's unlikely that an S905W box has encrypted boot, so I wouldn't run down that rabbit-hole before trying an SD card.

Xorg (and thus the Generic Legacy image) does not support HDR

Can you rm -rf the connman service folder for the NIC under /storage/.cache/connman/<name of service> and reboot. Any change?

And/Or try to use connmanctl to create a connection:

connmanctl

agent on

scan wifi

services

connect <service>

ConnMan intentionally cannot see hidden networks, but you can SSH into the device (over Ethernet) and configure WiFi using iwctl.

The image compatibility check will fail during RPi2 to RPi3 update/crossgrade as the image name doesn't match the current one. The cheat for that is "touch /storage/.update/.nocompat" before rebooting.

Feb 16 19:11:01.959281 LibreELEC kernel: usb 1-1.5: r8712u: CustomerID = 0x000a
Feb 16 19:11:01.960477 LibreELEC kernel: usb 1-1.5: r8712u: MAC Address from efuse = 24:05:0f:6b:f2:ef
Feb 16 19:11:01.961390 LibreELEC kernel: usb 1-1.5: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
Feb 16 19:11:01.962782 LibreELEC kernel: usbcore: registered new interface driver r8712u
...
Feb 16 19:11:02.386054 LibreELEC connmand[639]: wlan0 {create} index 3 type 1 <ETHER>
Feb 16 19:11:02.386091 LibreELEC connmand[639]: wlan0 {update} flags 4098 <DOWN>
Feb 16 19:11:02.386127 LibreELEC connmand[639]: wlan0 {newlink} index 3 address 24:05:0F:6B:F2:EF mtu 1500
Feb 16 19:11:02.386158 LibreELEC connmand[639]: wlan0 {newlink} index 3 operstate 2 <DOWN>
Feb 16 19:11:02.387214 LibreELEC connmand[639]: Adding interface wlan0 [ wifi ]

^ The MAC address of the USB NIC matches what ConnMan sees as wlan0. The only thing I see that looks abnormal is the interface not being brought to an UP state. What happens if you manually do "ifconfig wlan0 up" ?

Quote from miebster

Does anyone know how to get 2 identical displays?

Use an HDMI cable that duplicates (mirrors) the output to two displays. There are lots of cheap $5-10 options on Amazon/eBay.

Use numerical numbering, e.g. 11.0.1 .. 11.0.1.1 .. 11.0.1.2 .. 11.0.2

If you are going to release/maintain images please set BUILDER_NAME="ardaoktay" in .libreelec/options so we can track the image in active-install stats. This means you can also ask occasionally to discover how many (or few) users you are entertaining

Please you run "pastekodi" and share the URL so we can see the full log. The snipped you've shared appears to show the device being probed and the driver loaded. The difference between LE10 and LE11 is we've dropped the vendor driver in favour of an in-kernel driver that's in the process of replacing it.

To be clear, Kodi does not support downgrading so while "updating" to the older .tar file will downgrade the core OS and embedded Kodi app itself without any issues; there is zero support for downgrading add-ons and this may cause issues. If you see problems, you will need to stop Kodi and rename the current add-on binary folders out of the way and then restart and reinstall the add-ons you need. If you are lucky the K20 and K19 add-on settings formats are compatible; and if not you'll need to stop and rename those out of the way too.