Search Issue Tracker

Active

Votes

0

Found in

2019.4

2020.3

2021.1

2021.1.18f1

2021.2

2022.1

Issue ID

1362976

Regression

No

[Android] Application.targetFrameRate changes after locking/unlocking the screen

--

-

Reproduction steps:
1. Open the attached project "FPSbug.zip"
2. Build and run to Android device
3. Observe the FPS counter in the top right corner of the screen
4. Lock and unlock the screen with a fingerprint
5. Observe the FPS counter again

Expected result: Framerate before and after locking remains at 60 fps
Actual result: Framerate after unlocking changes to 45 fps (as reported on users device - 40 fps)

Reproducible with: 2019.4.31f1, 2020.3.19f1, 2021.1.23f1, 2021.2.0b13, 2022.1.0a11
OnePlus 7T (HD1907), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640

Not reproducible with:
VLNQA00099, Google Pixel XL (Pixel XL), Android 10, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00380, Xiaomi MI 8 Lite (MI 8 Lite), Android 9, CPU: Snapdragon 660, GPU: Adreno (TM) 512

Couldn't test with:
VLNQA00004, Meizu MX5 (MX5), Android 5.0.1, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200 (Android too old)
VLNQA00381, Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), Android 9, CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4 (framerate is locked to 30 fps at all times)

Note:
Framerate can be reset to normal by minimizing/maximizing the application. On the user's device, as reported, it can also be reset by changing the screen orientation.
The user reported that it is also reproducible on Xiaomi Redmi Note 7, Android 11;

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.