Screen orientation reverts from Inverted Portrait to Landscape without user input: collect bug report to determine cause

Android

Your device managed by Esper is reverting from Inverted Portrait to Landscape orientation without any user action or Blueprint changes. This article helps you investigate the cause and apply the appropriate fix.

Before you begin

Gather the following information:

Your device name and model
The date and time when you first noticed the orientation reversion
Whether your Blueprint has screen orientation enforcement set to Provisioning Only or Always Apply
Whether multiple devices are affected or just one

How to determine if Always Apply is viable

The most reliable fix is to change your Blueprint orientation enforcement from Provisioning Only to Always Apply. This ensures Esper re-applies the correct orientation every time your device syncs with the Blueprint.

However, if your devices require different orientations depending on their deployment location (for example, devices connected to different TV screens), this approach may not work for your setup.

If all your devices can use the same orientation: Proceed to "How to change Blueprint orientation enforcement" below.
If your devices require different orientations: Skip to "How to collect a bug report" to help Esper investigate the root cause.

How to change Blueprint orientation enforcement

In the Esper Console, go to Blueprints.
Select the Blueprint assigned to your device.
Navigate to Device Settings → Screen Orientation.
Change Enforcement from Provisioning Only to Always Apply.
Save your changes.
Wait for your device to sync (typically within the next few minutes). Your device should revert to the correct orientation automatically.
Monitor the device over the next several days to confirm the orientation remains stable.

How to collect a bug report

If changing orientation enforcement to Always Apply is not feasible for your deployment, collect a bug report the next time the orientation reverts. This helps Esper engineering identify whether a third-party app, OEM system service, or other process is causing the reversion.

When you notice the orientation has reverted, go to the Esper Console.
Navigate to Devices & Groups → [Your Device Name] → Actions.
Click Request Bug Report.
Wait for the report to generate (this typically takes a few minutes).
Download the bug report once it is ready.
Contact Esper Support and attach the bug report to your ticket.

How to collect ADB logs if a bug report cannot be captured

If the orientation reverts when you cannot access the Esper Console, you can collect logs via Android Debug Bridge (ADB) instead. You will need a computer with ADB installed and a USB cable.

Connect your device to your computer via USB.
Open a terminal or command prompt on your computer.
Run the following command to capture the system logs:
```
adb logcat -d > orientation_logcat.txt
```
Review the output file and look for entries related to WindowManager, DisplayManager, ActivityManager, or SensorManager. These entries may indicate what triggered the orientation change.
Share this file with Esper Support.

How to verify the fix

After applying your fix (either by changing orientation enforcement or collecting a bug report), monitor your device for several days.
In the Esper Console, go to Devices & Groups → [Your Device Name] → Device Info.
Confirm that the reported orientation matches your expected orientation (Inverted Portrait).
If the orientation remains correct after multiple days, the issue is resolved.

Still need help?

If the orientation continues to revert, or if you need assistance collecting or interpreting logs, contact Esper Support and include the following:

Your device name and model
A bug report or ADB logs captured at or shortly after a reversion event
Your Blueprint's current orientation enforcement setting
Whether this issue occurs on one device or multiple devices