Posts by chewitt

The UPnP client is embedded and cannot be disabled, but it's probably not the problem unless you're trying to use UPnP sources?

I'd also remove the cache tweaking from your advancedsettings.xml file.

I'm not sure what you really mean by narrowcasting .. but LE boots directly into Kodi, and using a simple autostart.py script you can start a playlist on Kodi startup. For stability and performance use an Ethernet and don't be tempted with wireless. Kodi can be controlled over CEC on most TV's (using the TV remote) and you can deliberately disable IR support (if the box has an IR sensor) to prevent visitors trying to control the boxes. We added an SSH console keyboard in the last couple of days (will be available in the next alpha).

Hope that helps.

HiassofT ^

You can't just compile the drivers, but/and it should just work.

The backup contains /storage/.config, /storage/.cache and /storage/.kodi .. anything outside those folders (and there won't be anything in most installs) is not included in the backup.

You either have to fiddle with the partition sizes using gparted from another Linux LiveUSB (Ubuntu or similar) .. basically you shrink the storage partition and then grow the boot partition to a larger size. It's not hard but will take many hours. The alternative and usually faster option is to backup the existing contents of /storage then clean install and restore the backup. The LE settings addon has a backup/restore function.

It will be removed once Team Kodi fork the v18 release branch and the master branch becomes v19. If you're lucky someone will come along and implement EGL streams + NVDEC support in Kodi. It's do-able, but it's unlikely to be someone from Team Kodi.

BCM4360 should be supported by the "wl" driver in Generic images. Provide "dmesg" output from a clean boot using the 006 alpha release.

There is no way to "cast" pics/video to Kodi (on LE, or any other distro or Kodi supported platform) since iOS 9.x was released (thanks Apple!) so the only thing you can do is copy them to a USB stick and connect it to the HTPC device. Or pick up an AppleTV for that purpose.

It's, err... different

Edit the syslinux.conf entries and add "tty" to the boot params of the "run" option.

It's not on a menu. Hit enter when the syslinux prompt shows, then type 'run' and hit enter again.

Unless your box has particularly crap components a decent SD card will give good LE performance.

It's been a while since I flashed one, but the rough sequence (once you installed the CM drivers to Win7) is to connect the USB cable and wait for that device to be detected, then run the exe file and it detects the device, then power the box on and the memory will mount. According to the Pi Foundation site the exe should run automagically but it never happened for me - I always had to do it manually. At this point if the original Slice image used a FAT partition for boot stuff (it's a couple of years since I saw the original noobs config and I can't remember) it will be mount and you can copy over (overwrite) the boot files from the target folder of the .tar file. If not, the only option will be to flash the eMMC with our .img file which will nuke the existing install .. but the ease the pain of loss you get some extra space on the eMMC as noobs is no longer present. Flashing the eMMC won't touch the internal HDD if you have one installed.

NB: No idea what J4 is about so definitely not required.

"run" gets you a persistent install on the USB and "live" gives you a non-persistent install

I've created webspace for balbes150 to upload an aarch64 repo into, so at some point over the weekend things should start working.

Put the alpha release on a USB stick and test-boot without touching the existing install.

Read Infrared Remotes [LibreELEC.wiki] for info on creating a custom IR config. It's not that hard and using the original remote is probably miles easier than suffering CEC (which works well on some TV's but can be awful on others).