Posts by chewitt

The best device for 3D support in LE is a Raspberry Pi 3B+ running the LE 9.2.x image; newer images use a revised video pipeline that doesn't support 3D yet (and maybe never will since it's not a big priority these days) and there is no support for 3D in the current Amlogic releases. It might work in older Amlogic releases but you can expect limited/no support on those now (different codebase, all the developers that hacked it are long gone). If you go RPi, use a simple HDMI > S/PDIF splitter for audio (or a DAC card, but that costs more).

Or you can use the cheap Android box with Kodi on Android .. which prob. works enough for playing occasional 3D movies.

ConnMan does not support being used as a repeater, and it's a very-deliberately simple hotspot function so I doubt it will acquire that ability.

If you want to create overlays you'll need to compile them (to use them); so in the context of the LE build-system you might as well just patch the device-tree that you want to use via a normal kernel patch. IMHO that's easier and doesn't need support for overlays.

Quote from DiMag

Does RPi4B (2GB RAM) play AV1 video reliably? (I take it as granted that it does play reliably HEVC, up to 10bit.)

AV1 is a new codec and there is very little hardware out there with native decoding for it (mostly Android TV boxes). So RPi4 will be forced to software decode AV1 content and I've seen RPi Foundation developers comment that SD/720p content should be in range, but not 1080p. As most of the content providers that started to offer AV1 content also provide it in H264 which an RPi4 plays easily, the lack of AV1 (and VP9) is more of a hypothetical problem than a real-world one. HEVC support on RPi4 is excellent.

Quote from lobbie1978

So yesterday I hardcoded EDID by SSH'ing into the Pi while a HDR movie was playing on my projector (TV was off) and programming EDID with getedid create. When I restarted the projector, the AVR and LE, the HDR availability was gone again.

I would keep things simple and capture the EDID direct from the projector without the AVR inline. Check it works over reboots before you add the AVR back into the mix.

Quote from lobbie1978

What would happen if I play HDR media on the TV? Wouldn't the TV just ignore the HDR signal and play content in UHD without HDR?

The RPi4 thinks an HDR compatible panel is connected so will output with HDR. If the TV has HDR > SDR auto-conversion then it would be able to handle the HDR signal and display in SDR, but generally the only TVs that have conversion capabilities are the ones that support HDR. So I think it is rather unlikely that it will be handled and I would expect green/purple tinged and washed colours due to the wrong colourspace.

There's no need to add extensions for flac files, it's one of the defaults. Have you defined the SMB share as a source and scraped the media into the Library? (Music is a Library view). Flac files are similar to mp3 and contain tags that are scraped.

Quote from Da Flex

I would say yes. Hopefully this bug will be fixed in the next stable release. Developers are informed.

There is no bug .. auto-update has not been enabled yet.

All S905X boards use the same Ethernet configuration so that should simply work in all S905X device-trees. Most devices are derivatives of the P212 reference design with few changes so all the core perhiperals will the same. The only major changes are buttons/LEDs .. and sometimes the SDIO WiFi/BT module.

There is no support in the upstream kernel for the RTL8189ETV chip, and I (and rest of the team) have no interest in adding more downstream Realtek drivers (https://github.com/jwrdegoede/rtl8189ES_linux) to the distro image - they're low quality and a pain to maintain. You could attempt a custom build with that driver included. The WiFi part of the SDIO module should probe; SDIO is a bus so connected devices are auto-discovered and wifi@1 reference in device-tree for broadcom chips will also work for Realtek. The BT part of the module will need things to be described correctly in device-tree.

I suggest you build in a Docker container to avoid all the hoop jumping with build environments.

I've recently pushed a change to LE master branch which enables (allows) Ethernet tethering in ConnMan. It works the same as WiFi tethering but in reverse (share the WiFi connection over Ethernet). This makes it fairly simple to connect the LE device to Hotel WiFI and then connect a laptop (behind a NAT connection) to negotiate the logon process. Next step is to make changes to the LE settings app to support the current Hotspot being rebranced as connection sharing and to support switching between WiFi and Ethernet. I suck at Python and have low time right now so that might take a year or two.

Quote from RavenRA

Can't make the wifi work on this box. DTBs from other S905Xes work. I am also very curious to install it to internal flash

I've never managed to get the RTL8189ETV to probe correctly but it's been a while since one came along. Start with expaining which dtb you are using to boot the device (which dtb has best overal fit for board features). NB: LE does not support installing to internal emmc on TV box devices; only SBC boards with dedicated images and upstream u-boot support. If you attempt using old scripts and forum posts I guarantee that it goes wrong and I guarantee zero sympathy and support for unbricking things.

You need to create multiple .config files (fr.config, ch.config, be.config, etc.) instead of putting multiple configs in one file.

You've erased u-boot. Your best hope/option going forwards is to find an Amlogic burning tool image on freaktab or similar. We have no real expertise or interest in Android images, and that's what you need to restore a working boot environment.

Quote from jamm

Is it actually the OS like the sbc versions?

Does it support a mouse or touch screen or does it need a dedicated remote?

It's exactly the same OS, only compiled for x86_64 CPU architecure and with different GPU drivers to suit "PC" hardware. It supports a mouse the same as the ARM/SBC releases. It could support a touchscreen; depending on the exact/specific hardware having drivers in the kernel or can be enabled in the kernel. Most users will attach some kind of remote; either the 'wireless' keyboard type, or an IR sensor like flirc.tv with a spare IR remote, or a BT remote. Unlike ARM devices, CEC is rarely supported in the PC world.

Add-on:SFTP support - Official Kodi Wiki

Quote from Origin

My setting is 1080/50 but the WIKI recommendation is 4096x2160 @ 60Hz (highest supported resolution of my TV) or not?

1080@60 (and whitelists for 4K modes, as you've done) would be our recommendation. The skin is 720p or 1080p (not sure which) so the TV does a better job of scaling an already rendered image to 4K than Kodi does using CPU to scale the content to render. Few people have HTPC devices with the CPU to handle 4K GUI smoothly.