> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/player-app/how-do-i-get-access-to-troubleshoot-the-player-app-for-android.md).

# How do I get access to troubleshoot the Player App for Android?

**Action and Navigation Bars** will come back at a touch or cursor movement.\
\
The most common menu items have been exposed by default:\
\
**Hide** - hide the Action Bar immediately (do not wait for the hide delay duration)\
\
**Status** - access the Status Dialogue

\
The **Menu** is accessible using the 3 stacked dots in the top right corner of the display.\
\
**Settings** - access the Settings Page\
\
**Check Licence** - allows manual confirmation of the software licence\
\
**About** - shows the About Window\
\
**Status Window** - used to determine what the Player is doing in real time with the primary use case for troubleshooting

**Connect to CMS** - connect a Player to the CMS providing a code

{% hint style="info" %}
If you require support via our help desk our support representative will find a screen shot of this status window useful!
{% endhint %}

Information shown is split into four areas:

**General Information**\
General configuration information to view settings and ensure they are correct. In particular the Licensed and Registered Status are important.

* **Licensed** flag to show whether the software is currently licenced or not. Possible values are “true (trial), true (FULL) and false”. If the Display is not licenced it will no longer download new content from the connected CMS.
* **Registered** flag to show whether the Display is registered with the CMS it is connected to. If not registered the Display will not be able to download any new content or schedules.

**CMS Status**\
Lists out the result of the last communication with the CMS. There are 3 messages transferred every collection interval (default 5 minutes) and all 3 should not have an error.

**Schedule Status**\
Shows the current schedule for the Player and the state of each Layout:

* **All Layouts**\
  Layouts that are downloaded but not necessarily currently in the schedule (for example a default Layout will be downloaded, but may not be shown if there are other Layouts scheduled).
* **Scheduled Layouts**\
  Layouts currently in the schedule will be listed.
* **Valid Layouts**\
  Layouts will be valid once all of their resources are downloaded.
* **Invalid Layouts**\
  Layouts with missing resources or blacklisted content will be invalid and removed from the schedule.
* **Blacklist**\
  If a media item is successfully downloaded and Xibo thinks it should play - but it doesn’t, under some circumstances it will be temporarily blacklisted. A good example is a video that has an unsupported codec.

**Log Messages -** list of the last 5 log messages recorded.

{% hint style="info" %}
This information is helpful to our support team during troubleshooting!
{% endhint %}

**About Window** - application version and EULA.<br>

#### **Closing the Xibo App**

Use the Home button on the navigation bar to close the application.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xibosignage.com/kb/player-app/how-do-i-get-access-to-troubleshoot-the-player-app-for-android.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.