> 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/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-android-life-cycle-policy.md). # Remote Desktop Manager Android life cycle policy The Remote Desktop Manager Android life cycle policy covers the current Android version and the three preceding major releases. Devolutions will ensure compatibility of Remote Desktop Manager with the current version of the Android operating system (OS) and the three major versions that directly precede it (e.g., from Android 15 to Android 12). A “major version” is defined as an official and numbered release that includes significant changes, enhancements, or updates (e.g., Android 14 to Android 15). It is the user’s responsibility to ensure that their device is operating a version of the mobile OS that is supported by Remote Desktop Manager. Compatibility with earlier OS versions is not guaranteed and may result in diminished functionality or inoperability. Devolutions shall not be liable for any failure, inability to perform, or performance issues of Remote Desktop Manager arising due to its use on unsupported or outdated versions of mobile operating systems, and reserves the right, at its sole discretion, to determine the support end date for older versions of mobile operating systems. --- # 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/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-android-life-cycle-policy.md?ask=&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.