[8.0.2e] LibreELEC 8.0 for S905/S905X

    Solution/Update: From another LibreElec thread I learned to disable/change HDMI-CEC settings in Kodi by going to Settings > System > Input > Peripherals > CEC. Problem solved!
    - - - -
    Just installed 8.0.0b on a NexBox S905 1G/8G. Previously ran 7.0.3.12c through 12i. Upgraded to 7.95.beta6 and instantly onwards to 8.0.0b.

    I'm experiencing an automatic shutdown of Kodi after changing HDMI source away from my Kodi box (HDMI2) to Chromecast (HDMI1). Log file:

    • Feb 21 09:30:37 Kodi: 09:30:37.365 T:4119078928 NOTICE: OnSleep: Running sleep jobs
    • Feb 21 09:30:37 Kodi: 09:30:37.365 T:4119078928 NOTICE: OnSleep: Stopping lirc

    The shutdown behavior is unwanted. How do I disable this auto-shutdown?

    Clarification: Kodi and LE runs perfect when in use (in my case, on HDMI2). If there's no activity, while the TV stays on HDMI2, Kodi simply dims the display (as intended) - and all is well, ready to resume. But if switch to HDMI1 (my chromecast), Kodi/LE will power itself off after a short period of time with the following two log entries: 1) "Feb 21 10:53:30 Kodi: 10:53:30.505 T:4119967760 NOTICE: OnSleep: Running sleep jobs" and 2) "Feb 21 10:53:30 kodi 10:53:30.506 T:4119967760 NOTICE: OnSleep: Stopping lirc".

    Edited once, last by fxfxfx (February 22, 2017 at 12:22 PM).

    The 64bit img for LibreELEC.tv-8.0.0a can be found at
    LE – Google Drive
    Together with two add-ons (which I use to watch and stream DVB-T2 Radio/TV)
    pvr.hts-3.4.18.1
    service.tvheadend42-8.1.109
    Works for me.
    Built from unmodified source.
    I will soon build 8.0.0b or perhaps wait for next release.

    Edited once, last by Nofan Tasi (February 21, 2017 at 9:53 PM).

    Quote from kszaq

    There is a new cheap Chinese WiFi chip in some of the boxes that does not have drivers available. You can check what chip you have by running udevadm info /sys/bus/sdio/devices/sdio*.


    Hi kszaq, this is the results of the command above:

    Code
    P: /devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DEVPATH=/devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: MODALIAS=sdio:c07v3030d3030
E: SDIO_CLASS=07
E: SDIO_ID=3030:3030
E: SUBSYSTEM=sdio
    Quote from willyfan


    Hi kszaq, this is the results of the command above:

    Code
    P: /devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DEVPATH=/devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: MODALIAS=sdio:c07v3030d3030
E: SDIO_CLASS=07
E: SDIO_ID=3030:3030
E: SUBSYSTEM=sdio

    This doesn't look good... Please get a list of Android kernel modules:

    Code
    mkdir -p /tmp/system
mount /dev/system /tmp/system
find /tmp/system -name *.ko


    [hr]
    michael123 Thank you! And I thank everyone who donated!

    Edited once, last by kszaq (February 21, 2017 at 10:00 PM).

    Quote from kszaq

    This doesn't look good... Please get a list of Android kernel modules:

    Code
    mkdir -p /tmp/system
mount /dev/system /tmp/system
find /tmp/system -name *.ko


    [hr]
    michael123 Thank you! And I thank everyone who donated!

    Code
    /tmp/system/lib/8189es.ko
/tmp/system/lib/8189fs.ko
/tmp/system/lib/8723bs.ko
/tmp/system/lib/9082xs.ko
/tmp/system/lib/aml_thermal.ko
/tmp/system/lib/audio_data.ko
/tmp/system/lib/dwc_otg.ko
/tmp/system/lib/ssv6051.ko

    willyfan You have ssv6051 WiFi chip - another one without drivers, yay!

    You can try doing this:

    Code
    mkdir -p /tmp/system
mount /dev/system /tmp/system
modprobe cfg80211
modprobe --force /tmp/system/lib/ssv6051.ko

    And see if WiFi works... but most probably it won't.

    Quote from kszaq


    willyfan You have ssv6051 WiFi chip - another one without drivers, yay!

    You can try doing this:

    Code
    mkdir -p /tmp/system
mount /dev/system /tmp/system
modprobe cfg80211
modprobe --force /tmp/system/lib/ssv6051.ko

    And see if WiFi works... but most probably it won't.


    at last command I receive the error:

    modprobe: FATAL: Module /tmp/system/lib/ssv6051.ko not found in directory /lib/modules/3.14.29

    ....

    Hello,
    thanks Raybuntu, and Kszaq for the work you do.
    Yesterday I tried to install the hub nand wetek, version LibreELEC-WeTek_Hub.arm-8,0-rb-krypton1.img.gz of Raybuntu.
    - I installed before LibreELEC-WeTek_Hub.aarch64-7.90.010.zip;
    - Then I gave the command with putty: touch /storage/.update/.nocompat;
    - Then I put in the update folder LibreELEC-WeTek_Hub.arm-8,0-rb-krypton1.img.gz.
    E 'went well apparently.
    I tried to play through LAN HEVC 23.976 fps film, but it was jerky.
    Maybe I did something wrong during the installation?
    The same film with the 8.0.0b version of kszaq have no problem.
    It 'possible that the versions of Raybuntu, that are specific to wetek hub, work worse than the versions of kszaq?
    Now I'm using the 'latest version of kszaq (8.0.0b) of the NAND wetek hub. When I play H264 and H265 seems to be going much better.

    Edited once, last by dibotto (February 22, 2017 at 1:27 AM).

    kszaq, thanks for implementing the remotesecond.conf support.

    I've tested it works only if remote.conf exists as well in the /storage/.config folder. I was hopping that only dropping in the remotesecond.conf into the .config folder and works.

    Hey,

    thank you for another cool release. I have a question to all of you. Do any of you notice that GUI is not as smooth anymore as it was in Jarvis?
    When booted up the GUI smoothness is pretty ok and then becomes sluggish over time compared to Jarvis releases...I don't notice any abnormal RAM usage, just the transitions in menus are not so smooth? It's pretty much the same if I use it on USB or SD card - it works flawlessly on the same storage in Jarvis.

    Quote from panterck


    Hey,

    thank you for another cool release. I have a question to all of you. Do any of you notice that GUI is not as smooth anymore as it was in Jarvis?
    When booted up the GUI smoothness is pretty ok and then becomes sluggish over time compared to Jarvis releases...I don't notice any abnormal RAM usage, just the transitions in menus are not so smooth? It's pretty much the same if I use it on USB or SD card - it works flawlessly on the same storage in Jarvis.

    I noticed something similar. Even video starts lagging if you scroll through the gui.