Sorry, but I have no clue as I only use the hdmi sound output. If it doesn’t work with setting it via the script, I don’t know whats wrong. Somebody else had a similar problem, but I think there was no solution either.
Kodi can’t be running in background, like EmulationStation?
No, that’s one of the reasons people have so much trouble using emulators with it on the pi and one of the main reasons I did those scripts that shutdown Kodi when emulationstation is started and restart it after emulationstation quits.
If you want to do this on a per rom basis, you will always be in the home screen again after quitting an emulator.
I don’t know why but if kodi runs in the background, the input cannot be grabbed by an emulator and I could not get sound working as I wanted.
Ok, thank you for your answer.
I saw some people that do other path: With RetroPie as base system they install Kodi + some desktop, so they have all in one system (but, sometimes, exit from kodi produces a blackscreen that forces to the users a reboot, I see some posts speaking about this “problem” and playing with runlevels to fix it).
I will try your script.
I know of this and the thing with the runlevels solves the same problem but in my eyes is a less elegant way.
It has the exactly same disadvantages as kodi will still be killed and restarted. And I don’t need to change runlevels.
You are pretty save from blackscreens also as my backgroundscript detects the shutdown or crash of emulationstation and starts kodi again.
You should really try this solution before you judge if anything else is better.
After trying this, you can try the runlevel stuff or installing kodi on naked raspbian alongside retropie if you like, see what better suits your needs.
I don’t want to prevent people from experimenting. Please report if you find anything useful on your way, that makes this easier or more userfriendly.
The code in:
Remove unneeded repositories from sources.list
Is only: sudo cp /etc/apt/sources.bak /etc/apt/sources.list
You can remove all of this:
sudo grep -v “raspbian” /etc/apt/sources.list > temp
sudo mv temp /etc/apt/sources.list
dialog --backtitle “RetroPie-OSMC setup script” --title “Removing unneeded sources from sources.list” --pause “\nSources removed.\n” 9 60 2
Because you don’t use this “grep’d” version of sources.list, just the next line is “cp bk original”
I make a backup of the sources.list file and copy it back after the script finishes.
A Pi 1 user would get into trouble otherwise as it uses raspbian by default.
And yes, this is an artifact of an older version probably.
Will clean that up when I have a minute 
One question about the RetroPie script (offcourse, I know that is not your script, you created the upper script that produces an enviorement to execute the retropie script, but I think that you can know the answer): Do you know if the RetroPie script updates the installation to the lastest things of RetroPie? (like update from RetroPie 3.0 BETA 1 to BETA 2, with the last things, like EmulationStation entry for some options).
And what version install your script? 2.6? 3.0 BETA 2? Edit: You do a “git clone --progress git://github.com/petrockblog/RetroPie-Setup.git” so I supose that the last version from trunk will be feetch. i.e. 3.0
My script always gets the newest version from github. So if you rerun it, it will update to latest retropie-setup and binaries.
Hi. I followed each step given by the guide and the install process ran straight through. Now emulationstation starts right from inside kodi but my problem is that everytime i want to start a rom my pi displays this error message in the shell:
/opt/retropie/supplementary/runcommand/runcommand.sh: line 452: tvservice: command not found
After that the screen fades back to emulationstation. I tried reinstalling several times but i have still no solution to this problem.
Line 452 from runcommand.sh:
local has_mode=$(tvservice -m ${mode_id[0]} | grep -w “mode ${mode_id[1]}”)
Hmmm. That is rather strange as the tvservice command should be provided by osmc.
Anyone else has this problem?
I’ll do a fresh install on my pi and investigate.
just yesterday i installed your script, i had evrething working except the controls of my wireless 360 controller while gaming.
the menu of retropie worked but not the controls of the emulators (nes snes)
and i could not really use the sudo ./retroarch-joyconfig
the whole prozess didnt wait for my input and clased instanntly
(i hope for a hint of someone)
could someone controll kodi with his wireless 360 controller?
Did you ever try any more to get this working on the Vero?
I have no Vero. How should I try it?
“4nd” asked “guran”, not you mcobit 
If I run this on my Vero, will it just fail? Is there any chance it will kill my Vero and force me to reinstall?
Hi! I have been looking around cubox forums to find an alternative but haven’t had the time to try any of the findings out (retro arch, lakka etc). I ran the install script provided here but it did not work. It didn’t install retropie and it didn’t destroy my vero installation. I will keep you guys updated if I make any progress. /G
The RetroPie Project is very tightly tied to the Hardware of the Pi.
A faster solution would be to try to build emulationstation and retroarch separately for theVero.
Does anyone tried this script with RPi 1 (Model B)?
We have a discussion on github about it right now. If you want to try it, install ca-certificates first.