Official Kodi Wiki - User contributions [en]

User:Got2Kids

2017-02-12T20:06:39Z

Got2Kids:

Father of two kids, running Kodi on several Android devices (mostly Fire TV 4k and Samsung Galaxy S7).

Amazon Fire TV

2017-02-10T18:52:07Z

Got2Kids: /* Fire TV Stick differences */

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

{{Note|Unless otherwise noted, the following information applies to both the Fire TV box (1 and 2) and Fire TV stick.}}

<section begin="intro" />'''Amazon Fire TV''' (first and second-generations) is a series of Android-based ([[wikipedia:Fire OS|Fire OS]]) set-top-box that contains a powerful ARM processor (that can even handle some of the more heavy Kodi skins). First released in 2014, Amazon's Fire TV series 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, which generally makes it a good pairing with Kodi.<section end="intro" />

Amazon have also 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 the same video playback features and capabilities as the first-generation of Amazon Fire TV, at least as far as running Kodi on it. The second-generation of Amazon Fire TV however does support newer video codecs and higher resolutions than the Fire TV Stick model.
{{-}}

== Fire TV Gen-1 and Gen-2 differences ==
The main differences between the first-generation Fire TV (released in 2014) and second-generation TV (released in 2015) is that the second-genration supports newer video codecs (HEVC and VP9) plus higher resolutions (Ultra HD /2160p at up to 30 fps, also known as "4K" resolution), and that includes HDMI 2.0 with HDCP 2.2 as required for 4K output by some streaming apps such as Netflix. And while the first-generation Fire TV (2014) shipped with an older version of the Fire TV operating-system it can now be upgraded to the same new version as the second-generation Fire TV (2015), so software-wise the old and new hardware can still support the same features and functions that are not dependent on newer [[Android hardware|Android hardware (such as video codecs and resolution)]].

== Fire TV Stick differences ==
In a nutshell: slower processor Broadcom BCM28145 (which won't be a huge difference for average Kodi usage), Amazon Fire TV Stick only has 1GB of RAM, comes withoput no USB port and wired Ethernet. The stick does feature HDMI, power, WiFi, and Bluetooth. The first versions of the Fire TV Stick does not support newer video codecs (HEVC and VP9), nor does it support higher resolutions than Full HD / 1080p, (so no support for Ultra HD /2160p at up to 30 fps, which also known as "4K" resolution). All released versions of the Fire TV Stick still work fairly well from a Kodi standpoint (faster than a Raspberry Pi 1, but slower than a Raspberry Pi 2/3).

In 2015 Amazon bundled the Fire TV Stick with the new voice remote control (that has an integrated microphone).

In 2016, Amazon released a new version. The dualcore Broadcom BCM28145 was replaced by a quadcore MediaTek MT8127, which does support HEVC. It is bigger, 85.9 mm x 30.0 mm x 12.6 mm compared to the older measuring 84,9 mm x 25,0 mm x 11,5 mm. Amazon US sells it as "All-New Fire TV Stick with Alexa Voice Remote".

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

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

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

== Copying files ==

The easiest ways to copy files onto the Fire TV for Kodi is to either use the Kodi '''[[file manager]]''' or use ES File Explorer from the Amazon app store.

== Controls ==

; Fire TV 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 Fire TV 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).

;Keyboards
:Through bluetooth or a USB connection (Fire TV box only) you can connect additional remotes and devices. These devices must be seen as a "keyboard" to the OS, so that they don't need additional software drivers. For example, the '''[[Flirc]]''', which is a universal learning IR receiver..

:See '''[[keyboard controls]]''' for how to control Kodi using a keyboard.

:Additional Fire TV controls goes as followed:
:{| class=prettytable
! Key !! Action
|-
| {{keypress|F11}}<br />or "browser search"<br />media key. || Voice Search ''(Does not send mic audio)''
|-
| {{keypress|F12}} || Fire TV home screen
|-
| {{keypress|Esc}} || Fire TV back button
|-
| {{keypress|Ctrl|Esc}}<br />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
|}
{{-}}

;Gamepads
:Any USB or bluetooth gamepad that works in general for the Fire TV will also work in Kodi.

:;Examples
:* Fire TV gamepad
:* 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

== Known issues ==
* VC-1 / WMV9 encoded videos is currently not hardware decoded in Kodi on the Amazon Fire TV box or stick
* 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.''}}

* Unless rooted, the micro USB port on the Amazon Fire TV Stick does not support USB host functions (no hard drives or USB input).

Kodi config is kept in <code>/sdcard/Android/data/org.xbmc.kodi/files/.kodi</code>

Let's say you wanted to edit a <code>sources.xml</code> or other XML configuration file on your FireTV.

<pre>
$ adb connect <fire_tv_ip>
$ adb pull /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/sources.xml
* edit the local copy of sources.xml *
$ adb push sources.xml /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/sources.xml
</pre>

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

== Links ==
* 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:Android]]
[[Category:ARM]]
[[Category:Fire TV|*]]

Amazon Fire TV

2017-02-10T18:19:12Z

Got2Kids: /* Fire TV Stick differences */

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

{{Note|Unless otherwise noted, the following information applies to both the Fire TV box (1 and 2) and Fire TV stick.}}

<section begin="intro" />'''Amazon Fire TV''' (first and second-generations) is a series of Android-based ([[wikipedia:Fire OS|Fire OS]]) set-top-box that contains a powerful ARM processor (that can even handle some of the more heavy Kodi skins). First released in 2014, Amazon's Fire TV series 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, which generally makes it a good pairing with Kodi.<section end="intro" />

Amazon have also 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 the same video playback features and capabilities as the first-generation of Amazon Fire TV, at least as far as running Kodi on it. The second-generation of Amazon Fire TV however does support newer video codecs and higher resolutions than the Fire TV Stick model.
{{-}}

== Fire TV Gen-1 and Gen-2 differences ==
The main differences between the first-generation Fire TV (released in 2014) and second-generation TV (released in 2015) is that the second-genration supports newer video codecs (HEVC and VP9) plus higher resolutions (Ultra HD /2160p at up to 30 fps, also known as "4K" resolution), and that includes HDMI 2.0 with HDCP 2.2 as required for 4K output by some streaming apps such as Netflix. And while the first-generation Fire TV (2014) shipped with an older version of the Fire TV operating-system it can now be upgraded to the same new version as the second-generation Fire TV (2015), so software-wise the old and new hardware can still support the same features and functions that are not dependent on newer [[Android hardware|Android hardware (such as video codecs and resolution)]].

== Fire TV Stick differences ==
In a nutshell: slower processor Broadcom BCM28145 (which won't be a huge difference for average Kodi usage), Amazon Fire TV Stick only has 1GB of RAM, comes withoput no USB port and wired Ethernet. The stick does feature HDMI, power, WiFi, and Bluetooth. No versions of the Fire TV Stick supports newer video codecs (HEVC and VP9), nor does it support higher resolutions than Full HD / 1080p, (so no support for Ultra HD /2160p at up to 30 fps, which also known as "4K" resolution). All released versions of the Fire TV Stick still work fairly well from a Kodi standpoint (faster than a Raspberry Pi 1, but slower than a Raspberry Pi 2/3).

Other than the new voice remote control (that has an integrated microphone) there are no differences hardware between the first-generation Fire TV Stick (released in 2014) and second-generation "new" Fire TV Stick (released in 2015).

In 2016, Amazon released a new version. The dualcore Broadcom BCM28145 was replaced by a quadcore MediaTek MT8127, which does support HEVC. It is bigger, 85.9 mm x 30.0 mm x 12.6 mm compared to the older measuring 84,9 mm x 25,0 mm x 11,5 mm. Amazon US sells it as "with Alexa voice remote".

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

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

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

== Copying files ==

The easiest ways to copy files onto the Fire TV for Kodi is to either use the Kodi '''[[file manager]]''' or use ES File Explorer from the Amazon app store.

== Controls ==

; Fire TV 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 Fire TV 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).

;Keyboards
:Through bluetooth or a USB connection (Fire TV box only) you can connect additional remotes and devices. These devices must be seen as a "keyboard" to the OS, so that they don't need additional software drivers. For example, the '''[[Flirc]]''', which is a universal learning IR receiver..

:See '''[[keyboard controls]]''' for how to control Kodi using a keyboard.

:Additional Fire TV controls goes as followed:
:{| class=prettytable
! Key !! Action
|-
| {{keypress|F11}}<br />or "browser search"<br />media key. || Voice Search ''(Does not send mic audio)''
|-
| {{keypress|F12}} || Fire TV home screen
|-
| {{keypress|Esc}} || Fire TV back button
|-
| {{keypress|Ctrl|Esc}}<br />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
|}
{{-}}

;Gamepads
:Any USB or bluetooth gamepad that works in general for the Fire TV will also work in Kodi.

:;Examples
:* Fire TV gamepad
:* 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

== Known issues ==
* VC-1 / WMV9 encoded videos is currently not hardware decoded in Kodi on the Amazon Fire TV box or stick
* 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.''}}

* Unless rooted, the micro USB port on the Amazon Fire TV Stick does not support USB host functions (no hard drives or USB input).

Kodi config is kept in <code>/sdcard/Android/data/org.xbmc.kodi/files/.kodi</code>

Let's say you wanted to edit a <code>sources.xml</code> or other XML configuration file on your FireTV.

<pre>
$ adb connect <fire_tv_ip>
$ adb pull /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/sources.xml
* edit the local copy of sources.xml *
$ adb push sources.xml /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/sources.xml
</pre>

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

== Links ==
* 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:Android]]
[[Category:ARM]]
[[Category:Fire TV|*]]

Android hardware

2017-02-10T18:02:23Z

Got2Kids: /* Compatible chipsets */

{{mininav|[[Android]]}}
<section begin="intro" />For most [[wikipedia:High-definition video|high-definition video]]s (1080p or higher resolution), hardware video decoding is necessary for smooth video playback on most Android devices. Therefor this article contains a list of SoC chipset hardware, (SoC stands for "System on a Chip" which contain the CPU plus GPU and VPU circuits combination, and is also known as a "chipset"), as on Android platforms this SoC chipset is what can playback common video codecs smoothly using Kodi/XBMC.<section end="intro" />

The fact is, while some devices might be able to smoothly decode [[wikipedia:Standard-definition television|standard-definition video]]s and even some 720p or higher resolution videos using only software video decoding with raw CPU compute power, offloading a large part of video decoding tasks to an integrated VPU (Video Processor Unit) that is optimized specifically for this job is considered essential for almost all Android devices to be able to smoothly playback high definition videos.

==Basic requirements==
{{see also|Supported hardware}}
{{#lst:Supported hardware|Android}}

==How do I know what chipset I have?==
There are so many out there so it can something be difficult to find out, but these are some good websites for looking up the SoC (System on a Chip) chipset used in your Android hardware device:

* http://www.iboum.com - Digital media players
* http://gsmarena.com - Phones
* [[Wikipedia:Comparison of Android devices]]
* http://www.androidcentral.com/devices

Also as a reference you can compare different SoC (System on a Chip) chipset specifications on system-on-a-chip.findthebest.com as well as in http://docs.google.com/spreadsheets/d/1GT7I4P8MDlfYvRaL9Wv0NplQJryl54pO_6-9P3g7Fvk/

==Compatible chipsets==
These specific mass-market hardware SoC chipsets listed below should be capable at least partial hardware accelerated video decoding support for the more popular video codecs in the latest official Kodi builds for Android. Also understand that for some devices you might first need to upgrade the hardware firmware image on the device to achieve smooth playback at 1080p or higher resolution. Please contact your hardware manufacturer support for an updated system update firmware and apply that upgrade image before installing Kodi.

{{warning|These pages are maintained by the community and should not be considered an endorsement or recommendation. The information on this page might contain errors. It might also contain ants, and their antsy antics. '''[[Kodi:General disclaimer|*]]''' }}

{|
| A "|| {{yes}} ||" mark indicates that SoC (System-on-a-Chip) chipset should be able to decode those codecs at least 1080p in Kodi without issues.
|}
{| width="100%" class="datatable"
|-
! rowspan="2" | Chip<br />manufacturer !! rowspan="2" | SoC chipset !! rowspan="2" | Examples of media players / development boards running Android and using these SoC chipsets with Kodi support !! colspan="5" | Hardware video decoding !! rowspan="2" | Notes
|-
! H.264 !! MPEG-2 !! VC-1 / WMV 9 !! HEVC (H.265) !! VP9
|-
| Actions Semi || S500 / ATM7029 / ATM7039S / ATM7059 || Aceberry S500 devboard, ActDuino S500 Development Board, Allo SPARKY board, Kaiboer F5 Plus, LeMaker Guitar, LemonPi, Roseapple Pi Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Actions Semi || S900 / ATM9009 || 96Boards Bubblegum-96 Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| ALi || M3733 || GoWarrior Tiger Development Board, Uyesee L100T2, Zidoo D1 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Allwinner || A31 / A31s / A33 || Justop Quadro, Mele A1000G/M8/M9, Measy B4K/U4K, VidOn Box, VidOn.me AV200 || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator">Warning for open source violators that do not comply with Kodi's GPL license! There are a few SoC manufacturers, like example Allwinner and Realtek or media player using their chipsets, that violate the GPL license that Kodi (and XBMC before) is bound under. This type of violation done by forking and not releasing all source code that they integrate into Kodi / XBMC when they modify or add closed source code or non-complatible code. This is because Kodi's code is bound under an open source license that require that all code integrating with Kodi's own GPL project is also releasing under a GPL compatible license. Other that hurting the Kodi project by not contributing as required, the risk for end-users buying hardware that rely on open source violations is not getting any support for the official Kodi project.</ref>
|-
| Allwinner || A80 / A83T || Tronsmart Draco AW80, Rikomagic MK80 || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Allwinner || H2+ / H3 / H8 || Inphic i8, Orange Pi 2/Plus, Tronsmart Draco H3, Zidoo X1 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} || <ref name="Open-source violator"/>
|-
| Allwinner || H5 / A64 / H64 || Nobel64 Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} || <ref name="Open-source violator"/>
|-
| [[Amlogic]] || AML8726-M1 / AML8726-M3 / AML8726-M6 / AML8726-MX / AML8726-MXS / AML8726-MXL || [[Pivos XIOS|Pivos XIOS DS/XS]], GameStick (by PlayJam), Geniatech ATV1220/ATV520/ATV1610, MyGica ATV420/ATV500/ATV1610, JynxBox M1/M6, Matricom G-Box Midnight MX2, [[WeTek Play]] || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| [[Amlogic]] || S801 / M802 / S802 / M802 (formerly AML8726-M8) || Geniatech ATV582 / MyGica ATV582, Minix Neo X8/X8-H, Eny Technology ES8, Tronsmart Vega S89/S89-H, Beelink S82/S82H/M8, Xiaomi Mi Box Enhanced || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| [[Amlogic]] || S805 / M805 / S806 / M806 / S812 || Eny Technology EM9/M8S/M8C/EM6Q-MXQ, Geniatech ATV585/ATV1810 / MyGica ATV585/ATV1810, Minix NEO X6 /X8-H Plus, [[ODROID|Hardkernel ODROID-C1]], Ugoos S85, SkyStream X5, Sumvision Cyclone X4, Xtreamer Wonder, Beelink S82 Plus, WeTek Core || {{yes}} || {{yes}} || {{yes}} || {{yes}}<br />{{smaller|(8-bit only)}} || {{?}} || <ref name="8-bit Main HEVC (H.265) profile support only">Some SoC's hardware video decoders like the one in Amlogic S805/M805/S806/M806/S812 and Rockchip RK3288/RK3368 are limited to only supporting the Main HEVC (H.265) profile, which means that they only support 8-bit color range and lower bit-rate, and they do therefor not support the Main10 HEVC or Main12 profiles which is uses for 10-bit and 12-bit color ranges respectivly, which also require support for higher bit-rates. This usually also means that they will not be capable of playing HEVC videos encoded in 4K (2160p) resolution at 60 FPS (frames per second). For more information see http://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels</ref>
|-
| [[Amlogic]] || S905 || Beelink MINI MX, Geniatech ATV495/ATV1950, MyGica ATV49/ATV1950, [[ODROID|Hardkernel ODROID-C2]], Ugoos AM1/AM2 || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| [[Amlogic]] || S905D / S905M / S905X / S908 || [[Xiaomi Mi Box|Xiaomi Mi Box (2016)]] / Xiaomi Mi Box 3 || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| [[Amlogic]] || S912 || Beelink GT1, Eny Technology Enybox X2, Rikomagic MK22, Videostrong KM8 Pro || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Broadcom || BCM2836 / BCM2837 || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Broadcom || BCM28145 / BCM28155 || [[Amazon Fire TV Stick|Amazon Fire TV Stick (2014/2015)]] || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} ||
|-
| Broadcom || BCM7250 / BCM7252 / BCM7252s / BCM72502 || Freebox Mini 4K, Infomir MAG350/MAG352, Smart Labs SML-482 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| [[Freescale]]/NSX || i.MX 6 series (i.MX6 / i.MX6S / i.MX6SL / i.MX6D / i.MX6DL / i.MX6Q) || [[CompuLab Utilite]], [[SolidRun CuBox-i|SolidRun CuBox-i & CuBoxTV]], [[SolidRun Hummingboard]], [[UDOO|UDOO Neo/Duo/Quad]], [[Wandboard|Wandboard Solo/Dual/Quad ]] || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| [[Freescale]]/NSX || i.MX 7 series || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| HiSilicon || Hi3798C / Hi3798M || HiMedia H7-II/M3/Q5-4K/Q5-IV/Q5X/Q10-IV, Open Hour Gekco, PixePlay KURO || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| HiSilicon || Hi3798C V200 || HiMedia Q10 Pro || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| HiSilicon || Kirin 620 || LeMaker HiKey Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Atom E3815 / E3825 || Intel MinnowBoard MAX Development Board || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Intel || Atom x3 / x5 / x7 (x3-C3130 / x3-C3230RK / x3-C3440 / x5-8300 / x5-8500 / x7-8700) || UDOO x86 Development Board (Basic & Advanced), Up Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Atom Z3530 / Z3560 / Z3580 / Z3735 || [[Google Nexus Player]], Minix Neo Z64 || {{yes}} || {{no}} || {{no}} || {{no}} || {{?}} ||
|-
| Intel || Celeron N3000 / N3050 / N3150, and Pentium N3700 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Core M3 6Y30 / M5 6Y54 / M5 6Y57 / M5 6Y75 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Marvell || ARMADA 1500 Mini/Pro/Pro4K/Ultra || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MediaTek || MTK6589 / MT6589 / MT6589T / MT6589M || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| MediaTek || MT8127 || Amazon Fire Tablet (7", 2015), Amazon Fire TV Stick with Alexa (2016) || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} ||
|-
| MediaTek || MT8173 || [[Amazon Fire TV|Amazon Fire TV (2015)]] || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} ||
|-
| MediaTek || MT8685 / MT8685A / MT8685B || UTStarcom MT8685/MC8685A/MC8685B, Xiaomi Mi Box Mini || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MediaTek || MT8693 || Xiaomi Mi Box 3 Pro || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MStar || MSO9180 / MSO9180D1R / MSO9280 / MSO9810 || Egreat A9, Kaiboer F5/Q6/C9-M, MeLE V10/X2000, UyeSee T1H, Tronsmart Pavo M9, Xtreamer Prodigy, Zidoo X9 || {{yes}} || {{yes}} || {{?}} || {{?}} || {{?}} ||
|-
| Nvidia || [[Tegra 3]] || [[OUYA]] || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra 4]] / [[Tegra 4i]] / [[Tegra 4s]] || ZTE FunBox, Mad Catz M.O.J.O., NanoTech Nuvola NP-1 / NP-C / NP-H1, UTStarcom MC8768, Google ADT-1 (Android TV Developer Kit), [[Nvidia SHIELD Portable]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra K1|Tegra K1 (TK1)]] || Unuiga Game PC U1, Snail Games OBox, UTStarcom MC8718, [[Nvidia SHIELD Tablet K1]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra X1|Tegra X1 (TX1)]] || [[Nvidia SHIELD TV]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{Yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 210 / 212 || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 410 / 412 / 415 / 425 / 430 / 435 || DragonBoard 410c (Turn off "MediaCodec" HW acceleration). Nobel64 Development Board || {{yes}} || {{yes}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 600 || [[Amazon Fire TV|Amazon Fire TV (2014)]], Compulab Utilite2, DragonBoard 600c, Inforce 6410Plus Development Board, Intrinsyc Open-Q 600 Development Board || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 610 / 615 / 618 / 620 / 625 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Qualcomm || Snapdragon 617 || Lenovo Moto G4 || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 652 || Samsung Galaxy Tab S2 || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 800 / 801 / 805 || [[Razor Forge TV]] || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 808 / 810 / 820 || HTC M9 (Turn off "MediaCodec" HW accelleration) || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Qualcomm || Snapdragon S4 || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Realtek || RTD1195 (RTK 1195) || || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Realtek || RTD1295 (RTK 1295) || || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Rockchip || RK3066 || Imito MX1/MX2, Minix NeoG4/X5, MK808/802, Ugoos UG802/UG007 || {{yes}} || {{?}} || {{no}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3188 || Jesurun DX05, Minix X7, MK802IV, MK809III, MK902, Ugoos UG007B, Tronsmart T428/MK908, CS968, CR11s, J22, GM282, LT88, T-R42, CS919-II, K-R42, CS918, MK888 || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3036 / RK3126 / RK3128 / RK3288 || Firefly-RK3288, ChipSpark PopMetal, Uyesee G1H, Nagrace HPH NT-V6, Eny Technology EKB318/EKB328, Kingnovel R6/K-R68, Beelink R28, FireFly FirePrime Development Board, Ugoos UT3/UM3, Rikomagic MK902 II, Measy B4S, Ruach A20s, CloudMedia OpenHour, CloudnetGo CR12/CR13CR16, Tronsmart Orion R28, Youku Box K1, Unuiga Game Box 19-6R || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3368 || Beelink i68, CloudnetGo CR18/CR13 Plus, Eny Technology EKB368, Himedia H7 III, Measy B4T, Ruach A20s-H, Rikomagic MK68, Tronsmart Orion R68, Zidoo X6/X6 Pro || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3228 / RK3228B / RK3228H || || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Rockchip || RK3229 / RK3399 || Firefly-RK3399, MXQ-4K || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Samsung || Exynos 3 Single (formerly Exynos 3110) || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 4 Dual/Quad series (formerly Exynos 4210 / 4212 /4412 / 4418) || [[ODROID|Hardkernel ODROID-U3/U2/X2]], FriendlyARM NanoPC-T1/NanoPC-T2 || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 5 Hexa/Octa series (Exynos 5260 / 5410/ 5420 / 5422) || [[ODROID|Hardkernel ODROID-XU/XU2/XU3/XU3 Lite]], Arndale Octa || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 7 Octa series (Exynos 7410 / 7420 / 7870) || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Samsung || Exynos 8 Octa series (Exynos 8890) || Samsung Galaxy S7 (Europe) || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Samsung || S5P6818 (Octa Core) || FriendlyARM NanoPi M3 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Telechips || TCC898x || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Texas Instruments || OMAP4430 / OMAP4440 / OMAP5430 / OMAP5432 || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Texas Instruments || Sitara AM3358 / AM3359 || BeagleBoard Black || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Texas Instruments || Sitara AM5728 || BeagleBoard-X15 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|}

== Common codecs currently without hardware decoding in Kodi ==
Videos encoded with these codecs can only be played back in Kodi using software video decoding using CPU, meaning no decoding tasks are offloaded to optimized VPU or GPU hardware. Many videos may still play back just fine at standard definition resolutions, while others might have severe issues with playback.

As platforms with faster CPUs come out for Android software video decoding using CPU will get better, but do not expect miracles from the average Android box. It still all can depend on how demanding the decoding of that particular video encoding is or how high resolution it uses, and how powerful the CPU is.

* H.264 Hi10P - No hardware decoders for [[Hi10P]] (High 10 Profile, also known 10-bit H.264) currently exist for any ARM hardware. Most H.264 Hi10P videos will not play smoothly as most ARM CPUs are just not powerful enough to software decode it fast enough.
* H.264 MVC - No open source software decoder or hardware decoding for [http://en.wikipedia.org/wiki/Multiview_Video_Coding MVC (Multiview Video Coding)] stereoscopic 3D video decoding currently exist for Kodi on any platform. Kodi relies on FFmpeg for software demuxing and decoding, so Kodi have to wait for FFmpeg to first add software decoding support of MVC for H.264, and for hardware decoding Kodi relies on the SoC chipset hardware manufacturer to add support for this to their SDK (Software Developer Kits) and for the media player box manufacturers to implement that into their firmware images.
* H.265 MVC (HEVC MVC) - No open source software decoder or hardware decoding for [http://en.wikipedia.org/wiki/Multiview_Video_Coding MVC (Multiview Video Coding)] stereoscopic 3D video decoding currently exist for Kodi on any platform. Kodi relies on FFmpeg for software demuxing and decoding, so Kodi have to wait for FFmpeg to first add software decoding support of MVC for H.265 (HEVC), and for hardware decoding Kodi relies on the SoC chipset hardware manufacturer to add support for this to their SDK (Software Developer Kits) and for the media player box manufacturers to implement that into their firmware images.
* RealVideo/RMVB (RV 8/9/10) - There is currently no support in Kodi for RealVideo hardware video decoding, though software decoding of RMVB videos is possible via FFmpeg but can struggle with high definition sources on older or low-end hardware.
* VP8 (WebM v1 video) and VP9 (WebM v2 video) - There is currently no support in Kodi for VP8 hardware video decoding, though software decoding of VP8 videos is possible via FFmpeg but can struggle with high definition sources on older or low-end hardware. Most hardware manufacturers have not even implemented API support for VP8 decoding in the firmware images of Android for their devices, and this is despite the fact that the WebM project licenses VP8 hardware accelerators (RTL IP) to semiconductor companies for 1080p encoding and decoding at zero cost. Nvidia and Rockchip and a few other less known companies does however provide hardware decoding of VP8 in their SoCs, for Tegra 4 and RK29xx respectivly. ARM, Broadcom, Texas Instruments, and Qualcomm as well as ZiiLABS, ST-Ericsson, and Huawei have all announced upcoming support for hardware acceleration of the WebM format and VP8/VP9 codecs. Intel have also let its intention known that they will add hardware-based acceleration for WebM and VP8/VP9 codecs in its future Atom-based chips if the format gains popularity. VP9 does howver to this date not appear to have hardware decoding support in all but the very newest ARM SoCs for Android, such as exanple Nvidia Tegra X1 (TX1) used in Nvidia Shield TV.

==Notes==
<references />

== Device specific info ==
Here are a few device-specific guides/help areas that the community has provided.

{{Device notice}}


<dpl>
category = HTPC
category = Android
format = ,{{list2|%PAGE%}}
</dpl>

{{Isengard updated}}

[[Category:Android]]
[[Category:Hardware]]

Archive:Android FAQ

2017-02-10T18:01:54Z

Got2Kids: /* Crashing when opened */

{{Kodi FAQ}}
{{mininav|[[Android]] }}
<section begin="intro" />'''F'''requently '''A'''sked '''Q'''uestions for Android.<section end="intro" />
__TOC__
{{-}}

== General FAQ ==
:{{big|''See also: '''[[Kodi all platforms FAQ]]''' for FAQs that apply to all versions of Kodi.''}}

=== Will this really do 1080p and all that stuff the desktop can do? ===
:* Yes! This is a full port of Kodi! It is not a thin client or lite version!
:* The reason Android port is to get Kodi working on Android set-top-boxes. Phones and tablets are also supported, but are not the main focus.

=== Requirements ===
{{anchor|1=Requirements}}
:{{see also|Android hardware}}
:{{#lst:Supported hardware|Android}}

=== There are two versions of Kodi for Android. Which one do I use? ===
{{anchor|1=CPU}}
:The vast majority of users will want to use the [{{download link|Android ARM}} "ARM" version]. Users who have an Android device with an Intel or AMD CPU will want to use the [{{Download link|Android x86}} "x86" version].

=== Installing/getting Kodi for Android ===
{{anchor|1=Installing}}
{{Main|HOW-TO:Install Kodi for Android}}
:* {{current version}} can be found here:
:** '''ARM''' (most users want this): {{Download link|Android ARM}}
:** '''x86''': {{Download link|Android x86}}
:* For nightlies, alphas, betas and experimental builds, see the links on '''[[Development builds]]'''

=== Is Kodi for Android different from normal Kodi? ===
{{anchor|1=Version}}
: The current version of Kodi for Android is based on {{current version}}, and is based on the same code as Kodi for all the other supported platforms.

{{anchor|1=Current_build}}
=== How do I find out what version of Kodi am I running? ===
: Kodi main menu > System > Lower submenu > System info. '''Note the version and build date.'''

=== Video and audio formats Kodi for Android can playback ===
{{anchor|1=Formats}}
:* Kodi for Android supports all the same formats that other platforms do (such as desktop OS).
:* Due to the weak processing power of most ARM processors, for smooth playback most Android hardware will require proper hardware decoding. (See [[#Requirements]] below)

=== Accessing media ===
{{anchor|1=Media}}
{{See also|Adding videos to the library|File sharing}}
:* You can connect to media that's being shared from a computer, HTPC, or NAS device on your local network.
:* You can access media on the internal memory, SD cards or from USB ports (hard drives, USB stick drives, directly or via hubs, etc).

=== Add-ons and skins ===
{{anchor|1=Add-ons|2=Skins}}
:* Kodi for Android is a full version of Kodi and will be able to use all non-platform specific [[add-ons]] and [[skins]].
:* If you are using a touch screen device and the build you are using did not include it, you can manually instal [[Add-on:Touched]] for better touch screen support.

=== Remote controls ===
{{anchor|1=Remotes}}
:* Some Android set-top-boxes come with a remote and an IR port which Kodi can use.
:* Any '''[[Keyboard]]''' such as wired, wireless, bluetooth (if supported in your Android ROM). This includes "keymotes" such as a Rii, [[Boxee remote]], most "air mouse" keyboard remotes, and others that appear as a normal USB keyboard to the system.
:* '''[[Web interface]]s''', including add-on interfaces.
:* Kodi '''[[:Category:Smartphone and tablet remotes|smartphone and tablet remote apps]]'''.
:* Other IR remotes can be used with IR receivers such as the '''[[Flirc]]'''.
:* Some Android devices support '''[[CEC]]'''

=== Launching Android apps from within Kodi ===
{{anchor|1=Apps}}
:{{main|HOW-TO:Launch Android apps}}
:{{#lst:HOW-TO:Launch Android apps|intro}}

=== Automatically start Kodi ===
{{anchor|1=Startup}}
: You can automatically start Kodi when your Android device boots up using an application such as [https://play.google.com/store/apps/details?id=imoblife.startupmanager Startup Manager (free)]

== Performance tips ==
{{Main|Android#Tips and tricks}}

=== Performance: video buffering, stuttering, choppiness ===
{{anchor|1=Buffering|2=Performance}}
:{{#lst:Android|FAQ Performance notes}}

== Troubleshooting ==
{{see also|Troubleshooting}}

=== Getting more help with Kodi for Android ===
{{anchor|1=Forum|2=IRC}}
:* '''[http://forum.kodi.tv/forumdisplay.php?fid=164 Kodi for Android specific help forum]'''
:* '''[irc://irc.freenode.org/kodi #kodi]''' [[w:IRC|IRC]] chat channel on irc.freenode.org.

=== Where is the Userdata folder ===
{{anchor|1=Userdata}}
:The userdata folder is located on external storage/sdcard at the following locations (depending on your device):
:;[[userdata folder]]
:* <code>{{userdata|Android}}</code>

=== Where is the Kodi log ===
{{anchor|1=Kodi log}}
:The Kodi log is located inside the temp folder, i.e.
:;[[debug log]]
:* /sdcard/Android/data/org.xbmc.kodi/files/.kodi/temp/kodi.log

=== How can I obtain a Minidump ===
{{anchor|1=minidump}}
:The Kodi minidumps are located inside the temp folder, i.e.
:* /sdcard/Android/data/org.xbmc.kodi/files/.kodi/temp/*.dmp

=== How can I obtain a Crash Log (logcat) ===
{{anchor|1=logcat}}
:A crash log (also called logcat) is mandatory to be able todebug hard crashes on Android
:* Download the '''[https://play.google.com/store/apps/details?id=org.l6n.sendlog SendLog app]''' from the Google Play store. It allows you to send your system log to an email address. Email it to yourself and show us where the error happened. '''(requires root)'''
:* Alternatively, you can use your computer. Plug your device, download and unzip the [http://d.android.com/sdk/index.html Android SDK] and run ddms.bat in the tools folder. There you have it under ''LogCat''.
:* The logfile is kept on a phone for a while, so you don't need to reproduce a crash in order to get the log.
:* Be sure to have hidden folders set to be shown in your file explorer.

=== How to hide the Android navigation bar ===
{{anchor|1=navbar}}
:* As of v13, Kodi supports Android 4.4 (Kitkat)'s immersive mode, allowing for fullscreen automatically.
:* '''To remove the navbar:'''
:** You can use "[http://ppareit.github.com/HideBar/ HideBar]" (Has a free version, and is open source if you wish to compile yourself)
:** The app "[https://play.google.com/store/apps/details?id=de.tsorn.FullScreen Full!Screen]" is free and should also work.
:** A custom Android distribution can be installed to correctly handle the navbar. [http://replicant.us/ Replicant], [http://www.cyanogenmod.org/ CyanogenMod] and some others offer an “extended desktop” mode which hides the navigation bar and, optionally, the status bar too. Also check for firmware on sites such as http://freaktab.com for more firmware options.

=== Audio sync/delay issues ===
{{anchor|1=audio_sync}}
:Is some or all of your audio out of sync with the video? Try these tips:
:* Check for firmware updates for your specific Android device.
:* If you have a delay that is consistent regardless of the file, you can manually adjust the delay:
:*# Open any video that has audio playing.
:*# Bring up the '''[[Video playback#On screen display (OSD)|on-screen-display]]''' and select the [[Video playback#OSD audio and subtitle settings|audio options]].
:*# Select '''[[Video playback#OSD audio and subtitle settings|Audio offset]]''' and then adjust the audio until the delay is corrected.
:*# Back in the OSD audio settings, scroll down and select '''Set as default for all videos'''.
:* {{editor note|Sometimes things can be corrected by just not using audio passthrough, but either some people don't want to do that at all, or they don't know exactly what that is. We probably need a guide about audio sync in general (not just Android), and add that to our general '''[[audio]]''' help pages.}}

{{anchor|no_video}}
=== Amlogic playback issues (zoomed in, 1/4 screen, no video, etc) ===
* As of v15 and later, Kodi will no longer ask to fix incorrect video decoding permissions on Amlogic-based devices that have incorrectly configured firmware. This might cause an issue in some situations, and if this happens to you, first try to manually disable '''amcodec''' and only use '''mediacodec''' and '''libstagefright''' under {{highlight|bordered=yes| [[Settings/Videos#Acceleration|Settings -> Videos -> Acceleration]] }}. If videos still won't play correctly then the device might a firmware/OS update for things to work properly.

* In some cases video playback is fine, but incorrectly sized so that it only takes up a small portion of the screen. This again is most likely a firmware issue, but a temp workaround would be to go into Android's system settings (not Kodi's settings) and change the GUI resolution to 720 and/or disable "auto select". Video will still render at 1080, and only the GUI is limited to 720.

* There may also be situations were Kodi isn't correctly detecting the box's ability to use the "amcodec", and thus prematurely disabling it. Our devs are currently looking into this situation, and if true, will attempt to fix it.

:;Why was this changed?
::Kodi doesn't try to manually fix the permissions anymore. Doing so was a hack that the devs didn't feel comfortable with, and vendors need to fix this on the firmware level, not the application level. Some hardware vendors are still unwilling to set the necessary permissions because of a misconception on "security", which ironically requires granting apps root-level access, which is far less secure.

::However, the mediacodec "path" to decoding doesn't require the permissions changes, and mediacodec support has improved both in Kodi and in most firmware (even in some of the flawed ones). So now when amcodec fails it falls back on mediacodec, which normally works. In that sense it is "fixed". Eventually mediacodec will be the single standard, and there won't be a need for amcodec, but the option is still there for some special situations.

=== Videos play, but are not always smooth ===
{{anchor|1=rough_playback}}
:There are a number of reasons why this can happen, so it's hard to give general advice for such a description, but here are some things that you can try:
:* Some Android hardware has bugs using the "MediaCodec" hardware decoding method, but plays video fine using "libstagefright". Try turning off "MediaCodec" and leaving "libstageright" on in: {{highlight|bordered=yes|[[Settings/Videos#Acceleration|Settings -> Videos -> Acceleration]]}}. Users of [[Android hardware|AMLogic hardware]] can ignore this, as those devices use a third "AmCodec" hardware decoding method.
:* Hardware video decoding might not be enabled at all on your device. Most Android boxes will require hardware video decoding for smooth HD video playback. Check settings under {{highlight|bordered=yes|[[Settings/Videos#Acceleration|Settings -> Videos -> Acceleration]]}}
:* Most Android boxes don't support hardware video decoding of some codecs, such as VC-1, Hi10P, and HEVC(H.265). Consult the compatibility list on '''[[Android hardware]]'''.
:* Rule out network performance by loading a small test video directly to the internal memory of your Android device.
:* Some AVI files with H.264 encoded video have problems if you play them with hardware decoding - some SoCs play them smoothly (like Mediatek 8129, 8173), while others don't (like Broadcom BCM28145, Qualcomm Snapdragon 617, 652, Samsung Exynos 8890). If your SoC is powerful enough, try disabling hardware decoding.

=== Downloading Kodi results in a .txt or .zip file instead of a .apk file ===
:* Some web browsers will rename .apk files for some reason. To fix this you simply need to rename the file back to .apk and it should then work to install Kodi. To rename files you can use a file manager/explorer program.

=== Video playback stops when another app is in focus ===
* This is expected behavior for newer Google APIs and how Kodi v16 works. In addition to making sure that the new video decoding APIs are working correctly, this also has the side effect of making sure Kodi doesn't prevent other apps from using video, such as Netflix, even if Kodi is still open.

* To prevent this from happening when a video is paused, make sure that Kodi's screensaver is either off or using a screensaver other than "Dim" or "Black". That will prevent the Android screensaver/daydream from becoming active.

=== Low volume or strange volume behavior ===
* To support TVs that have Android built-in, and to prevent the "double volume bar" of previous releases, Kodi v16 no longer changes both '''Kodi volume''' and '''system volume''' at the same time. Instead, these are now controlled seperately.

* Most users will likely wish to leave Kodi volume at full and then control system volume, which is what most remote controls use by default for their volume buttons.

* If volume is low then you might need to turn up the internal "Kodi volume". If you are using a skin that doesn't show the volume bar, then you can change the volume by playing a video and opening the on-screen-display and selecting the audio settings. Alternatively, you can also hook up a USB keyboard to turn the volume up using the {{keypress|+}} or {{keypress|1==}} keys.

=== Crashing when opened ===
: A few things to try it this happens:
* Go into Android's settings and into "Apps". Then select Kodi and select '''"Clear cache"'''. {{small|''Do '''{{color|red|not}}''' select "Clear data".''}}

* If you are using MySQL then see '''[[MySQL/Upgrading]]'''.

* Make sure your Android device has at least 500 MB of free space (a rough estimate).

* Re-install without uninstalling. This should keep your settings.

* As a last resort, uninstalling and re-installing can be done, but doing so will reset all settings.

* If you need more help, please leave a message on '''http://forum.kodi.tv'''.

=== GUI no longer rendered at 4K ===
: Kodi v15 would render everything in 4K for the Nvidia Shield TV, but used a method that won't work correctly on other 4K boxes, as the GUI is handled by the CPU and not a hardware decoder.

: This has been changed for Kodi v16. On supported hardware, such as some official Android TV devices, 4K video will always output at 4K. Only the user interface will render at 1080, so that less powerful CPUs aren't bogged down. In other words, the video lists and buttons are not as "sharp", but video will still be fine. In the future there ''might'' be an option to render everything at 4K, for devices that are powerful enough.

=== Missing "brightness" and "contrast" options ===
: If in Kodi v15 you had brightness and contrast [[video playback]] options, but they are missing in v16, then you can re-enable them by going to {{highlight|bordered=yes|Settings -> Videos -> Acceleration -> }} and disable only '''"Mediacodec (surface)"'''. Video will still be hardware decoded, but this will disable 4K output support for 4K Android hardware.

{{Updated|16}}

[[Category:Manual]]
[[Category:FAQ|Android]]
[[Category:Android|*]]
[[Category:Troubleshooting]]

Archive:Android FAQ

2017-02-10T17:58:32Z

Got2Kids: /* Videos play, but are not always smooth */

{{Kodi FAQ}}
{{mininav|[[Android]] }}
<section begin="intro" />'''F'''requently '''A'''sked '''Q'''uestions for Android.<section end="intro" />
__TOC__
{{-}}

== General FAQ ==
:{{big|''See also: '''[[Kodi all platforms FAQ]]''' for FAQs that apply to all versions of Kodi.''}}

=== Will this really do 1080p and all that stuff the desktop can do? ===
:* Yes! This is a full port of Kodi! It is not a thin client or lite version!
:* The reason Android port is to get Kodi working on Android set-top-boxes. Phones and tablets are also supported, but are not the main focus.

=== Requirements ===
{{anchor|1=Requirements}}
:{{see also|Android hardware}}
:{{#lst:Supported hardware|Android}}

=== There are two versions of Kodi for Android. Which one do I use? ===
{{anchor|1=CPU}}
:The vast majority of users will want to use the [{{download link|Android ARM}} "ARM" version]. Users who have an Android device with an Intel or AMD CPU will want to use the [{{Download link|Android x86}} "x86" version].

=== Installing/getting Kodi for Android ===
{{anchor|1=Installing}}
{{Main|HOW-TO:Install Kodi for Android}}
:* {{current version}} can be found here:
:** '''ARM''' (most users want this): {{Download link|Android ARM}}
:** '''x86''': {{Download link|Android x86}}
:* For nightlies, alphas, betas and experimental builds, see the links on '''[[Development builds]]'''

=== Is Kodi for Android different from normal Kodi? ===
{{anchor|1=Version}}
: The current version of Kodi for Android is based on {{current version}}, and is based on the same code as Kodi for all the other supported platforms.

{{anchor|1=Current_build}}
=== How do I find out what version of Kodi am I running? ===
: Kodi main menu > System > Lower submenu > System info. '''Note the version and build date.'''

=== Video and audio formats Kodi for Android can playback ===
{{anchor|1=Formats}}
:* Kodi for Android supports all the same formats that other platforms do (such as desktop OS).
:* Due to the weak processing power of most ARM processors, for smooth playback most Android hardware will require proper hardware decoding. (See [[#Requirements]] below)

=== Accessing media ===
{{anchor|1=Media}}
{{See also|Adding videos to the library|File sharing}}
:* You can connect to media that's being shared from a computer, HTPC, or NAS device on your local network.
:* You can access media on the internal memory, SD cards or from USB ports (hard drives, USB stick drives, directly or via hubs, etc).

=== Add-ons and skins ===
{{anchor|1=Add-ons|2=Skins}}
:* Kodi for Android is a full version of Kodi and will be able to use all non-platform specific [[add-ons]] and [[skins]].
:* If you are using a touch screen device and the build you are using did not include it, you can manually instal [[Add-on:Touched]] for better touch screen support.

=== Remote controls ===
{{anchor|1=Remotes}}
:* Some Android set-top-boxes come with a remote and an IR port which Kodi can use.
:* Any '''[[Keyboard]]''' such as wired, wireless, bluetooth (if supported in your Android ROM). This includes "keymotes" such as a Rii, [[Boxee remote]], most "air mouse" keyboard remotes, and others that appear as a normal USB keyboard to the system.
:* '''[[Web interface]]s''', including add-on interfaces.
:* Kodi '''[[:Category:Smartphone and tablet remotes|smartphone and tablet remote apps]]'''.
:* Other IR remotes can be used with IR receivers such as the '''[[Flirc]]'''.
:* Some Android devices support '''[[CEC]]'''

=== Launching Android apps from within Kodi ===
{{anchor|1=Apps}}
:{{main|HOW-TO:Launch Android apps}}
:{{#lst:HOW-TO:Launch Android apps|intro}}

=== Automatically start Kodi ===
{{anchor|1=Startup}}
: You can automatically start Kodi when your Android device boots up using an application such as [https://play.google.com/store/apps/details?id=imoblife.startupmanager Startup Manager (free)]

== Performance tips ==
{{Main|Android#Tips and tricks}}

=== Performance: video buffering, stuttering, choppiness ===
{{anchor|1=Buffering|2=Performance}}
:{{#lst:Android|FAQ Performance notes}}

== Troubleshooting ==
{{see also|Troubleshooting}}

=== Getting more help with Kodi for Android ===
{{anchor|1=Forum|2=IRC}}
:* '''[http://forum.kodi.tv/forumdisplay.php?fid=164 Kodi for Android specific help forum]'''
:* '''[irc://irc.freenode.org/kodi #kodi]''' [[w:IRC|IRC]] chat channel on irc.freenode.org.

=== Where is the Userdata folder ===
{{anchor|1=Userdata}}
:The userdata folder is located on external storage/sdcard at the following locations (depending on your device):
:;[[userdata folder]]
:* <code>{{userdata|Android}}</code>

=== Where is the Kodi log ===
{{anchor|1=Kodi log}}
:The Kodi log is located inside the temp folder, i.e.
:;[[debug log]]
:* /sdcard/Android/data/org.xbmc.kodi/files/.kodi/temp/kodi.log

=== How can I obtain a Minidump ===
{{anchor|1=minidump}}
:The Kodi minidumps are located inside the temp folder, i.e.
:* /sdcard/Android/data/org.xbmc.kodi/files/.kodi/temp/*.dmp

=== How can I obtain a Crash Log (logcat) ===
{{anchor|1=logcat}}
:A crash log (also called logcat) is mandatory to be able todebug hard crashes on Android
:* Download the '''[https://play.google.com/store/apps/details?id=org.l6n.sendlog SendLog app]''' from the Google Play store. It allows you to send your system log to an email address. Email it to yourself and show us where the error happened. '''(requires root)'''
:* Alternatively, you can use your computer. Plug your device, download and unzip the [http://d.android.com/sdk/index.html Android SDK] and run ddms.bat in the tools folder. There you have it under ''LogCat''.
:* The logfile is kept on a phone for a while, so you don't need to reproduce a crash in order to get the log.
:* Be sure to have hidden folders set to be shown in your file explorer.

=== How to hide the Android navigation bar ===
{{anchor|1=navbar}}
:* As of v13, Kodi supports Android 4.4 (Kitkat)'s immersive mode, allowing for fullscreen automatically.
:* '''To remove the navbar:'''
:** You can use "[http://ppareit.github.com/HideBar/ HideBar]" (Has a free version, and is open source if you wish to compile yourself)
:** The app "[https://play.google.com/store/apps/details?id=de.tsorn.FullScreen Full!Screen]" is free and should also work.
:** A custom Android distribution can be installed to correctly handle the navbar. [http://replicant.us/ Replicant], [http://www.cyanogenmod.org/ CyanogenMod] and some others offer an “extended desktop” mode which hides the navigation bar and, optionally, the status bar too. Also check for firmware on sites such as http://freaktab.com for more firmware options.

=== Audio sync/delay issues ===
{{anchor|1=audio_sync}}
:Is some or all of your audio out of sync with the video? Try these tips:
:* Check for firmware updates for your specific Android device.
:* If you have a delay that is consistent regardless of the file, you can manually adjust the delay:
:*# Open any video that has audio playing.
:*# Bring up the '''[[Video playback#On screen display (OSD)|on-screen-display]]''' and select the [[Video playback#OSD audio and subtitle settings|audio options]].
:*# Select '''[[Video playback#OSD audio and subtitle settings|Audio offset]]''' and then adjust the audio until the delay is corrected.
:*# Back in the OSD audio settings, scroll down and select '''Set as default for all videos'''.
:* {{editor note|Sometimes things can be corrected by just not using audio passthrough, but either some people don't want to do that at all, or they don't know exactly what that is. We probably need a guide about audio sync in general (not just Android), and add that to our general '''[[audio]]''' help pages.}}

{{anchor|no_video}}
=== Amlogic playback issues (zoomed in, 1/4 screen, no video, etc) ===
* As of v15 and later, Kodi will no longer ask to fix incorrect video decoding permissions on Amlogic-based devices that have incorrectly configured firmware. This might cause an issue in some situations, and if this happens to you, first try to manually disable '''amcodec''' and only use '''mediacodec''' and '''libstagefright''' under {{highlight|bordered=yes| [[Settings/Videos#Acceleration|Settings -> Videos -> Acceleration]] }}. If videos still won't play correctly then the device might a firmware/OS update for things to work properly.

* In some cases video playback is fine, but incorrectly sized so that it only takes up a small portion of the screen. This again is most likely a firmware issue, but a temp workaround would be to go into Android's system settings (not Kodi's settings) and change the GUI resolution to 720 and/or disable "auto select". Video will still render at 1080, and only the GUI is limited to 720.

* There may also be situations were Kodi isn't correctly detecting the box's ability to use the "amcodec", and thus prematurely disabling it. Our devs are currently looking into this situation, and if true, will attempt to fix it.

:;Why was this changed?
::Kodi doesn't try to manually fix the permissions anymore. Doing so was a hack that the devs didn't feel comfortable with, and vendors need to fix this on the firmware level, not the application level. Some hardware vendors are still unwilling to set the necessary permissions because of a misconception on "security", which ironically requires granting apps root-level access, which is far less secure.

::However, the mediacodec "path" to decoding doesn't require the permissions changes, and mediacodec support has improved both in Kodi and in most firmware (even in some of the flawed ones). So now when amcodec fails it falls back on mediacodec, which normally works. In that sense it is "fixed". Eventually mediacodec will be the single standard, and there won't be a need for amcodec, but the option is still there for some special situations.

=== Videos play, but are not always smooth ===
{{anchor|1=rough_playback}}
:There are a number of reasons why this can happen, so it's hard to give general advice for such a description, but here are some things that you can try:
:* Some Android hardware has bugs using the "MediaCodec" hardware decoding method, but plays video fine using "libstagefright". Try turning off "MediaCodec" and leaving "libstageright" on in: {{highlight|bordered=yes|[[Settings/Videos#Acceleration|Settings -> Videos -> Acceleration]]}}. Users of [[Android hardware|AMLogic hardware]] can ignore this, as those devices use a third "AmCodec" hardware decoding method.
:* Hardware video decoding might not be enabled at all on your device. Most Android boxes will require hardware video decoding for smooth HD video playback. Check settings under {{highlight|bordered=yes|[[Settings/Videos#Acceleration|Settings -> Videos -> Acceleration]]}}
:* Most Android boxes don't support hardware video decoding of some codecs, such as VC-1, Hi10P, and HEVC(H.265). Consult the compatibility list on '''[[Android hardware]]'''.
:* Rule out network performance by loading a small test video directly to the internal memory of your Android device.
:* Some AVI files with H.264 encoded video have problems if you play them with hardware decoding - some SoCs play them smoothly (like Mediatek 8129, 8173), while others don't (like Broadcom BCM28145, Qualcomm Snapdragon 617, 652, Samsung Exynos 8890). If your SoC is powerful enough, try disabling hardware decoding.

=== Downloading Kodi results in a .txt or .zip file instead of a .apk file ===
:* Some web browsers will rename .apk files for some reason. To fix this you simply need to rename the file back to .apk and it should then work to install Kodi. To rename files you can use a file manager/explorer program.

=== Video playback stops when another app is in focus ===
* This is expected behavior for newer Google APIs and how Kodi v16 works. In addition to making sure that the new video decoding APIs are working correctly, this also has the side effect of making sure Kodi doesn't prevent other apps from using video, such as Netflix, even if Kodi is still open.

* To prevent this from happening when a video is paused, make sure that Kodi's screensaver is either off or using a screensaver other than "Dim" or "Black". That will prevent the Android screensaver/daydream from becoming active.

=== Low volume or strange volume behavior ===
* To support TVs that have Android built-in, and to prevent the "double volume bar" of previous releases, Kodi v16 no longer changes both '''Kodi volume''' and '''system volume''' at the same time. Instead, these are now controlled seperately.

* Most users will likely wish to leave Kodi volume at full and then control system volume, which is what most remote controls use by default for their volume buttons.

* If volume is low then you might need to turn up the internal "Kodi volume". If you are using a skin that doesn't show the volume bar, then you can change the volume by playing a video and opening the on-screen-display and selecting the audio settings. Alternatively, you can also hook up a USB keyboard to turn the volume up using the {{keypress|+}} or {{keypress|1==}} keys.

=== Crashing when opened ===
: A few things to try it this happens:
* Go into Android's settings and into "Apps". Then select Kodi and select '''"Clear cache"'''. {{small|''Do '''{{color|red|not}}''' select "Clear data".''}}

* If you are using MySQL then see '''[[MySQL/Upgrading]]'''.

* Make sure your Android device has at least 500 MB of free space (a rough estimate).

* As a last resort, uninstalling and re-installing can be done, but doing so will reset all settings.

* If you need more help, please leave a message on '''http://forum.kodi.tv'''.

=== GUI no longer rendered at 4K ===
: Kodi v15 would render everything in 4K for the Nvidia Shield TV, but used a method that won't work correctly on other 4K boxes, as the GUI is handled by the CPU and not a hardware decoder.

: This has been changed for Kodi v16. On supported hardware, such as some official Android TV devices, 4K video will always output at 4K. Only the user interface will render at 1080, so that less powerful CPUs aren't bogged down. In other words, the video lists and buttons are not as "sharp", but video will still be fine. In the future there ''might'' be an option to render everything at 4K, for devices that are powerful enough.

=== Missing "brightness" and "contrast" options ===
: If in Kodi v15 you had brightness and contrast [[video playback]] options, but they are missing in v16, then you can re-enable them by going to {{highlight|bordered=yes|Settings -> Videos -> Acceleration -> }} and disable only '''"Mediacodec (surface)"'''. Video will still be hardware decoded, but this will disable 4K output support for 4K Android hardware.

{{Updated|16}}

[[Category:Manual]]
[[Category:FAQ|Android]]
[[Category:Android|*]]
[[Category:Troubleshooting]]

Kodi v18 (Leia) changelog

2017-02-10T17:27:09Z

Got2Kids:

{{mininav|[[Releases]] {{l2| [[Leia]] }} }}

{{notice|Kodi v17 (Krypton) final has just been released, so please keep in mind that a final non-alpha/beta v18 (Leia) release is still far far away into the future. As such, these new features/functions and API changes is a placeholder containing changes to the current Kodi mainline (the git master tree repository on GitHub). It is a very much a work in progress, this is only listing changes commited to the master branch after Jarvis branching, and many many many features/functions and API additions, alterations or removal are still subject to future change.}}
{{incomplete}}
{{future|18}}

{{see also|Kodi v18 (Leia) FAQ|Leia API changes|Releases}}

This is a placeholder and Kodi Wiki copy of the condensed changelog for the future Kodi v18.x version (codename: "Leia") releases with a summery of the most important core features and functions as well as other notable changes to key areas of the application software or its user interface.

== Changelog ==

=== Gaming (Games interface and Game Clients)===
* Added a RetroPlayer player core supporting game clients as well as emulator cores via libretro API<ref name="RetroPlayer">RetroPlayer http://forum.kodi.tv/showthread.php?tid=164725</ref><ref>http://github.com/xbmc/xbmc/pull/11022</ref>
* Added support for Game Client Addons as new type of addons with just-in-time emulator installation<ref name="RetroPlayer"/>
* Added a Games window entry to the GUI<ref name="RetroPlayer"/>
* Added a gaming and game configuration interface for Game settings to the GUI<ref name="RetroPlayer"/>
* Added support for Game Info Tags (game info tag) and exposed properties to Python list items<ref name="RetroPlayer"/>
* Added a savestate (savestate) manager to Kodi for games<ref>http://github.com/xbmc/xbmc/pull/11034</ref>
* Added support for in-game (save RAM) saves<ref>http://github.com/xbmc/xbmc/pull/11380</ref>
* Added support for Keyboard players via Joystick Emulation<ref name="RetroPlayer"/>
* Added support for libretro API and game cores (emulators and games) that support it
* Added [[Game_Add-ons|game clients addons]] for many popular third-party game console emulators and games *
** ''* Game Client Addons for Kodi is changing quickly so checkout the [[Game_Add-ons|game clients addons]] article for a current list''
* Extended Kodi's Addon API to support Game Client Addons, supporting Kodi's VFS (Virtual File System), etc.<ref name="RetroPlayer"/>
* ?

=== Live TV and PVR (Personal Video Recorder) ===
* * Major gui actions refactoring and context menu rewrite in the PVR section<ref>ttp://github.com/xbmc/xbmc/pull/10870</ref><ref>http://github.com/xbmc/xbmc/pull/11115</ref>
* ?

=== Add-ons Framework, API, and Manager ===
For full changelogs of all Addons APIs, see [[Leia API changes]], [http://forum.kodi.tv/forumdisplay.php?fid=174 JSON-RPC], and [http://forum.kodi.tv/forumdisplay.php?fid=26 Add-ons] Development Forums
* Major refactoring of Kodi's handling of binary addons<ref>http://github.com/xbmc/xbmc/pulls?q=label%3A%22Binary+Addons%22+is%3Aclosed</ref>
* Added support for VFS (Virtual File System) addons<ref>http://github.com/xbmc/xbmc/pull/8966</ref>
* Added support to allow Python addons to set the videoinfotag path<ref>http://github.com/xbmc/xbmc/pull/11012</ref>
* Added support to allow Python addons to get/set the dbid of a (music) listitem<ref>http://github.com/xbmc/xbmc/pull/10858</ref>
* Added support for mediatype to musicinfotag tag retrieving via Python API<ref>http://github.com/xbmc/xbmc/pull/11110</ref>
* Added support "int/float slider" to Kodi's Python API<ref>http://github.com/xbmc/xbmc/pull/11230</ref>
* Added support "setContent for mediawindows" to Kodi's Python API<ref>http://github.com/xbmc/xbmc/pull/11258</ref>
* ?

=== GUI Engine (Skinning Engine) ===
For full changelog on changes to the skinning engine, see [[Leia API changes]] and the [http://forum.kodi.tv/showthread.php?tid=298565 Skin Development Forum]
* Added windows to support Games in the new default skins (Estuary and Estouchy)
* Added support for skins/gui to allow implicit container referencing for non-media windows<ref>http://github.com/xbmc/xbmc/pull/10883</ref>
* Added support for addons to add "Enable/Disable" to context menu<ref>http://github.com/xbmc/xbmc/pull/11124</ref>
* Added support for remember last used keyboard layout in GUI<ref>http://github.com/xbmc/xbmc/pull/11242</ref>
* Improved Kodi's GUI engine support for scaling container layouts<ref>http://github.com/xbmc/xbmc/pull/11229</ref>
* Improved Kodi's GUI engine by allowing %-values for origin, camera and animation attribs<ref>http://github.com/xbmc/xbmc/pull/11233</ref>
* Updated guilib ABI (for libgui) to version 5.13.0<ref>http://github.com/xbmc/xbmc/pull/11306</ref>
* Updated keyboard layout for some languages and added new keyboard layout for Croatian QWERTZ
* ?

=== Platform Independent Playback ===
* Added a VC1-Packet bitstream parser implementation for improved VC-1 playback<ref>http://github.com/xbmc/xbmc/pull/11417</ref>
* ?

=== Library ===
* ?

=== Web Scrapers ===
* Added support for Python (script) based web scrapers for Kodi<ref>http://github.com/xbmc/xbmc/pull/9984</ref>
* Refactored and updated many XML based scrapers in Kodi for music, movies, tv shows, and music videos
* ?

=== AudioEngine ===
* ?

=== Other ===
* Added support to build Kodi with support for Bluetooth<ref>http://github.com/xbmc/xbmc/pull/11137</ref>
* Improved Kodi's JSON-RPC API
* Improved code documentation in doxygen coding guidelines
* Removed all glew (libglew library) dependencies in Kodi's code<ref>http://github.com/xbmc/xbmc/pull/11128</ref>
* ?

=== Android Specific ===
* Changed Zeroconf to be disabled by default on Android due to unresolved bugs<ref>http://github.com/xbmc/xbmc/pull/11393</ref>
* ?

=== BSD Specific ===
* ?

=== Linux Specific ===
* Added support for Mir windowing system for Kodi<ref>http://github.com/xbmc/xbmc/pull/10898</ref> and added support for VAAPI on Mir using DRM<ref>http://github.com/xbmc/xbmc/pull/11040</ref>
* Added support for build Kodi with imx support using CMake<ref>http://github.com/xbmc/xbmc/pull/11288</ref>
* Moved the CMake build system to the top of the code tree (moved to root)<ref>http://github.com/xbmc/xbmc/pull/10446</ref>
* Removed support for autotools based build system for Kodi and binary addons (in favour of CMake)<ref>http://github.com/xbmc/xbmc/pull/10429</ref>
* ?

=== iOS Specific ===
* ?

=== OS X Specific ===
* ?

=== Windows Specific ===
* ?

== References ==
<references/>

== See also ==
* [[Leia API changes]]
{{Changelogs}}

[[Category:Manual]]
[[Category:Leia|*]]
[[Category:Changelogs|18]]

Android hardware

2017-02-09T20:58:57Z

Got2Kids: /* Compatible chipsets */

{{mininav|[[Android]]}}
<section begin="intro" />For most [[wikipedia:High-definition video|high-definition video]]s (1080p or higher resolution), hardware video decoding is necessary for smooth video playback on most Android devices. Therefor this article contains a list of SoC chipset hardware, (SoC stands for "System on a Chip" which contain the CPU plus GPU and VPU circuits combination, and is also known as a "chipset"), as on Android platforms this SoC chipset is what can playback common video codecs smoothly using Kodi/XBMC.<section end="intro" />

The fact is, while some devices might be able to smoothly decode [[wikipedia:Standard-definition television|standard-definition video]]s and even some 720p or higher resolution videos using only software video decoding with raw CPU compute power, offloading a large part of video decoding tasks to an integrated VPU (Video Processor Unit) that is optimized specifically for this job is considered essential for almost all Android devices to be able to smoothly playback high definition videos.

==Basic requirements==
{{see also|Supported hardware}}
{{#lst:Supported hardware|Android}}

==How do I know what chipset I have?==
There are so many out there so it can something be difficult to find out, but these are some good websites for looking up the SoC (System on a Chip) chipset used in your Android hardware device:

* http://www.iboum.com - Digital media players
* http://gsmarena.com - Phones
* [[Wikipedia:Comparison of Android devices]]
* http://www.androidcentral.com/devices

Also as a reference you can compare different SoC (System on a Chip) chipset specifications on system-on-a-chip.findthebest.com as well as in http://docs.google.com/spreadsheets/d/1GT7I4P8MDlfYvRaL9Wv0NplQJryl54pO_6-9P3g7Fvk/

==Compatible chipsets==
These specific mass-market hardware SoC chipsets listed below should be capable at least partial hardware accelerated video decoding support for the more popular video codecs in the latest official Kodi builds for Android. Also understand that for some devices you might first need to upgrade the hardware firmware image on the device to achieve smooth playback at 1080p or higher resolution. Please contact your hardware manufacturer support for an updated system update firmware and apply that upgrade image before installing Kodi.

{{warning|These pages are maintained by the community and should not be considered an endorsement or recommendation. The information on this page might contain errors. It might also contain ants, and their antsy antics. '''[[Kodi:General disclaimer|*]]''' }}

{|
| A "|| {{yes}} ||" mark indicates that SoC (System-on-a-Chip) chipset should be able to decode those codecs at least 1080p in Kodi without issues.
|}
{| width="100%" class="datatable"
|-
! rowspan="2" | Chip<br />manufacturer !! rowspan="2" | SoC chipset !! rowspan="2" | Examples of media players / development boards running Android and using these SoC chipsets with Kodi support !! colspan="5" | Hardware video decoding !! rowspan="2" | Notes
|-
! H.264 !! MPEG-2 !! VC-1 / WMV 9 !! HEVC (H.265) !! VP9
|-
| Actions Semi || S500 / ATM7029 / ATM7039S / ATM7059 || Aceberry S500 devboard, ActDuino S500 Development Board, Allo SPARKY board, Kaiboer F5 Plus, LeMaker Guitar, LemonPi, Roseapple Pi Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Actions Semi || S900 / ATM9009 || 96Boards Bubblegum-96 Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| ALi || M3733 || GoWarrior Tiger Development Board, Uyesee L100T2, Zidoo D1 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Allwinner || A31 / A31s / A33 || Justop Quadro, Mele A1000G/M8/M9, Measy B4K/U4K, VidOn Box, VidOn.me AV200 || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator">Warning for open source violators that do not comply with Kodi's GPL license! There are a few SoC manufacturers, like example Allwinner and Realtek or media player using their chipsets, that violate the GPL license that Kodi (and XBMC before) is bound under. This type of violation done by forking and not releasing all source code that they integrate into Kodi / XBMC when they modify or add closed source code or non-complatible code. This is because Kodi's code is bound under an open source license that require that all code integrating with Kodi's own GPL project is also releasing under a GPL compatible license. Other that hurting the Kodi project by not contributing as required, the risk for end-users buying hardware that rely on open source violations is not getting any support for the official Kodi project.</ref>
|-
| Allwinner || A80 / A83T || Tronsmart Draco AW80, Rikomagic MK80 || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Allwinner || H2+ / H3 / H8 || Inphic i8, Orange Pi 2/Plus, Tronsmart Draco H3, Zidoo X1 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} || <ref name="Open-source violator"/>
|-
| Allwinner || H5 / A64 / H64 || Nobel64 Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} || <ref name="Open-source violator"/>
|-
| [[Amlogic]] || AML8726-M1 / AML8726-M3 / AML8726-M6 / AML8726-MX / AML8726-MXS / AML8726-MXL || [[Pivos XIOS|Pivos XIOS DS/XS]], GameStick (by PlayJam), Geniatech ATV1220/ATV520/ATV1610, MyGica ATV420/ATV500/ATV1610, JynxBox M1/M6, Matricom G-Box Midnight MX2, [[WeTek Play]] || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| [[Amlogic]] || S801 / M802 / S802 / M802 (formerly AML8726-M8) || Geniatech ATV582 / MyGica ATV582, Minix Neo X8/X8-H, Eny Technology ES8, Tronsmart Vega S89/S89-H, Beelink S82/S82H/M8, Xiaomi Mi Box Enhanced || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| [[Amlogic]] || S805 / M805 / S806 / M806 / S812 || Eny Technology EM9/M8S/M8C/EM6Q-MXQ, Geniatech ATV585/ATV1810 / MyGica ATV585/ATV1810, Minix NEO X6 /X8-H Plus, [[ODROID|Hardkernel ODROID-C1]], Ugoos S85, SkyStream X5, Sumvision Cyclone X4, Xtreamer Wonder, Beelink S82 Plus, WeTek Core || {{yes}} || {{yes}} || {{yes}} || {{yes}}<br />{{smaller|(8-bit only)}} || {{?}} || <ref name="8-bit Main HEVC (H.265) profile support only">Some SoC's hardware video decoders like the one in Amlogic S805/M805/S806/M806/S812 and Rockchip RK3288/RK3368 are limited to only supporting the Main HEVC (H.265) profile, which means that they only support 8-bit color range and lower bit-rate, and they do therefor not support the Main10 HEVC or Main12 profiles which is uses for 10-bit and 12-bit color ranges respectivly, which also require support for higher bit-rates. This usually also means that they will not be capable of playing HEVC videos encoded in 4K (2160p) resolution at 60 FPS (frames per second). For more information see http://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels</ref>
|-
| [[Amlogic]] || S905 || Beelink MINI MX, Geniatech ATV495/ATV1950, MyGica ATV49/ATV1950, [[ODROID|Hardkernel ODROID-C2]], Ugoos AM1/AM2 || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| [[Amlogic]] || S905D / S905M / S905X / S908 || [[Xiaomi Mi Box|Xiaomi Mi Box (2016)]] / Xiaomi Mi Box 3 || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| [[Amlogic]] || S912 || Beelink GT1, Eny Technology Enybox X2, Rikomagic MK22, Videostrong KM8 Pro || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Broadcom || BCM2836 / BCM2837 || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Broadcom || BCM28145 / BCM28155 || [[Amazon Fire TV Stick|Amazon Fire TV Stick (2014/2015)]] || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} ||
|-
| Broadcom || BCM7250 / BCM7252 / BCM7252s / BCM72502 || Freebox Mini 4K, Infomir MAG350/MAG352, Smart Labs SML-482 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| [[Freescale]]/NSX || i.MX 6 series (i.MX6 / i.MX6S / i.MX6SL / i.MX6D / i.MX6DL / i.MX6Q) || [[CompuLab Utilite]], [[SolidRun CuBox-i|SolidRun CuBox-i & CuBoxTV]], [[SolidRun Hummingboard]], [[UDOO|UDOO Neo/Duo/Quad]], [[Wandboard|Wandboard Solo/Dual/Quad ]] || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| [[Freescale]]/NSX || i.MX 7 series || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| HiSilicon || Hi3798C / Hi3798M || HiMedia H7-II/M3/Q5-4K/Q5-IV/Q5X/Q10-IV, Open Hour Gekco, PixePlay KURO || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| HiSilicon || Hi3798C V200 || HiMedia Q10 Pro || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| HiSilicon || Kirin 620 || LeMaker HiKey Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Atom E3815 / E3825 || Intel MinnowBoard MAX Development Board || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Intel || Atom x3 / x5 / x7 (x3-C3130 / x3-C3230RK / x3-C3440 / x5-8300 / x5-8500 / x7-8700) || UDOO x86 Development Board (Basic & Advanced), Up Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Atom Z3530 / Z3560 / Z3580 / Z3735 || [[Google Nexus Player]], Minix Neo Z64 || {{yes}} || {{no}} || {{no}} || {{no}} || {{?}} ||
|-
| Intel || Celeron N3000 / N3050 / N3150, and Pentium N3700 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Core M3 6Y30 / M5 6Y54 / M5 6Y57 / M5 6Y75 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Marvell || ARMADA 1500 Mini/Pro/Pro4K/Ultra || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MediaTek || MTK6589 / MT6589 / MT6589T / MT6589M || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| MediaTek || MT8127 || Amazon Fire Tablet (6", 2015) || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} ||
|-
| MediaTek || MT8173 || [[Amazon Fire TV|Amazon Fire TV (2015)]] || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} ||
|-
| MediaTek || MT8685 / MT8685A / MT8685B || UTStarcom MT8685/MC8685A/MC8685B, Xiaomi Mi Box Mini || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MediaTek || MT8693 || Xiaomi Mi Box 3 Pro || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MStar || MSO9180 / MSO9180D1R / MSO9280 / MSO9810 || Egreat A9, Kaiboer F5/Q6/C9-M, MeLE V10/X2000, UyeSee T1H, Tronsmart Pavo M9, Xtreamer Prodigy, Zidoo X9 || {{yes}} || {{yes}} || {{?}} || {{?}} || {{?}} ||
|-
| Nvidia || [[Tegra 3]] || [[OUYA]] || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra 4]] / [[Tegra 4i]] / [[Tegra 4s]] || ZTE FunBox, Mad Catz M.O.J.O., NanoTech Nuvola NP-1 / NP-C / NP-H1, UTStarcom MC8768, Google ADT-1 (Android TV Developer Kit), [[Nvidia SHIELD Portable]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra K1|Tegra K1 (TK1)]] || Unuiga Game PC U1, Snail Games OBox, UTStarcom MC8718, [[Nvidia SHIELD Tablet K1]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra X1|Tegra X1 (TX1)]] || [[Nvidia SHIELD TV]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{Yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 210 / 212 || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 410 / 412 / 415 / 425 / 430 / 435 || DragonBoard 410c (Turn off "MediaCodec" HW acceleration). Nobel64 Development Board || {{yes}} || {{yes}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 600 || [[Amazon Fire TV|Amazon Fire TV (2014)]], Compulab Utilite2, DragonBoard 600c, Inforce 6410Plus Development Board, Intrinsyc Open-Q 600 Development Board || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 610 / 615 / 618 / 620 / 625 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Qualcomm || Snapdragon 617 || Lenovo Moto G4 || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 652 || Samsung Galaxy Tab S2 || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 800 / 801 / 805 || [[Razor Forge TV]] || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 808 / 810 / 820 || HTC M9 (Turn off "MediaCodec" HW accelleration) || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Qualcomm || Snapdragon S4 || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Realtek || RTD1195 (RTK 1195) || || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Realtek || RTD1295 (RTK 1295) || || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Rockchip || RK3066 || Imito MX1/MX2, Minix NeoG4/X5, MK808/802, Ugoos UG802/UG007 || {{yes}} || {{?}} || {{no}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3188 || Jesurun DX05, Minix X7, MK802IV, MK809III, MK902, Ugoos UG007B, Tronsmart T428/MK908, CS968, CR11s, J22, GM282, LT88, T-R42, CS919-II, K-R42, CS918, MK888 || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3036 / RK3126 / RK3128 / RK3288 || Firefly-RK3288, ChipSpark PopMetal, Uyesee G1H, Nagrace HPH NT-V6, Eny Technology EKB318/EKB328, Kingnovel R6/K-R68, Beelink R28, FireFly FirePrime Development Board, Ugoos UT3/UM3, Rikomagic MK902 II, Measy B4S, Ruach A20s, CloudMedia OpenHour, CloudnetGo CR12/CR13CR16, Tronsmart Orion R28, Youku Box K1, Unuiga Game Box 19-6R || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3368 || Beelink i68, CloudnetGo CR18/CR13 Plus, Eny Technology EKB368, Himedia H7 III, Measy B4T, Ruach A20s-H, Rikomagic MK68, Tronsmart Orion R68, Zidoo X6/X6 Pro || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3228 / RK3228B / RK3228H || || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Rockchip || RK3229 / RK3399 || Firefly-RK3399, MXQ-4K || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Samsung || Exynos 3 Single (formerly Exynos 3110) || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 4 Dual/Quad series (formerly Exynos 4210 / 4212 /4412 / 4418) || [[ODROID|Hardkernel ODROID-U3/U2/X2]], FriendlyARM NanoPC-T1/NanoPC-T2 || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 5 Hexa/Octa series (Exynos 5260 / 5410/ 5420 / 5422) || [[ODROID|Hardkernel ODROID-XU/XU2/XU3/XU3 Lite]], Arndale Octa || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 7 Octa series (Exynos 7410 / 7420 / 7870) || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Samsung || Exynos 8 Octa series (Exynos 8890) || Samsung Galaxy S7 (Europe) || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Samsung || S5P6818 (Octa Core) || FriendlyARM NanoPi M3 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Telechips || TCC898x || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Texas Instruments || OMAP4430 / OMAP4440 / OMAP5430 / OMAP5432 || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Texas Instruments || Sitara AM3358 / AM3359 || BeagleBoard Black || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Texas Instruments || Sitara AM5728 || BeagleBoard-X15 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|}

== Common codecs currently without hardware decoding in Kodi ==
Videos encoded with these codecs can only be played back in Kodi using software video decoding using CPU, meaning no decoding tasks are offloaded to optimized VPU or GPU hardware. Many videos may still play back just fine at standard definition resolutions, while others might have severe issues with playback.

As platforms with faster CPUs come out for Android software video decoding using CPU will get better, but do not expect miracles from the average Android box. It still all can depend on how demanding the decoding of that particular video encoding is or how high resolution it uses, and how powerful the CPU is.

* H.264 Hi10P - No hardware decoders for [[Hi10P]] (High 10 Profile, also known 10-bit H.264) currently exist for any ARM hardware. Most H.264 Hi10P videos will not play smoothly as most ARM CPUs are just not powerful enough to software decode it fast enough.
* H.264 MVC - No open source software decoder or hardware decoding for [http://en.wikipedia.org/wiki/Multiview_Video_Coding MVC (Multiview Video Coding)] stereoscopic 3D video decoding currently exist for Kodi on any platform. Kodi relies on FFmpeg for software demuxing and decoding, so Kodi have to wait for FFmpeg to first add software decoding support of MVC for H.264, and for hardware decoding Kodi relies on the SoC chipset hardware manufacturer to add support for this to their SDK (Software Developer Kits) and for the media player box manufacturers to implement that into their firmware images.
* H.265 MVC (HEVC MVC) - No open source software decoder or hardware decoding for [http://en.wikipedia.org/wiki/Multiview_Video_Coding MVC (Multiview Video Coding)] stereoscopic 3D video decoding currently exist for Kodi on any platform. Kodi relies on FFmpeg for software demuxing and decoding, so Kodi have to wait for FFmpeg to first add software decoding support of MVC for H.265 (HEVC), and for hardware decoding Kodi relies on the SoC chipset hardware manufacturer to add support for this to their SDK (Software Developer Kits) and for the media player box manufacturers to implement that into their firmware images.
* RealVideo/RMVB (RV 8/9/10) - There is currently no support in Kodi for RealVideo hardware video decoding, though software decoding of RMVB videos is possible via FFmpeg but can struggle with high definition sources on older or low-end hardware.
* VP8 (WebM v1 video) and VP9 (WebM v2 video) - There is currently no support in Kodi for VP8 hardware video decoding, though software decoding of VP8 videos is possible via FFmpeg but can struggle with high definition sources on older or low-end hardware. Most hardware manufacturers have not even implemented API support for VP8 decoding in the firmware images of Android for their devices, and this is despite the fact that the WebM project licenses VP8 hardware accelerators (RTL IP) to semiconductor companies for 1080p encoding and decoding at zero cost. Nvidia and Rockchip and a few other less known companies does however provide hardware decoding of VP8 in their SoCs, for Tegra 4 and RK29xx respectivly. ARM, Broadcom, Texas Instruments, and Qualcomm as well as ZiiLABS, ST-Ericsson, and Huawei have all announced upcoming support for hardware acceleration of the WebM format and VP8/VP9 codecs. Intel have also let its intention known that they will add hardware-based acceleration for WebM and VP8/VP9 codecs in its future Atom-based chips if the format gains popularity. VP9 does howver to this date not appear to have hardware decoding support in all but the very newest ARM SoCs for Android, such as exanple Nvidia Tegra X1 (TX1) used in Nvidia Shield TV.

==Notes==
<references />

== Device specific info ==
Here are a few device-specific guides/help areas that the community has provided.

{{Device notice}}


<dpl>
category = HTPC
category = Android
format = ,{{list2|%PAGE%}}
</dpl>

{{Isengard updated}}

[[Category:Android]]
[[Category:Hardware]]

Android hardware

2017-02-09T20:55:32Z

Got2Kids: /* Compatible chipsets */

{{mininav|[[Android]]}}
<section begin="intro" />For most [[wikipedia:High-definition video|high-definition video]]s (1080p or higher resolution), hardware video decoding is necessary for smooth video playback on most Android devices. Therefor this article contains a list of SoC chipset hardware, (SoC stands for "System on a Chip" which contain the CPU plus GPU and VPU circuits combination, and is also known as a "chipset"), as on Android platforms this SoC chipset is what can playback common video codecs smoothly using Kodi/XBMC.<section end="intro" />

The fact is, while some devices might be able to smoothly decode [[wikipedia:Standard-definition television|standard-definition video]]s and even some 720p or higher resolution videos using only software video decoding with raw CPU compute power, offloading a large part of video decoding tasks to an integrated VPU (Video Processor Unit) that is optimized specifically for this job is considered essential for almost all Android devices to be able to smoothly playback high definition videos.

==Basic requirements==
{{see also|Supported hardware}}
{{#lst:Supported hardware|Android}}

==How do I know what chipset I have?==
There are so many out there so it can something be difficult to find out, but these are some good websites for looking up the SoC (System on a Chip) chipset used in your Android hardware device:

* http://www.iboum.com - Digital media players
* http://gsmarena.com - Phones
* [[Wikipedia:Comparison of Android devices]]
* http://www.androidcentral.com/devices

Also as a reference you can compare different SoC (System on a Chip) chipset specifications on system-on-a-chip.findthebest.com as well as in http://docs.google.com/spreadsheets/d/1GT7I4P8MDlfYvRaL9Wv0NplQJryl54pO_6-9P3g7Fvk/

==Compatible chipsets==
These specific mass-market hardware SoC chipsets listed below should be capable at least partial hardware accelerated video decoding support for the more popular video codecs in the latest official Kodi builds for Android. Also understand that for some devices you might first need to upgrade the hardware firmware image on the device to achieve smooth playback at 1080p or higher resolution. Please contact your hardware manufacturer support for an updated system update firmware and apply that upgrade image before installing Kodi.

{{warning|These pages are maintained by the community and should not be considered an endorsement or recommendation. The information on this page might contain errors. It might also contain ants, and their antsy antics. '''[[Kodi:General disclaimer|*]]''' }}

{|
| A "|| {{yes}} ||" mark indicates that SoC (System-on-a-Chip) chipset should be able to decode those codecs at least 1080p in Kodi without issues.
|}
{| width="100%" class="datatable"
|-
! rowspan="2" | Chip<br />manufacturer !! rowspan="2" | SoC chipset !! rowspan="2" | Examples of media players / development boards running Android and using these SoC chipsets with Kodi support !! colspan="5" | Hardware video decoding !! rowspan="2" | Notes
|-
! H.264 !! MPEG-2 !! VC-1 / WMV 9 !! HEVC (H.265) !! VP9
|-
| Actions Semi || S500 / ATM7029 / ATM7039S / ATM7059 || Aceberry S500 devboard, ActDuino S500 Development Board, Allo SPARKY board, Kaiboer F5 Plus, LeMaker Guitar, LemonPi, Roseapple Pi Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Actions Semi || S900 / ATM9009 || 96Boards Bubblegum-96 Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| ALi || M3733 || GoWarrior Tiger Development Board, Uyesee L100T2, Zidoo D1 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Allwinner || A31 / A31s / A33 || Justop Quadro, Mele A1000G/M8/M9, Measy B4K/U4K, VidOn Box, VidOn.me AV200 || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator">Warning for open source violators that do not comply with Kodi's GPL license! There are a few SoC manufacturers, like example Allwinner and Realtek or media player using their chipsets, that violate the GPL license that Kodi (and XBMC before) is bound under. This type of violation done by forking and not releasing all source code that they integrate into Kodi / XBMC when they modify or add closed source code or non-complatible code. This is because Kodi's code is bound under an open source license that require that all code integrating with Kodi's own GPL project is also releasing under a GPL compatible license. Other that hurting the Kodi project by not contributing as required, the risk for end-users buying hardware that rely on open source violations is not getting any support for the official Kodi project.</ref>
|-
| Allwinner || A80 / A83T || Tronsmart Draco AW80, Rikomagic MK80 || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Allwinner || H2+ / H3 / H8 || Inphic i8, Orange Pi 2/Plus, Tronsmart Draco H3, Zidoo X1 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} || <ref name="Open-source violator"/>
|-
| Allwinner || H5 / A64 / H64 || Nobel64 Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} || <ref name="Open-source violator"/>
|-
| [[Amlogic]] || AML8726-M1 / AML8726-M3 / AML8726-M6 / AML8726-MX / AML8726-MXS / AML8726-MXL || [[Pivos XIOS|Pivos XIOS DS/XS]], GameStick (by PlayJam), Geniatech ATV1220/ATV520/ATV1610, MyGica ATV420/ATV500/ATV1610, JynxBox M1/M6, Matricom G-Box Midnight MX2, [[WeTek Play]] || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| [[Amlogic]] || S801 / M802 / S802 / M802 (formerly AML8726-M8) || Geniatech ATV582 / MyGica ATV582, Minix Neo X8/X8-H, Eny Technology ES8, Tronsmart Vega S89/S89-H, Beelink S82/S82H/M8, Xiaomi Mi Box Enhanced || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| [[Amlogic]] || S805 / M805 / S806 / M806 / S812 || Eny Technology EM9/M8S/M8C/EM6Q-MXQ, Geniatech ATV585/ATV1810 / MyGica ATV585/ATV1810, Minix NEO X6 /X8-H Plus, [[ODROID|Hardkernel ODROID-C1]], Ugoos S85, SkyStream X5, Sumvision Cyclone X4, Xtreamer Wonder, Beelink S82 Plus, WeTek Core || {{yes}} || {{yes}} || {{yes}} || {{yes}}<br />{{smaller|(8-bit only)}} || {{?}} || <ref name="8-bit Main HEVC (H.265) profile support only">Some SoC's hardware video decoders like the one in Amlogic S805/M805/S806/M806/S812 and Rockchip RK3288/RK3368 are limited to only supporting the Main HEVC (H.265) profile, which means that they only support 8-bit color range and lower bit-rate, and they do therefor not support the Main10 HEVC or Main12 profiles which is uses for 10-bit and 12-bit color ranges respectivly, which also require support for higher bit-rates. This usually also means that they will not be capable of playing HEVC videos encoded in 4K (2160p) resolution at 60 FPS (frames per second). For more information see http://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels</ref>
|-
| [[Amlogic]] || S905 || Beelink MINI MX, Geniatech ATV495/ATV1950, MyGica ATV49/ATV1950, [[ODROID|Hardkernel ODROID-C2]], Ugoos AM1/AM2 || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| [[Amlogic]] || S905D / S905M / S905X / S908 || [[Xiaomi Mi Box|Xiaomi Mi Box (2016)]] / Xiaomi Mi Box 3 || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| [[Amlogic]] || S912 || Beelink GT1, Eny Technology Enybox X2, Rikomagic MK22, Videostrong KM8 Pro || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Broadcom || BCM2836 / BCM2837 || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Broadcom || BCM28145 / BCM28155 || [[Amazon Fire TV Stick|Amazon Fire TV Stick (2014/2015)]] || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} ||
|-
| Broadcom || BCM7250 / BCM7252 / BCM7252s / BCM72502 || Freebox Mini 4K, Infomir MAG350/MAG352, Smart Labs SML-482 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| [[Freescale]]/NSX || i.MX 6 series (i.MX6 / i.MX6S / i.MX6SL / i.MX6D / i.MX6DL / i.MX6Q) || [[CompuLab Utilite]], [[SolidRun CuBox-i|SolidRun CuBox-i & CuBoxTV]], [[SolidRun Hummingboard]], [[UDOO|UDOO Neo/Duo/Quad]], [[Wandboard|Wandboard Solo/Dual/Quad ]] || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| [[Freescale]]/NSX || i.MX 7 series || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| HiSilicon || Hi3798C / Hi3798M || HiMedia H7-II/M3/Q5-4K/Q5-IV/Q5X/Q10-IV, Open Hour Gekco, PixePlay KURO || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| HiSilicon || Hi3798C V200 || HiMedia Q10 Pro || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| HiSilicon || Kirin 620 || LeMaker HiKey Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Atom E3815 / E3825 || Intel MinnowBoard MAX Development Board || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Intel || Atom x3 / x5 / x7 (x3-C3130 / x3-C3230RK / x3-C3440 / x5-8300 / x5-8500 / x7-8700) || UDOO x86 Development Board (Basic & Advanced), Up Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Atom Z3530 / Z3560 / Z3580 / Z3735 || [[Google Nexus Player]], Minix Neo Z64 || {{yes}} || {{no}} || {{no}} || {{no}} || {{?}} ||
|-
| Intel || Celeron N3000 / N3050 / N3150, and Pentium N3700 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Core M3 6Y30 / M5 6Y54 / M5 6Y57 / M5 6Y75 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Marvell || ARMADA 1500 Mini/Pro/Pro4K/Ultra || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MediaTek || MTK6589 / MT6589 / MT6589T / MT6589M || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| MediaTek || MT8127 || Amazon Fire Tablet (6", 2015) || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} ||
|-
| MediaTek || MT8173 || [[Amazon Fire TV|Amazon Fire TV (2015)]] || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} ||
|-
| MediaTek || MT8685 / MT8685A / MT8685B || UTStarcom MT8685/MC8685A/MC8685B, Xiaomi Mi Box Mini || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MediaTek || MT8693 || Xiaomi Mi Box 3 Pro || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MStar || MSO9180 / MSO9180D1R / MSO9280 / MSO9810 || Egreat A9, Kaiboer F5/Q6/C9-M, MeLE V10/X2000, UyeSee T1H, Tronsmart Pavo M9, Xtreamer Prodigy, Zidoo X9 || {{yes}} || {{yes}} || {{?}} || {{?}} || {{?}} ||
|-
| Nvidia || [[Tegra 3]] || [[OUYA]] || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra 4]] / [[Tegra 4i]] / [[Tegra 4s]] || ZTE FunBox, Mad Catz M.O.J.O., NanoTech Nuvola NP-1 / NP-C / NP-H1, UTStarcom MC8768, Google ADT-1 (Android TV Developer Kit), [[Nvidia SHIELD Portable]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra K1|Tegra K1 (TK1)]] || Unuiga Game PC U1, Snail Games OBox, UTStarcom MC8718, [[Nvidia SHIELD Tablet K1]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra X1|Tegra X1 (TX1)]] || [[Nvidia SHIELD TV]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{Yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 210 / 212 || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 410 / 412 / 415 / 425 / 430 / 435 || DragonBoard 410c (Turn off "MediaCodec" HW acceleration). Nobel64 Development Board || {{yes}} || {{yes}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 600 || [[Amazon Fire TV|Amazon Fire TV (2014)]], Compulab Utilite2, DragonBoard 600c, Inforce 6410Plus Development Board, Intrinsyc Open-Q 600 Development Board || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 610 / 615 / 618 / 620 / 625 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Qualcomm || Snapdragon 617 || Lenovo Moto G4 || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 652 || Samsung Galaxy Tab S2 || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 800 / 801 / 805 || [[Razor Forge TV]] || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 808 / 810 / 820 || HTC M9 (Turn off "MediaCodec" HW accelleration) || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Qualcomm || Snapdragon S4 || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Realtek || RTD1195 (RTK 1195) || || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Realtek || RTD1295 (RTK 1295) || || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Rockchip || RK3066 || Imito MX1/MX2, Minix NeoG4/X5, MK808/802, Ugoos UG802/UG007 || {{yes}} || {{?}} || {{no}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3188 || Jesurun DX05, Minix X7, MK802IV, MK809III, MK902, Ugoos UG007B, Tronsmart T428/MK908, CS968, CR11s, J22, GM282, LT88, T-R42, CS919-II, K-R42, CS918, MK888 || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3036 / RK3126 / RK3128 / RK3288 || Firefly-RK3288, ChipSpark PopMetal, Uyesee G1H, Nagrace HPH NT-V6, Eny Technology EKB318/EKB328, Kingnovel R6/K-R68, Beelink R28, FireFly FirePrime Development Board, Ugoos UT3/UM3, Rikomagic MK902 II, Measy B4S, Ruach A20s, CloudMedia OpenHour, CloudnetGo CR12/CR13CR16, Tronsmart Orion R28, Youku Box K1, Unuiga Game Box 19-6R || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3368 || Beelink i68, CloudnetGo CR18/CR13 Plus, Eny Technology EKB368, Himedia H7 III, Measy B4T, Ruach A20s-H, Rikomagic MK68, Tronsmart Orion R68, Zidoo X6/X6 Pro || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3228 / RK3228B / RK3228H || || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Rockchip || RK3229 / RK3399 || Firefly-RK3399, MXQ-4K || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Samsung || Exynos 3 Single (formerly Exynos 3110) || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 4 Dual/Quad series (formerly Exynos 4210 / 4212 /4412 / 4418) || [[ODROID|Hardkernel ODROID-U3/U2/X2]], FriendlyARM NanoPC-T1/NanoPC-T2 || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 5 Hexa/Octa series (Exynos 5260 / 5410/ 5420 / 5422) || [[ODROID|Hardkernel ODROID-XU/XU2/XU3/XU3 Lite]], Arndale Octa || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 7 Octa series (Exynos 7410 / 7420 / 7870) || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Samsung || S5P6818 (Octa Core) || FriendlyARM NanoPi M3 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Telechips || TCC898x || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Texas Instruments || OMAP4430 / OMAP4440 / OMAP5430 / OMAP5432 || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Texas Instruments || Sitara AM3358 / AM3359 || BeagleBoard Black || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Texas Instruments || Sitara AM5728 || BeagleBoard-X15 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|}

== Common codecs currently without hardware decoding in Kodi ==
Videos encoded with these codecs can only be played back in Kodi using software video decoding using CPU, meaning no decoding tasks are offloaded to optimized VPU or GPU hardware. Many videos may still play back just fine at standard definition resolutions, while others might have severe issues with playback.

As platforms with faster CPUs come out for Android software video decoding using CPU will get better, but do not expect miracles from the average Android box. It still all can depend on how demanding the decoding of that particular video encoding is or how high resolution it uses, and how powerful the CPU is.

* H.264 Hi10P - No hardware decoders for [[Hi10P]] (High 10 Profile, also known 10-bit H.264) currently exist for any ARM hardware. Most H.264 Hi10P videos will not play smoothly as most ARM CPUs are just not powerful enough to software decode it fast enough.
* H.264 MVC - No open source software decoder or hardware decoding for [http://en.wikipedia.org/wiki/Multiview_Video_Coding MVC (Multiview Video Coding)] stereoscopic 3D video decoding currently exist for Kodi on any platform. Kodi relies on FFmpeg for software demuxing and decoding, so Kodi have to wait for FFmpeg to first add software decoding support of MVC for H.264, and for hardware decoding Kodi relies on the SoC chipset hardware manufacturer to add support for this to their SDK (Software Developer Kits) and for the media player box manufacturers to implement that into their firmware images.
* H.265 MVC (HEVC MVC) - No open source software decoder or hardware decoding for [http://en.wikipedia.org/wiki/Multiview_Video_Coding MVC (Multiview Video Coding)] stereoscopic 3D video decoding currently exist for Kodi on any platform. Kodi relies on FFmpeg for software demuxing and decoding, so Kodi have to wait for FFmpeg to first add software decoding support of MVC for H.265 (HEVC), and for hardware decoding Kodi relies on the SoC chipset hardware manufacturer to add support for this to their SDK (Software Developer Kits) and for the media player box manufacturers to implement that into their firmware images.
* RealVideo/RMVB (RV 8/9/10) - There is currently no support in Kodi for RealVideo hardware video decoding, though software decoding of RMVB videos is possible via FFmpeg but can struggle with high definition sources on older or low-end hardware.
* VP8 (WebM v1 video) and VP9 (WebM v2 video) - There is currently no support in Kodi for VP8 hardware video decoding, though software decoding of VP8 videos is possible via FFmpeg but can struggle with high definition sources on older or low-end hardware. Most hardware manufacturers have not even implemented API support for VP8 decoding in the firmware images of Android for their devices, and this is despite the fact that the WebM project licenses VP8 hardware accelerators (RTL IP) to semiconductor companies for 1080p encoding and decoding at zero cost. Nvidia and Rockchip and a few other less known companies does however provide hardware decoding of VP8 in their SoCs, for Tegra 4 and RK29xx respectivly. ARM, Broadcom, Texas Instruments, and Qualcomm as well as ZiiLABS, ST-Ericsson, and Huawei have all announced upcoming support for hardware acceleration of the WebM format and VP8/VP9 codecs. Intel have also let its intention known that they will add hardware-based acceleration for WebM and VP8/VP9 codecs in its future Atom-based chips if the format gains popularity. VP9 does howver to this date not appear to have hardware decoding support in all but the very newest ARM SoCs for Android, such as exanple Nvidia Tegra X1 (TX1) used in Nvidia Shield TV.

==Notes==
<references />

== Device specific info ==
Here are a few device-specific guides/help areas that the community has provided.

{{Device notice}}


<dpl>
category = HTPC
category = Android
format = ,{{list2|%PAGE%}}
</dpl>

{{Isengard updated}}

[[Category:Android]]
[[Category:Hardware]]