Posts by chewitt

Amlogic video support is now "as good as it gets" until the next wave of VideoPlayer changes land in Kodi v18. We might see some tinkering around the edges if small changes backport easily, but nothing substantial. The developer in question has already stated he does not support attempts to backport larger 'agile' changes to Krypton and we will not add things that are not upstream supported.

NB: Raspberry Pi does not use "amcodec" within Kodi so even if it does play VC-1 nicely the comparison is (on a technical level) irrelevant

On what hardware? With what LE version/image?

"journalctl -b 0 --no-pager | paste" from a clean boot, and share the URL, then we can see what happens to the NTP check. The "wait for network" option delays Kodi start and has no effect on NTP/networking.

The fact that SSH/samba access do not work points towards networking not being right, i.e. Ethernet port at half-duplex or bad cabling. Solve that and you may find that NTP suddenly works too.

Quote from mweinmann

syscontact root@openelec

  lsellens (cough)

I would start by updating the UEFI firmware on the device. I completely forget the details of which boxes involved etc. but other reports of blank screens and issues on Chromebox devices have been resolved with an update.

MrChromebox.tech

Pulseaudio - LibreELEC

it can be configured as discussed in that wiki article, at the expense of multichannel audio over HDMI which most people consider to be more important (hence it is not a default configuration).

parted -s /dev/sdb mklabel gpt
parted -s /dev/sdb mkpart primary ext4 40s 100%
parted -s /dev/sdb name 1 'MEDIA'
mkfs.ext4 -L "MEDIA" /dev/sdb1
fsck.ext4 -y /dev/sdb1

this creates a GPT partition structure, creates a single primary ext4 partition that is 100% of the available space, labels the partition "MEDIA" then formats an ext4 filesystem labelled as "MEDIA" (for consistency) then fsck's the partition to ensure all is okay. Commands assume /dev/sda is the boot SSD and /dev/sdb is the secondary HDD. You need to check/validate /dev/sdb by checking dmesg output as the commands are destructive.

Probably the anti-piracy measures we added to the OS blocking write from those apps.

I'll comment that 'pictures' is the bastard unloved child of Kodi features, but it should generally work. Kodi debug log please.

You are making an incorrect assumption that any conf file placed in /storage/.config overwrites the equivalent in /etc. This only works for a very limited set of files and nsswitch.conf is not one of them. Make sure Kodi has been configured with the name of your workgroup and WINS server.

Make sure "adjust display to match refresh rate" is disabled, else passthrough is disabled an everything it output in PCM with the channel configuration you've defined (default is 2.0).

If you bothered to compare githashes on the version of atvclient we package and the upstream repo you're enthusing about instead of posting all over the place, you'd discover those changes have been included for a while.

Kodi auto-detects audio properties based on the underlying alsa configuration so a card needs to have drivers/overlay enabled in the Linux kernel and cards with an S/PDIF port need to have an alsa conf to ensure correct IEC958 detection. The older Mamboberry DAC+ model appears to use the same overlay as hifiberry cards, which we've supported for a long time, but I wasn't able to find any information on their website about set-up for the LS+ card. It's normally trivial to add support for new DAC devices - but we need more details. Perhaps (as their customer) you can ask them to contact us, or follow-up on this post.

No current support and those devices are not on our radar. You'll find that anything using an Allwinner chipset isn't so popular among FOSS developers due to that companies poor documentation and software support (although that's nothing unique) and history of GPL violations. Someone was making OE builds for the older models (which I guess you found) but I'm not aware of anyone doing LE builds.

LE 7.0.3 contains the older 304.xx driver needed for prehistoric nVidia cards, but we have never released an x86 (32-bit) build, although if you know or learn your way around our build-system it's still possible to manually re-add support and create one.

Your method backs-up and then restores "all the crap" from OE into the new clean LE install. There is no cleaning benefit

The add-on description in the Kodi GUI states "ProFTPd is a secure and configurable FTP server with SSL/TLS" so i'd take a wild guess that it supports FTPS, which is not SFTP, and which leads my inner security nerd to caution that the box should not be exposed to the public internet unless you know what you're doing.

There is a community add-on for FTP, which will never be added to official builds because it is not a secure protocol, unlike SFTP which has been supported in our codebase since ~2009 ish.