The add-on repo was down for a few hours yesterday, but an LE12 device shouldn't be querying the LE11 repo. It's hard to guess things from a log snippet. Share a full debug log.
Posts by chewitt
-
-
Can you recommend a lightweight skin
The default Estuary skin is probably the best optimised one.
-
Have a read of this https://github.com/LibreELEC/amlogic-boot-fip/pull/27 - and please note that this forum really isn't interested in dealing with Android backup/recovery issues (not our OS, not our problem).
Also note that LE does not support install of the OS to the internal storage and while booting LE from an SD card changes the boot process slightly it's not harmful to the Android install - modern upstream kernels cannot see/mount any of the partitions created by the vendor boot firmware due to Amlogic's proprietary partition scheme - so we're not going to mess Android up.
NB: You can easily dump the full content of eMMC storage from inside LE using "dd" although this is a raw image and you will not be able to use it as recovery media in the event of eMMC issues as the u-boot in the dump is for eMMC boot only; magic headers are located at the wrong offset for SD/USB boot due to S905 requiring different offsets.
-
-
On the TV you can see the detailed signal info, which shows that HDR was enabled for the HDR content.
HDR is a much more nebulous concept than most people realise. It's not a fixed standard like "4K" and forcibly adding metadata to the HDMI signal to switch the TV into "make everything bright and show the logo" mode is simple and doesn't need to have any relationship to media being played. I wouldn't be too surprised if Windows drivers look for properties frequently associated with HDR and fake/trigger the mode change on the TV and/or blindly force output in some way. Linux is going to limit the output options based on what is possible, and while EDID suggests the TV supports HDR colourspaces (which can be seen in the debug log) that alone doesn't guarantee that HDR is possible. Again, the odd/incomplete set of resolutions listed suggests to me that something isn't right in the HDMI chain - symptoms not cause.
-
Code
Found resolution 4096x2160 with 4096x2160 @ 24.000000 Hz Found resolution 4096x2160 with 4096x2160 @ 23.976025 Hz Found resolution 3840x2160 with 3840x2160 @ 30.000000 Hz Found resolution 3840x2160 with 3840x2160 @ 29.970032 Hz Found resolution 3840x2160 with 3840x2160 @ 25.000000 Hz Found resolution 3840x2160 with 3840x2160 @ 24.000000 Hz Found resolution 3840x2160 with 3840x2160 @ 23.976025 Hz Found resolution 1920x1080 with 1920x1080 @ 60.000000 Hz Found resolution 1920x1080 with 1920x1080 @ 59.940063 Hz Found resolution 1920x1080 with 1920x1080 @ 50.000000 HzThe thing that stands out to me is ^ that's an odd collection of resolutions for a modern AVR and TV to have. I'd expect to see 1080p @ 30/29.97/25/24/23.976 not just 60/59.94/50, and the full range of 4K (4096 and 3840) resolutions not a few (but again, not all) of the < 30 ones. To me that suggests something isn't right with cables/ports (or the configuration of ports) in the HDMI chain; and I'd normally point fingers at the TV side since AVR's generally default to mirroring the upstream HDMI capabilities to the downstream HTPC device (although they too can fiddle with things).
The curveball on modern PC boxes with DP hardware is whether an LSPCON chip is being used to generate HDMI, and if yes, what bugs the LSPCON firmware has, because they are notorious for issues - including the "but it worked in Windows" kind.
-
Streaming from AirPlay worked until iOS 8.0, then Apple changed the (proprietary) protocol and it hasn't worked since. Miracast has never been supported in Kodi.
-
I've never seen a device that wasn't 115200,8,n,1 and I would advise against connecting the 3.3v/5v pins on the TTL device (asking for shorting issues and power isn't required). Yes it's possible that UART output is blocked in bootloaders, but that's normally only major-vendor streaming boxes (Amazon, etc.) and you're seeing stuff on-screen so that's unlikely. Not sure what to suggest as the only time I've seen something similar is when I'm connected to the wrong pins, e.g. JTAG not UART.
Tempting though large ones are, and the square one is normally GND .. Have you tried the 3x little round pads that are labelled?
-
VNC server is possible under old Xorg/X11 images (Generic Legacy) but that's for accessing an LE from a remote device. Creating some kind of VNC client add-on to create an outbound connection and display that through Kodi is an entirely different and more complex proposition. The better option would be to support "casting" but there is no cross-platform standard (and VNC is not one either) and Apple has buried theirs in proprietary encryption (AirPlay worked in the past, but no longer). It's something that will be shitty to implement and support and thus no community developers have volunteered or been self-motivated for the task.
-
Yup, create the file and either reboot the device or "systemctl restart kodi" from the console.
-
The first thing to figure out is what chipset(s) are on the card. The Geniatech website isn't helpful on that, but the driver file you have will probably show the info. The question is .. what downstream hackery did Geniatech do to make their driver work, and against which kernel.
-
Yes, although IMHO that requires more effort. You need to use an app like Notepad++ which supports Linux file endings and connect to the LE device using SFTP (FTP over SSH) not FTPS (SSL secured FTP).
-
I moved the thread from the Rockhip section as S905 is an Amlogic chip.
Read: https://wiki.libreelec.tv/hardware/amlogic .. follow the "box" instructions.
-
Nope, but the basic instructions in /storage/.config/system.d/openvpn.service.sample are valid for creating a client connection. If you want to create a server, read up on how to create an OpenVPN server conf and use the same service/conf to start a server. The only challenge with LE will be that any external files you link into conf will need to be located somewhere under /storage and not the usual /etc/openvpn location used in any guides you read.
-
It looks the same as the Tanix TX3-mini remote which has an upstream keymap (LE doesn't use remote.conf files).
See https://wiki.libreelec.tv/configuration/…iguration-basic and use the "tanix_tx3mini" keymap.
-
Will it work on old imac?
I suspect the macOS version will be too old, but there's no harm in trying. If it doesn't work you can unzip the .img.gz file and use 'dd' from Terminal.app to write the image to an USB/SD device.
-
If the file doesn't exist, create it with the "nano" text editor over SSH.
-
I'm effectively doing the same/similar. An RPi5 (2GB or more) is a reliable and well supported board.
The perenial challenge with DVB cards is drivers; LE uses latest/recent kernels and the support for DVB cards often relies upon older kernels or custom patches. If you can afford to spend a little, a Digitbit Twin network Sat>IP device is the default recommendation of staff and many users around here. The extra up-front cost is paid back in long-term low/zero maintenance effort. USB tuners will be cheaper, but expect more maintenance effort.
NB: Configuring the YouTube add-on in Kodi is painful due to the need for personal Google API keys (as it's not an official Google add-on with them embedded) but that's a one-time setup chore and completly invisible to parents/wives/kids once done.
