Posts by HiassofT

I just noticed that the latest RPi firmware contains a fix for 1366x768 mode - see bug discussion here rpi4 hdmi not working with motorola atrix lapdock · Issue #1202 · raspberrypi/firmware · GitHub

Testing with that might be worth a try (drop hdmi_drive/group/mode from config.txt and only keep hdmi_force_hotplug=1). Use the following commands to update to the latest firmware:

mount -o remount,rw /flash
wget -O /flash/start.elf https://github.com/raspberrypi/firmware/raw/master/boot/start4x.elf
wget -O /flash/fixup.dat https://github.com/raspberrypi/firmware/raw/master/boot/fixup4x.dat

so long,

Hias

Thanks for the info, I've informed popcornmix (one of the RPi devs) about it - it's a bit puzzling and I'm not 100% sure what's going on/wrong there.

so long,

Hias

Edit the cmdline.txt file on the FAT partition of the SD card and add "ssh" (after "quiet", with a space between) - ths will enable ssh. You can do this from Windows, but make sure you use an editor that uses unix line endings, like Notepad++

Then ssh in and post the outputs of the following commands

journalctl -a | pastebinit
tvservice -s
tvservice -m CEA
tvservice -m DMT
pastebinit .kodi/temp/kodi.log

BTW: Do you see the LibreELEC splash screen when the system starts or is the screen scrambled from the beginning?

so long,

Hias

Another option would be to tell eventlircd to translate the keyboard events from your remote into lirc events - then you can use kodi's Lircmap.xml plus remote.xml (or keymap editor addon) to map the button codes.

To do this you first need to find out the USB vendor and model/product id using "lsusb" - note the "ID" output from your RF receiver, the first 4-digit hex number (before the colon) is the vendor ID, the second 4-digit hex number (after the colon) is the model/product ID.

Then copy LibreELEC's eventlircd udev rule to /storage/.config/udev.rules.d and edit it:

cp /usr/lib/udev/rules.d/98-eventlircd.rules /storage/.config/udev.rules.d/
nano /storage/.config/udev.rules.d/98-eventlircd.rules

At the beginning of the USB section in that file (around line 90, after the 'ENV{ID_USB_INTERFACES}=="", IMPORT{builtin}="usb_id"') add a line with the following content. Substitute XXXX/ / YYYY with your vendor / model IDs from lsusb and make sure everything is on a single line:

ENV{ID_VENDOR_ID}=="0bc7", ENV{ID_MODEL_ID}=="0006", ENV{eventlircd_enable}="true"

After a reboot eventlircd should pick up your remote and the buttons should show up as Lirc events instead of keyboard events in kodi.log.

so long,

Hias

As suspected the remote is sending some keycodes that kodi doesn't handle.

You can change the keycodes with a hwdb file - eg map the scancodes to some function keys like f1, f2, f3, ... Read this post for more info Ok button doesn't work on H1 remote

Also look at the /lib/udev/hwdb.d/60-keyboard.hwdb file in LE, it contains the documentation of the hwdb file format and several entries for keyboards that you can use as a reference.

so long,

Hias

Sorry, I had a stupid typo in that command - it should have been /storage/.cache/cores, not /storage/cache/.cores - this is what I get for not using copy&paste but typing stuff manually

It looks like you already found the culprit, so I think you should be fine and we won't need more info.

so long,

Hias

Check the contents of the /storage/cache/.cores/ directory - the core file names should include the program name.

eg post the output of

ls -l /storage/cache/.cores/ | head -10

When you notice that a new core file had been created it'd also be useful to post your journal - that should contain some additional info what crashed, and maybe why. run the following command and post the output:

journalctl -a | pastebinit

BTW: probably the number one reason for unexplainable crashes on RPis is a bad power supply. The official RPi power supply is known to be good, use that if in doubt.

so long,

Hias

Can you upload the kodi log where you press some of those buttons?

My guess is the remote shows up as a keyboard in kodi and it's sending some keycodes that kodi doesn't handle - the logfile should tell us what's happening.

so long,

Hias

Quote from Monie

Also even after 9.1.002 update there still seems to be a very minor amount of stuttering on a 1080p x265 video. Is there any way to generate a report on this and upload it here?

A debug log might help. Enable debug logging in Kodi, reboot your RPi, play that file until you see the stuttering, then stop it and use the logfile upload function in LE settings and post the URL here.

See Provide Log File [LibreELEC.wiki] for details

so long,

Hias

Quote from Freestyler

I'm still missing full HBR audio support for RPi4. DTS HD MA is detected just like DTS and in option of Kodi there is no option to turn on DTS HD MA.

HBR audio isn't implemented yet for the RPi4. It's in the queue but will take a bit (probably months, not weeks).

so long,

Hias

Quote from Puschl

I haven't looked at the temperatures but yesterday I experienced asynchronous video playback on a 1080p Netflix stream. Video was up to two seconds behind the audio but after a scene cut it was in sync again for 1 or 2 minutes. Maybe it has something to do with the cpu temperature.

I'm using the Pi4 without a case but I have a hifiberry on the GPIO

Quite certainly the CPU was maxed out and the RPi couldn't keep up with decoding the video.

While that can be caused by high temperature (and thus throttling, in which case you should see the thermometer icon pop up) I've also seen that with some streams (eg Black Mirror S01E02 at around 59:30-1:00:00) which have very high peak bitrate scenes.

The RPi4 probably needs to be overclocked to keep up with this - or switch to the next lower bitrate stream (IIRC the ~7Mbit/sec 1080p Black Mirror stream peaked to about 11-13Mbit/sec and ran into a/v sync issues, the ~6Mbit/sec 1080p stream played fine). Limiting the max bitrate may also help with that.

so long,

Hias

Quote from bbro_spo

This is what I assumed, but also read that libreelec ships with upgraded firmware. So, is that true? Does it flash the (Pi Hardware) firmware on (Libreelec) version updates?

LE 9.1.002 ships with updated VideoCore / VPU firmware - the other 2 firmwares (bootloader and USB chip) which are in flash chips aren't touched.

so long,

Hias

Try disabling the pvr client addon, reboot and check if you still have high CPU usage.

Can't recommend anything else ATM without seeing your full debug log.

so long,

Hias

Can you post kodi debug log as well? perf top shows some hefty xml prcessing going on - could be pvr/xmltv addon for example.

so long,

Hias

You can run perf top and check kodi debug log to get some more detailed info. Such high CPU load is definitely not normal - most of the time that's caused by some misbehaving/broken addon.

so long,

Hias

Easiest way is to enable debug logging in kodi and then watch kodi log as you press buttons. eg

tail -f .kodi/temp/kodi.log

You can also use evtest from the system tools addon, but you have to make sure you've stopped kodi and eventlircd as both of them might grab the input device and thus evtest doesn't report any buttons/keys (evtest will warn you about that). BTW: If eventlircd grabbed the remote input button presses will show up as LIRC events instead of keyboard/input events in kodi.

so long,

Hias

This is a known issue. With the updated firmware it's a lot better (but still not 100% perfect). An updated LibreELEC version (with new firmware) should be released real soon now.

BTW: You can also disable the slide animations in Estuary skin setting if the tearing is too annoying for you.

so long,

Hias

The LE kernel has a built-in initramfs, taking care of the early linux init steps of LE, so using it on another distro won't quite work (it'll have exactly the result you posted).

It's probably easiest to just build a kernel yourself, using the LE kernel config linux.arm.conf

so long,

Hias