(2016-10-17, 01:10)treml96 Wrote: So I have another question... the LibreELEC version that I used (Generic x86_64, v7.90.007), contained a beta version of Kodi, which may or may not be causing me problems with other add ons. Is there a simple way to change the version of Kodi (or LibreELEC for that matter)?

Quote:Or is the only solution to create a bootable USB with the ISO on it, plug it in and open a terminal, run the ChromeOS device Firmware Utility script, restore stock firmware, do a factory reset, and then reinstall a new version of LibreELEC? I started to do this route but creating the bootable USB with the ISO image was getting slightly confusing for me so I figured I would check with you first.

(2016-10-17, 01:28)Matt Devo Wrote: LibreELEC and Kodi are intertwined, you update (or downgrade) them as a single unit. If the addons you want to use aren't fully compatible with Kodi v17 yet, you can downgrade to LibreELEC 7.0.2 (stable) which contains Kodi 16.1. Just create a new USB/SD installer like you did before, but for LE 7.0.2, which is based on Kodi 16.1 (stable).
.

(2016-10-17, 18:40)paolotca Wrote: I now see your comment above in regards using a USB/SD installer. Can you not downgrade via the manual update procedure?

I apologize in advance if the answer is obvious and that I am just being dense.

(2016-10-21, 19:55)t2ffn Wrote: I've recently bought a Samsung KS9000 and have the Chromebox running OE from this script, and when I change the source to the HDMI to view Kodi via the AVR, the TV see's it as a PC input. This can be over-ridden in the TV source settings, but this never happened with my previous Panasonic plasma. Have you heard of similar, or have any thoughts how to make it appear as a set top box input rather than PC? The colours and blacks look as they should, I have the colour setting in Kodi to send full colour not limited.

Thanks

(2016-10-22, 01:50)t2ffn Wrote: Thanks Matt, I'm running OpenElec as I set this box up way way back. Is it simple to move to LibreElec by dropping a file in the update folder?

Thanks

(2016-10-22, 20:36)t2ffn Wrote: Thanks, I managed to upgrade to LE but it was the Krypton build so I reverted back to OE and I couldn't find a LE for Jarvis 16.1.

It's confirmed now that the Chromebox, on boot, sends an unsupported (PC) resolution, and if it's booted while that HMDI isn't on screen it often results in a black screen and needs power cycling while the TV is set to view the Chromebox HMDI source. It did this on my last TV, I used to note that if I powered up the Chromebox (usually was on 24/7) before turning the TV on, I'd need to reboot it again to get anything on screen.

So, any idea how I can stop it sending unsupported / PC resolutions on boot, or how I can upgrade to LE 16.1 if this also fixes the issue on boot?

I've ran this set up for years but with this recent issue since buying a new TV I'm starting to look for a 'set top box' solution as it's very frustrating if I need to reboot for any reason I pretty much have to bring a PC monitor into the living room to get it running!

Thanks in advance

(2016-10-23, 00:39)Matt Devo Wrote:

(2016-10-22, 20:36)t2ffn Wrote: Thanks, I managed to upgrade to LE but it was the Krypton build so I reverted back to OE and I couldn't find a LE for Jarvis 16.1.

It's confirmed now that the Chromebox, on boot, sends an unsupported (PC) resolution, and if it's booted while that HMDI isn't on screen it often results in a black screen and needs power cycling while the TV is set to view the Chromebox HMDI source. It did this on my last TV, I used to note that if I powered up the Chromebox (usually was on 24/7) before turning the TV on, I'd need to reboot it again to get anything on screen.

So, any idea how I can stop it sending unsupported / PC resolutions on boot, or how I can upgrade to LE 16.1 if this also fixes the issue on boot?

I've ran this set up for years but with this recent issue since buying a new TV I'm starting to look for a 'set top box' solution as it's very frustrating if I need to reboot for any reason I pretty much have to bring a PC monitor into the living room to get it running!

Thanks in advance

in another thread, a user having a similar issue was able to fix it by using my UEFI firmware rather than the Legacy one installed by the Kodi EZ Setup Script. What you would need to do is boot a Linux USB (eg, Ubuntu or GalliumOS), run my Firmware Utility Script, update the firmware, and choose UEFI when prompted. After that, re-install LibreELEC fresh. You can create the install media using LE's USB/SD creator tool, or using the EZ Setup Script - just be sure to choose version 7.0.2 stable, not 7.90.007.

(2016-11-03, 21:44)Chilll Wrote: I am having the same issue with my KS8000, Yamaha RX-A550 & Asus Chromebox running both Legacy/UEFI & Intel-openelc 6 / Libreelec 7.02. I tried flashing the UEFI firmware after having used the legacy firmware for years & can confirm the TV still resets the input to PC. I also picked up a JU7100 from 2015 & did not have this issue, but had to upgrade with the KS8000 sale that has been going on recently. The KS8000 is only TV of about 10 that I have tested it with that has this problem.

I swapped the Chromebox with an odroid c2 & it did not reset the input, so it is an isolated issue with the Chromebox, KS8000 & A/V receiver. I love my Chromebox & hopefully can get this resolved, but I don't think it will & my only solution is to replace it with a different box. Its worth the time saved having to select the input & reset all devices to get picture formatted properly with Movie mode selected every time I want to watch TV. At least with more 4K HEVC coming down the pipes, the Chromebox was going to be on its way out in the near future but not so soon . It served me well for few years thanks again to Mr Chromebox!

(2016-11-04, 05:46)Matt Devo Wrote: can you provide more detail about what input signal the KS8000 is getting such that it determines it to be a "PC" input vs another type? If it's an issue with the color space, that should be able to be resolved by changing the driver mode via an xrandr command in an autostart.sh script. If you can, fire up an ssh session to your Chromebox, and run 'xrandr --props' and see what the Broadcast RGB setting is. The default is automatic; you can try setting it via ssh to Limited 16:235 via 'xrandr --output HDMI1 --set "Broadcast RGB" "Limited 16:235"' (alternately, try the "Video 16:235 pass-through" option)