Official Kodi Wiki - User contributions [en]

NVIDIA SHIELD TV

2017-02-17T16:25:03Z

Rodalpho: removed note about remote connections-- they work now and are fully supported in the UI

{{mininav|[[Devices]]|[[Android]]}}
{{device notice}}

{{Infobox information appliance| name = NVIDIA SHIELD TV| image = [[File:Nvidia_SHIELD_Console.jpg|250px]]| manufacturer = NVIDIA| releasedate = May 28, 2015 (first-version) and January 16, 2017 (second-release)| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 5.1 "Lollipop", with updates to Android 6.0 "Marshmallow") and Android 7.0 "Nougat"| soc = [[Nvidia Tegra]] X1 (TX1) | cpu = [[Nvidia Tegra]] X1 (TX1), Big.LITTLE Octa-Core (4 x ARM Cortex A57 CPU cores and 4 x ARM Cortex A53 CPU cores)| graphics = 256-core Maxwell GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 30 fps | storage = Standard model with 16 GB internal, Pro model with 500 GB harddrive, and all models extendable with optional external| memory = 3 GB RAM| connectivity = HDMI 2.0b supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.1/BLE, 2 x USB 3.0 (Type A), 1 x Micro-USB 2.0 port, Dual-Band WiFi (802.11ac 2×2 MIMO), 10/100/1000 Ethernet, IR Receiver| dimensions = 210 x 130 x 25 mm}}

<section begin="intro" />'''NVIDIA SHIELD TV''' (originally known as ''SHIELD Console'') is an Android-based set-top box and game console that contains a very powerful ARM processor, (that is able to handle the most heavy of Kodi skins and more). It is one of the first Android based devices featuring high-end media playback capabilities such as of and support high-definition audio at up to 192 kHz, 23.976 Hz support with automatic refresh rate switching, 10-bit HEVC (H.265), and VP9 video codecs, and 4K UltraHD (2160p) resolution with HDR via HDMI 2.0b output support for Kodi.<section end="intro" />

Running the [[wikipedia:Android TV|Android TV]] operating system (first-generation was originally released on [[wikipedia:Android Lollipop|Android 5.1 "Lollipop"]] and have since then recieved official updates to [[wikipedia:Android Marshmallow|Android 6.0 "Marshmallow"]] and [[wikipedia:Android Nougat|Android 7.0 "Nougat"]]) on a [[Nvidia Tegra|Tegra X1 SoC (System on Chip)]], the NVIDIA SHIELD TV stands above most of the other high-end Android-based offerings not only because best-in-class hardware offering the fastest graphics for gaming capabilities for Android, but also because due to NVIDIA's strong product support and long lifecycle updates of their own SHIELD series products. It comes with [[10 foot interface|remote friendly]] versions of Amazon Video, Netflix, Vudu, Hulu, HBO, UltraFlix, Fox, Google Play Movies, and other video service clients, with many supporting videos in native 4K Ultra HD (2160p) resolution at up to 60 frames-per-second and HDR.

The Android TV platform delivers good conversational voice search for the native Android TV (leanback) app via an integrated microphone inside the included game controller. Adding to that it also comes with NVIDIA's gaming ecosystem capable of running all graphically intensive [[wikipedia:AAA (game industry)|AAA ("triple A") games]] for Android in 1080p at 60fps, as well as supporting NVIDIA's low-latency GameStream technologies for GeForce-equipped PC game streaming in up to 4K HDR resolution, including direct access to Steam Big Picture from the Steam app, and NVIDIA's "GeForce NOW" (formerly "Nvidia GRID") cloud game-streaming service. All these gaming features combined with high-end media player functionality makes it a very good convergence device when pairing with Kodi for media playback.

== Installing Kodi==
{{Main|HOW-TO:Install Kodi for Android TV}}

Normal "vanilla" builds of Kodi should run just fine on the Shield.

{{Google Play}}

== Launching Android apps within Kodi ==
{{main|HOW-TO:Launch Android apps}}
{{#lst:HOW-TO:Launch Android apps|extended intro}}
{{-}}

== Controls ==
You can use standard Bluetooth accessories, such as a wireless keyboard, mouse, or game controller with your Nvidia SHIELD TV console.

=== Bluetooth remote ===
* NVIDIA SHIELD Remote [http://shield.nvidia.com/store/remote]
* Other standard Bluetooth remotes (such as the Amazon Fire TV replacement remote) can be paired and should also work.

=== Integrated IR Reciever ===
* Logitech Harmony IR Remotes are supported by NVIDIA SHIELD (2015) and NVIDIA SHIELD Pro (2017). The NVIDIA SHIELD (2017) with 16GB storage does not have an IR receiver.
(Tested and reported working with a Logitech Harmony Touch, supposedly also with others. Button ABXY don't work yet, so no easy way to access the Kodi Menu. You can notice a slight lag during browsing. Custom keyboard layouts need to be used for this. Logitech said in numerous forums posts that they're working on better support.)

=== CEC ===
Generic Android-level CEC support is available on the Android TV platform, however Kodi will not see a CEC device directly, but instead just treat the it like generic input.

=== USB ===
USB port allows for various additional remote types, such as [[FLIRC]] IR dongle, various RF dongles, etc. Most of these devices will likely show up as a keyboard type input.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the NVIDIA SHIELD TV Console. Most of these devices will likely show up as a [[keyboard]] type input.
* Reported working with a Microsoft Bluetooth Mobile Keyboard 6000.

====Working Bluetooth Gamepads====
* NVIDIA SHIELD Controller [http://shield.nvidia.com/store/controller]
* 8Bitdo NES30 controller is working, but is not recognized by all Android games.

====Working Bluetooth Remotes====
* Harmony Smart Control Hub
List of working codes/commands (as of 2015/7/1) http://www.mediafire.com/view/i0i6y6k7z8lhdf8/Harmon_SCH_-_Sheild_ATV_Commands.pdf

== Videos ==
A Kodi oriented review of the Shield:

{{youtube|0MH73mhO0fM}}

Kodi-related videos for end-users:

{{youtube|A2i_TiIJ7uM}}

Kodi-related videos for developers:

{{youtube|QpJ3r9FWfow}}

== Hints and tips ==
Some of this is copied directly from NVIDIA's GeForce Forum for SHIELD Android TV support.[https://forums.geforce.com/default/topic/836884/shield-android-tv/helpful-shield-information-for-new-shield-android-tv-users-updated-6-5-2015-/] More generic but useful info about the SHIELD Android TV that is not specific to Kodi can also be found in NVIDIA's official SHIELD FAQ[http://shield.nvidia.com/support/nvidia-android-tv/faq/1] and SHIELD User Guide[http://support-shield.nvidia.com/android-tv-user-guide/index.htm#_ga=1.98702110.121900636.1426802792&t=About_SHIELD.htm].
* If you hold the play button on the SHIELD game controller a '''mouse cursor''' will pop up on your screen and turn the right analog thumb stick on your game controller to a mouse controller which can control that mouse cursor.
* If you plan on using a '''microSD card or USB storage''' with your SHIELD, make sure to '''unmount''' the drive before unplugging it. This is done from ''Settings'' -> ''Storage and reset'' inside the Android TV menus, not inside Kodi. Select your storage device and then choose the unmount option. Now you may safely unplug/remove your storage device from your SHIELD Android TV.
* If you are unable to '''pair your SHIELD game controller''' during initial setup and your SHIELD is connected to your network over wired Ethernet, try temporarily disconnecting your wired Ethernet cable to go into WiFi mode and check if pairing issue is fixed.
* If the '''Google Play Store is not opening''', check if the version is at least 5.5.15 or later. If not you should be receiving this update soon. After the update if the problem continues, try clearing the data and cache for the Google Play Store app.
* For maximum performance, '''wired Ethernet is recommended'''. The wired Ethernet port on SHIELD supports 10/100/1000 Mbps. Once wired Ethernet is connected, SHIELD will disable Wi-Fi and automatically switch to use only wired Ethernet.
* If you experience '''audio playback issues''' try going to ''Settings'' -> ''System'' -> ''Audio output'' and setting the value for ''Keep audio device alive'' to ''Never'' (the default is 1 minute).
* If you press and hold the "O" button on the SHIELD remote (or the Nvidia button on the game controller) it will pull up a window that allows you to '''take screenshots or a video''' of anything that is being displayed on your TV. If you use the video function it will capture both video and audio of anything currently being displayed. Also, if you have ES File Explore installed, you can directly upload the screenshot or video to any location that ES has access to.
* '''Watching 4K content''' from SHIELD requires a 4K UltraHD display with '''HDMI 2.0 and HDCP 2.2''' support. Connect SHIELD to only the 4K-enabled HDMI input that supports HDCP 2.2. Consult your 4K UltraHD display's user guide to find the correct HDMI port to plug SHIELD into for watching 4K content. SHIELD also supports content rendered with 4:4:4, and 4:2:0 chroma subsampling frequency ratios. (NOTE: Netflix 4K content is currently only enabled for HDCP 2.2 ports. See your 4K UltraHD display's user guide for further details). If one of the HDMI 2.0 ports does not work then try another until you find a port that works.
* Use of an AV Receiver with HDMI for video and Toslink for audio may result in '''audio lagging behind video''', and each of the these type of configurations may add varying levels of delay along the audio and video path resulting in lip-sync issues in the content viewed on the TV. Use the built-in AV sync slider utility (not in Kodi) in the SHIELD menu ''Settings'' > ''HDMI'' > ''AV Sync Tuner'' to calibrate for any audio lag. Adjust the delay on the audio signal until you hear the audio beep from your speakers exactly when the bouncing ball touches the line. The AV sync slider allows you to advance audio by 1 second at most (in small increments of 10ms) to synchronize the audio and video. (Note: This tool is effective only when SHIELD is connected to your AV Receiver over HDMI (i.e. audio/video over HDMI); it is not meant to be used when a headset is plugged into SHIELD controller/SHIELD remote or USB audio device or Bluetooth audio device).
* If '''video lags behind audio''' instead (i.e. audio is ahead of video) then use your AV receiver’s settings to delay audio.
*?

== Known issues and limitations==
Known issues and limitations related to usage of Kodi on NVIDIA SHIELD TV, including limitations in the hardware, firmware, and software directly or indirectly related to and for Kodi usage.
* HDMI-CEC is supposedly supported supported in the hardware and in the Android firmware, but no news yet on API or other interface with [[LibCEC]] for native (direct) Kodi support of the CEC controller.
* Kodi's existing [[Settings/Videos|video setting options]] for "Adjust display refresh rate to match video" and "Sync playback to display" to sync screen refresh rate to playback frame rate option is included in the Kodi 15.x (Isengard) releases, but it is still limited to 24/25/30/50/60 Hz refresh rates in the firmware from Nvidia. Nvidia's Shield Android TV OTA 2.0 Update also added support for for 23.976 and 59.94 Hz but it may not work in Kodi for all setups.
** Automatic refresh rate switching is not working with all televisions brands/models, and on some that do work only do so after the SHIELD have been rebooted/restarted or booted after your television and AV-receiver. Other than waiting for future firmware updates the general advice is to try another HDMI until on your television or AV-receiver you find a port that works (or work better).
* MPEG-2 hardware decoding (and hardware deinterlacing) did not work before NVIDIA SHIELD TV Pro OTA Firmware version 1.2 update, so be sure to update to latest firmware.
* VC-1 and WMV-9 videos are software decoded only so far, reason for this is that NVIDIA have so far only licensed MPEG-2, H.264, HEVC (H.265), and VP9 codecs for video playback, as well as Dolby Digital (DD) and Dolby Digital Plus (DD+) for audio<ref>http://www.legitreviews.com/nvidia-shield-android-tv-review_164223/3 Legit Reviews - NVIDIA SHIELD TV Review</ref>, (and unfortunately NVIDIA do at least not yet offer a add-on license keys for a codec pack similar to Raspberry Pi<ref name="RaspPi Codec License keys">http://www.raspberrypi.com/license-keys/ Raspberry Pi Store - License keys</ref>).<ref name="Requests to NVIDIA for Codec Packs">https://forums.geforce.com/default/topic/836487/shield-android-tv/codec-support-/ GeForce Forums - Requests to Nvidia for Codec Packs</ref> There is however apparently a hack available to enable VC-1 hardware decoding by editing Android file "/system/etc/media_codecs.xml" if you have first rooted the SATV.[http://forum.xda-developers.com/showpost.php?p=61241497&postcount=47]
*HD audio including DTS-HD MA, DTS:X, Dolby True HD, Dolby Atmos can be all be passed-through (bitstreamed) on Nvidia Shieild TV, but this currently only works with the native video player. Pass-through for HD audio is currently not working in Kodi and is a work-in-progress.
* The Nexus Player remote does not pair at all with the Shield console. It did with the Razer Forge, but not the Shield console.
* VP9 hardware video decode is supposedly supported at to to 4K / 2160p (UltraHD) resolution, such as YouTube source, but not yet confirmed working in Kodi for Android on the NVIDIA Tegra X1 (TX1) SoC.
* VC-1 hardware decoding (possibly including hardware deinterlacing?) is suppose to work since OTA Firmware version 2.0 update from NVIDIA for SHIELD TV, so be sure to update to latest firmware and run tests in Kodi for independent confirmations.
* WMV-9 hardware decoding (possibly including hardware deinterlacing?) is suppose to work since OTA Firmware version 2.0 update from NVIDIA for SHIELD TV, so be sure to update to latest firmware and run tests in Kodi for independent confirmations.
* OTA Firmware version 2.0 update from NVIDIA for SHIELD TV is suppose to have added native playback and output of video content encoded at 23.976 and 59.94 Hz. Also supports since erlier are video content encoded at 24 Hz, 25 Hz, 30 Hz. This however needs testing and confirmation if it works with Kodi's existing [[Settings/Videos|video setting options]] for "Adjust display refresh rate to match video" and "Sync playback to display" to sync screen refresh rate to playback frame rate option is included in the very latest nighty builds. Note though that automatic refresh rate switching will not work with all televisions brands/models or in all HDMI ports.
* OTA Firmware version 3.2 update from NVIDIA for SHIELD TV is suppose to have native pass-through/bit-streaming audio support for AC3, EAC3, Dolby 5.1, Dolby 7.1, DTS-HD, DTS-HD MA, DTS:X, Dolby TrueHD, and Dolby Atmos, up to high resolution 24-bit 192 kHz audio over HDMI and USB. Also added is support for USB-S/PDIF dongles which can enable users to connect SHIELD to older sound bars and audio receivers. All this however needs testing and confirmation if it works with Kodi's very latest nighty builds of Kodi for Android.
* ?

== Random notes ==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}

* ?

==References==
{{reflist}}
* [http://www.anandtech.com/show/9289/the-nvidia-shield-android-tv-review/6 AnandTech - The NVIDIA SHIELD Android TV Review: A Premium 4K Set Top Box]
* [http://www.legitreviews.com/nvidia-shield-android-tv-review_164223/3 Legit Reviews - NVIDIA SHIELD Android TV Review]

== See also ==
* [[Android hardware]]
* [[Android]]

== Links ==
* Kodi forum discussion threads about the NVIDIA SHIELD TV:
**Support and help thread: http://forum.kodi.tv/showthread.php?tid=228158
**General hardware discussion: http://forum.kodi.tv/showthread.php?tid=220297
*Related articles on Wikipedia:
** Wikipedia article on NVIDIA SHIELD TV: [[wikipedia:Nvidia Shield Console]]
** Wikipedia article on Android TV (OS used on NVIDIA SHIELD Console): [[wikipedia:Android TV]]
*Official NVIDIA pages and sites about the SHIELD console:
** NVIDIA SHIELD TV product page: http://shield.nvidia.com/console
***NVIDIA SHIELD Remote Control http://shield.nvidia.com/store/remote
***NVIDIA SHIELD Game Controller http://shield.nvidia.com/store/controller
** NVIDIA SHIELD TV FAQ (Frequently Asked Questions): http://shield.nvidia.com/support/nvidia-android-tv/faq/1
** NVIDIA SHIELD TV User Guide: http://support-shield.nvidia.com/android-tv-user-guide/index.htm#_ga=1.98702110.121900636.1426802792&t=About_SHIELD.htm
** NVIDIA Blog post: http://blogs.nvidia.com/blog/2015/05/28/nvidia-shield-available/
** NVIDIA SHIELD forum for Android TV https://forums.geforce.com/default/board/159/
** NVIDIA SHIELD development tools and other resources for developers: https://developer.nvidia.com/develop4shield
**Tegra Android Development Pack: https://developer.nvidia.com/tegra-android-development-pack
* NVIDIA SHIELD TV Utility App: http://goo.gl/4FiQCT

[[Category:HTPC]]
[[Category:Android]]
[[Category:ARM]]
[[Category:Nvidia SHIELD]]
[[Category:Nvidia Tegra]]

NVIDIA SHIELD TV

2017-02-17T16:22:53Z

Rodalpho: noted that the new $200 2017 shieldtv does not support IR

{{mininav|[[Devices]]|[[Android]]}}
{{device notice}}

{{Infobox information appliance| name = NVIDIA SHIELD TV| image = [[File:Nvidia_SHIELD_Console.jpg|250px]]| manufacturer = NVIDIA| releasedate = May 28, 2015 (first-version) and January 16, 2017 (second-release)| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 5.1 "Lollipop", with updates to Android 6.0 "Marshmallow") and Android 7.0 "Nougat"| soc = [[Nvidia Tegra]] X1 (TX1) | cpu = [[Nvidia Tegra]] X1 (TX1), Big.LITTLE Octa-Core (4 x ARM Cortex A57 CPU cores and 4 x ARM Cortex A53 CPU cores)| graphics = 256-core Maxwell GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 30 fps | storage = Standard model with 16 GB internal, Pro model with 500 GB harddrive, and all models extendable with optional external| memory = 3 GB RAM| connectivity = HDMI 2.0b supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.1/BLE, 2 x USB 3.0 (Type A), 1 x Micro-USB 2.0 port, Dual-Band WiFi (802.11ac 2×2 MIMO), 10/100/1000 Ethernet, IR Receiver| dimensions = 210 x 130 x 25 mm}}

<section begin="intro" />'''NVIDIA SHIELD TV''' (originally known as ''SHIELD Console'') is an Android-based set-top box and game console that contains a very powerful ARM processor, (that is able to handle the most heavy of Kodi skins and more). It is one of the first Android based devices featuring high-end media playback capabilities such as of and support high-definition audio at up to 192 kHz, 23.976 Hz support with automatic refresh rate switching, 10-bit HEVC (H.265), and VP9 video codecs, and 4K UltraHD (2160p) resolution with HDR via HDMI 2.0b output support for Kodi.<section end="intro" />

Running the [[wikipedia:Android TV|Android TV]] operating system (first-generation was originally released on [[wikipedia:Android Lollipop|Android 5.1 "Lollipop"]] and have since then recieved official updates to [[wikipedia:Android Marshmallow|Android 6.0 "Marshmallow"]] and [[wikipedia:Android Nougat|Android 7.0 "Nougat"]]) on a [[Nvidia Tegra|Tegra X1 SoC (System on Chip)]], the NVIDIA SHIELD TV stands above most of the other high-end Android-based offerings not only because best-in-class hardware offering the fastest graphics for gaming capabilities for Android, but also because due to NVIDIA's strong product support and long lifecycle updates of their own SHIELD series products. It comes with [[10 foot interface|remote friendly]] versions of Amazon Video, Netflix, Vudu, Hulu, HBO, UltraFlix, Fox, Google Play Movies, and other video service clients, with many supporting videos in native 4K Ultra HD (2160p) resolution at up to 60 frames-per-second and HDR.

The Android TV platform delivers good conversational voice search for the native Android TV (leanback) app via an integrated microphone inside the included game controller. Adding to that it also comes with NVIDIA's gaming ecosystem capable of running all graphically intensive [[wikipedia:AAA (game industry)|AAA ("triple A") games]] for Android in 1080p at 60fps, as well as supporting NVIDIA's low-latency GameStream technologies for GeForce-equipped PC game streaming in up to 4K HDR resolution, including direct access to Steam Big Picture from the Steam app, and NVIDIA's "GeForce NOW" (formerly "Nvidia GRID") cloud game-streaming service. All these gaming features combined with high-end media player functionality makes it a very good convergence device when pairing with Kodi for media playback.

== Installing Kodi==
{{Main|HOW-TO:Install Kodi for Android TV}}

Normal "vanilla" builds of Kodi should run just fine on the Shield.

{{Google Play}}

== Launching Android apps within Kodi ==
{{main|HOW-TO:Launch Android apps}}
{{#lst:HOW-TO:Launch Android apps|extended intro}}
{{-}}

== Controls ==
You can use standard Bluetooth accessories, such as a wireless keyboard, mouse, or game controller with your Nvidia SHIELD TV console.

=== Bluetooth remote ===
* NVIDIA SHIELD Remote [http://shield.nvidia.com/store/remote]
* Other standard Bluetooth remotes (such as the Amazon Fire TV replacement remote) can be paired and should also work.

=== Integrated IR Reciever ===
* Logitech Harmony IR Remotes are supported by NVIDIA SHIELD (2015) and NVIDIA SHIELD Pro (2017). The NVIDIA SHIELD (2017) with 16GB storage does not have an IR receiver.
(Tested and reported working with a Logitech Harmony Touch, supposedly also with others. Button ABXY don't work yet, so no easy way to access the Kodi Menu. You can notice a slight lag during browsing. Custom keyboard layouts need to be used for this. Logitech said in numerous forums posts that they're working on better support.)

=== CEC ===
Generic Android-level CEC support is available on the Android TV platform, however Kodi will not see a CEC device directly, but instead just treat the it like generic input.

=== USB ===
USB port allows for various additional remote types, such as [[FLIRC]] IR dongle, various RF dongles, etc. Most of these devices will likely show up as a keyboard type input.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the NVIDIA SHIELD TV Console. Most of these devices will likely show up as a [[keyboard]] type input.
* Reported working with a Microsoft Bluetooth Mobile Keyboard 6000.

====Working Bluetooth Gamepads====
* NVIDIA SHIELD Controller [http://shield.nvidia.com/store/controller]
* 8Bitdo NES30 controller is working, but is not recognized by all Android games.

====Working Bluetooth Remotes====
* Harmony Smart Control Hub
List of working codes/commands (as of 2015/7/1) http://www.mediafire.com/view/i0i6y6k7z8lhdf8/Harmon_SCH_-_Sheild_ATV_Commands.pdf

== Videos ==
A Kodi oriented review of the Shield:

{{youtube|0MH73mhO0fM}}

Kodi-related videos for end-users:

{{youtube|A2i_TiIJ7uM}}

Kodi-related videos for developers:

{{youtube|QpJ3r9FWfow}}

== Hints and tips ==
Some of this is copied directly from NVIDIA's GeForce Forum for SHIELD Android TV support.[https://forums.geforce.com/default/topic/836884/shield-android-tv/helpful-shield-information-for-new-shield-android-tv-users-updated-6-5-2015-/] More generic but useful info about the SHIELD Android TV that is not specific to Kodi can also be found in NVIDIA's official SHIELD FAQ[http://shield.nvidia.com/support/nvidia-android-tv/faq/1] and SHIELD User Guide[http://support-shield.nvidia.com/android-tv-user-guide/index.htm#_ga=1.98702110.121900636.1426802792&t=About_SHIELD.htm].
* If you hold the play button on the SHIELD game controller a '''mouse cursor''' will pop up on your screen and turn the right analog thumb stick on your game controller to a mouse controller which can control that mouse cursor.
* If you plan on using a '''microSD card or USB storage''' with your SHIELD, make sure to '''unmount''' the drive before unplugging it. This is done from ''Settings'' -> ''Storage and reset'' inside the Android TV menus, not inside Kodi. Select your storage device and then choose the unmount option. Now you may safely unplug/remove your storage device from your SHIELD Android TV.
* If you are unable to '''pair your SHIELD game controller''' during initial setup and your SHIELD is connected to your network over wired Ethernet, try temporarily disconnecting your wired Ethernet cable to go into WiFi mode and check if pairing issue is fixed.
* If the '''Google Play Store is not opening''', check if the version is at least 5.5.15 or later. If not you should be receiving this update soon. After the update if the problem continues, try clearing the data and cache for the Google Play Store app.
* For maximum performance, '''wired Ethernet is recommended'''. The wired Ethernet port on SHIELD supports 10/100/1000 Mbps. Once wired Ethernet is connected, SHIELD will disable Wi-Fi and automatically switch to use only wired Ethernet.
* If you experience '''audio playback issues''' try going to ''Settings'' -> ''System'' -> ''Audio output'' and setting the value for ''Keep audio device alive'' to ''Never'' (the default is 1 minute).
* If you press and hold the "O" button on the SHIELD remote (or the Nvidia button on the game controller) it will pull up a window that allows you to '''take screenshots or a video''' of anything that is being displayed on your TV. If you use the video function it will capture both video and audio of anything currently being displayed. Also, if you have ES File Explore installed, you can directly upload the screenshot or video to any location that ES has access to.
* '''Watching 4K content''' from SHIELD requires a 4K UltraHD display with '''HDMI 2.0 and HDCP 2.2''' support. Connect SHIELD to only the 4K-enabled HDMI input that supports HDCP 2.2. Consult your 4K UltraHD display's user guide to find the correct HDMI port to plug SHIELD into for watching 4K content. SHIELD also supports content rendered with 4:4:4, and 4:2:0 chroma subsampling frequency ratios. (NOTE: Netflix 4K content is currently only enabled for HDCP 2.2 ports. See your 4K UltraHD display's user guide for further details). If one of the HDMI 2.0 ports does not work then try another until you find a port that works.
* Use of an AV Receiver with HDMI for video and Toslink for audio may result in '''audio lagging behind video''', and each of the these type of configurations may add varying levels of delay along the audio and video path resulting in lip-sync issues in the content viewed on the TV. Use the built-in AV sync slider utility (not in Kodi) in the SHIELD menu ''Settings'' > ''HDMI'' > ''AV Sync Tuner'' to calibrate for any audio lag. Adjust the delay on the audio signal until you hear the audio beep from your speakers exactly when the bouncing ball touches the line. The AV sync slider allows you to advance audio by 1 second at most (in small increments of 10ms) to synchronize the audio and video. (Note: This tool is effective only when SHIELD is connected to your AV Receiver over HDMI (i.e. audio/video over HDMI); it is not meant to be used when a headset is plugged into SHIELD controller/SHIELD remote or USB audio device or Bluetooth audio device).
* If '''video lags behind audio''' instead (i.e. audio is ahead of video) then use your AV receiver’s settings to delay audio.
*?

== Known issues and limitations==
Known issues and limitations related to usage of Kodi on NVIDIA SHIELD TV, including limitations in the hardware, firmware, and software directly or indirectly related to and for Kodi usage.
* HDMI-CEC is supposedly supported supported in the hardware and in the Android firmware, but no news yet on API or other interface with [[LibCEC]] for native (direct) Kodi support of the CEC controller.
* Kodi's existing [[Settings/Videos|video setting options]] for "Adjust display refresh rate to match video" and "Sync playback to display" to sync screen refresh rate to playback frame rate option is included in the Kodi 15.x (Isengard) releases, but it is still limited to 24/25/30/50/60 Hz refresh rates in the firmware from Nvidia. Nvidia's Shield Android TV OTA 2.0 Update also added support for for 23.976 and 59.94 Hz but it may not work in Kodi for all setups.
** Automatic refresh rate switching is not working with all televisions brands/models, and on some that do work only do so after the SHIELD have been rebooted/restarted or booted after your television and AV-receiver. Other than waiting for future firmware updates the general advice is to try another HDMI until on your television or AV-receiver you find a port that works (or work better).
* MPEG-2 hardware decoding (and hardware deinterlacing) did not work before NVIDIA SHIELD TV Pro OTA Firmware version 1.2 update, so be sure to update to latest firmware.
* VC-1 and WMV-9 videos are software decoded only so far, reason for this is that NVIDIA have so far only licensed MPEG-2, H.264, HEVC (H.265), and VP9 codecs for video playback, as well as Dolby Digital (DD) and Dolby Digital Plus (DD+) for audio<ref>http://www.legitreviews.com/nvidia-shield-android-tv-review_164223/3 Legit Reviews - NVIDIA SHIELD TV Review</ref>, (and unfortunately NVIDIA do at least not yet offer a add-on license keys for a codec pack similar to Raspberry Pi<ref name="RaspPi Codec License keys">http://www.raspberrypi.com/license-keys/ Raspberry Pi Store - License keys</ref>).<ref name="Requests to NVIDIA for Codec Packs">https://forums.geforce.com/default/topic/836487/shield-android-tv/codec-support-/ GeForce Forums - Requests to Nvidia for Codec Packs</ref> There is however apparently a hack available to enable VC-1 hardware decoding by editing Android file "/system/etc/media_codecs.xml" if you have first rooted the SATV.[http://forum.xda-developers.com/showpost.php?p=61241497&postcount=47]
*HD audio including DTS-HD MA, DTS:X, Dolby True HD, Dolby Atmos can be all be passed-through (bitstreamed) on Nvidia Shieild TV, but this currently only works with the native video player. Pass-through for HD audio is currently not working in Kodi and is a work-in-progress.
* Currently the Shield Android TV does not support Remote Connections, so to connect to the Shield to sideload via ADB it requires a direct connection.
* The Nexus Player remote does not pair at all with the Shield console. It did with the Razer Forge, but not the Shield console.
* VP9 hardware video decode is supposedly supported at to to 4K / 2160p (UltraHD) resolution, such as YouTube source, but not yet confirmed working in Kodi for Android on the NVIDIA Tegra X1 (TX1) SoC.
* VC-1 hardware decoding (possibly including hardware deinterlacing?) is suppose to work since OTA Firmware version 2.0 update from NVIDIA for SHIELD TV, so be sure to update to latest firmware and run tests in Kodi for independent confirmations.
* WMV-9 hardware decoding (possibly including hardware deinterlacing?) is suppose to work since OTA Firmware version 2.0 update from NVIDIA for SHIELD TV, so be sure to update to latest firmware and run tests in Kodi for independent confirmations.
* OTA Firmware version 2.0 update from NVIDIA for SHIELD TV is suppose to have added native playback and output of video content encoded at 23.976 and 59.94 Hz. Also supports since erlier are video content encoded at 24 Hz, 25 Hz, 30 Hz. This however needs testing and confirmation if it works with Kodi's existing [[Settings/Videos|video setting options]] for "Adjust display refresh rate to match video" and "Sync playback to display" to sync screen refresh rate to playback frame rate option is included in the very latest nighty builds. Note though that automatic refresh rate switching will not work with all televisions brands/models or in all HDMI ports.
* OTA Firmware version 3.2 update from NVIDIA for SHIELD TV is suppose to have native pass-through/bit-streaming audio support for AC3, EAC3, Dolby 5.1, Dolby 7.1, DTS-HD, DTS-HD MA, DTS:X, Dolby TrueHD, and Dolby Atmos, up to high resolution 24-bit 192 kHz audio over HDMI and USB. Also added is support for USB-S/PDIF dongles which can enable users to connect SHIELD to older sound bars and audio receivers. All this however needs testing and confirmation if it works with Kodi's very latest nighty builds of Kodi for Android.
* ?

== Random notes ==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}

* ?

==References==
{{reflist}}
* [http://www.anandtech.com/show/9289/the-nvidia-shield-android-tv-review/6 AnandTech - The NVIDIA SHIELD Android TV Review: A Premium 4K Set Top Box]
* [http://www.legitreviews.com/nvidia-shield-android-tv-review_164223/3 Legit Reviews - NVIDIA SHIELD Android TV Review]

== See also ==
* [[Android hardware]]
* [[Android]]

== Links ==
* Kodi forum discussion threads about the NVIDIA SHIELD TV:
**Support and help thread: http://forum.kodi.tv/showthread.php?tid=228158
**General hardware discussion: http://forum.kodi.tv/showthread.php?tid=220297
*Related articles on Wikipedia:
** Wikipedia article on NVIDIA SHIELD TV: [[wikipedia:Nvidia Shield Console]]
** Wikipedia article on Android TV (OS used on NVIDIA SHIELD Console): [[wikipedia:Android TV]]
*Official NVIDIA pages and sites about the SHIELD console:
** NVIDIA SHIELD TV product page: http://shield.nvidia.com/console
***NVIDIA SHIELD Remote Control http://shield.nvidia.com/store/remote
***NVIDIA SHIELD Game Controller http://shield.nvidia.com/store/controller
** NVIDIA SHIELD TV FAQ (Frequently Asked Questions): http://shield.nvidia.com/support/nvidia-android-tv/faq/1
** NVIDIA SHIELD TV User Guide: http://support-shield.nvidia.com/android-tv-user-guide/index.htm#_ga=1.98702110.121900636.1426802792&t=About_SHIELD.htm
** NVIDIA Blog post: http://blogs.nvidia.com/blog/2015/05/28/nvidia-shield-available/
** NVIDIA SHIELD forum for Android TV https://forums.geforce.com/default/board/159/
** NVIDIA SHIELD development tools and other resources for developers: https://developer.nvidia.com/develop4shield
**Tegra Android Development Pack: https://developer.nvidia.com/tegra-android-development-pack
* NVIDIA SHIELD TV Utility App: http://goo.gl/4FiQCT

[[Category:HTPC]]
[[Category:Android]]
[[Category:ARM]]
[[Category:Nvidia SHIELD]]
[[Category:Nvidia Tegra]]

Archive:Chromebox

2015-11-02T13:20:13Z

Rodalpho: /* OS and Kodi Installation */

{{mininav|[[Devices]]|[[x86 hardware]]}}
{{device notice}}

{{Infobox information appliance
| name = Chromebox
| image = [[File:Asus_chromebox.jpg|300px]]
| releasedate = 2014-03-14 (US)
| os = ChromeOS
| cpu = Intel® Celeron 2955U/2957U Intel® Core i3-4010U/4030U Intel® Core i7-4600U
| graphics = Intel® HD Graphics/GT1 (Celeron) Intel® HD Graphics 4400/GT2 (i3/i7)
| storage = 16GB internal SSD (M.2 SATA)
| memory = 2GB/4GB/8GB standard, 16GB max Dual Channel DDR3L-12800
| connectivity = HDMI 1.4a DisplayPort 1.2a Bluetooth 4.0 USB 3.0 (4x) 802.11 abgn/AC wifi 10/100/1000 Ethernet 2 -in-1 Card Reader 3.5mm headphone plug
| 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]]

<section begin="intro" />The Chromebox is an inexpensive small form-factor PC which runs Google's ChromeOS; it is the desktop variant of a Chromebook laptop. Although Kodi does not run natively under ChromeOS, the Chromebox can easily be made to run Linux (or Windows) and {{Kodi}}.<section end="intro" />

This page is a collection of links, information, tips, and guides related to running {{Kodi}} on Chromebox mini PCs.

{{note|This page was originally written for the ASUS ChromeBox, but all of the information is valid for the HP, Acer, and Dell Chromeboxes as well. The hardware is virtually identical: the Acer has a slightly different form factor; the HP model has only 1 dimm slot (vs the 2 the others have); the fan of the HP is also a bit louder than the others (with the Asus being the most quiet); the Dell models have an 802.11 AC wifi module, whereas the others only have 802.11 abgn.}} 

== ChromeBox Overview ==
The Haswell Celeron-based Chromebox is small, lightweight x86-64 PC that natively runs ChromeOS, but with a few simple tweaks, has the capability to run any Linux-based OS (plus Windows 8.1+). It features HDMI and DisplayPort video outputs (which can be used simultaneously), 4x USB 3.0 ports, gigabit Ethernet, an SD card slot, and built-in 802.11a/b/g/n wireless and Bluetooth 4.0.

Capability wise, the ChromeBox fully supports hardware accelerated H.264/MPEG-2/VC-1 video playback at up to 2160p24/p30 (4K), proper 24p output, and full 7.1/HD audio bitstream output. 3D playback is supported (HSBS/HTAB), though the decoding of MVC streams (as used in 3D Blu-ray ISOs) is not supported under Linux at this time; the hardware itself is capable. Hi10 H.264 1080p playback is software decoded, but works well with few exceptions. 2160p60 is available only via DisplayPort with MST (multi-stream transport), as HDMI 1.4a is limited to 2160p30. H.265/HEVC is software (CPU) decoded, so playback is limited to 1080p max and low/moderate bit-rates. From a purely Kodi/media playback standpoint, there's no advantage to the Core i3/i7 models over the Celeron model (outside of 2160p60 video playback, which the i3/i7's HD4400 GPU can handle), although dual channel memory (2 identical capacity modules) provides a decent performance boost in some situations (like playback of 60fps video).

The ChromeBox uses customized open-source firmware components (mainly [http://www.coreboot.org coreboot]) to boot ChromeOS in a secure/verified manner. By putting it in developer mode, we disable the verified boot restriction, and allow the ChromeBox to boot in "legacy mode" (via a legacy boot payload, [http://www.seabios.org SeaBIOS]), which enables other operating systems (eg: OpenELEC, Ubuntu/Kodibuntu) to be installed / dual booted. If ChromeOS isn't needed, then custom firmware can be installed to directly boot the legacy BIOS. A simplified overview of the ChromeBox boot process is shown here (click for full-size):
 
[[File:ChromeBox_boot_process.png|400px]]
 
This wiki page will guide you through the steps necessary to put the ChromeBox into developer mode and set it up in either a dual boot or standalone (non-ChromeOS) configuration. The majority of the process has been automated via the ChromeBox EZ Setup Script, making it safe and easy to run Linux/Kodi on your ChromeBox.

== Device Preparation ==

=== Disable Firmware Write Protect ===

Disabling the firmware write protect will allow us to shorten the timeout on the developer boot screen (from 30s to ~1s) in a dual boot configuration, and optionally boot directly in "legacy mode" (and into Ubuntu or OpenELEC). Disabling the write protect is also necessary for standalone setups so that the stock firmware can be replaced with a custom version.

With the device powered off and unplugged:

# Remove (4) rubber feet from bottom of unit
# Remove (4) screws under rubber feet
# Take off the bottom cover.
#:Tip: Thread two of the screws that you just removed into the VESA mounting holes, and use them to pull/separate bottom cover.
# Remove write-protect screw circled below:
#::Asus/HP/Dell: [[File:Inside-chrome1.jpg|300px]]
#::Acer: [[File:Acer wp screw.png|400px]]
#::  
#:: '''Notes:'''
#:: -- The write-protect screw on the Acer model is under the heat pipe, which needs to be removed to access it. Be sure to smooth out (or replace) the heatsink grease before reinstallation of the heatsink / heat pipe.
#:: -- On some boxes (this is rare, but seems to be most common on the Dells), even after removing the write-protect screw, there is still connectivity between the two semi-circles, in which case you may need to use a small flathead screwdriver (eg) to lightly scrape away the excess material which is causing continuity. You can verify with a DMM.
# Reassemble in reverse order

'''Important:''' The write-protect screw should be left out permanently.
 
 

=== Put in Developer Mode ===

Putting the ChromeBox in developer mode will disable verified boot mode, and allow you to access the underlying Linux operating system features necessary for installing/running Kodi (via OpenELEC/Ubuntu).

'''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
#: [[File:Recoverybutton.png|200px]]
# 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 (vs verified boot mode), and the developer boot screen (shown below) will be displayed at each boot.
 
 
'''Note:''' The recovery button (and booting to recovery mode) are a of function of the stock firmware. If you've flashed a custom firmware on your box (either as part of a standalone setup or otherwise), the recovery button has no function and the ChromeOS recovery mode doesn't exist.
 
 
[[File:ChromeBox_dev_boot.jpg|400px]]

The developer boot screen has a warning about OS verification being off. '''Do not hit [SPACE]''', as it will return the device to verified boot mode. The ChromeBox must remain in developer mode, else you will potentially have to redo the setup from the beginning. The developer mode boot screen has a ~30s timeout, followed by two beeps, before booting. You can skip the delay by pressing [CTRL-D] to immediately boot into ChromeOS.
 
 

=== Perform a Factory Reset ===

A factory reset is not needed for a standalone setup, but must be performed prior to any dual-boot (re)install.

# Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/answer/1080595?hl=en or use the [https://chrome.google.com/webstore/detail/chromebook-recovery-utili/jndclpdbaamdhonoechobihbbiimdgai?hl=en ChromeBook Recovery Utility from the Chrome web store].

Note: Google's recovery tool can be picky about what kind/size of USB/SD media you use. If one USB stick doesn't work, try another.

# 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 - so be sure to reset them back to the 'ChromeOS + 30s default' option '''before''' performing a factory reset. If you forget to do that, you'll need to press [CTRL-D] on the developer boot screen (or before the legacy boot/SeaBIOS boot screen) in order to boot ChromeOS after performing the recovery.
 
 
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:
:*:Asus: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_panther_recovery_stable-channel_mp.bin.zip
:*: HP: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_zako_recovery_stable-channel_mp-v2.bin.zip
:*:Acer: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_mccloud_recovery_stable-channel_mp.bin.zip
:*:Dell: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_tricky_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
 
 
'''Note:''' The recovery media created using Google's recovery tool works only when the ChromeBox is booted into recovery mode, which only exists when using the stock firmware. If you've flashed a custom firmware on your box (either as part of a standalone setup or otherwise), ChromeOS recovery mode doesn't exist, and attempting to boot the recovery media from SeaBIOS will not work.
 
 

== Installation, Configuration, and Updating ==

=== OS and Kodi Installation ===
Kodi can be installed on the ChromeBox in a variety of ways. The two most common are via OpenELEC or Ubuntu+Kodi, in either a standalone or dual boot configuration. This is accomplished via the ChromeBox E-Z Setup script, which must be run (at least initially) from ChromeOS.
 
The EZ setup script will facilitate everything needed to install either a dual boot setup, or install a custom firmware which allows the installation of any Linux-based OS in standalone mode.
 
To run the ChromeBox E-Z Setup script, perform the following steps:

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

:Note: the first command is curl space dash capital-L space dash capital-O space http://goo.gl/3Tfu5W.

Full instructions and a detailed explanation of the script's functions and usage can be found at the following forum thread: http://forum.kodi.tv/showthread.php?tid=194362
 
 
'''Older Kernels:''' If installing a Linux-based OS other than OpenELEC (eg, Ubuntu/Kodibuntu), you will most likely need to manually update the kernel for optimal operation. Kernel version 3.18.4 is the minimum recommended, as it has a fix for an Intel GPU bug that can cause hanging during video playback. Updating the kernel is OS-specific and beyond the scope of this wiki, but instructions are easily found by googling.
 
'''Ubuntu 15.10:''' Ubuntu Wily Werewolf (15.10) ships with Linux kernel 4.2.0, which immediately panics upon boot on Chromeboxes. To fix this, you can run an earlier kernel. Alternatively, if you're able to boot, you can disable ACPI. To do this, add "acpi=off" to the end of the commandline default line in your "/etc/default/grub: file like so:
 
:: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw acpi=off"
This file must be edited as root. Once completed, run "update-grub" as root and reboot. This bug is fixed in Linux kernel 4.3. When it is released, update and remove the acpi=off flag.
 

=== Dual Boot OS Selection ===
When dual booting with ChromeOS and OpenELEC/Ubuntu, due to the ChromeBox's firmware setup, there is no conventional boot menu. Instead, the OS selection is made via keyboard shortcuts on the developer mode boot screen (shown above): [CTRL-D] boots directly ChromeOS; [CTRL-L] boots the legacy BIOS (and whatever secondary OS is installed). The default OS and boot timeout are set using the 'Set Boot Options' feature of the EZ Setup Script.
 
 

=== Updating Kodi ===

==== OpenELEC ====

The Chromebox is, at its core, a standard 64-bit x86 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). Automatic updates won't update from a stable to a beta release, but will update stable->stable, beta->beta, and beta->stable. If the automatic update doesn't work for some reason, or you want to update to a test/nightly/beta/RC build, you can manually update using the instructions on the [http://wiki.openelec.tv/index.php?title=Updating_OpenELEC OpenELEC wiki].
 
 

=== Recommended Settings ===

==== Kodi General ====

* System-->Settings-->System: Settings Level:'''Expert'''
* System-->Settings-->System-->Video Output: Vertical blank sync:'''Let driver decide'''
* System-->Settings-->System-->Power Saving: Shutdown function:'''Suspend''' (sets IR power toggle to suspend)
* System-->Settings-->Videos-->Acceleration: Enable HQ Scalers for scalings above:'''20%'''
* System-->Settings-->Videos-->Acceleration: Use VC-1 VAAPI:'''Selected''' (de-select if you have interlaced VC-1 content)
* System-->Settings-->Videos-->Acceleration: Prefer VAAPI render method:'''Selected'''
 
Also see the video playback settings as shown in the screenshots below. Change as needed, then hit 'Set as default for all videos' to save.
 
 
==== OpenELEC Specific ====

* System-->OpenELEC-->System: Automatic Updates:'''Auto'''
* System-->OpenELEC-->Network: Wireless Networks/Active:'''Selected''' (if using WiFi)
* System-->OpenELEC-->Network: Wait for network before starting Kodi:'''Selected''' (if using a external mysql database)
* System-->OpenELEC-->Services: Enable Bluetooth:'''Selected''' (if using Bluetooth)
 
 

<gallery>
File:chromebox_video_accel_settings_1.png|ChromeBox Settings: Video/Acceleration
File:chromebox_video_playback_settings_1.png|ChromeBox Video Playback Settings (1/2)
File:chromebox_video_playback_settings_2.png|ChromeBox Video Playback Settings (2/2)
</gallery>

=== Switching between Standalone and Dual Boot configurations ===

If you have a dual boot setup and wish to switch to a standalone setup, the steps are no different than installing on a "fresh" system, though you can obviously skip the steps you have already performed (removing the write-protect screw, putting the box in developer mode). If you have an OpenELEC dual boot setup and are switching to an OpenELEC standalone setup, then you can backup your settings etc using the built-in tools, copy to another PC/USB, and restore after performing the standalone setup.

If you have a standalone setup and wish to switch to a dual boot setup, you need to first [[Chromebox#Restoring_the_Stock_Firmware|restore the stock firmware]], then [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], after which you can continue with the dual boot setup.
 
 

== Recommended Accessories / Hardware Upgrades ==
 
For most users, there's no need to upgrade the ChromeBox's RAM or HDD; OpenELEC uses minimal RAM and disk space, and there's no benefit to upgrading. However, users who opt for a full Ubuntu/Kodibuntu setup, and plan on running lots of background processes etc, may find it beneficial to install additional RAM or upgrade to a larger SSD.
 
 
'''RAM:'''
: The ChromeBox has two (2) 204-Pin SODIMM slots (HP models only have one), 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)
:* HP H6Y75AA (4GB, 1.35v)
: 
: 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 2242 M.2 SATA SSD (22mm x 42mm); stock is a 16GB unit (usually Sandisk or Kensington). Any M.2 SATA 2242 replacement drive should work without issue.
 
'''Remote Controls:'''
: The ChromeBox does not have a built-in IR sensor, and must therefore use a USB IR receiver (or a Bluetooth remote). In general, any remote/receiver listed on the Kodi wiki as fully working under Linux should be fine, though some have issues when connected to USB3 ports. 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)
:* Sony IR receiver model PCVA-IR8U (MCE/eHome)
:* HP IR remote/receiver kit [http://www.amazon.com/dp/B00AYE6JDO/ OVU400102/71] (MCE/eHome, includes 5187-4593 receiver)
:* Ortek IR remote/receiver kit [http://www.amazon.com/dp/B00224ZDFY/ VRC-1100] (MCE clone, receiver also works well w/Logitech Harmony remotes)
:* Rosewill RHRC-11002 remote (MCE clone, includes receiver model IR605)
:* Rosewill WMC RRC-127 remote/receiver
:* Microsoft XBOX 360 IR remote (with MCE/eHome receiver or Flirc)
:* Microsoft XBOX One IR remote (with MCE/eHome receiver or Flirc)
:* Logitech Harmony remotes (programmed as Microsoft Media Center Extender - not as a keyboard - with MCE/eHome receiver; not recommended for use with a Flirc)
:* Sony Playstation 3 (PS3) Bluetooth remote (works with built-in BT receiver)
:*: press/hold START + ENTER to pair, choose 'Trust and Connect', then hit Ok and Enable Standby after connecting
:* Logitech Harmony Smart Hub (via Bluetooth, works with built-in BT receiver, [http://forum.kodi.tv/showthread.php?tid=194362&pid=1843165#pid1843165 see forum post here])
:* Measy RC11 Android Monitor Wireless Keyboard Air Mouse Remote Controller With Gyroscope (cannot wake up Chromebox but works otherwise nicely, with keys as well as with mouse pointer at both OpenELEC and ChromeOS)
:* Amazon FireTV / Fire Stick remotes (Bluetooth)
:NOTE: If you need to re-map remote buttons, you can use the [[Add-on:Keymap Editor|Keymap Editor Add-on]] to do so.

:'''Currently non-working''':
:* HP IR receiver model 5070-2584 (MCE/eHome)
:* AVS Gear HA-IR01SV (MCE/eHome)
:* All Topseed manufactured MCE IR receivers
 
'''USB Audio Devices''':
:As the ChromeBox only has HDMI and analog audio outputs, if you need SPDIF, then either a converter or external/USB device must be used. The following devices have been tested/confirmed working:
:* [http://www.amazon.com/gp/product/B0036VO4X4/ Turtle Beach Audio Advantage Micro II ] (plug/play in both OpenELEC and Win8.1)
:* ASUS Xonar U3 USB (OpenELEC: requires un-muting the SPDIF line, see [http://openelec.tv/forum/41-supported-hardware/71023-asus-xonar-u3-usb-soundcard this forum post])
 
'''HDMI-CEC''':
:The ChromeBox does not support HDMI-CEC natively, but support can be added using an [http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx external USB CEC adapter] from Pulse-Eight. The USB CEC Adapter needs power to the USB port BEFORE there is any video out, or it simply will not pass through any video signal. There are several ways to work around this:

:* Either always leave your Chromebox on, or just put it into standby; never turn it off
:* Use an externally powered source (eg, USB hub, TV set) to power the adapter (rather than the ChromeBox itself), so it always has power
:* If you have a spare HDMI port, you actually can split video in and control in for one HDMI channel using two physical HDMI ports. The video will be connected to the main port, and that's the port you use in the HDMI config settings in {{Kodi}}, and then you simply connect the USB CEC adapter to a spare HDMI port, does not appear to matter which.
 
 

== Troubleshooting, Known Issues, Fixes/Workarounds ==

Installation, Dual Booting, USB booting:
:* 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 Kodi on a ChromeBox, or to select between OSes in a dual boot setup. The Logitech K400 is one of these, so use another keyboard to install if yours doesn't appear to be working. Most Bluetooth keyboards '''will not work''' due to the fact that they require the OS to be loaded in order to reconnect to the ChromeBox.
:*: An effort is underway on the forums to catalog which keyboards work (and which do not); the thread (which is being updated regularly) can be found here: http://forum.kodi.tv/showthread.php?tid=211797
:* Help! I'm stuck on the black SeaBIOS boot screen, with the "booting from hard disk" text displayed (and possibly a bunch of nonsensical text afterwards).
:*:This happens because SeaBIOS is trying to boot from the internal hard drive, but no bootable OS (or only ChromeOS) is installed.
::* If you have a dual boot setup, 99% of the time this is due to not having performed a factory reset prior to running the EZ Setup Script, [[Chromebox#Perform_a_Factory_Reset|as listed in the Device Prep section above]]. Simply perform the factory reset, then redo the dual boot setup using the script as before.
::* If you have a standalone setup, and are trying to boot from USB:
::*: If you see the 'Press ESC for boot menu' text but pressing it doesn't work, then the issue is your keyboard, so try using a different one.
::*: If you '''don't''' see the 'Press ESC for boot menu' text, then the issue is with your boot media, so try using a different USB flash drive.
:* Ok, I have an OS installed, but I can't boot from USB - it boots too fast!
:*: This means your USB boot media isn't being recognized, otherwise you would have 5s to press ESC and bring up the boot menu. Re-create your boot media, possibly using a different USB stick. If you're trying to boot a Linux ISO, write the ISO directly to USB (using Win32DiskImager or dd), don't use a tool like unetbootin (eg).
:* If you're getting an error similar to "It appears your computer only has 639K of low ("DOS") RAM.", then you're pressing the dual boot selection keys (CTRL-D/CTRL-L) too late in the boot sequence - they need to be pressed on the developer mode boot screen, before it boots either ChromeOS or the Legacy BIOS (SeaBIOS). On some displays, this may mean pressing them before the display comes on, particularly if you've set the boot delay to 1s.
:* If the install media created by the script doesn't work (or you forget to create it before rebooting), then you can simply download the latest stable version (or beta/RC if you'd like) from [http://openelec.tv/get-openelec OpenELEC's website here]. The ChromeBox runs the Generic 64-bit version of OpenELEC, and it's recommended that you download the diskimage version, and create the install media, as per the instructions [http://wiki.openelec.tv/index.php/HOW-TO:Installing_OpenELEC/Creating_The_Install_Key#tab=DiskImage on the OpenELEC wiki].
:* Some TVs/displays are not able to show the developer boot screen due to the resolution it uses (1024x768 @ 60Hz), in which case you'll need to use a different display to complete the initial setup steps.
:* Many TVs have overscan enabled by default, which will cut off the text display of the ChromeOS shell. Be sure to set your TV to a mode which does not overscan (varies by manufacturer - often called 'just scan', 'exact' 'pixel perfect'; some TVs require you to label the input as a PC).
:* Using a '''passive''' DisplayPort-->HDMI cable/adapter is often problematic, and can cause the video output drop out after booting. Use either a straight DP cable or straight HDMI/HDMI-->DVI cable; if you have to use a DisplayPort-->HDMI adapter, be sure it is the '''active''' type.

Color Range Selection:
:* This topic is a bit of a minefield, but [http://forum.kodi.tv/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 Kodi option 'Used limited color range' under Settings-->System-->Video Output. Use the video clip and image above as a guide.
:*: '''Note:''' If you want to output Limited color range, you are required to do the following setting as well: Settings-->Video-->Acceleration-->Prefer VAAPI Rendering: disabled/de-selected.

No Audio and/or corrupted video on Wakeup from Suspend:
:* Some displays/AVRs don't successfully handshake when resuming from suspend, leading to no audio output and/or corrupted video output until the Chromebox is rebooted.
:*: Solution: If using a universal remote, such as a Harmony, ensure that you are turning off (suspending) the ChromeBox '''before''' your AVR/TV, and turning it on (resuming) '''after''' the AVR/TV.
:*: Solution: download/enable a script that will force the ChromeBox to reset the audio/video output on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
:*::<nowiki>mkdir -p /storage/.config/sleep.d</nowiki>
:*::<nowiki>cd /storage/.config/sleep.d</nowiki>
:*::<nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/01-cbox_resume.power</nowiki>
:*::<nowiki>chmod +x 01-cbox_resume.power</nowiki>
:*: Then reboot the ChromeBox
:*: Note: If connected via the DisplayPort output, use a text editor (eg, nano) to edit the script and replace references to 'HDMI1' with 'DP1'.

High/Full fan speed on Wakeup from Suspend:
:* A change in the Linux kernel ACPI system results in the fan speed being set to high for at least 10s on resume from suspend; sometimes a reboot is required to return to normal speed.
:*: Workaroound: download/enable a script that will force the ChromeBox's fan speed back to normal on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
:*::<nowiki>mkdir -p /storage/.config/sleep.d</nowiki>
:*::<nowiki>cd /storage/.config/sleep.d</nowiki>
:*::<nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/02-cbox_resume.power</nowiki>
:*::<nowiki>chmod +x 02-cbox_resume.power</nowiki>
:*: Then reboot the ChromeBox

Video Playback:
:* An Intel Linux video driver bug causes intermittent freezes where the video locks up but audio keeps playing.
:*: Solution: This issue is fixed as of OpenELEC 5.0.0; users running a different Linux distro should be sure to update their kernel to 3.18.4 or 3.19.0 (or newer).

On Screen Display:
:* Some OpenELEC 6 users have reported problems with On Screen Display elements not refreshing properly. Changing System -> Settings -> System -> Video Output -> Vertical Blank Sync -> Let Driver Choose will fix the problem.

Remote Controls:
:* Most MCE IR receivers work properly now when connected to USB3 ports under Linux with kernel 3.16+ (older kernels will require a patch/fix); OpenELEC 4.0+ is fully up to date. The version of Ubuntu installed by the ChromeBox EZ setup script in a dual boot setup also includes an up-to-date kernel. However, some buggy MCE receivers still do not work properly (at all), as noted below in the Hardware/Remotes section.

:: For standalone Ubuntu (or any other distro) installs, you will need to update to a 3.16 (or later) kernel.

Unreliable Wireless Devices attached to USB 3.0 ports:
:* Use a USB extension cable to move the device as far away from the USB port as possible. USB 3.0 can cause wireless interference. [http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-interference-paper.html Intel has released a whitepaper documenting the issue.]

Power Management:
:* Suspend/resume is generally problematic with the stock firmware (dual boot setups - OpenELEC will reboot on resume), but works reliably in standalone setups running the coreboot firmware. Resume via IR remote (USB) and wake-on-lan (eg, via YATSE) work perfectly well.
:* Note: WOL only works when the ChromeBox is suspended, not fully powered off, and requires the MAC address of the box to be set (eg, in YATSE)

Windows 8/8.1/10:
:* (Updated 2015/06/08) HDMI audio works, but requires specific drivers (Intel HD graphics 9.18.10.3220 and Intel Display Audio 6.16.0.3112), otherwise HDMI audi is non-functional.
:*: Drivers are mirrored here for your convenience:
:*: [https://dl.dropboxusercontent.com/u/98309225/haswell_driver_vga_32bit.exe Windows 8/8.1/10 32-bit]
:*: [https://dl.dropboxusercontent.com/u/98309225/haswell_driver_vga_64bit.exe Windows 8/8.1/10 64-bit]
:* Bluray disc playback doesn't work, as PowerDVD and WinDVD report that the video drivers are not supported, even though they report the hardware is capable.
:* The CPU fan will shut down at boot and not come back on unless a utility like SpeedFan is used to start it. After manually starting the fan (set PWM1 to 50%), set Speedfan for automatic control and then create a shortcut for it to run at startup.
:* Windows 7 doesn't install/work, so don't ask for help with it.
:* Discussion of running Windows on a ChromeBox can be found on this forum thread: http://forum.kodi.tv/showthread.php?tid=203040

Linux Video Tearing:
:* Some users may experience screen tearing under the Linux desktop, or when watching video (e.g., Netflix). The fix for this is [https://wiki.archlinux.org/index.php/Intel_Graphics#Tear-free_video documented on the Arch Wiki], and copied here for convenience.

:: from a terminal/shell prompt:
:::<nowiki>sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf</nowiki>

:: copy/paste the following:

:::<nowiki>Section "Device"</nowiki>
::::<nowiki>Identifier "Intel Graphics"</nowiki>
::::<nowiki>Driver "intel"</nowiki>
::::<nowiki>Option "TearFree" "true"</nowiki>
:::<nowiki>EndSection</nowiki>

:: then save, exit, and reboot.

High CPU at Idle:
:* When running a Linux setup, there is high idle CPU usage with some older kernels which do not fully support the Haswell platform; be sure to update to the latest kernel available (at '''least''' 3.18.4). On some (mostly dual boot) setups, it may also be necessary to add the following kernel boot parameters to disable the TPM: tpm_tis.force=1 tpm_tis.interrupts=0

OpenELEC Fails to boot:
:* If the OS isn't shutdown cleanly, sometimes a filesystem check (fsck) will be automatically performed. In some cases, the automatic repair is unsuccessful, and an error will show:
::<nowiki>***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***</nowiki> 
::<nowiki>### Starting debugging shell... type exit to quit ###</nowiki> 
::<nowiki>sh: can't access tty; job control turned off</nowiki> 
::<nowiki>#_</nowiki> 
 
In this case, simply run fsck manually as instructed, using the following commands, hitting [enter] after each: 
 
For a standalone setup:
:<nowiki>fsck /dev/sda1</nowiki> 
:<nowiki>fsck /dev/sda2</nowiki> 
 
For a dual-boot setup:
:<nowiki>fsck /dev/sda6</nowiki> 
:<nowiki>fsck /dev/sda7</nowiki> 
 
After the fsck is run, type 'reboot' then hit [enter] and the system should boot normally.
 
 

== Firmware/BIOS Updating ==

As depicted in the overview section above, the ChromeBox's firmware consists of two main parts: the main firmware (coreboot), and the Legacy BIOS payload (SeaBIOS). Users running a dual-boot configuration only need to update the Legacy BIOS portion. Users running a standalone setup should update the custom coreboot firmware only, as it contains an updated SeaBIOS payload (which can not be updated separately).

'''NOTE''': Under normal conditions, the ChromeBox's firmware does not need to be updated after the initial install/update via the EZ Setup Script. As the old saying goes: if it ain't broke, don't fix it. Only update if you are having an issue that is specifically noted in the changelog as being addressed by a newer version.

Dual-boot users should simply boot to ChromeOS and re-download/re-run the EZ Setup Script, choosing the '''Update Legacy BIOS''' option under the Dual Boot heading.

Standalone users should also re-download/re-run the setup script, but instead choosing the '''coreboot firmware install/update''' option under the Standalone heading. As of v3.0, the script can be run under any version of Linux with a full bash shell. As OpenELEC does not have a full bash shell, OE users will need to use the (separate) standalone firmware update script, as described near the end of [http://forum.kodi.tv/showthread.php?tid=194362 the EZ Setup Script forum post].
 
 

== Resetting to Stock ==

If you have a dual boot setup, simply [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], then hit [space] on the developer mode boot screen to revert to verified boot mode. Done. (Note: be sure to use the Kodi EZ Setup Script to reset the boot options to default before doing this, or you may not be able to exit developer mode)
 
 
If you have standalone setup, it is necessary to restore the stock firmware before performing a factory reset to reload ChromeOS.
 
In order to do this, you will need to download/run the ChromeOS device Firmware Utility script and select the appropriate option from the menu. The script will give you the option to restore from either a backup file from USB (which you created before originally flashing the custom coreboot firmware) or from a generic copy extracted from Google's recovery image. Like the Kodi EZ Setup Script, this script must be run from a Linux terminal with a full bash shell; OpenELEC users will need to boot a Linux Live USB ([http://www.ubuntu.com/download/desktop Ubuntu 14.04.2 64-bit] works fine) from which to run the script. Just download the ISO of and write it to USB using Win32DiskImager (from Windows) or dd (Linux/MacOS).
 
 

* Boot the Linux live USB, then open a terminal/shell window
* Download and run the ChromeOS device Firmware Utility script using the following two commands (hit enter after typing each command):
*: <nowiki>curl -L -O https://goo.gl/1hFfO3</nowiki>
*: <nowiki>sudo bash 1hFfO3 </nowiki>

* Select option 3, Restore Stock Firmware
* Choose whether to restore from a backup file on USB or not
*: If not, select your ChromeBox model so the appropriate firmware can be downloaded
 
After restoring the stock firmware, reboot, and proceed to [[ASUS_Chromebox#Perform_a_Factory_Reset|Perform_a_Factory_Reset]] above to restore/reload ChromeOS.
 
 

==External Links==
* [http://en.wikipedia.org/wiki/Chromebox Chromebox wikipedia article]
* [https://www.google.com/work/chrome/ Google's "Chrome for Work" web page]

{{Helix updated}}

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

Archive:Chromebox

2015-11-02T13:19:16Z

Rodalpho: /* OS and Kodi Installation */

{{mininav|[[Devices]]|[[x86 hardware]]}}
{{device notice}}

{{Infobox information appliance
| name = Chromebox
| image = [[File:Asus_chromebox.jpg|300px]]
| releasedate = 2014-03-14 (US)
| os = ChromeOS
| cpu = Intel® Celeron 2955U/2957U Intel® Core i3-4010U/4030U Intel® Core i7-4600U
| graphics = Intel® HD Graphics/GT1 (Celeron) Intel® HD Graphics 4400/GT2 (i3/i7)
| storage = 16GB internal SSD (M.2 SATA)
| memory = 2GB/4GB/8GB standard, 16GB max Dual Channel DDR3L-12800
| connectivity = HDMI 1.4a DisplayPort 1.2a Bluetooth 4.0 USB 3.0 (4x) 802.11 abgn/AC wifi 10/100/1000 Ethernet 2 -in-1 Card Reader 3.5mm headphone plug
| 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]]

<section begin="intro" />The Chromebox is an inexpensive small form-factor PC which runs Google's ChromeOS; it is the desktop variant of a Chromebook laptop. Although Kodi does not run natively under ChromeOS, the Chromebox can easily be made to run Linux (or Windows) and {{Kodi}}.<section end="intro" />

This page is a collection of links, information, tips, and guides related to running {{Kodi}} on Chromebox mini PCs.

{{note|This page was originally written for the ASUS ChromeBox, but all of the information is valid for the HP, Acer, and Dell Chromeboxes as well. The hardware is virtually identical: the Acer has a slightly different form factor; the HP model has only 1 dimm slot (vs the 2 the others have); the fan of the HP is also a bit louder than the others (with the Asus being the most quiet); the Dell models have an 802.11 AC wifi module, whereas the others only have 802.11 abgn.}} 

== ChromeBox Overview ==
The Haswell Celeron-based Chromebox is small, lightweight x86-64 PC that natively runs ChromeOS, but with a few simple tweaks, has the capability to run any Linux-based OS (plus Windows 8.1+). It features HDMI and DisplayPort video outputs (which can be used simultaneously), 4x USB 3.0 ports, gigabit Ethernet, an SD card slot, and built-in 802.11a/b/g/n wireless and Bluetooth 4.0.

Capability wise, the ChromeBox fully supports hardware accelerated H.264/MPEG-2/VC-1 video playback at up to 2160p24/p30 (4K), proper 24p output, and full 7.1/HD audio bitstream output. 3D playback is supported (HSBS/HTAB), though the decoding of MVC streams (as used in 3D Blu-ray ISOs) is not supported under Linux at this time; the hardware itself is capable. Hi10 H.264 1080p playback is software decoded, but works well with few exceptions. 2160p60 is available only via DisplayPort with MST (multi-stream transport), as HDMI 1.4a is limited to 2160p30. H.265/HEVC is software (CPU) decoded, so playback is limited to 1080p max and low/moderate bit-rates. From a purely Kodi/media playback standpoint, there's no advantage to the Core i3/i7 models over the Celeron model (outside of 2160p60 video playback, which the i3/i7's HD4400 GPU can handle), although dual channel memory (2 identical capacity modules) provides a decent performance boost in some situations (like playback of 60fps video).

The ChromeBox uses customized open-source firmware components (mainly [http://www.coreboot.org coreboot]) to boot ChromeOS in a secure/verified manner. By putting it in developer mode, we disable the verified boot restriction, and allow the ChromeBox to boot in "legacy mode" (via a legacy boot payload, [http://www.seabios.org SeaBIOS]), which enables other operating systems (eg: OpenELEC, Ubuntu/Kodibuntu) to be installed / dual booted. If ChromeOS isn't needed, then custom firmware can be installed to directly boot the legacy BIOS. A simplified overview of the ChromeBox boot process is shown here (click for full-size):
 
[[File:ChromeBox_boot_process.png|400px]]
 
This wiki page will guide you through the steps necessary to put the ChromeBox into developer mode and set it up in either a dual boot or standalone (non-ChromeOS) configuration. The majority of the process has been automated via the ChromeBox EZ Setup Script, making it safe and easy to run Linux/Kodi on your ChromeBox.

== Device Preparation ==

=== Disable Firmware Write Protect ===

Disabling the firmware write protect will allow us to shorten the timeout on the developer boot screen (from 30s to ~1s) in a dual boot configuration, and optionally boot directly in "legacy mode" (and into Ubuntu or OpenELEC). Disabling the write protect is also necessary for standalone setups so that the stock firmware can be replaced with a custom version.

With the device powered off and unplugged:

# Remove (4) rubber feet from bottom of unit
# Remove (4) screws under rubber feet
# Take off the bottom cover.
#:Tip: Thread two of the screws that you just removed into the VESA mounting holes, and use them to pull/separate bottom cover.
# Remove write-protect screw circled below:
#::Asus/HP/Dell: [[File:Inside-chrome1.jpg|300px]]
#::Acer: [[File:Acer wp screw.png|400px]]
#::  
#:: '''Notes:'''
#:: -- The write-protect screw on the Acer model is under the heat pipe, which needs to be removed to access it. Be sure to smooth out (or replace) the heatsink grease before reinstallation of the heatsink / heat pipe.
#:: -- On some boxes (this is rare, but seems to be most common on the Dells), even after removing the write-protect screw, there is still connectivity between the two semi-circles, in which case you may need to use a small flathead screwdriver (eg) to lightly scrape away the excess material which is causing continuity. You can verify with a DMM.
# Reassemble in reverse order

'''Important:''' The write-protect screw should be left out permanently.
 
 

=== Put in Developer Mode ===

Putting the ChromeBox in developer mode will disable verified boot mode, and allow you to access the underlying Linux operating system features necessary for installing/running Kodi (via OpenELEC/Ubuntu).

'''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
#: [[File:Recoverybutton.png|200px]]
# 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 (vs verified boot mode), and the developer boot screen (shown below) will be displayed at each boot.
 
 
'''Note:''' The recovery button (and booting to recovery mode) are a of function of the stock firmware. If you've flashed a custom firmware on your box (either as part of a standalone setup or otherwise), the recovery button has no function and the ChromeOS recovery mode doesn't exist.
 
 
[[File:ChromeBox_dev_boot.jpg|400px]]

The developer boot screen has a warning about OS verification being off. '''Do not hit [SPACE]''', as it will return the device to verified boot mode. The ChromeBox must remain in developer mode, else you will potentially have to redo the setup from the beginning. The developer mode boot screen has a ~30s timeout, followed by two beeps, before booting. You can skip the delay by pressing [CTRL-D] to immediately boot into ChromeOS.
 
 

=== Perform a Factory Reset ===

A factory reset is not needed for a standalone setup, but must be performed prior to any dual-boot (re)install.

# Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/answer/1080595?hl=en or use the [https://chrome.google.com/webstore/detail/chromebook-recovery-utili/jndclpdbaamdhonoechobihbbiimdgai?hl=en ChromeBook Recovery Utility from the Chrome web store].

Note: Google's recovery tool can be picky about what kind/size of USB/SD media you use. If one USB stick doesn't work, try another.

# 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 - so be sure to reset them back to the 'ChromeOS + 30s default' option '''before''' performing a factory reset. If you forget to do that, you'll need to press [CTRL-D] on the developer boot screen (or before the legacy boot/SeaBIOS boot screen) in order to boot ChromeOS after performing the recovery.
 
 
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:
:*:Asus: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_panther_recovery_stable-channel_mp.bin.zip
:*: HP: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_zako_recovery_stable-channel_mp-v2.bin.zip
:*:Acer: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_mccloud_recovery_stable-channel_mp.bin.zip
:*:Dell: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_tricky_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
 
 
'''Note:''' The recovery media created using Google's recovery tool works only when the ChromeBox is booted into recovery mode, which only exists when using the stock firmware. If you've flashed a custom firmware on your box (either as part of a standalone setup or otherwise), ChromeOS recovery mode doesn't exist, and attempting to boot the recovery media from SeaBIOS will not work.
 
 

== Installation, Configuration, and Updating ==

=== OS and Kodi Installation ===
Kodi can be installed on the ChromeBox in a variety of ways. The two most common are via OpenELEC or Ubuntu+Kodi, in either a standalone or dual boot configuration. This is accomplished via the ChromeBox E-Z Setup script, which must be run (at least initially) from ChromeOS.
 
The EZ setup script will facilitate everything needed to install either a dual boot setup, or install a custom firmware which allows the installation of any Linux-based OS in standalone mode.
 
To run the ChromeBox E-Z Setup script, perform the following steps:

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

:Note: the first command is curl space dash capital-L space dash capital-O space http://goo.gl/3Tfu5W.

Full instructions and a detailed explanation of the script's functions and usage can be found at the following forum thread: http://forum.kodi.tv/showthread.php?tid=194362
 
 
'''Older Kernels:''' If installing a Linux-based OS other than OpenELEC (eg, Ubuntu/Kodibuntu), you will most likely need to manually update the kernel for optimal operation. Kernel version 3.18.4 is the minimum recommended, as it has a fix for an Intel GPU bug that can cause hanging during video playback. Updating the kernel is OS-specific and beyond the scope of this wiki, but instructions are easily found by googling.
 
'''Ubuntu 15.10:''' Ubuntu Wily Werewolf (15.10) ships with Linux kernel 4.2.0, which immediately panics upon boot on Chromeboxes. To fix this, you can run an earlier kernel. Alternatively, if you're able to boot, you can disable ACPI. To do this, add "acpi=off" to the end of the commandline default line in your "/etc/default/grub: file like so:
 
:: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw acpi=off"
This bug is fixed in Linux kernel 4.3. When it is released, update and remove the acpi=off flag.
 

=== Dual Boot OS Selection ===
When dual booting with ChromeOS and OpenELEC/Ubuntu, due to the ChromeBox's firmware setup, there is no conventional boot menu. Instead, the OS selection is made via keyboard shortcuts on the developer mode boot screen (shown above): [CTRL-D] boots directly ChromeOS; [CTRL-L] boots the legacy BIOS (and whatever secondary OS is installed). The default OS and boot timeout are set using the 'Set Boot Options' feature of the EZ Setup Script.
 
 

=== Updating Kodi ===

==== OpenELEC ====

The Chromebox is, at its core, a standard 64-bit x86 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). Automatic updates won't update from a stable to a beta release, but will update stable->stable, beta->beta, and beta->stable. If the automatic update doesn't work for some reason, or you want to update to a test/nightly/beta/RC build, you can manually update using the instructions on the [http://wiki.openelec.tv/index.php?title=Updating_OpenELEC OpenELEC wiki].
 
 

=== Recommended Settings ===

==== Kodi General ====

* System-->Settings-->System: Settings Level:'''Expert'''
* System-->Settings-->System-->Video Output: Vertical blank sync:'''Let driver decide'''
* System-->Settings-->System-->Power Saving: Shutdown function:'''Suspend''' (sets IR power toggle to suspend)
* System-->Settings-->Videos-->Acceleration: Enable HQ Scalers for scalings above:'''20%'''
* System-->Settings-->Videos-->Acceleration: Use VC-1 VAAPI:'''Selected''' (de-select if you have interlaced VC-1 content)
* System-->Settings-->Videos-->Acceleration: Prefer VAAPI render method:'''Selected'''
 
Also see the video playback settings as shown in the screenshots below. Change as needed, then hit 'Set as default for all videos' to save.
 
 
==== OpenELEC Specific ====

* System-->OpenELEC-->System: Automatic Updates:'''Auto'''
* System-->OpenELEC-->Network: Wireless Networks/Active:'''Selected''' (if using WiFi)
* System-->OpenELEC-->Network: Wait for network before starting Kodi:'''Selected''' (if using a external mysql database)
* System-->OpenELEC-->Services: Enable Bluetooth:'''Selected''' (if using Bluetooth)
 
 

<gallery>
File:chromebox_video_accel_settings_1.png|ChromeBox Settings: Video/Acceleration
File:chromebox_video_playback_settings_1.png|ChromeBox Video Playback Settings (1/2)
File:chromebox_video_playback_settings_2.png|ChromeBox Video Playback Settings (2/2)
</gallery>

=== Switching between Standalone and Dual Boot configurations ===

If you have a dual boot setup and wish to switch to a standalone setup, the steps are no different than installing on a "fresh" system, though you can obviously skip the steps you have already performed (removing the write-protect screw, putting the box in developer mode). If you have an OpenELEC dual boot setup and are switching to an OpenELEC standalone setup, then you can backup your settings etc using the built-in tools, copy to another PC/USB, and restore after performing the standalone setup.

If you have a standalone setup and wish to switch to a dual boot setup, you need to first [[Chromebox#Restoring_the_Stock_Firmware|restore the stock firmware]], then [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], after which you can continue with the dual boot setup.
 
 

== Recommended Accessories / Hardware Upgrades ==
 
For most users, there's no need to upgrade the ChromeBox's RAM or HDD; OpenELEC uses minimal RAM and disk space, and there's no benefit to upgrading. However, users who opt for a full Ubuntu/Kodibuntu setup, and plan on running lots of background processes etc, may find it beneficial to install additional RAM or upgrade to a larger SSD.
 
 
'''RAM:'''
: The ChromeBox has two (2) 204-Pin SODIMM slots (HP models only have one), 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)
:* HP H6Y75AA (4GB, 1.35v)
: 
: 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 2242 M.2 SATA SSD (22mm x 42mm); stock is a 16GB unit (usually Sandisk or Kensington). Any M.2 SATA 2242 replacement drive should work without issue.
 
'''Remote Controls:'''
: The ChromeBox does not have a built-in IR sensor, and must therefore use a USB IR receiver (or a Bluetooth remote). In general, any remote/receiver listed on the Kodi wiki as fully working under Linux should be fine, though some have issues when connected to USB3 ports. 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)
:* Sony IR receiver model PCVA-IR8U (MCE/eHome)
:* HP IR remote/receiver kit [http://www.amazon.com/dp/B00AYE6JDO/ OVU400102/71] (MCE/eHome, includes 5187-4593 receiver)
:* Ortek IR remote/receiver kit [http://www.amazon.com/dp/B00224ZDFY/ VRC-1100] (MCE clone, receiver also works well w/Logitech Harmony remotes)
:* Rosewill RHRC-11002 remote (MCE clone, includes receiver model IR605)
:* Rosewill WMC RRC-127 remote/receiver
:* Microsoft XBOX 360 IR remote (with MCE/eHome receiver or Flirc)
:* Microsoft XBOX One IR remote (with MCE/eHome receiver or Flirc)
:* Logitech Harmony remotes (programmed as Microsoft Media Center Extender - not as a keyboard - with MCE/eHome receiver; not recommended for use with a Flirc)
:* Sony Playstation 3 (PS3) Bluetooth remote (works with built-in BT receiver)
:*: press/hold START + ENTER to pair, choose 'Trust and Connect', then hit Ok and Enable Standby after connecting
:* Logitech Harmony Smart Hub (via Bluetooth, works with built-in BT receiver, [http://forum.kodi.tv/showthread.php?tid=194362&pid=1843165#pid1843165 see forum post here])
:* Measy RC11 Android Monitor Wireless Keyboard Air Mouse Remote Controller With Gyroscope (cannot wake up Chromebox but works otherwise nicely, with keys as well as with mouse pointer at both OpenELEC and ChromeOS)
:* Amazon FireTV / Fire Stick remotes (Bluetooth)
:NOTE: If you need to re-map remote buttons, you can use the [[Add-on:Keymap Editor|Keymap Editor Add-on]] to do so.

:'''Currently non-working''':
:* HP IR receiver model 5070-2584 (MCE/eHome)
:* AVS Gear HA-IR01SV (MCE/eHome)
:* All Topseed manufactured MCE IR receivers
 
'''USB Audio Devices''':
:As the ChromeBox only has HDMI and analog audio outputs, if you need SPDIF, then either a converter or external/USB device must be used. The following devices have been tested/confirmed working:
:* [http://www.amazon.com/gp/product/B0036VO4X4/ Turtle Beach Audio Advantage Micro II ] (plug/play in both OpenELEC and Win8.1)
:* ASUS Xonar U3 USB (OpenELEC: requires un-muting the SPDIF line, see [http://openelec.tv/forum/41-supported-hardware/71023-asus-xonar-u3-usb-soundcard this forum post])
 
'''HDMI-CEC''':
:The ChromeBox does not support HDMI-CEC natively, but support can be added using an [http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx external USB CEC adapter] from Pulse-Eight. The USB CEC Adapter needs power to the USB port BEFORE there is any video out, or it simply will not pass through any video signal. There are several ways to work around this:

:* Either always leave your Chromebox on, or just put it into standby; never turn it off
:* Use an externally powered source (eg, USB hub, TV set) to power the adapter (rather than the ChromeBox itself), so it always has power
:* If you have a spare HDMI port, you actually can split video in and control in for one HDMI channel using two physical HDMI ports. The video will be connected to the main port, and that's the port you use in the HDMI config settings in {{Kodi}}, and then you simply connect the USB CEC adapter to a spare HDMI port, does not appear to matter which.
 
 

== Troubleshooting, Known Issues, Fixes/Workarounds ==

Installation, Dual Booting, USB booting:
:* 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 Kodi on a ChromeBox, or to select between OSes in a dual boot setup. The Logitech K400 is one of these, so use another keyboard to install if yours doesn't appear to be working. Most Bluetooth keyboards '''will not work''' due to the fact that they require the OS to be loaded in order to reconnect to the ChromeBox.
:*: An effort is underway on the forums to catalog which keyboards work (and which do not); the thread (which is being updated regularly) can be found here: http://forum.kodi.tv/showthread.php?tid=211797
:* Help! I'm stuck on the black SeaBIOS boot screen, with the "booting from hard disk" text displayed (and possibly a bunch of nonsensical text afterwards).
:*:This happens because SeaBIOS is trying to boot from the internal hard drive, but no bootable OS (or only ChromeOS) is installed.
::* If you have a dual boot setup, 99% of the time this is due to not having performed a factory reset prior to running the EZ Setup Script, [[Chromebox#Perform_a_Factory_Reset|as listed in the Device Prep section above]]. Simply perform the factory reset, then redo the dual boot setup using the script as before.
::* If you have a standalone setup, and are trying to boot from USB:
::*: If you see the 'Press ESC for boot menu' text but pressing it doesn't work, then the issue is your keyboard, so try using a different one.
::*: If you '''don't''' see the 'Press ESC for boot menu' text, then the issue is with your boot media, so try using a different USB flash drive.
:* Ok, I have an OS installed, but I can't boot from USB - it boots too fast!
:*: This means your USB boot media isn't being recognized, otherwise you would have 5s to press ESC and bring up the boot menu. Re-create your boot media, possibly using a different USB stick. If you're trying to boot a Linux ISO, write the ISO directly to USB (using Win32DiskImager or dd), don't use a tool like unetbootin (eg).
:* If you're getting an error similar to "It appears your computer only has 639K of low ("DOS") RAM.", then you're pressing the dual boot selection keys (CTRL-D/CTRL-L) too late in the boot sequence - they need to be pressed on the developer mode boot screen, before it boots either ChromeOS or the Legacy BIOS (SeaBIOS). On some displays, this may mean pressing them before the display comes on, particularly if you've set the boot delay to 1s.
:* If the install media created by the script doesn't work (or you forget to create it before rebooting), then you can simply download the latest stable version (or beta/RC if you'd like) from [http://openelec.tv/get-openelec OpenELEC's website here]. The ChromeBox runs the Generic 64-bit version of OpenELEC, and it's recommended that you download the diskimage version, and create the install media, as per the instructions [http://wiki.openelec.tv/index.php/HOW-TO:Installing_OpenELEC/Creating_The_Install_Key#tab=DiskImage on the OpenELEC wiki].
:* Some TVs/displays are not able to show the developer boot screen due to the resolution it uses (1024x768 @ 60Hz), in which case you'll need to use a different display to complete the initial setup steps.
:* Many TVs have overscan enabled by default, which will cut off the text display of the ChromeOS shell. Be sure to set your TV to a mode which does not overscan (varies by manufacturer - often called 'just scan', 'exact' 'pixel perfect'; some TVs require you to label the input as a PC).
:* Using a '''passive''' DisplayPort-->HDMI cable/adapter is often problematic, and can cause the video output drop out after booting. Use either a straight DP cable or straight HDMI/HDMI-->DVI cable; if you have to use a DisplayPort-->HDMI adapter, be sure it is the '''active''' type.

Color Range Selection:
:* This topic is a bit of a minefield, but [http://forum.kodi.tv/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 Kodi option 'Used limited color range' under Settings-->System-->Video Output. Use the video clip and image above as a guide.
:*: '''Note:''' If you want to output Limited color range, you are required to do the following setting as well: Settings-->Video-->Acceleration-->Prefer VAAPI Rendering: disabled/de-selected.

No Audio and/or corrupted video on Wakeup from Suspend:
:* Some displays/AVRs don't successfully handshake when resuming from suspend, leading to no audio output and/or corrupted video output until the Chromebox is rebooted.
:*: Solution: If using a universal remote, such as a Harmony, ensure that you are turning off (suspending) the ChromeBox '''before''' your AVR/TV, and turning it on (resuming) '''after''' the AVR/TV.
:*: Solution: download/enable a script that will force the ChromeBox to reset the audio/video output on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
:*::<nowiki>mkdir -p /storage/.config/sleep.d</nowiki>
:*::<nowiki>cd /storage/.config/sleep.d</nowiki>
:*::<nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/01-cbox_resume.power</nowiki>
:*::<nowiki>chmod +x 01-cbox_resume.power</nowiki>
:*: Then reboot the ChromeBox
:*: Note: If connected via the DisplayPort output, use a text editor (eg, nano) to edit the script and replace references to 'HDMI1' with 'DP1'.

High/Full fan speed on Wakeup from Suspend:
:* A change in the Linux kernel ACPI system results in the fan speed being set to high for at least 10s on resume from suspend; sometimes a reboot is required to return to normal speed.
:*: Workaroound: download/enable a script that will force the ChromeBox's fan speed back to normal on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
:*::<nowiki>mkdir -p /storage/.config/sleep.d</nowiki>
:*::<nowiki>cd /storage/.config/sleep.d</nowiki>
:*::<nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/02-cbox_resume.power</nowiki>
:*::<nowiki>chmod +x 02-cbox_resume.power</nowiki>
:*: Then reboot the ChromeBox

Video Playback:
:* An Intel Linux video driver bug causes intermittent freezes where the video locks up but audio keeps playing.
:*: Solution: This issue is fixed as of OpenELEC 5.0.0; users running a different Linux distro should be sure to update their kernel to 3.18.4 or 3.19.0 (or newer).

On Screen Display:
:* Some OpenELEC 6 users have reported problems with On Screen Display elements not refreshing properly. Changing System -> Settings -> System -> Video Output -> Vertical Blank Sync -> Let Driver Choose will fix the problem.

Remote Controls:
:* Most MCE IR receivers work properly now when connected to USB3 ports under Linux with kernel 3.16+ (older kernels will require a patch/fix); OpenELEC 4.0+ is fully up to date. The version of Ubuntu installed by the ChromeBox EZ setup script in a dual boot setup also includes an up-to-date kernel. However, some buggy MCE receivers still do not work properly (at all), as noted below in the Hardware/Remotes section.

:: For standalone Ubuntu (or any other distro) installs, you will need to update to a 3.16 (or later) kernel.

Unreliable Wireless Devices attached to USB 3.0 ports:
:* Use a USB extension cable to move the device as far away from the USB port as possible. USB 3.0 can cause wireless interference. [http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-interference-paper.html Intel has released a whitepaper documenting the issue.]

Power Management:
:* Suspend/resume is generally problematic with the stock firmware (dual boot setups - OpenELEC will reboot on resume), but works reliably in standalone setups running the coreboot firmware. Resume via IR remote (USB) and wake-on-lan (eg, via YATSE) work perfectly well.
:* Note: WOL only works when the ChromeBox is suspended, not fully powered off, and requires the MAC address of the box to be set (eg, in YATSE)

Windows 8/8.1/10:
:* (Updated 2015/06/08) HDMI audio works, but requires specific drivers (Intel HD graphics 9.18.10.3220 and Intel Display Audio 6.16.0.3112), otherwise HDMI audi is non-functional.
:*: Drivers are mirrored here for your convenience:
:*: [https://dl.dropboxusercontent.com/u/98309225/haswell_driver_vga_32bit.exe Windows 8/8.1/10 32-bit]
:*: [https://dl.dropboxusercontent.com/u/98309225/haswell_driver_vga_64bit.exe Windows 8/8.1/10 64-bit]
:* Bluray disc playback doesn't work, as PowerDVD and WinDVD report that the video drivers are not supported, even though they report the hardware is capable.
:* The CPU fan will shut down at boot and not come back on unless a utility like SpeedFan is used to start it. After manually starting the fan (set PWM1 to 50%), set Speedfan for automatic control and then create a shortcut for it to run at startup.
:* Windows 7 doesn't install/work, so don't ask for help with it.
:* Discussion of running Windows on a ChromeBox can be found on this forum thread: http://forum.kodi.tv/showthread.php?tid=203040

Linux Video Tearing:
:* Some users may experience screen tearing under the Linux desktop, or when watching video (e.g., Netflix). The fix for this is [https://wiki.archlinux.org/index.php/Intel_Graphics#Tear-free_video documented on the Arch Wiki], and copied here for convenience.

:: from a terminal/shell prompt:
:::<nowiki>sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf</nowiki>

:: copy/paste the following:

:::<nowiki>Section "Device"</nowiki>
::::<nowiki>Identifier "Intel Graphics"</nowiki>
::::<nowiki>Driver "intel"</nowiki>
::::<nowiki>Option "TearFree" "true"</nowiki>
:::<nowiki>EndSection</nowiki>

:: then save, exit, and reboot.

High CPU at Idle:
:* When running a Linux setup, there is high idle CPU usage with some older kernels which do not fully support the Haswell platform; be sure to update to the latest kernel available (at '''least''' 3.18.4). On some (mostly dual boot) setups, it may also be necessary to add the following kernel boot parameters to disable the TPM: tpm_tis.force=1 tpm_tis.interrupts=0

OpenELEC Fails to boot:
:* If the OS isn't shutdown cleanly, sometimes a filesystem check (fsck) will be automatically performed. In some cases, the automatic repair is unsuccessful, and an error will show:
::<nowiki>***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***</nowiki> 
::<nowiki>### Starting debugging shell... type exit to quit ###</nowiki> 
::<nowiki>sh: can't access tty; job control turned off</nowiki> 
::<nowiki>#_</nowiki> 
 
In this case, simply run fsck manually as instructed, using the following commands, hitting [enter] after each: 
 
For a standalone setup:
:<nowiki>fsck /dev/sda1</nowiki> 
:<nowiki>fsck /dev/sda2</nowiki> 
 
For a dual-boot setup:
:<nowiki>fsck /dev/sda6</nowiki> 
:<nowiki>fsck /dev/sda7</nowiki> 
 
After the fsck is run, type 'reboot' then hit [enter] and the system should boot normally.
 
 

== Firmware/BIOS Updating ==

As depicted in the overview section above, the ChromeBox's firmware consists of two main parts: the main firmware (coreboot), and the Legacy BIOS payload (SeaBIOS). Users running a dual-boot configuration only need to update the Legacy BIOS portion. Users running a standalone setup should update the custom coreboot firmware only, as it contains an updated SeaBIOS payload (which can not be updated separately).

'''NOTE''': Under normal conditions, the ChromeBox's firmware does not need to be updated after the initial install/update via the EZ Setup Script. As the old saying goes: if it ain't broke, don't fix it. Only update if you are having an issue that is specifically noted in the changelog as being addressed by a newer version.

Dual-boot users should simply boot to ChromeOS and re-download/re-run the EZ Setup Script, choosing the '''Update Legacy BIOS''' option under the Dual Boot heading.

Standalone users should also re-download/re-run the setup script, but instead choosing the '''coreboot firmware install/update''' option under the Standalone heading. As of v3.0, the script can be run under any version of Linux with a full bash shell. As OpenELEC does not have a full bash shell, OE users will need to use the (separate) standalone firmware update script, as described near the end of [http://forum.kodi.tv/showthread.php?tid=194362 the EZ Setup Script forum post].
 
 

== Resetting to Stock ==

If you have a dual boot setup, simply [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], then hit [space] on the developer mode boot screen to revert to verified boot mode. Done. (Note: be sure to use the Kodi EZ Setup Script to reset the boot options to default before doing this, or you may not be able to exit developer mode)
 
 
If you have standalone setup, it is necessary to restore the stock firmware before performing a factory reset to reload ChromeOS.
 
In order to do this, you will need to download/run the ChromeOS device Firmware Utility script and select the appropriate option from the menu. The script will give you the option to restore from either a backup file from USB (which you created before originally flashing the custom coreboot firmware) or from a generic copy extracted from Google's recovery image. Like the Kodi EZ Setup Script, this script must be run from a Linux terminal with a full bash shell; OpenELEC users will need to boot a Linux Live USB ([http://www.ubuntu.com/download/desktop Ubuntu 14.04.2 64-bit] works fine) from which to run the script. Just download the ISO of and write it to USB using Win32DiskImager (from Windows) or dd (Linux/MacOS).
 
 

* Boot the Linux live USB, then open a terminal/shell window
* Download and run the ChromeOS device Firmware Utility script using the following two commands (hit enter after typing each command):
*: <nowiki>curl -L -O https://goo.gl/1hFfO3</nowiki>
*: <nowiki>sudo bash 1hFfO3 </nowiki>

* Select option 3, Restore Stock Firmware
* Choose whether to restore from a backup file on USB or not
*: If not, select your ChromeBox model so the appropriate firmware can be downloaded
 
After restoring the stock firmware, reboot, and proceed to [[ASUS_Chromebox#Perform_a_Factory_Reset|Perform_a_Factory_Reset]] above to restore/reload ChromeOS.
 
 

==External Links==
* [http://en.wikipedia.org/wiki/Chromebox Chromebox wikipedia article]
* [https://www.google.com/work/chrome/ Google's "Chrome for Work" web page]

{{Helix updated}}

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

Archive:Chromebox

2015-11-02T13:18:38Z

Rodalpho: /* OS and Kodi Installation */

{{mininav|[[Devices]]|[[x86 hardware]]}}
{{device notice}}

{{Infobox information appliance
| name = Chromebox
| image = [[File:Asus_chromebox.jpg|300px]]
| releasedate = 2014-03-14 (US)
| os = ChromeOS
| cpu = Intel® Celeron 2955U/2957U Intel® Core i3-4010U/4030U Intel® Core i7-4600U
| graphics = Intel® HD Graphics/GT1 (Celeron) Intel® HD Graphics 4400/GT2 (i3/i7)
| storage = 16GB internal SSD (M.2 SATA)
| memory = 2GB/4GB/8GB standard, 16GB max Dual Channel DDR3L-12800
| connectivity = HDMI 1.4a DisplayPort 1.2a Bluetooth 4.0 USB 3.0 (4x) 802.11 abgn/AC wifi 10/100/1000 Ethernet 2 -in-1 Card Reader 3.5mm headphone plug
| 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]]

<section begin="intro" />The Chromebox is an inexpensive small form-factor PC which runs Google's ChromeOS; it is the desktop variant of a Chromebook laptop. Although Kodi does not run natively under ChromeOS, the Chromebox can easily be made to run Linux (or Windows) and {{Kodi}}.<section end="intro" />

This page is a collection of links, information, tips, and guides related to running {{Kodi}} on Chromebox mini PCs.

{{note|This page was originally written for the ASUS ChromeBox, but all of the information is valid for the HP, Acer, and Dell Chromeboxes as well. The hardware is virtually identical: the Acer has a slightly different form factor; the HP model has only 1 dimm slot (vs the 2 the others have); the fan of the HP is also a bit louder than the others (with the Asus being the most quiet); the Dell models have an 802.11 AC wifi module, whereas the others only have 802.11 abgn.}} 

== ChromeBox Overview ==
The Haswell Celeron-based Chromebox is small, lightweight x86-64 PC that natively runs ChromeOS, but with a few simple tweaks, has the capability to run any Linux-based OS (plus Windows 8.1+). It features HDMI and DisplayPort video outputs (which can be used simultaneously), 4x USB 3.0 ports, gigabit Ethernet, an SD card slot, and built-in 802.11a/b/g/n wireless and Bluetooth 4.0.

Capability wise, the ChromeBox fully supports hardware accelerated H.264/MPEG-2/VC-1 video playback at up to 2160p24/p30 (4K), proper 24p output, and full 7.1/HD audio bitstream output. 3D playback is supported (HSBS/HTAB), though the decoding of MVC streams (as used in 3D Blu-ray ISOs) is not supported under Linux at this time; the hardware itself is capable. Hi10 H.264 1080p playback is software decoded, but works well with few exceptions. 2160p60 is available only via DisplayPort with MST (multi-stream transport), as HDMI 1.4a is limited to 2160p30. H.265/HEVC is software (CPU) decoded, so playback is limited to 1080p max and low/moderate bit-rates. From a purely Kodi/media playback standpoint, there's no advantage to the Core i3/i7 models over the Celeron model (outside of 2160p60 video playback, which the i3/i7's HD4400 GPU can handle), although dual channel memory (2 identical capacity modules) provides a decent performance boost in some situations (like playback of 60fps video).

The ChromeBox uses customized open-source firmware components (mainly [http://www.coreboot.org coreboot]) to boot ChromeOS in a secure/verified manner. By putting it in developer mode, we disable the verified boot restriction, and allow the ChromeBox to boot in "legacy mode" (via a legacy boot payload, [http://www.seabios.org SeaBIOS]), which enables other operating systems (eg: OpenELEC, Ubuntu/Kodibuntu) to be installed / dual booted. If ChromeOS isn't needed, then custom firmware can be installed to directly boot the legacy BIOS. A simplified overview of the ChromeBox boot process is shown here (click for full-size):
 
[[File:ChromeBox_boot_process.png|400px]]
 
This wiki page will guide you through the steps necessary to put the ChromeBox into developer mode and set it up in either a dual boot or standalone (non-ChromeOS) configuration. The majority of the process has been automated via the ChromeBox EZ Setup Script, making it safe and easy to run Linux/Kodi on your ChromeBox.

== Device Preparation ==

=== Disable Firmware Write Protect ===

Disabling the firmware write protect will allow us to shorten the timeout on the developer boot screen (from 30s to ~1s) in a dual boot configuration, and optionally boot directly in "legacy mode" (and into Ubuntu or OpenELEC). Disabling the write protect is also necessary for standalone setups so that the stock firmware can be replaced with a custom version.

With the device powered off and unplugged:

# Remove (4) rubber feet from bottom of unit
# Remove (4) screws under rubber feet
# Take off the bottom cover.
#:Tip: Thread two of the screws that you just removed into the VESA mounting holes, and use them to pull/separate bottom cover.
# Remove write-protect screw circled below:
#::Asus/HP/Dell: [[File:Inside-chrome1.jpg|300px]]
#::Acer: [[File:Acer wp screw.png|400px]]
#::  
#:: '''Notes:'''
#:: -- The write-protect screw on the Acer model is under the heat pipe, which needs to be removed to access it. Be sure to smooth out (or replace) the heatsink grease before reinstallation of the heatsink / heat pipe.
#:: -- On some boxes (this is rare, but seems to be most common on the Dells), even after removing the write-protect screw, there is still connectivity between the two semi-circles, in which case you may need to use a small flathead screwdriver (eg) to lightly scrape away the excess material which is causing continuity. You can verify with a DMM.
# Reassemble in reverse order

'''Important:''' The write-protect screw should be left out permanently.
 
 

=== Put in Developer Mode ===

Putting the ChromeBox in developer mode will disable verified boot mode, and allow you to access the underlying Linux operating system features necessary for installing/running Kodi (via OpenELEC/Ubuntu).

'''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
#: [[File:Recoverybutton.png|200px]]
# 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 (vs verified boot mode), and the developer boot screen (shown below) will be displayed at each boot.
 
 
'''Note:''' The recovery button (and booting to recovery mode) are a of function of the stock firmware. If you've flashed a custom firmware on your box (either as part of a standalone setup or otherwise), the recovery button has no function and the ChromeOS recovery mode doesn't exist.
 
 
[[File:ChromeBox_dev_boot.jpg|400px]]

The developer boot screen has a warning about OS verification being off. '''Do not hit [SPACE]''', as it will return the device to verified boot mode. The ChromeBox must remain in developer mode, else you will potentially have to redo the setup from the beginning. The developer mode boot screen has a ~30s timeout, followed by two beeps, before booting. You can skip the delay by pressing [CTRL-D] to immediately boot into ChromeOS.
 
 

=== Perform a Factory Reset ===

A factory reset is not needed for a standalone setup, but must be performed prior to any dual-boot (re)install.

# Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/answer/1080595?hl=en or use the [https://chrome.google.com/webstore/detail/chromebook-recovery-utili/jndclpdbaamdhonoechobihbbiimdgai?hl=en ChromeBook Recovery Utility from the Chrome web store].

Note: Google's recovery tool can be picky about what kind/size of USB/SD media you use. If one USB stick doesn't work, try another.

# 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 - so be sure to reset them back to the 'ChromeOS + 30s default' option '''before''' performing a factory reset. If you forget to do that, you'll need to press [CTRL-D] on the developer boot screen (or before the legacy boot/SeaBIOS boot screen) in order to boot ChromeOS after performing the recovery.
 
 
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:
:*:Asus: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_panther_recovery_stable-channel_mp.bin.zip
:*: HP: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_zako_recovery_stable-channel_mp-v2.bin.zip
:*:Acer: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_mccloud_recovery_stable-channel_mp.bin.zip
:*:Dell: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_tricky_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
 
 
'''Note:''' The recovery media created using Google's recovery tool works only when the ChromeBox is booted into recovery mode, which only exists when using the stock firmware. If you've flashed a custom firmware on your box (either as part of a standalone setup or otherwise), ChromeOS recovery mode doesn't exist, and attempting to boot the recovery media from SeaBIOS will not work.
 
 

== Installation, Configuration, and Updating ==

=== OS and Kodi Installation ===
Kodi can be installed on the ChromeBox in a variety of ways. The two most common are via OpenELEC or Ubuntu+Kodi, in either a standalone or dual boot configuration. This is accomplished via the ChromeBox E-Z Setup script, which must be run (at least initially) from ChromeOS.
 
The EZ setup script will facilitate everything needed to install either a dual boot setup, or install a custom firmware which allows the installation of any Linux-based OS in standalone mode.
 
To run the ChromeBox E-Z Setup script, perform the following steps:

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

:Note: the first command is curl space dash capital-L space dash capital-O space http://goo.gl/3Tfu5W.

Full instructions and a detailed explanation of the script's functions and usage can be found at the following forum thread: http://forum.kodi.tv/showthread.php?tid=194362
 
 
'''Older Kernels:''' If installing a Linux-based OS other than OpenELEC (eg, Ubuntu/Kodibuntu), you will most likely need to manually update the kernel for optimal operation. Kernel version 3.18.4 is the minimum recommended, as it has a fix for an Intel GPU bug that can cause hanging during video playback. Updating the kernel is OS-specific and beyond the scope of this wiki, but instructions are easily found by googling.
 
'''Ubuntu 15.10:''' Ubuntu Wily Werewolf (15.10) ships with Linux kernel 4.2.0, which immediately panics upon boot on Chromeboxes. To fix this, you can run an earlier kernel. Alternatively, if you're able to boot, you can disable ACPI. To do this, add "acpi=off" to the end of the commandline default line in your "/etc/default/grub: file like so:
 
:: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw acpi=off"
 
This bug is fixed in Linux kernel 4.3. When it is released, update and remove the acpi=off flag.
 
 

=== Dual Boot OS Selection ===
When dual booting with ChromeOS and OpenELEC/Ubuntu, due to the ChromeBox's firmware setup, there is no conventional boot menu. Instead, the OS selection is made via keyboard shortcuts on the developer mode boot screen (shown above): [CTRL-D] boots directly ChromeOS; [CTRL-L] boots the legacy BIOS (and whatever secondary OS is installed). The default OS and boot timeout are set using the 'Set Boot Options' feature of the EZ Setup Script.
 
 

=== Updating Kodi ===

==== OpenELEC ====

The Chromebox is, at its core, a standard 64-bit x86 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). Automatic updates won't update from a stable to a beta release, but will update stable->stable, beta->beta, and beta->stable. If the automatic update doesn't work for some reason, or you want to update to a test/nightly/beta/RC build, you can manually update using the instructions on the [http://wiki.openelec.tv/index.php?title=Updating_OpenELEC OpenELEC wiki].
 
 

=== Recommended Settings ===

==== Kodi General ====

* System-->Settings-->System: Settings Level:'''Expert'''
* System-->Settings-->System-->Video Output: Vertical blank sync:'''Let driver decide'''
* System-->Settings-->System-->Power Saving: Shutdown function:'''Suspend''' (sets IR power toggle to suspend)
* System-->Settings-->Videos-->Acceleration: Enable HQ Scalers for scalings above:'''20%'''
* System-->Settings-->Videos-->Acceleration: Use VC-1 VAAPI:'''Selected''' (de-select if you have interlaced VC-1 content)
* System-->Settings-->Videos-->Acceleration: Prefer VAAPI render method:'''Selected'''
 
Also see the video playback settings as shown in the screenshots below. Change as needed, then hit 'Set as default for all videos' to save.
 
 
==== OpenELEC Specific ====

* System-->OpenELEC-->System: Automatic Updates:'''Auto'''
* System-->OpenELEC-->Network: Wireless Networks/Active:'''Selected''' (if using WiFi)
* System-->OpenELEC-->Network: Wait for network before starting Kodi:'''Selected''' (if using a external mysql database)
* System-->OpenELEC-->Services: Enable Bluetooth:'''Selected''' (if using Bluetooth)
 
 

<gallery>
File:chromebox_video_accel_settings_1.png|ChromeBox Settings: Video/Acceleration
File:chromebox_video_playback_settings_1.png|ChromeBox Video Playback Settings (1/2)
File:chromebox_video_playback_settings_2.png|ChromeBox Video Playback Settings (2/2)
</gallery>

=== Switching between Standalone and Dual Boot configurations ===

If you have a dual boot setup and wish to switch to a standalone setup, the steps are no different than installing on a "fresh" system, though you can obviously skip the steps you have already performed (removing the write-protect screw, putting the box in developer mode). If you have an OpenELEC dual boot setup and are switching to an OpenELEC standalone setup, then you can backup your settings etc using the built-in tools, copy to another PC/USB, and restore after performing the standalone setup.

If you have a standalone setup and wish to switch to a dual boot setup, you need to first [[Chromebox#Restoring_the_Stock_Firmware|restore the stock firmware]], then [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], after which you can continue with the dual boot setup.
 
 

== Recommended Accessories / Hardware Upgrades ==
 
For most users, there's no need to upgrade the ChromeBox's RAM or HDD; OpenELEC uses minimal RAM and disk space, and there's no benefit to upgrading. However, users who opt for a full Ubuntu/Kodibuntu setup, and plan on running lots of background processes etc, may find it beneficial to install additional RAM or upgrade to a larger SSD.
 
 
'''RAM:'''
: The ChromeBox has two (2) 204-Pin SODIMM slots (HP models only have one), 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)
:* HP H6Y75AA (4GB, 1.35v)
: 
: 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 2242 M.2 SATA SSD (22mm x 42mm); stock is a 16GB unit (usually Sandisk or Kensington). Any M.2 SATA 2242 replacement drive should work without issue.
 
'''Remote Controls:'''
: The ChromeBox does not have a built-in IR sensor, and must therefore use a USB IR receiver (or a Bluetooth remote). In general, any remote/receiver listed on the Kodi wiki as fully working under Linux should be fine, though some have issues when connected to USB3 ports. 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)
:* Sony IR receiver model PCVA-IR8U (MCE/eHome)
:* HP IR remote/receiver kit [http://www.amazon.com/dp/B00AYE6JDO/ OVU400102/71] (MCE/eHome, includes 5187-4593 receiver)
:* Ortek IR remote/receiver kit [http://www.amazon.com/dp/B00224ZDFY/ VRC-1100] (MCE clone, receiver also works well w/Logitech Harmony remotes)
:* Rosewill RHRC-11002 remote (MCE clone, includes receiver model IR605)
:* Rosewill WMC RRC-127 remote/receiver
:* Microsoft XBOX 360 IR remote (with MCE/eHome receiver or Flirc)
:* Microsoft XBOX One IR remote (with MCE/eHome receiver or Flirc)
:* Logitech Harmony remotes (programmed as Microsoft Media Center Extender - not as a keyboard - with MCE/eHome receiver; not recommended for use with a Flirc)
:* Sony Playstation 3 (PS3) Bluetooth remote (works with built-in BT receiver)
:*: press/hold START + ENTER to pair, choose 'Trust and Connect', then hit Ok and Enable Standby after connecting
:* Logitech Harmony Smart Hub (via Bluetooth, works with built-in BT receiver, [http://forum.kodi.tv/showthread.php?tid=194362&pid=1843165#pid1843165 see forum post here])
:* Measy RC11 Android Monitor Wireless Keyboard Air Mouse Remote Controller With Gyroscope (cannot wake up Chromebox but works otherwise nicely, with keys as well as with mouse pointer at both OpenELEC and ChromeOS)
:* Amazon FireTV / Fire Stick remotes (Bluetooth)
:NOTE: If you need to re-map remote buttons, you can use the [[Add-on:Keymap Editor|Keymap Editor Add-on]] to do so.

:'''Currently non-working''':
:* HP IR receiver model 5070-2584 (MCE/eHome)
:* AVS Gear HA-IR01SV (MCE/eHome)
:* All Topseed manufactured MCE IR receivers
 
'''USB Audio Devices''':
:As the ChromeBox only has HDMI and analog audio outputs, if you need SPDIF, then either a converter or external/USB device must be used. The following devices have been tested/confirmed working:
:* [http://www.amazon.com/gp/product/B0036VO4X4/ Turtle Beach Audio Advantage Micro II ] (plug/play in both OpenELEC and Win8.1)
:* ASUS Xonar U3 USB (OpenELEC: requires un-muting the SPDIF line, see [http://openelec.tv/forum/41-supported-hardware/71023-asus-xonar-u3-usb-soundcard this forum post])
 
'''HDMI-CEC''':
:The ChromeBox does not support HDMI-CEC natively, but support can be added using an [http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx external USB CEC adapter] from Pulse-Eight. The USB CEC Adapter needs power to the USB port BEFORE there is any video out, or it simply will not pass through any video signal. There are several ways to work around this:

:* Either always leave your Chromebox on, or just put it into standby; never turn it off
:* Use an externally powered source (eg, USB hub, TV set) to power the adapter (rather than the ChromeBox itself), so it always has power
:* If you have a spare HDMI port, you actually can split video in and control in for one HDMI channel using two physical HDMI ports. The video will be connected to the main port, and that's the port you use in the HDMI config settings in {{Kodi}}, and then you simply connect the USB CEC adapter to a spare HDMI port, does not appear to matter which.
 
 

== Troubleshooting, Known Issues, Fixes/Workarounds ==

Installation, Dual Booting, USB booting:
:* 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 Kodi on a ChromeBox, or to select between OSes in a dual boot setup. The Logitech K400 is one of these, so use another keyboard to install if yours doesn't appear to be working. Most Bluetooth keyboards '''will not work''' due to the fact that they require the OS to be loaded in order to reconnect to the ChromeBox.
:*: An effort is underway on the forums to catalog which keyboards work (and which do not); the thread (which is being updated regularly) can be found here: http://forum.kodi.tv/showthread.php?tid=211797
:* Help! I'm stuck on the black SeaBIOS boot screen, with the "booting from hard disk" text displayed (and possibly a bunch of nonsensical text afterwards).
:*:This happens because SeaBIOS is trying to boot from the internal hard drive, but no bootable OS (or only ChromeOS) is installed.
::* If you have a dual boot setup, 99% of the time this is due to not having performed a factory reset prior to running the EZ Setup Script, [[Chromebox#Perform_a_Factory_Reset|as listed in the Device Prep section above]]. Simply perform the factory reset, then redo the dual boot setup using the script as before.
::* If you have a standalone setup, and are trying to boot from USB:
::*: If you see the 'Press ESC for boot menu' text but pressing it doesn't work, then the issue is your keyboard, so try using a different one.
::*: If you '''don't''' see the 'Press ESC for boot menu' text, then the issue is with your boot media, so try using a different USB flash drive.
:* Ok, I have an OS installed, but I can't boot from USB - it boots too fast!
:*: This means your USB boot media isn't being recognized, otherwise you would have 5s to press ESC and bring up the boot menu. Re-create your boot media, possibly using a different USB stick. If you're trying to boot a Linux ISO, write the ISO directly to USB (using Win32DiskImager or dd), don't use a tool like unetbootin (eg).
:* If you're getting an error similar to "It appears your computer only has 639K of low ("DOS") RAM.", then you're pressing the dual boot selection keys (CTRL-D/CTRL-L) too late in the boot sequence - they need to be pressed on the developer mode boot screen, before it boots either ChromeOS or the Legacy BIOS (SeaBIOS). On some displays, this may mean pressing them before the display comes on, particularly if you've set the boot delay to 1s.
:* If the install media created by the script doesn't work (or you forget to create it before rebooting), then you can simply download the latest stable version (or beta/RC if you'd like) from [http://openelec.tv/get-openelec OpenELEC's website here]. The ChromeBox runs the Generic 64-bit version of OpenELEC, and it's recommended that you download the diskimage version, and create the install media, as per the instructions [http://wiki.openelec.tv/index.php/HOW-TO:Installing_OpenELEC/Creating_The_Install_Key#tab=DiskImage on the OpenELEC wiki].
:* Some TVs/displays are not able to show the developer boot screen due to the resolution it uses (1024x768 @ 60Hz), in which case you'll need to use a different display to complete the initial setup steps.
:* Many TVs have overscan enabled by default, which will cut off the text display of the ChromeOS shell. Be sure to set your TV to a mode which does not overscan (varies by manufacturer - often called 'just scan', 'exact' 'pixel perfect'; some TVs require you to label the input as a PC).
:* Using a '''passive''' DisplayPort-->HDMI cable/adapter is often problematic, and can cause the video output drop out after booting. Use either a straight DP cable or straight HDMI/HDMI-->DVI cable; if you have to use a DisplayPort-->HDMI adapter, be sure it is the '''active''' type.

Color Range Selection:
:* This topic is a bit of a minefield, but [http://forum.kodi.tv/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 Kodi option 'Used limited color range' under Settings-->System-->Video Output. Use the video clip and image above as a guide.
:*: '''Note:''' If you want to output Limited color range, you are required to do the following setting as well: Settings-->Video-->Acceleration-->Prefer VAAPI Rendering: disabled/de-selected.

No Audio and/or corrupted video on Wakeup from Suspend:
:* Some displays/AVRs don't successfully handshake when resuming from suspend, leading to no audio output and/or corrupted video output until the Chromebox is rebooted.
:*: Solution: If using a universal remote, such as a Harmony, ensure that you are turning off (suspending) the ChromeBox '''before''' your AVR/TV, and turning it on (resuming) '''after''' the AVR/TV.
:*: Solution: download/enable a script that will force the ChromeBox to reset the audio/video output on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
:*::<nowiki>mkdir -p /storage/.config/sleep.d</nowiki>
:*::<nowiki>cd /storage/.config/sleep.d</nowiki>
:*::<nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/01-cbox_resume.power</nowiki>
:*::<nowiki>chmod +x 01-cbox_resume.power</nowiki>
:*: Then reboot the ChromeBox
:*: Note: If connected via the DisplayPort output, use a text editor (eg, nano) to edit the script and replace references to 'HDMI1' with 'DP1'.

High/Full fan speed on Wakeup from Suspend:
:* A change in the Linux kernel ACPI system results in the fan speed being set to high for at least 10s on resume from suspend; sometimes a reboot is required to return to normal speed.
:*: Workaroound: download/enable a script that will force the ChromeBox's fan speed back to normal on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
:*::<nowiki>mkdir -p /storage/.config/sleep.d</nowiki>
:*::<nowiki>cd /storage/.config/sleep.d</nowiki>
:*::<nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/02-cbox_resume.power</nowiki>
:*::<nowiki>chmod +x 02-cbox_resume.power</nowiki>
:*: Then reboot the ChromeBox

Video Playback:
:* An Intel Linux video driver bug causes intermittent freezes where the video locks up but audio keeps playing.
:*: Solution: This issue is fixed as of OpenELEC 5.0.0; users running a different Linux distro should be sure to update their kernel to 3.18.4 or 3.19.0 (or newer).

On Screen Display:
:* Some OpenELEC 6 users have reported problems with On Screen Display elements not refreshing properly. Changing System -> Settings -> System -> Video Output -> Vertical Blank Sync -> Let Driver Choose will fix the problem.

Remote Controls:
:* Most MCE IR receivers work properly now when connected to USB3 ports under Linux with kernel 3.16+ (older kernels will require a patch/fix); OpenELEC 4.0+ is fully up to date. The version of Ubuntu installed by the ChromeBox EZ setup script in a dual boot setup also includes an up-to-date kernel. However, some buggy MCE receivers still do not work properly (at all), as noted below in the Hardware/Remotes section.

:: For standalone Ubuntu (or any other distro) installs, you will need to update to a 3.16 (or later) kernel.

Unreliable Wireless Devices attached to USB 3.0 ports:
:* Use a USB extension cable to move the device as far away from the USB port as possible. USB 3.0 can cause wireless interference. [http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-interference-paper.html Intel has released a whitepaper documenting the issue.]

Power Management:
:* Suspend/resume is generally problematic with the stock firmware (dual boot setups - OpenELEC will reboot on resume), but works reliably in standalone setups running the coreboot firmware. Resume via IR remote (USB) and wake-on-lan (eg, via YATSE) work perfectly well.
:* Note: WOL only works when the ChromeBox is suspended, not fully powered off, and requires the MAC address of the box to be set (eg, in YATSE)

Windows 8/8.1/10:
:* (Updated 2015/06/08) HDMI audio works, but requires specific drivers (Intel HD graphics 9.18.10.3220 and Intel Display Audio 6.16.0.3112), otherwise HDMI audi is non-functional.
:*: Drivers are mirrored here for your convenience:
:*: [https://dl.dropboxusercontent.com/u/98309225/haswell_driver_vga_32bit.exe Windows 8/8.1/10 32-bit]
:*: [https://dl.dropboxusercontent.com/u/98309225/haswell_driver_vga_64bit.exe Windows 8/8.1/10 64-bit]
:* Bluray disc playback doesn't work, as PowerDVD and WinDVD report that the video drivers are not supported, even though they report the hardware is capable.
:* The CPU fan will shut down at boot and not come back on unless a utility like SpeedFan is used to start it. After manually starting the fan (set PWM1 to 50%), set Speedfan for automatic control and then create a shortcut for it to run at startup.
:* Windows 7 doesn't install/work, so don't ask for help with it.
:* Discussion of running Windows on a ChromeBox can be found on this forum thread: http://forum.kodi.tv/showthread.php?tid=203040

Linux Video Tearing:
:* Some users may experience screen tearing under the Linux desktop, or when watching video (e.g., Netflix). The fix for this is [https://wiki.archlinux.org/index.php/Intel_Graphics#Tear-free_video documented on the Arch Wiki], and copied here for convenience.

:: from a terminal/shell prompt:
:::<nowiki>sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf</nowiki>

:: copy/paste the following:

:::<nowiki>Section "Device"</nowiki>
::::<nowiki>Identifier "Intel Graphics"</nowiki>
::::<nowiki>Driver "intel"</nowiki>
::::<nowiki>Option "TearFree" "true"</nowiki>
:::<nowiki>EndSection</nowiki>

:: then save, exit, and reboot.

High CPU at Idle:
:* When running a Linux setup, there is high idle CPU usage with some older kernels which do not fully support the Haswell platform; be sure to update to the latest kernel available (at '''least''' 3.18.4). On some (mostly dual boot) setups, it may also be necessary to add the following kernel boot parameters to disable the TPM: tpm_tis.force=1 tpm_tis.interrupts=0

OpenELEC Fails to boot:
:* If the OS isn't shutdown cleanly, sometimes a filesystem check (fsck) will be automatically performed. In some cases, the automatic repair is unsuccessful, and an error will show:
::<nowiki>***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***</nowiki> 
::<nowiki>### Starting debugging shell... type exit to quit ###</nowiki> 
::<nowiki>sh: can't access tty; job control turned off</nowiki> 
::<nowiki>#_</nowiki> 
 
In this case, simply run fsck manually as instructed, using the following commands, hitting [enter] after each: 
 
For a standalone setup:
:<nowiki>fsck /dev/sda1</nowiki> 
:<nowiki>fsck /dev/sda2</nowiki> 
 
For a dual-boot setup:
:<nowiki>fsck /dev/sda6</nowiki> 
:<nowiki>fsck /dev/sda7</nowiki> 
 
After the fsck is run, type 'reboot' then hit [enter] and the system should boot normally.
 
 

== Firmware/BIOS Updating ==

As depicted in the overview section above, the ChromeBox's firmware consists of two main parts: the main firmware (coreboot), and the Legacy BIOS payload (SeaBIOS). Users running a dual-boot configuration only need to update the Legacy BIOS portion. Users running a standalone setup should update the custom coreboot firmware only, as it contains an updated SeaBIOS payload (which can not be updated separately).

'''NOTE''': Under normal conditions, the ChromeBox's firmware does not need to be updated after the initial install/update via the EZ Setup Script. As the old saying goes: if it ain't broke, don't fix it. Only update if you are having an issue that is specifically noted in the changelog as being addressed by a newer version.

Dual-boot users should simply boot to ChromeOS and re-download/re-run the EZ Setup Script, choosing the '''Update Legacy BIOS''' option under the Dual Boot heading.

Standalone users should also re-download/re-run the setup script, but instead choosing the '''coreboot firmware install/update''' option under the Standalone heading. As of v3.0, the script can be run under any version of Linux with a full bash shell. As OpenELEC does not have a full bash shell, OE users will need to use the (separate) standalone firmware update script, as described near the end of [http://forum.kodi.tv/showthread.php?tid=194362 the EZ Setup Script forum post].
 
 

== Resetting to Stock ==

If you have a dual boot setup, simply [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], then hit [space] on the developer mode boot screen to revert to verified boot mode. Done. (Note: be sure to use the Kodi EZ Setup Script to reset the boot options to default before doing this, or you may not be able to exit developer mode)
 
 
If you have standalone setup, it is necessary to restore the stock firmware before performing a factory reset to reload ChromeOS.
 
In order to do this, you will need to download/run the ChromeOS device Firmware Utility script and select the appropriate option from the menu. The script will give you the option to restore from either a backup file from USB (which you created before originally flashing the custom coreboot firmware) or from a generic copy extracted from Google's recovery image. Like the Kodi EZ Setup Script, this script must be run from a Linux terminal with a full bash shell; OpenELEC users will need to boot a Linux Live USB ([http://www.ubuntu.com/download/desktop Ubuntu 14.04.2 64-bit] works fine) from which to run the script. Just download the ISO of and write it to USB using Win32DiskImager (from Windows) or dd (Linux/MacOS).
 
 

* Boot the Linux live USB, then open a terminal/shell window
* Download and run the ChromeOS device Firmware Utility script using the following two commands (hit enter after typing each command):
*: <nowiki>curl -L -O https://goo.gl/1hFfO3</nowiki>
*: <nowiki>sudo bash 1hFfO3 </nowiki>

* Select option 3, Restore Stock Firmware
* Choose whether to restore from a backup file on USB or not
*: If not, select your ChromeBox model so the appropriate firmware can be downloaded
 
After restoring the stock firmware, reboot, and proceed to [[ASUS_Chromebox#Perform_a_Factory_Reset|Perform_a_Factory_Reset]] above to restore/reload ChromeOS.
 
 

==External Links==
* [http://en.wikipedia.org/wiki/Chromebox Chromebox wikipedia article]
* [https://www.google.com/work/chrome/ Google's "Chrome for Work" web page]

{{Helix updated}}

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

Archive:Chromebox

2015-11-02T13:16:11Z

Rodalpho: added note on kernel panic on boot for 4.2.0

{{mininav|[[Devices]]|[[x86 hardware]]}}
{{device notice}}

{{Infobox information appliance
| name = Chromebox
| image = [[File:Asus_chromebox.jpg|300px]]
| releasedate = 2014-03-14 (US)
| os = ChromeOS
| cpu = Intel® Celeron 2955U/2957U Intel® Core i3-4010U/4030U Intel® Core i7-4600U
| graphics = Intel® HD Graphics/GT1 (Celeron) Intel® HD Graphics 4400/GT2 (i3/i7)
| storage = 16GB internal SSD (M.2 SATA)
| memory = 2GB/4GB/8GB standard, 16GB max Dual Channel DDR3L-12800
| connectivity = HDMI 1.4a DisplayPort 1.2a Bluetooth 4.0 USB 3.0 (4x) 802.11 abgn/AC wifi 10/100/1000 Ethernet 2 -in-1 Card Reader 3.5mm headphone plug
| 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]]

<section begin="intro" />The Chromebox is an inexpensive small form-factor PC which runs Google's ChromeOS; it is the desktop variant of a Chromebook laptop. Although Kodi does not run natively under ChromeOS, the Chromebox can easily be made to run Linux (or Windows) and {{Kodi}}.<section end="intro" />

This page is a collection of links, information, tips, and guides related to running {{Kodi}} on Chromebox mini PCs.

{{note|This page was originally written for the ASUS ChromeBox, but all of the information is valid for the HP, Acer, and Dell Chromeboxes as well. The hardware is virtually identical: the Acer has a slightly different form factor; the HP model has only 1 dimm slot (vs the 2 the others have); the fan of the HP is also a bit louder than the others (with the Asus being the most quiet); the Dell models have an 802.11 AC wifi module, whereas the others only have 802.11 abgn.}} 

== ChromeBox Overview ==
The Haswell Celeron-based Chromebox is small, lightweight x86-64 PC that natively runs ChromeOS, but with a few simple tweaks, has the capability to run any Linux-based OS (plus Windows 8.1+). It features HDMI and DisplayPort video outputs (which can be used simultaneously), 4x USB 3.0 ports, gigabit Ethernet, an SD card slot, and built-in 802.11a/b/g/n wireless and Bluetooth 4.0.

Capability wise, the ChromeBox fully supports hardware accelerated H.264/MPEG-2/VC-1 video playback at up to 2160p24/p30 (4K), proper 24p output, and full 7.1/HD audio bitstream output. 3D playback is supported (HSBS/HTAB), though the decoding of MVC streams (as used in 3D Blu-ray ISOs) is not supported under Linux at this time; the hardware itself is capable. Hi10 H.264 1080p playback is software decoded, but works well with few exceptions. 2160p60 is available only via DisplayPort with MST (multi-stream transport), as HDMI 1.4a is limited to 2160p30. H.265/HEVC is software (CPU) decoded, so playback is limited to 1080p max and low/moderate bit-rates. From a purely Kodi/media playback standpoint, there's no advantage to the Core i3/i7 models over the Celeron model (outside of 2160p60 video playback, which the i3/i7's HD4400 GPU can handle), although dual channel memory (2 identical capacity modules) provides a decent performance boost in some situations (like playback of 60fps video).

The ChromeBox uses customized open-source firmware components (mainly [http://www.coreboot.org coreboot]) to boot ChromeOS in a secure/verified manner. By putting it in developer mode, we disable the verified boot restriction, and allow the ChromeBox to boot in "legacy mode" (via a legacy boot payload, [http://www.seabios.org SeaBIOS]), which enables other operating systems (eg: OpenELEC, Ubuntu/Kodibuntu) to be installed / dual booted. If ChromeOS isn't needed, then custom firmware can be installed to directly boot the legacy BIOS. A simplified overview of the ChromeBox boot process is shown here (click for full-size):
 
[[File:ChromeBox_boot_process.png|400px]]
 
This wiki page will guide you through the steps necessary to put the ChromeBox into developer mode and set it up in either a dual boot or standalone (non-ChromeOS) configuration. The majority of the process has been automated via the ChromeBox EZ Setup Script, making it safe and easy to run Linux/Kodi on your ChromeBox.

== Device Preparation ==

=== Disable Firmware Write Protect ===

Disabling the firmware write protect will allow us to shorten the timeout on the developer boot screen (from 30s to ~1s) in a dual boot configuration, and optionally boot directly in "legacy mode" (and into Ubuntu or OpenELEC). Disabling the write protect is also necessary for standalone setups so that the stock firmware can be replaced with a custom version.

With the device powered off and unplugged:

# Remove (4) rubber feet from bottom of unit
# Remove (4) screws under rubber feet
# Take off the bottom cover.
#:Tip: Thread two of the screws that you just removed into the VESA mounting holes, and use them to pull/separate bottom cover.
# Remove write-protect screw circled below:
#::Asus/HP/Dell: [[File:Inside-chrome1.jpg|300px]]
#::Acer: [[File:Acer wp screw.png|400px]]
#::  
#:: '''Notes:'''
#:: -- The write-protect screw on the Acer model is under the heat pipe, which needs to be removed to access it. Be sure to smooth out (or replace) the heatsink grease before reinstallation of the heatsink / heat pipe.
#:: -- On some boxes (this is rare, but seems to be most common on the Dells), even after removing the write-protect screw, there is still connectivity between the two semi-circles, in which case you may need to use a small flathead screwdriver (eg) to lightly scrape away the excess material which is causing continuity. You can verify with a DMM.
# Reassemble in reverse order

'''Important:''' The write-protect screw should be left out permanently.
 
 

=== Put in Developer Mode ===

Putting the ChromeBox in developer mode will disable verified boot mode, and allow you to access the underlying Linux operating system features necessary for installing/running Kodi (via OpenELEC/Ubuntu).

'''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
#: [[File:Recoverybutton.png|200px]]
# 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 (vs verified boot mode), and the developer boot screen (shown below) will be displayed at each boot.
 
 
'''Note:''' The recovery button (and booting to recovery mode) are a of function of the stock firmware. If you've flashed a custom firmware on your box (either as part of a standalone setup or otherwise), the recovery button has no function and the ChromeOS recovery mode doesn't exist.
 
 
[[File:ChromeBox_dev_boot.jpg|400px]]

The developer boot screen has a warning about OS verification being off. '''Do not hit [SPACE]''', as it will return the device to verified boot mode. The ChromeBox must remain in developer mode, else you will potentially have to redo the setup from the beginning. The developer mode boot screen has a ~30s timeout, followed by two beeps, before booting. You can skip the delay by pressing [CTRL-D] to immediately boot into ChromeOS.
 
 

=== Perform a Factory Reset ===

A factory reset is not needed for a standalone setup, but must be performed prior to any dual-boot (re)install.

# Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/answer/1080595?hl=en or use the [https://chrome.google.com/webstore/detail/chromebook-recovery-utili/jndclpdbaamdhonoechobihbbiimdgai?hl=en ChromeBook Recovery Utility from the Chrome web store].

Note: Google's recovery tool can be picky about what kind/size of USB/SD media you use. If one USB stick doesn't work, try another.

# 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 - so be sure to reset them back to the 'ChromeOS + 30s default' option '''before''' performing a factory reset. If you forget to do that, you'll need to press [CTRL-D] on the developer boot screen (or before the legacy boot/SeaBIOS boot screen) in order to boot ChromeOS after performing the recovery.
 
 
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:
:*:Asus: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_panther_recovery_stable-channel_mp.bin.zip
:*: HP: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_zako_recovery_stable-channel_mp-v2.bin.zip
:*:Acer: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_mccloud_recovery_stable-channel_mp.bin.zip
:*:Dell: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_7077.95.0_tricky_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
 
 
'''Note:''' The recovery media created using Google's recovery tool works only when the ChromeBox is booted into recovery mode, which only exists when using the stock firmware. If you've flashed a custom firmware on your box (either as part of a standalone setup or otherwise), ChromeOS recovery mode doesn't exist, and attempting to boot the recovery media from SeaBIOS will not work.
 
 

== Installation, Configuration, and Updating ==

=== OS and Kodi Installation ===
Kodi can be installed on the ChromeBox in a variety of ways. The two most common are via OpenELEC or Ubuntu+Kodi, in either a standalone or dual boot configuration. This is accomplished via the ChromeBox E-Z Setup script, which must be run (at least initially) from ChromeOS.
 
The EZ setup script will facilitate everything needed to install either a dual boot setup, or install a custom firmware which allows the installation of any Linux-based OS in standalone mode.
 
To run the ChromeBox E-Z Setup script, perform the following steps:

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

:Note: the first command is curl space dash capital-L space dash capital-O space http://goo.gl/3Tfu5W.

Full instructions and a detailed explanation of the script's functions and usage can be found at the following forum thread: http://forum.kodi.tv/showthread.php?tid=194362
 
 
'''Older Kernels:''' If installing a Linux-based OS other than OpenELEC (eg, Ubuntu/Kodibuntu), you will most likely need to manually update the kernel for optimal operation. Kernel version 3.18.4 is the minimum recommended, as it has a fix for an Intel GPU bug that can cause hanging during video playback. Updating the kernel is OS-specific and beyond the scope of this wiki, but instructions are easily found by googling.
 
'''Ubuntu 15.10:''' Ubuntu Wily Werewolf (15.10) ships with Linux kernel 4.2.0, which immediately panics upon boot on Chromeboxes. To fix this, you can run an earlier kernel. Alternatively, if you're able to boot, you can disable ACPI. To do this, add "acpi=off" to the end of the commandline default line in your "/etc/default/grub: file like so:
 
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw acpi=off"
 
 
This bug is fixed in Linux kernel 4.3. When it is released, update and remove the acpi=off flag.
 
 

=== Dual Boot OS Selection ===
When dual booting with ChromeOS and OpenELEC/Ubuntu, due to the ChromeBox's firmware setup, there is no conventional boot menu. Instead, the OS selection is made via keyboard shortcuts on the developer mode boot screen (shown above): [CTRL-D] boots directly ChromeOS; [CTRL-L] boots the legacy BIOS (and whatever secondary OS is installed). The default OS and boot timeout are set using the 'Set Boot Options' feature of the EZ Setup Script.
 
 

=== Updating Kodi ===

==== OpenELEC ====

The Chromebox is, at its core, a standard 64-bit x86 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). Automatic updates won't update from a stable to a beta release, but will update stable->stable, beta->beta, and beta->stable. If the automatic update doesn't work for some reason, or you want to update to a test/nightly/beta/RC build, you can manually update using the instructions on the [http://wiki.openelec.tv/index.php?title=Updating_OpenELEC OpenELEC wiki].
 
 

=== Recommended Settings ===

==== Kodi General ====

* System-->Settings-->System: Settings Level:'''Expert'''
* System-->Settings-->System-->Video Output: Vertical blank sync:'''Let driver decide'''
* System-->Settings-->System-->Power Saving: Shutdown function:'''Suspend''' (sets IR power toggle to suspend)
* System-->Settings-->Videos-->Acceleration: Enable HQ Scalers for scalings above:'''20%'''
* System-->Settings-->Videos-->Acceleration: Use VC-1 VAAPI:'''Selected''' (de-select if you have interlaced VC-1 content)
* System-->Settings-->Videos-->Acceleration: Prefer VAAPI render method:'''Selected'''
 
Also see the video playback settings as shown in the screenshots below. Change as needed, then hit 'Set as default for all videos' to save.
 
 
==== OpenELEC Specific ====

* System-->OpenELEC-->System: Automatic Updates:'''Auto'''
* System-->OpenELEC-->Network: Wireless Networks/Active:'''Selected''' (if using WiFi)
* System-->OpenELEC-->Network: Wait for network before starting Kodi:'''Selected''' (if using a external mysql database)
* System-->OpenELEC-->Services: Enable Bluetooth:'''Selected''' (if using Bluetooth)
 
 

<gallery>
File:chromebox_video_accel_settings_1.png|ChromeBox Settings: Video/Acceleration
File:chromebox_video_playback_settings_1.png|ChromeBox Video Playback Settings (1/2)
File:chromebox_video_playback_settings_2.png|ChromeBox Video Playback Settings (2/2)
</gallery>

=== Switching between Standalone and Dual Boot configurations ===

If you have a dual boot setup and wish to switch to a standalone setup, the steps are no different than installing on a "fresh" system, though you can obviously skip the steps you have already performed (removing the write-protect screw, putting the box in developer mode). If you have an OpenELEC dual boot setup and are switching to an OpenELEC standalone setup, then you can backup your settings etc using the built-in tools, copy to another PC/USB, and restore after performing the standalone setup.

If you have a standalone setup and wish to switch to a dual boot setup, you need to first [[Chromebox#Restoring_the_Stock_Firmware|restore the stock firmware]], then [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], after which you can continue with the dual boot setup.
 
 

== Recommended Accessories / Hardware Upgrades ==
 
For most users, there's no need to upgrade the ChromeBox's RAM or HDD; OpenELEC uses minimal RAM and disk space, and there's no benefit to upgrading. However, users who opt for a full Ubuntu/Kodibuntu setup, and plan on running lots of background processes etc, may find it beneficial to install additional RAM or upgrade to a larger SSD.
 
 
'''RAM:'''
: The ChromeBox has two (2) 204-Pin SODIMM slots (HP models only have one), 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)
:* HP H6Y75AA (4GB, 1.35v)
: 
: 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 2242 M.2 SATA SSD (22mm x 42mm); stock is a 16GB unit (usually Sandisk or Kensington). Any M.2 SATA 2242 replacement drive should work without issue.
 
'''Remote Controls:'''
: The ChromeBox does not have a built-in IR sensor, and must therefore use a USB IR receiver (or a Bluetooth remote). In general, any remote/receiver listed on the Kodi wiki as fully working under Linux should be fine, though some have issues when connected to USB3 ports. 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)
:* Sony IR receiver model PCVA-IR8U (MCE/eHome)
:* HP IR remote/receiver kit [http://www.amazon.com/dp/B00AYE6JDO/ OVU400102/71] (MCE/eHome, includes 5187-4593 receiver)
:* Ortek IR remote/receiver kit [http://www.amazon.com/dp/B00224ZDFY/ VRC-1100] (MCE clone, receiver also works well w/Logitech Harmony remotes)
:* Rosewill RHRC-11002 remote (MCE clone, includes receiver model IR605)
:* Rosewill WMC RRC-127 remote/receiver
:* Microsoft XBOX 360 IR remote (with MCE/eHome receiver or Flirc)
:* Microsoft XBOX One IR remote (with MCE/eHome receiver or Flirc)
:* Logitech Harmony remotes (programmed as Microsoft Media Center Extender - not as a keyboard - with MCE/eHome receiver; not recommended for use with a Flirc)
:* Sony Playstation 3 (PS3) Bluetooth remote (works with built-in BT receiver)
:*: press/hold START + ENTER to pair, choose 'Trust and Connect', then hit Ok and Enable Standby after connecting
:* Logitech Harmony Smart Hub (via Bluetooth, works with built-in BT receiver, [http://forum.kodi.tv/showthread.php?tid=194362&pid=1843165#pid1843165 see forum post here])
:* Measy RC11 Android Monitor Wireless Keyboard Air Mouse Remote Controller With Gyroscope (cannot wake up Chromebox but works otherwise nicely, with keys as well as with mouse pointer at both OpenELEC and ChromeOS)
:* Amazon FireTV / Fire Stick remotes (Bluetooth)
:NOTE: If you need to re-map remote buttons, you can use the [[Add-on:Keymap Editor|Keymap Editor Add-on]] to do so.

:'''Currently non-working''':
:* HP IR receiver model 5070-2584 (MCE/eHome)
:* AVS Gear HA-IR01SV (MCE/eHome)
:* All Topseed manufactured MCE IR receivers
 
'''USB Audio Devices''':
:As the ChromeBox only has HDMI and analog audio outputs, if you need SPDIF, then either a converter or external/USB device must be used. The following devices have been tested/confirmed working:
:* [http://www.amazon.com/gp/product/B0036VO4X4/ Turtle Beach Audio Advantage Micro II ] (plug/play in both OpenELEC and Win8.1)
:* ASUS Xonar U3 USB (OpenELEC: requires un-muting the SPDIF line, see [http://openelec.tv/forum/41-supported-hardware/71023-asus-xonar-u3-usb-soundcard this forum post])
 
'''HDMI-CEC''':
:The ChromeBox does not support HDMI-CEC natively, but support can be added using an [http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx external USB CEC adapter] from Pulse-Eight. The USB CEC Adapter needs power to the USB port BEFORE there is any video out, or it simply will not pass through any video signal. There are several ways to work around this:

:* Either always leave your Chromebox on, or just put it into standby; never turn it off
:* Use an externally powered source (eg, USB hub, TV set) to power the adapter (rather than the ChromeBox itself), so it always has power
:* If you have a spare HDMI port, you actually can split video in and control in for one HDMI channel using two physical HDMI ports. The video will be connected to the main port, and that's the port you use in the HDMI config settings in {{Kodi}}, and then you simply connect the USB CEC adapter to a spare HDMI port, does not appear to matter which.
 
 

== Troubleshooting, Known Issues, Fixes/Workarounds ==

Installation, Dual Booting, USB booting:
:* 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 Kodi on a ChromeBox, or to select between OSes in a dual boot setup. The Logitech K400 is one of these, so use another keyboard to install if yours doesn't appear to be working. Most Bluetooth keyboards '''will not work''' due to the fact that they require the OS to be loaded in order to reconnect to the ChromeBox.
:*: An effort is underway on the forums to catalog which keyboards work (and which do not); the thread (which is being updated regularly) can be found here: http://forum.kodi.tv/showthread.php?tid=211797
:* Help! I'm stuck on the black SeaBIOS boot screen, with the "booting from hard disk" text displayed (and possibly a bunch of nonsensical text afterwards).
:*:This happens because SeaBIOS is trying to boot from the internal hard drive, but no bootable OS (or only ChromeOS) is installed.
::* If you have a dual boot setup, 99% of the time this is due to not having performed a factory reset prior to running the EZ Setup Script, [[Chromebox#Perform_a_Factory_Reset|as listed in the Device Prep section above]]. Simply perform the factory reset, then redo the dual boot setup using the script as before.
::* If you have a standalone setup, and are trying to boot from USB:
::*: If you see the 'Press ESC for boot menu' text but pressing it doesn't work, then the issue is your keyboard, so try using a different one.
::*: If you '''don't''' see the 'Press ESC for boot menu' text, then the issue is with your boot media, so try using a different USB flash drive.
:* Ok, I have an OS installed, but I can't boot from USB - it boots too fast!
:*: This means your USB boot media isn't being recognized, otherwise you would have 5s to press ESC and bring up the boot menu. Re-create your boot media, possibly using a different USB stick. If you're trying to boot a Linux ISO, write the ISO directly to USB (using Win32DiskImager or dd), don't use a tool like unetbootin (eg).
:* If you're getting an error similar to "It appears your computer only has 639K of low ("DOS") RAM.", then you're pressing the dual boot selection keys (CTRL-D/CTRL-L) too late in the boot sequence - they need to be pressed on the developer mode boot screen, before it boots either ChromeOS or the Legacy BIOS (SeaBIOS). On some displays, this may mean pressing them before the display comes on, particularly if you've set the boot delay to 1s.
:* If the install media created by the script doesn't work (or you forget to create it before rebooting), then you can simply download the latest stable version (or beta/RC if you'd like) from [http://openelec.tv/get-openelec OpenELEC's website here]. The ChromeBox runs the Generic 64-bit version of OpenELEC, and it's recommended that you download the diskimage version, and create the install media, as per the instructions [http://wiki.openelec.tv/index.php/HOW-TO:Installing_OpenELEC/Creating_The_Install_Key#tab=DiskImage on the OpenELEC wiki].
:* Some TVs/displays are not able to show the developer boot screen due to the resolution it uses (1024x768 @ 60Hz), in which case you'll need to use a different display to complete the initial setup steps.
:* Many TVs have overscan enabled by default, which will cut off the text display of the ChromeOS shell. Be sure to set your TV to a mode which does not overscan (varies by manufacturer - often called 'just scan', 'exact' 'pixel perfect'; some TVs require you to label the input as a PC).
:* Using a '''passive''' DisplayPort-->HDMI cable/adapter is often problematic, and can cause the video output drop out after booting. Use either a straight DP cable or straight HDMI/HDMI-->DVI cable; if you have to use a DisplayPort-->HDMI adapter, be sure it is the '''active''' type.

Color Range Selection:
:* This topic is a bit of a minefield, but [http://forum.kodi.tv/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 Kodi option 'Used limited color range' under Settings-->System-->Video Output. Use the video clip and image above as a guide.
:*: '''Note:''' If you want to output Limited color range, you are required to do the following setting as well: Settings-->Video-->Acceleration-->Prefer VAAPI Rendering: disabled/de-selected.

No Audio and/or corrupted video on Wakeup from Suspend:
:* Some displays/AVRs don't successfully handshake when resuming from suspend, leading to no audio output and/or corrupted video output until the Chromebox is rebooted.
:*: Solution: If using a universal remote, such as a Harmony, ensure that you are turning off (suspending) the ChromeBox '''before''' your AVR/TV, and turning it on (resuming) '''after''' the AVR/TV.
:*: Solution: download/enable a script that will force the ChromeBox to reset the audio/video output on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
:*::<nowiki>mkdir -p /storage/.config/sleep.d</nowiki>
:*::<nowiki>cd /storage/.config/sleep.d</nowiki>
:*::<nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/01-cbox_resume.power</nowiki>
:*::<nowiki>chmod +x 01-cbox_resume.power</nowiki>
:*: Then reboot the ChromeBox
:*: Note: If connected via the DisplayPort output, use a text editor (eg, nano) to edit the script and replace references to 'HDMI1' with 'DP1'.

High/Full fan speed on Wakeup from Suspend:
:* A change in the Linux kernel ACPI system results in the fan speed being set to high for at least 10s on resume from suspend; sometimes a reboot is required to return to normal speed.
:*: Workaroound: download/enable a script that will force the ChromeBox's fan speed back to normal on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
:*::<nowiki>mkdir -p /storage/.config/sleep.d</nowiki>
:*::<nowiki>cd /storage/.config/sleep.d</nowiki>
:*::<nowiki>curl -L -O https://dl.dropboxusercontent.com/u/98309225/02-cbox_resume.power</nowiki>
:*::<nowiki>chmod +x 02-cbox_resume.power</nowiki>
:*: Then reboot the ChromeBox

Video Playback:
:* An Intel Linux video driver bug causes intermittent freezes where the video locks up but audio keeps playing.
:*: Solution: This issue is fixed as of OpenELEC 5.0.0; users running a different Linux distro should be sure to update their kernel to 3.18.4 or 3.19.0 (or newer).

On Screen Display:
:* Some OpenELEC 6 users have reported problems with On Screen Display elements not refreshing properly. Changing System -> Settings -> System -> Video Output -> Vertical Blank Sync -> Let Driver Choose will fix the problem.

Remote Controls:
:* Most MCE IR receivers work properly now when connected to USB3 ports under Linux with kernel 3.16+ (older kernels will require a patch/fix); OpenELEC 4.0+ is fully up to date. The version of Ubuntu installed by the ChromeBox EZ setup script in a dual boot setup also includes an up-to-date kernel. However, some buggy MCE receivers still do not work properly (at all), as noted below in the Hardware/Remotes section.

:: For standalone Ubuntu (or any other distro) installs, you will need to update to a 3.16 (or later) kernel.

Unreliable Wireless Devices attached to USB 3.0 ports:
:* Use a USB extension cable to move the device as far away from the USB port as possible. USB 3.0 can cause wireless interference. [http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-interference-paper.html Intel has released a whitepaper documenting the issue.]

Power Management:
:* Suspend/resume is generally problematic with the stock firmware (dual boot setups - OpenELEC will reboot on resume), but works reliably in standalone setups running the coreboot firmware. Resume via IR remote (USB) and wake-on-lan (eg, via YATSE) work perfectly well.
:* Note: WOL only works when the ChromeBox is suspended, not fully powered off, and requires the MAC address of the box to be set (eg, in YATSE)

Windows 8/8.1/10:
:* (Updated 2015/06/08) HDMI audio works, but requires specific drivers (Intel HD graphics 9.18.10.3220 and Intel Display Audio 6.16.0.3112), otherwise HDMI audi is non-functional.
:*: Drivers are mirrored here for your convenience:
:*: [https://dl.dropboxusercontent.com/u/98309225/haswell_driver_vga_32bit.exe Windows 8/8.1/10 32-bit]
:*: [https://dl.dropboxusercontent.com/u/98309225/haswell_driver_vga_64bit.exe Windows 8/8.1/10 64-bit]
:* Bluray disc playback doesn't work, as PowerDVD and WinDVD report that the video drivers are not supported, even though they report the hardware is capable.
:* The CPU fan will shut down at boot and not come back on unless a utility like SpeedFan is used to start it. After manually starting the fan (set PWM1 to 50%), set Speedfan for automatic control and then create a shortcut for it to run at startup.
:* Windows 7 doesn't install/work, so don't ask for help with it.
:* Discussion of running Windows on a ChromeBox can be found on this forum thread: http://forum.kodi.tv/showthread.php?tid=203040

Linux Video Tearing:
:* Some users may experience screen tearing under the Linux desktop, or when watching video (e.g., Netflix). The fix for this is [https://wiki.archlinux.org/index.php/Intel_Graphics#Tear-free_video documented on the Arch Wiki], and copied here for convenience.

:: from a terminal/shell prompt:
:::<nowiki>sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf</nowiki>

:: copy/paste the following:

:::<nowiki>Section "Device"</nowiki>
::::<nowiki>Identifier "Intel Graphics"</nowiki>
::::<nowiki>Driver "intel"</nowiki>
::::<nowiki>Option "TearFree" "true"</nowiki>
:::<nowiki>EndSection</nowiki>

:: then save, exit, and reboot.

High CPU at Idle:
:* When running a Linux setup, there is high idle CPU usage with some older kernels which do not fully support the Haswell platform; be sure to update to the latest kernel available (at '''least''' 3.18.4). On some (mostly dual boot) setups, it may also be necessary to add the following kernel boot parameters to disable the TPM: tpm_tis.force=1 tpm_tis.interrupts=0

OpenELEC Fails to boot:
:* If the OS isn't shutdown cleanly, sometimes a filesystem check (fsck) will be automatically performed. In some cases, the automatic repair is unsuccessful, and an error will show:
::<nowiki>***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***</nowiki> 
::<nowiki>### Starting debugging shell... type exit to quit ###</nowiki> 
::<nowiki>sh: can't access tty; job control turned off</nowiki> 
::<nowiki>#_</nowiki> 
 
In this case, simply run fsck manually as instructed, using the following commands, hitting [enter] after each: 
 
For a standalone setup:
:<nowiki>fsck /dev/sda1</nowiki> 
:<nowiki>fsck /dev/sda2</nowiki> 
 
For a dual-boot setup:
:<nowiki>fsck /dev/sda6</nowiki> 
:<nowiki>fsck /dev/sda7</nowiki> 
 
After the fsck is run, type 'reboot' then hit [enter] and the system should boot normally.
 
 

== Firmware/BIOS Updating ==

As depicted in the overview section above, the ChromeBox's firmware consists of two main parts: the main firmware (coreboot), and the Legacy BIOS payload (SeaBIOS). Users running a dual-boot configuration only need to update the Legacy BIOS portion. Users running a standalone setup should update the custom coreboot firmware only, as it contains an updated SeaBIOS payload (which can not be updated separately).

'''NOTE''': Under normal conditions, the ChromeBox's firmware does not need to be updated after the initial install/update via the EZ Setup Script. As the old saying goes: if it ain't broke, don't fix it. Only update if you are having an issue that is specifically noted in the changelog as being addressed by a newer version.

Dual-boot users should simply boot to ChromeOS and re-download/re-run the EZ Setup Script, choosing the '''Update Legacy BIOS''' option under the Dual Boot heading.

Standalone users should also re-download/re-run the setup script, but instead choosing the '''coreboot firmware install/update''' option under the Standalone heading. As of v3.0, the script can be run under any version of Linux with a full bash shell. As OpenELEC does not have a full bash shell, OE users will need to use the (separate) standalone firmware update script, as described near the end of [http://forum.kodi.tv/showthread.php?tid=194362 the EZ Setup Script forum post].
 
 

== Resetting to Stock ==

If you have a dual boot setup, simply [[Chromebox#Perform_a_Factory_Reset|perform a factory reset]], then hit [space] on the developer mode boot screen to revert to verified boot mode. Done. (Note: be sure to use the Kodi EZ Setup Script to reset the boot options to default before doing this, or you may not be able to exit developer mode)
 
 
If you have standalone setup, it is necessary to restore the stock firmware before performing a factory reset to reload ChromeOS.
 
In order to do this, you will need to download/run the ChromeOS device Firmware Utility script and select the appropriate option from the menu. The script will give you the option to restore from either a backup file from USB (which you created before originally flashing the custom coreboot firmware) or from a generic copy extracted from Google's recovery image. Like the Kodi EZ Setup Script, this script must be run from a Linux terminal with a full bash shell; OpenELEC users will need to boot a Linux Live USB ([http://www.ubuntu.com/download/desktop Ubuntu 14.04.2 64-bit] works fine) from which to run the script. Just download the ISO of and write it to USB using Win32DiskImager (from Windows) or dd (Linux/MacOS).
 
 

* Boot the Linux live USB, then open a terminal/shell window
* Download and run the ChromeOS device Firmware Utility script using the following two commands (hit enter after typing each command):
*: <nowiki>curl -L -O https://goo.gl/1hFfO3</nowiki>
*: <nowiki>sudo bash 1hFfO3 </nowiki>

* Select option 3, Restore Stock Firmware
* Choose whether to restore from a backup file on USB or not
*: If not, select your ChromeBox model so the appropriate firmware can be downloaded
 
After restoring the stock firmware, reboot, and proceed to [[ASUS_Chromebox#Perform_a_Factory_Reset|Perform_a_Factory_Reset]] above to restore/reload ChromeOS.
 
 

==External Links==
* [http://en.wikipedia.org/wiki/Chromebox Chromebox wikipedia article]
* [https://www.google.com/work/chrome/ Google's "Chrome for Work" web page]

{{Helix updated}}

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

Amazon Fire TV

2015-03-11T05:19:00Z

Rodalpho: /* Troubleshooting */

{{Infobox information appliance
| name = Amazon Fire TV
| image = [[File:Amazon Fire TV.jpg|300px]]
| manufacturer = Amazon.com
| releasedate = 2014-04-02 (US)
| os = [[wikipedia:Fire OS|Fire OS]] 3.0 "Mojito" (Based on [[Android]])
| soc = Qualcomm Snapdragon 8064 (Snapdragon 600 Series)
| cpu = Qualcomm Krait 300, quad-core to 1.7 Ghz
| graphics = Qualcomm Adreno 320
| display = 1080p
| storage = 8 GB internal
| memory = 2 GB RAM
| connectivity = HDMI, Bluetooth 4.0, USB 2.0, Wifi (802.11n), 10/100 Ethernet, Optical audio, CEC
| dimensions = 115 × 115 × 17.5 mm (4.53 × 4.53 × 0.69 in)
}}
[[File:Amazon Fire TV ports.jpg|right|300px|Amazon Fire TV ports|thumb]]
{{mininav|[[Devices]]|[[Android]]}}

<section begin="intro" />'''Amazon Fire TV''' is an Android-based ([[wikipedia:Fire OS|Fire OS]]) set-top-box that contains a very powerful ARM processor (that can even handle some of the more heavy XBMC skins). Fire TV stands above some of the other Android-based offerings due to Amazon's strong product support and because it contains more [[10 foot interface|remote friendly]] versions of Netflix, Amazon Prime Video, and other video service clients, making it a good pairing with {{Kodi}}.<section end="intro" />

Amazon in addition recently released [[Amazon Fire TV Stick]] as a low cost version in a HDMI-stick format, and while the Amazon Fire TV Stick also uses the same Android-based ([[wikipedia:Fire OS|Fire OS]]) software platform it contains less powerful ARM processor hardware it should still technically provides all the same video playback features and capabilities as its big brother, the Amazon Fire TV, at least as far as running {{Kodi}} on it.

== Builds ==
=== Official Builds ===
'''[http://mirrors.kodi.tv/releases/android/arm/kodi-14.1-Helix-armeabi-v7a.apk Kodi v14.1 "Helix" for Android (ARM)]'''

=== Other builds ===
* '''[http://forum.xda-developers.com/showthread.php?t=2790392 elmerohueso's XBMC/Kodi builds]''' - The official build of XBMC/Kodi, modified to have Launcher functionality and [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's repo] for some other tweaks. Includes Gotham 13.1 and 13.2, and Helix 14.0 and 14.1 versions.
* '''[[SPMC]]''' - SPMC is a fork of XBMC (currently built on Gotham) and sometimes contains special fixes that are not yet in the official builds. Users who are unsure of which version to use should normally try out the official XBMC/Kodi builds first and see how it runs, and if they have issues then try SPMC.

== installing ==
Kodi can be installed on any Fire TV or Fire TV Stick. Root is not required.

{{see|HOW-TO:Install Kodi on Fire TV}}

== Bypassing Amazon Home ==
{{See|HOW-TO:Bypass Home on Fire TV}} - {{#lst:HOW-TO:Bypass Home on Fire TV|intro}}

== Launch Kodi from Recent on the FTV Home Screen ==
This process allows Kodi to show in Recent on the FireTV Home Screen. Note that Kodi will not show in the main Apps menu, only Recent.

Amazon only approves Kodi for Android mobile devices, not the FireTV. Therefore it still needs to be installed and upgraded via sideloading.

==== Procedure ====
# [http://smile.amazon.com/XBMC-Foundation-Kodi/dp/B00TWM8IBA/ "Buy" Kodi on the Amazon Store.] (It is free.)
# On the FireTV, select Settings, My Account, then Sync Amazon Content
# Now Kodi will show in Recent Apps on the FireTV Home Screen.

==== Troubleshooting ====
* Before Kodi shows in Recents, it must be recently run. If you haven't used Kodi yet, launch it from Settings, Applications first.
* You may need to restart your FireTV and sync again.
* Some users have reported that they needed to de-register and then re-register their FireTV.

== Launch Kodi from an Existing App on the FTV Home Screen ==
There is a alternative way to invoke Kodi from the FTV Home Screen using Llama. This method uses a “sacrificial” app that you have installed from Amazon that you will use to access Kodi. The app can be anything you have installed but don’t need to use; however, some apps behave better than others (some apps will enter a loop when exiting Kodi). One app that has been tested and works well for this purpose is “Classic TV”.

The advantage of this method is that using the sacrificial app you have Home Screen Access to Kodi and you can exit Kodi to the FTV Home Screen just as you would any other FTV app.

==== Prerequisites ====
# Llama side loaded on your FTV.
# The app called “Classic TV” from the Amazon app store.
# One Llama Event (described below).

==== Procedure ====
# Install / side-load Llama.
# Install “Classic TV” (or “ikono TV” in the UK) app from Amazon app store.
# Launch Llama (From FireTV - Settings > Applications > Llama > Launch Application).
# Go to EVENTS on top menu and click '+' to add a NEW EVENT.
# In your NEW EVENT select ADD CONDITION then, from the Menu select 'Active Application' and select 'Choose App’. Scroll through the list of apps until you find “Classic TV” and select this app. Doing this should return you to the Events Menu.
# Next, select ADD ACTION and select 'Run Application' from the Menu list. From here, select whatever the name of your Kodi build is. That should create your event. At this point you can also name your event to distinguish it from others.

Now when you start the “Classic TV” app from the Home Screen, it should automatically open XBMC. Feel free to experiment with other apps from the FTV app store. Just be aware that some will loop back and re-start Kodi when you try and exit Kodi to get back to the FTV Home Screen.

== Launching Android Apps within Kodi ==
[[File:FTVXbmcAndroidApps.png|350px|thumb|right]]
* In Gotham builds, it is possible to launch Android Apps from shortcuts on the main menu.
* It is recommended to use the Confluence skin, go to Programs, then Android Apps and favorite any applications you would like to launch from Kodi.
* Skins like Amber allow you place custom shortcuts on the main menu to these favorite items.
* In Frodo builds you can only launch these apps from going into Programs -> Android Apps. They will not launch when put onto the main menu.

{{-}}

NOTE: For skins that allow you to add "Favorites" to the main menu, if you add an App to favorites then uninstall that App you should make sure to remove that App from favorites first. If you uninstall an App that you have added to favorites and don't remove it from favorites first it may cause XBMC to crash.

If this happens, reinstall the App you uninstalled, then launch Kodi and remove it from favorites. This will stop Kodi from crashing.

== Copying files ==

=== Copy userdata settings (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV
;Copying from PC to Fire TV
:Copy files to Fire TV userdata folder using <code>adb push <local> <remote></code>
::*For example, to copy '''advancedsettings.xml''' from your local folder to your Fire TV XBMC userdata folder:<pre>>adb push advancedsettings.xml /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata</pre>
:::where '''org.xbmc.kodi''' is replaced with your package name such as '''tv.ouya.xbmc''' (XBMC for Ouya) or '''com.semperpax.spmc''' (SPMC)
;Copying files from Fire TV to PC
:Copy files from Fire TV userdata folder using <code>adb pull <remote> <local></code>
::*For example, to copy '''advancedsettings.xml''' from your Fire TV XBMC userdata folder to your local folder:<pre>>adb pull /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml</pre>

You can use <code>adb shell</code> to open a remote shell on the Fire TV. Use standard Linux commands such as <code>cd</code> and <code>ls</code> to navigate the file structure. Type <code>exit</code> to exit adb shell.

See [[userdata folder]] for more information on the contents of the userdata folder.

=== Update Splash Image (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV

::*If the splash image file is splash.png, you can run the following command to copy the file to Fire TV (you may need to update the folder name):

For Gotham
<pre>>adb push splash.png /sdcard/Android/data/org.xbmc.xbmc/files/.xbmc/media/splash.png</pre>

Fire TV splash images:
* Non-version specific
:*Created by elmerohueso: [http://postimg.org/image/o04tj7aad/full/ v1] [http://postimg.org/image/xad60t9qz/full/ v2]
:*[http://i59.tinypic.com/2mi409g.png Created by reaven]
*Version specific
:*[http://www.mediafire.com/view/33x6ujbuiljhycq/AFTV_splash_13.1.png Gotham 13.1 created by Tinwarble]
:*[http://www.mediafire.com/view/i8amt483inhpyz2/AFTV_splash_Helix_alpha.png Helix|Alpha created by Tinwarble]
:*[http://www.mediafire.com/view/o8twvdt9t6mnbwy/AFTV_splash_Helix_beta.png Helix|Beta created by Tinwarble]

'''Note:''' The "Non-version specific" splashscreens can also be applied using elmerohueso's "XBMC Tweaks for FTV" program addon, which is available from [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's XBMC repo].

== Controls ==

=== Bluetooth remote ===
{{big|{{note|For better button layouts, see '''[[Alternative keymaps for Fire TV remote]]'''.}} }}

{| class="prettytable"
! Button !! Global action !! Fullscreen video action
| rowspan="8" | [[File:Amazon Fire TV remote.jpg|185px]]
|-
! 3
| Directional pad:
:* Up
:* Down
:* Right
:* Left
| Directional pad:
:* Up: Next chapter or go forward 10 minutes
:* Down: Previous chapter or go back 10 minutes
:* Right: +30 seconds
:* Left: -30 seconds
|-
! 4
| Select
| On-screen-display menu
|-
! 6
| Context menu
| Playlist
|-
! 8
| Play/pause
| Play/pause
|-
! 9
| Back
| Back out of fullscreen video (does not stop playback)
|}
{{-}}

To reboot the Fire TV with the Bluetooth remote, hold Play/Pause (8) and Select (4) for 5 seconds.

=== CEC ===
People are reporting that the Amazon Fire TV has basic CEC support. [http://forum.xda-developers.com/fire-tv/help/amazon-fire-tv-xbmc-cec-functionality-t2867626 Reported] working keys are ''UP'', ''DOWN'', ''RIGHT'', ''LEFT'', ''SELECT'', ''PLAY'' and ''PAUSE'' (depending on the TV brand).

=== USB ===
USB port allows for various additional remote types, such as FLIRC, various RF dongles, etc. Most of these devices will show up as a keyboard type input.

====USB Keyboards====
* Logitech K400r, K520, K700 and K800 and DiNovo mini wireless keyboards are said to work, as reported in the forum http://forum.xbmc.org/showthread.php?tid=191109&pid=1673921#pid1673921 (and the next post).

* Logitech DiNovo Edge keyboard works, but touch pad and media keys do not work. DiNovo Edge doesn't have a menu key.

* IOGEAR GKM561R wireless keyboard/mouse combo works (although Shift/Capslock does not in 12.x, apparently an issue addressed on Gotham)

* FAVI Entertainment SmartStick Wireless Keyboard with Touchpad Mouse, FE02RF-BL

* See '''[[keyboard controls]]''' for how to control XBMC using a keyboard. Additional Fire TV controls goes as followed:
:{| class=prettytable
! Key !! Action
|-
| {{keypress|F11}} or "browser search" media key. || Voice Search ''(Does not send mic audio)''
|-
| {{keypress|F12}} || Fire TV home screen
|-
| {{keypress|Esc}} || Fire TV back button
|-
| {{keypress|Ctrl|Esc}} or "Menu" (to the right of the Windows key on the right side) || Fire TV menu button
|-
| {{keypress|Alt|Tab}} || Recent App
|-
| {{keypress|Ctrl|Alt|Delete}} || System reset
|}
{{-}}

====USB Infrared Remotes====
[http://forum.xbmc.org/showthread.php?tid=191109&pid=1677710#pid1677710 MCE (IR) remote] - 2nd generation works. Turn on the Fire TV after plugging in the IR receiver and it should work. You can also use a logitech Harmony remote to work with the IR dongle itself
=====[[Remote_Control_Reviews#Unbranded_MCE_remote|Unbranded MCE remote]]=====
Two versions, the cheaper verson is available online for around 4 dollars - [http://forum.xbmc.org/showthread.php?tid=104943 HARMONY:Chinavasio?n CVSB-983]

These work perfectly well with Amazon Fire TV and XBMC including play, stop, pause, fast forward, rewind, next chapter, previous chapter etc. The all important CONTEXT MENU button can be activated by pressing the Right Mouse Click; Home (to Amazon Fire TV home) = WWW; Back = ESC. The only button/function that will not work of course is voice search, which you'll need the original Amazon Fire TV remote for.
 
 

If programming a Harmony One (IR) remote to go with this MCE remote: 

1. Add device: Computer. Media Centre PC. Chinavision. CVSB-983. 

2. Customising buttons: all buttons work pretty well with default button settings. There are only three buttons you would need to set yourself: 

: a. Context menu = Mouse Right Click. 

: b. Home (to AmazonFireTV) = WWW. 

: c. Back = ESC. 

Up, down, left, right, select, play, stop, pause, fast forward, rewind, next track, previous track, all work fine as-is. 

If you wanted to, you can also customise the Harmony One's digit keyboard to become a your mouse direction and select tool. i.e. 5 = ENTER. 1 = mouse left down. 2 = mouse down. 3 = mouse right down. 4 = mouse left. 6 = mouse right. 7 = mouse left up. 8 = mouse up. 9 = mouse right up. etc. 

3. Unplug power from Amazon Fire TV Unit. Plug in IR reader for the MCE remote (as-is or via a USB hub is also okay). Reinsert Power. You'll be good to go. 

Additional tip: 

1. Set XBMC Power settings to exit after xx minutes of idle activity (e.g. 15 minutes). It will shutdown (properly) and return to the Amazon Fire TV home screen. 

2. Set Llama events to put the FireTV to sleep after xx minutes of idle activity (e.g. 15 minutes). 

The two combined, the unit will self shut down after xx minutes of idle activity (30 minutes using the example). 

=====[[Remote_Control_Reviews#VRC-1100 |VRC-1100]]=====
This remote is available online for about 15 dollars - [http://forum.xbmc.org/showthread.php?tid=55406 HARMONY:ortek avr-1100]

====USB Gamepads====
* Logitech F710 Wireless Gamepad (uses a small USB dongle)
* Xbox 360 wired gamepad
* Xbox 360 wireless gamepad works if you use the Wireless Gaming Receiver for Windows

====Flirc====

The rewind, fast forward, and play/pause keys on the Fire TV controller operate the same as a keyboard's media keys. Use the "Media Keys" controller in the Flirc application to set these on your remote. Netflix and Pandora on the Fire TV (and possibly other apps) do pick up the other media keys such as stop. XBMC also picks up these keys.

{{keypress|Esc}} can be used as the back button. Remapping XBMC's back to {{keypress|Esc}} would be required to use one button for both commands.

{{keypress|Menu}} (the button to the right of the Windows key on the right side on a keyboard) works as the Fire TV's menu button and does not have the issues {{keypress|Ctrl|Esc}} has. {{keypress|Ctrl|Esc}} usually results in duplicate keypresses and will sometimes act as just {{keypress|Esc}}. At this time the Flirc GUI does not have a button to map "Menu" on the "Full Keyboard" controller, but on the command line <code>flirc_util record_api 0 101</code> can be used.

{{collapse top|Basic example using a Harmony One and Flirc:}}

{| class="prettytable"
! Remote button !! Keypress !! Fire TV action !! Global action !! Fullscreen video action || rowspan="19" | [[File:Harmony firetv.jpg|220px]]
|-
! 1
| {{keypress|Menu}} || Menu || Context menu || Context menu
|-
! 2
| {{keypress|PageUp}} || N/A || Page up || Page up
|-
! 3
| {{keypress|I}} || N/A || Info || Info
|-
! 4
| {{keypress|Backspace}} || N/A || Previous menu OR Home screen || Exit full screen
|-
! 5
| {{keypress|PageDown}} || N/A || Page down || Page down
|-
! 6
| {{keypress|Up}} || Up || Up || Step forward 10min '''OR''' Next chapter
|-
! 7
| {{keypress|Left}} || Left || Left || Step back 30s
|-
! 8
| {{keypress|Enter}} || Select || Select || Player controls (OSD)
|-
! 9
| {{keypress|Right}} || Right || Right || Step forward 30s
|-
! 10
| {{keypress|Down}} || Down || Down || Step backward 10min '''OR''' Previous chapter
|-
! 11
| {{keypress|Esc}} || Back || Back || Exit full screen
|-
! 12
| Rewind media key || Rewind || Rewind || Rewind
|-
! 13
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 14
| Fast forward media key || Fast Forward || Fast forward || Fast forward
|-
! 15
| Previous media key || Previous || Previous track || Step backward 30s
|-
! 16
| Next media key || Next || Next track || Step forward 30s
|-
! 17
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 18
| Stop media key || Stop || Stop || Stop
|}
{{-}}
For this setup use the following keyboard.xml file.

<syntaxhighlight lang="xml" enclose="div">
<keymap>
<global>
<keyboard>
<key id="61656">ContextMenu</key>
<key id="61467">Back</key>
<key id="61637">FastForward</key>
<key id="61636">Rewind</key>
<backspace>PreviousMenu</backspace>
</keyboard>
</global>
<FullscreenVideo>
<keyboard>
<next_track>StepForward</next_track>
<prev_track>StepBack</prev_track>
</keyboard>
</FullscreenVideo>
</keymap>
</syntaxhighlight>
{{collapse bottom}}

Also note that the Fire TV Home button is a soft key set to {{keypress|F12}}.

Using the "Flirc, XBMC" profile in Harmony is optional. Using it will get you started with XBMC commands faster, but you will probably also need to change some of the keypresses, which can be done without changing profiles.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Fire TV. Most of these devices will show up as a [[keyboard]] type input.

====Bluetooth Gamepads====

* Nyko PlayPad Pro
* Ouya Controller

== Uninstall XBMC ==
# From the Fire TV Home screen, select '''Settings'''
# Select '''Applications'''
# Find and select your XBMC installation (it may be named "XBMC", "SPMC", or "XBMC on OUYA")
# Select '''Uninstall'''

Alternatively, you can do the uninstall over ADB with one of the following commands.

OUYA
<pre>adb uninstall tv.ouya.xbmc</pre>

SPMC
<pre>adb uninstall com.semperpax.spmc</pre>

XBMC
<pre>adb uninstall org.xbmc.xbmc</pre>

== Video guide ==

{{youtube|-hQ3e9gdsmE}}

== Known issues ==
* VC-1 / WMV9 encoded videos is currently not hardware decoded in {{kodi}} on the Amazon Fire TV box.
* USB for storage on the Fire TV box requires root access.
* Live IPTV (via multicast UDP/RTP) is currently not supported due to [http://android.stackexchange.com/questions/93396/cant-play-multicast-using-vlc-application-on-amazon-fire-tv-settop-box missing kernel support].

== Random notes ==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}

* The USB port works with keyboard and mice. If you root the Fire TV then you can also use it for other things such as storage.
* Debug information in the Fire TV's Netflix app can be accessed by pressing {{keypress|Ctrl|Alt|Shift|D}}.
* The FireTV will not go to 'sleep' when XBMC is the active application. In the Gotham builds, you may set the '''Power Saving -> Shutdown Function''' to Quit, and choose any time between 5-120 minutes. This will Exit the application after being idle, which allows the FireTV screensaver to run (the screensaver should pop up right when XBMC exits; test this by using the 5 minute Quit timer). This also appears to function correctly and allow the device to sleep even if you are using the Llama settings to always keep XBMC running.
* You can change the FTV to use non-US Time Zones by using [http://apkleecher.com/download/?dl=com.futurek.android.tzc TimeZone Changer].

== See also ==
* [[Amazon Fire TV Stick]]
* [[Android hardware]]
* [[Android]]

== Links ==
* XBMC forum thread about the Amazon Fire TV: http://forum.xbmc.org/showthread.php?tid=191109
* Amazon Fire TV product page: http://www.amazon.com/Amazon-CL1130-Fire-TV/dp/B00CX5P8FC
* iFixit teardown: http://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856
* Supported codecs: https://developer.amazon.com/sdk/asb/media-specs.html
* Wikipedia article on Amazon Fire TV: [[wikipedia:Amazon Fire TV]]
** Wikipedia article on Fire OS (Amazon's Android based OS): [[wikipedia:Fire OS]]
* Qualcomm Blog: http://www.qualcomm.com/snapdragon/blog/2014/04/02/new-amazon-fire-tv-powered-snapdragon-600-processor
* XDA Developers Fire TV forum: http://forum.xda-developers.com/fire-tv
* TechRepublic teardown: http://www.techrepublic.com/pictures/cracking-open-amazon-fire-tv/18/
* AFTVnews (News and Guides): http://www.aftvnews.com/
* Amazon Fire TV Utility App: http://goo.gl/woVu0s or http://goo.gl/lUNWaT
[[Category:HTPC]]
[[Category:Index]]
[[Category:Android]]
[[Category:ARM]]
[[Category:Fire TV|*]]

Amazon Fire TV

2015-03-11T05:18:21Z

Rodalpho: /* Troubleshooting */

{{Infobox information appliance
| name = Amazon Fire TV
| image = [[File:Amazon Fire TV.jpg|300px]]
| manufacturer = Amazon.com
| releasedate = 2014-04-02 (US)
| os = [[wikipedia:Fire OS|Fire OS]] 3.0 "Mojito" (Based on [[Android]])
| soc = Qualcomm Snapdragon 8064 (Snapdragon 600 Series)
| cpu = Qualcomm Krait 300, quad-core to 1.7 Ghz
| graphics = Qualcomm Adreno 320
| display = 1080p
| storage = 8 GB internal
| memory = 2 GB RAM
| connectivity = HDMI, Bluetooth 4.0, USB 2.0, Wifi (802.11n), 10/100 Ethernet, Optical audio, CEC
| dimensions = 115 × 115 × 17.5 mm (4.53 × 4.53 × 0.69 in)
}}
[[File:Amazon Fire TV ports.jpg|right|300px|Amazon Fire TV ports|thumb]]
{{mininav|[[Devices]]|[[Android]]}}

<section begin="intro" />'''Amazon Fire TV''' is an Android-based ([[wikipedia:Fire OS|Fire OS]]) set-top-box that contains a very powerful ARM processor (that can even handle some of the more heavy XBMC skins). Fire TV stands above some of the other Android-based offerings due to Amazon's strong product support and because it contains more [[10 foot interface|remote friendly]] versions of Netflix, Amazon Prime Video, and other video service clients, making it a good pairing with {{Kodi}}.<section end="intro" />

Amazon in addition recently released [[Amazon Fire TV Stick]] as a low cost version in a HDMI-stick format, and while the Amazon Fire TV Stick also uses the same Android-based ([[wikipedia:Fire OS|Fire OS]]) software platform it contains less powerful ARM processor hardware it should still technically provides all the same video playback features and capabilities as its big brother, the Amazon Fire TV, at least as far as running {{Kodi}} on it.

== Builds ==
=== Official Builds ===
'''[http://mirrors.kodi.tv/releases/android/arm/kodi-14.1-Helix-armeabi-v7a.apk Kodi v14.1 "Helix" for Android (ARM)]'''

=== Other builds ===
* '''[http://forum.xda-developers.com/showthread.php?t=2790392 elmerohueso's XBMC/Kodi builds]''' - The official build of XBMC/Kodi, modified to have Launcher functionality and [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's repo] for some other tweaks. Includes Gotham 13.1 and 13.2, and Helix 14.0 and 14.1 versions.
* '''[[SPMC]]''' - SPMC is a fork of XBMC (currently built on Gotham) and sometimes contains special fixes that are not yet in the official builds. Users who are unsure of which version to use should normally try out the official XBMC/Kodi builds first and see how it runs, and if they have issues then try SPMC.

== installing ==
Kodi can be installed on any Fire TV or Fire TV Stick. Root is not required.

{{see|HOW-TO:Install Kodi on Fire TV}}

== Bypassing Amazon Home ==
{{See|HOW-TO:Bypass Home on Fire TV}} - {{#lst:HOW-TO:Bypass Home on Fire TV|intro}}

== Launch Kodi from Recent on the FTV Home Screen ==
This process allows Kodi to show in Recent on the FireTV Home Screen. Note that Kodi will not show in the main Apps menu, only Recent.

Amazon only approves Kodi for Android mobile devices, not the FireTV. Therefore it still needs to be installed and upgraded via sideloading.

==== Procedure ====
# [http://smile.amazon.com/XBMC-Foundation-Kodi/dp/B00TWM8IBA/ "Buy" Kodi on the Amazon Store.] (It is free.)
# On the FireTV, select Settings, My Account, then Sync Amazon Content
# Now Kodi will show in Recent Apps on the FireTV Home Screen.

==== Troubleshooting ====
* Before Kodi shows in Recents, it must be recently run. If you haven't used Kodi yet, launch it from Settings, Applications first.
* You may need to restart your FireTV and sync again for Kodi to show in Recents.
* Some users have reported that they needed to de-register and then re-register their FireTV for Kodi to show in Recents.

== Launch Kodi from an Existing App on the FTV Home Screen ==
There is a alternative way to invoke Kodi from the FTV Home Screen using Llama. This method uses a “sacrificial” app that you have installed from Amazon that you will use to access Kodi. The app can be anything you have installed but don’t need to use; however, some apps behave better than others (some apps will enter a loop when exiting Kodi). One app that has been tested and works well for this purpose is “Classic TV”.

The advantage of this method is that using the sacrificial app you have Home Screen Access to Kodi and you can exit Kodi to the FTV Home Screen just as you would any other FTV app.

==== Prerequisites ====
# Llama side loaded on your FTV.
# The app called “Classic TV” from the Amazon app store.
# One Llama Event (described below).

==== Procedure ====
# Install / side-load Llama.
# Install “Classic TV” (or “ikono TV” in the UK) app from Amazon app store.
# Launch Llama (From FireTV - Settings > Applications > Llama > Launch Application).
# Go to EVENTS on top menu and click '+' to add a NEW EVENT.
# In your NEW EVENT select ADD CONDITION then, from the Menu select 'Active Application' and select 'Choose App’. Scroll through the list of apps until you find “Classic TV” and select this app. Doing this should return you to the Events Menu.
# Next, select ADD ACTION and select 'Run Application' from the Menu list. From here, select whatever the name of your Kodi build is. That should create your event. At this point you can also name your event to distinguish it from others.

Now when you start the “Classic TV” app from the Home Screen, it should automatically open XBMC. Feel free to experiment with other apps from the FTV app store. Just be aware that some will loop back and re-start Kodi when you try and exit Kodi to get back to the FTV Home Screen.

== Launching Android Apps within Kodi ==
[[File:FTVXbmcAndroidApps.png|350px|thumb|right]]
* In Gotham builds, it is possible to launch Android Apps from shortcuts on the main menu.
* It is recommended to use the Confluence skin, go to Programs, then Android Apps and favorite any applications you would like to launch from Kodi.
* Skins like Amber allow you place custom shortcuts on the main menu to these favorite items.
* In Frodo builds you can only launch these apps from going into Programs -> Android Apps. They will not launch when put onto the main menu.

{{-}}

NOTE: For skins that allow you to add "Favorites" to the main menu, if you add an App to favorites then uninstall that App you should make sure to remove that App from favorites first. If you uninstall an App that you have added to favorites and don't remove it from favorites first it may cause XBMC to crash.

If this happens, reinstall the App you uninstalled, then launch Kodi and remove it from favorites. This will stop Kodi from crashing.

== Copying files ==

=== Copy userdata settings (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV
;Copying from PC to Fire TV
:Copy files to Fire TV userdata folder using <code>adb push <local> <remote></code>
::*For example, to copy '''advancedsettings.xml''' from your local folder to your Fire TV XBMC userdata folder:<pre>>adb push advancedsettings.xml /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata</pre>
:::where '''org.xbmc.kodi''' is replaced with your package name such as '''tv.ouya.xbmc''' (XBMC for Ouya) or '''com.semperpax.spmc''' (SPMC)
;Copying files from Fire TV to PC
:Copy files from Fire TV userdata folder using <code>adb pull <remote> <local></code>
::*For example, to copy '''advancedsettings.xml''' from your Fire TV XBMC userdata folder to your local folder:<pre>>adb pull /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml</pre>

You can use <code>adb shell</code> to open a remote shell on the Fire TV. Use standard Linux commands such as <code>cd</code> and <code>ls</code> to navigate the file structure. Type <code>exit</code> to exit adb shell.

See [[userdata folder]] for more information on the contents of the userdata folder.

=== Update Splash Image (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV

::*If the splash image file is splash.png, you can run the following command to copy the file to Fire TV (you may need to update the folder name):

For Gotham
<pre>>adb push splash.png /sdcard/Android/data/org.xbmc.xbmc/files/.xbmc/media/splash.png</pre>

Fire TV splash images:
* Non-version specific
:*Created by elmerohueso: [http://postimg.org/image/o04tj7aad/full/ v1] [http://postimg.org/image/xad60t9qz/full/ v2]
:*[http://i59.tinypic.com/2mi409g.png Created by reaven]
*Version specific
:*[http://www.mediafire.com/view/33x6ujbuiljhycq/AFTV_splash_13.1.png Gotham 13.1 created by Tinwarble]
:*[http://www.mediafire.com/view/i8amt483inhpyz2/AFTV_splash_Helix_alpha.png Helix|Alpha created by Tinwarble]
:*[http://www.mediafire.com/view/o8twvdt9t6mnbwy/AFTV_splash_Helix_beta.png Helix|Beta created by Tinwarble]

'''Note:''' The "Non-version specific" splashscreens can also be applied using elmerohueso's "XBMC Tweaks for FTV" program addon, which is available from [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's XBMC repo].

== Controls ==

=== Bluetooth remote ===
{{big|{{note|For better button layouts, see '''[[Alternative keymaps for Fire TV remote]]'''.}} }}

{| class="prettytable"
! Button !! Global action !! Fullscreen video action
| rowspan="8" | [[File:Amazon Fire TV remote.jpg|185px]]
|-
! 3
| Directional pad:
:* Up
:* Down
:* Right
:* Left
| Directional pad:
:* Up: Next chapter or go forward 10 minutes
:* Down: Previous chapter or go back 10 minutes
:* Right: +30 seconds
:* Left: -30 seconds
|-
! 4
| Select
| On-screen-display menu
|-
! 6
| Context menu
| Playlist
|-
! 8
| Play/pause
| Play/pause
|-
! 9
| Back
| Back out of fullscreen video (does not stop playback)
|}
{{-}}

To reboot the Fire TV with the Bluetooth remote, hold Play/Pause (8) and Select (4) for 5 seconds.

=== CEC ===
People are reporting that the Amazon Fire TV has basic CEC support. [http://forum.xda-developers.com/fire-tv/help/amazon-fire-tv-xbmc-cec-functionality-t2867626 Reported] working keys are ''UP'', ''DOWN'', ''RIGHT'', ''LEFT'', ''SELECT'', ''PLAY'' and ''PAUSE'' (depending on the TV brand).

=== USB ===
USB port allows for various additional remote types, such as FLIRC, various RF dongles, etc. Most of these devices will show up as a keyboard type input.

====USB Keyboards====
* Logitech K400r, K520, K700 and K800 and DiNovo mini wireless keyboards are said to work, as reported in the forum http://forum.xbmc.org/showthread.php?tid=191109&pid=1673921#pid1673921 (and the next post).

* Logitech DiNovo Edge keyboard works, but touch pad and media keys do not work. DiNovo Edge doesn't have a menu key.

* IOGEAR GKM561R wireless keyboard/mouse combo works (although Shift/Capslock does not in 12.x, apparently an issue addressed on Gotham)

* FAVI Entertainment SmartStick Wireless Keyboard with Touchpad Mouse, FE02RF-BL

* See '''[[keyboard controls]]''' for how to control XBMC using a keyboard. Additional Fire TV controls goes as followed:
:{| class=prettytable
! Key !! Action
|-
| {{keypress|F11}} or "browser search" media key. || Voice Search ''(Does not send mic audio)''
|-
| {{keypress|F12}} || Fire TV home screen
|-
| {{keypress|Esc}} || Fire TV back button
|-
| {{keypress|Ctrl|Esc}} or "Menu" (to the right of the Windows key on the right side) || Fire TV menu button
|-
| {{keypress|Alt|Tab}} || Recent App
|-
| {{keypress|Ctrl|Alt|Delete}} || System reset
|}
{{-}}

====USB Infrared Remotes====
[http://forum.xbmc.org/showthread.php?tid=191109&pid=1677710#pid1677710 MCE (IR) remote] - 2nd generation works. Turn on the Fire TV after plugging in the IR receiver and it should work. You can also use a logitech Harmony remote to work with the IR dongle itself
=====[[Remote_Control_Reviews#Unbranded_MCE_remote|Unbranded MCE remote]]=====
Two versions, the cheaper verson is available online for around 4 dollars - [http://forum.xbmc.org/showthread.php?tid=104943 HARMONY:Chinavasio?n CVSB-983]

These work perfectly well with Amazon Fire TV and XBMC including play, stop, pause, fast forward, rewind, next chapter, previous chapter etc. The all important CONTEXT MENU button can be activated by pressing the Right Mouse Click; Home (to Amazon Fire TV home) = WWW; Back = ESC. The only button/function that will not work of course is voice search, which you'll need the original Amazon Fire TV remote for.
 
 

If programming a Harmony One (IR) remote to go with this MCE remote: 

1. Add device: Computer. Media Centre PC. Chinavision. CVSB-983. 

2. Customising buttons: all buttons work pretty well with default button settings. There are only three buttons you would need to set yourself: 

: a. Context menu = Mouse Right Click. 

: b. Home (to AmazonFireTV) = WWW. 

: c. Back = ESC. 

Up, down, left, right, select, play, stop, pause, fast forward, rewind, next track, previous track, all work fine as-is. 

If you wanted to, you can also customise the Harmony One's digit keyboard to become a your mouse direction and select tool. i.e. 5 = ENTER. 1 = mouse left down. 2 = mouse down. 3 = mouse right down. 4 = mouse left. 6 = mouse right. 7 = mouse left up. 8 = mouse up. 9 = mouse right up. etc. 

3. Unplug power from Amazon Fire TV Unit. Plug in IR reader for the MCE remote (as-is or via a USB hub is also okay). Reinsert Power. You'll be good to go. 

Additional tip: 

1. Set XBMC Power settings to exit after xx minutes of idle activity (e.g. 15 minutes). It will shutdown (properly) and return to the Amazon Fire TV home screen. 

2. Set Llama events to put the FireTV to sleep after xx minutes of idle activity (e.g. 15 minutes). 

The two combined, the unit will self shut down after xx minutes of idle activity (30 minutes using the example). 

=====[[Remote_Control_Reviews#VRC-1100 |VRC-1100]]=====
This remote is available online for about 15 dollars - [http://forum.xbmc.org/showthread.php?tid=55406 HARMONY:ortek avr-1100]

====USB Gamepads====
* Logitech F710 Wireless Gamepad (uses a small USB dongle)
* Xbox 360 wired gamepad
* Xbox 360 wireless gamepad works if you use the Wireless Gaming Receiver for Windows

====Flirc====

The rewind, fast forward, and play/pause keys on the Fire TV controller operate the same as a keyboard's media keys. Use the "Media Keys" controller in the Flirc application to set these on your remote. Netflix and Pandora on the Fire TV (and possibly other apps) do pick up the other media keys such as stop. XBMC also picks up these keys.

{{keypress|Esc}} can be used as the back button. Remapping XBMC's back to {{keypress|Esc}} would be required to use one button for both commands.

{{keypress|Menu}} (the button to the right of the Windows key on the right side on a keyboard) works as the Fire TV's menu button and does not have the issues {{keypress|Ctrl|Esc}} has. {{keypress|Ctrl|Esc}} usually results in duplicate keypresses and will sometimes act as just {{keypress|Esc}}. At this time the Flirc GUI does not have a button to map "Menu" on the "Full Keyboard" controller, but on the command line <code>flirc_util record_api 0 101</code> can be used.

{{collapse top|Basic example using a Harmony One and Flirc:}}

{| class="prettytable"
! Remote button !! Keypress !! Fire TV action !! Global action !! Fullscreen video action || rowspan="19" | [[File:Harmony firetv.jpg|220px]]
|-
! 1
| {{keypress|Menu}} || Menu || Context menu || Context menu
|-
! 2
| {{keypress|PageUp}} || N/A || Page up || Page up
|-
! 3
| {{keypress|I}} || N/A || Info || Info
|-
! 4
| {{keypress|Backspace}} || N/A || Previous menu OR Home screen || Exit full screen
|-
! 5
| {{keypress|PageDown}} || N/A || Page down || Page down
|-
! 6
| {{keypress|Up}} || Up || Up || Step forward 10min '''OR''' Next chapter
|-
! 7
| {{keypress|Left}} || Left || Left || Step back 30s
|-
! 8
| {{keypress|Enter}} || Select || Select || Player controls (OSD)
|-
! 9
| {{keypress|Right}} || Right || Right || Step forward 30s
|-
! 10
| {{keypress|Down}} || Down || Down || Step backward 10min '''OR''' Previous chapter
|-
! 11
| {{keypress|Esc}} || Back || Back || Exit full screen
|-
! 12
| Rewind media key || Rewind || Rewind || Rewind
|-
! 13
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 14
| Fast forward media key || Fast Forward || Fast forward || Fast forward
|-
! 15
| Previous media key || Previous || Previous track || Step backward 30s
|-
! 16
| Next media key || Next || Next track || Step forward 30s
|-
! 17
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 18
| Stop media key || Stop || Stop || Stop
|}
{{-}}
For this setup use the following keyboard.xml file.

<syntaxhighlight lang="xml" enclose="div">
<keymap>
<global>
<keyboard>
<key id="61656">ContextMenu</key>
<key id="61467">Back</key>
<key id="61637">FastForward</key>
<key id="61636">Rewind</key>
<backspace>PreviousMenu</backspace>
</keyboard>
</global>
<FullscreenVideo>
<keyboard>
<next_track>StepForward</next_track>
<prev_track>StepBack</prev_track>
</keyboard>
</FullscreenVideo>
</keymap>
</syntaxhighlight>
{{collapse bottom}}

Also note that the Fire TV Home button is a soft key set to {{keypress|F12}}.

Using the "Flirc, XBMC" profile in Harmony is optional. Using it will get you started with XBMC commands faster, but you will probably also need to change some of the keypresses, which can be done without changing profiles.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Fire TV. Most of these devices will show up as a [[keyboard]] type input.

====Bluetooth Gamepads====

* Nyko PlayPad Pro
* Ouya Controller

== Uninstall XBMC ==
# From the Fire TV Home screen, select '''Settings'''
# Select '''Applications'''
# Find and select your XBMC installation (it may be named "XBMC", "SPMC", or "XBMC on OUYA")
# Select '''Uninstall'''

Alternatively, you can do the uninstall over ADB with one of the following commands.

OUYA
<pre>adb uninstall tv.ouya.xbmc</pre>

SPMC
<pre>adb uninstall com.semperpax.spmc</pre>

XBMC
<pre>adb uninstall org.xbmc.xbmc</pre>

== Video guide ==

{{youtube|-hQ3e9gdsmE}}

== Known issues ==
* VC-1 / WMV9 encoded videos is currently not hardware decoded in {{kodi}} on the Amazon Fire TV box.
* USB for storage on the Fire TV box requires root access.
* Live IPTV (via multicast UDP/RTP) is currently not supported due to [http://android.stackexchange.com/questions/93396/cant-play-multicast-using-vlc-application-on-amazon-fire-tv-settop-box missing kernel support].

== Random notes ==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}

* The USB port works with keyboard and mice. If you root the Fire TV then you can also use it for other things such as storage.
* Debug information in the Fire TV's Netflix app can be accessed by pressing {{keypress|Ctrl|Alt|Shift|D}}.
* The FireTV will not go to 'sleep' when XBMC is the active application. In the Gotham builds, you may set the '''Power Saving -> Shutdown Function''' to Quit, and choose any time between 5-120 minutes. This will Exit the application after being idle, which allows the FireTV screensaver to run (the screensaver should pop up right when XBMC exits; test this by using the 5 minute Quit timer). This also appears to function correctly and allow the device to sleep even if you are using the Llama settings to always keep XBMC running.
* You can change the FTV to use non-US Time Zones by using [http://apkleecher.com/download/?dl=com.futurek.android.tzc TimeZone Changer].

== See also ==
* [[Amazon Fire TV Stick]]
* [[Android hardware]]
* [[Android]]

== Links ==
* XBMC forum thread about the Amazon Fire TV: http://forum.xbmc.org/showthread.php?tid=191109
* Amazon Fire TV product page: http://www.amazon.com/Amazon-CL1130-Fire-TV/dp/B00CX5P8FC
* iFixit teardown: http://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856
* Supported codecs: https://developer.amazon.com/sdk/asb/media-specs.html
* Wikipedia article on Amazon Fire TV: [[wikipedia:Amazon Fire TV]]
** Wikipedia article on Fire OS (Amazon's Android based OS): [[wikipedia:Fire OS]]
* Qualcomm Blog: http://www.qualcomm.com/snapdragon/blog/2014/04/02/new-amazon-fire-tv-powered-snapdragon-600-processor
* XDA Developers Fire TV forum: http://forum.xda-developers.com/fire-tv
* TechRepublic teardown: http://www.techrepublic.com/pictures/cracking-open-amazon-fire-tv/18/
* AFTVnews (News and Guides): http://www.aftvnews.com/
* Amazon Fire TV Utility App: http://goo.gl/woVu0s or http://goo.gl/lUNWaT
[[Category:HTPC]]
[[Category:Index]]
[[Category:Android]]
[[Category:ARM]]
[[Category:Fire TV|*]]

Amazon Fire TV

2015-03-11T05:16:46Z

Rodalpho: /* Procedure */

{{Infobox information appliance
| name = Amazon Fire TV
| image = [[File:Amazon Fire TV.jpg|300px]]
| manufacturer = Amazon.com
| releasedate = 2014-04-02 (US)
| os = [[wikipedia:Fire OS|Fire OS]] 3.0 "Mojito" (Based on [[Android]])
| soc = Qualcomm Snapdragon 8064 (Snapdragon 600 Series)
| cpu = Qualcomm Krait 300, quad-core to 1.7 Ghz
| graphics = Qualcomm Adreno 320
| display = 1080p
| storage = 8 GB internal
| memory = 2 GB RAM
| connectivity = HDMI, Bluetooth 4.0, USB 2.0, Wifi (802.11n), 10/100 Ethernet, Optical audio, CEC
| dimensions = 115 × 115 × 17.5 mm (4.53 × 4.53 × 0.69 in)
}}
[[File:Amazon Fire TV ports.jpg|right|300px|Amazon Fire TV ports|thumb]]
{{mininav|[[Devices]]|[[Android]]}}

<section begin="intro" />'''Amazon Fire TV''' is an Android-based ([[wikipedia:Fire OS|Fire OS]]) set-top-box that contains a very powerful ARM processor (that can even handle some of the more heavy XBMC skins). Fire TV stands above some of the other Android-based offerings due to Amazon's strong product support and because it contains more [[10 foot interface|remote friendly]] versions of Netflix, Amazon Prime Video, and other video service clients, making it a good pairing with {{Kodi}}.<section end="intro" />

Amazon in addition recently released [[Amazon Fire TV Stick]] as a low cost version in a HDMI-stick format, and while the Amazon Fire TV Stick also uses the same Android-based ([[wikipedia:Fire OS|Fire OS]]) software platform it contains less powerful ARM processor hardware it should still technically provides all the same video playback features and capabilities as its big brother, the Amazon Fire TV, at least as far as running {{Kodi}} on it.

== Builds ==
=== Official Builds ===
'''[http://mirrors.kodi.tv/releases/android/arm/kodi-14.1-Helix-armeabi-v7a.apk Kodi v14.1 "Helix" for Android (ARM)]'''

=== Other builds ===
* '''[http://forum.xda-developers.com/showthread.php?t=2790392 elmerohueso's XBMC/Kodi builds]''' - The official build of XBMC/Kodi, modified to have Launcher functionality and [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's repo] for some other tweaks. Includes Gotham 13.1 and 13.2, and Helix 14.0 and 14.1 versions.
* '''[[SPMC]]''' - SPMC is a fork of XBMC (currently built on Gotham) and sometimes contains special fixes that are not yet in the official builds. Users who are unsure of which version to use should normally try out the official XBMC/Kodi builds first and see how it runs, and if they have issues then try SPMC.

== installing ==
Kodi can be installed on any Fire TV or Fire TV Stick. Root is not required.

{{see|HOW-TO:Install Kodi on Fire TV}}

== Bypassing Amazon Home ==
{{See|HOW-TO:Bypass Home on Fire TV}} - {{#lst:HOW-TO:Bypass Home on Fire TV|intro}}

== Launch Kodi from Recent on the FTV Home Screen ==
This process allows Kodi to show in Recent on the FireTV Home Screen. Note that Kodi will not show in the main Apps menu, only Recent.

Amazon only approves Kodi for Android mobile devices, not the FireTV. Therefore it still needs to be installed and upgraded via sideloading.

==== Procedure ====
# [http://smile.amazon.com/XBMC-Foundation-Kodi/dp/B00TWM8IBA/ "Buy" Kodi on the Amazon Store.] (It is free.)
# On the FireTV, select Settings, My Account, then Sync Amazon Content
# Now Kodi will show in Recent Apps on the FireTV Home Screen.

==== Troubleshooting ====
* Before Kodi shows in Recents, it needs to be recently run. You need to launch it from Settings, Applications first.
* You may need to restart your FireTV and sync again for Kodi to show in Recents.
* Some users have reported that they needed to de-register and then re-register their FireTV, but those reports are rare.

== Launch Kodi from an Existing App on the FTV Home Screen ==
There is a alternative way to invoke Kodi from the FTV Home Screen using Llama. This method uses a “sacrificial” app that you have installed from Amazon that you will use to access Kodi. The app can be anything you have installed but don’t need to use; however, some apps behave better than others (some apps will enter a loop when exiting Kodi). One app that has been tested and works well for this purpose is “Classic TV”.

The advantage of this method is that using the sacrificial app you have Home Screen Access to Kodi and you can exit Kodi to the FTV Home Screen just as you would any other FTV app.

==== Prerequisites ====
# Llama side loaded on your FTV.
# The app called “Classic TV” from the Amazon app store.
# One Llama Event (described below).

==== Procedure ====
# Install / side-load Llama.
# Install “Classic TV” (or “ikono TV” in the UK) app from Amazon app store.
# Launch Llama (From FireTV - Settings > Applications > Llama > Launch Application).
# Go to EVENTS on top menu and click '+' to add a NEW EVENT.
# In your NEW EVENT select ADD CONDITION then, from the Menu select 'Active Application' and select 'Choose App’. Scroll through the list of apps until you find “Classic TV” and select this app. Doing this should return you to the Events Menu.
# Next, select ADD ACTION and select 'Run Application' from the Menu list. From here, select whatever the name of your Kodi build is. That should create your event. At this point you can also name your event to distinguish it from others.

Now when you start the “Classic TV” app from the Home Screen, it should automatically open XBMC. Feel free to experiment with other apps from the FTV app store. Just be aware that some will loop back and re-start Kodi when you try and exit Kodi to get back to the FTV Home Screen.

== Launching Android Apps within Kodi ==
[[File:FTVXbmcAndroidApps.png|350px|thumb|right]]
* In Gotham builds, it is possible to launch Android Apps from shortcuts on the main menu.
* It is recommended to use the Confluence skin, go to Programs, then Android Apps and favorite any applications you would like to launch from Kodi.
* Skins like Amber allow you place custom shortcuts on the main menu to these favorite items.
* In Frodo builds you can only launch these apps from going into Programs -> Android Apps. They will not launch when put onto the main menu.

{{-}}

NOTE: For skins that allow you to add "Favorites" to the main menu, if you add an App to favorites then uninstall that App you should make sure to remove that App from favorites first. If you uninstall an App that you have added to favorites and don't remove it from favorites first it may cause XBMC to crash.

If this happens, reinstall the App you uninstalled, then launch Kodi and remove it from favorites. This will stop Kodi from crashing.

== Copying files ==

=== Copy userdata settings (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV
;Copying from PC to Fire TV
:Copy files to Fire TV userdata folder using <code>adb push <local> <remote></code>
::*For example, to copy '''advancedsettings.xml''' from your local folder to your Fire TV XBMC userdata folder:<pre>>adb push advancedsettings.xml /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata</pre>
:::where '''org.xbmc.kodi''' is replaced with your package name such as '''tv.ouya.xbmc''' (XBMC for Ouya) or '''com.semperpax.spmc''' (SPMC)
;Copying files from Fire TV to PC
:Copy files from Fire TV userdata folder using <code>adb pull <remote> <local></code>
::*For example, to copy '''advancedsettings.xml''' from your Fire TV XBMC userdata folder to your local folder:<pre>>adb pull /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml</pre>

You can use <code>adb shell</code> to open a remote shell on the Fire TV. Use standard Linux commands such as <code>cd</code> and <code>ls</code> to navigate the file structure. Type <code>exit</code> to exit adb shell.

See [[userdata folder]] for more information on the contents of the userdata folder.

=== Update Splash Image (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV

::*If the splash image file is splash.png, you can run the following command to copy the file to Fire TV (you may need to update the folder name):

For Gotham
<pre>>adb push splash.png /sdcard/Android/data/org.xbmc.xbmc/files/.xbmc/media/splash.png</pre>

Fire TV splash images:
* Non-version specific
:*Created by elmerohueso: [http://postimg.org/image/o04tj7aad/full/ v1] [http://postimg.org/image/xad60t9qz/full/ v2]
:*[http://i59.tinypic.com/2mi409g.png Created by reaven]
*Version specific
:*[http://www.mediafire.com/view/33x6ujbuiljhycq/AFTV_splash_13.1.png Gotham 13.1 created by Tinwarble]
:*[http://www.mediafire.com/view/i8amt483inhpyz2/AFTV_splash_Helix_alpha.png Helix|Alpha created by Tinwarble]
:*[http://www.mediafire.com/view/o8twvdt9t6mnbwy/AFTV_splash_Helix_beta.png Helix|Beta created by Tinwarble]

'''Note:''' The "Non-version specific" splashscreens can also be applied using elmerohueso's "XBMC Tweaks for FTV" program addon, which is available from [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's XBMC repo].

== Controls ==

=== Bluetooth remote ===
{{big|{{note|For better button layouts, see '''[[Alternative keymaps for Fire TV remote]]'''.}} }}

{| class="prettytable"
! Button !! Global action !! Fullscreen video action
| rowspan="8" | [[File:Amazon Fire TV remote.jpg|185px]]
|-
! 3
| Directional pad:
:* Up
:* Down
:* Right
:* Left
| Directional pad:
:* Up: Next chapter or go forward 10 minutes
:* Down: Previous chapter or go back 10 minutes
:* Right: +30 seconds
:* Left: -30 seconds
|-
! 4
| Select
| On-screen-display menu
|-
! 6
| Context menu
| Playlist
|-
! 8
| Play/pause
| Play/pause
|-
! 9
| Back
| Back out of fullscreen video (does not stop playback)
|}
{{-}}

To reboot the Fire TV with the Bluetooth remote, hold Play/Pause (8) and Select (4) for 5 seconds.

=== CEC ===
People are reporting that the Amazon Fire TV has basic CEC support. [http://forum.xda-developers.com/fire-tv/help/amazon-fire-tv-xbmc-cec-functionality-t2867626 Reported] working keys are ''UP'', ''DOWN'', ''RIGHT'', ''LEFT'', ''SELECT'', ''PLAY'' and ''PAUSE'' (depending on the TV brand).

=== USB ===
USB port allows for various additional remote types, such as FLIRC, various RF dongles, etc. Most of these devices will show up as a keyboard type input.

====USB Keyboards====
* Logitech K400r, K520, K700 and K800 and DiNovo mini wireless keyboards are said to work, as reported in the forum http://forum.xbmc.org/showthread.php?tid=191109&pid=1673921#pid1673921 (and the next post).

* Logitech DiNovo Edge keyboard works, but touch pad and media keys do not work. DiNovo Edge doesn't have a menu key.

* IOGEAR GKM561R wireless keyboard/mouse combo works (although Shift/Capslock does not in 12.x, apparently an issue addressed on Gotham)

* FAVI Entertainment SmartStick Wireless Keyboard with Touchpad Mouse, FE02RF-BL

* See '''[[keyboard controls]]''' for how to control XBMC using a keyboard. Additional Fire TV controls goes as followed:
:{| class=prettytable
! Key !! Action
|-
| {{keypress|F11}} or "browser search" media key. || Voice Search ''(Does not send mic audio)''
|-
| {{keypress|F12}} || Fire TV home screen
|-
| {{keypress|Esc}} || Fire TV back button
|-
| {{keypress|Ctrl|Esc}} or "Menu" (to the right of the Windows key on the right side) || Fire TV menu button
|-
| {{keypress|Alt|Tab}} || Recent App
|-
| {{keypress|Ctrl|Alt|Delete}} || System reset
|}
{{-}}

====USB Infrared Remotes====
[http://forum.xbmc.org/showthread.php?tid=191109&pid=1677710#pid1677710 MCE (IR) remote] - 2nd generation works. Turn on the Fire TV after plugging in the IR receiver and it should work. You can also use a logitech Harmony remote to work with the IR dongle itself
=====[[Remote_Control_Reviews#Unbranded_MCE_remote|Unbranded MCE remote]]=====
Two versions, the cheaper verson is available online for around 4 dollars - [http://forum.xbmc.org/showthread.php?tid=104943 HARMONY:Chinavasio?n CVSB-983]

These work perfectly well with Amazon Fire TV and XBMC including play, stop, pause, fast forward, rewind, next chapter, previous chapter etc. The all important CONTEXT MENU button can be activated by pressing the Right Mouse Click; Home (to Amazon Fire TV home) = WWW; Back = ESC. The only button/function that will not work of course is voice search, which you'll need the original Amazon Fire TV remote for.
 
 

If programming a Harmony One (IR) remote to go with this MCE remote: 

1. Add device: Computer. Media Centre PC. Chinavision. CVSB-983. 

2. Customising buttons: all buttons work pretty well with default button settings. There are only three buttons you would need to set yourself: 

: a. Context menu = Mouse Right Click. 

: b. Home (to AmazonFireTV) = WWW. 

: c. Back = ESC. 

Up, down, left, right, select, play, stop, pause, fast forward, rewind, next track, previous track, all work fine as-is. 

If you wanted to, you can also customise the Harmony One's digit keyboard to become a your mouse direction and select tool. i.e. 5 = ENTER. 1 = mouse left down. 2 = mouse down. 3 = mouse right down. 4 = mouse left. 6 = mouse right. 7 = mouse left up. 8 = mouse up. 9 = mouse right up. etc. 

3. Unplug power from Amazon Fire TV Unit. Plug in IR reader for the MCE remote (as-is or via a USB hub is also okay). Reinsert Power. You'll be good to go. 

Additional tip: 

1. Set XBMC Power settings to exit after xx minutes of idle activity (e.g. 15 minutes). It will shutdown (properly) and return to the Amazon Fire TV home screen. 

2. Set Llama events to put the FireTV to sleep after xx minutes of idle activity (e.g. 15 minutes). 

The two combined, the unit will self shut down after xx minutes of idle activity (30 minutes using the example). 

=====[[Remote_Control_Reviews#VRC-1100 |VRC-1100]]=====
This remote is available online for about 15 dollars - [http://forum.xbmc.org/showthread.php?tid=55406 HARMONY:ortek avr-1100]

====USB Gamepads====
* Logitech F710 Wireless Gamepad (uses a small USB dongle)
* Xbox 360 wired gamepad
* Xbox 360 wireless gamepad works if you use the Wireless Gaming Receiver for Windows

====Flirc====

The rewind, fast forward, and play/pause keys on the Fire TV controller operate the same as a keyboard's media keys. Use the "Media Keys" controller in the Flirc application to set these on your remote. Netflix and Pandora on the Fire TV (and possibly other apps) do pick up the other media keys such as stop. XBMC also picks up these keys.

{{keypress|Esc}} can be used as the back button. Remapping XBMC's back to {{keypress|Esc}} would be required to use one button for both commands.

{{keypress|Menu}} (the button to the right of the Windows key on the right side on a keyboard) works as the Fire TV's menu button and does not have the issues {{keypress|Ctrl|Esc}} has. {{keypress|Ctrl|Esc}} usually results in duplicate keypresses and will sometimes act as just {{keypress|Esc}}. At this time the Flirc GUI does not have a button to map "Menu" on the "Full Keyboard" controller, but on the command line <code>flirc_util record_api 0 101</code> can be used.

{{collapse top|Basic example using a Harmony One and Flirc:}}

{| class="prettytable"
! Remote button !! Keypress !! Fire TV action !! Global action !! Fullscreen video action || rowspan="19" | [[File:Harmony firetv.jpg|220px]]
|-
! 1
| {{keypress|Menu}} || Menu || Context menu || Context menu
|-
! 2
| {{keypress|PageUp}} || N/A || Page up || Page up
|-
! 3
| {{keypress|I}} || N/A || Info || Info
|-
! 4
| {{keypress|Backspace}} || N/A || Previous menu OR Home screen || Exit full screen
|-
! 5
| {{keypress|PageDown}} || N/A || Page down || Page down
|-
! 6
| {{keypress|Up}} || Up || Up || Step forward 10min '''OR''' Next chapter
|-
! 7
| {{keypress|Left}} || Left || Left || Step back 30s
|-
! 8
| {{keypress|Enter}} || Select || Select || Player controls (OSD)
|-
! 9
| {{keypress|Right}} || Right || Right || Step forward 30s
|-
! 10
| {{keypress|Down}} || Down || Down || Step backward 10min '''OR''' Previous chapter
|-
! 11
| {{keypress|Esc}} || Back || Back || Exit full screen
|-
! 12
| Rewind media key || Rewind || Rewind || Rewind
|-
! 13
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 14
| Fast forward media key || Fast Forward || Fast forward || Fast forward
|-
! 15
| Previous media key || Previous || Previous track || Step backward 30s
|-
! 16
| Next media key || Next || Next track || Step forward 30s
|-
! 17
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 18
| Stop media key || Stop || Stop || Stop
|}
{{-}}
For this setup use the following keyboard.xml file.

<syntaxhighlight lang="xml" enclose="div">
<keymap>
<global>
<keyboard>
<key id="61656">ContextMenu</key>
<key id="61467">Back</key>
<key id="61637">FastForward</key>
<key id="61636">Rewind</key>
<backspace>PreviousMenu</backspace>
</keyboard>
</global>
<FullscreenVideo>
<keyboard>
<next_track>StepForward</next_track>
<prev_track>StepBack</prev_track>
</keyboard>
</FullscreenVideo>
</keymap>
</syntaxhighlight>
{{collapse bottom}}

Also note that the Fire TV Home button is a soft key set to {{keypress|F12}}.

Using the "Flirc, XBMC" profile in Harmony is optional. Using it will get you started with XBMC commands faster, but you will probably also need to change some of the keypresses, which can be done without changing profiles.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Fire TV. Most of these devices will show up as a [[keyboard]] type input.

====Bluetooth Gamepads====

* Nyko PlayPad Pro
* Ouya Controller

== Uninstall XBMC ==
# From the Fire TV Home screen, select '''Settings'''
# Select '''Applications'''
# Find and select your XBMC installation (it may be named "XBMC", "SPMC", or "XBMC on OUYA")
# Select '''Uninstall'''

Alternatively, you can do the uninstall over ADB with one of the following commands.

OUYA
<pre>adb uninstall tv.ouya.xbmc</pre>

SPMC
<pre>adb uninstall com.semperpax.spmc</pre>

XBMC
<pre>adb uninstall org.xbmc.xbmc</pre>

== Video guide ==

{{youtube|-hQ3e9gdsmE}}

== Known issues ==
* VC-1 / WMV9 encoded videos is currently not hardware decoded in {{kodi}} on the Amazon Fire TV box.
* USB for storage on the Fire TV box requires root access.
* Live IPTV (via multicast UDP/RTP) is currently not supported due to [http://android.stackexchange.com/questions/93396/cant-play-multicast-using-vlc-application-on-amazon-fire-tv-settop-box missing kernel support].

== Random notes ==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}

* The USB port works with keyboard and mice. If you root the Fire TV then you can also use it for other things such as storage.
* Debug information in the Fire TV's Netflix app can be accessed by pressing {{keypress|Ctrl|Alt|Shift|D}}.
* The FireTV will not go to 'sleep' when XBMC is the active application. In the Gotham builds, you may set the '''Power Saving -> Shutdown Function''' to Quit, and choose any time between 5-120 minutes. This will Exit the application after being idle, which allows the FireTV screensaver to run (the screensaver should pop up right when XBMC exits; test this by using the 5 minute Quit timer). This also appears to function correctly and allow the device to sleep even if you are using the Llama settings to always keep XBMC running.
* You can change the FTV to use non-US Time Zones by using [http://apkleecher.com/download/?dl=com.futurek.android.tzc TimeZone Changer].

== See also ==
* [[Amazon Fire TV Stick]]
* [[Android hardware]]
* [[Android]]

== Links ==
* XBMC forum thread about the Amazon Fire TV: http://forum.xbmc.org/showthread.php?tid=191109
* Amazon Fire TV product page: http://www.amazon.com/Amazon-CL1130-Fire-TV/dp/B00CX5P8FC
* iFixit teardown: http://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856
* Supported codecs: https://developer.amazon.com/sdk/asb/media-specs.html
* Wikipedia article on Amazon Fire TV: [[wikipedia:Amazon Fire TV]]
** Wikipedia article on Fire OS (Amazon's Android based OS): [[wikipedia:Fire OS]]
* Qualcomm Blog: http://www.qualcomm.com/snapdragon/blog/2014/04/02/new-amazon-fire-tv-powered-snapdragon-600-processor
* XDA Developers Fire TV forum: http://forum.xda-developers.com/fire-tv
* TechRepublic teardown: http://www.techrepublic.com/pictures/cracking-open-amazon-fire-tv/18/
* AFTVnews (News and Guides): http://www.aftvnews.com/
* Amazon Fire TV Utility App: http://goo.gl/woVu0s or http://goo.gl/lUNWaT
[[Category:HTPC]]
[[Category:Index]]
[[Category:Android]]
[[Category:ARM]]
[[Category:Fire TV|*]]

Amazon Fire TV

2015-03-11T05:16:28Z

Rodalpho: /* Procedure */

{{Infobox information appliance
| name = Amazon Fire TV
| image = [[File:Amazon Fire TV.jpg|300px]]
| manufacturer = Amazon.com
| releasedate = 2014-04-02 (US)
| os = [[wikipedia:Fire OS|Fire OS]] 3.0 "Mojito" (Based on [[Android]])
| soc = Qualcomm Snapdragon 8064 (Snapdragon 600 Series)
| cpu = Qualcomm Krait 300, quad-core to 1.7 Ghz
| graphics = Qualcomm Adreno 320
| display = 1080p
| storage = 8 GB internal
| memory = 2 GB RAM
| connectivity = HDMI, Bluetooth 4.0, USB 2.0, Wifi (802.11n), 10/100 Ethernet, Optical audio, CEC
| dimensions = 115 × 115 × 17.5 mm (4.53 × 4.53 × 0.69 in)
}}
[[File:Amazon Fire TV ports.jpg|right|300px|Amazon Fire TV ports|thumb]]
{{mininav|[[Devices]]|[[Android]]}}

<section begin="intro" />'''Amazon Fire TV''' is an Android-based ([[wikipedia:Fire OS|Fire OS]]) set-top-box that contains a very powerful ARM processor (that can even handle some of the more heavy XBMC skins). Fire TV stands above some of the other Android-based offerings due to Amazon's strong product support and because it contains more [[10 foot interface|remote friendly]] versions of Netflix, Amazon Prime Video, and other video service clients, making it a good pairing with {{Kodi}}.<section end="intro" />

Amazon in addition recently released [[Amazon Fire TV Stick]] as a low cost version in a HDMI-stick format, and while the Amazon Fire TV Stick also uses the same Android-based ([[wikipedia:Fire OS|Fire OS]]) software platform it contains less powerful ARM processor hardware it should still technically provides all the same video playback features and capabilities as its big brother, the Amazon Fire TV, at least as far as running {{Kodi}} on it.

== Builds ==
=== Official Builds ===
'''[http://mirrors.kodi.tv/releases/android/arm/kodi-14.1-Helix-armeabi-v7a.apk Kodi v14.1 "Helix" for Android (ARM)]'''

=== Other builds ===
* '''[http://forum.xda-developers.com/showthread.php?t=2790392 elmerohueso's XBMC/Kodi builds]''' - The official build of XBMC/Kodi, modified to have Launcher functionality and [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's repo] for some other tweaks. Includes Gotham 13.1 and 13.2, and Helix 14.0 and 14.1 versions.
* '''[[SPMC]]''' - SPMC is a fork of XBMC (currently built on Gotham) and sometimes contains special fixes that are not yet in the official builds. Users who are unsure of which version to use should normally try out the official XBMC/Kodi builds first and see how it runs, and if they have issues then try SPMC.

== installing ==
Kodi can be installed on any Fire TV or Fire TV Stick. Root is not required.

{{see|HOW-TO:Install Kodi on Fire TV}}

== Bypassing Amazon Home ==
{{See|HOW-TO:Bypass Home on Fire TV}} - {{#lst:HOW-TO:Bypass Home on Fire TV|intro}}

== Launch Kodi from Recent on the FTV Home Screen ==
This process allows Kodi to show in Recent on the FireTV Home Screen. Note that Kodi will not show in the main Apps menu, only Recent.

Amazon only approves Kodi for Android mobile devices, not the FireTV. Therefore it still needs to be installed and upgraded via sideloading.

==== Procedure ====
# [http://smile.amazon.com/XBMC-Foundation-Kodi/dp/B00TWM8IBA/ "Buy" Kodi on the Amazon Store.] (It is free.)
# On the FireTV, select Settings, My Account, then Sync Amazon Content
# Now Kodi will show in Recent Apps on the FireTV Home Screen.

==== Troubleshooting ====
* Before Kodi shows in Recents, it needs to be recently run. You need to launch it from Settings, Applications first.
* You may need to restart your FireTV and sync again for Kodi to show in Recents.
* Some users have reported that they needed to de-register and then re-register their FireTV, but those reports are rare.

== Launch Kodi from an Existing App on the FTV Home Screen ==
There is a alternative way to invoke Kodi from the FTV Home Screen using Llama. This method uses a “sacrificial” app that you have installed from Amazon that you will use to access Kodi. The app can be anything you have installed but don’t need to use; however, some apps behave better than others (some apps will enter a loop when exiting Kodi). One app that has been tested and works well for this purpose is “Classic TV”.

The advantage of this method is that using the sacrificial app you have Home Screen Access to Kodi and you can exit Kodi to the FTV Home Screen just as you would any other FTV app.

==== Prerequisites ====
# Llama side loaded on your FTV.
# The app called “Classic TV” from the Amazon app store.
# One Llama Event (described below).

==== Procedure ====
# Install / side-load Llama.
# Install “Classic TV” (or “ikono TV” in the UK) app from Amazon app store.
# Launch Llama (From FireTV - Settings > Applications > Llama > Launch Application).
# Go to EVENTS on top menu and click '+' to add a NEW EVENT.
# In your NEW EVENT select ADD CONDITION then, from the Menu select 'Active Application' and select 'Choose App’. Scroll through the list of apps until you find “Classic TV” and select this app. Doing this should return you to the Events Menu.
# Next, select ADD ACTION and select 'Run Application' from the Menu list. From here, select whatever the name of your Kodi build is. That should create your event. At this point you can also name your event to distinguish it from others.

Now when you start the “Classic TV” app from the Home Screen, it should automatically open XBMC. Feel free to experiment with other apps from the FTV app store. Just be aware that some will loop back and re-start Kodi when you try and exit Kodi to get back to the FTV Home Screen.

== Launching Android Apps within Kodi ==
[[File:FTVXbmcAndroidApps.png|350px|thumb|right]]
* In Gotham builds, it is possible to launch Android Apps from shortcuts on the main menu.
* It is recommended to use the Confluence skin, go to Programs, then Android Apps and favorite any applications you would like to launch from Kodi.
* Skins like Amber allow you place custom shortcuts on the main menu to these favorite items.
* In Frodo builds you can only launch these apps from going into Programs -> Android Apps. They will not launch when put onto the main menu.

{{-}}

NOTE: For skins that allow you to add "Favorites" to the main menu, if you add an App to favorites then uninstall that App you should make sure to remove that App from favorites first. If you uninstall an App that you have added to favorites and don't remove it from favorites first it may cause XBMC to crash.

If this happens, reinstall the App you uninstalled, then launch Kodi and remove it from favorites. This will stop Kodi from crashing.

== Copying files ==

=== Copy userdata settings (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV
;Copying from PC to Fire TV
:Copy files to Fire TV userdata folder using <code>adb push <local> <remote></code>
::*For example, to copy '''advancedsettings.xml''' from your local folder to your Fire TV XBMC userdata folder:<pre>>adb push advancedsettings.xml /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata</pre>
:::where '''org.xbmc.kodi''' is replaced with your package name such as '''tv.ouya.xbmc''' (XBMC for Ouya) or '''com.semperpax.spmc''' (SPMC)
;Copying files from Fire TV to PC
:Copy files from Fire TV userdata folder using <code>adb pull <remote> <local></code>
::*For example, to copy '''advancedsettings.xml''' from your Fire TV XBMC userdata folder to your local folder:<pre>>adb pull /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml</pre>

You can use <code>adb shell</code> to open a remote shell on the Fire TV. Use standard Linux commands such as <code>cd</code> and <code>ls</code> to navigate the file structure. Type <code>exit</code> to exit adb shell.

See [[userdata folder]] for more information on the contents of the userdata folder.

=== Update Splash Image (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV

::*If the splash image file is splash.png, you can run the following command to copy the file to Fire TV (you may need to update the folder name):

For Gotham
<pre>>adb push splash.png /sdcard/Android/data/org.xbmc.xbmc/files/.xbmc/media/splash.png</pre>

Fire TV splash images:
* Non-version specific
:*Created by elmerohueso: [http://postimg.org/image/o04tj7aad/full/ v1] [http://postimg.org/image/xad60t9qz/full/ v2]
:*[http://i59.tinypic.com/2mi409g.png Created by reaven]
*Version specific
:*[http://www.mediafire.com/view/33x6ujbuiljhycq/AFTV_splash_13.1.png Gotham 13.1 created by Tinwarble]
:*[http://www.mediafire.com/view/i8amt483inhpyz2/AFTV_splash_Helix_alpha.png Helix|Alpha created by Tinwarble]
:*[http://www.mediafire.com/view/o8twvdt9t6mnbwy/AFTV_splash_Helix_beta.png Helix|Beta created by Tinwarble]

'''Note:''' The "Non-version specific" splashscreens can also be applied using elmerohueso's "XBMC Tweaks for FTV" program addon, which is available from [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's XBMC repo].

== Controls ==

=== Bluetooth remote ===
{{big|{{note|For better button layouts, see '''[[Alternative keymaps for Fire TV remote]]'''.}} }}

{| class="prettytable"
! Button !! Global action !! Fullscreen video action
| rowspan="8" | [[File:Amazon Fire TV remote.jpg|185px]]
|-
! 3
| Directional pad:
:* Up
:* Down
:* Right
:* Left
| Directional pad:
:* Up: Next chapter or go forward 10 minutes
:* Down: Previous chapter or go back 10 minutes
:* Right: +30 seconds
:* Left: -30 seconds
|-
! 4
| Select
| On-screen-display menu
|-
! 6
| Context menu
| Playlist
|-
! 8
| Play/pause
| Play/pause
|-
! 9
| Back
| Back out of fullscreen video (does not stop playback)
|}
{{-}}

To reboot the Fire TV with the Bluetooth remote, hold Play/Pause (8) and Select (4) for 5 seconds.

=== CEC ===
People are reporting that the Amazon Fire TV has basic CEC support. [http://forum.xda-developers.com/fire-tv/help/amazon-fire-tv-xbmc-cec-functionality-t2867626 Reported] working keys are ''UP'', ''DOWN'', ''RIGHT'', ''LEFT'', ''SELECT'', ''PLAY'' and ''PAUSE'' (depending on the TV brand).

=== USB ===
USB port allows for various additional remote types, such as FLIRC, various RF dongles, etc. Most of these devices will show up as a keyboard type input.

====USB Keyboards====
* Logitech K400r, K520, K700 and K800 and DiNovo mini wireless keyboards are said to work, as reported in the forum http://forum.xbmc.org/showthread.php?tid=191109&pid=1673921#pid1673921 (and the next post).

* Logitech DiNovo Edge keyboard works, but touch pad and media keys do not work. DiNovo Edge doesn't have a menu key.

* IOGEAR GKM561R wireless keyboard/mouse combo works (although Shift/Capslock does not in 12.x, apparently an issue addressed on Gotham)

* FAVI Entertainment SmartStick Wireless Keyboard with Touchpad Mouse, FE02RF-BL

* See '''[[keyboard controls]]''' for how to control XBMC using a keyboard. Additional Fire TV controls goes as followed:
:{| class=prettytable
! Key !! Action
|-
| {{keypress|F11}} or "browser search" media key. || Voice Search ''(Does not send mic audio)''
|-
| {{keypress|F12}} || Fire TV home screen
|-
| {{keypress|Esc}} || Fire TV back button
|-
| {{keypress|Ctrl|Esc}} or "Menu" (to the right of the Windows key on the right side) || Fire TV menu button
|-
| {{keypress|Alt|Tab}} || Recent App
|-
| {{keypress|Ctrl|Alt|Delete}} || System reset
|}
{{-}}

====USB Infrared Remotes====
[http://forum.xbmc.org/showthread.php?tid=191109&pid=1677710#pid1677710 MCE (IR) remote] - 2nd generation works. Turn on the Fire TV after plugging in the IR receiver and it should work. You can also use a logitech Harmony remote to work with the IR dongle itself
=====[[Remote_Control_Reviews#Unbranded_MCE_remote|Unbranded MCE remote]]=====
Two versions, the cheaper verson is available online for around 4 dollars - [http://forum.xbmc.org/showthread.php?tid=104943 HARMONY:Chinavasio?n CVSB-983]

These work perfectly well with Amazon Fire TV and XBMC including play, stop, pause, fast forward, rewind, next chapter, previous chapter etc. The all important CONTEXT MENU button can be activated by pressing the Right Mouse Click; Home (to Amazon Fire TV home) = WWW; Back = ESC. The only button/function that will not work of course is voice search, which you'll need the original Amazon Fire TV remote for.
 
 

If programming a Harmony One (IR) remote to go with this MCE remote: 

1. Add device: Computer. Media Centre PC. Chinavision. CVSB-983. 

2. Customising buttons: all buttons work pretty well with default button settings. There are only three buttons you would need to set yourself: 

: a. Context menu = Mouse Right Click. 

: b. Home (to AmazonFireTV) = WWW. 

: c. Back = ESC. 

Up, down, left, right, select, play, stop, pause, fast forward, rewind, next track, previous track, all work fine as-is. 

If you wanted to, you can also customise the Harmony One's digit keyboard to become a your mouse direction and select tool. i.e. 5 = ENTER. 1 = mouse left down. 2 = mouse down. 3 = mouse right down. 4 = mouse left. 6 = mouse right. 7 = mouse left up. 8 = mouse up. 9 = mouse right up. etc. 

3. Unplug power from Amazon Fire TV Unit. Plug in IR reader for the MCE remote (as-is or via a USB hub is also okay). Reinsert Power. You'll be good to go. 

Additional tip: 

1. Set XBMC Power settings to exit after xx minutes of idle activity (e.g. 15 minutes). It will shutdown (properly) and return to the Amazon Fire TV home screen. 

2. Set Llama events to put the FireTV to sleep after xx minutes of idle activity (e.g. 15 minutes). 

The two combined, the unit will self shut down after xx minutes of idle activity (30 minutes using the example). 

=====[[Remote_Control_Reviews#VRC-1100 |VRC-1100]]=====
This remote is available online for about 15 dollars - [http://forum.xbmc.org/showthread.php?tid=55406 HARMONY:ortek avr-1100]

====USB Gamepads====
* Logitech F710 Wireless Gamepad (uses a small USB dongle)
* Xbox 360 wired gamepad
* Xbox 360 wireless gamepad works if you use the Wireless Gaming Receiver for Windows

====Flirc====

The rewind, fast forward, and play/pause keys on the Fire TV controller operate the same as a keyboard's media keys. Use the "Media Keys" controller in the Flirc application to set these on your remote. Netflix and Pandora on the Fire TV (and possibly other apps) do pick up the other media keys such as stop. XBMC also picks up these keys.

{{keypress|Esc}} can be used as the back button. Remapping XBMC's back to {{keypress|Esc}} would be required to use one button for both commands.

{{keypress|Menu}} (the button to the right of the Windows key on the right side on a keyboard) works as the Fire TV's menu button and does not have the issues {{keypress|Ctrl|Esc}} has. {{keypress|Ctrl|Esc}} usually results in duplicate keypresses and will sometimes act as just {{keypress|Esc}}. At this time the Flirc GUI does not have a button to map "Menu" on the "Full Keyboard" controller, but on the command line <code>flirc_util record_api 0 101</code> can be used.

{{collapse top|Basic example using a Harmony One and Flirc:}}

{| class="prettytable"
! Remote button !! Keypress !! Fire TV action !! Global action !! Fullscreen video action || rowspan="19" | [[File:Harmony firetv.jpg|220px]]
|-
! 1
| {{keypress|Menu}} || Menu || Context menu || Context menu
|-
! 2
| {{keypress|PageUp}} || N/A || Page up || Page up
|-
! 3
| {{keypress|I}} || N/A || Info || Info
|-
! 4
| {{keypress|Backspace}} || N/A || Previous menu OR Home screen || Exit full screen
|-
! 5
| {{keypress|PageDown}} || N/A || Page down || Page down
|-
! 6
| {{keypress|Up}} || Up || Up || Step forward 10min '''OR''' Next chapter
|-
! 7
| {{keypress|Left}} || Left || Left || Step back 30s
|-
! 8
| {{keypress|Enter}} || Select || Select || Player controls (OSD)
|-
! 9
| {{keypress|Right}} || Right || Right || Step forward 30s
|-
! 10
| {{keypress|Down}} || Down || Down || Step backward 10min '''OR''' Previous chapter
|-
! 11
| {{keypress|Esc}} || Back || Back || Exit full screen
|-
! 12
| Rewind media key || Rewind || Rewind || Rewind
|-
! 13
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 14
| Fast forward media key || Fast Forward || Fast forward || Fast forward
|-
! 15
| Previous media key || Previous || Previous track || Step backward 30s
|-
! 16
| Next media key || Next || Next track || Step forward 30s
|-
! 17
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 18
| Stop media key || Stop || Stop || Stop
|}
{{-}}
For this setup use the following keyboard.xml file.

<syntaxhighlight lang="xml" enclose="div">
<keymap>
<global>
<keyboard>
<key id="61656">ContextMenu</key>
<key id="61467">Back</key>
<key id="61637">FastForward</key>
<key id="61636">Rewind</key>
<backspace>PreviousMenu</backspace>
</keyboard>
</global>
<FullscreenVideo>
<keyboard>
<next_track>StepForward</next_track>
<prev_track>StepBack</prev_track>
</keyboard>
</FullscreenVideo>
</keymap>
</syntaxhighlight>
{{collapse bottom}}

Also note that the Fire TV Home button is a soft key set to {{keypress|F12}}.

Using the "Flirc, XBMC" profile in Harmony is optional. Using it will get you started with XBMC commands faster, but you will probably also need to change some of the keypresses, which can be done without changing profiles.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Fire TV. Most of these devices will show up as a [[keyboard]] type input.

====Bluetooth Gamepads====

* Nyko PlayPad Pro
* Ouya Controller

== Uninstall XBMC ==
# From the Fire TV Home screen, select '''Settings'''
# Select '''Applications'''
# Find and select your XBMC installation (it may be named "XBMC", "SPMC", or "XBMC on OUYA")
# Select '''Uninstall'''

Alternatively, you can do the uninstall over ADB with one of the following commands.

OUYA
<pre>adb uninstall tv.ouya.xbmc</pre>

SPMC
<pre>adb uninstall com.semperpax.spmc</pre>

XBMC
<pre>adb uninstall org.xbmc.xbmc</pre>

== Video guide ==

{{youtube|-hQ3e9gdsmE}}

== Known issues ==
* VC-1 / WMV9 encoded videos is currently not hardware decoded in {{kodi}} on the Amazon Fire TV box.
* USB for storage on the Fire TV box requires root access.
* Live IPTV (via multicast UDP/RTP) is currently not supported due to [http://android.stackexchange.com/questions/93396/cant-play-multicast-using-vlc-application-on-amazon-fire-tv-settop-box missing kernel support].

== Random notes ==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}

* The USB port works with keyboard and mice. If you root the Fire TV then you can also use it for other things such as storage.
* Debug information in the Fire TV's Netflix app can be accessed by pressing {{keypress|Ctrl|Alt|Shift|D}}.
* The FireTV will not go to 'sleep' when XBMC is the active application. In the Gotham builds, you may set the '''Power Saving -> Shutdown Function''' to Quit, and choose any time between 5-120 minutes. This will Exit the application after being idle, which allows the FireTV screensaver to run (the screensaver should pop up right when XBMC exits; test this by using the 5 minute Quit timer). This also appears to function correctly and allow the device to sleep even if you are using the Llama settings to always keep XBMC running.
* You can change the FTV to use non-US Time Zones by using [http://apkleecher.com/download/?dl=com.futurek.android.tzc TimeZone Changer].

== See also ==
* [[Amazon Fire TV Stick]]
* [[Android hardware]]
* [[Android]]

== Links ==
* XBMC forum thread about the Amazon Fire TV: http://forum.xbmc.org/showthread.php?tid=191109
* Amazon Fire TV product page: http://www.amazon.com/Amazon-CL1130-Fire-TV/dp/B00CX5P8FC
* iFixit teardown: http://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856
* Supported codecs: https://developer.amazon.com/sdk/asb/media-specs.html
* Wikipedia article on Amazon Fire TV: [[wikipedia:Amazon Fire TV]]
** Wikipedia article on Fire OS (Amazon's Android based OS): [[wikipedia:Fire OS]]
* Qualcomm Blog: http://www.qualcomm.com/snapdragon/blog/2014/04/02/new-amazon-fire-tv-powered-snapdragon-600-processor
* XDA Developers Fire TV forum: http://forum.xda-developers.com/fire-tv
* TechRepublic teardown: http://www.techrepublic.com/pictures/cracking-open-amazon-fire-tv/18/
* AFTVnews (News and Guides): http://www.aftvnews.com/
* Amazon Fire TV Utility App: http://goo.gl/woVu0s or http://goo.gl/lUNWaT
[[Category:HTPC]]
[[Category:Index]]
[[Category:Android]]
[[Category:ARM]]
[[Category:Fire TV|*]]

Amazon Fire TV

2015-03-11T04:59:19Z

Rodalpho: /* Procedure */

{{Infobox information appliance
| name = Amazon Fire TV
| image = [[File:Amazon Fire TV.jpg|300px]]
| manufacturer = Amazon.com
| releasedate = 2014-04-02 (US)
| os = [[wikipedia:Fire OS|Fire OS]] 3.0 "Mojito" (Based on [[Android]])
| soc = Qualcomm Snapdragon 8064 (Snapdragon 600 Series)
| cpu = Qualcomm Krait 300, quad-core to 1.7 Ghz
| graphics = Qualcomm Adreno 320
| display = 1080p
| storage = 8 GB internal
| memory = 2 GB RAM
| connectivity = HDMI, Bluetooth 4.0, USB 2.0, Wifi (802.11n), 10/100 Ethernet, Optical audio, CEC
| dimensions = 115 × 115 × 17.5 mm (4.53 × 4.53 × 0.69 in)
}}
[[File:Amazon Fire TV ports.jpg|right|300px|Amazon Fire TV ports|thumb]]
{{mininav|[[Devices]]|[[Android]]}}

<section begin="intro" />'''Amazon Fire TV''' is an Android-based ([[wikipedia:Fire OS|Fire OS]]) set-top-box that contains a very powerful ARM processor (that can even handle some of the more heavy XBMC skins). Fire TV stands above some of the other Android-based offerings due to Amazon's strong product support and because it contains more [[10 foot interface|remote friendly]] versions of Netflix, Amazon Prime Video, and other video service clients, making it a good pairing with {{Kodi}}.<section end="intro" />

Amazon in addition recently released [[Amazon Fire TV Stick]] as a low cost version in a HDMI-stick format, and while the Amazon Fire TV Stick also uses the same Android-based ([[wikipedia:Fire OS|Fire OS]]) software platform it contains less powerful ARM processor hardware it should still technically provides all the same video playback features and capabilities as its big brother, the Amazon Fire TV, at least as far as running {{Kodi}} on it.

== Builds ==
=== Official Builds ===
'''[http://mirrors.kodi.tv/releases/android/arm/kodi-14.1-Helix-armeabi-v7a.apk Kodi v14.1 "Helix" for Android (ARM)]'''

=== Other builds ===
* '''[http://forum.xda-developers.com/showthread.php?t=2790392 elmerohueso's XBMC/Kodi builds]''' - The official build of XBMC/Kodi, modified to have Launcher functionality and [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's repo] for some other tweaks. Includes Gotham 13.1 and 13.2, and Helix 14.0 and 14.1 versions.
* '''[[SPMC]]''' - SPMC is a fork of XBMC (currently built on Gotham) and sometimes contains special fixes that are not yet in the official builds. Users who are unsure of which version to use should normally try out the official XBMC/Kodi builds first and see how it runs, and if they have issues then try SPMC.

== installing ==
Kodi can be installed on any Fire TV or Fire TV Stick. Root is not required.

{{see|HOW-TO:Install Kodi on Fire TV}}

== Bypassing Amazon Home ==
{{See|HOW-TO:Bypass Home on Fire TV}} - {{#lst:HOW-TO:Bypass Home on Fire TV|intro}}

== Launch Kodi from Recent on the FTV Home Screen ==
This process allows Kodi to show in Recent on the FireTV Home Screen. Note that Kodi will not show in the main Apps menu, only Recent.

Amazon only approves Kodi for Android mobile devices, not the FireTV. Therefore it still needs to be installed and upgraded via sideloading.

==== Procedure ====
# [http://smile.amazon.com/XBMC-Foundation-Kodi/dp/B00TWM8IBA/ "Buy" Kodi on the Amazon Store.] (It is free.)
# On the FireTV, select Settings, My Account, then Sync Amazon Content
# Now Kodi will show in Recent Apps on the FireTV Home Screen.

You may need to restart your FireTV and sync again for Kodi to show in Recents. Some users have reported that they needed to de-register and then re-register their FireTV, but those reports are rare.

== Launch Kodi from an Existing App on the FTV Home Screen ==
There is a alternative way to invoke Kodi from the FTV Home Screen using Llama. This method uses a “sacrificial” app that you have installed from Amazon that you will use to access Kodi. The app can be anything you have installed but don’t need to use; however, some apps behave better than others (some apps will enter a loop when exiting Kodi). One app that has been tested and works well for this purpose is “Classic TV”.

The advantage of this method is that using the sacrificial app you have Home Screen Access to Kodi and you can exit Kodi to the FTV Home Screen just as you would any other FTV app.

==== Prerequisites ====
# Llama side loaded on your FTV.
# The app called “Classic TV” from the Amazon app store.
# One Llama Event (described below).

==== Procedure ====
# Install / side-load Llama.
# Install “Classic TV” (or “ikono TV” in the UK) app from Amazon app store.
# Launch Llama (From FireTV - Settings > Applications > Llama > Launch Application).
# Go to EVENTS on top menu and click '+' to add a NEW EVENT.
# In your NEW EVENT select ADD CONDITION then, from the Menu select 'Active Application' and select 'Choose App’. Scroll through the list of apps until you find “Classic TV” and select this app. Doing this should return you to the Events Menu.
# Next, select ADD ACTION and select 'Run Application' from the Menu list. From here, select whatever the name of your Kodi build is. That should create your event. At this point you can also name your event to distinguish it from others.

Now when you start the “Classic TV” app from the Home Screen, it should automatically open XBMC. Feel free to experiment with other apps from the FTV app store. Just be aware that some will loop back and re-start Kodi when you try and exit Kodi to get back to the FTV Home Screen.

== Launching Android Apps within Kodi ==
[[File:FTVXbmcAndroidApps.png|350px|thumb|right]]
* In Gotham builds, it is possible to launch Android Apps from shortcuts on the main menu.
* It is recommended to use the Confluence skin, go to Programs, then Android Apps and favorite any applications you would like to launch from Kodi.
* Skins like Amber allow you place custom shortcuts on the main menu to these favorite items.
* In Frodo builds you can only launch these apps from going into Programs -> Android Apps. They will not launch when put onto the main menu.

{{-}}

NOTE: For skins that allow you to add "Favorites" to the main menu, if you add an App to favorites then uninstall that App you should make sure to remove that App from favorites first. If you uninstall an App that you have added to favorites and don't remove it from favorites first it may cause XBMC to crash.

If this happens, reinstall the App you uninstalled, then launch Kodi and remove it from favorites. This will stop Kodi from crashing.

== Copying files ==

=== Copy userdata settings (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV
;Copying from PC to Fire TV
:Copy files to Fire TV userdata folder using <code>adb push <local> <remote></code>
::*For example, to copy '''advancedsettings.xml''' from your local folder to your Fire TV XBMC userdata folder:<pre>>adb push advancedsettings.xml /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata</pre>
:::where '''org.xbmc.kodi''' is replaced with your package name such as '''tv.ouya.xbmc''' (XBMC for Ouya) or '''com.semperpax.spmc''' (SPMC)
;Copying files from Fire TV to PC
:Copy files from Fire TV userdata folder using <code>adb pull <remote> <local></code>
::*For example, to copy '''advancedsettings.xml''' from your Fire TV XBMC userdata folder to your local folder:<pre>>adb pull /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml</pre>

You can use <code>adb shell</code> to open a remote shell on the Fire TV. Use standard Linux commands such as <code>cd</code> and <code>ls</code> to navigate the file structure. Type <code>exit</code> to exit adb shell.

See [[userdata folder]] for more information on the contents of the userdata folder.

=== Update Splash Image (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV

::*If the splash image file is splash.png, you can run the following command to copy the file to Fire TV (you may need to update the folder name):

For Gotham
<pre>>adb push splash.png /sdcard/Android/data/org.xbmc.xbmc/files/.xbmc/media/splash.png</pre>

Fire TV splash images:
* Non-version specific
:*Created by elmerohueso: [http://postimg.org/image/o04tj7aad/full/ v1] [http://postimg.org/image/xad60t9qz/full/ v2]
:*[http://i59.tinypic.com/2mi409g.png Created by reaven]
*Version specific
:*[http://www.mediafire.com/view/33x6ujbuiljhycq/AFTV_splash_13.1.png Gotham 13.1 created by Tinwarble]
:*[http://www.mediafire.com/view/i8amt483inhpyz2/AFTV_splash_Helix_alpha.png Helix|Alpha created by Tinwarble]
:*[http://www.mediafire.com/view/o8twvdt9t6mnbwy/AFTV_splash_Helix_beta.png Helix|Beta created by Tinwarble]

'''Note:''' The "Non-version specific" splashscreens can also be applied using elmerohueso's "XBMC Tweaks for FTV" program addon, which is available from [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's XBMC repo].

== Controls ==

=== Bluetooth remote ===
{{big|{{note|For better button layouts, see '''[[Alternative keymaps for Fire TV remote]]'''.}} }}

{| class="prettytable"
! Button !! Global action !! Fullscreen video action
| rowspan="8" | [[File:Amazon Fire TV remote.jpg|185px]]
|-
! 3
| Directional pad:
:* Up
:* Down
:* Right
:* Left
| Directional pad:
:* Up: Next chapter or go forward 10 minutes
:* Down: Previous chapter or go back 10 minutes
:* Right: +30 seconds
:* Left: -30 seconds
|-
! 4
| Select
| On-screen-display menu
|-
! 6
| Context menu
| Playlist
|-
! 8
| Play/pause
| Play/pause
|-
! 9
| Back
| Back out of fullscreen video (does not stop playback)
|}
{{-}}

To reboot the Fire TV with the Bluetooth remote, hold Play/Pause (8) and Select (4) for 5 seconds.

=== CEC ===
People are reporting that the Amazon Fire TV has basic CEC support. [http://forum.xda-developers.com/fire-tv/help/amazon-fire-tv-xbmc-cec-functionality-t2867626 Reported] working keys are ''UP'', ''DOWN'', ''RIGHT'', ''LEFT'', ''SELECT'', ''PLAY'' and ''PAUSE'' (depending on the TV brand).

=== USB ===
USB port allows for various additional remote types, such as FLIRC, various RF dongles, etc. Most of these devices will show up as a keyboard type input.

====USB Keyboards====
* Logitech K400r, K520, K700 and K800 and DiNovo mini wireless keyboards are said to work, as reported in the forum http://forum.xbmc.org/showthread.php?tid=191109&pid=1673921#pid1673921 (and the next post).

* Logitech DiNovo Edge keyboard works, but touch pad and media keys do not work. DiNovo Edge doesn't have a menu key.

* IOGEAR GKM561R wireless keyboard/mouse combo works (although Shift/Capslock does not in 12.x, apparently an issue addressed on Gotham)

* FAVI Entertainment SmartStick Wireless Keyboard with Touchpad Mouse, FE02RF-BL

* See '''[[keyboard controls]]''' for how to control XBMC using a keyboard. Additional Fire TV controls goes as followed:
:{| class=prettytable
! Key !! Action
|-
| {{keypress|F11}} or "browser search" media key. || Voice Search ''(Does not send mic audio)''
|-
| {{keypress|F12}} || Fire TV home screen
|-
| {{keypress|Esc}} || Fire TV back button
|-
| {{keypress|Ctrl|Esc}} or "Menu" (to the right of the Windows key on the right side) || Fire TV menu button
|-
| {{keypress|Alt|Tab}} || Recent App
|-
| {{keypress|Ctrl|Alt|Delete}} || System reset
|}
{{-}}

====USB Infrared Remotes====
[http://forum.xbmc.org/showthread.php?tid=191109&pid=1677710#pid1677710 MCE (IR) remote] - 2nd generation works. Turn on the Fire TV after plugging in the IR receiver and it should work. You can also use a logitech Harmony remote to work with the IR dongle itself
=====[[Remote_Control_Reviews#Unbranded_MCE_remote|Unbranded MCE remote]]=====
Two versions, the cheaper verson is available online for around 4 dollars - [http://forum.xbmc.org/showthread.php?tid=104943 HARMONY:Chinavasio?n CVSB-983]

These work perfectly well with Amazon Fire TV and XBMC including play, stop, pause, fast forward, rewind, next chapter, previous chapter etc. The all important CONTEXT MENU button can be activated by pressing the Right Mouse Click; Home (to Amazon Fire TV home) = WWW; Back = ESC. The only button/function that will not work of course is voice search, which you'll need the original Amazon Fire TV remote for.
 
 

If programming a Harmony One (IR) remote to go with this MCE remote: 

1. Add device: Computer. Media Centre PC. Chinavision. CVSB-983. 

2. Customising buttons: all buttons work pretty well with default button settings. There are only three buttons you would need to set yourself: 

: a. Context menu = Mouse Right Click. 

: b. Home (to AmazonFireTV) = WWW. 

: c. Back = ESC. 

Up, down, left, right, select, play, stop, pause, fast forward, rewind, next track, previous track, all work fine as-is. 

If you wanted to, you can also customise the Harmony One's digit keyboard to become a your mouse direction and select tool. i.e. 5 = ENTER. 1 = mouse left down. 2 = mouse down. 3 = mouse right down. 4 = mouse left. 6 = mouse right. 7 = mouse left up. 8 = mouse up. 9 = mouse right up. etc. 

3. Unplug power from Amazon Fire TV Unit. Plug in IR reader for the MCE remote (as-is or via a USB hub is also okay). Reinsert Power. You'll be good to go. 

Additional tip: 

1. Set XBMC Power settings to exit after xx minutes of idle activity (e.g. 15 minutes). It will shutdown (properly) and return to the Amazon Fire TV home screen. 

2. Set Llama events to put the FireTV to sleep after xx minutes of idle activity (e.g. 15 minutes). 

The two combined, the unit will self shut down after xx minutes of idle activity (30 minutes using the example). 

=====[[Remote_Control_Reviews#VRC-1100 |VRC-1100]]=====
This remote is available online for about 15 dollars - [http://forum.xbmc.org/showthread.php?tid=55406 HARMONY:ortek avr-1100]

====USB Gamepads====
* Logitech F710 Wireless Gamepad (uses a small USB dongle)
* Xbox 360 wired gamepad
* Xbox 360 wireless gamepad works if you use the Wireless Gaming Receiver for Windows

====Flirc====

The rewind, fast forward, and play/pause keys on the Fire TV controller operate the same as a keyboard's media keys. Use the "Media Keys" controller in the Flirc application to set these on your remote. Netflix and Pandora on the Fire TV (and possibly other apps) do pick up the other media keys such as stop. XBMC also picks up these keys.

{{keypress|Esc}} can be used as the back button. Remapping XBMC's back to {{keypress|Esc}} would be required to use one button for both commands.

{{keypress|Menu}} (the button to the right of the Windows key on the right side on a keyboard) works as the Fire TV's menu button and does not have the issues {{keypress|Ctrl|Esc}} has. {{keypress|Ctrl|Esc}} usually results in duplicate keypresses and will sometimes act as just {{keypress|Esc}}. At this time the Flirc GUI does not have a button to map "Menu" on the "Full Keyboard" controller, but on the command line <code>flirc_util record_api 0 101</code> can be used.

{{collapse top|Basic example using a Harmony One and Flirc:}}

{| class="prettytable"
! Remote button !! Keypress !! Fire TV action !! Global action !! Fullscreen video action || rowspan="19" | [[File:Harmony firetv.jpg|220px]]
|-
! 1
| {{keypress|Menu}} || Menu || Context menu || Context menu
|-
! 2
| {{keypress|PageUp}} || N/A || Page up || Page up
|-
! 3
| {{keypress|I}} || N/A || Info || Info
|-
! 4
| {{keypress|Backspace}} || N/A || Previous menu OR Home screen || Exit full screen
|-
! 5
| {{keypress|PageDown}} || N/A || Page down || Page down
|-
! 6
| {{keypress|Up}} || Up || Up || Step forward 10min '''OR''' Next chapter
|-
! 7
| {{keypress|Left}} || Left || Left || Step back 30s
|-
! 8
| {{keypress|Enter}} || Select || Select || Player controls (OSD)
|-
! 9
| {{keypress|Right}} || Right || Right || Step forward 30s
|-
! 10
| {{keypress|Down}} || Down || Down || Step backward 10min '''OR''' Previous chapter
|-
! 11
| {{keypress|Esc}} || Back || Back || Exit full screen
|-
! 12
| Rewind media key || Rewind || Rewind || Rewind
|-
! 13
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 14
| Fast forward media key || Fast Forward || Fast forward || Fast forward
|-
! 15
| Previous media key || Previous || Previous track || Step backward 30s
|-
! 16
| Next media key || Next || Next track || Step forward 30s
|-
! 17
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 18
| Stop media key || Stop || Stop || Stop
|}
{{-}}
For this setup use the following keyboard.xml file.

<syntaxhighlight lang="xml" enclose="div">
<keymap>
<global>
<keyboard>
<key id="61656">ContextMenu</key>
<key id="61467">Back</key>
<key id="61637">FastForward</key>
<key id="61636">Rewind</key>
<backspace>PreviousMenu</backspace>
</keyboard>
</global>
<FullscreenVideo>
<keyboard>
<next_track>StepForward</next_track>
<prev_track>StepBack</prev_track>
</keyboard>
</FullscreenVideo>
</keymap>
</syntaxhighlight>
{{collapse bottom}}

Also note that the Fire TV Home button is a soft key set to {{keypress|F12}}.

Using the "Flirc, XBMC" profile in Harmony is optional. Using it will get you started with XBMC commands faster, but you will probably also need to change some of the keypresses, which can be done without changing profiles.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Fire TV. Most of these devices will show up as a [[keyboard]] type input.

====Bluetooth Gamepads====

* Nyko PlayPad Pro
* Ouya Controller

== Uninstall XBMC ==
# From the Fire TV Home screen, select '''Settings'''
# Select '''Applications'''
# Find and select your XBMC installation (it may be named "XBMC", "SPMC", or "XBMC on OUYA")
# Select '''Uninstall'''

Alternatively, you can do the uninstall over ADB with one of the following commands.

OUYA
<pre>adb uninstall tv.ouya.xbmc</pre>

SPMC
<pre>adb uninstall com.semperpax.spmc</pre>

XBMC
<pre>adb uninstall org.xbmc.xbmc</pre>

== Video guide ==

{{youtube|-hQ3e9gdsmE}}

== Known issues ==
* VC-1 / WMV9 encoded videos is currently not hardware decoded in {{kodi}} on the Amazon Fire TV box.
* USB for storage on the Fire TV box requires root access.
* Live IPTV (via multicast UDP/RTP) is currently not supported due to [http://android.stackexchange.com/questions/93396/cant-play-multicast-using-vlc-application-on-amazon-fire-tv-settop-box missing kernel support].

== Random notes ==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}

* The USB port works with keyboard and mice. If you root the Fire TV then you can also use it for other things such as storage.
* Debug information in the Fire TV's Netflix app can be accessed by pressing {{keypress|Ctrl|Alt|Shift|D}}.
* The FireTV will not go to 'sleep' when XBMC is the active application. In the Gotham builds, you may set the '''Power Saving -> Shutdown Function''' to Quit, and choose any time between 5-120 minutes. This will Exit the application after being idle, which allows the FireTV screensaver to run (the screensaver should pop up right when XBMC exits; test this by using the 5 minute Quit timer). This also appears to function correctly and allow the device to sleep even if you are using the Llama settings to always keep XBMC running.
* You can change the FTV to use non-US Time Zones by using [http://apkleecher.com/download/?dl=com.futurek.android.tzc TimeZone Changer].

== See also ==
* [[Amazon Fire TV Stick]]
* [[Android hardware]]
* [[Android]]

== Links ==
* XBMC forum thread about the Amazon Fire TV: http://forum.xbmc.org/showthread.php?tid=191109
* Amazon Fire TV product page: http://www.amazon.com/Amazon-CL1130-Fire-TV/dp/B00CX5P8FC
* iFixit teardown: http://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856
* Supported codecs: https://developer.amazon.com/sdk/asb/media-specs.html
* Wikipedia article on Amazon Fire TV: [[wikipedia:Amazon Fire TV]]
** Wikipedia article on Fire OS (Amazon's Android based OS): [[wikipedia:Fire OS]]
* Qualcomm Blog: http://www.qualcomm.com/snapdragon/blog/2014/04/02/new-amazon-fire-tv-powered-snapdragon-600-processor
* XDA Developers Fire TV forum: http://forum.xda-developers.com/fire-tv
* TechRepublic teardown: http://www.techrepublic.com/pictures/cracking-open-amazon-fire-tv/18/
* AFTVnews (News and Guides): http://www.aftvnews.com/
* Amazon Fire TV Utility App: http://goo.gl/woVu0s or http://goo.gl/lUNWaT
[[Category:HTPC]]
[[Category:Index]]
[[Category:Android]]
[[Category:ARM]]
[[Category:Fire TV|*]]

Amazon Fire TV

2015-03-11T04:57:06Z

Rodalpho: added new method to show Kodi on the FTV homescreen

{{Infobox information appliance
| name = Amazon Fire TV
| image = [[File:Amazon Fire TV.jpg|300px]]
| manufacturer = Amazon.com
| releasedate = 2014-04-02 (US)
| os = [[wikipedia:Fire OS|Fire OS]] 3.0 "Mojito" (Based on [[Android]])
| soc = Qualcomm Snapdragon 8064 (Snapdragon 600 Series)
| cpu = Qualcomm Krait 300, quad-core to 1.7 Ghz
| graphics = Qualcomm Adreno 320
| display = 1080p
| storage = 8 GB internal
| memory = 2 GB RAM
| connectivity = HDMI, Bluetooth 4.0, USB 2.0, Wifi (802.11n), 10/100 Ethernet, Optical audio, CEC
| dimensions = 115 × 115 × 17.5 mm (4.53 × 4.53 × 0.69 in)
}}
[[File:Amazon Fire TV ports.jpg|right|300px|Amazon Fire TV ports|thumb]]
{{mininav|[[Devices]]|[[Android]]}}

<section begin="intro" />'''Amazon Fire TV''' is an Android-based ([[wikipedia:Fire OS|Fire OS]]) set-top-box that contains a very powerful ARM processor (that can even handle some of the more heavy XBMC skins). Fire TV stands above some of the other Android-based offerings due to Amazon's strong product support and because it contains more [[10 foot interface|remote friendly]] versions of Netflix, Amazon Prime Video, and other video service clients, making it a good pairing with {{Kodi}}.<section end="intro" />

Amazon in addition recently released [[Amazon Fire TV Stick]] as a low cost version in a HDMI-stick format, and while the Amazon Fire TV Stick also uses the same Android-based ([[wikipedia:Fire OS|Fire OS]]) software platform it contains less powerful ARM processor hardware it should still technically provides all the same video playback features and capabilities as its big brother, the Amazon Fire TV, at least as far as running {{Kodi}} on it.

== Builds ==
=== Official Builds ===
'''[http://mirrors.kodi.tv/releases/android/arm/kodi-14.1-Helix-armeabi-v7a.apk Kodi v14.1 "Helix" for Android (ARM)]'''

=== Other builds ===
* '''[http://forum.xda-developers.com/showthread.php?t=2790392 elmerohueso's XBMC/Kodi builds]''' - The official build of XBMC/Kodi, modified to have Launcher functionality and [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's repo] for some other tweaks. Includes Gotham 13.1 and 13.2, and Helix 14.0 and 14.1 versions.
* '''[[SPMC]]''' - SPMC is a fork of XBMC (currently built on Gotham) and sometimes contains special fixes that are not yet in the official builds. Users who are unsure of which version to use should normally try out the official XBMC/Kodi builds first and see how it runs, and if they have issues then try SPMC.

== installing ==
Kodi can be installed on any Fire TV or Fire TV Stick. Root is not required.

{{see|HOW-TO:Install Kodi on Fire TV}}

== Bypassing Amazon Home ==
{{See|HOW-TO:Bypass Home on Fire TV}} - {{#lst:HOW-TO:Bypass Home on Fire TV|intro}}

== Launch Kodi from Recent on the FTV Home Screen ==
This process allows Kodi to show in Recent on the FireTV Home Screen. Note that Kodi will not show in the main Apps menu, only Recent.

Amazon only approves Kodi for Android mobile devices, not the FireTV. Therefore it still needs to be installed and upgraded via sideloading.

==== Procedure ====
# [http://smile.amazon.com/XBMC-Foundation-Kodi/dp/B00TWM8IBA/ "Buy" Kodi on the Amazon Store.]
# On the FireTV, select Settings, My Account, then Sync Amazon Content
# Now Kodi should show in Recent Apps on the FireTV Home Screen.

You may need to restart your FireTV and sync again to get it to show up. Some users have reported that they needed to de-register and re-register their FireTV as well, but those reports are rare.

== Launch Kodi from an Existing App on the FTV Home Screen ==
There is a alternative way to invoke Kodi from the FTV Home Screen using Llama. This method uses a “sacrificial” app that you have installed from Amazon that you will use to access Kodi. The app can be anything you have installed but don’t need to use; however, some apps behave better than others (some apps will enter a loop when exiting Kodi). One app that has been tested and works well for this purpose is “Classic TV”.

The advantage of this method is that using the sacrificial app you have Home Screen Access to Kodi and you can exit Kodi to the FTV Home Screen just as you would any other FTV app.

==== Prerequisites ====
# Llama side loaded on your FTV.
# The app called “Classic TV” from the Amazon app store.
# One Llama Event (described below).

==== Procedure ====
# Install / side-load Llama.
# Install “Classic TV” (or “ikono TV” in the UK) app from Amazon app store.
# Launch Llama (From FireTV - Settings > Applications > Llama > Launch Application).
# Go to EVENTS on top menu and click '+' to add a NEW EVENT.
# In your NEW EVENT select ADD CONDITION then, from the Menu select 'Active Application' and select 'Choose App’. Scroll through the list of apps until you find “Classic TV” and select this app. Doing this should return you to the Events Menu.
# Next, select ADD ACTION and select 'Run Application' from the Menu list. From here, select whatever the name of your Kodi build is. That should create your event. At this point you can also name your event to distinguish it from others.

Now when you start the “Classic TV” app from the Home Screen, it should automatically open XBMC. Feel free to experiment with other apps from the FTV app store. Just be aware that some will loop back and re-start Kodi when you try and exit Kodi to get back to the FTV Home Screen.

== Launching Android Apps within Kodi ==
[[File:FTVXbmcAndroidApps.png|350px|thumb|right]]
* In Gotham builds, it is possible to launch Android Apps from shortcuts on the main menu.
* It is recommended to use the Confluence skin, go to Programs, then Android Apps and favorite any applications you would like to launch from Kodi.
* Skins like Amber allow you place custom shortcuts on the main menu to these favorite items.
* In Frodo builds you can only launch these apps from going into Programs -> Android Apps. They will not launch when put onto the main menu.

{{-}}

NOTE: For skins that allow you to add "Favorites" to the main menu, if you add an App to favorites then uninstall that App you should make sure to remove that App from favorites first. If you uninstall an App that you have added to favorites and don't remove it from favorites first it may cause XBMC to crash.

If this happens, reinstall the App you uninstalled, then launch Kodi and remove it from favorites. This will stop Kodi from crashing.

== Copying files ==

=== Copy userdata settings (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV
;Copying from PC to Fire TV
:Copy files to Fire TV userdata folder using <code>adb push <local> <remote></code>
::*For example, to copy '''advancedsettings.xml''' from your local folder to your Fire TV XBMC userdata folder:<pre>>adb push advancedsettings.xml /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata</pre>
:::where '''org.xbmc.kodi''' is replaced with your package name such as '''tv.ouya.xbmc''' (XBMC for Ouya) or '''com.semperpax.spmc''' (SPMC)
;Copying files from Fire TV to PC
:Copy files from Fire TV userdata folder using <code>adb pull <remote> <local></code>
::*For example, to copy '''advancedsettings.xml''' from your Fire TV XBMC userdata folder to your local folder:<pre>>adb pull /sdcard/android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml</pre>

You can use <code>adb shell</code> to open a remote shell on the Fire TV. Use standard Linux commands such as <code>cd</code> and <code>ls</code> to navigate the file structure. Type <code>exit</code> to exit adb shell.

See [[userdata folder]] for more information on the contents of the userdata folder.

=== Update Splash Image (optional) ===

Run XBMC at least once to initialize the userdata folder on the Fire TV

::*If the splash image file is splash.png, you can run the following command to copy the file to Fire TV (you may need to update the folder name):

For Gotham
<pre>>adb push splash.png /sdcard/Android/data/org.xbmc.xbmc/files/.xbmc/media/splash.png</pre>

Fire TV splash images:
* Non-version specific
:*Created by elmerohueso: [http://postimg.org/image/o04tj7aad/full/ v1] [http://postimg.org/image/xad60t9qz/full/ v2]
:*[http://i59.tinypic.com/2mi409g.png Created by reaven]
*Version specific
:*[http://www.mediafire.com/view/33x6ujbuiljhycq/AFTV_splash_13.1.png Gotham 13.1 created by Tinwarble]
:*[http://www.mediafire.com/view/i8amt483inhpyz2/AFTV_splash_Helix_alpha.png Helix|Alpha created by Tinwarble]
:*[http://www.mediafire.com/view/o8twvdt9t6mnbwy/AFTV_splash_Helix_beta.png Helix|Beta created by Tinwarble]

'''Note:''' The "Non-version specific" splashscreens can also be applied using elmerohueso's "XBMC Tweaks for FTV" program addon, which is available from [https://github.com/elmerohueso/xbmc.repo.elmerohueso/raw/master/download/xbmc.repo.elmerohueso/xbmc.repo.elmerohueso-1.0.zip elmerohueso's XBMC repo].

== Controls ==

=== Bluetooth remote ===
{{big|{{note|For better button layouts, see '''[[Alternative keymaps for Fire TV remote]]'''.}} }}

{| class="prettytable"
! Button !! Global action !! Fullscreen video action
| rowspan="8" | [[File:Amazon Fire TV remote.jpg|185px]]
|-
! 3
| Directional pad:
:* Up
:* Down
:* Right
:* Left
| Directional pad:
:* Up: Next chapter or go forward 10 minutes
:* Down: Previous chapter or go back 10 minutes
:* Right: +30 seconds
:* Left: -30 seconds
|-
! 4
| Select
| On-screen-display menu
|-
! 6
| Context menu
| Playlist
|-
! 8
| Play/pause
| Play/pause
|-
! 9
| Back
| Back out of fullscreen video (does not stop playback)
|}
{{-}}

To reboot the Fire TV with the Bluetooth remote, hold Play/Pause (8) and Select (4) for 5 seconds.

=== CEC ===
People are reporting that the Amazon Fire TV has basic CEC support. [http://forum.xda-developers.com/fire-tv/help/amazon-fire-tv-xbmc-cec-functionality-t2867626 Reported] working keys are ''UP'', ''DOWN'', ''RIGHT'', ''LEFT'', ''SELECT'', ''PLAY'' and ''PAUSE'' (depending on the TV brand).

=== USB ===
USB port allows for various additional remote types, such as FLIRC, various RF dongles, etc. Most of these devices will show up as a keyboard type input.

====USB Keyboards====
* Logitech K400r, K520, K700 and K800 and DiNovo mini wireless keyboards are said to work, as reported in the forum http://forum.xbmc.org/showthread.php?tid=191109&pid=1673921#pid1673921 (and the next post).

* Logitech DiNovo Edge keyboard works, but touch pad and media keys do not work. DiNovo Edge doesn't have a menu key.

* IOGEAR GKM561R wireless keyboard/mouse combo works (although Shift/Capslock does not in 12.x, apparently an issue addressed on Gotham)

* FAVI Entertainment SmartStick Wireless Keyboard with Touchpad Mouse, FE02RF-BL

* See '''[[keyboard controls]]''' for how to control XBMC using a keyboard. Additional Fire TV controls goes as followed:
:{| class=prettytable
! Key !! Action
|-
| {{keypress|F11}} or "browser search" media key. || Voice Search ''(Does not send mic audio)''
|-
| {{keypress|F12}} || Fire TV home screen
|-
| {{keypress|Esc}} || Fire TV back button
|-
| {{keypress|Ctrl|Esc}} or "Menu" (to the right of the Windows key on the right side) || Fire TV menu button
|-
| {{keypress|Alt|Tab}} || Recent App
|-
| {{keypress|Ctrl|Alt|Delete}} || System reset
|}
{{-}}

====USB Infrared Remotes====
[http://forum.xbmc.org/showthread.php?tid=191109&pid=1677710#pid1677710 MCE (IR) remote] - 2nd generation works. Turn on the Fire TV after plugging in the IR receiver and it should work. You can also use a logitech Harmony remote to work with the IR dongle itself
=====[[Remote_Control_Reviews#Unbranded_MCE_remote|Unbranded MCE remote]]=====
Two versions, the cheaper verson is available online for around 4 dollars - [http://forum.xbmc.org/showthread.php?tid=104943 HARMONY:Chinavasio?n CVSB-983]

These work perfectly well with Amazon Fire TV and XBMC including play, stop, pause, fast forward, rewind, next chapter, previous chapter etc. The all important CONTEXT MENU button can be activated by pressing the Right Mouse Click; Home (to Amazon Fire TV home) = WWW; Back = ESC. The only button/function that will not work of course is voice search, which you'll need the original Amazon Fire TV remote for.
 
 

If programming a Harmony One (IR) remote to go with this MCE remote: 

1. Add device: Computer. Media Centre PC. Chinavision. CVSB-983. 

2. Customising buttons: all buttons work pretty well with default button settings. There are only three buttons you would need to set yourself: 

: a. Context menu = Mouse Right Click. 

: b. Home (to AmazonFireTV) = WWW. 

: c. Back = ESC. 

Up, down, left, right, select, play, stop, pause, fast forward, rewind, next track, previous track, all work fine as-is. 

If you wanted to, you can also customise the Harmony One's digit keyboard to become a your mouse direction and select tool. i.e. 5 = ENTER. 1 = mouse left down. 2 = mouse down. 3 = mouse right down. 4 = mouse left. 6 = mouse right. 7 = mouse left up. 8 = mouse up. 9 = mouse right up. etc. 

3. Unplug power from Amazon Fire TV Unit. Plug in IR reader for the MCE remote (as-is or via a USB hub is also okay). Reinsert Power. You'll be good to go. 

Additional tip: 

1. Set XBMC Power settings to exit after xx minutes of idle activity (e.g. 15 minutes). It will shutdown (properly) and return to the Amazon Fire TV home screen. 

2. Set Llama events to put the FireTV to sleep after xx minutes of idle activity (e.g. 15 minutes). 

The two combined, the unit will self shut down after xx minutes of idle activity (30 minutes using the example). 

=====[[Remote_Control_Reviews#VRC-1100 |VRC-1100]]=====
This remote is available online for about 15 dollars - [http://forum.xbmc.org/showthread.php?tid=55406 HARMONY:ortek avr-1100]

====USB Gamepads====
* Logitech F710 Wireless Gamepad (uses a small USB dongle)
* Xbox 360 wired gamepad
* Xbox 360 wireless gamepad works if you use the Wireless Gaming Receiver for Windows

====Flirc====

The rewind, fast forward, and play/pause keys on the Fire TV controller operate the same as a keyboard's media keys. Use the "Media Keys" controller in the Flirc application to set these on your remote. Netflix and Pandora on the Fire TV (and possibly other apps) do pick up the other media keys such as stop. XBMC also picks up these keys.

{{keypress|Esc}} can be used as the back button. Remapping XBMC's back to {{keypress|Esc}} would be required to use one button for both commands.

{{keypress|Menu}} (the button to the right of the Windows key on the right side on a keyboard) works as the Fire TV's menu button and does not have the issues {{keypress|Ctrl|Esc}} has. {{keypress|Ctrl|Esc}} usually results in duplicate keypresses and will sometimes act as just {{keypress|Esc}}. At this time the Flirc GUI does not have a button to map "Menu" on the "Full Keyboard" controller, but on the command line <code>flirc_util record_api 0 101</code> can be used.

{{collapse top|Basic example using a Harmony One and Flirc:}}

{| class="prettytable"
! Remote button !! Keypress !! Fire TV action !! Global action !! Fullscreen video action || rowspan="19" | [[File:Harmony firetv.jpg|220px]]
|-
! 1
| {{keypress|Menu}} || Menu || Context menu || Context menu
|-
! 2
| {{keypress|PageUp}} || N/A || Page up || Page up
|-
! 3
| {{keypress|I}} || N/A || Info || Info
|-
! 4
| {{keypress|Backspace}} || N/A || Previous menu OR Home screen || Exit full screen
|-
! 5
| {{keypress|PageDown}} || N/A || Page down || Page down
|-
! 6
| {{keypress|Up}} || Up || Up || Step forward 10min '''OR''' Next chapter
|-
! 7
| {{keypress|Left}} || Left || Left || Step back 30s
|-
! 8
| {{keypress|Enter}} || Select || Select || Player controls (OSD)
|-
! 9
| {{keypress|Right}} || Right || Right || Step forward 30s
|-
! 10
| {{keypress|Down}} || Down || Down || Step backward 10min '''OR''' Previous chapter
|-
! 11
| {{keypress|Esc}} || Back || Back || Exit full screen
|-
! 12
| Rewind media key || Rewind || Rewind || Rewind
|-
! 13
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 14
| Fast forward media key || Fast Forward || Fast forward || Fast forward
|-
! 15
| Previous media key || Previous || Previous track || Step backward 30s
|-
! 16
| Next media key || Next || Next track || Step forward 30s
|-
! 17
| Play/Pause media key || Play/pause || Play/pause || Play/pause
|-
! 18
| Stop media key || Stop || Stop || Stop
|}
{{-}}
For this setup use the following keyboard.xml file.

<syntaxhighlight lang="xml" enclose="div">
<keymap>
<global>
<keyboard>
<key id="61656">ContextMenu</key>
<key id="61467">Back</key>
<key id="61637">FastForward</key>
<key id="61636">Rewind</key>
<backspace>PreviousMenu</backspace>
</keyboard>
</global>
<FullscreenVideo>
<keyboard>
<next_track>StepForward</next_track>
<prev_track>StepBack</prev_track>
</keyboard>
</FullscreenVideo>
</keymap>
</syntaxhighlight>
{{collapse bottom}}

Also note that the Fire TV Home button is a soft key set to {{keypress|F12}}.

Using the "Flirc, XBMC" profile in Harmony is optional. Using it will get you started with XBMC commands faster, but you will probably also need to change some of the keypresses, which can be done without changing profiles.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Fire TV. Most of these devices will show up as a [[keyboard]] type input.

====Bluetooth Gamepads====

* Nyko PlayPad Pro
* Ouya Controller

== Uninstall XBMC ==
# From the Fire TV Home screen, select '''Settings'''
# Select '''Applications'''
# Find and select your XBMC installation (it may be named "XBMC", "SPMC", or "XBMC on OUYA")
# Select '''Uninstall'''

Alternatively, you can do the uninstall over ADB with one of the following commands.

OUYA
<pre>adb uninstall tv.ouya.xbmc</pre>

SPMC
<pre>adb uninstall com.semperpax.spmc</pre>

XBMC
<pre>adb uninstall org.xbmc.xbmc</pre>

== Video guide ==

{{youtube|-hQ3e9gdsmE}}

== Known issues ==
* VC-1 / WMV9 encoded videos is currently not hardware decoded in {{kodi}} on the Amazon Fire TV box.
* USB for storage on the Fire TV box requires root access.
* Live IPTV (via multicast UDP/RTP) is currently not supported due to [http://android.stackexchange.com/questions/93396/cant-play-multicast-using-vlc-application-on-amazon-fire-tv-settop-box missing kernel support].

== Random notes ==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}

* The USB port works with keyboard and mice. If you root the Fire TV then you can also use it for other things such as storage.
* Debug information in the Fire TV's Netflix app can be accessed by pressing {{keypress|Ctrl|Alt|Shift|D}}.
* The FireTV will not go to 'sleep' when XBMC is the active application. In the Gotham builds, you may set the '''Power Saving -> Shutdown Function''' to Quit, and choose any time between 5-120 minutes. This will Exit the application after being idle, which allows the FireTV screensaver to run (the screensaver should pop up right when XBMC exits; test this by using the 5 minute Quit timer). This also appears to function correctly and allow the device to sleep even if you are using the Llama settings to always keep XBMC running.
* You can change the FTV to use non-US Time Zones by using [http://apkleecher.com/download/?dl=com.futurek.android.tzc TimeZone Changer].

== See also ==
* [[Amazon Fire TV Stick]]
* [[Android hardware]]
* [[Android]]

== Links ==
* XBMC forum thread about the Amazon Fire TV: http://forum.xbmc.org/showthread.php?tid=191109
* Amazon Fire TV product page: http://www.amazon.com/Amazon-CL1130-Fire-TV/dp/B00CX5P8FC
* iFixit teardown: http://www.ifixit.com/Teardown/Amazon+Fire+TV+Teardown/23856
* Supported codecs: https://developer.amazon.com/sdk/asb/media-specs.html
* Wikipedia article on Amazon Fire TV: [[wikipedia:Amazon Fire TV]]
** Wikipedia article on Fire OS (Amazon's Android based OS): [[wikipedia:Fire OS]]
* Qualcomm Blog: http://www.qualcomm.com/snapdragon/blog/2014/04/02/new-amazon-fire-tv-powered-snapdragon-600-processor
* XDA Developers Fire TV forum: http://forum.xda-developers.com/fire-tv
* TechRepublic teardown: http://www.techrepublic.com/pictures/cracking-open-amazon-fire-tv/18/
* AFTVnews (News and Guides): http://www.aftvnews.com/
* Amazon Fire TV Utility App: http://goo.gl/woVu0s or http://goo.gl/lUNWaT
[[Category:HTPC]]
[[Category:Index]]
[[Category:Android]]
[[Category:ARM]]
[[Category:Fire TV|*]]