(2016-03-03, 06:39)Matt Devo Wrote: given that the only actual difference (affecting the x86_64 version) between .198 and anything after is the WiFi startup / network delay fix, your best bet is to stick with .198. I'm not going to be chasing issues on OE6 builds since Kodi 15 is now 2 versions back from where development is focused, and fritsch moved on long ago. If it's an issue on these Kodi 17 test builds still, then it's something we can investigate

(2016-03-03, 07:15)n2vwz Wrote: .198 is working well. I don't have any issues. The Intel drivers provide noticeable improvements in picture quality, but, going forward, please be aware that a programmable KODI startup delay is required for both wired as well as wireless connections. I struggled with missing NAS shares for almost a year before discovering the startup delay that fixed the problem.

Are there any Kodi 17 builds available for testing? The only thing that I found is a KODI 16 Beta: https://dl.dropboxusercontent.com/u/98309225/OpenELEC-Generic.x86_64-6.94.2.tar

(2016-03-03, 07:19)Matt Devo Wrote: I'm not understanding what you need a startup delay for, if not to wait for the network to come online. How are you mounting these NAS shares that they aren't available automatically once Kodi is started? The 'wait for network' delay setting isn't designed to wait a set amount of time without condition; if that's what you need (which I'm not understanding why you do) then there's likely a more appropriate way to implement that.

also, there are Kodi 17 builds by fritsch in the 2nd post of this thread, and also in Milhouse's testing thread (also stickied in this forum).

(2016-03-03, 07:47)n2vwz Wrote: The problem that I was having is that my NAS SMB shares were not present on KODI startup. By navigating on the main Confluence menu to Video/Files, I would click on a programmed File Menu item and I would get a pop-up message stating that the connection was not found. The SMB shares would usually appear on their own after several minutes of waiting, but not always. It was acting like KODI was trying to establish a SMB share connection before the OpenElec network connection was fully established. I found that by adding a 2 second KODI startup delay, the SMB share was available immediately without the several minutes of waiting.

My network connection is wired using a static IP address. I also have NFS networking available, but haven't played with it.

(2016-03-03, 07:52)Matt Devo Wrote: I'd just add a ~2s delay using an autostart script:

Code:

#!/bin/sh
sleep 2

(2016-03-03, 08:02)n2vwz Wrote: I will play with this. Does the script get wiped out when I do a firmware/software update?

(2016-03-03, 08:04)Matt Devo Wrote:

(2016-03-03, 08:02)n2vwz Wrote: I will play with this. Does the script get wiped out when I do a firmware/software update?

no, only if you do a fresh install (or hard reset) of OE, which would erase any/all userdata. firmware updates don't touch anything on disk.

(2016-03-03, 01:40)Roby77 Wrote: Try using Custom EDID guide: http://wiki.openelec.tv/index.php/Configuring_a_Custom_xorg.conf#tab=Intel

talking about it ...is there a command via ssh to check that edid is correctly loaded ? like xrandr --prop or verbos to check video output

(i'm sure that is loaded correctly cause dts-hd and true hd in audio settings are available even if amp is not switched on before htpc.....just curious)

(2016-03-03, 11:03)Devil-Strike Wrote: Will post log but must first enable deug somehow.