Posts by Da Flex

Thanks. The menu looks OK, sda1 is un-mounted.

Shrink sda2, and then execute the shrinking by pressing big green hook button on the right.

After that try to resize sda1 again.

Set GParted to English language (maybe restart necessary), and make a screenshot of the right-click-menu of sda1.

Maybe sda1 is mounted, and that avoids resizing. Try to un-mount sda1 (right mouse click menu).

1) Press the right mouse button over the sda2 table entry. Select "change size / displace".

2) Shrink size by 1024MiB.

3) Do step 1) for sda1.

4) Expand size by 1024MiB.

It always costs me some nerves whenever I use GParted. It's an expert tool.

Yeah, see my PS above.

PS: If GiB is not available, set it to 1024 MiB.

Yes, that's the right menu.

1) Switch from MiB to GiB (forth menu entry).

2) Set the the second entry number to 1 (GiB).

PS: You have to shrink sda2 first (same menu, shrink by 1GB).

Expand the first partition (sda1) to 1GB. After that expand the user data partition (sda2) to the max.

HiassofT is right: If a too small OS partition is your problem, you don't need to buy an SSD. Just enlarge the OS partition with an appropriate tool like GParted. I suggest to give 1GB to the OS partition (LIBREELEC / OPENELEC), and assign the rest to the user data partition (STORAGE).

Quote from ToddeSwe

So for me to update and get a bigger one (the one inside is 40gb Intel SSD 2.5" drive) i have a ASUS S1-AT5NM10E Barebone for the task. Does any new SSD work?

Sure, copy from HDD to SSD, and LE should work.

Quote from Anderssen

If set 24Hz in the system display settings (as I wrote above) there really are no problems..

Maybe you can keep the original HDMI mode, and just switch de-interlacing off: Click!

Quote from Laurent

In kodi: Settings/video settings/Deinterlace method Off

Interesting solution, thanks!

Quote from Laurent

Always the same problem. The problem exist also with VLC, then is it more a system/hardware problem ?

Maybe your TS file has errors, and some players auto-fix those errors.

Quote from Laurent

Do you find a solution ?

Please try this advancedsettings.xml:

<advancedsettings version="1.0">
    <cache>
        <buffermode>4</buffermode>
        <memorysize>7000000</memorysize>
        <readfactor>4</readfactor>
    </cache>
</advancedsettings>

Quote from loveridgem

The fact it works on my Acer monitor leaves me scratching my head and really bummed the Pi 4 is having these issues.

Very rare, but possible. If my last advice doesn't work, I would go for a replacement.

One final thing, before I'm running out of ideas. Try different color spaces by editing hdmi_pixel_encoding at config.txt. Some monitors use YCbCr instead of RGB. Good luck!

Try this config.txt (enforces CEA mode 16):

gpu_mem=320
force_turbo=0
hdmi_ignore_edid=0xa5000080
disable_overscan=1
framebuffer_width=1920
framebuffer_height=1080
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16
dtparam=audio=on
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

Those settings work for many users with older monitors.

Do you use HDMI 0 as RPi's output? If you use a case with HDMI wiring, remove the case.

PS: Did you already tried hdmi_safe=1 at config.txt?