# General Diagnostics Before attempting workarounds or opening a support ticket, collect the following diagnostic data. ## Environment Snapshot ```bash adb shell getprop ro.product.model adb shell getprop ro.build.version.release adb shell getprop ro.hardware adb shell dumpsys meminfo | head -n 50 adb shell dumpsys thermalservice | head -n 50 ``` ## Logs Enable Bitmovin player logs as described in [Enable Logging in Bitmovin Player SDK](https://developer.bitmovin.com/playback/docs/how-to-enable-logging-in-the-bitmovin-android-player). Once enabled, logs can be gathered by capturing an [Android bug report](https://developer.android.com/studio/debug/bug-report). ## Available Codecs ```bash adb shell cmd media.codec list # or older devices: adb shell dumpsys media.codec ``` Compare against the media codec string (e.g. `hvc1.1.6.L120`) to confirm support. *** ## Record Playback Context When reporting or analyzing: - Bitmovin Player Android SDK version - Device model, Android version - Player and Source configuration including stream urls - If possible, a link to the affected [analytics session](https://dash.readme.com/project/bitmovin-playback/v1/docs/how-to-activate-the-player-and-analytics-bundle-in-the-bitmovin-dashboard) ## Using Bitmovin Analytics for Error Tracking Bitmovin Analytics is a powerful tool when it comes to debugging errors. Follow the guide [Using Top-Errors for debugging](doc:using-top-errors-for-debugging) to how to utilize it for trouble shooting.