Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.47f1
2021.3.22f1
2022.2.13f1
2023.1.0b11
2023.2.0a9
Issue ID
UUM-32686
Regression
No
[Android] Force upside down rotation doesn't work when autorotation is disabled in device settings
*Steps to reproduce:*
# Open the "[ScreenOrientation|https://github.cds.internal.unity3d.com/unity/ScreenOrientation20174-TestProject]" project
# In File > Build Settings switch to Android Platform
# Build and Run to the device
# Make sure that autorotation is disabled in the device settings
# Press on the "Portrait Upside Down" button
*Expected:* Rotation is forced and the device screen rotates to Upside Down Portrait mode
*Actual:* The device screen stays in Portrait mode
*Reproducible with:* 2020.3.47f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b11, 2023.2.0a9
*Reproducible with devices:*
* VLNQA00230 - OnePlus 6T (ONEPLUS A6013), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 9.0.0
* VLNQA00090 - Samsung Galaxy S8 (USA) (SM-G950U), CPU: Snapdragon 835 MSM8998, GPU: Adreno 540, OS: 7.0.0
* VLNQA00119 - Xiaomi Mi 5 (MI 5), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 8.0.0
*Not reproducible with devices:*
* VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 13
* VLNQA00467 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 12
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
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.