2017-02-05, 09:35
(2017-02-04, 21:11)MasterYous Wrote: FYI.
I have the latest beta of LibreELEC, which now includes Kodi 17 final.
I then installed the latest SiLVO from the repo (6.0.3). Upon reboot, the slick animated intro movie plays, but then Kodi hangs/freezes. I traced the problem to two things, it seems, at least for me:
1) the settings !Skin.HasSetting(Disable.StartupIntro) does not seem to matter. I think SiLVO's default is Disable, but the animation plays anyway. Toggling back and forth and rebooting does not seem to matter.
2) the following settings in 16x9/Startup.xml:
Quote: <!-- Intro -->
<onload condition="!Skin.HasSetting(Disable.StartupIntro)">AlarmClock(Play Intro,PlayMedia(special://skin/extras/intro.mp4,1),00:01,silent)</onload>
<onload condition="Skin.HasSetting(Disable.StartupIntro)">ReplaceWindow($INFO[System.StartupWindow])</onload>
<onunload condition="!Skin.HasSetting(Disable.StartupIntro)">PlayerControl(Stop)</onunload>
<defaultcontrol condition="!Skin.HasSetting(Disable.StartupIntro)">10</defaultcontrol>
Below, I commented out the first line to get the intro to skip. At this point, the skin will load the main menu, albeit after a 10 second pause:
Quote:Not sure if a change in SiLVO tickled this, or a change in Kodi. Just thought people would want to know, in case my situation is not unique. This is a great skin and I'll keep using it regardless. Glad there was a workaround...
<!-- Intro -->
<!--
<onload condition="!Skin.HasSetting(Disable.StartupIntro)">AlarmClock(Play Intro,PlayMedia(special://skin/extras/intro.mp4,1),00:01,silent)</onload>
-->
<onload condition="Skin.HasSetting(Disable.StartupIntro)">ReplaceWindow($INFO[System.StartupWindow])</onload>
<onunload condition="!Skin.HasSetting(Disable.StartupIntro)">PlayerControl(Stop)</onunload>
<defaultcontrol condition="!Skin.HasSetting(Disable.StartupIntro)">10</defaultcontrol>
I had the same hang/freeze at the splash screen, I removed the guisettings.xml to boot the default screen but I haven't had time to dig into the logs yet. So it doesn't seem like an isolated incident