(2016-12-23, 19:23)t2ffn Wrote: [ -> ]So I've followed the above instructions, installed the UEFI firmware, installed LibreELEC 7.90.010 which installed fine.
I have two issues now;
1. I can't get it to boot properly if the HDMI is plugged into my AVR. The TV shows no input on the HDMI source from the AVR. It boots fine if connected to a PC monitor though.
2. I've moved my advancedsettings.xml into Userdata but my library isn't populating. I've added the sources etc. and 'update library' does nothing.
3. Also won't play any videos from the NAS. The name shows up top right of the screen when you select something to play after finding it through the network, but video window doesn't open and video doesn't play.
I wonder if the alpha release has an issue.
1) what AVR? does unplugging/re-plugging help
2) what's the kodi.log file say? Assume you're using advancedsettings for a mysql backend?
3) see #2
I'll do a fresh install of 7.90.010 here later and see if I can reproduce any of these issues. This release is an alpha in name only,and because the LE team decided to stay "one step" behind Kodi. So, since Kodi is still in beta, LE remains an alpha. When Kodi goes RC, LE will move to beta.
1. An Onkyo HTX 22HDX (non-4k), then through to a Samsung 65KS9000 (4k). Kodi is set up to be 1080p. Yes, if I boot via the monitor then move the HDMI to the AVR I can see Kodi on the TV. If I boot with the HDMI in the AVR the TV shows no source input.
2. Paste of log below. Looks like it can't access the MySQL, but can't figure out why. The log file is while plugged into the PC Monitor.
http://pastebin.com/raw/hZbDviWA
OK issues 2 and 3 solved by altering the audio/video settings after moving the HDMI from the monitor to the AVR, and changing the wait for network from 5s to 10s.
I'll work on issue 1 and see if some other setting is affecting it on boot.
Thanks
(2016-12-23, 20:02)t2ffn Wrote: [ -> ]OK issues 2 and 3 solved by altering the audio/video settings after moving the HDMI from the monitor to the AVR, and changing the wait for network from 5s to 10s.
I'll work on issue 1 and see if some other setting is affecting it on boot.
Thanks
if your AVR is in pass thru mode for video, but can't pass 4K, then that's problematic since the TV is reporting (via its EDID) that the max/native res is 2160p which your AVR cannot pass thru
But Kodi is set to 1080p...
Ok after some settings updates and many a restart it now boots up while connected to the AVR. I think you're right in that it thinks it's 4k at first as the Libreelec logo is mosyly off screen on boot, only partly visible, but then it sorts itself out when kodi starts up.
Now to recheck all settings, and soon to try out TVH... the whole reason for the refresh. Thanks Matt, hope you have a great christmas
(2016-12-23, 20:16)t2ffn Wrote: [ -> ]But Kodi is set to 1080p...
right, but the absolute first thing that happens is that the UEFI display driver initializes the screen based on the reported EDID data. The Kodi setting doesn't take effect until way later on.
I'm not sure under what criteria Samsung classifies an input as PC other not, but I know it's been complained about at length over on the avsforums. If I knew I might be able to work around it but at this point I'd just be guessing
I think it's somewhat down to the refresh rate / maybe plus the resolution. If the refresh rate is set at certain values, such as 60hz, the input is seen as a PC input, but if you change it to 30hz the regular TV options come back. I'll need to do some further testing but it could be as simple as ensuring to stay away from what Samsung sees as a 'PC refresh rate'.
Should've bought a Sony!
(2016-12-24, 03:16)t2ffn Wrote: [ -> ]I think it's somewhat down to the refresh rate / maybe plus the resolution. If the refresh rate is set at certain values, such as 60hz, the input is seen as a PC input, but if you change it to 30hz the regular TV options come back. I'll need to do some further testing but it could be as simple as ensuring to stay away from what Samsung sees as a 'PC refresh rate'.
Should've bought a Sony!
potentially 60.0Hz vs 59.97Hz? there are various standards for timings, it could be as simple as that. Either way it seems like Samsung's firmware on these sets is pretty buggy and inflexible.
If you'd like, I can provide you with a custom firmware that is limited to 1080p and uses different timings to try and sort out the issue -- shoot me an email at mrchromebox at gmail
(2016-12-24, 03:22)Matt Devo Wrote: [ -> ] (2016-12-24, 03:16)t2ffn Wrote: [ -> ]I think it's somewhat down to the refresh rate / maybe plus the resolution. If the refresh rate is set at certain values, such as 60hz, the input is seen as a PC input, but if you change it to 30hz the regular TV options come back. I'll need to do some further testing but it could be as simple as ensuring to stay away from what Samsung sees as a 'PC refresh rate'.
Should've bought a Sony!
potentially 60.0Hz vs 59.97Hz? there are various standards for timings, it could be as simple as that. Either way it seems like Samsung's firmware on these sets is pretty buggy and inflexible.
If you'd like, I can provide you with a custom firmware that is limited to 1080p and uses different timings to try and sort out the issue -- shoot me an email at mrchromebox at gmail
Is there any way to put that 1080p limitation as an option in the main UEFI firmware? I installed the UEFI firmware today and noticed my cabling (in wall) doesn't handle 2160p well, even though the Chromebox and 4k TV handshake to 2160p. This has been my issue, which I workaround by connecting temporarily with a short HDMI cable to get up and running.
(2016-12-24, 06:34)giant25 Wrote: [ -> ]Is there any way to put that 1080p limitation as an option in the main UEFI firmware? I installed the UEFI firmware today and noticed my cabling (in wall) doesn't handle 2160p well, even though the Chromebox and 4k TV handshake to 2160p. This has been my issue, which I workaround by connecting temporarily with a short HDMI cable to get up and running.
not super easily unfortunately, but I'll look into it some more. The main problem is I don't have a 4K set to test, and I'm leery of pushing a change like that without proper testing
(2016-12-24, 18:12)Matt Devo Wrote: [ -> ] (2016-12-24, 06:34)giant25 Wrote: [ -> ]Is there any way to put that 1080p limitation as an option in the main UEFI firmware? I installed the UEFI firmware today and noticed my cabling (in wall) doesn't handle 2160p well, even though the Chromebox and 4k TV handshake to 2160p. This has been my issue, which I workaround by connecting temporarily with a short HDMI cable to get up and running.
not super easily unfortunately, but I'll look into it some more. The main problem is I don't have a 4K set to test, and I'm leery of pushing a change like that without proper testing
No worries, thanks for the reply. I've always used an xrandr command within an autostart.sh to force 1080p, but it hasn't worked well since moving from OE to LE, not sure why. I wonder if there's a way to delay the xrandr command a few seconds without holding up the rest of the boot (not sure if "sleep 5" or something like that would work, or hold up the boot process). Had any luck there?
(2016-12-24, 19:38)giant25 Wrote: [ -> ]No worries, thanks for the reply. I've always used an xrandr command within an autostart.sh to force 1080p, but it hasn't worked well since moving from OE to LE, not sure why. I wonder if there's a way to delay the xrandr command a few seconds without holding up the rest of the boot (not sure if "sleep 5" or something like that would work, or hold up the boot process). Had any luck there?
I've never had a reason to do so / haven't tested it. As I said before, I can easily build a firmware that has a fixed boot resolution of 1080p, and I can provide you an easy way to update to it, I just don't want to make that the default (yet)
(2016-12-24, 19:45)Matt Devo Wrote: [ -> ] (2016-12-24, 19:38)giant25 Wrote: [ -> ]No worries, thanks for the reply. I've always used an xrandr command within an autostart.sh to force 1080p, but it hasn't worked well since moving from OE to LE, not sure why. I wonder if there's a way to delay the xrandr command a few seconds without holding up the rest of the boot (not sure if "sleep 5" or something like that would work, or hold up the boot process). Had any luck there?
I've never had a reason to do so / haven't tested it. As I said before, I can easily build a firmware that has a fixed boot resolution of 1080p, and I can provide you an easy way to update to it, I just don't want to make that the default (yet)
Thanks Matt, sounds good. No rush, enjoy the holidays. I'm also game to test things out for you in general if you need a hand.