> For the complete documentation index, see [llms.txt](https://docs.smartlauncher.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smartlauncher.net/products/faq/performance-and-battery/best-smart-launcher-setup-for-battery-friendly-phones.md).

# Best Smart Launcher setup for battery-friendly phones

Smart Launcher is already optimized to be energy efficient and, as explained in the page below, battery drain is usually influenced by broader usage and environmental conditions.

{% content-ref url="/pages/h96Q7S6XDSk7jyKgZ2NE" %}
[Performances](/products/faq/performance-and-battery/performances.md)
{% endcontent-ref %}

If you want to push battery saving further, here are some practical suggestions:

1. Disable features you do not use. If you do not use an SL feature or widget, removing it can help both battery usage and home screen clarity.
2. If your device has an AMOLED display, prefer a black or very dark wallpaper and use dark mode as much as possible.
3. Avoid live wallpapers, which typically consume more energy than static wallpapers.
4. Avoid widgets that refresh too often.
5. Reduce update frequency for features like random wallpaper rotation and news feed refresh.

Finally, remember that most battery monitoring tools provide rough estimates. If you notice unusual behavior, observe it for a few days, then change one variable at a time to understand what actually affects your battery usage.

If you think you found a bug, do not hesitate to contact us. We are here to help.

{% content-ref url="/pages/-LmFD-JI\_WDNokmjHe08" %}
[Device specific issues](/products/faq/common-issues/device-specific-issues.md)
{% endcontent-ref %}


---

# 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.smartlauncher.net/products/faq/performance-and-battery/best-smart-launcher-setup-for-battery-friendly-phones.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.