Posts by sakos

    Hi guys. I am thinking of upgrading to 8.9, what is the safest way to do this. I would love to just add the TAR file to the update folder but the partition rename from ""libreelec disk"" to ""storage"" , I am guessing this would cause problems. What is the easiest and safest way to upgrade


    Thanks

    I think you can copy the TAR file to the update folder then rename the disk label to "storage" by this command:

    Code
    1. e2label /dev/data "STORAGE" 

    Then reboot the system to start upgrade.

    This is the most simple solution. Anyway, do a backup, should this procedure fails.

    If you saw "Missing (target) kernel.img or SYSTEM!" at boot loop then you probably suffered from the issue described in upgrade/downgrade fault topic.


    My VLC problem is an LE9.0 issue, therefore I cannot upgrade to LE9 and cannot test latest tvhedend builds. This is why I asked if possible to build them for LE8.x.

    Can you explain why LE9 is useless in a Wetek Play1. ?


    i was just about to install LE9 on a Wetek Play1 and use it for Live TV Only with TVHeadend (and possibly IPTV later if possible)


    Could you share your findings ?

    Yes, ofc.

    - VNC is not working. Wetek Play1 no picture (black screen) with LE 8.95.002 if monitor connected later. - LibreELEC Forum

    - Upgrade issues. Wetek Play 1: After upgrade to Alpha 006 (from LE 8) no upgrade/downgrade possible

    - I also read in a local forum that audio pass-trough is not working on the SPDIF out meanwhile the box is getting very hot

    I neither can downgrade back my Wetek play 1 box from LE 8.95.002 to LE 8.2.5.


    (There was also a strange thing seen twice. After upgrade from LE 8.2.5 to LE 8.95.002, copying some files and doing a power cycle the system started with reporting file system corruption error. I let it to correct them - thousands of lines running on the screen - and finally the system was recovered without any obvious loss.)

    LE 8.95.002 is installed on a Wetek Play box. I intend to use this device in headless mode (no monitor attached) and access the GUI by AML-VNC. It worked fine until LE8. However it is not working in LE9 beta. I got black screen via VNC connection.


    Finally I performed a hard reset and found that the screen is black if the HDMI is not connected at boot but connected a bit later. The system is up and running, I can even hear the Kodi GUI clicks if I use the remote but the screen is black on the connected monitor. I can reproduce this issue with default configuration of LE, no add-on installed, nothing configured.

    If the HDMI is already connected when the device boots then everything is fine. If it is not connected before boot then I cannot get picture later.


    Update: Tested again with LE 8.2.5. It works fine. It is a degradation in in LE 8.95.002

    Thanks for the great work!


    I did a quick test. See my observations.

    - If you come from 8.2.3.1 (or similar) kszaq build and "Boot from SD card, use internal memory for data" is active then the 9.0 will fail to boot after the upgrade. To prevent this apply this command after putting the tar file to update folder and before rebooting:

    Code
    1. e2label /dev/data "STORAGE"

    - There is no sound on HDMI output if audio output is set to HDMI. If audio output is set to analog then HDMI output works.

    - CEC is unreliable. It happened twice that CEC was not working after a restart. Once Kodi also crashed during CEC connection establishment.

    Could you please clarify your recommendation?

    I got also this error message:

    Code
    1. ERROR: LibreELEC-S905.arm-8.2.4.2-S905Test-1529136339.tar is not compatible with S905.arm hardware - update cancelled.
    2. Current system: S905.arm
    3. Update system: S912.arm

    The box is X96 (S905X). What do you mean on "bad version"? Shall I really try with the v8.2.4.2-Test2-wetekdvb build on this box?

    Hard to believe that nobody can tell me which image to be installed my S905X box.

    Now I downloaded the LibreELEC-S905.arm-8.2.4.2-S905Test-1529136339.img.gz file and it contains the LibreELEC-S912.arm-8.2.4.2-S905Test-1529136339.img.

    This version is bad, use this, or look at ext4 version.

    Could you please clarify your recommendation?

    I got also this error message:

    Code
    1. ERROR: LibreELEC-S905.arm-8.2.4.2-S905Test-1529136339.tar is not compatible with S905.arm hardware - update cancelled.
    2. Current system: S905.arm
    3. Update system: S912.arm

    The box is X96 (S905X). What do you mean on "bad version"? Shall I really try with the v8.2.4.2-Test2-wetekdvb build on this box?

    I have a normal PC running Libreelec 8.2.3. It is controlled by an MCE remote with its USB IR receiver. The remote power button should suspend and wake up the htpc.


    The problem is that when the PC wakes up it immediatelly goes to suspend again. Sometimes it does not happen if I can push the power button very short.

    It seems the HTPC processes the power button signal after waking up and it triggers the suspend again and again.



    Is there any solution to prevent this behavior? e.g. somehow discard remote commands for some seconds after wake up .

    I have a strange problem with my x96 box remote setup. The proposed remote.conf file is downloaded and installed. Everything work fine except the button "0". Kodi does not really recognizes the scancode. See the debug log when I press the buttons 1,2,3...9,0


    I think the remote.conf is good. Key "0" is mapped to scancode 11d


    Code
    1. 0x4e 2 #1 -> 1
    2. 0x0d 3 #2 -> 2
    3. 0x0c 4 #3 -> 3
    4. 0x4a 5 #4 -> 4
    5. 0x09 6 #5 -> 5
    6. 0x08 7 #6 -> 6
    7. 0x46 8 #7 -> 7
    8. 0x05 9 #8 -> 8
    9. 0x04 10 #9 -> 9
    10. 0x01 11 #0 -> 0

    ***Update***


    The root cause and solution is found. Sharing here if helps someone in the future.

    I have Hungarian keyboard layout set in Kodi. It remaps "0" key to another character. The solution is another scancode to be assigned in remote.conf file. Instead of top row "0" button I assigned the numpad 0/Ins button. See below the change.


    Code
    1. [CODE]
    2. # 0x01 11
    3. 0x01 82
    4. [/CODE]

    Did anyone manage to solve this issue? When my Libreelec box is running at 1920x1080 I get this problem - connect using VNC and you only see part of the screen. Run the box at 1280x720 and VNC works fine and you can see the whole screen.


    Is this something that could be fixed?


    Thanks

    I have the same problem. If the resolution is set to 1920x1080p then only a part of the desktop is visible.


    In case of 1280x720p the complete desktop can be seen, however the resolution is so low that it is absolutely unreadable.



    The client is realVNC VNC viewer 6.17.1113


    Any clue how to make it usable?