Posts by Da Flex

According to this diagram, the video contact is the yellow plug. You can solder an adjustable resistor into your existing cable (inner contact of the yellow plug).

To my knowledge there is no gamma correction by software (for both, composite and HDMI). I would use hardware to fix this: Use an adjustable resistor on the composite video pin.

You could remove the interlaced parameter "i" from the cmdline.txt line.

PS: Check the wiring of linked thread.

PPS: Downgrading to LE 10.0.1 is also worth a try, because thats the version of the linked thread.

Into actual config.txt please. As you know, always reboot after an edit.

Also try this alternative line (replacement for dtoverlay=vc4-kms-v3d,cma-512,composite=1) :

dtoverlay=vc4-kms-v3d-pi4,composite

Edit this dtoverlay line at config.txt, resulting in this:

dtoverlay=vc4-kms-v3d,cma-512,composite=1

Add this line to the end of config.txt:

enable_tvout=1

Add video=Composite-1:720x480@60ie to the end of your existing boot parameters line (file cmdline.txt, after the "quiet" parameter, separated by a space sign).

Read here: Click!

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.