Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2017.4.X, 2018.4.X, 2019.2.X, 2019.3.X
Votes
66
Found in
2017.4
2018.4
2018.4.9f1
2019.1
2019.2
2019.3
2020.1
Issue ID
1186295
Regression
No
[Android] 64 bit Build with Physics.Processing runs at a very low FPS
Steps to reproduce:
1. Open user's attached project "PerformanceDrop.zip"
2. Build it on Huawei Huawei mate 20 pro
3. Run it and tap on the screen
4. Notice a massive FPS drop to about 3 FPS
Expected results: The app is running at 30 Frames
Actual results: The app starts running at 13 Frames and drops to about 3 frames after interaction
Reproducible with: 2017.4.33f1, 2018.4.9f1, 2019.1.14f1, 2019.2.7f1, 2019.3.0b4, 2020.1.0a5
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
Samsung Galaxy Note10 (SM-N970U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Not Reproducible with:
VLNQA00166, Huawei P20 (EML-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00136, Samsung Galaxy S9+ (SM-G965F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00165, Samsung Galaxy S7 (SM-G930F), Android 7.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00216, Razer Phone 2 (Phone 2), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00121, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00027, Xiaomi MI MAX (MI MAX), Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00017, Huawei Nexus 6P (Nexus 6P), Android 8.0.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00287, Motorola moto g(7) power (moto g(7) power), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
Massive FPS drops on some 64bit Android devices
Comments (26)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
unity5_1
Nov 04, 2019 15:41
Experiencing the same issue
erenkumcuoglu
Nov 04, 2019 15:16
Experiencing this problem. Seems like a critical bug causes serious performance issues. Looking forward for a fix soonest.
denizyilmaz
Nov 04, 2019 15:15
Experiencing the same issue, urgent support would be great.
unity_tFOw_uSnlqvM7w
Nov 04, 2019 15:14
Same problem. It is important because 64 bit support is enforced by Google to publish the app.
orkunbicaker
Nov 04, 2019 15:10
We have the same problem. Since this is a very critical bug for our game, We kindly request an immediate correction.
eliteunity
Nov 04, 2019 14:59
Same problem. It is mission critical because Google no longer allows putting apps without 64 bit support on the app store.