Posts by nvdias

  • "pulse-eight cec adapter" notification stuck on screen on 9.2.3

    Found it !

    So, let me explain:

    Following HiassofT sugestion of renaming .kodi and running a clean kodi install: Everything works just fine ! No stuck notification

    So: What's wrong ?

    Back to "my" .kodi.

    Went into peripheral definitions, looking into userdata, but nothing.

    Started to remove everything that it was not default, disabled and enable add-ons, etc ...

    And remembered to looin into config files, as .... advancedsettings.xml

    namely this section:

    Code
    <gui>
  <algorithmdirtyregions>0</algorithmdirtyregions>
  <smartredraw>true</smartredraw>
</gui>

    Removing this part from advancedsetings.xml solves the problem of the hanging cec notificaiton at startup.


    Thank you HiassofT for pointing out the way

    :)

  • "pulse-eight cec adapter" notification stuck on screen on 9.2.3

    Quote from HiassofT

    CEC is working fine here, too (RPi4, LG TV), and I haven't spotted any CEC related changes between 9.2.1 and 9.2.3 yet.

    nvdias could you try replacing start.elf and fixup.dat in /flash with the files from 9.2.1 and test if this makes a difference?

    so long,

    Hias

    Hi,

    I've made as you suggested replacing start.elf and fixup.dat with the ones from 921 over 923.

    The same issue: Stuck pluse-eight CEC adater notification

    Back to 9.2.1: All ok

    Quote from HiassofT

    ah, and it would also be interesting to see the full kodi debug log and journal after the stuck notification appeared.

    ssh in, then run pastekodi and post the URL.

    so long,

    Hias

    HiassofT I have the logs from a run with 9.2.3 and the notification stuck.

    But they have a lot of personal info (tvhaedend, inadyn, letsencrypt, they all place to much personal info in the journal).

    May I send-them to you as an attachment by private message ?

    EDIT: There is no info about the notification in the logs, but I may share them anyway,

  • "pulse-eight cec adapter" notification stuck on screen on 9.2.3

    I've updated from Libreelec 9.2.1 to 9.2.3.

    Running on a Raspberry Pi 4, 4GB

    At boot I now get

    "pulse-eight cec adapter" notification stuck on screen.

    It does not go awaing and prevents any other notification to be displayed.

    Going back to 921, it works ok.

    Back again o 923: notification stuck.

    Is there any idea on what may be the issue ?


    I've compared kodi.log from both 921 and 923 versions using winmerge and there is no differences (besides the obvious version changes in libreelec, kodi and kernel):

    There is also no warning or error reported in journal regarding hdmi or cec


    diff lines in 921:

    Code
    NOTICE: Starting Kodi (18.6 Git:leia_pi4_18.6-Leia). Platform: Linux ARM 32-bit
NOTICE: Using Release Kodi x32 build
NOTICE: Kodi compiled 2020-03-03 by GCC 8.3.0 for Linux ARM 32-bit version 4.19.106 (267114)
NOTICE: Running on LibreELEC (official): 9.2.1, kernel: Linux ARM 32-bit version 4.19.106

NOTICE: ADDON: xbmc.addon v18.6.0 installed

over_voltage_avs=-23750

NOTICE: Checking resolution 23

    dff lines in 923:

    Anyone else with this issue ?

  • RPi 4 - 9.2.1 - Live TV Playback (interlacing and aliasing issues)

    Quote from chewitt

    ... Do not "sync playback to display" ....

    Exactly.


    Quote from kreeture

    Thanks guys,

    Interestingly there is no 25hz option for 1080 and I tried just whitelisting 1080 at 50 but I still get the judder as the TV is switching to 1080p.

    Is there anyway to force Kodi to use 1080i instead, maybe this would solve my issue?

    Just whitelist 1920x1080@ 50, disable sync playback to display, and enable "Adjust display refresh rate" "on start/stop".

    That would be all you need.

    I use a usb dvb-c receiver and there are no issues .

    ---

    You should also look into your tvheadend configuration:

    Aren't you using any stream processing that may be changing the framerate ?

    Try to force "pass" profile as default.

    The attached images are my "Pass" and "htsp" profiles current configurations:

    (tweaked a little bit to get best results with handling some video artefacts in reception)

    [configuration / stream / streamprofiles]

    I also use:

    "General / base / packet backlog" : active

  • [UPDATED] OpenVPN Server for LibreELEC

    #UPDATED Version 1.0.9 - 27th September 2022

    Running with LE11 (and E12)

    # UPDATED Version 1.0.6 --- 19th March 2021

    Now runs in both LibreELEC 9.X and 10.X

    Link update bellow

    # INTRO

    I've made a small openvpn server that can be installed on LibreELEC running raspberry pi devices (and eventually other arm devices).

    The server runs in a small docker image (around 20MB) that is automatically loaded on first start

    After first run, you should configure your server address giving its ddns name or wan ip address.

    Then, START THE ADDON and go to your ssh CONSOLE and run:

    "openvpn-add-server" to:

    - create the server config and keys;

    - define your router address (so your openvpn clients can get access to your lan).

    Note that the keys will take up to 15 minutes to create in a Raspberry Pi 4 (be patient).

    Then call:

    "openvpn-add-user" to:

    - create users and get the ovpn file of each one.

    Theses are the files you must give to the client to acess your openvpn server using an openvpn client software.

    Restart the add-on and it's done !

    ### DOWNLOAD HERE

    Version 1.0.9 - LE11 & LE12

    https://mega.nz/file/EOAhCYDb#WtSj0s5-jXdcuqftXOD0IOUGaBV-UxjhrpF3_T8EsRQ

    # TECH STUFF

    ### The docker is hosted in:

    Docker Hub

    ### The git source is:

    GitHub - nvdias0/rpi-docker-openvpn: Docker OpenVPN image for Raspberry Pi

    it is a fork from olivierguerriat/rpi-docker-openvpn, which in turn is a fork from kylemanna/docker-openvpn with an armhf base image

    Look at those links above if you want to know more.

  • LibreELEC 9.2.X video judder and stuttering [renamed]

    Quote from Mattx

    So, your RasPi connects directly to the TV, without AV-Receiver?
    Could you do me a favor: While judder and frame-dropping...can you switch off the TV (let the RasPi run!) and switch it on after 20 seconds again.
    Does this make any difference and the judder is gone for a few minutes? Thanx, Greetings!

    That's what happens to me at the moment: First I had the same problems you described in the first post, than I could get rid of it for a few weeks ( algorithmdirtyregions) and now all is back much worse.

    I've also tried algorithmdirtyregions. But after some time, all the isswues were back.

    The set of setting above is giving the best results.

    Note: I've tried your test ith the TV, But I notice no diference - I'm using a Sony Android TV (2016 model) with a Raspberry Pi 4.

  • LibreELEC 9.2.X video judder and stuttering [renamed]

    I've watched somme movies which had judder with MMAL other without-it.

    After some more testing, I've had the most stable video viewing experience using the following set of settings:

    Settings

    Player

    Adjust display refresh rate ALWAYS

    Sync playback to display YES

    Enable HQ Scalers above 50%

    Allow hardware accel. MMAL YES

    System / Display

    White list - only All 1920x1080 resolutions (this will force upscaling in kodi when needed)

    Preferred mode Same as Movies

    System / Audio

    Allow passthrough NO


    (The bold settings seems to be the more influent)

  • Docker crashing in LibreELEC 9.2 beta 2

    I need to revive the thread:

    I've been noticing that my simple web server running over docker's container "linuxserver/letsencrypt" is stopping.

    After several days looking into the logs, I've found that it only happens after a docker update as the one following:

    Code
    Apr 20 04:05:00 LibreELEC crond[2632]: USER root pid 4212 cmd /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/update.sh > /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/update.log && /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/prune.sh > /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/prune.log

    At this time docker container stops and do not start again unless I reboot the system.

    I'm using LibreELEC 9.2.1 runnng in a RPi 4

  • Docker crashing in LibreELEC 9.2 beta 2

    I was able to replicate the problem with a fresh install:

    I've Installed LibreELEC 9.1.502 in another new 8GB SD-CARD in my Pi 4 4GB.

    After 1st boot configured ssh, wired ethernet, fixed ip (into which my router forwards ports 80 and 443).

    Activated debug logging.

    Installed docker, linux.io repo and the add-on with letsencrypt and nginx

    Configured ddns in the add-on as requested per install.

    All seem to be ok.

    After another reboot, docker crashed as in my initial SD-CARD.

    (as before, this happens roughly 1 in each 3 reboots).

    This happens only in beta 2. In beta 1, All is ok.


    This url is for full untouched logs of this fresh install:

    http://ix.io/20xr

    (search for "segmentation fault")

    Hope this help in finding the issue.


    Thanks Guys.

    LibreELEC has been awesome !

  • Docker crashing in LibreELEC 9.2 beta 2

    LibreELEC 9.2 Beta 2 and Docker

    I'm creating this thread to easily read and get support :), as the previous post was placed in the news section.


    Updated the system to Beta 2

    I have docker installed with only the official container for letsencrypt and nginx.

    a) At each 3 reboots, docker fails, at least 1 time - sometimes work, sometimes don't - always working fine in beta 1;

    b) Doing a "docker restart docker.linuxserver.letsencrypt" in ssh shell, takes a lot of time (compared to Libreelec Beta 1) and fails to start again a lot of times.

    c) System shutdown / reboot taking a lot of time (a stop job is running for docker container .... 3 minutes) - almost immediate with beta 1

    Logs from a failed docker start after system boot:

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.



    Note docker crashes in this lines:

    Code
    Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.760117072+01:00" level=info msg="libcontainerd: started new containerd process" pid=430
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.760551072+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.760600776+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.797000224+01:00" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0  <nil>}]" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.797126520+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.797396094+01:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0x4d6ab50, CONNECTING" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.819133578+01:00" level=error msg="containerd did not exit successfully" error="signal: segmentation fault (core dumped)" module=libcontainerd


    Back to LibreELEC 9.1 Beta 1 .. All is fine with docker .. no more core dumps.

    I 've also tried a Beta 2 fresh install in a clean sd-card and got the same symptoms - testing several restarts, and docker fails to start 30% to 40% of the time