Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a1
2018.3.10f1
2019.1.0a1
2019.2.0a1
Issue ID
1143263
Regression
No
[Android] Frequently changing the vSyncCount causes a black screen flicker
Steps to reproduce:
1. Open attached project
2. Build & Run to an Android device
3. Observe the flickering
Expected result: changing the target frame rate should not cause a black screen flicker
Reproduced in: 2019.2.0a11, 2018.3.10f1, 2017.4.25f1
Devices under test:
Reproduced;
VLNQA00218, Samsung Galaxy Note9 (SM-N960U), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00021, Samsung Galaxy S7 (SM-G930F), Android 7.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00117, Google Pixel 2 (Pixel 2), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00261, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Not reproduced:
iPhone 8 Plus (iOS 12.1.2)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2019.3.X):
Please, use Application.targetFrameRate in order to change frame rate