(2014-07-11, 01:54)Mark the Red Wrote: Just got my new IR receiver in. Now my wife and I are living the dream! A couple of remote commands are not intuitive to program, but it works fantastically! Thanks again Matt!

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.

Finally, I just would very much like to give Matt a very sincere and deserved thank you for all your help on this thread and for pioneering this HT solution. This $210 4GB XBMC box (+ IR receiver) exceeds my wildest expectations as to performance and value. It boots in like 4 seconds. Streams HD via WIFI effortlessly and makes my TV look capital "P" pimp with the Ace skin. You are a great man!

(2014-07-11, 05:09)jsp1 Wrote: If that is the case Matt, would a temporary custom compile of openelec with kernel 3.13 have a working suspend/resume? Or would such a thing even be possible without breaking many other things that now rely on the new kernel?

(2014-07-10, 21:15)Mark the Red Wrote:

(2014-07-10, 06:10)jsp1 Wrote: 1. I was experiencing a degree of black crush using the 'full rgb' xrandr command. (I failed to perceive this without patterns, with them it was quite clear)
2. I was not getting a properly calibrated image leaving everything as is (default).
3. I do get a perfectly calibrated image by using xrandr full rgd + limited output option from within xbmc.

If I check the limited range option after the xrandr command it defaults to the original washed out greyed image.

My TV is a Samsung PN59D8000. I have the color space calibrated via 10p white balance which may explain why my TV is somewhat abnormal in this matter. However, Samsung TV's are no small percent of the market share either...

(2014-07-11, 05:12)Matt Devo Wrote:

(2014-07-11, 05:09)jsp1 Wrote: If that is the case Matt, would a temporary custom compile of openelec with kernel 3.13 have a working suspend/resume? Or would such a thing even be possible without breaking many other things that now rely on the new kernel?

that's what I'm working on currently. OpenELEC 4.0.x started off with kernel 3.14, so not sure what dragons await trying to use an older kernel. I'm testing newer kernels first just in case it's already been fixed.

(2014-07-11, 18:12)YellowDog Wrote: I don't know if this is meaningful or not. On my desktop running Fedora 20 with kernel 3.15.4-200, I am able to wake the system up from sleep with a USB keyboard connected to a USB3 port.

(2014-07-11, 18:15)Matt Devo Wrote:

(2014-07-11, 18:12)YellowDog Wrote: I don't know if this is meaningful or not. On my desktop running Fedora 20 with kernel 3.15.4-200, I am able to wake the system up from sleep with a USB keyboard connected to a USB3 port.

sleep, or S3 suspend? Hold [ALT] then hit the power button on taskbar, then pause button. That will put it into suspend, and see if you can wake it up. I know the default Fedora kernel (3.11.x) is good, trying to figure out now where it broke so I can identify and revert the commit which is causing the issue

(2014-07-11, 19:07)YellowDog Wrote: Wakes from both 'Sleep' & 'Hibernate'. I'm running KDE, not too sure what back end command is being used, I'm just choosing those commands on the menu. For my system Hibernate works flawlessly, with Sleep the X server gets wonky, just a blank screen happens on USB2 & USB3 wake. But the system is definitely being waken up. I can ssh in after sleep and do a reboot to reset the X server issue.

(2014-07-11, 19:10)Matt Devo Wrote:

(2014-07-11, 19:07)YellowDog Wrote: Wakes from both 'Sleep' & 'Hibernate'. I'm running KDE, not too sure what back end command is being used, I'm just choosing those commands on the menu. For my system Hibernate works flawlessly, with Sleep the X server gets wonky, just a blank screen happens on USB2 & USB3 wake. But the system is definitely being waken up. I can ssh in after sleep and do a reboot to reset the X server issue.

edit: looks like it's an OpenELEC configuration issue. I'm compiling a custom build now which (hopefully) will resolve the issue

(2014-07-12, 02:34)Matt Devo Wrote:

(2014-07-11, 19:10)Matt Devo Wrote:

(2014-07-11, 19:07)YellowDog Wrote: Wakes from both 'Sleep' & 'Hibernate'. I'm running KDE, not too sure what back end command is being used, I'm just choosing those commands on the menu. For my system Hibernate works flawlessly, with Sleep the X server gets wonky, just a blank screen happens on USB2 & USB3 wake. But the system is definitely being waken up. I can ssh in after sleep and do a reboot to reset the X server issue.

edit: looks like it's an OpenELEC configuration issue. I'm compiling a custom build now which (hopefully) will resolve the issue

and fixed. update will go up later tonight. Will just require a manual OE update for anyone already set up.

(2014-07-12, 02:34)Matt Devo Wrote:

(2014-07-11, 19:10)Matt Devo Wrote:

(2014-07-11, 19:07)YellowDog Wrote: Wakes from both 'Sleep' & 'Hibernate'. I'm running KDE, not too sure what back end command is being used, I'm just choosing those commands on the menu. For my system Hibernate works flawlessly, with Sleep the X server gets wonky, just a blank screen happens on USB2 & USB3 wake. But the system is definitely being waken up. I can ssh in after sleep and do a reboot to reset the X server issue.

edit: looks like it's an OpenELEC configuration issue. I'm compiling a custom build now which (hopefully) will resolve the issue

and fixed. update will go up later tonight. Will just require a manual OE update for anyone already set up.

(2014-07-12, 06:04)jsp1 Wrote:

Matt Devo Wrote: and fixed. update will go up later tonight. Will just require a manual OE update for anyone already set up.

This getting committed to the official build?

(2014-07-12, 02:34)Matt Devo Wrote: and fixed. update will go up later tonight. Will just require a manual OE update for anyone already set up.

(2014-07-12, 06:32)Matt Devo Wrote: Yes. It requires the use of a custom OpenELEC build, since their default configuration is to disable any USB3 controllers prior to suspend. Until I can convince them to change their config, anyway. But the custom build will be part of the script, as well as available for anyone to manually update an existing setup

(2014-07-12, 15:26)YellowDog Wrote: Brilliant

(2014-07-12, 15:58)jsp1 Wrote: Awesome! Thank you once again.