Exiting Kodi to EmulationStation gives black screen

BuZz

aah you are launching Kodi from ES - that fix is when launching Kodi before ES. I'll give another.

BuZz

add sleep 1; fbset -depth 8; fbset -depth 32 to the end of /usr/bin/kodi before the exit or you could try Kodi 17 rc1 which I believe has the wrapper script sorted now

https://retropie.org.uk/forum/topic/6308/testing-kodi-17-release-candidate-1-available-for-retropie

Rascas

@BuZz yes, it is included in the new kodi and I removed the tvservice since I saw it is now included in runcommand.

@devotee take a look at Kodi 17 RC1, it is very close to final, it might be the last testing version also, it seems to be pretty stable already ;)

columboscoat

@Rascas Is Kodi 17 RC 1 stable enough? It seems like Krypton is taking forever for a stable release. Much more so than Jarvis (I appreciate there are fundamental changes in 17, but...) I love Kodi, perhaps the whole thing is toxic now...

Rascas

@columboscoat I think yes. Like I said ( check the release annoucement also) final stable version is very close. I am already using it in all my devices ;) ( I have to because de database version for mysql syncronization)

columboscoat

Hmm, I'm genuinely asking. I wamt to upgrade. Will it fark my whole shit up? Been ruuning 2 Pi's stable for a while. Lessons have been learned...

Rascas

@columboscoat Read the post about it here. I recommend to make a backup always in this cases.

columboscoat

Well, you should always back up. I'm asking for my errrr, really lazy friend.... Kodi is a breeze to set up. I was just asking if there are any obvious bugs in RC1. I stopped following progress on 17 cos it looked like an actual release was never gonna happen...

BuZz

@Rascas said in Exiting Kodi to EmulationStation gives black screen:

@BuZz yes, it is included in the new kodi and I removed the tvservice since I saw it is now included in runcommand.

just wanted to confirm this - you don't reset mode on exit anymore or ? I had assumed you would use the code we discussed before for restoring the mode/framebuffer (if Kodi uses a different mode from the boot mode).

tvservice is only used in runcommand if the screenmode is changed with runcommand - and when launching Kodi before ES runcommand is not used.

Rascas

@BuZz I added the fbset save and restore depth, and removed the chvt lines, since in your tests and mine, it seems that chvt isn't needed anymore with fbset. And removed the sudo tvservice -p >/dev/null 2>&1because of runcommand but I didn't remembered that RetroPie has now an option to boot directly to Kodi, and on exit to open ES.
I can put it back again on kodi launch script, but it would be nice if this could be implemented in the Kodi -> ES launch (I didn't saw how you do that yet) instead, because now the Kodi launch script doesn't depend on sudo on RetroPie and Raspbian.

BuZz

@Rascas You don't need sudo to run tvservice. But rather than tvervice -p you could use the code I posted in the other thread, which correctly saves/restores the screenmode (and works on composite).

Rascas

@BuZz Oh nice! Another thing I forgot :P
Is it ok ?
https://github.com/nsenica/xbmc/commit/38f4856082fbba21128941144edff844c916fe09

Will be on the next Kodi build.

BuZz

@Rascas from a quick look it looks good - thanks! :)