Exiting Kodi into Emulationstation
-
Are you forcing a composite mode in
/boot/config.txt
?if you ssh in and run
tvservice -c "PAL 4:3"
does that help ? -
I am trying to force the SDTV using the following in the /boot/config.txt:
sdtv_mode=0 sdtv_aspect=1
The
tvservice -c "PAL 16:9"
command makes the screen flicker, but nothing else. I have tried the other combinations as well NTSC, 4:3. -
maybe it's to do with PAL/NTSC switching - can you make sure your kodi mode and the mode in the config are the same (both pal or both ntsc)
-
@BuZz Where would I check that? I haven't specifically set anything.
Curious, when Kodi "Quits", what commands are being run? I noticed somewhere that you could specify a resolution for Emulationstation. I am curious if maybe something is being passed then in a script or something, that isn't when it initially starts up or doesn't effect it when using HDMI.
-
Ok this might help. I am using the
tvservice -s
(Status) command check what its doing.When I initially boot into Emulationstation:
pi@TruckPi:~ $ tvservice -s state 0x40001 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced
When I go to Kodi from Ports>Kodi:
pi@TruckPi:~ $ tvservice -s state 0x40001 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced
When I quit Kodi to return to Emulationstation:
pi@TruckPi:~ $ tvservice -s state 0x40005 [DVI CEA (1) RGB lim 4:3], 640x480 @ 60.00Hz, progressive
So something must be telling it to use "[DVI CEA (1) RGB lim 4:3]" somewhere. Any idea where to look?
-
Anyone have any ideas where I might look for the command or script that Kodi runs to launch Emulationstation when it is Quit?
-
I think I have the answer.
The Kodi launch script calls
sudo tvservice -p >/dev/null 2>&1
to switch the resolution back to "the preferred" mod, which I think it is getting wrong in your case. This could be argued that it is a firmware bug as the composite should be the preferred mode in your case. If you edit/usr/bin/kodi
and remove this line (towards the end), it should solve it.Just to check also, you don't have an hdmi cable plugged in at the same time or ?
@Rascas Perhaps this could be worked around, by not calling
tvservice -p
if for example the current mode is a PAL/NTSC mode ? -
@cyberhomie instead of editing the file directly, you could copy it to /usr/local/bin/ and edit it there - which would take priority over the shipped script - you would need to manually keep it up to date as needed though until this is resolved in the Kodi launch script.
-
@BuZz I commented that line out and it works!
No, I don't have HDMI plugged in, nor using any forced HDMI argument in the config.txt.
-
@BuZz said in Exiting Kodi into Emulationstation:
@cyberhomie instead of editing the file directly, you could copy it to /usr/local/bin/ and edit it there - which would take priority over the shipped script - you would need to manually keep it up to date as needed though until this is resolved in the Kodi launch script.
@BuZz I tried initially doing a separate file, but didn't seem to have any effect. Maybe I needed to change it's permissions? Otherwise commenting the line out on the main file did work.
Thanks!
-
This is not my case... System appears to be "looped" <green led on the raspberry is showing activity>, but the screen in KODI where exit option is displayed is showed on my TV.
Please, any suggestion will be very useful. My system do not return to emulationstation when I run KODI. What to do?
Thank you very much !!!
-
@JordiMayor I'd recommend starting a new thread on the forum listing details on your setup in not rather than hijacking a solved thread from October.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.