Posts by Roby77

    What is waf test ( wife acceptance factor ? ) ?

    Since fritsch's oe build no problem with avshd test

    Same for libre 8

    Which tv are you speaking of ?

    If i remember correctly if av doesn't have full and limited setting...it's limited


    I'm hitting the same thing.

    LibreELEC build #0501
    NUC- NUC5PGYHR
    BIOS- PY0053 - 4/1/2016

    TACU and BUPP

    I can only use box for 1-4 mins before it locks up. Strangely enough the SSH session is still active after KODI locks up so the box isn't hardlocked.

    I've tried disabling all C States thinking it was related to this bug 88012 – [bisected BYT] complete freeze after: drm/i915/vlv: WA for Turbo and RC6 to work together but that did not help.

    Use build #420

    Build released after crash due a kernel bug

    Maybe rc6 will solve it

    LibreELEC Testbuilds for x86_64 (Kodi 17.0)


    Your error linked imho is abou a bug with q1900 and cstate ( never solved if i remember correctly)

    You have a braswell cpu/gpu

    Just curious and want to see if i'm the only one

    Hardware :

    Haswell chromebox and Beebox N3150

    Denon Avr x2000

    Panasonic plasma

    Starting from oe 17 i'm experiencing black screen when i stop a movie...need to reboot chromebox

    Tried forcing Edid as wiki suggested no solved

    BUT if i force gui to 60hz instead of 50hz problem is solved


    So when beebox arrived i switched of chromebox and did a fresh libre 8 install

    And the problem reappear

    I didn't try yet edid solution but forcing 60hz via gui now doesn't help

    Need to reebot hardware or restart kodi via ssh

    Ah...I think what has happened is that 2-3 days ago the 16-235 patch was added to a pending PR that I'm using which meant I could drop the 16-235 patch I'd been using up until that point from my builds... now I see the 16-235 patch is no longer in the pending PR, so it's no longer in the build at all. I'll restore the patch I'd been using to my build.

    thank you!

    Waiting for my beebox i formatted chromebox and tried a new setup

    Downloaded official libreelec and upgraded with v17 if i set 16-235 i get washed black

    And using xrandr --verbose rgb settings is in automatic instead of video 16-235 passthrough

    What's up ?

    With old setup from oe v.15 >fritsch v.17 and finally upgraded to libre milhouse v17 i had video 16-235 passthrough and use 16-235 setting

    edit:maybe libreelec source miss autostart line for xrandr ?

    could anyone check via xranrd --verbose what rgb mode is in use ?

    Try providing a tvheadend log, although those tvheadend builds are based on ffmpeg2 while the LE8 builds are based on ffmpeg3 so may not work. When tvheadend is building against ffmpeg3 I'll provide updated builds, until then it's not really my priority, and you may have to stick with LE7/OE7 if you must have tvheadend.

    Not a big problem, just an user a page ago asked me to test and i tried

    I really don't know what tvheadend is for :D


    A little confused on naming here, hope someone can help. I switched from openelec to libreelec. Was already vaguely aware of something called Milhouse builds through a topic on the Kodi site, which I think are really up to date alpha versions for those wanting to test the latest and greatest.


    Now I see a reference here to Milhouse generic builds and the path to that is on the libreelec site as well (Index of /builds/master/), so should I now consider this "pre-alpha" versions of Libreelec? That might eventually make it to "official" Libreelec builds? For those more courageous to test early changes?

    Generic in download section are Jarvis (kodi 16) based without Egl driver

    Generic linked here are krypton (kodi 17 alpha) based with Egl driver (LibreElec 8)


    Am I right in thinking you can add millhouses builds as a custom path in dev update?
    I've been trying to install dev update and nothing installs or have I got it totally wrong


    Devupdate addon doesn't work also for me with librelec custom source

    No builds were found for Generic X86_64

    Probably it search for oe filename

    Put manually the tar file in update folder