Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2018.4
2018.4.12f1
2020.2
Issue ID
1259295
Regression
No
[Android] Screen orientation is not working on second display of LG V50 after the initial screen rotation
Reproduction steps:
1. Open the attached user's project "SecondScreenOrientation.zip"
2. Build and Run the project with LG V50
3. Open the installed app on the second screen
4. Rotate the device
Expected result: Screen orientation is working on the second display after the initial screen rotation
Actual result: Screen orientation is not working on the second display after the initial screen rotation (See attached SecondScreenOrientation.mp4)
Reproduces on: 2018.4.26f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0a21
Reproduced with these devices:
N/A, LG V50 ThinQ 5G (LMM-V500N), Android 10, CPU: Qualcomm Snapdragon 855 (SM8150), Adreno 640
Does not reproduce with these devices:
VLNQA00273, Vivo V1821BA (V1821A), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
N/A, Samsung Galaxy Fold (SM-F900F), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Notes:
-Screen orientation on the main screen is working as expected
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
- The Sprite Library Editor window has an incorrect order of Sprites when the Sprites are reordered and the order saved
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
Resolution Note (fix version 2021.1):
Fixed in 2021.1.6f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.7f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.26f1