> For the complete documentation index, see [llms.txt](https://docs.lawnchair.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lawnchair.app/troubleshooting/battery-optimization.md). # Battery optimization Stop background restrictions from breaking widgets, gestures, and reloads. Android includes power-saving features that stop apps from running in the background. That helps battery life, but it can also cause problems for launchers like Lawnchair. ### How battery optimization affects Lawnchair If your device’s system kills Lawnchair to save battery, you may experience the following issues: * Gestures, such as double-tap to sleep, stop working because the system disables the accessibility service * Widgets stop updating or become unresponsive * The home screen reloads or appears with a delay after leaving an app #### How to fix these issues To keep Lawnchair working reliably, turn off battery optimization for the app. Because each manufacturer handles these settings differently, the exact steps vary by device. Use the guide below for your device: {% embed url="" %} --- # 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.lawnchair.app/troubleshooting/battery-optimization.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.