> 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/media-players/portrait-orientation-using-sony-bravia-soc-displays.md).

# Portrait Orientation using Sony Bravia SoC displays

Portrait orientation is only available on devices under RDM and must be selected using 'My Account'

To open the management page for the device follow the below steps:

1. From the **Hardware** section of My Account, scroll down to **A list of devices available for Remote Management**
2. Locate the entry for the Display and select **View Details** using the row menu

Once selected, the following CMS changes are required:

* Use a SurfaceView for Video Rendering? = **Off**
* Orientation: **Device Default**
* Video Engine: **ExoPlayer**
* Use Multiple Video Decoders: **Off**

{% hint style="info" %}
We recommend creating a dedicated [Display Settings Profile](https://xibosignage.com/manual/en/displays_settings) for your Sony Bravia inside the CMS.
{% endhint %}

{% hint style="info" %}
The Android TV user interface will not be rotated.
{% endhint %}


---

# 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.xibosignage.com/kb/media-players/portrait-orientation-using-sony-bravia-soc-displays.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.