Android hardware

From Official Kodi Wiki
Jump to navigation Jump to search
Home icon grey.png   ▶ Devices ▶ Android ▶ Android hardware

This is a list of Android SoC's (System on a Chip, which is the CPU, GPU, VPU, etc. Also known as "chipsets") that will use hardware video decoding with XBMC. For most HD videos, hardware video decoding is necessary for smooth video playback. While some devices might be able to do SD and even some 720 content using software video decoding, hardware video decoding is considered essential for most Android devices.

Basic requirements

Stop hand.png It is highly recommended for users to not make any hardware purchases in anticipation of running Kodi on Android without first researching the device you want to buy. Before you do buy, make sure multiple people have verified that it works! If in doubt, do not buy any hardware!
  • Kodi v17 and later requires Android 5.0 or higher.
  • x86 (Intel) or a NEON-compatible ARM-processor, (for example: Nvidia Tegra 3 and newer are fully supported by Kodi, while Tegra 2 and older are not).
  • The main aim for the Android port of Kodi is to foremost target media-players/set-top-boxes/sticks that connect to a large screen television and uses a standard remote control as its main interface device, (that is the same market as for HTPC).

How do I know what chipset I have?

Some places that are good for looking up the chipset/SoC (System on a chip):

Chipsets

Note: Please only list devices that are able to play at least one of the three "video decoding" columns in HD.

A Yes mark indicates the device should be able to play those codecs at least as high as 1080p resolution.
Chip
manufacturer
Chipset Examples Video decoding Notes
H.264
& others[1]
MPEG2 VC-1
Allwinner A31 (and A31s) Yes ? ? [2]
AMLogic AML8726-M1 Pivos XIOS (older), JynxBox M1 Yes Yes Yes
AMLogic AML8726-M3 Pivos XIOS (newer), TLBB, G-Box Midnight, Yes Yes Yes
AMLogic AML8726-M6 JynxBox M6, Yes Yes Yes
AMLogic AML8726-MX ATV1220, Mygica TV420/TV500, ATV520, G-Box MX2 Yes Yes Yes
Freescale i.MX6 Wandboard, Utilite, Udoo, Matrix TBS2910, CuBox-i Yes Yes Yes [3]
MediaTek MTK6589T Yes ? ?
Nvidia Tegra 3 OUYA, Yes SD & some 720 No [2]
Nvidia Tegra 4 Nvidia Shield, Yes Yes
(CPU)
? [2]
Qualcomm Snapdragon S4 Nexus 7 (2013), Yes ? ?
Rockchip RK3066 Imito MX1/MX2, Minix NeoG4/X5, MK808/802, Ugoos UG802/UG007 Yes ? No [4][2]
Rockchip RK3188 Tronsmart T428/MK908, CS968, CR11s, J22, GM282, LT88, T-R42, CS919-II, K-R24, CS918, MK888, Jesurun DX05, Minix X7, MK802IV, MK809III, MK902, Ugoos UG007B Yes Yes
(CPU)
? [4][2]
Samsung Exynos 3110 Yes ? ?
Samsung Exynos 4210 Yes ? ?
Samsung Exynos 4212 Yes ? ?
Samsung Exynos 4412 ODROID-U2/U3/XU Yes Yes
(CPU)
Yes
(CPU)
Texas Instruments OMAP4430 Yes ? ?

Avoid

  • Allwinner A1x (A10/A10s/A13) and A2x (A20/A23) because its VPU is not yet supported in XBMC mainline, so you need to use third-party builds which are not officially supported, and those builds not recommended for mainstream use by non-developers.
  • Freescale i.MX6 because its VPU is not yet supported in XBMC mainline, so you need to use third-party builds which are not officially supported, and those builds not recommended for mainstream use by non-developers.
  • Nvidia Tegra 2 SoC because its CPU lacks support for ARM's NEON instruction set which official XBMC mainline requires.

Notes

  1. Note goes here about common formats that are hardware decoded
  2. 2.0 2.1 2.2 2.3 2.4 Hardware decoding on this chipset and devices are processed using OpenMAX IL or AL via Android's MediaCodec API or LibStageFright video codec API
  3. Freescale i.MX6 VPU is not yet supported in XBMC mainline, so you need to use third-party builds which are not officially supported, and those builds not recommended for mainstream use by non-developers
  4. 4.0 4.1 Some devices might need an updated firmware from the hardware manufacturer for smooth 1080p playback. [1]