Search Issue Tracker
By Design
Votes
0
Found in
2017.3.1p3
Issue ID
1021765
Regression
No
[Android] LG G4 performance is very poor by comparison with Pixel2 and iPhone 6s
To reproduce:
1. Download attached project "ProfilingTest.zip" and open in Unity
2. Open "scene" scene
3. Select Cube
4. In Inspector find "Update Controller" script and in Update info > Garbage Info set to "Make Garbage" to True
6. Run logcat
7. Build and Run the project on a Device with a Development Build and Autoconnect Profiler checked
8. Take an example of a Profiler
9. Turn off Application and clear logcat
10. Select Cube
11. In Inspector find "Update Controller" script and in Update info > Garbage Info set to "Make Garbage" to False
12. Run logcat
13. Build and Run the project on a Device with a Development Build and Autoconnect Profiler checked
14. Take an example of a Profiler
15. Repeat 3 - 14 steps with every device - LG G4, Pixel 2 and iPhone 6s
Notes:
- Logcats are shared in the Comments section
- Profilers images are shared in the Comments section
- We do not have OnePlus 5 so I tested on Pixel 2 XL
- If we look at non-allocating screenshots LG vs Pixel 2 vs iPhone 6s, then we see that LG is slower and is more erratic / spikier
- If we look at the allocating screenshots LG vs Pixel 2 vs iPhone 6s, then we see that LG is still slower and is much more erratic / spikier
- Pixel 2, in general, is very stable and smooth
- iPhone 6s, in general, stays smooth but with the occasional large periodic spike and sometimes come upon troughs of even less time being consumed
Devices:
- LG G4, OS: 6.0, CPU: arm64-v8a, GPU: Adreno (TM) 418
- Google Pixel 2, OS: 8.1.0, CPU: arm64-v8a, GPU: Adreno (TM) 540
- iPhone 6s, iOS: 10.3.2, CPU: A9
Reproduced on Unity 5.6.5p4, 2017.1.3p3, 2017.2.2p3, 2017.3.2f1, 2017.4.1f1, 2018.1.0f1 and 2018.2.0a9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Timeline section stops rendering after restoring Profiler Window modules
- Cursor image does not update when Cursor.SetCursor is called again with CursorMode.Auto
- Crash on do_runtime_invoke when reopening a specific project after failing to build it
- Animations change speed when rigidbody is added
- Low FPS persists when re-entering Play mode after an extended session in a specific project
Add comment