Posts by chewitt

If your network and the internet are good, the low-quality (or in current world situation, over-subscribed) pirate IPTV service is the issue and cache fiddling cannot resolve slow streams. Forcing Kodi to increase cache size just means you wait long for the stream to start and wait longer for the cache to refil and restart playback when the stream stalls. Удачі..

The Telos and Meta boards are based on the same design. I'm not saying that's the same design as your board (no idea). Start with the p200.

It looks like it crashes in the i915 graphics driver. I'm not sure why.. others may comment though.

Someone swapping their drives from NTFS to EXT4 would at least eliminate or confirm the issue is related to NTFS; if the problem goes away it's something in the in-kernel filesystem driver. If it occurs with EXT4 then it's something else.

The Telos/Meta variants are 2GB, the pro is 1GB; otherwise they're based on the same board design (derived from the P200 reference board) and have much the same features.

If all you want/need to do is edit files in the OS, enable SSH access and connect using PuTTY (on Windows) and use nano to edit files. It's a lot less hassle than (re)booting from another OS to make minor changes.

libdsm is a lightweight SMB client that VLC uses for browsing SMB shares. Kodi has an SMB client that it uses for browsing SMB shares. Kodi does not support alternatives; because there's no need for that .. it already has an SMB client. If for some reason that doesn't work you can also use kernel SMB capabilities to mount a remote filesystem to a path on the local host .. but that kind of thing is not really required as Kodi has a perfectly good SMB client.

ngrok would probably have dependencies on networking so systemd would always be the better approach since you can sequence the start to happen after the network is up/online.

You can add a systemd service file in /storage/.config/system.d to execute commands

Unless you share the boot logs there is nothing to take a stab at.

Please read https://wiki.libreelec.tv/hardware/amlogic#install2internal .. in short, that script isn't usable now.

I'm working on an approach for user-driven tweaking of the speeds that the mmc controller runs the SD card at. There are silicon bugs in the Amlogic controller that cause stability issues at higher speeds so most boards are currently and deliberatly underclocked to use a safe "runs everywhere" 50MHz speed. Most (but not all) boards will support this being raised to 100MHz with UHS modes enabled, and some might even tolerate 150MHz, but i'm confident none will reliably run at the 200MHz rate used in the vendor kernel. Amlogic implemented some hacky and unsafe workarounds for the vendor kernel to run that fast; and those changes would never be accepted into the usptream kernel.

In the absence of a log file, no idea. Perhaps try other device-tree files?

video=HDMI-A-1:1920x1080M@60

Only use the HDMI port nearest the PSU connector, and add this ^ to cmdline.txt. Fixed?

Not a known thing (at least not in this forum). As it's technically nothign to do with LE, the Kodi forum would be a better place to look.

ilmich ^ the above issue is caused by sarbes front-to-back patch, I've seen the same with AMLGX. It's a promising change but it needs further testing before we adopt it

echo "options snd-usb-audio quirk_alias=05a71020:047f02f7" > /storage/.config/modprobe.d/bose.conf
reboot

^ run that over SSH

Disable the official Plex add-on and install the one from this repo which works fine: https://pannal.github.io/dontpanickodi/

Hopefully Plex will figure out the same changes needed for the official add-on, but until then..

Can you drop the connman.service/iwd.service from the file and then run "systemctl daemon-reload" before rebooting? .. still working?

If yes I will write it up for the wiki.