It depends on the keyboard but it is generally the key \ or one of the ones close to Enter.

You can remove the USB drive as long as you don't need to read stuff from it.

@mitu settled, many thanks.

@bc320 said in Pi4 and libreELEC: Is there a way to set up my pi so when I boot I can choose LibreElec and Kodi OR Retropie? Using something like NOOBS or PINN could help you install multiple systems on the same sdcard. is there an easy way to move between the 2? Apart from using separate cards, try option 1. if I am able to get a wireless/bluetooth controller to work with retropie will it work with LibreElec? I don't know, if it has bluetooth support built in, then it should work.

@mitu thanks dude, that was it. i had removed everything with kodi- before it in synaptic package manager and then reinstalled kodi from binary in retropie and restarted retropie/es and now kodi shows up and runs within ports! thanks you

I changed my mind. I'm better off watching on the laptop.

Okay, here's what I've got in es_systems.cfg <system> <name>ports</name> <fullname>Ports</fullname> <path>/home/pi/RetroPie/roms/ports</path> <extension>.sh .SH</extension> <command>bash %ROM%</command> <platform>pc</platform> <theme>ports</theme> </system> And then put this in/home/pi/RetroPie/roms/ports/Kodi.sh #!/bin/bash "/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "kodi" ""

Just as I posted this I managed to figure it out. It seams that when kodi in osmc starts a script it starts it in root directory where it has no privilages. Adding "cd /home/osmc" at the beginning of "/home/osmc/RetroPie/scripts/retropie.sh" solved the problem!

@mitu Ah, that scuppers those plans then. I think I'll give this up as a failed experiment. I did manage to get Kodi to launch from my green button by importing psutil and check_output and changing the code to espid = int(check_output(["pidof","-s","emulationstation"])) es = psutil.Process(espid) es.suspend() Kodi = subprocess.Popen("/home/pi/RetroPie/roms/ports/Kodi.sh") Kodi.wait es.resume() But then the script would no longer start from my crontab on boot so not really usable.

In Raspi-Config, Select Advanced, Overscan and then Disable. That should allow your GUI to extend to the edges of your screen. if it's still not to your liking you'll need to change the Overscan value in Config.txt in the /boot partition on your MicroSD card.

@ignatius We don't offer support for 3rd party images - especially the ones sold with RetroPie - https://retropie.org.uk/forum/topic/3/read-this-first. Selling RetroPie is agains the project's license, so you just enriched a scammer. You should ask the seller for support.

So I finally figured it out. As usual it was a couple things, but none of them were as difficult as I was looking for. Everything was a little out of date, and because I was working on wifi, i figured id let it update everything over night. Turns out I hadnt done that since enabling usbrom service. After the update it (mostly) solved my problem, and after putting the pi on stretch instead of Jessie I'm good. Thanks @Efriim for going down the rabbit hole with me. I appreciated your help

@daviduco AFAIk Recalbox uses version 17,not 18 available in Retropie.

Ok thank you it works.

@CapNinja I suggest it can be the timer that leads to such behaviour. After 3s of waiting if the PID is active then a kill term 9 is send to process. That leads to a process abort. You can try to extend the time by changing the sleep command or by changing the number counter. I get some obscure errors if a process was terminated with siglevel 9. No I don't think it has something to do with the script. Sounds like problem with data access from KODI. Suddenly is a kind of magic, too. You wrote you use a pendrive, which can lead to problem 2 - writing cache for KODI. KODI responds sometimes slow on pendrives esp. with ntfs format Unrelated to script. All in all I think you might get some problems with the powering and the pendrive. To be sure I would extent the sleep timer from 0.1 to 0.25 be aware that a not closing process needs now 30x0.25s time ~ 8s to be forced closed now. Maybe you can give feedback to this later ;) @Efriim retropie-setup dialogs can't be closed. As long as the call was initiated by runcommand shell script then every script or binary can be closed. If the runcommand call is missing then there is no pathway for the close switch.

Found in an old post. Solution for others, Settings > Player > Videos > Playback > Adjust display refresh rate > On start / stop

@Halvhjearne said in retropie on ubuntu 18.10 is adding unnecessary/broken apt sources: there is a package available upstream for both cosmic and bionic, would it be possible to maybe fix the script to not add the broken repo for cosmic? The repo is mainained by the FS-UAE author and it's the recommended way to install it (https://fs-uae.net/download#ubuntu). If anything changes regarding that, we can also update the script. While for 18.x the latest package is upstreamed (Ubuntu), for older releases the PPA has the latest version. Let's see what happens when 19.04 breaks loose.

Bump. Ran into this minor problem as well