RetroELEC Kodi+Wayland+Emulationstation+RetroArch (x86/XU4/RPi)

    And you have quotes around /path/to/script.sh? Like I posted earlier : XBMC.System.Exec("/storage/script.sh")

    Quote from andersos

    And you have quotes around /path/to/script.sh? Like I posted earlier : XBMC.System.Exec("/storage/script.sh")

    Yeah tried this with and without... Still no luck.

    Also tried dos2unix on scripts etc as was thinking it might be because I'm using windows. But still nothing.


    Update:

    Been at this for ages.... Not the type to give up.

    Have spent some time now trying to get it to launch from emulation station side. Again.... getting it in the menu is easy just cant get it to launch.

    Going to boot linux up tonight or tomorrow and write scripts from there and see if it makes any difference.

    Again thanks for any help its much appreciated.

    Edited once, last by scottglindsay (November 1, 2017 at 7:40 PM).

    escalade

    Build LibreELEC-Generic.x86_64-8.2-devel-20171027.img

    23:30:54.189 T:139676094560000 ERROR: Unable to load libnfs.so.11, reason: libnfs.so.11: cannot open shared object file: No such file or directory

    23:30:54.189 T:139676094560000 ERROR: NFS: Error loading libnfs (HandleDyLoad).


    -> Kodi 17.5 needs to be recompiled to include nfs support again?


    PS:

    Build LibreELEC-Generic.x86_64-8.2-devel-20171024.img works fine :)

    23:45:21.324 T:139903846156416 NOTICE: VideoPlayer: Opening: nfs://192.168.1.....

    Edited once, last by 5schatten (November 1, 2017 at 10:47 PM).

    Dear escalade,

    there is one thing that i found in your recent build (LibreELEC-Generic.x86_64-8.2-devel-20171102.tar).

    The disc tray opening command is not working anymore.

    I tried this function with several different skins, but without success.

    Update:

    I tried to reject the BD of the drive manually, using the console terminal via Putty.

    I even can´t get a SSH connection to my system anymore.

    Just getting now the error message "Network error. Connection refused"

    Edited once, last by Samui (November 2, 2017 at 3:14 PM).

    Edit3 (2017-11-04):

    Found a working microSD card (an older 16GB one).

    Code
    #dmesg
<snip>
[44958.212991] mmc2: new high speed SDHC card at address 1234
[44958.213697] mmcblk2: mmc2:1234 SA16G 14.6 GiB 
[44958.215760]  mmcblk2: p1
[44958.612711] EXT4-fs (mmcblk2p1): mounted filesystem with ordered data mode. Opts: (null)

#df -hT
<snip>
/dev/mmcblk2p1       ext4           14.3G     36.6M     13.5G   0% /var/media/mmcblk2p1-mmc-SA16G_0x2d4b0aeb

    Googling further found a reference to an Tronsmart forum thread (currently under maintenance):

    1397-micro-sd-card-compatibility-thread

    But already indicating the Tronsmart Ara X5 Plus is picky regarding microSD cards.

    [/Edit3]

    A microSD On the Tronsmart Ara X5 Plus is not working.

    I'm trying to use a FAT32 formated microSD card in the external microSD slot, but get the following error:

    Code
    # dmesg | grep -i mmc2
[    2.306880] mmc2: SDHCI controller on ACPI [80860F14:03] using ADMA
[    2.554270] mmc2: error -110 whilst initialising SD card
[  910.604454] mmc2: error -110 whilst initialising SD card
[  932.276147] mmc2: error -110 whilst initialising SD card
[ 1555.050434] mmc2: error -110 whilst initialising SD card

    (a timeout error according: Error -110 whilst initializing SD card - Raspberry Pi Forums)

    I tried a full format to FAT32 (on a windows machine), but no change.

    Edit (2017-11-03): tried a few other cards with same or similar results:

    Code
    Using a 64GB microSD card gives (from a RPi3 without reformatting):
[88714.382270] mmc2: error -84 whilst initialising SD card
Using a 8GB microSD card gives (from a RPi3 without reformatting):
[89282.452225] mmc2: error -110 whilst initialising SD card
Using a 128GB microSD card gives (from a RPi3 without reformatting):
[89418.383785] mmc2: error -110 whilst initialising SD card

    (error -84 is a 'illegal command sequence' according: error -84 (when hot?) - Raspberry Pi Forums)

    Edited 4 times, last by RomMon: Testing other uSD cards (February 20, 2020 at 11:40 PM).

    escalade

    Thank you for the continued work you put into this build. Its awesome. Thank you.

    For anyone having controller issues.

    I wanted to share my experience regarding recent Bluetooth controller issues. This is a retroarch issue, not an le8 remix issue. This isn't very specific, quite vague, and I don't really know how I fixed my problem, but I thought it might help someone.

    I haven't fired up emulationStation in a while, but I regularly update le8 remix on my pi2(s), its the best thing I've used since using the original xbox days from years ago. I booted a rom last weekend, and the controller would not work in retroarch. It worked in kodi. It worked in emulation station. However, it did not work in retroarch at all. I've searched through the forum and seen others mentioning similar issues. I messed around with it for a few hours and it finally got it working on one of my pi2's, but not the other. I was convinced it was because of the bluetooth dongle. This weekend and swapped my bluetooth dongles and it didn't change anything for either of my pi2's. I spent a few hours this weekend and got it working for my other pi2 (with the different dongle).

    This is what I (kinda) think solved my issue. I first got my ps3 controller working in kodi. Then I booted into eS and got the controller working there ... Then I exited back to kodi. I ssh'd into the pi2 and ran either the retroarch.sh or retroarch.start (not sure it it matters) with the ps3 controller disconnected. If I connected the ps3 controller, the d-pad didn't work quite right and it screwed up the keyboard input ... So make sure the ps3 controller is disconnected ... I navigated to input with a usb keyboard. I turned on the option to allow all controllers to navigate retroarch menu then I went to controller one bind all ... at this point I turned on the ps3 controller and I found that I could configure the ps3 controller. It then sort of worked, some buttons didn't, it still had some weird issues. I could navigate the menu in retroarch with both my keyboard and ps3 controller ... If I loaded a rom, then D-pad right would bring me back to the retroarch menu rather than send right to the emulator, but most of the other buttons worked as is. However, when I exited retroarch back to kodi and went to emulators (emulation station) as normal ... it just worked. It just works now. I'm not really sure what did it. I had previously copied the entire retroarch and emulation station folder under ./config from the working pi to the non-working one, and the non working didn't start work, but doing what I described above resulted in it just working again (i think).

    This is vague, but it did finally work. I hope this helps someone.

    Edited once, last by dtw_2000: grammer (November 18, 2017 at 12:01 AM).

    Hi I already have stable libreelec 8.1.2 on my NUC. If I use this by placing the file in the update folder will it update and keep my previous settings like PVR channels or will it overwrite everything. Sorry for noob question I am new to all of this many thanks

    Hi, I have it installed and working on a Intel I3-4010U box. I would like to know how I can get it work with my favorite Skin, "New Moded version of AeonMQ6 for Krypton". I do not really use the browser or spotify (can not exit Spotify once launched, I have to reboot). I would like it to launch "Emulation Station" from the "GAME" menu. Can it be done?

    Quote from mwake

    Hi I already have stable libreelec 8.1.2 on my NUC. If I use this by placing the file in the update folder will it update and keep my previous settings like PVR channels or will it overwrite everything. Sorry for noob question I am new to all of this many thanks

    This build is bigger and needs a bigger partition I believe, but you can do a system and kodi backup from libreelec and them just move the the backup from the back up folder to another computer. Do a fresh install and move the backup back into the backup folder and do a restore. Works for me. Not sure if there is an easier way.

    Quote from gwilly7

    This build is bigger and needs a bigger partition I believe, but you can do a system and kodi backup from libreelec and them just move the the backup from the back up folder to another computer. Do a fresh install and move the backup back into the backup folder and do a restore. Works for me. Not sure if there is an easier way.

    Thankyou for your quick reply! If that's the definite answer then thats a lot of work for me lol. I haven't found a way to easily save my PVR settings (took all day to organise iptv channels). I'm a bit busy at the moment so if there isnt an easy way to just upgrade and keep settings Ill wait till vacation so I can do a fresh install as you suggested. Regardless thanks again for reply and thank you to the developer for this work :)

    Edit (2017-11-19):

    Restored to LibreELEC-Generic.x86_64-8.0-devel-20170621.img.gz for the moment, and with this image I don't have an issue stopping Spotify using [ALT]+[ESC].

    Edit (2017-11-12):

    Found a bit of a workaround.

    copied the Estuary skin to storage, and added a menu item to kill spotify, and start pulseaudio again.

    I haven't played much with it yet, but found just killing spotify + starting pulseaudio wasn't enough.

    See note below.

    Code
    cp -r /usr/share/kodi/addons/skin.estuary/ /storage/.kodi/addons/
vi /storage/.kodi/addons/skin.estuary/xml/Home.xml
:901
<add below additional menu item>
systemctl stop kodi
systemctl start kodi

    Item menu added:

    Code
    <item>
        <label>Stop Spotify</label>
        <onclick>XBMC.System.Exec(/storage/.config/stopspotify.sh)</onclick>
        <thumb>DefaultAddonMusic.png</thumb>
        <property name="id">Stop Spotify</property>
</item>

    NOTE: Below script isn't optimal, and I observe that I need to execute it twice to 'hear the click sound' while navigating the menu in Kodi. Killing spotify, and starting something with audio does work already with the first try. Executing the scrip form cli always gives the 'click sound' the first time, but not from within Kodi? (You can test with: sh -x /storage/.config/stopspotify.sh )

    Script:

    # cat /storage/.config/stopspotify.sh

    Bash
    #!/bin/sh
pkill spotify
sleep 3
#systemctl stop pulseaudio
#kodifreeze.sh freeze muteonly
systemctl start pulseaudio
#kodifreeze.sh unfreeze muteonly

    chmod +x /storage/.config/stopspotify.sh

    [/Edit]

    Edit 2 (2017-11-12):

    Just to give a better problem description including the use of above script:

    - Staring Spotify normally always works (99%)

    - Closing the Spotify window with [ALT]+[ESC] always works (100%), but nearly always (95%) of the time sound keeps going.

    - Using above script from CLI always works (100%) to kill Spotify and get sound back to Kodi.

    - Using above script from the added Kodi menu always kills Spotify (100%), and always works (100%) to have sound for started items (e.g. LiveTV, video, music), but menu-sound (moving through the menu with a remote gives a click sound) only get restored after a second time (100%).

    [/Edit 2]

    ==================================================================================================================

    Now playing with Spotify I do noticed sound keeps running after quitting (ALT+ESC).

    Had the same yesterday also.

    (LibreELEC-Generic.x86_64-8.2-devel-20171016.tar, cherry trail)

    ps shows spotify is still running.

    Code
    # ps -ef | grep -i spot | grep -v grep
 1904 root       0:00 {spotify} /bin/sh /usr/bin/spotify
 1916 root       3:58 /storage/.cache/app.spotify/spotify
 1918 root       0:00 /storage/.cache/app.spotify/spotify --type=zygote --no-sandbox --lang=en-US --log-file=/storage/.cache/app.spotify/debug.log --log-severity=disable --product-version=Spotify/1.0.57.474
 1939 root       2:34 /storage/.cache/app.spotify/spotify --type=gpu-process --no-sandbox --lang=en-US --log-file=/storage/.cache/app.spotify/debug.log --log-severity=disable --product-version=Spotify/1.0.57.474 --supports-dual-gpus=false --gpu-driver-bug-workarounds=1,7,23,61,74 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --gpu-vendor-id=0x8086 --gpu-device-id=0x22b0 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --lang=en-US --log-file=/storage/.cache/app.spotify/debug.log --log-severity=disable --product-version=Spotify/1.0.57.474 --service-request-channel-token=8C4AB353FFED75EF748DFAC7321F77CD --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd
 1952 root       5:24 /storage/.cache/app.spotify/spotify --type=renderer --disable-pinch --no-sandbox --primordial-pipe-token=282CFD01371A42FB4697754B4D891313 --lang=en-US --lang=en-US --log-file=/storage/.cache/app.spotify/debug.log --log-severity=disable --product-version=Spotify/1.0.57.474 --disable-spell-checking --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553 --disable-accelerated-video-decode --service-request-channel-token=282CFD01371A42FB4697754B4D891313 --renderer-client-id=3 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd

    Edit (2017-11-06):

    The created spotify log is filling with '(spotify:1916): GLib-GIO-CRITICAL **: g_dbus_connection_send_message: assertion 'G_IS_DBUS_CONNECTION (connection)' failed'

    Edit2 (2017-11-06):

    Tried again, and this time ALT+ESC correctly terminated Spotify.

    Spotify log:


    Ps is still showing the old process running (1916):

    Code
    # ps -ef | grep -i spot | grep -v grep 1904 root       
 0:00 {spotify} /bin/sh /usr/bin/spotify
 1916 root       6:48 /storage/.cache/app.spotify/spotify
 1918 root       0:00 /storage/.cache/app.spotify/spotify --type=zygote --no-sandbox --lang=en-US --log-file=/storage/.cache/app.spotify/debug.log --log-severity=disable --product-version=Spotify/1.0.57.474
 1939 root       2:34 /storage/.cache/app.spotify/spotify --type=gpu-process --no-sandbox --lang=en-US --log-file=/storage/.cache/app.spotify/debug.log --log-severity=disable --product-version=Spotify/1.0.57.474 --supports-dual-gpus=false --gpu-driver-bug-workarounds=1,7,23,61,74 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --gpu-vendor-id=0x8086 --gpu-device-id=0x22b0 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --lang=en-US --log-file=/storage/.cache/app.spotify/debug.log --log-severity=disable --product-version=Spotify/1.0.57.474 --service-request-channel-token=8C4AB353FFED75EF748DFAC7321F77CD --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd 1952 root       5:47 /storage/.cache/app.spotify/spotify --type=renderer --disable-pinch --no-sandbox --primordial-pipe-token=282CFD01371A42FB4697754B4D891313 --lang=en-US --lang=en-US --log-file=/storage/.cache/app.spotify/debug.log --log-severity=disable --product-version=Spotify/1.0.57.474 --disable-spell-checking --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553 --disable-accelerated-video-decode --service-request-channel-token=282CFD01371A42FB4697754B4D891313 --renderer-client-id=3 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd

    .

    Edited 11 times, last by RomMon: share possible workaround (February 20, 2020 at 11:38 PM).