Kodi Community Forum

yes, black screen prob is history. thanks!

Just updated and everything is working flawlessly for me. Absolutely LOVE the theme! Very nice!

(2016-03-04, 21:20)_Spook_ Wrote: [ -> ]

(2016-03-04, 20:23)fritsch Wrote: [ -> ]Uploading new build ... this service.xbmc.versioncheck seems very stubborn :-)

All good. No more black screen. Thanks Will do some soundchecks now to see if passthrough audio works on my miniDP1.2->HDMI 2.0 adapter again

EDIT: Still no go on passthrough audio when using the adapter. No biggie. The new skin takes some getting used to

I still have no idea which adapter you use, but hey: if that thingy breaks passthrough - throw it :-)

(2016-03-04, 16:14)n2vwz Wrote: [ -> ]I loaded the latest Milhouse KODI 17 build (#0226, 26-Feb-2016) ... I did notice, however that the OpenELEC settings menu is missing from the SYSTEM top level menu. Is this a permanent condition in consideration that this is test software?

The default skin is changing. Confluence is no more. It's been added to the Kodi repository, the version bumped (3.0.0) and your Kodi has automatically pulled down the new version of Confluence from the repository. The repository version doesn't include the OpenELEC branding.

With the next update the new Estuary skin will replace Confluence as the default shipping skin, although those with existing installations (such as yourself) will continue using the now repository-based Confluence until such time as you decide to manually switch to Estuary.

Anyone installing these test builds to a "clean" system will go straight into Estuary.

(2016-03-04, 23:04)fritsch Wrote: [ -> ]

(2016-03-04, 21:20)_Spook_ Wrote: [ -> ]

(2016-03-04, 20:23)fritsch Wrote: [ -> ]Uploading new build ... this service.xbmc.versioncheck seems very stubborn :-)

All good. No more black screen. Thanks Will do some soundchecks now to see if passthrough audio works on my miniDP1.2->HDMI 2.0 adapter again

EDIT: Still no go on passthrough audio when using the adapter. No biggie. The new skin takes some getting used to

I still have no idea which adapter you use, but hey: if that thingy breaks passthrough - throw it :-)

It's the Club3D CAC-1170, and it only breaks passthrough on Atmos/TrueHD and DTS-HD MA it seems. And it's no big deal. I just use the HDMI 1.4b on the NUC instead.

Yeah - has nothing to do with us ...

(2016-03-05, 00:17)fritsch Wrote: [ -> ]Yeah - has nothing to do with us ...

My thought exatly so not going to bother you with it Will talk to Club3D about a firmware update.

Hello ,
With the last build 22240, I have incomplete codecs info displayed ...

It was removed by fernetmenta and will come back coded in a more optimized way.

@the-dreamer: What happens if you force the monitor to 1080p50? I also have such a HD ready display, but it nicely takes 1080p50 when one sends it.

/storage/.config/xorg.conf

Quote:Section "Device"
Identifier "Device0"
Driver "intel"
VendorName "INTEL Corporation"
Option "TripleBuffer" "false"
Option "TearFree" "false"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "HDMI1"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080@50p" "[email protected]" "1920x1080@23p" "1920x1080@24p" "1920x1080@60p"
EndSubSection
EndSection

Section "Monitor"
Identifier "HDMI1"
HorizSync 14.0 - 70.0
VertRefresh 24.0 - 62.0
Option "PreferredMode" "1920x1080@50p"
# Option "DPMS" "true"
Modeline "1920x1080@23p" 74.176 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
Modeline "1920x1080@24p" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
Modeline "1920x1080@50p" 148.500 1920 2448 2492 2640 1080 1084 1094 1125 +hsync +vsync
Modeline "[email protected]" 148.352 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "1920x1080@60p" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
EndSection

Section "Extensions"
# fixes tearing
Option "Composite" "Disable"
EndSection

Make sure you adjust the bold two things.

So I can just update and switch to estuary and everything will be normal? Right?

Or do I have to clean install with a .img. I don't mind either way, my library is baked up with nfos.

Just update ... if it does not work (as those are alpha test builds) you can still do a fresh installation - in any case make a backup.

(2016-02-28, 09:10)fritsch Wrote: [ -> ]Jep @wsnipex that's the case - I installed 16.04 on a braswell two days ago. Only difference, one needs to install the xserver-xorg-legacy packages and reconfigure that instead of x11-common. Also wsnipex vaapi ppa is not needed anymore. For kodi one could also install the kodi nightly ppa.

Tried a xenial server nightly.
Do i have to install the mentioned 'xserver-xorg-legacy' package additionally or instead of a/some package(s) you stated in your first post ?

(2016-03-06, 01:02)Markus_23 Wrote: [ -> ]

(2016-02-28, 09:10)fritsch Wrote: [ -> ]Jep @wsnipex that's the case - I installed 16.04 on a braswell two days ago. Only difference, one needs to install the xserver-xorg-legacy packages and reconfigure that instead of x11-common. Also wsnipex vaapi ppa is not needed anymore. For kodi one could also install the kodi nightly ppa.

Tried a xenial server nightly.
Do i have to install the mentioned 'xserver-xorg-legacy' package additionally or instead of a/some package(s) you stated in your first post ?

It depends on the others. So just add it.

I just went from OpenELEC-Generic.x86_64-8.0-Milhouse-20160305021244-#0304-g0e31f7f to OpenELEC-Generic.x86_64-7.0-devel-20160305113516-r22243-gebb3cbd as with the Milhouse build I got the blank screen and mouse icon after carrying out a full reset in the OpenELEC menu.

I now seem to be missing the OpenELEC menu from your latest build fritsch (Apologies if this is a known problem, I have been away!)?