When you go to change that setting (shutdown function), the tooltip at the bottom states 'Define what action XBMC should do when it has been idle for a long period of time.'
At least for the Aeon Nox 5 skin.
I have that set to suspend anyways.
(2014-07-15, 03:47)Walrus Wrote: [ -> ]When you go to change that setting (shutdown function), the tooltip at the bottom states 'Define what action XBMC should do when it has been idle for a long period of time.'
At least for the Aeon Nox 5 skin.
I have that set to suspend anyways.
yeah, that's a bit of a misnomer. It literally means 'what should XBMC do when the Shutdown timer (setting directly above) expires,' but also affects the function performed when the powertoggle remote code is received.
Ok. It's the same behavior I was getting with my windows setup and the same dongle from the RRC-126 remote. Had to keep sending repetitive powertoggle commands and then it would finally wake. That HTPC I am using as my home server for now, so I have it set to 'exit' XBMC instead and leave the pc running. Power on actually sends a 'WIN+3' command to launch XBMC from the pinned program on the taskbar.
Right now I'm going to try sending 3 powertoggles in a row to turn it on. If that doesn't work, I'll order a receiver like one of the two you use. If that all fails, I'll just leave it running all the time.
(2014-07-15, 04:10)Walrus Wrote: [ -> ]Ok. It's the same behavior I was getting with my windows setup and the same dongle from the RRC-126 remote. Had to keep sending repetitive powertoggle commands and then it would finally wake. That HTPC I am using as my home server for now, so I have it set to 'exit' XBMC instead and leave the pc running. Power on actually sends a 'WIN+3' command to launch XBMC from the pinned program on the taskbar.
Right now I'm going to try sending 3 powertoggles in a row to turn it on. If that doesn't work, I'll order a receiver like one of the two you use. If that all fails, I'll just leave it running all the time.
there are other options to debug your remote issues before replacing the hardware. what IR receiver are you using? google show any other linux users with the same issue?
(2014-07-14, 23:22)Mark the Red Wrote: [ -> ] (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.
Makes a lot of sense, because when the issue occurs my Pioneer AVR is no longer listed under HDMI1 were it used to be. So the box remains on HDMI1 but somehow the handshake doesn't occur. It would be nice to just throw a reboot command in the autostart.sh file, but I have a feeling this isn't triggered after a resume.
While I'm at it, why no threads discussing video lockup? I know about this:
https://bugs.freedesktop.org/show_bug.cgi?id=78960
but it is really lacking in any info and quite discouraging to be honest. I know it will take someone some (presumably) hard work to fix and I'm not trying to rush anyone...it just seems like it would be nice to post an update on possible progress every once in a while. Is the issue linux wide for haswell or chromebox specific? Anyone know?
Does anyone know how to wake on lan OpenElec from Windows 8 PC locally? if it can be done via SSH or VNC then even better, TIA!
I have used Yatse app to WOL the Chromebox with standalone OpenElec but i want to be able to do it from my windows 8 PC too
(2014-07-15, 04:16)Matt Devo Wrote: [ -> ]there are other options to debug your remote issues before replacing the hardware. what IR receiver are you using? google show any other linux users with the same issue?
Dongle from Rosewill RRC-126 remote. Google shows some issues. I'll try some of the troubleshooting options, like changing the responsiveness in Harmony software. Hmm.. I need to shove the batteries in the actual Rosewill remote and see if it powers on reliably. If it does, it's a Harmony issue then.
This is the remote:
http://www.newegg.com/global/au/Product/...6880101002
Has anyone figured out, if possible yet, to dual boot openelec with ubuntu (or any OS with OE)?
(2014-07-15, 16:50)vudiff Wrote: [ -> ]Has anyone figured out, if possible yet, to dual boot openelec with ubuntu (or any OS with OE)?
of course you can - configure the Chromebox to run in standalone mode, then setup would be the same as on any other PC (which is beyond the scope of this script/thread)
Thanks for the quick response Matt. But everything I've tried, I am unable to boot anything after modifying the grub "40_custom" file after setting up as standalone & manually adding OE partitions. I am not a noob to linux but not an expert either. I'll keep trying! Also, I want to thank you for all your hard work on this script. Made everything easier
(2014-07-15, 17:06)vudiff Wrote: [ -> ]Thanks for the quick response Matt. But everything I've tried, I am unable to boot anything after modifying the grub "40_custom" file after setting up as standalone & manually adding OE partitions. I am not a noob to linux but not an expert either. I'll keep trying! Also, I want to thank you for all your hard work on this script. Made everything easier
I'm afraid I'm not familiar enough with grub to advise how to get that working. maybe try either the OpenELEC or Ubuntu forums?
Will do! Thanks again for the quick replies
(2014-07-15, 05:29)jsp1 Wrote: [ -> ]While I'm at it, why no threads discussing video lockup? I know about this: https://bugs.freedesktop.org/show_bug.cgi?id=78960
but it is really lacking in any info and quite discouraging to be honest. I know it will take someone some (presumably) hard work to fix and I'm not trying to rush anyone...it just seems like it would be nice to post an update on possible progress every once in a while. Is the issue linux wide for haswell or chromebox specific? Anyone know?
i'm curious what material people are playing when the lockup occurs. i have vaapi enabled and haven't once experienced a lockup. all my material is h264 streamed over smb. chromebox is oe standalone with just the standard 2gb ram.