1---
2title: Supported devices
3---
4
5The minimum Android versions required for core ExoPlayer use cases are:
6
7| Use case | Android version number | Android API level |
8|----------|:------------:|:------------:|
9| Audio playback | 4.1 | 16 |
10| Video playback | 4.1 | 16 |
11| DASH (no DRM) | 4.1 | 16 |
12| DASH (Widevine CENC; "cenc" scheme) | 4.4 | 19 |
13| DASH (Widevine CENC; "cbcs" scheme) | 7.1 | 25 |
14| DASH (ClearKey; "cenc" scheme) | 5.0 | 21 |
15| SmoothStreaming (no DRM) | 4.1 | 16 |
16| SmoothStreaming (PlayReady SL2000; "cenc" scheme) | AndroidTV | AndroidTV |
17| HLS (no DRM) | 4.1 | 16 |
18| HLS (AES-128 encryption) | 4.1 | 16 |
19| HLS (Widevine CENC; "cenc" scheme) | 4.4 | 19 |
20| HLS (Widevine CENC; "cbcs" scheme) | 7.1 | 25 |
21
22For a given use case, we aim to support ExoPlayer on all Android devices that
23satisfy the minimum version requirement. Known device specific compatibility
24issues are listed below. Device specific issues on our GitHub issue tracker can
25be found
26[here](https://github.com/google/ExoPlayer/labels/bug%3A%20device%20specific).
27
28* **FireOS (version 4 and earlier)** - Whilst we endeavour to support FireOS
29  devices, FireOS is a fork of Android and as a result we are unable to
30  guarantee support. Device specific issues encountered on FireOS are normally
31  caused by incompatibilities in the support that FireOS provides for running
32  Android applications. Such issues should be reported to Amazon in the first
33  instance. We are aware of issues affecting FireOS version 4 and earlier. We
34  believe FireOS version 5 resolved these issues.
35* **Nexus Player (only when using an HDMI to DVI cable)** - There is a known
36  issue affecting Nexus Player, only when the device is connected to a monitor
37  using a certain type of HDMI to DVI cable, which causes video being played too
38  quickly. Use of an HDMI to DVI cable is not realistic for an end user setup
39  because such cables cannot carry audio. Hence this issue can be safely
40  ignored. We suggest using a realistic end user setup (e.g., the device
41  connected to a TV using a standard HDMI cable) for development and testing.
42* **Emulators** - Some Android emulators do not properly implement components of
43  Android's media stack, and as a result do not support ExoPlayer. This is an
44  issue with the emulator, not with ExoPlayer. Android's official emulator
45  ("Virtual Devices" in Android Studio) supports ExoPlayer provided the system
46  image has an API level of at least 23. System images with earlier API levels
47  do not support ExoPlayer. The level of support provided by third party
48  emulators varies. Issues running ExoPlayer on third party emulators should be
49  reported to the developer of the emulator rather than to the ExoPlayer team.
50  Where possible, we recommend testing media applications on physical devices
51  rather than emulators.
52