> 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/widget-issues.md).

# Widget issues

Fix common widget setup, refresh, and disappearance problems.

Widget behavior on Android can be inconsistent across apps, launchers, and device manufacturers.

These are the most common widget issues in Lawnchair and how to fix them.

<details>

<summary>Widget not appearing or crashing during setup</summary>

This can happen with widgets that open a setup screen, especially on older Android versions.

To fix it:

1. Temporarily change your default launcher to your system's default launcher (e.g., Pixel Launcher, One UI Home).
2. Open Lawnchair.
3. Attempt to add the widget you want to use.
4. Set Lawnchair as the default launcher again.

</details>

<details>

<summary>Widget data not updating</summary>

If a widget's information is not updating:

1. Resize the widget to a different size, then return it to its original size.
2. Open the app that provides the widget:
   1. Check that the app has the permissions it needs.
   2. Clear the app's cache.

</details>

<details>

<summary>All widgets disappeared from the home screen</summary>

This can happen after the home screen has been inactive for a while.

To fix it:

1. Long-press the home screen, then tap **Home settings**.
2. Tap **More** <i class="fa-ellipsis-vertical">:ellipsis-vertical:</i>, then tap <i class="fa-arrow-rotate-left">:arrow-rotate-left:</i> **Restart Lawnchair**.

</details>


---

# 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/widget-issues.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.