Official Kodi Wiki - User contributions [en]

Talk:Android hardware

2015-05-09T13:53:53Z

Freechelmi: /* VP9 required for YouTube in 4K */

== unnecessary detail ==
I really appreciate any work that is done on the wiki, and I don't want to do anything to discourage people, but please resist the urge to add unnecessary detail on a page such as this. Normally details are good, but on this page the entire point is to help clear up a very confusing aspect of XBMC hardware support.

The three decoding categories are grouped basically by what you are likely to see as supported or not. There's no point in listing two codecs in their own columns if they are always supported in mediacodec/libstagefright/amlcodec. "H.264" is mentioned simply as the most common example of the common codecs. If a codec isn't currently supported by any chipset/decoding codec in XBMC then there's also no point in making a column for that, and it should instead be noted "globally". -- [[User:Ned Scott|Ned Scott]] ([[User talk:Ned Scott|talk]]) 00:47, 25 February 2014 (EST)

==VP9 required for YouTube in 4K==
VP9 hardware decoding support needed for YouTube support in 4K (2160p), plus even YouTube in 720p and 1080p benefits as it uses half the bandwidth on H.264 so wondering if that is not enough reason to have VP9 i this matrix for Android hardware? And yes there are already Android hardware out there now which supports hardware decode and it is also suppose to be supported via the Android MediaCodec API on those devices, not surprisingly since it is Google who promotes both VP9 and Android.
* http://youtube-eng.blogspot.de/2015/04/vp9-faster-better-buffer-free-youtube.html VP9 needed for "''faster, better, buffer-free YouTube videos''", and "''Thanks to our device partners, VP9 decoding support is available today in the Chrome web browser, in Android devices like the Samsung Galaxy S6, and in TVs and game consoles from Sony, LG, Sharp, and more. More than 20 device partners across the industry are launching products in 2015 and beyond using VP9.''"
* http://en.wikipedia.org/wiki/VP9 ''Chromium, Chrome, Firefox, and Opera support playing VP9 video format in the HTML5 video tag.''
— Preceding [[w:Wikipedia:Signatures|unsigned]] comment added by [[User:Gamester17|Gamester17]] ([[User talk:Gamester17|talk]] • [[Special:Contributions/Gamester17|contribs]]) 

::It's pointless to mention on this page until there is anything on the list that uses it in Kodi. Theoretical support means nothing to the people viewing this page. It either works in Kodi or it doesn't. -- [[User:Ned Scott|Ned Scott]] ([[User talk:Ned Scott|talk]]) 21:11, 4 May 2015 (EDT)

::@Ned Scott : Can you stop destroying other people work ? We want to choose an android Box with a VP9 decoding chipset, we don't care if Kodi does not support it , we know it's just a software matter to be integrated in few months. So please restore the VP8/VP9 columns. [[User:Freechelmi|Freechelmi]] ([[User talk:Freechelmi|talk]]) 09:53, 9 May 2015 (EDT)

==MPEG-2 CPU decode is not HW decode==
Should the matrix really be green for those hardware claiming "''MPEG-2 (CPU)''"? There is no way that we can verify performance of proper MPEG-2 software decode, especially with software decode with deinterlacing, so why not just put a "No" on devices which can only do MPEG-2 software decode? Hardware decode is hardware decode, and if a device can not perform hardware decode of a codec then that should not be green in my opinion. Most modern Android hardware today could now even software decode H.264 in 1080p but again that is noting that we can verify so we could not either list "''H.264 (CPU)''" or should we? — Preceding [[w:Wikipedia:Signatures|unsigned]] comment added by [[User:Gamester17|Gamester17]] ([[User talk:Gamester17|talk]] • [[Special:Contributions/Gamester17|contribs]]) 

:First, the ability to decode MPEG2 or not is a separate issue than being able to hardware deinterlace or not. There are several boxes that can hardware decode but not hardware deinterlace.

:There is a way to verify which boxes can play something, and that is with our eyes. That's what this page is all about. The end user doesn't care if it is the CPU or the VPU that is decoding the video. All that matters is if it works or not. For example Mac OS X can only hardware decode H.264, but no one cares because the CPUs on all supported Macs are pretty much all fast enough to handle everything else. It's never been something we've had to warn people about.

:If an Android box comes along and has no hardware decoding, but has an insanely fast CPU, then why would anyone care? It either works or it doesn't work. -- [[User:Ned Scott|Ned Scott]] ([[User talk:Ned Scott|talk]]) 21:16, 4 May 2015 (EDT)

Android hardware

2014-09-11T09:18:47Z

Freechelmi:

{{mininav|[[Android]]}}
<section begin="intro" />For most 1080p [http://en.wikipedia.org/wiki/High-definition_video high definition video]s, hardware video decoding is necessary for smooth video playback on Android devices. And this article contains a list of SoC's (System on a Chip, which is the CPU, GPU, VPU, etc. also known as "chipsets") for Android platforms that can playback common video codecs smoothly using XBMC. While some devices might be able to smoothly decode [http://en.wikipedia.org/wiki/Standard-definition_television standard definition] and even some 720p videos using only software video decoding, offloading a large part of video decoding tasks to an integrated VPU (Video Processor Unit) optimized specifically for that job is considered essential for most Android devices to playback high definition videos.<section end="intro" />

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

==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:

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

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

==Compatible chipsets==
These listed specific hardware SoC chipsets have at least partial hardware accelerated video decoding support in XBMC, though understand that for some devices you might first need to upgrade the hardware manufacturers firmware image on the device to achieve smooth 1080p playback. Please contact your hardware manufacturer support for an updated system update firmware and apply that upgrade image before installing XBMC.

{|
| '''Note:''' Please only list devices that are able to play at least one of the three "video decoding" columns in Full HD (1080p). Codecs that are less used are currently not listed here.<ref name="other codecs">Sych as WebM (VP8/VP9), Xiph Theora (VP3/Ogg), On2 TrueMotion VP6, and RealVideo/RMVB (RV 8/9/10)</ref> The "|| {{yes}} ||" mark indicates that the chipset should be able to play those codecs at least 1080p.
|}
{| width="100%" class="datatable"
|-
! rowspan="2" | Chip manufacturer !! rowspan="2" | SoC chipset !! rowspan="2" | Examples of Android media players using these SoC chipsets with XBMC support !! colspan="5" | Hardware video decoding !! rowspan="2" | Notes
|-
! H.264 !! MPEG-2 !! VC-1 / WMV 9 !! VP8 !! VP9
|-
| Allwinner || A31 / A31s / A80 || VidOn.me AV200, Justop Quadro, Mele A1000G/M8/M9, Measy B4K/U4K || {{yes}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Amlogic || AML8726-M1 / AML8726-M3 / AML8726-M6 / AML8726-MX / AML8726-MXS / AML8726-MXL || [[Pivos XIOS|Pivos XIOS DS]], GameStick (by PlayJam), Geniatech ATV1220/ATV520, MyGica TV420/TV500, JynxBox M1/M6, Matricom G-Box Midnight MX2 || {{yes}} || {{yes}} || {{yes}} || {{?}} || {{?}} ||
|-
| 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 || {{yes}} || {{yes}} || {{yes}} || {{?}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| Amlogic || S805 / M805 / S806 / M806 / S812 || Geniatech ATV585 / MyGica ATV585, Eny Technology MXQ || {{yes}} || {{yes}} || {{yes}} || {{?}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| MediaTek || MTK6589 / MT6589 / MT6589T / MT6589M || || {{yes}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Mstar || MSO9180 / MSO9180D1R / MSO 9810 || Kaiboer Q6/C9-M, MeLE V10, UyeSee T1H || {{yes}} || {{yes}} || {{?}} || {{?}} || {{?}} ||
|-
| Nvidia || Tegra 3 || [[OUYA]] || {{yes}} || {{no}} || {{no}} || {{?}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| Nvidia || Tegra 4 / Tegra 4i || ZTE FunBox, Mad Catz M.O.J.O., NanoTech Nuvola NP-1 / NP-C / NP-H1, Nvidia Shield || {{Yes}} || {{yes}} {{smaller|(CPU)}} || {{?}} || {{?}} || {{?}} ||
|-
| Nvidia || Tegra K1 || || {{Yes}} || {{yes}} {{smaller|(CPU)}} || {{?}} || {{?}} || {{?}} ||
|-
| Qualcomm || Snapdragon 600 || [[Amazon Fire TV]] (2014) || {{yes}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Qualcomm || Snapdragon S4 || || {{yes}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Rockchip || RK3066 || Imito MX1/MX2, Minix NeoG4/X5, MK808/802, Ugoos UG802/UG007 || {{yes}} || {{?}} || {{no}} || {{?}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback">Some devices might need an updated firmware system update image from the hardware manufacturer for smooth 1080p playback.</ref>
|-
| Rockchip || RK3188 || Jesurun DX05, Minix X7, MK802IV, MK809III, MK902, Ugoos UG007B, Tronsmart T428/MK908, CS968, CR11s, J22, GM282, LT88, T-R42, CS919-II, K-R24, CS918, MK888 || {{yes}} || {{yes}} {{smaller|(CPU)}} || {{?}} || {{?}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| Rockchip || RK3288 || || {{yes}} || {{yes}} {{smaller|(CPU)}} || {{?}} || {{?}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| Samsung || Exynos 3 Single (formerly Exynos 3110) || || {{yes}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Samsung || Exynos 4 Dual/Quad series (formerly Exynos 4210 / 4212 /4412) || ODROID-U3/U2/X2 || {{yes}} || {{yes}} {{smaller|(CPU)}} || {{yes}} {{smaller|(CPU)}} || {{?}} || {{?}} ||
|-
| Samsung || Exynos 5 Hexa/Octa series (Exynos 5260 / 5410/ 5420 / 5422) || ODROID-XU/XU2, Arndale Octa || {{yes}} || {{yes}} {{smaller|(CPU)}} || {{yes}} {{smaller|(CPU)}} || {{?}} || {{?}} ||
|-
| Texas Instruments || OMAP4430 / OMAP4440 || || {{yes}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|}

== Common codecs currently without hardware decoding in XBMC ==
Videos encoded with these codecs can only be played back in XBMC 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, while others might have severe issues.

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.265/HEVC
* 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 XBMC on any platform. XBMC relies on FFmpeg for software demuxing and decoding, so XBMC have to wait for FFmpeg to first add software decoding support.
* 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.
* RealVideo/RMVB (RV 8/9/10)
* WebM (VP8/VP9)

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

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

==Notes==
<references />

{{Gotham updated}}

[[Category:Android]]

Android hardware

2014-09-11T09:16:01Z

Freechelmi: /* Compatible chipsets */

{{mininav|[[Android]]}}
<section begin="intro" />For most 1080p [http://en.wikipedia.org/wiki/High-definition_video high definition video]s, hardware video decoding is necessary for smooth video playback on Android devices. And this article contains a list of SoC's (System on a Chip, which is the CPU, GPU, VPU, etc. also known as "chipsets") for Android platforms that can playback common video codecs smoothly using XBMC. While some devices might be able to smoothly decode [http://en.wikipedia.org/wiki/Standard-definition_television standard definition] and even some 720p videos using only software video decoding, offloading a large part of video decoding tasks to an integrated VPU (Video Processor Unit) optimized specifically for that job is considered essential for most Android devices to playback high definition videos.<section end="intro" />

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

==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:

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

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

==Compatible chipsets==
These listed specific hardware SoC chipsets have at least partial hardware accelerated video decoding support in XBMC, though understand that for some devices you might first need to upgrade the hardware manufacturers firmware image on the device to achieve smooth 1080p playback. Please contact your hardware manufacturer support for an updated system update firmware and apply that upgrade image before installing XBMC.

{|
| '''Note:''' Please only list devices that are able to play at least one of the three "video decoding" columns in Full HD (1080p). Codecs that are less used are currently not listed here.<ref name="other codecs">Sych as WebM (VP8/VP9), Xiph Theora (VP3/Ogg), On2 TrueMotion VP6, and RealVideo/RMVB (RV 8/9/10)</ref> The "|| {{yes}} ||" mark indicates that the chipset should be able to play those codecs at least 1080p.
|}
{| width="100%" class="datatable"
|-
! rowspan="2" | Chip manufacturer !! rowspan="2" | SoC chipset !! rowspan="2" | Examples of Android media players using these SoC chipsets with XBMC support !! colspan="5" | Hardware video decoding !! rowspan="2" | Notes
|-
! H.264 !! MPEG-2 !! VC-1 / WMV 9 !! VP8 !! VP9
|-
| Allwinner || A31 / A31s / A80 || VidOn.me AV200, Justop Quadro, Mele A1000G/M8/M9, Measy B4K/U4K || {{yes}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Amlogic || AML8726-M1 / AML8726-M3 / AML8726-M6 / AML8726-MX / AML8726-MXS / AML8726-MXL || [[Pivos XIOS|Pivos XIOS DS]], GameStick (by PlayJam), Geniatech ATV1220/ATV520, MyGica TV420/TV500, JynxBox M1/M6, Matricom G-Box Midnight MX2 || {{yes}} || {{yes}} || {{yes}} || {{?}} || {{?}} ||
|-
| 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 || {{yes}} || {{yes}} || {{yes}} || {{?}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| Amlogic || S805 / M805 / S806 / M806 / S812 || Geniatech ATV585 / MyGica ATV585, Eny Technology MXQ || {{yes}} || {{yes}} || {{yes}} || {{?}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| MediaTek || MTK6589 / MT6589 / MT6589T / MT6589M || || {{yes}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Mstar || MSO9180 / MSO9180D1R / MSO 9810 || Kaiboer Q6/C9-M, MeLE V10, UyeSee T1H || {{yes}} || {{yes}} || {{?}} ||
|-
| Nvidia || Tegra 3 || [[OUYA]] || {{yes}} || {{no}} || {{no}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| Nvidia || Tegra 4 / Tegra 4i || ZTE FunBox, Mad Catz M.O.J.O., NanoTech Nuvola NP-1 / NP-C / NP-H1, Nvidia Shield || {{Yes}} || {{yes}} {{smaller|(CPU)}} || {{?}} ||
|-
| Nvidia || Tegra K1 || || {{Yes}} || {{yes}} {{smaller|(CPU)}} || {{?}} ||
|-
| Qualcomm || Snapdragon 600 || [[Amazon Fire TV]] (2014) || {{yes}} || {{?}} || {{?}} ||
|-
| Qualcomm || Snapdragon S4 || || {{yes}} || {{?}} || {{?}} ||
|-
| Rockchip || RK3066 || Imito MX1/MX2, Minix NeoG4/X5, MK808/802, Ugoos UG802/UG007 || {{yes}} || {{?}} || {{no}} || <ref name="Firmware upgrade might be needed for smooth playback">Some devices might need an updated firmware system update image from the hardware manufacturer for smooth 1080p playback.</ref>
|-
| Rockchip || RK3188 || Jesurun DX05, Minix X7, MK802IV, MK809III, MK902, Ugoos UG007B, Tronsmart T428/MK908, CS968, CR11s, J22, GM282, LT88, T-R42, CS919-II, K-R24, CS918, MK888 || {{yes}} || {{yes}} {{smaller|(CPU)}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| Rockchip || RK3288 || || {{yes}} || {{yes}} {{smaller|(CPU)}} || {{?}} || <ref name="Firmware upgrade might be needed for smooth playback"/>
|-
| Samsung || Exynos 3 Single (formerly Exynos 3110) || || {{yes}} || {{?}} || {{?}} ||
|-
| Samsung || Exynos 4 Dual/Quad series (formerly Exynos 4210 / 4212 /4412) || ODROID-U3/U2/X2 || {{yes}} || {{yes}} {{smaller|(CPU)}} || {{yes}} {{smaller|(CPU)}} ||
|-
| Samsung || Exynos 5 Hexa/Octa series (Exynos 5260 / 5410/ 5420 / 5422) || ODROID-XU/XU2, Arndale Octa || {{yes}} || {{yes}} {{smaller|(CPU)}} || {{yes}} {{smaller|(CPU)}} ||
|-
| Texas Instruments || OMAP4430 / OMAP4440 || || {{yes}} || {{?}} || {{?}} ||
|}

== Common codecs currently without hardware decoding in XBMC ==
Videos encoded with these codecs can only be played back in XBMC 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, while others might have severe issues.

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.265/HEVC
* 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 XBMC on any platform. XBMC relies on FFmpeg for software demuxing and decoding, so XBMC have to wait for FFmpeg to first add software decoding support.
* 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.
* RealVideo/RMVB (RV 8/9/10)
* WebM (VP8/VP9)

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

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

==Notes==
<references />

{{Gotham updated}}

[[Category:Android]]