Posts by chewitt

30 seconds reading the content added/removed section of your IPTV provider's forum shows them (not surprisingly) to be a pirate IPTV service.

The current Slice image is just our standard Raspberry Pi image with an extra overlay loaded via config.txt for ethernet, sound and the LEDs, plus the Kodi service add-on.

Deinterlace is configurable under Open-GL (on x86 hardware) but not when using Open-GLES (on ARM chips). They are distinct and quite different ways to render video on-screen.

If things take 50 seconds to boot there's an issue somewhere. Sharing the systemd journal log after boot should show where the delay is; unless the issue is in u-boot before the kernel/system (which generate the boot log) run.

Please understand that RK development is "work in progress" and far from complete. Playback glitches should be expected.

You can mount the Gluster node via CIFS/SMB or NFS .. there is no support for their native client libs in LE or Kodi. You can either remote mount to a local folder using the systemd SMB/NFS .mount templates in /storage/.config/system.d or use the Kodi client capabilities as normal. IMHO unless you need to use/learn GlusterFS for some other purpose it's probably an unnecessary complication.

mount -o remount,rw /flash
cp /path/to/your/splash.png /flash/oemsplash.png
mount -o remount,ro /flash

^ no need to recompile to change the splash

TCPServer[569]: segfault at 7fb2e8db7000 ip 0000000000bd5e76 sp 00007fb2c57f9580 error 4 in kodi.bin[400000+ef4000]

^ suggests something network stack related not GPU, but regardless this is an unsupported configuration (GPU pass-thru) of the unsupported Virtual image so it will be up to the wider community to guess the issue. Sorry it's not a better answer..

MikeKL at the moment the only changes to S912 images are micro-bumps to the panfrost mesa code. There is no 10-bit video support and most 4K media is 10-bit HEVC so lockups/crashes when playing unsupported media are expected.

In short, no, it's not a filesystem we depend upon so we don't include tools (and incur bloat) for it.

As the saying goes .. no log = no problem

Make a backup of the working LE device and restore the backup on the non-working device. You should now have devices with identical configuration and thus should eliminate "PEBKAC" from the setup process. If you still see issues; then yes it might be something server-side, but there is nothing by default in Windows that can/would restrict the number of clients connecting (until you reached large numbers of clients).

There are no camera drivers in LE, because it's not a use-case we need (or want) to support. Use Raspbian.

You can submit the changes as a pull request to our GitHub repo so changes can be picked for testing, but no guarantee they are accepted as this is for older hardware.

The 4th generation AppleTV remote uses IR for navigation and BT audio for siri voice commands. So it's not a "BT remote" that can be paired.

The short answer is no. However, in our add-on repo there's a Bluetooth audio device switcher that is functionally similar to what you need; it detects the connection of the BT device (over d-bus) and auto-switches the Kodi audio output from alsa to pulse-audio. It's probably not impossible to extend that or plagiarise the device switching code to work with other devices (USB devices don't generate d-bus events so another method of initiating the switch is required) but if you don't have the developer skills to do that yourself the challenge is always finding a willing volunteer who does.

Amazon-VOD from the Sandman79 repo is the only one that works for me

If you run "systemctl restart kodi" does HDMI audio appear?

If yes it's a simple timing issue where the audio drivers haven't loaded before Kodi starts so the alsa devices can't be auto-detected. Adding a "wait for network" delay via LE settings should fix that. It's badly named and will act as an arbitrary Kodi startup delay.

It might be easier to explain what you're trying to functionally achieve? then we can suggest other approaches.

Plan B .. get a USB flirc dongle