Decoder Errors

Decoder-related issues in the Bitmovin Android Player SDK indicate that the device’s hardware or software decoder failed to initialize, decode, or support the media stream. This page provides per-error explanations and links to troubleshooting resources.

ℹ️

Due to the fragmented device landscape within the Android ecosystem, occasional decoder errors are expected, especially on lower-end or less common devices. The Bitmovin Android SDK includes features to help recover playback when this occurs.

The error indicates that the decoder operation failed without a more specific subtype.
This error can originate from lower-level platform components and may be triggered by:

Common causes:

  • A generic failure that could not be categorised further.
  • Decoder query failures — the player was unable to query available codecs or capabilities from the Android MediaCodecList.
  • AudioTrack initialization failures — the audio output track could not be created or configured (for example, due to unsupported sample rates or channel layouts).
  • AudioTrack write operation failures — data could not be written to the audio output device, often caused by buffer underruns or hardware-level output issues.

Next steps:


The decoder could not be created or configured.
Common causes:

  • Vendor codec configuration failure
  • Limited resources, e.g. the required decoder is already used by a different player instance/ app

Next steps:


The decoder started but failed during playback.

Common causes:

  • Corrupt or unsupported bitstream segment
  • Exceeds runtime constraints (bitrate/fps/bit depth)
  • Surface rebind or backgrounding issues

Next steps:

  • Investigate error frequency and distribution in Bitmovin Analytics
  • Test lower resolution / alternate codec on affected devices
  • Capture logs to determine a root cause

The requested format is not supported by any decoder on the device. Try

Next steps:


The device supports the codec but not the requested level, resolution, or bitrate.

Next steps: