> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/resources/es/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-android-life-cycle-policy.md).

# Política de ciclo de vida de Remote Desktop Manager Android

La política de ciclo de vida de Remote Desktop Manager Android abarca la versión actual de Android y las tres versiones principales anteriores.

Devolutions garantizará la compatibilidad de Remote Desktop Manager con la versión actual del sistema operativo (SO) Android y las tres versiones principales que la preceden directamente (por ejemplo, desde Android 15 hasta Android 12).

Una «versión principal» se define como una versión oficial y numerada que incluye cambios, mejoras o actualizaciones significativas (por ejemplo, de Android 14 a Android 15). Es responsabilidad del usuario asegurarse de que su dispositivo funcione con una versión del SO móvil compatible con Remote Desktop Manager.

La compatibilidad con versiones anteriores del SO no está garantizada y puede provocar una funcionalidad reducida o la imposibilidad de uso. Devolutions no será responsable de ningún fallo, incapacidad de funcionamiento o problema de rendimiento de Remote Desktop Manager derivado de su uso en versiones no compatibles u obsoletas de sistemas operativos móviles, y se reserva el derecho, a su entera discreción, de determinar la fecha de fin de soporte de las versiones anteriores de los sistemas operativos móviles.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/resources/es/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-android-life-cycle-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
