Posts by HiassofT

FritzOS 7.50, which is currently being rolled out, adds support for wireguard

FRITZ!OS 7.50 | AVM Deutschland

avm.de

so long,

Hias

Quote from bornagainpenguin

Is there a list of addons that require the Chrome browser to function somewhere?

None of the addons depend on Chrome.

so long,

Hias

Also drop the overclock settings you added to config.txt and check if your RPi works fine without them.

Overclocking abilities are very specific to each individual devices, some can't be overclocked at all while others will happily run at 2GHz - there's no guarantee for anything so take every guide that tells you that setting X and Y work fine with a huge grain of salt - at best take those guides as a rough starting point while for checking which settings work with your particular device.

If you overclocked your RPi and something doesn't work right the first thing to suspect is always that the overclocking parameters you used don't work for your device - so remove them before digging further.

so long,

Hias

A 100MB log file is definitely not normal (unless you enabled some component logging bits, which aren't needed here - normal debug logging will do fine).

I suggest you do a clean install of the latest nightly on a separate SD card or USB stick. Only setup display resolution and whitelist, and play the file with that. If it fails, post the log.

so long,

Hias

hdmi_force_hotplug (and most other hdmi_ settings in config.txt) ceased to have any effect since LE10 - vc4.force_hotplug in cmdline.txt is the replacement for it.

so long,

Hias

Use vc4.force_hotplug=1 - inval_delay and cec_debug were temporary test settings that have been removed and replaced with force_hotplug.

so long,

Hias

Quote from titoasi

Installed last nightly build and same error happened

then please post a crashlog from it

so long,

Hias

See the info in our wiki:

https://wiki.libreelec.tv/support/log-files

https://wiki.libreelec.tv/support/update

if you run "pastecrash -c > my-log-file" you can save the crash log to a file, copy it over to your PC and simply attach it here to a post.

so long,

Hias

Quote from mglae

Maybe someone know what the burst of kodi.sh[864]: Failed to import fence to syncobj: -1 means.

That seems to come from mesa https://gitlab.freedesktop.org/mesa/mesa/-/bl…v3d_fence.c#L92 but I've never seen that issue here so no idea. Kodi crashlog might tell us more.

so long,

Hias

Just use the "upload crash log" option in LE settings, immediately after kodi crashed and restarted or ssh in, run "pastecrash" and post the URL you got from it.

BTW: please test with the latest LE11 nightly from here, it contains some additional video decoder fixes.

https://test.libreelec.tv/11.0/RPi/RPi4/

so long,

Hias

Good to hear LE11 is running fine on your setup, too!

Skipped frames with GUI overlays is a known kodi issue, unfortunately no solution for that yet.

The current LE11 nightlies should be very stable, I'm running them as a daily driver here. LE11 final should be out in the next couple of weeks and so far I'm not aware of any major issues on RPi.

So it should be safe to use it until LE11 final is released.

so long,

Hias

Quote from ciclista71

Sorry for missing the part about the sample.

I would have sent it earlier. I have two clips, one starts from the beginning and the other shows some rolling titles which clearly show skipped frames

Clip1

Clip2

Thanks for the samples! Both of them play fine on LE11 and the scroller/ticker is smooth, too.

so long,

Hias

We can't tell more without a sample - I asked for it in post #2 - so you'll have to test yourself if it works with LE11 nightlies.

so long,

Hias

force_turbo will boost all clocks (including ARM CPU) which can help with general performance but likely result in higher temperatures. core_freq_min will only raise clocks needed for HW decoding so temperatures will be a bit lower.

You have to check yourself, it also depends on how well your RPi is cooled - a too high boost can have quite negative effect without proper cooling, then it will start throttling after a while if temps get too high and have worse performance than without clock boosting.

so long,

Hias

Log shows you didn't add core_freq_min or force_turbo to config.txt as mentioned in the release notes

LibreELEC (Matrix) 10.0.4 - LibreELEC

If this doesn't help please test with a clean installation of the latest LE11 nightly from here (also with core_freq_min or force_turbo)

https://test.libreelec.tv/11.0/RPi/RPi4/

so long,

Hias

Please uninstall the vpn manager addon. It seems to be having severe issues, constantly generating log entries, spamming the logs and that might be the cause of your issues.

Once you removed it please upload a pastekodi log as requested - kodi log alone isn't enough.

so long,

Hias

You can zip the file you got from "pastekodi -c" and attach it to a post here.

But it'd be better to reproduce the issue immediately after kodi start, stop playing a few seconds after the issue happened and then create the log - that should be small enough for standard pastekodi upload (if you get an error, retry a few time with some 30-60 seconds between retries, ix.io might be busy and thus fail to accept the paste).

so long,

Hias

Please post a short sample and a full debug log.