Android hardware: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
{{mininav|[[Devices]]|[[Android]]}}
{{mininav|[[Devices]]|[[Android]]}}
This is a list of Android hardware devices that uses a SoC ([http://en.wikipedia.org/wiki/System-on-a-chip 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.  
This is a list of Android hardware devices that uses a SoC ([http://en.wikipedia.org/wiki/System-on-a-chip System on a Chip], which embeds CPU, GPU, VPU, etc. on a single integrated circuit, (also sometimes refereed to as as "chipsets" in this context), that will both run the XBMC application's GUI-engine as well as its hardware video decoding capabilities.  


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

Revision as of 18:15, 24 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 embeds CPU, GPU, VPU, etc. on a single integrated circuit, (also sometimes refereed to as as "chipsets" in this context), that will both run the XBMC application's GUI-engine as well as its hardware video decoding capabilities.

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

Some SoC manufacturers out there do claim that a few of their very latest chipsets does have such a powerful GPU (Graphics Processor Unit) with CPGPU capability that they are able to utilize optimized software decoders written for OpenCL that can off-load some or most of the video decoding processing to the GPU for some codecs, like example the HEVC / H.265 codec[1], but understand there is however no guarantee that XBMC will ever be able to utilize such software decoders, as such codecs are usually rely on proprietary code, cost money in royalties to use, or are closed source so might not compatible with XBMC's GPL license.

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?

These are some good websites for looking up the SoC (System on a Chip) chipset used in your Android hardware device:

Also a referense you can compare different SoC (System on a Chip) chipset specifications on system-on-a-chip.findthebest.com

Compatible shipsets

Note: Please only list devices that are able to play at least one of the three "video decoding" columns in Full HD with either hardware decoding using VPU (Video Processor Unit) or hardware accelerated / assisted using GPU (Graphics Processor Unit).

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

Avoid officially unsupported chipsets

Until further notice it is recommended that non-developers avoid hardware platforms that are not yet supported in XBMC mainline. Official support for chipsets that are not yet support today might be added at a later date, though there are no guarantees that they will all be developed for mainline.

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.[11]
  • 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.[12]
  • 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.[13]

ARM SoCs without NEON support

Team XBMC had to limit itself to officially only support SoCs which feature support for NEON instruction set (ARM's general-purpose SIMD engine) or the overall experience of XBMC is deemed to be too slow without those extra optimizations.

Examples:

  • Nvidia Tegra 1 and Tegra 2 SoCs CPUs lack support for NEON instruction set which XBMC mainline requires so will officially never be supported by Team-XBMC at xbmc.org or its community.

Notes

  1. ↑ 1.0 1.1 HEVC (High Efficiency Video Coding) a new video compression codec that follows the H.265 standard, it is an up and coming format which is not yet common, but is seen as the successor to H.264 / MPEG-4 AVC (Advanced Video Coding)
  2. ↑ 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
  3. ↑ 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
  4. ↑ MPEG-2 (also known as H.262 compression codec) compatibility usually also assumes included MPEG-TS (MPEG Transport Stream) support as used in broadcast systems such as DVB (DVB-C/DVB-S/DVB-T), ATSC and IPTV.
  5. ↑ VC-1 is based on Microsoft Windows Media Video 9 (WMV9/WMV3/WVC1/WMVA) codecs and is most commonly known for being used by Blu-ray Discs, Windows Media, Microsoft's Silverlight, Slingbox, and the now-discontinued HD DVD
  6. ↑ Ultra HD (Ultra High Definition) support means SoC can capable of decoding H.264 / MPEG-4 AVC and HEVC / H.265 encoded videos up to native 4K UHD (2160p) or 8K UHD (4320p) resolution and output to HDMI 2.0 / HDMI UHD
  7. ↑ 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)
  8. ↑ 8.0 8.1 8.2 8.3 8.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
  9. ↑ 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
  10. ↑ 10.0 10.1 Some devices might need an updated firmware from the hardware manufacturer for smooth 1080p playback. [1]
  11. ↑ 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
  12. ↑ http://forum.xbmc.org/showthread.php?tid=161793 XBMC is being ported to Freescale i.MX6 SoC series
  13. ↑ 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=69383"