> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting.md).

# Set up Crash Reporting

- [Disabling/Enabling Crash Reporting](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting/disabling-enabling-crash-reporting.md): Stop Luciq from sending crash reports from your Android app with a single method, and disable ANR capture separately while crash reporting stays on.
- [Deobfuscation for Android](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting/deobfuscation-for-android.md): This guide explains how to deobfuscate crashes in your Android apps to get fully readable stack traces for Java, Kotlin and C++.
- [Crash Reporting Callbacks](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting/crash-reporting-callbacks.md): Covered here is how to set up the callbacks that fire before every crash report is sent so that a specific block of code is executed in your Android app.
- [Reporting Crashes For Android](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting/reporting-crashes-for-android.md): See how crashes reach your Luciq dashboard from an Android app, automatically or reported manually, plus the crash-free session and user trends.
- [Capturing ANRs For Android](https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting/reporting-crashes-for-android/capturing-anrs-for-android.md): Compare the v1 and v2 ANR detection mechanisms in the Luciq Android SDK, with the trade-offs of each, so you can pick the one that fits your app.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.luciq.ai/android/set-up-luciq-for-android/set-up-crash-reporting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.