Search Issue Tracker
Fixed in 2017.2.X
Votes
9
Found in
5.4.3f1
Issue ID
867885
Regression
No
Time.realtimeSinceStartup returns delayed time when Android device screen is locked
Reproduction steps:
1. Open the attached project
2. Build the project on Android device
3. Prepare stopwatch
4. Run the project on Android device
5. Start the stopwatch when splash screen appears
6. In the project application press "start" button
7. Lock the device and wait about 20 seconds
8. Unlock the device and notice that the time on the application is delayed
Expected result: Time on the application and on the stopwatch should be synchronized
Actual result: Time on the application and on the stopwatch aren't synchronized (check "repro.mp4")
Note:
- Issue doesn't reproduce when phone is charging
Reproduced on:
5.3.7p3, 5.4.3f1, 5.4.4p1, 5.5.0p4, 5.6.0b3
DUT(repro):
Meizu MX5 with Android 5.0.1
Motorola Moto E with Android 4.4.4
DUT(no repro):
Lumia 520 with Windows Phone 8.1
Comments (3)
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
luckin
Jul 28, 2017 03:08
please backport to Unity 5.5
Kaan-Yy
Apr 12, 2017 06:50
I have had the same problem with an IOS device and opened a bug:
https://fogbugz.unity3d.com/default.asp?892103_vj9qm1ibm5087n1j
dlegare_scientific
Feb 14, 2017 22:51
This issue also happens for me on iOS, though not on all devices. I have two iPad 4s, on one Time.realtimeSinceStartup works as expected, on the other time doesn't progress as expected when the device is locked. Both are running iOS 10.1.1. If this is a separate issue then I'll file a bug report, but they sound similar to me.