Posts by Da Flex

Skin developers are usually at Kodi forums. Ask there. We don't know about specific skin dependencies.

gthebest You've been ignored the warning. Now accept the consequence, which is ostracism.

Yes, it's unsupported, and we should bury all those threads on the graveyard. However, you will find some tweaks here.

Thanks for the NFS test. I think my first theory was right, and a new buffering algorithm is needed in Kodi. Not our turf.

PS: More practical approach: Reduce the X/Y resolution of the pictures for a smaller memory footprint.

LuRu Makes sense. If you need a beta tester for RPi 3B+ with SSD1306, let me know.

LuRu Are you sure you need RPi.GPIO? SPI gets activated by config.txt, and that should be all.

CvH I'll try that.

Quote from LuRu

I don't (yet) have a problem with the RPi.GPIO. So far I'm only working with OPi.GPIO. However, it seems to work reliably. And if I take into account the use (controlling the display), it is not a nuclear power plant and some random error cannot be a problem at all. In any case, thank you for trying to help.

The LED goes off for a long time. I just wanted to mention that to avoid unnecessary research.

If RPi.GPIO works reliable for you, then I'll check my installation again. The problem exists since LE 10 for me.

I have to mention that RPi.GPIO of RPi Tools isn't reliable. The power LED connected to my RPi 3B+ (GPIO 13 / Ground) switches on and off randomly. I was testing electrical contacts - no problem there. It's definitely a software problem. If I can help to track down the issue, please ask.

My script for the LED:

#!/usr/bin/python

import sys
sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib')
import RPi.GPIO as GPIO
import os

led_gpio_number = 13
GPIO.setmode(GPIO.BCM)
GPIO.setup(led_gpio_number, GPIO.OUT)
GPIO.output(led_gpio_number, True)

Now I'm starting to think there are too many Samba errors, and at the end they result in a segmentation fault:

2022-07-02 17:44:30.397 T:741      INFO <general>: SMBFile->Open: Unable to open file : 'smb://10.117.1.10/bilder'
                                                   unix_err:'15' error : 'Is a directory'
...
Jul 02 17:48:02.525513 LibreELEC kodi.sh[665]: ExifParse - Nonfatal Error : Illegal exif or interop ofset directory link 0 0
...
Jul 02 17:48:02.525513 LibreELEC kodi.sh[661]: Segmentation fault (core dumped)

HiassofT Do you think the same way?

Bedford Can you switch from Samba to NFS for your NAS?

The old Chrome was done by LE dev CvH , but the new version will be done by someone else.

Maybe Kodi forum has more info. The add-on sandbox is a big deal, and it's strongly connected to Kodi core code.

Physically to avoid surprises on regular usage. No big deal.

Use the default skin.

Log from LE 11, installed on a different microSD please. Link to nightly builds: Click!

If you still have issues with LE11 nightly, then it's time to post a report at Kodi forum (not sure whether it's a known bug). A caching algorithm for picture scrolling should be implemented.

Sometimes it takes a while until pastekodi creates a link, but it also could be a server error during the upload. However, the CMA error is visible at the current log:

Jun 23 20:17:15 pan kernel: [drm:vc4_bo_create] *ERROR* Failed to allocate from CMA:
Jun 23 20:17:15 pan kernel: vc4-drm soc:gpu: [drm]                            V3D: 287868kb BOs (281)
Jun 23 20:17:15 pan kernel: vc4-drm soc:gpu: [drm]                     V3D shader:     44kb BOs (11)
Jun 23 20:17:15 pan kernel: vc4-drm soc:gpu: [drm]                           dumb:   4052kb BOs (1)
Jun 23 20:17:15 pan kernel: vc4-drm soc:gpu: [drm]                         binner:  16384kb BOs (1)
Jun 23 20:17:15 pan kernel: vc4-drm soc:gpu: [drm]                total purged BO: 240528kb BOs (235)

If you provide a log, then we could get a proof for bad caching implementation, and Kodi team hopefully reacts:

More and more people will ask for apps in the future.