Kodi Community Forum

Yeah, it is no big deal. I think perhaps the box resumes faster than my AVR is capable of detecting or something. I'll check in with OE chat when I get some time.

Sorry if this has been posted somewhere in this thread. I'm on 2014-06-14 -- v2.10 with standalone OpenELEC. What are the steps to update to 2014-07-12 -- v2.14? Thank you.

If any of you are using the FLIRC to control your ChromeBox, make sure you set the "sleep detection" bit and program a wake key when setting it up otherwise absolutely any IR signal will wake up your box from sleep.

Jeff

(2014-07-14, 17:42)hdmkv Wrote: [ -> ]Sorry if this has been posted somewhere in this thread. I'm on 2014-06-14 -- v2.10 with standalone OpenELEC. What are the steps to update to 2014-07-12 -- v2.14? Thank you.

update which aspect - the coreboot firmware or OpenELEC? For the former, you need to just re-run the script, from a bootable ChromiumOS USB stick. For the latter, if you want the wake from sleep via IR remote feature, you should update to my custom OpenELEC build. Info for both is on the wiki, though I'll be adding a separate section for updating coreboot at some point

(2014-07-14, 17:44)trick420 Wrote: [ -> ]If any of you are using the FLIRC to control your ChromeBox, make sure you set the "sleep detection" bit and program a wake key when setting it up otherwise absolutely any IR signal will wake up your box from sleep.

Jeff

good note, added to the wiki

Coreboot firmware... so, to re-run the script, do I pop in the USB stick with my backup of ChromeOS (made during initial set-up)? Or, if ChromiumOS is necessary, I assume I'd need to download and have in on a USB stick as a boot stick? Just use this?

(2014-07-14, 18:28)hdmkv Wrote: [ -> ]Coreboot firmware... so, to re-run the script, do I pop in the USB stick with my backup of ChromeOS (made during initial set-up)? Or, if ChromiumOS is necessary, I assume I'd need to download and have in on a USB stick as a boot stick? Just use this?

You need to run ChromiumOS, ChromeOS won't run with my coreboot firmware, which is why I removed that feature from the script.

Use the link from either the OP or the wiki, not the one you posted, as those builds are well over 1 year old.

(2014-07-11, 01:54)Mark the Red Wrote: [ -> ]I read Yuri's post earlier, but has anyone figured out to have an IR command remote power this thing on from sleep / hibernate mode? It's really no big deal, just a curiosity.

Does the latest update fix this for you? I just bought a Celeron chromebox, and used the guide for a standalone openelec yesterday. Using a harmony remote and a RRC-126 dongle just like I have on my main windows setup, the remote SOMETIMES turns on from suspend. I'm thinking I need to play with the delays or something. I have the device as Media Center SE, I'll try changing to Media Center Extender.

On my windows setup I have it set up as Media Center SE for most commands, but also MCE Keyboard to send keypresses for stuff like C for context menu. I've tried setting up MCE Keyboard as another device in harmony for the chromebox, but it doesn't respond to any keyboard commands from the remote. Tried setting the remote keypress option on & off in XBMC. Not a big deal, just means I can't program exit button on harmony remote as ESC like I do on my windows XBMC system.

(2014-07-14, 18:44)Walrus Wrote: [ -> ]Does the latest update fix this for you? I just bought a Celeron chromebox, and used the guide for a standalone openelec yesterday. Using a harmony remote and a RRC-126 dongle just like I have on my main windows setup, the remote SOMETIMES turns on from suspend. I'm thinking I need to play with the delays or something. I have the device as Media Center SE, I'll try changing to Media Center Extender.

On my windows setup I have it set up as Media Center SE for most commands, but also MCE Keyboard to send keypresses for stuff like C for context menu. I've tried setting up MCE Keyboard as another device in harmony for the chromebox, but it doesn't respond to any keyboard commands from the remote. Tried setting the remote keypress option on & off in XBMC. Not a big deal, just means I can't program exit button on harmony remote as ESC like I do on my windows XBMC system.

it works 100% reliably here with my Harmony + MCE receiver. My Harmony is programmed as a Media Center Extender, with a 200ms Inter-key delay

if i update to the custom OpenElec build will i lose settings and data? i mean will i have to setup everything again?

(2014-07-14, 19:07)Veronica Wrote: [ -> ]if i update to the custom OpenElec build will i lose settings and data? i mean will i have to setup everything again?

no, OpenELEC updates do not touch user data at all (unless the update necessitates a database version upgrade)

(2014-07-14, 18:47)Matt Devo Wrote: [ -> ]it works 100% reliably here with my Harmony + MCE receiver. My Harmony is programmed as a Media Center Extender, with a 200ms Inter-key delay

Thanks for the response, I'll play with it some more and try the device as a Media Center Extender with the same delay. I had the same intermittent power on problem with my windows build, maybe it's because I have the primary device as Media Center SE. Which MCE receiver do you have, in case I can't get it to work reliably and maybe its the dongle I am using?

(2014-07-14, 20:21)Walrus Wrote: [ -> ]Thanks for the response, I'll play with it some more and try the device as a Media Center Extender with the same delay. I had the same intermittent power on problem with my windows build, maybe it's because I have the primary device as Media Center SE. Which MCE receiver do you have, in case I can't get it to work reliably and maybe its the dongle I am using?

the two MCE receivers currently listed in the wiki

(2014-07-14, 17:12)jsp1 Wrote: [ -> ]Yeah, it is no big deal. I think perhaps the box resumes faster than my AVR is capable of detecting or something. I'll check in with OE chat when I get some time.

I did some googling on the issue. Really haven't had a chance to implement the supposed fixes, but it appears it has something to do with HMDI CEC+ Anynet connections. Basically, when you "power" off your AVR, it may / may not allows a passthrough HDMI connection to a connected TV which your Chromebox tries to "adjust" to on the fly. So when you resume, it remembers the passthrough connection as the last audio driver and not the correct default AVR connection.

I have the same issue with my Chromebox, that when / if power it on without my AVR turned on first, I get no video because Chromebox thinks there are no active video outputs connected at the time it powered on. I fixed that by making the Harmony power this on last when I start the activity, but it is definitely similar problem to the audio resume issue.

Now I wish I could turn off the "smart adjust on the fly" features of the XBMC (Chromebox). In other words, force it to always output HDMI#1 1920 x1080p and the same deault DENON HDMI audio driver even if God himself tells it otherwise or powers it on. In other words, I would love for XBMC to have a "I'm not paying you to think" checkbox and always default to the same audio / video settings REGARDLESS of what is connected to it. But alas this is wish-thinking and coding this via ssh is beyond my ability.

(2014-07-14, 20:49)Matt Devo Wrote: [ -> ]the two MCE receivers currently listed in the wiki

Still flaky. Maybe need a different receiver.

I have it sending a 'powertoggle' command for powering on & powering off. How do I know this is telling the box to suspend and not power off? Or does it only ever suspend? Under 'power saving' settings I have default action as suspend, but the info when on the default action says it's the default action after inactivity, not the default shutdown action?

(2014-07-15, 03:04)Walrus Wrote: [ -> ]Still flaky. Maybe need a different receiver.

I have it sending a 'powertoggle' command for powering on & powering off. How do I know this is telling the box to suspend and not power off? Or does it only ever suspend? Under 'power saving' settings I have default action as suspend, but the info when on the default action says it's the default action after inactivity, not the default shutdown action?

Ensure your 'Settings Level' is Advanced or Expert.

Settings --> Power Saving --> Shutdown function: Suspend