[Matt Devo]

Do you have that issue while in Confluence skin or while using other skin? I'm having it in Aeon MQ5 skin but not in Confluence, i also have a casual freeze/hang while browsing the menus or when i switch mode to watch TV and after a while of not being in use, i go back to it only to find out it's frozen and nothing respond so i have to force POWER OFF.
Again this is with AEON MQ5 skin, with Confluence i only had 1 freeze while browsing the menus and that's it with AEON MQ is more frecuent.

Confluence is BORING as hell, now the question is does this box has the guts to run AEON MQ5 with all the whistles? Will adding 2gb more of RAM will make it more fluent and fix some of the issues or not?

I'll disable HARDWARE ACCELERATION and report back, i wonder how are other skins behaving... need FEEDBACK

the hardware acceleration setting doesn't affect UI (skin) rendering, only video playback/decoding.

I may be wrong but the latest fernetmenta XBMC builds (may not be in OpenElec yet) may address this with a workaround : http://forum.xbmc.org/showthread.php?tid...pid1744261

I had some content that always froze prior to this and now plays fine if you disable "Prefer VAAPI rendering" (which retains VAAPI decoding, but uses software de-interlacing AND continues to use the SSE copying for progressive content too) It may not fix everything - but I've not had any hangs with VAAPI acceleration since?

if that's the case, I'll do a custom OE build with that branch.

Matt Devo - I may well be running two Chromeboxes on the same network, both with new core boot firmware, soon. How do I ensure they have different MAC addresses?

current version of my script will persist the MAC address of any newly-flashed box, and allow you to load the device-specific data (VPD) from a firmware backup (if you have it) for any that were originally flashed before I added this feature.

Something so easy was so difficult for me...

When I tried to switch to Developer Mode, by holding reset when power on, there was no signal through the HDMI cable. Nothing displayed on the TV.

If I boot it normally, I can see the screen to log in within 3 seconds. What's going on?

TV? HDMI cable?

your TV is not able to set the resolution needed for the recovery screen/dev boot screen (1024x768). Use a computer monitor to setup instead.

Yeah disabling of "Prefer VAAPI Rendering" is a workaround exactly for that issue. On older builds or on OpenELEC 4.0.x there is another option in Expert Settings of Acceleration: "Use SW Filter" which needs to be turned on.

The Prefer VAAPI Rendering is the inverted setting of "Use SW Filter". It will automatically fallback to VAAPI Rendering when you are decoding surfaces larges than 1920x1088 for peformance reasons.

on OE 4.0.6, I get a full lockup with the "Use SW filter" option selected, but only a ~3-5s hitch with it deselected. I'll try pulling from your repo and see if that works better.

Tried this on my DEV box and received this:

MediaRoom:~ # xrandr --output HDMI1 --set "Broadcast RGB" "Full"
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 139 (RANDR)
Minor opcode of failed request: 21 (RRSetCrtcConfig)
Serial number of failed request: 63
Current serial number in output stream: 63

perhaps your output isn't on HDMI1, but on HDMI0? there's nothing wrong with the syntax of the command