Android hardware: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
Line 60: Line 60:
|-
|-
| Samsung || Exynos 4412 || ODROID-U2/U3/XU || {{yes}} || {{?}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{?}} ||
| Samsung || Exynos 4412 || ODROID-U2/U3/XU || {{yes}} || {{?}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{?}} ||
|-
| Telechips || TCC8930, TCC8933, TCC8935 || Hotach HTV003, Mele X1000 || {{?}} || {{?}} || {{?}} || {{?}} || {{no}} || {{?}} ||
|-
|-
| Texas Instruments || OMAP4430 ||  || {{yes}} || {{?}} || {{?}} || {{?}} || {{no}} || {{?}} ||
| Texas Instruments || OMAP4430 ||  || {{yes}} || {{?}} || {{?}} || {{?}} || {{no}} || {{?}} ||
|}
|}


===Avoid===
===Avoid officially unsupported hardware===
* 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.
Until further notice it is recommended that non-developers avoid hardware platforms that are not yet supported in XBMC mainline, like example:
* 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.<ref>http://www.cnx-software.com/2013/12/20/xbmc-arm-news-allwinner-a20-a31-apk-released-10-discount-on-ouya-console/ VidOn.me AV100 features Allwinner A20 SoC and manufacturer claims XBMC support with their own builds</ref>
* 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.
* 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 1 and Tegra 2 SoCs because their CPUs lacks support for ARM's NEON instruction set which official XBMC mainline requires.
* TeleChips TCC893x (TCC8930/TCC8933/TCC8935) 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.<ref>http://www.cnx-software.com/2014/01/20/telechips-tcc893x-dual-core-arm-cortex-a9-cortex-m3-socs-tcc8930-tcc8933-tcc8935/ Mele X1000 and Hotach HTV003 features TCC8935 SoC and manufacturer claims XBMC support with their own builds </ref>
 
====SoCs which ARM CPU without NEON support====
XBMC had to limit itself to officially only support SoCs that feature support for ARM's NEON instruction set
* Nvidia Tegra 1 and Tegra 2 SoCs CPUs lack support for ARM's NEON instruction set which XBMC mainline requires so will official never be supported.


===Notes===
===Notes===

Revision as of 15:19, 20 February 2014

Home icon grey.png   ▶ Devices ▶ Android ▶ Android hardware

This is a list of Android hardware devices that uses a SoC (System on a Chip, which integrates CPU, GPU, VPU, etc. on a single integrated circuit, also sometimes refereed to as as "chipsets" in this context) that will use hardware video decoding with XBMC.

For most high definition videos (in 720p, 1080p or higher resolution), hardware video decoding via an integrated VPU (Video Processor Unit) circuit is necessary for smooth video playback on these low-power embedded systems. While many newer SoC based devices might be able to playback standard definition video and to some extent even some 720p resolution content using soley software video decoding on the CPU, hardware video decoding on a VPU that is purposely designed to decode high definition videos is considered essential for most Android hardware devices.

Basic requirements

See also: Supported hardware
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 Full HD using VPU (Video Processor Unit).

A Yes mark indicates the device should be able to play those codecs at least as high as 1080p resolution using hardware video decoding.
Chip
manufacturer		 Chipset Examples Hardware video decoding Notes
H.264 [1] MPEG-4 ASP[2] MPEG-2[3] VC-1 / WMV 9 HEVC / H.265 Other common
codecs/formats[4]
Allwinner A31 (and A31s) VidOn.me AV200, Justop Quadro, Mele A1000G, Mele M8, Mele M9, Measy B4K, Measy U4K Yes ? ? ? No ? [5]
AMLogic AML8726-M1 Pivos XIOS DS (older), JynxBox M1 Yes ? Yes Yes No ?
AMLogic AML8726-M3 Pivos XIOS DS (newer), G-Box Midnight Yes ? Yes Yes No ?
AMLogic AML8726-M6 JynxBox Android M6 Yes ? Yes Yes No ?
AMLogic AML8726-MX GameStick (by PlayJam), Geniatech ATV1220/ATV520, MyGica TV420/TV500, G-Box Midnight MX2 Yes ? Yes Yes No ?
Freescale i.MX6 Wandboard, Utilite, Udoo, Matrix TBS2910, CuBox-i Yes ? Yes Yes No ? [6]
MediaTek MTK6589T Yes ? ? ? No ?
Nvidia Tegra 3 OUYA Yes ? SD & some 720p No No ? [5]
Nvidia Tegra 4 Nvidia Shield Yes ? Yes
(CPU)		 ? No ? [5]
Qualcomm Snapdragon S4 Nexus 7 (2013) Yes ? ? ? No ?
Rockchip RK3066 Imito MX1/MX2, Minix NeoG4/X5, MK808/802, Ugoos UG802/UG007 Yes ? ? No No ? [7][5]
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)		 ? No ? [7][5]
Samsung Exynos 3110 Yes ? ? ? No ?
Samsung Exynos 4210 Yes ? ? ? No ?
Samsung Exynos 4212 Yes ? ? ? No ?
Samsung Exynos 4412 ODROID-U2/U3/XU Yes ? Yes
(CPU)		 Yes
(CPU)		 No ?
Texas Instruments OMAP4430 Yes ? ? ? No ?

Avoid officially unsupported hardware

Until further notice it is recommended that non-developers avoid hardware platforms that are not yet supported in XBMC mainline, like example:

  • 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.[8]
  • 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.
  • TeleChips TCC893x (TCC8930/TCC8933/TCC8935) 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.[9]

SoCs which ARM CPU without NEON support

XBMC had to limit itself to officially only support SoCs that feature support for ARM's NEON instruction set

  • Nvidia Tegra 1 and Tegra 2 SoCs CPUs lack support for ARM's NEON instruction set which XBMC mainline requires so will official never be supported.

Notes

  1. ↑ H.264 also known as MPEG-4 Part 10 or MPEG-4 AVC (short for MPEG-4 Advanced Video Coding) is known under many names and available in different container formats, probably most commonly known for being used by Blu-ray Disc movies
  2. ↑ MPEG-4 Part 2 or MPEG-4 ASP (short for MPEG-4 Advanced Simple Profile) decoder can decode H.263 and derivatives such as XviD, DivX, 3ivx, and Nero Digital
  3. ↑ MPEG-2 compatibility usually also assumes included MPEG-TS (MPEG Transport Stream) support as used in broadcast systems such as DVB, ATSC and IPTV.
  4. ↑ Note goes here about other popular video codecs and formats that can be hardware decoded, common examples are Google's WebM (VP8/VP9), Xiph Theora (VP3/Ogg), On2 TrueMotion VP6, and RealVideo/RMVB (RV 8/9/10)
  5. ↑ 5.0 5.1 5.2 5.3 5.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
  6. ↑ 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
  7. ↑ 7.0 7.1 Some devices might need an updated firmware from the hardware manufacturer for smooth 1080p playback. [1]
  8. ↑ http://www.cnx-software.com/2013/12/20/xbmc-arm-news-allwinner-a20-a31-apk-released-10-discount-on-ouya-console/ VidOn.me AV100 features Allwinner A20 SoC and manufacturer claims XBMC support with their own builds
  9. ↑ http://www.cnx-software.com/2014/01/20/telechips-tcc893x-dual-core-arm-cortex-a9-cortex-m3-socs-tcc8930-tcc8933-tcc8935/ Mele X1000 and Hotach HTV003 features TCC8935 SoC and manufacturer claims XBMC support with their own builds
Retrieved from "https://kodi.wiki/index.php?title=Android_hardware&oldid=69340"