Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0f3
Issue ID
854739
Regression
Yes
[Android] Devices running aOS 4.1 and lower has visual artefacts after rotations has been changed in runtime
Details: when rotating android devices with aOS 4.1 and lower the screen produces visual artefacts
To reproduce:
1. run the attached project on device with aOS 4.1 or lower
2. rotate the device
Reproduces on 5.5.0b3 , 5.5.0b4 , 5.5.0b5 , 5.5.0b6 , 5.5.0f2 , 5.5.0f3
Does not reproduce on 5.4, 5.5.0b2
note: the screen is split 5+ times see image.
DUT: armeabi-v7a Adreno (TM) 225 720x1280 4.1.2 Samsung SC 06D (Galaxy S3)
Comments (1)
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
- Crash on TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
sadstorygr
Jun 06, 2018 22:50
If anyone is reading this I am having the same issue now in the latest version. After changing the screen orientation, from Landscape to portrait, a script of mine in the new scene is not getting the right height/width values. The device is Huawei P10 Lite. I managed to solve the problem by calling
void Update()
{
if (runScaller)
{
if (Screen.height > Screen.width)
{
MyScallingMethod();
runScaller = false;
}
}
}
It works, probably after few frames but it's very annoying.