---
title: Troubleshooting Android SDK issues
description: Learn how to troubleshoot issues with Android Monitoring.
breadcrumbs: >-
  Docs > RUM & Session Replay > Application Monitoring > Android and Android TV
  Monitoring > Troubleshooting Android SDK issues
---

# Troubleshooting Android SDK issues

## Overview{% #overview %}

If you experience unexpected behavior with Datadog RUM, use this guide to resolve issues quickly. If you continue to have trouble, contact [Datadog Support](https://docs.datadoghq.com/help) for further assistance.

## Check if Datadog RUM is initialized{% #check-if-datadog-rum-is-initialized %}

Use the utility method `isInitialized` to check if the SDK is properly initialized:

```kotlin
if (Datadog.isInitialized()) {
    // your code here
}
```

## Debugging{% #debugging %}

When writing your application, you can enable development logs by calling the `setVerbosity` method. All internal messages in the library with a priority equal to or higher than the provided level are then logged to Android's Logcat:

```kotlin
Datadog.setVerbosity(Log.INFO)
```

## RUM Debug Widget{% #rum-debug-widget %}

The [RUM Debug Widget](https://github.com/DataDog/dd-sdk-android/tree/develop/features/dd-sdk-android-rum-debug-widget) provides a floating overlay that displays key metrics such as memory usage, CPU load, and RUM events in real time. It is intended for debugging and development purposes only.

See the [module README](https://github.com/DataDog/dd-sdk-android/blob/develop/features/dd-sdk-android-rum-debug-widget/README.md) for setup instructions.

{% image
   source="https://datadog-docs.imgix.net/images/real_user_monitoring/android/android-rum-debug-widget.dbd0dd922c26913dd72794e259cfc513.png?auto=format"
   alt="The RUM Debug Widget overlay displaying real-time metrics including memory, CPU, threads, and GC rate, with an\nevents timeline showing Action, Resource, Slow, and Frozen event markers." /%}

## Migrating to 3.0.0{% #migrating-to-300 %}

If you've been using the SDK v2 or SDK v1, there are some breaking changes introduced in version `3.0.0`. See the [migration guide](https://docs.datadoghq.com/real_user_monitoring/guide/mobile-sdk-upgrade) for more information.

## "Deobfuscation failed" warning{% #deobfuscation-failed-warning %}

A warning appears when deobfuscation fails for a stack trace. If the stack trace is not obfuscated to begin with, you can ignore this warning. Otherwise, use the [RUM Debug Symbols page](https://app.datadoghq.com/source-code/setup/rum) to view all your uploaded mapping files. See [Investigate Obfuscated Stack Traces with RUM Debug Symbols](https://docs.datadoghq.com/real_user_monitoring/guide/debug-symbols).

## Further Reading{% #further-reading %}

- [dd-sdk-android Source code](https://github.com/DataDog/dd-sdk-android)
- [Explore Real User Monitoring](https://docs.datadoghq.com/real_user_monitoring)