Official Kodi Wiki - User contributions [en]

Add-on:Arctic: Zephyr

2015-04-16T19:27:16Z

Borromini: Confirmed custom home item support

{{Addon
|Name=Arctic: Zephyr
|provider-name=jurialmunkey
|ID=skin.arctic.zephyr
|latest-version=1.2.4
|extension point=xbmc.gui.skin
|provides=
|Summary=Clean, minimal, elegant, simple, light.
|Description=Arctic: Zephyr is the third iteration of the Arctic skin created by jurialmunkey. Arctic focuses on being simple, clean and minimalistic with a light spin.
|Platform=all
|Language=
|License=
|Forum=
|Website=
|Source=
|Email=
|broken=
|icon url=http://mirrors.kodi.tv/addons/helix/skin.arctic.zephyr/icon.png}}

{{Skin features
| custom home items = {{yes}}
}}

[[Category:Helix add-on repository]]

Archive:Chromebox

2014-07-27T17:11:36Z

Borromini:

{{Infobox information appliance
| name = Asus Chromebox
| image = [[File:Asus_chromebox.jpg|300px]]
| manufacturer = Asus
| releasedate = 2014-03-14 (US)
| os = Chrome OS
| cpu = Intel® Celeron 2955U (M004U) / Intel® Core i3-4010U (M075U)
| graphics = Intel® HD Graphics 4000 (M004U) / Intel® HD Graphics 4400 (M075U)
| storage = 16GB internal SSD
| memory = 2 GB (M004U) / 4GB (M075U), Dual Channel, DDR3 at 1600MHz
| connectivity = HDMI, Displayport, Bluetooth 4.0, USB 3.0, Wifi 802.11 a/b/g/n, 10/100/1000 Ethernet, 2 -in-1 Card Reader, Audio jack
| dimensions = 4.88 x 4.88 x 1.65 inch (WxDxH)
}}
[[File:Asus_chromebox_ports.jpg|right|300px|Asus Chromebox Rear Ports|thumb]]
[[File:Asus_chromebox_ports_2.jpg|right|300px|Asus Chromebox Side/Front Ports|thumb]]
{{mininav|[[Devices]]|[[x86 hardware]]}}
<section begin="intro" />The ASUS Chromebox is a small lightweight intel PC that runs Chrome OS and can be made to boot into other linux versions. It features HDMI, Displayport, USB 3 ports, gig ethernet, SD card slot, and internal wireless-n networking. This page is a collection of links, information, tips, and guides related to running XBMC on the ASUS Chromebox line of computers.

Nearly all of these steps will be the same on the HP Chromebox. The hardware is almost identical except for only having 1 dimm instead of the 2 the ASUS has.<section end="intro" />

== Device Preparation ==

=== Put in Developer Mode ===

Putting the ChromeBox in developer mode will allow you to access the underlying Linux operating system features necessary for installing XBMC.

'''WARNING''': This will erase all user data on the device.

With the device powered off:
# Insert a paperclip into the hole left of the SD card slot and press the recovery button
# Power on the device, then remove the paper clip
# When greeted with the recovery screen, press CTRL-D to enter developer mode
# Press the recovery button (with paperclip) to confirm.
 
After confirming, the device will reboot and wipe any existing user data - this will take ~5 minutes. Afterwards, the ChromeBox will be in developer mode (as opposed to standard/verified boot mode), and the developer boot screen will be shown at each boot.
 
 
The developer boot screen has some scary text about OS verification being off, with instructions to hit [SPACE] if you want to re-enable it. This will return the device from developer mode to standard/verified boot mode, so don't do that. The developer mode boot screen has a ~30s delay, followed by two beeps, before booting. You can skip the delay by pressing [CTRL-D] to immediately boot into ChromeOS.
 
 
[[File:Recoverybutton.png|300px]]
 
 

=== Disable Firmware Write Protect ===

Disabling the firmware write protect will allow us to shorten the developer boot screen timeout (from 30s to ~1s) in a dial boot configuration, and optionally boot directly to the legacy BIOS (and into Ubuntu or OpenELEC). This is also necessary for standalone setups so that the stock firmware can be updated.

With the device powered off and unplugged:

# Remove (4) rubber feet from bottom of unit
# Remove (4) screws under rubber feet
# Separate two halves of unit. Tip: partially insert the screw removed from the notched end, but do not re-thread it. Use it to help separate the two halves.
# Remove write-protect screw circled below:
#::[[File:Inside-chrome1.jpg|300px]]
# Reassemble in reverse order

The write-protect screw can be left out permanently.
 
 

=== Perform a Factory Reset ===

A factory reset is not needed on a Standalone setup, but must be performed prior to any dual-boot installation.

Google's recovery tool seems to be picky about what kind/size of USB/SD media you use. I've had the best luck with 4GB/8GB media, but YMMV.
Anecdotally, creating the recovery media from within ChromeOS seems to be the most reliable method.

# Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/answer/1080595?hl=en or open chrome://imageburner on the device
# With the device powered off, use a paperclip to press the Recovery button and power on the device
# Insert the recovery media (USB or SD) when prompted
 
Note that this will re-partition the internal hard drive and restore the original copy of ChromeOS, erasing anything else on the drive. The ChromeBox will still be left in developer mode, and if you changed the boot options they will still be set.
 
 
If you're having trouble creating the recovery media using Google's recovery tool above, you can manually download the recovery image and write it to a USB stick:
:*Download Recovery image: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_5500.130.0_panther_recovery_stable-channel_mp.bin.zip
:* Download Win32 Disk Imager: http://sourceforge.net/projects/win32diskimager/
:* Unzip the recovery image; the file should be ~1.5 GB
:* Rename the recovery image extension from .bin to .img
:* Write the image to your USB media using Win32 Disk Imager
 
 

== Installing XBMC ==

XBMC can be installed via OpenELEC or Ubuntu+XBMC, in either a standalone or dual boot configuration. This is accomplished via the ChromeBox E-Z Setup script, which must be run from either ChromeOS or ChromiumOS.

To run the ChromeBox E-Z Setup script, perform the following steps:

# Power on and boot to ChromeOS/ChromiumOS. Do not log in, but ensure a network connection is established.
# Hit CTRL-ALT-F2 to open command prompt
# Login with user chronos (no password required for ChromeOS; ChromiumOS uses 'password')
# Download and run the ChromeBox setup script with the commands:
#: <nowiki>curl -L -O http://goo.gl/3Tfu5W</nowiki>
#: <nowiki>sudo bash 3Tfu5W </nowiki>

Full instructions and explanation of the script's usage can be found at the following forum thread: http://forum.xbmc.org/showthread.php?tid=194362

=== Updating XBMC ===

==== OpenELEC ====

The Chromebox is a pretty run-of-the-mill x86_64 Intel system (albeit, like the NUC, with an ultra low power processor). The standard OpenELEC builds - labeled 'Generic x86_64' - work perfectly well, and it is recommended to use OpenELEC's auto-update feature (System --> OpenELEC --> System --> Automatic Updates: auto). If that doesn't work for some reason, you can manually update using the instructions on the [http://wiki.openelec.tv/index.php?title=Updating_OpenELEC OpenELEC wiki].
 
 

== Known issues + Fixes/Workarounds ==

Installation:
:* Some keyboards seem to have issues working on the ChromeOS developer boot screen (before the OS is booted), and therefore cannot be used to setup/install XBMC on a ChromeBox. The Logitech K400 is one of these, so use another keyboard to install if yours doesn't appear to be working.

Color Range Selection:
:* This topic is a bit of a minefield, but [http://forum.xbmc.org/showthread.php?tid=176718&pid=1756704#pid1756704 this post on the forums is a good read]. It's for a NUC, but it applies to the ChromeBox as well. On some displays, the display and Intel video driver are not able to automatically sync up (in terms of which color space is being used), leading to incorrect black/white levels. You can download/play the following video clip to test: [https://dl.dropboxusercontent.com/u/98309225/1-Grayscale%20Ramp%20.mp4 Grayscale Ramp test] (file courtesy of avsforum.com). The correct output will show the grayscale ramp having a smooth transition (rather than stair steps) from 16-235, with solid black/white past the dots at the ends. See: [https://dl.dropboxusercontent.com/u/98309225/grayscale_ramp_good.png correct grayscale ramp].
:*: Solution: add the following line to the autostart script and reboot the device:
:*::<nowiki>xrandr --output HDMI1 --set "Broadcast RGB" "Full"</nowiki>
:*: Use 'DP1' instead of 'HDMI1' if connected via the DisplayPort output. See [http://wiki.openelec.tv/index.php?title=Autostart.sh the OpenELEC Autostart wiki page] for more info.
:*: You may also need to select the XBMC option 'Used limited color range' under Settings-->System-->Video Output. Use the video clip and image above as a guide.

No Audio on Wakeup
:* Some displays/AVRs don't successfully handshake when resuming from suspend, leading to no audio output until the audio output device is changed or the device rebooted.
:*: Solution: add the following line to the autostart script and reboot the device:
:*::<nowiki>xrandr --output HDMI1 --set "audio" "on"</nowiki>
:*: Use 'DP1' instead of 'HDMI1' if connected via the DisplayPort output. See [http://wiki.openelec.tv/index.php?title=Autostart.sh the OpenELEC Autostart wiki page] for more info.

Video Playback:
:* An Intel Linux video driver bug ( https://bugs.freedesktop.org/show_bug.cgi?id=78960 ) causes intermittent freezes/pauses.
:*: Workaround: (OpenELEC) enable the 'Use SW filter for VAAPI' option Settings-->Video-->Acceleration.
:*: Workaround: (XBMC 13.2+?) disable the 'Prefer VAAPI Rendering' option Settings-->Video-->Acceleration.
:* Another Intel Linux video driver bug (which is much more rare -- https://bugs.freedesktop.org/show_bug.cgi?id=81447 ) causes intermittent freezes/pauses.
:*: Recommendation: use settings above, but if playback issues are encountered, disable hardware acceleration under Settings-->Video-->Acceleration. Be sure to enable multi-threaded software decoding as well.
:* With the stock firmware, some kernels have high idle CPU usage on one core with a single channel/single 2GB stick of RAM; 4GB (2x2GB, or any dual-channel configuration) has no issue. Standalone setups running coreboot firmware do not have this issue regardless of memory configuration.

Remote Controls:
:* Some MCE remote IR receivers do not currently work with USB 3.0 ports under Linux due to a bug in the mceusb kernel driver. OpenELEC (4.0+) already includes a fix for this. The version of Ubuntu installed by the ChromeBox setup script in a dual boot setup also includes this fix.

:: For standalone Ubuntu (or any other distro) installs, a custom kernel will need to be compiled with the fixed driver. The patch is available [http://pastebin.com/REqHTekE here], but the application of the patch and installation of the fixed driver is beyond the scope of this wiki. A user on ubuntuforums has made a precompiled fixed driver available with instructions here: http://ubuntuforums.org/showthread.php?t=2203116&p=13007838#post13007838

:: It appears that the fix for MCE remotes will be included in the 3.16 kernel, so once that is available, MCE remotes should work out of the box for everyone.

Power Management:
:* Suspend/resume is generally problematic with the stock firmware (dual boot setups - OpenELEC will reboot on resume), but seems to work reliably in standalone setups running the coreboot firmware. Resume via IR remote (USB) and wake-on-lan (eg, via YATSE) work perfectly well.

Misc:
:* Some USB3 external hard drives seem to have issues booting. Issue is under investigation.
 
 

== Recommended Accessories / Hardware Upgrades ==
 
RAM:
: The ChromeBox has two (2) 204-Pin SODIMM slots, which accept 1.35V DDR3-1600 (PC3-12800) modules. Known working modules include:
:* Crucial CT25664BF160B (2GB, 1.35v/1.5v)
:* Crucial CT2CP51264BF160B (8GB [4GB x2] 1.35v/1.5v)
:* Crucial CT2KIT102464BF160B (16GB [8GB x2] 1.35v/1.5v)
:* Hynix HMT351S6CFR8C-PB (2GB, OEM)
: 
: Crucial also has a list of 1.35v-only compatible modules here: http://www.crucial.com/usa/en/compatible-memory-for/ASUS/chromebox
 
SDD:
: The ChromeBox uses a single M.2 SATA III SSD (42mm); stock is a 16GB SanDisk unit. Compatible upgrades include:
:* MyDigitalSSD MDM242-SC2-128 (128GB)
:* MyDigitalSSD MDM242-SB-064 (64GB)
:* MyDigitalSSD MDM242-SB-032 (32GB)
 
Remote Controls:
: The ChromeBox does not have a built-in IR sensor, and must therefore use an external USB receiver. In general, any remote listed on the XBMC wiki as fully working under Linux should be fine. A Microsoft eHome compatible remote/receiver is one of the most compatible, subject to the limitations listed in the 'Known Issues' section above. Specific models tested as working include:
:* [http://flirc.tv/ Flirc]
:*: Flirc users need to 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.
:* HP IR receiver model 5188-1667 (MCE/eHome)
:* HP IR receiver model 5187-4593 (MCE/eHome)
:* Microsoft IR receiver model 1040 (MCE/eHome)
:* HP remote/receiver kit [http://www.amazon.com/dp/B00AYE6JDO/ OVU400102/71] (MCE/eHome, includes 5187-4593 receiver)
:* Microsoft XBOX 360 remote (with MCE/eHome receiver or Flirc)
:* Microsoft XBOX One remote (with MCE/eHome receiver or Flirc)
:* Logitech Harmony remotes (programmed as Microsoft Media Center Extender, with MCE/eHome receiver or Flirc)
 
 

== Firmware/BIOS Updating ==

The ChromeBox's firmware consists of two main parts: the firmware itself (coreboot), and the Legacy BIOS (SeaBIOS). Users running a dual-boot configuration only need be concerned with updating the Legacy BIOS portion. Users running a standalone setup should update the custom coreboot firmware only, as it already contains an updated Legacy BIOS, which is not able to be updated separately.
 
 
=== Updating the Legacy BIOS ===

Dual-boot users should simply boot to ChromeOS and re-download/re-run the setup script, choosing the '''Update Legacy BIOS''' option under the Dual Boot heading.
 
 
=== Updating Coreboot ===

Standalone users should also re-download/re-run the setup script, but instead choosing the '''coreboot firmware install/update''' option under the Standalone heading. Since standalone users can no longer run ChromeOS, the firmware update must be performed using ChromiumOS, the open-source version of ChromeOS. Follow the instructions in the section below to create the ChromiumOS USB stick, boot it, and then run the setup script as per above to update.
 
 
=== Restoring the Stock Firmware ===
If you have used the ChromeBox Setup Script's Standalone setup option, or otherwise manually updated the ChromeBox's firmware with a custom Coreboot build, it is necessary to restore the stock firmware before [[ASUS_Chromebox#Perform_a_Factory_Reset|performing a factory reset]] to re-load ChromeOS.

In order to do this, we will create a bootable USB stick with ChromiumOS (the open-source version of ChromeOS) and use that to re-flash the stock firmware, which you backed up before flashing the Coreboot firmware. If you didn't make a backup, we can use a copy extracted from Google's recovery image, but an actual backup is preferred.
 
 

# Create ChromiumOS USB Stick
#:* Download the latest AMD64OS daily build from http://arnoldthebat.co.uk/wordpress/chromium-os/. Be sure it's the AMD64OS version, and the image version (.img.7z) and not the virtual machine version (.vdi.7z). Example: Camd64OS-20140527010101.img.7z
#:* Follow the instructions at the link above to extract and copy the image onto a USB disk. You will need at least a 4GB drive, and the contents of it will be erased. I recommend a USB2 device as USB3 devices seem to be flaky on the ChromeBox. Do '''NOT''' use the same USB stick that you used for your firmware backup
# Get a ChromiumOS Shell Prompt
#:* Connect the ChromiumOS USB stick to the ChromeBox, power on, and select the USB stick from the boot menu. Boot into ChromiumOS
#:* Open a shell the same way as in ChromeOS: [CTRL]-[ALT]-[F2] and login as user 'chronos' with password 'password'
# Copy firmware backup file
#:* If you have your firmware backup on USB, connect it now, then run the following commands from the shell prompt
#:*:<nowiki>mkdir /tmp/usb</nowiki>
#:*:<nowiki>sudo mount /dev/sdc /tmp/usb (If this fails, use /dev/sdc1 instead of /dev/sdc)</nowiki>
#:*:<nowiki>cp /tmp/usb/stock-firmware.rom ./</nowiki>
#:*:<nowiki>sudo umount /tmp/usb</nowiki>
#:* If you don't have a firmware backup, then run the following command to download one extracted from the recovery image
#:*:<nowiki>curl -L -o stock-firmware.bin https://dl.dropboxusercontent.com/u/98309225/firmware-panther-factory-recovery.bin</nowiki>
# Restore stock firmware
#:* After completing the above, then run the following commands from the shell prompt
#:*:<nowiki>sudo flashrom -w stock-firmware.bin</nowiki>
#:*Assuming it is successful, then:
#:*:<nowiki>sudo poweroff</nowiki>

You can now remove the ChromiumOS USB drive (and firmware backup USB drive). Proceed to [[ASUS_Chromebox#Perform_a_Factory_Reset|Perform_a_Factory_Reset]] above to restore/reload ChromeOS.
 
 

== Old / Deprecated Content ==

The steps below are now performed automatically by the ChromeBox setup script, but may still be useful in troubleshooting or recovery.

=== Set Developer Boot Flags ===

Setting the following boot flags will allow you to boot either to a backup copy of ChromeOS on USB/SD (using CTRL-U) or to the legacy BIOS (using CTRL-L) and into Ubuntu or OpenELEC.

'''Important: These boot flags must be set before installing either Ubuntu or OpenELEC.'''
 
 
To set the developer mode boot flags, perform the following steps:

# Power on and boot to ChromeOS.
# Press CTRL-ALT-F2 to open a shell.
# Login as user chronos, no password is needed.
# Run the commands:
#: <nowiki>sudo crossystem dev_boot_usb=1</nowiki>
#: <nowiki>sudo crossystem dev_boot_legacy=1</nowiki>
 
 
=== Create a Backup Copy of ChromeOS (on USB/SD)===

If you plan on wiping ChromeOS to install OpenELEC (vs dual booting), it's a good idea to have a backup copy of ChromeOS on USB that you can boot to if necessary. These instructions assume you have already put the ChromeBox into developer mode and set the developer boot flags as per above.

'''IMPORTANT:''' As part of creating the USB backup copy, the stock legacy BIOS will be restored, so you will need to (re)flash the fixed legacy BIOS '''after''' performing this step.

To create a bootable USB copy of ChromeOS, perform the following steps:

# Power on and boot to ChromeOS.
#: Press CTRL-ALT-F2 to open a shell.
#: Login as user chronos, no password is needed.
#:
# Insert a USB stick or SD card (8GB minimum) and run the command:
#: <nowiki>sudo fdisk -l | grep 'Disk /dev/sd'</nowiki>
#:
#: This will list all the drives your ChromeBox sees. The main internal HDD is /dev/sda, any connected USB/SD devices will be /dev/sdb, /dev/sdc, etc. Identify the device corresponding to the USB/SD card you inserted (compare sizes).
#:
# Run the following command to copy/install ChromeOS to your USB/SD card:
#: <nowiki>sudo chromeos-install --skip_src_removable --skip_dst_removable --skip_vblock --dst /dev/sdb (or whatever your device is from above step)</nowiki>
#:
# When the process completes, your Chromebook will reboot. Now with the USB/SD card still inserted, Press CTRL-U to boot the USB/SD copy of ChromeOS. On first boot, it will want to repair itself and then reboot to the standard login screen.
#:
# Lets confirm we're booted off of the external device.
#: Press CTRL-ALT-F2 to open a shell.
#: Login as user chronos, no password is needed.
#: Run the command:
#:: <nowiki>rootdev -s -d </nowiki>
#:
We should see the same device as identified in step 2 above, instead of /dev/sda for the internal HDD.
Now we have a backup ChromeOS install that we can boot into at will using CTRL-U on the dev boot screen
 
 

=== Update the Legacy BIOS ===

It is necessary to update the legacy BIOS to enable booting from USB/SD media, or if replacing ChromeOS with Ubuntu/OpenELEC, as the stock legacy BIOS is completely broken. If you are dual booting and using either the ChrUbuntu or ChrOpenELEC scripts to install, then this step is performed by those scripts and does not need to be done manually.
 
 
To update the legacy BIOS:
 

# Power on and boot to ChromeOS
# Hit CTRL-ALT-F2 to open a shell
# Login with user chronos (no password required)
# Download the updated legacy BIOS with the command:
#: <nowiki>curl -L -O http://johnlewis.ie/asus-chromebox-SeaBIOS-new.bin</nowiki>
# Flash the new bios with the command:
#: <nowiki>sudo flashrom -w -i RW_LEGACY:asus-chromebox-SeaBIOS-new.bin</nowiki>
 
This updated legacy BIOS has a ~5s wait on the 'Press ECS to show boot menu' screen. If you would prefer a shorter wait (~1.5s), use the following file/commands instead of those listed in steps 4/5 above:
: <nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/cbox-seabios-nowait.bin</nowiki>
: <nowiki>sudo flashrom -w -i RW_LEGACY:cbox-seabios-nowait.bin</nowiki>

The md5sum on cbox-seabios-nowait.bin is F1290EC96AC77026044E29E62B40F6CC
 
 
=== Set Firmware Boot Flags ===

With the firmware write-protect disabled, we can shorten the default developer-mode boot wait time (from 30s to ~1s) and set the ChromeBox to default to booting the legacy BIOS (and into Ubuntu or OpenELEC) instead of requiring CTRL-D or CTRL-L to be pressed each time.

'''Important: If you are going to wipe ChromeOS and have a dedicated OpenELEC/Ubuntu setup (and don't care to make a bootable USB copy of ChromeOS), then these boot flags must be set before installing either Ubuntu or OpenELEC. If you are going to be dual booting, then this step must be performed AFTER installation.'''
 
 
To set the firmware boot flags, perform the following steps:

* Power on and boot to ChromeOS
* Hit CTRL-ALT-F2 to get to command prompt
* Login with user chronos (no password required)
 
To shorten the boot wait time only, run the command:
: sudo set_gbb_flags.sh 0x1
: (This is the same as immediately pressing CTRL-D)
 
To shorten the boot wait time and set the default boot to the legacy BIOS:
: sudo set_gbb_flags.sh 0x489
: (This is the same as immediately pressing CTRL-L)
 
To set the default to legacy boot only (keeping the 30s timeout), run the command:
: sudo set_gbb_flags.sh 0x488
 
To reset these options to default, use:
: sudo set_gbb_flags.sh 0x0

 
 

== Links ==
* http://www.deconetworks.com/chromebox-full-linux-desktop/
* http://www.willispickering.com/content/upgrade-asus-chromebox-add-more-memory-and-ssd-and-ubuntu
* http://johnlewis.ie/asus-chromebox-owners-rejoice/
* http://forum.xbmc.org/showthread.php?tid=185329

[[Category:Hardware]]
[[Category:HTPC]]
[[Category:x86]]

Archive:Chromebox

2014-07-27T17:08:27Z

Borromini: Clarified that the Chromebox is a regular Intel x86_64 box and hence OpenELEC's generic 64 bit image is the best fit. Previous wording seemed a bit confusing (the generic x86_64 bit only being mentioned at the end of the paragraph).

{{Infobox information appliance
| name = Asus Chromebox
| image = [[File:Asus_chromebox.jpg|300px]]
| manufacturer = Asus
| releasedate = 2014-03-14 (US)
| os = Chrome OS
| cpu = Intel® Celeron 2955U (M004U) / Intel® Core i3-4010U (M075U)
| graphics = Intel® HD Graphics 4000 (M004U) / Intel® HD Graphics 4400 (M075U)
| storage = 16GB internal SSD
| memory = 2 GB (M004U) / 4GB (M075U), Dual Channel, DDR3 at 1600MHz
| connectivity = HDMI, Displayport, Bluetooth 4.0, USB 3.0, Wifi 802.11 a/b/g/n, 10/100/1000 Ethernet, 2 -in-1 Card Reader, Audio jack
| dimensions = 4.88 x 4.88 x 1.65 inch (WxDxH)
}}
[[File:Asus_chromebox_ports.jpg|right|300px|Asus Chromebox Rear Ports|thumb]]
[[File:Asus_chromebox_ports_2.jpg|right|300px|Asus Chromebox Side/Front Ports|thumb]]
{{mininav|[[Devices]]|[[x86 hardware]]}}
<section begin="intro" />The ASUS Chromebox is a small lightweight intel PC that runs Chrome OS and can be made to boot into other linux versions. It features HDMI, Displayport, USB 3 ports, gig ethernet, SD card slot, and internal wireless-n networking. This page is a collection of links, information, tips, and guides related to running XBMC on the ASUS Chromebox line of computers.

Nearly all of these steps will be the same on the HP Chromebox. The hardware is almost identical except for only having 1 dimm instead of the 2 the ASUS has.<section end="intro" />

== Device Preparation ==

=== Put in Developer Mode ===

Putting the ChromeBox in developer mode will allow you to access the underlying Linux operating system features necessary for installing XBMC.

'''WARNING''': This will erase all user data on the device.

With the device powered off:
# Insert a paperclip into the hole left of the SD card slot and press the recovery button
# Power on the device, then remove the paper clip
# When greeted with the recovery screen, press CTRL-D to enter developer mode
# Press the recovery button (with paperclip) to confirm.
 
After confirming, the device will reboot and wipe any existing user data - this will take ~5 minutes. Afterwards, the ChromeBox will be in developer mode (as opposed to standard/verified boot mode), and the developer boot screen will be shown at each boot.
 
 
The developer boot screen has some scary text about OS verification being off, with instructions to hit [SPACE] if you want to re-enable it. This will return the device from developer mode to standard/verified boot mode, so don't do that. The developer mode boot screen has a ~30s delay, followed by two beeps, before booting. You can skip the delay by pressing [CTRL-D] to immediately boot into ChromeOS.
 
 
[[File:Recoverybutton.png|300px]]
 
 

=== Disable Firmware Write Protect ===

Disabling the firmware write protect will allow us to shorten the developer boot screen timeout (from 30s to ~1s) in a dial boot configuration, and optionally boot directly to the legacy BIOS (and into Ubuntu or OpenELEC). This is also necessary for standalone setups so that the stock firmware can be updated.

With the device powered off and unplugged:

# Remove (4) rubber feet from bottom of unit
# Remove (4) screws under rubber feet
# Separate two halves of unit. Tip: partially insert the screw removed from the notched end, but do not re-thread it. Use it to help separate the two halves.
# Remove write-protect screw circled below:
#::[[File:Inside-chrome1.jpg|300px]]
# Reassemble in reverse order

The write-protect screw can be left out permanently.
 
 

=== Perform a Factory Reset ===

A factory reset is not needed on a Standalone setup, but must be performed prior to any dual-boot installation.

Google's recovery tool seems to be picky about what kind/size of USB/SD media you use. I've had the best luck with 4GB/8GB media, but YMMV.
Anecdotally, creating the recovery media from within ChromeOS seems to be the most reliable method.

# Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/answer/1080595?hl=en or open chrome://imageburner on the device
# With the device powered off, use a paperclip to press the Recovery button and power on the device
# Insert the recovery media (USB or SD) when prompted
 
Note that this will re-partition the internal hard drive and restore the original copy of ChromeOS, erasing anything else on the drive. The ChromeBox will still be left in developer mode, and if you changed the boot options they will still be set.
 
 
If you're having trouble creating the recovery media using Google's recovery tool above, you can manually download the recovery image and write it to a USB stick:
:*Download Recovery image: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_5500.130.0_panther_recovery_stable-channel_mp.bin.zip
:* Download Win32 Disk Imager: http://sourceforge.net/projects/win32diskimager/
:* Unzip the recovery image; the file should be ~1.5 GB
:* Rename the recovery image extension from .bin to .img
:* Write the image to your USB media using Win32 Disk Imager
 
 

== Installing XBMC ==

XBMC can be installed via OpenELEC or Ubuntu+XBMC, in either a standalone or dual boot configuration. This is accomplished via the ChromeBox E-Z Setup script, which must be run from either ChromeOS or ChromiumOS.

To run the ChromeBox E-Z Setup script, perform the following steps:

# Power on and boot to ChromeOS/ChromiumOS. Do not log in, but ensure a network connection is established.
# Hit CTRL-ALT-F2 to open command prompt
# Login with user chronos (no password required for ChromeOS; ChromiumOS uses 'password')
# Download and run the ChromeBox setup script with the commands:
#: <nowiki>curl -L -O http://goo.gl/3Tfu5W</nowiki>
#: <nowiki>sudo bash 3Tfu5W </nowiki>

Full instructions and explanation of the script's usage can be found at the following forum thread: http://forum.xbmc.org/showthread.php?tid=194362

=== Updating XBMC ===

==== OpenELEC ====

The Chromebox is a pretty run-of-the-mill x86_64 Intel system (albeit, like the NUC, with an ultra low power processor). The standard OpenELEC builds - labeled 'Generic x86_64' work perfectly well, and it is recommended to use OpenELEC's auto-update feature (System --> OpenELEC --> System --> Automatic Updates: auto). If that doesn't work for some reason, you can manually update using the instructions on the [http://wiki.openelec.tv/index.php?title=Updating_OpenELEC OpenELEC wiki].
 
 

== Known issues + Fixes/Workarounds ==

Installation:
:* Some keyboards seem to have issues working on the ChromeOS developer boot screen (before the OS is booted), and therefore cannot be used to setup/install XBMC on a ChromeBox. The Logitech K400 is one of these, so use another keyboard to install if yours doesn't appear to be working.

Color Range Selection:
:* This topic is a bit of a minefield, but [http://forum.xbmc.org/showthread.php?tid=176718&pid=1756704#pid1756704 this post on the forums is a good read]. It's for a NUC, but it applies to the ChromeBox as well. On some displays, the display and Intel video driver are not able to automatically sync up (in terms of which color space is being used), leading to incorrect black/white levels. You can download/play the following video clip to test: [https://dl.dropboxusercontent.com/u/98309225/1-Grayscale%20Ramp%20.mp4 Grayscale Ramp test] (file courtesy of avsforum.com). The correct output will show the grayscale ramp having a smooth transition (rather than stair steps) from 16-235, with solid black/white past the dots at the ends. See: [https://dl.dropboxusercontent.com/u/98309225/grayscale_ramp_good.png correct grayscale ramp].
:*: Solution: add the following line to the autostart script and reboot the device:
:*::<nowiki>xrandr --output HDMI1 --set "Broadcast RGB" "Full"</nowiki>
:*: Use 'DP1' instead of 'HDMI1' if connected via the DisplayPort output. See [http://wiki.openelec.tv/index.php?title=Autostart.sh the OpenELEC Autostart wiki page] for more info.
:*: You may also need to select the XBMC option 'Used limited color range' under Settings-->System-->Video Output. Use the video clip and image above as a guide.

No Audio on Wakeup
:* Some displays/AVRs don't successfully handshake when resuming from suspend, leading to no audio output until the audio output device is changed or the device rebooted.
:*: Solution: add the following line to the autostart script and reboot the device:
:*::<nowiki>xrandr --output HDMI1 --set "audio" "on"</nowiki>
:*: Use 'DP1' instead of 'HDMI1' if connected via the DisplayPort output. See [http://wiki.openelec.tv/index.php?title=Autostart.sh the OpenELEC Autostart wiki page] for more info.

Video Playback:
:* An Intel Linux video driver bug ( https://bugs.freedesktop.org/show_bug.cgi?id=78960 ) causes intermittent freezes/pauses.
:*: Workaround: (OpenELEC) enable the 'Use SW filter for VAAPI' option Settings-->Video-->Acceleration.
:*: Workaround: (XBMC 13.2+?) disable the 'Prefer VAAPI Rendering' option Settings-->Video-->Acceleration.
:* Another Intel Linux video driver bug (which is much more rare -- https://bugs.freedesktop.org/show_bug.cgi?id=81447 ) causes intermittent freezes/pauses.
:*: Recommendation: use settings above, but if playback issues are encountered, disable hardware acceleration under Settings-->Video-->Acceleration. Be sure to enable multi-threaded software decoding as well.
:* With the stock firmware, some kernels have high idle CPU usage on one core with a single channel/single 2GB stick of RAM; 4GB (2x2GB, or any dual-channel configuration) has no issue. Standalone setups running coreboot firmware do not have this issue regardless of memory configuration.

Remote Controls:
:* Some MCE remote IR receivers do not currently work with USB 3.0 ports under Linux due to a bug in the mceusb kernel driver. OpenELEC (4.0+) already includes a fix for this. The version of Ubuntu installed by the ChromeBox setup script in a dual boot setup also includes this fix.

:: For standalone Ubuntu (or any other distro) installs, a custom kernel will need to be compiled with the fixed driver. The patch is available [http://pastebin.com/REqHTekE here], but the application of the patch and installation of the fixed driver is beyond the scope of this wiki. A user on ubuntuforums has made a precompiled fixed driver available with instructions here: http://ubuntuforums.org/showthread.php?t=2203116&p=13007838#post13007838

:: It appears that the fix for MCE remotes will be included in the 3.16 kernel, so once that is available, MCE remotes should work out of the box for everyone.

Power Management:
:* Suspend/resume is generally problematic with the stock firmware (dual boot setups - OpenELEC will reboot on resume), but seems to work reliably in standalone setups running the coreboot firmware. Resume via IR remote (USB) and wake-on-lan (eg, via YATSE) work perfectly well.

Misc:
:* Some USB3 external hard drives seem to have issues booting. Issue is under investigation.
 
 

== Recommended Accessories / Hardware Upgrades ==
 
RAM:
: The ChromeBox has two (2) 204-Pin SODIMM slots, which accept 1.35V DDR3-1600 (PC3-12800) modules. Known working modules include:
:* Crucial CT25664BF160B (2GB, 1.35v/1.5v)
:* Crucial CT2CP51264BF160B (8GB [4GB x2] 1.35v/1.5v)
:* Crucial CT2KIT102464BF160B (16GB [8GB x2] 1.35v/1.5v)
:* Hynix HMT351S6CFR8C-PB (2GB, OEM)
: 
: Crucial also has a list of 1.35v-only compatible modules here: http://www.crucial.com/usa/en/compatible-memory-for/ASUS/chromebox
 
SDD:
: The ChromeBox uses a single M.2 SATA III SSD (42mm); stock is a 16GB SanDisk unit. Compatible upgrades include:
:* MyDigitalSSD MDM242-SC2-128 (128GB)
:* MyDigitalSSD MDM242-SB-064 (64GB)
:* MyDigitalSSD MDM242-SB-032 (32GB)
 
Remote Controls:
: The ChromeBox does not have a built-in IR sensor, and must therefore use an external USB receiver. In general, any remote listed on the XBMC wiki as fully working under Linux should be fine. A Microsoft eHome compatible remote/receiver is one of the most compatible, subject to the limitations listed in the 'Known Issues' section above. Specific models tested as working include:
:* [http://flirc.tv/ Flirc]
:*: Flirc users need to 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.
:* HP IR receiver model 5188-1667 (MCE/eHome)
:* HP IR receiver model 5187-4593 (MCE/eHome)
:* Microsoft IR receiver model 1040 (MCE/eHome)
:* HP remote/receiver kit [http://www.amazon.com/dp/B00AYE6JDO/ OVU400102/71] (MCE/eHome, includes 5187-4593 receiver)
:* Microsoft XBOX 360 remote (with MCE/eHome receiver or Flirc)
:* Microsoft XBOX One remote (with MCE/eHome receiver or Flirc)
:* Logitech Harmony remotes (programmed as Microsoft Media Center Extender, with MCE/eHome receiver or Flirc)
 
 

== Firmware/BIOS Updating ==

The ChromeBox's firmware consists of two main parts: the firmware itself (coreboot), and the Legacy BIOS (SeaBIOS). Users running a dual-boot configuration only need be concerned with updating the Legacy BIOS portion. Users running a standalone setup should update the custom coreboot firmware only, as it already contains an updated Legacy BIOS, which is not able to be updated separately.
 
 
=== Updating the Legacy BIOS ===

Dual-boot users should simply boot to ChromeOS and re-download/re-run the setup script, choosing the '''Update Legacy BIOS''' option under the Dual Boot heading.
 
 
=== Updating Coreboot ===

Standalone users should also re-download/re-run the setup script, but instead choosing the '''coreboot firmware install/update''' option under the Standalone heading. Since standalone users can no longer run ChromeOS, the firmware update must be performed using ChromiumOS, the open-source version of ChromeOS. Follow the instructions in the section below to create the ChromiumOS USB stick, boot it, and then run the setup script as per above to update.
 
 
=== Restoring the Stock Firmware ===
If you have used the ChromeBox Setup Script's Standalone setup option, or otherwise manually updated the ChromeBox's firmware with a custom Coreboot build, it is necessary to restore the stock firmware before [[ASUS_Chromebox#Perform_a_Factory_Reset|performing a factory reset]] to re-load ChromeOS.

In order to do this, we will create a bootable USB stick with ChromiumOS (the open-source version of ChromeOS) and use that to re-flash the stock firmware, which you backed up before flashing the Coreboot firmware. If you didn't make a backup, we can use a copy extracted from Google's recovery image, but an actual backup is preferred.
 
 

# Create ChromiumOS USB Stick
#:* Download the latest AMD64OS daily build from http://arnoldthebat.co.uk/wordpress/chromium-os/. Be sure it's the AMD64OS version, and the image version (.img.7z) and not the virtual machine version (.vdi.7z). Example: Camd64OS-20140527010101.img.7z
#:* Follow the instructions at the link above to extract and copy the image onto a USB disk. You will need at least a 4GB drive, and the contents of it will be erased. I recommend a USB2 device as USB3 devices seem to be flaky on the ChromeBox. Do '''NOT''' use the same USB stick that you used for your firmware backup
# Get a ChromiumOS Shell Prompt
#:* Connect the ChromiumOS USB stick to the ChromeBox, power on, and select the USB stick from the boot menu. Boot into ChromiumOS
#:* Open a shell the same way as in ChromeOS: [CTRL]-[ALT]-[F2] and login as user 'chronos' with password 'password'
# Copy firmware backup file
#:* If you have your firmware backup on USB, connect it now, then run the following commands from the shell prompt
#:*:<nowiki>mkdir /tmp/usb</nowiki>
#:*:<nowiki>sudo mount /dev/sdc /tmp/usb (If this fails, use /dev/sdc1 instead of /dev/sdc)</nowiki>
#:*:<nowiki>cp /tmp/usb/stock-firmware.rom ./</nowiki>
#:*:<nowiki>sudo umount /tmp/usb</nowiki>
#:* If you don't have a firmware backup, then run the following command to download one extracted from the recovery image
#:*:<nowiki>curl -L -o stock-firmware.bin https://dl.dropboxusercontent.com/u/98309225/firmware-panther-factory-recovery.bin</nowiki>
# Restore stock firmware
#:* After completing the above, then run the following commands from the shell prompt
#:*:<nowiki>sudo flashrom -w stock-firmware.bin</nowiki>
#:*Assuming it is successful, then:
#:*:<nowiki>sudo poweroff</nowiki>

You can now remove the ChromiumOS USB drive (and firmware backup USB drive). Proceed to [[ASUS_Chromebox#Perform_a_Factory_Reset|Perform_a_Factory_Reset]] above to restore/reload ChromeOS.
 
 

== Old / Deprecated Content ==

The steps below are now performed automatically by the ChromeBox setup script, but may still be useful in troubleshooting or recovery.

=== Set Developer Boot Flags ===

Setting the following boot flags will allow you to boot either to a backup copy of ChromeOS on USB/SD (using CTRL-U) or to the legacy BIOS (using CTRL-L) and into Ubuntu or OpenELEC.

'''Important: These boot flags must be set before installing either Ubuntu or OpenELEC.'''
 
 
To set the developer mode boot flags, perform the following steps:

# Power on and boot to ChromeOS.
# Press CTRL-ALT-F2 to open a shell.
# Login as user chronos, no password is needed.
# Run the commands:
#: <nowiki>sudo crossystem dev_boot_usb=1</nowiki>
#: <nowiki>sudo crossystem dev_boot_legacy=1</nowiki>
 
 
=== Create a Backup Copy of ChromeOS (on USB/SD)===

If you plan on wiping ChromeOS to install OpenELEC (vs dual booting), it's a good idea to have a backup copy of ChromeOS on USB that you can boot to if necessary. These instructions assume you have already put the ChromeBox into developer mode and set the developer boot flags as per above.

'''IMPORTANT:''' As part of creating the USB backup copy, the stock legacy BIOS will be restored, so you will need to (re)flash the fixed legacy BIOS '''after''' performing this step.

To create a bootable USB copy of ChromeOS, perform the following steps:

# Power on and boot to ChromeOS.
#: Press CTRL-ALT-F2 to open a shell.
#: Login as user chronos, no password is needed.
#:
# Insert a USB stick or SD card (8GB minimum) and run the command:
#: <nowiki>sudo fdisk -l | grep 'Disk /dev/sd'</nowiki>
#:
#: This will list all the drives your ChromeBox sees. The main internal HDD is /dev/sda, any connected USB/SD devices will be /dev/sdb, /dev/sdc, etc. Identify the device corresponding to the USB/SD card you inserted (compare sizes).
#:
# Run the following command to copy/install ChromeOS to your USB/SD card:
#: <nowiki>sudo chromeos-install --skip_src_removable --skip_dst_removable --skip_vblock --dst /dev/sdb (or whatever your device is from above step)</nowiki>
#:
# When the process completes, your Chromebook will reboot. Now with the USB/SD card still inserted, Press CTRL-U to boot the USB/SD copy of ChromeOS. On first boot, it will want to repair itself and then reboot to the standard login screen.
#:
# Lets confirm we're booted off of the external device.
#: Press CTRL-ALT-F2 to open a shell.
#: Login as user chronos, no password is needed.
#: Run the command:
#:: <nowiki>rootdev -s -d </nowiki>
#:
We should see the same device as identified in step 2 above, instead of /dev/sda for the internal HDD.
Now we have a backup ChromeOS install that we can boot into at will using CTRL-U on the dev boot screen
 
 

=== Update the Legacy BIOS ===

It is necessary to update the legacy BIOS to enable booting from USB/SD media, or if replacing ChromeOS with Ubuntu/OpenELEC, as the stock legacy BIOS is completely broken. If you are dual booting and using either the ChrUbuntu or ChrOpenELEC scripts to install, then this step is performed by those scripts and does not need to be done manually.
 
 
To update the legacy BIOS:
 

# Power on and boot to ChromeOS
# Hit CTRL-ALT-F2 to open a shell
# Login with user chronos (no password required)
# Download the updated legacy BIOS with the command:
#: <nowiki>curl -L -O http://johnlewis.ie/asus-chromebox-SeaBIOS-new.bin</nowiki>
# Flash the new bios with the command:
#: <nowiki>sudo flashrom -w -i RW_LEGACY:asus-chromebox-SeaBIOS-new.bin</nowiki>
 
This updated legacy BIOS has a ~5s wait on the 'Press ECS to show boot menu' screen. If you would prefer a shorter wait (~1.5s), use the following file/commands instead of those listed in steps 4/5 above:
: <nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/cbox-seabios-nowait.bin</nowiki>
: <nowiki>sudo flashrom -w -i RW_LEGACY:cbox-seabios-nowait.bin</nowiki>

The md5sum on cbox-seabios-nowait.bin is F1290EC96AC77026044E29E62B40F6CC
 
 
=== Set Firmware Boot Flags ===

With the firmware write-protect disabled, we can shorten the default developer-mode boot wait time (from 30s to ~1s) and set the ChromeBox to default to booting the legacy BIOS (and into Ubuntu or OpenELEC) instead of requiring CTRL-D or CTRL-L to be pressed each time.

'''Important: If you are going to wipe ChromeOS and have a dedicated OpenELEC/Ubuntu setup (and don't care to make a bootable USB copy of ChromeOS), then these boot flags must be set before installing either Ubuntu or OpenELEC. If you are going to be dual booting, then this step must be performed AFTER installation.'''
 
 
To set the firmware boot flags, perform the following steps:

* Power on and boot to ChromeOS
* Hit CTRL-ALT-F2 to get to command prompt
* Login with user chronos (no password required)
 
To shorten the boot wait time only, run the command:
: sudo set_gbb_flags.sh 0x1
: (This is the same as immediately pressing CTRL-D)
 
To shorten the boot wait time and set the default boot to the legacy BIOS:
: sudo set_gbb_flags.sh 0x489
: (This is the same as immediately pressing CTRL-L)
 
To set the default to legacy boot only (keeping the 30s timeout), run the command:
: sudo set_gbb_flags.sh 0x488
 
To reset these options to default, use:
: sudo set_gbb_flags.sh 0x0

 
 

== Links ==
* http://www.deconetworks.com/chromebox-full-linux-desktop/
* http://www.willispickering.com/content/upgrade-asus-chromebox-add-more-memory-and-ssd-and-ubuntu
* http://johnlewis.ie/asus-chromebox-owners-rejoice/
* http://forum.xbmc.org/showthread.php?tid=185329

[[Category:Hardware]]
[[Category:HTPC]]
[[Category:x86]]

Smart playlists

2014-06-07T20:10:11Z

Borromini: /* Fields */ Set possibility to use the "dateadded" flag with movies to "yes".

{{mininav|[[Playlists]] }}
<section begin="intro"/>XBMC supports '''smart playlists''' for all types of media (excluding pictures), which essentially use a set of rules to limit the results from the [[XBMC databases|databases]]. This means that to be able to create a smart playlist in the GUI, music/video ''must'' first be added to the libraries using a [[Scrapers|scraper]] [[Add-ons|addon]] or by creating [[NFO files]]. Smart playlist can be created either by using the built-in GUI smart playlist editor accessible from the [[Playlists]] section, or by creating an [[w:XML|XML]] file with the extension XSP ('''X'''BMC '''S'''mart '''P'''laylist).<section end="intro"/>

== Creating a smart playlist in the GUI ==
=== Smart playlist for music ===
{{highlight|Music -> Playlists -> New smart playlist|bordered=yes}}

<gallery widths=600px heights=340px>
Image:Musicxsp1.png|{{big|'''Step 1:'''}} Select "Music" on main menu.
Image:Musicxsp2.png|{{big|'''Step 2:'''}} Select "Playlists" from the options.
Image:Musicxsp3.png|{{big|'''Step 3:'''}} Select "New smart playlist" from the options.
Image:Musicxsp4.png|{{big|'''Step 4:'''}} Fill in with the desired options and when done press OK.
</gallery>

=== Smart playlist for video ===
{{highlight|Video -> Playlists -> New smart playlist|bordered=yes}}

<gallery widths=600px heights=340px>
Image:Videoxsp1.png|{{big|'''Step 1:'''}} Select "Videos" on main menu.
Image:Videoxsp2.png|{{big|'''Step 2:'''}} Select "Playlists" from the options.
Image:Videoxsp3.png|{{big|'''Step 3:'''}} Select "New smart playlist" from the options.
Image:Videoxsp4.png|{{big|'''Step 4:'''}} Fill in with the desired options and when done press OK.
</gallery>

== Format of a smart playlist file ==
Smart playlists are plain text files that can be parsed by an XML reader (e.g. [[w:Visual_studio|Visual Studio]] and [[w:Notepad%2B%2B|Notepad++]]). Any text editor can be used to create them. They should be saved with the extension XSP and placed in your [[userdata]] directory, as there is only limited support for smart playlists saved outside of the userdata folder.

The format is as follows:
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<smartplaylist type="songs">
<name>All U2 from after 1990</name>
<match>all</match>
<rule field="artist" operator="is">
<value>U2</value>
</rule>
<rule field="year" operator="greaterthan">
<value>1990</value>
</rule>
<limit>50</limit>
<order direction="descending">playcount</order>
</smartplaylist>
</syntaxhighlight>

=== Types ===
Smart playlists can be of one of the following types:
* songs (default)
* albums
* movies
* tvshows
* episodes
* musicvideos
* mixed (audio and music videos)

<syntaxhighlight lang="xml" enclose="div">
<smartplaylist type="songs">
</syntaxhighlight>

=== Name and Match ===
Basically there are two header tags, <code><name></code> and <code><match></code> and then a set of <code><rule></code> tags that define the rules to use, along with an <code><order></code> tag to allow sorting and a <code><limit></code> tag to limit the returned results.
{{Note|that the tags and attributes are all case-sensitive.}}
The <code><name></code> tag is the name of the playlist and the <code><match></code> tag indicates how the <code><rule></code> tags should be matched. If <code><match>all</match></code> like in the above example, then only songs which satisfy all the <code><rule></code>'s will be included. If <code><match>one</match></code> is specified, then songs that satisfy any one (or more) of the <code><rule></code>'s will be included.

<syntaxhighlight lang="xml" enclose="div">
<name>All U2 from after 1990</name>
<match>all</match>
</syntaxhighlight>

=== Rules ===
The <code><rule></code> tags, of which there can be as many as you wish, have two attributes (<code>field</code> and <code>operator</code>) and a <code><value></code> tag.

<syntaxhighlight lang="xml" enclose="div">
<rule field="artist" operator="is">
<value>U2</value>
</rule>
</syntaxhighlight>

==== Fields ====
Depending on the type of the smart playlist different <code>field</code>s are available:
{| class="prettytable" style="margin-right: 0;"
!colspan="2"|<code>field</code>
!colspan="3"|music
!colspan="4"|video
!colspan="1"|type
|-
!style="padding-left: 5px; padding-right: 10px;"|Name
!style="padding-left: 10px; padding-right: 10px;"|Data type
!style="padding-left: 10px; padding-right: 10px;"|songs
!style="padding-left: 10px; padding-right: 10px;"|albums
!style="padding-left: 10px; padding-right: 10px;"|artists
!style="padding-left: 10px; padding-right: 10px;"|movies
!style="padding-left: 10px; padding-right: 10px;"|tvshows
!style="padding-left: 10px; padding-right: 10px;"|episodes
!style="padding-left: 10px; padding-right: 10px;"|musicvideos
!style="padding-left: 10px; padding-right: 10px;"|mixed
|-
|style="padding-left: 5px;"|genre
|string
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|album
|string
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|artist
|string
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|albumartist
|string
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|title
|string
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|year
|number
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|time
|number
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|tracknumber
|number
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|filename
|string
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|path
|string
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|playcount
|number
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|lastplayed
|date
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|inprogress
|boolean
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|rating
|number
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|comment
|string
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|dateadded
|date
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|plot
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|plotoutline
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|tagline
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|mpaarating
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|top250
|number
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|status
|string
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|votes
|number
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|director
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|actor
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|studio
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|country
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|numepisodes
|number
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|numwatched
|number
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|writers
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|airdate
|date
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|episode
|number
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|season
|number
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|tvshow
|string
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|episodetitle
|string
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|review
|string
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|themes
|string
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|moods
|string
|{{no}}
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|styles
|string
|{{no}}
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|type
|string
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|label
|string
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|hastrailer
|boolean
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|videoresolution
|number
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|audiochannels
|number
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|videocodec
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|audiocodec
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|audiolanguage
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|subtitlelanguage
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|videoaspect
|number
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|set
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|-
|style="padding-left: 5px;"|tag
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|instruments
|string
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|biography
|string
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|born
|string
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|band formed
|string
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|disbanded
|string
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|died
|string
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|playlist
|string
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|}

==== Operators ====
The <code>operator</code> attribute specifies the rule that should be used to match the parameter to the <code>field</code>. All matching is done case-insensitive. The allowed <code>operator</code>s are:

{| class="prettytable" style="margin-right: 0;"
! <code>operator</code>
! Definition
|-
| contains
| True if the field contains the parameter as a substring
|-
| doesnotcontain
| True if the field does not contain the parameter as a substring
|-
| is
| True if the field matches the parameter exactly
|-
| isnot
| True if the field does not match the parameter exactly
|-
| startswith
| True if the start of the field matches the parameter
|-
| endswith
| True if the end of the field matches the parameter
|-
| lessthan
| True if the content of the field is less than the parameter
|-
| greaterthan
| True if the content of the field is greater than the parameter
|-
| after
| True if the content of the field comes after the parameter
|-
| before
| True if the content of the field comes before the parameter
|-
| inthelast
| True if the field falls in the last range specified by the parameter. Only applicable for a date field.
|-
| notinthelast
| True if the field does not fall in the last range specified by the parameter. Only applicable for a date field.
|}

=== Limit and Order ===
The <code><limit></code> tag simply takes a number of songs as it's limit. A missing limit tag, or <code><limit>0</limit></code> will retrieve all matching songs. The <code><order></code> tag has a <code>direction</code> attribute, the values of which can be <code>ascending</code> or <code>descending</code>, and it's value is a field as above, or can be <code><order>random</order></code> if you want a random ordering returned. Note that random should be used with care - it is quite slow if the returned results from the <code><rule></code> sets is large (more than 500 items).

The above example, therefore selects all songs whose artist field is U2 and whose year field is greater than 1990, orders them by the number of times they've been played (most played first) then limits it to just 50. Thus, the top 50 songs you've played from all U2 songs published after 1990.

<syntaxhighlight lang="xml" enclose="div">
<limit>50</limit>
<order direction="descending">playcount</order>
</syntaxhighlight>

=== Grouping ===
Grouping was added in XBMC v13. The <code><group></code> tag allows to group the resulting list of media items by a specific category. The final list will consist of folder nodes containing matching media items. Depending on the type of the Smart Playlist the following grouping categories exist:

{| class="prettytable" style="margin-right: 0;"
!colspan="2"|<code>field</code>
!colspan="3"|music
!colspan="4"|video
!colspan="1"|
|-
!style="padding-left: 5px; padding-right: 10px;"|Name
!style="padding-left: 10px; padding-right: 10px;"|Data type
!style="padding-left: 10px; padding-right: 10px;"|songs
!style="padding-left: 10px; padding-right: 10px;"|albums
!style="padding-left: 10px; padding-right: 10px;"|artists
!style="padding-left: 10px; padding-right: 10px;"|movies
!style="padding-left: 10px; padding-right: 10px;"|tvshows
!style="padding-left: 10px; padding-right: 10px;"|episodes
!style="padding-left: 10px; padding-right: 10px;"|musicvideos
!style="padding-left: 10px; padding-right: 10px;"|mixed
|-
|style="padding-left: 5px;"|none
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|genres
|string
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|years
|string
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|actors
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|artists
|string
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|directors
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|writers
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|studios
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|style="padding-left: 5px;"|countries
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|sets
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{no}}
|{{no}}
|{{no}}
|{{no}}
|-
|style="padding-left: 5px;"|tags
|string
|{{no}}
|{{no}}
|{{no}}
|{{yes}}
|{{yes}}
|{{no}}
|{{yes}}
|{{yes}}
|-
|}

{{Notice|There's an important difference between not providing a <code><group></code> tag (or providing an empty <code><group></code> tag) and setting the value of the <code><group></code> tag to '''none''': The latter will overrule any mixed grouping that would be applied by default to a list of media items (specifically for a mixed list of movies and [[movie sets]] if the setting ''Group movies into sets'' is enabled).}}

==== Mixed grouping ====

For the '''sets''' grouping category there is support for additional so called mixed grouping. The difference to normal grouping is that the resulting list will not just be a list of grouped folders but a mix of media items and grouped folders. Mixed grouping can be controlled using the '''mixed''' attribute in the <code><group></code> tag with a boolean value (''true'' or ''false'').

== Combining playlists ==
The <code>playlist</code> <code>field</code> can be used to combine several playlists together. When playlists are combined, the <code><limit></code> and <code><order></code> tags of the included playlists are ignored; only the <code><order></code> and <code><limit></code> of the final playlist are used.

As a simple example, lets create a new playlist combining the "Rock Music from the 1970s" and "Recently Played Songs" playlists above, to produce a playlist with the recently played rock songs from the 1970s.

'''Recently played rock tracks from the 1970s'''
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0"?>
<smartplaylist type="songs">
<name>Recently played Rock Tracks from the 1970s</name>
<match>all</match>
<rule field="playlist" operator="is">Rock Music from the 1970s</rule>
<rule field="playlist" operator="is">Recently Played Songs</rule>
</smartplaylist>
</syntaxhighlight>

Using this system allows very complex queries to be built. Note that in a single playlist, you can only match ALL of the rules, or ONE (or more) of the rules. This is basically either ANDing the conditions together, or ORing them together. You cannot mix AND with OR in a single playlist. To build up a playlist with both AND and OR operations on the rules, you use multiple playlists to group the AND operations and the OR operations, then combine them as above.

== Examples ==
=== Movie examples ===
==== Random movie ====
Only ''one'' movie is added to the list. This isn't possible to create in the GUI because the lower limit is 10 (or at least the limit needs to be edited afterward). 
Even though the limit is only ''one'' you still need to set ''random'' order.

<syntaxhighlight lang=xml>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<smartplaylist type="movies">
<name>Random movie</name>
<match>all</match>
<rule field="playcount" operator="is">
<value>0</value>
</rule>
<limit>1</limit>
<order direction="ascending">random</order>
</smartplaylist>
</syntaxhighlight> 

=== Music examples ===
==== Recently played songs ====
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<smartplaylist type="songs">
<name>Recently Played Songs</name>
<match>all</match>
<rule field="lastplayed" operator="inthelast">
<value>2 weeks</value>
</rule>
<order direction="descending">lastplayed</order>
</smartplaylist>
</syntaxhighlight>

==== Top 100 songs ====
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<smartplaylist type="songs">
<name>Top 100 Songs</name>
<match>all</match>
<rule field="playcount" operator="greaterthan">
<value>0</value>
</rule>
<order direction="descending">playcount</order>
<limit>100</limit>
</smartplaylist>
</syntaxhighlight>

==== Rock music from the 1970s ====
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<smartplaylist type="songs">
<name>Rock Music from the 1970s</name>
<match>all</match>
<rule field="genre" operator="is">
<value>Rock</value>
</rule>
<rule field="year" operator="greaterthan">
<value>1969</value>
</rule>
<rule field="year" operator="lessthan">
<value>1980</value>
</rule>
</smartplaylist>
</syntaxhighlight> 

=== TV show examples ===
==== Last played episodes (history) ====
Not ''in progress'' episodes and ''playcount'' > 0.
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<smartplaylist type="episodes">
<name>Last played episodes (history)</name>
<match>all</match>
<rule field="lastplayed" operator="inthelast">
<value>6 months</value>
</rule>
<rule field="inprogress" operator="false" />
<rule field="playcount" operator="greaterthan">
<value>0</value>
</rule>
<order direction="descending">lastplayed</order>
</smartplaylist>
</syntaxhighlight>

==== Last played TV shows ====
Including TV shows with ''in progress'' episodes.
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<smartplaylist type="tvshows">
<name>Last played TV shows</name>
<match>all</match>
<rule field="lastplayed" operator="inthelast">
<value>6 months</value>
</rule>
<order direction="descending">lastplayed</order>
</smartplaylist>
</syntaxhighlight>

== Notes ==
<references/>

{{Gotham updated}}

[[Category:Video library]]
[[Category:Music library]]

CEC

2014-01-12T10:40:39Z

Borromini: Added Sony KDL-52NX800 and Yamaha RX-1071 to compatibility list

{{mininav|[[General topics]]|[[Remotes]]}}
HDMI [[w:Consumer Electronics Control|CEC]] stands for Consumer Electronics Control. Since the Eden release XBMC comes with the new [http://libcec.pulse-eight.com/ libCEC 2.1.3] which allows control of the XBMC interface over the standard TV remote that comes with your TV. As buttons are pressed the remote command is sent via the HDMI cable to your XBMC device. CEC allows for control of devices over the HDMI port, which allows for things like:
* Controlling XBMC from the TV's remote control
* Automatically switch to the right TV input device
* letting the HTPC control what mode your audio receiver is on when the TV switches on
* Turning all devices off with one remote
* and a lot more!

== Settings ==
Settings for your CEC devices can be found in:

System -> Settings -> System -> Input Devices -> Peripherals -> CEC adapter

== Trade names ==
There are different trade names for HDMI CEC, depending on who is the manufacturer of your device, so it doesn't have to be stated as HDMI-CEC. Find your manufacturer on this list and see what it is called for your device:

* Samsung - '''Anynet+'''
* Sony - '''BRAVIA Link''' or '''BRAVIA Sync'''
* Sharp - '''Aquos Link'''
* Hitachi - '''HDMI-CEC'''
* AOC - '''E-link'''
* Pioneer - '''Kuro Link'''
* Toshiba - '''Regza Link''' or '''CE-Link'''
* Onkyo - '''RIHD (Remote Interactive over HDMI)'''
* LG - '''SimpLink'''
* Panasonic - '''VIERA Link''' or '''HDAVI Control''' or '''EZ-Sync'''
* Philips - '''EasyLink'''
* Mitsubishi - '''NetCommand for HDMI'''
* Runco International - '''RuncoLink'''

== Devices Known to work ==
With different TV's and devices comes different compatibility. An up to date vendor support matrix can be found [http://libcec.pulse-eight.com/vendor/support here], which lists which features are supported for each vendor.

Below is a list of TV's which are known to be working with CEC and XBMC:

=== TVs ===
* LG 47LS4600
* LG 47CS570
* LG LM620T
* LG 37LG6000
* LG 42LD420
* LG 42LD550
* LG 60PM6700 (Most of the expected buttons work, EXCEPT the number & channel buttons)
* LG 32LN572B (2013 model tested on Raspberry Pi running OpenELEC 3.2.3. The regular TV remote control works except forward and rewind but the left and right skip keys works so it's quiet useable. The Magic Remote also seems to work but haven't been tested properly)
* Panasonic TXL-47DT50
* Panasonic Viera GT30
* Panasonic Viera S60
* Panasonic Viera ST50
* Panasonic Viera TH-42PX80E
* Panasonic Viera TH-42PZ85E
* Panasonic Viera TH-P42S10A
* Panasonic Viera TH-P50G10A
* Philips 37PFL6007K
* Philips 47PFL5007K
* Samsung ES6800
* Samsung LE32B650
* Samsung LE37D570
* Samsung UE40C7700
* Samsung UE46F8000
* Samsung UE50EH5300
* Samsung UE55F6510
* Sharp LC-52D83X
* Sony Bravia KDL46-HX800
* Sony Bravia KDL-40HX705
* Sony Bravia KDL-46NX715
* Sony Bravia KDL-40M4000
* Sony Bravia KDL-32W5500
* Sony Bravia KDL-46EX520
* Sony Bravia KDL-52NX800
* Sony Bravia KD55X9004A
* Sony NSX-40GT1 (Google TV)
* Vizio M-Series

=== Home Cinema Systems ===
* Onkyo HT-R390 Amplifier
* Yamaha RX-V473 AV-Receiver
* Yamaha RX-V1071 AV Receiver (only on HDMI Out 1)

=== Projectors ===
* Epson EH-TW6100

=== XBMC Devices ===
HDMI ports on computers (onboard or via GPU) do not have the CEC feature, but can use a CEC adapter such as this one from [[Pulse-Eight]]: http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx

Some recent Intel motherboards come with a new HTPC header, to connect Pulse-Eight's internal HDMI CEC adapter: http://www.pulse-eight.com/store/products/117-internal-hdmi-cec-adapter.aspx

==== [[Raspberry Pi]] ====
The Raspberry Pi GPU has CEC support which is supported by libCEC, and is therefore fully supported by XBMC.

=== Common Issues with CEC ===
When "setting up" CEC make sure your configuration uses good HDMI cables. Especially cheap cables - still able to support 1080p without any problems - have been reported to cause problems with CEC (eg. devices like raspberry not showing up in the CEC menu at all, devices showing up but remote not working, etc).

Using better HDMI cables might resolve that problem.

There are also reports of devices with improper HDMI CEC implementation, such as ROKU streaming box, causing problems with CEC device recognition. Disconnecting non-CEC devices, or upgrading firmware on those devices, may resolve the problem.

== Branding of CEC ==
Different brands will call CEC a different name on their products, the list below will show what the branding of CEC:

* Samsung - AnyNet+
* Sharp - Aquos Link
* Sony - BRAVIA Link and BRAVIA Sync
* Hitachi - HDMI-CEC
* AOC - E-Link
* Pioneer - Kuro Link
* Toshiba - CE-Link and Regza Link
* Onkyo - RIHD (Remote Interactive over HDMI)
* LG - SimpLink
* Panasonic - HDAVI Control, EZ-Sync, VIERA Link
* Philips - EasyLink
* Loewe - Digital Link Plus or without Plus

== Further reading ==
* http://libcec.pulse-eight.com/faq

[[Category:Remotes]]
[[Category:XBMC Manual]]
{{frodo updated}}