Posts by HiassofT

  • Raspberry PI 4B, Sharp Aquos (~2011), LibreElec = Scrambled Video

    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

    Code
    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

  • Is there an addon or a command to detect remote key for RF remote like LIRC ?

    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:

    Code
    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:

    Code
    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

  • Is there an addon or a command to detect remote key for RF remote like LIRC ?

    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

  • My 12GB SD card has filled up in a day

    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

  • My 12GB SD card has filled up in a day

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

    eg post the output of

    Code
    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:

    Code
    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

  • LibreELEC (Leia) 9.2 ALPHA1 with Raspberry Pi 4B Support

    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

  • LibreELEC (Leia) 9.1.002 ALPHA

    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

  • Is there an addon or a command to detect remote key for RF remote like LIRC ?

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

    Code
    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

  • LibreELEC (Leia) 9.2 ALPHA1 with Raspberry Pi 4B Support

    Quote from @fterlife

    Both of the mentioned log files don't seem to give any extra info and simply repeat the error I quoted here. Hopefully this will shed some light on the issue.

    Please post the contents of the logfiles, sometimes they contain references to other logs (eg failed dependencies) so it's worth to check them, too.

    If in doubt capture the full build log and upload it somewhere (it could be huge, though). eg

    Code
    ARCH=arm PROJECT=RPi DEVICE=RPi4 make image 2>&1 | tee build.log

    so long,

    Hias