Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.11f1
6000.0.0b11
7000.0.0a1
Issue ID
UUM-77043
Regression
No
[Android] Inconsistent frame rate due to increased "WaitForTargetFPS" usage in the Android Player
How to reproduce:
1. Open the "IN_65938" project
2. In the Build Settings "Run Device" dropdown, select the desired device
3. Enable Development Build and Autoconnect Profiler
4. Press Build And Run
5. Observe the Profiler
Expected result: Frame rate is stable
Actual result: Vsync value varies ~-4ms and frame rate is unstable
Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b7
Testing environment: Windows 10 Pro, Windows 11 (user reported)
Reproducible on: No other environment tested
Reproducible on these devices:
OnePlus 10 Pro 5G (user reported)
VLNQA00267, Samsung Galaxy S10 (SM-G975F), Android 12, CPU: Exynos 9 (9820), GPU: Mali-G76
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880
Not reproducible on these devices:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Notes:
- Limiting frame rate using "Application.targetFrameRate = 30;" still reproduce the issue
- Not reproducible on the Windows Standalone Platform
- Reproducible on Vulkan and OpenGLES3 Graphics API
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug as these happen on older devices. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Postpone, U7 ports.