# Android debugger The Android debugger has the following particularities and limitations: \- Android on ARM is supported (not on x86) \- Both ARM and Thumb mode code is supported \- Multithreaded applications can be debugged. However, since the operating system does not report thread deaths, they are reported only when the debugger notices that the thread is missing (for example, because there is an error when we try to suspend it) \- Apparently Android reports applications that are currently executing a system call as executing "LDMFD SP!, {R4,R7}" before the syscall. Once the syscall completes, the next instruction is reached. \- Hardware breakpoints are not supported. See also * [Start process](https://docs.hex-rays.com/9.0/user-guide/user-interface/menu-bar/debugger/process-control/start-process) * [Debugger submenu](https://docs.hex-rays.com/9.0/user-guide/user-interface/menu-bar/debugger) * [How to launch remote debugging](https://docs.hex-rays.com/9.0/user-guide/debugger/remote-debugging) --- # Agent Instructions: 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: ``` GET https://docs.hex-rays.com/9.0/user-guide/debugger/remote-debugging/android-debugger.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.