2016-10-22, 20:36
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
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