(2017-04-30, 06:20)eros28 Wrote: Hi Matt,

I hope you're having a good weekend. I have a dilemma and hope you can steer me in the right direction. I have a Asus chomebox with LibreElec (Krypton 17.1) installed and it's working great (dual boot if that matters).

I was playing around with an Amazon Fire TV remote and was able to connect it to my chromebox via bluetooth. The issue arises when i restart the box. The AFT remote doesn't pair or connect when LibreElec loads again. I have to manually unpair it and pair it again for it to function.

Any ideas? Would I have to get a separate bluetooth dongle for it to work properly? Something like this: https://www.amazon.com/Plugable-Bluetooth-Adapter-Raspberry-Compatible/dp/B009ZIILLI/ref=sr_1_3?s=electronics&ie=UTF8&qid=1493523875&sr=1-3&keywords=bluetooth+dongle

Cheers,

(2017-04-26, 05:04)Matt Devo Wrote:

(2017-04-26, 04:58)lucho528 Wrote: Hi, I been having some weird issues with my asus chromebox cn60, when I'm watching any kind of video even just browsing the interface it just hangs, I have to get up and power it down and back up again. Before I upgraded to Librelec with Kodi 17 everything was working flawlessly. I reverted back to Libreelec Kodi 16.1 everything seems fine. But I wanted to keep my system up to date (you know been one of the cool kids). I do have to mention that I have never upgraded the Chromebox firmware besides the first time I ran E-Z Setup script like 2 years ago. Do I need to update to a new firmware (maybe tthats the problem)?

Thanks
Luis

Luis,

sounds like an addon incompatibility, since a clean install of LE 8.0/Kodi 17.1 shouldn't exhibit any of those issues. To test that theory, you could create a USB installer for LE 8.0 and boot it in Live mode, and see if the symptoms persist.

while I don't think this is in any way firmware related, the newer/UEFI firmware is a lot better than the older Legacy boot firmware you're running. If you do want to update, you'll need to first backup your LE userdata (using the built-in backup function) to USB, update the firmware, reinstall LE from USB, then restore your userdata. This is necessary since the UEFI firmware can't boot an OS installed in legacy BIOS mode.

(2016-11-07, 19:20)Matt Devo Wrote:

(2016-11-07, 18:59)Chilll Wrote: It will re select "PC" as the input if u power cycle the display. Yes I've searched rtings & several of the big avs threads on my TV model & saw some users mentioned having the same problem, but no one every replied back with a solution. They don't mention what media player they were using, but I tested my odroid c2 & rpi2 which neither had this problem. I dont have any other players to test it with.

I tried changing the "PC" input name to Kodi, once I powered both Chromebox & TV down then back on. It renamed the input back to "PC" everytime

sounds like Samsung has some serious firmware bugs related to that feature unfortunately

Quote:Re: KS8000 - Please help me get out of PC mode
Is not a perfect fix but what I did that helped me was setting my nvidia control panel on the setting called "resolution" to output "ycbcr422" at "8bpc" and "Limited" range and that stopped it from auto switching. Full rgb gives me the same issue.

Your black levels will be crap after this so you will have to calibrate your settings a bit more but it works!

(2017-05-09, 16:35)bolmsted Wrote: I picked up a 65KS8000 recently and hooked up my chromebox and it seems I have the issue with the interface defaulting back to a PC and someone mentioned this:

Quote:Re: KS8000 - Please help me get out of PC mode
Is not a perfect fix but what I did that helped me was setting my nvidia control panel on the setting called "resolution" to output "ycbcr422" at "8bpc" and "Limited" range and that stopped it from auto switching. Full rgb gives me the same issue.

Your black levels will be crap after this so you will have to calibrate your settings a bit more but it works!

Is it possible to get the chromebox to these sort of settings?

(2017-05-12, 23:39)bolmsted Wrote: I'll check your settings tonight but what I meant by overscan is that you do a video calibration to set the boundaries of the screen at 50Hz. When I play back 24fps material it seems fine but 60Hz seems to have sides cut off like the on screen display which was calibrated at 50Hz. I know it doesn't make sense but that's the behaviour I notice. I'll check the other setting after things settle down here tonight

(2017-05-14, 01:30)waverz Wrote: Just to avoid having to go through all 758 pages, what's the best method of updating? I haven't used this box in over a year.

Sent from my SM-G900R4 (typie typie)