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
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
WolveX
Feb 19, 2020 10:40
Why it still in review for 2017 LTS? why it is not available in latest version 2017.4.37 ?
ReneSchleese
Jan 21, 2020 09:22
The fix worked for me!
64bit apk built with Unity 2019.2.18 now runs smoothly again on our S7.
ReneSchleese
Jan 21, 2020 08:33
@hongjianxi:
No idea. Since this is a copy-paste from a bug report, and Unity encourages you to attach a project to said report, it is likely that the project is not publicly available.
From the release notes of 2019.2.18f:
"* Android: Fixed a physics performance issue on ARM64 on certain devices with power mode disabled. (1186295)"
Will test it on our problem device (Galaxy S7) soon.
hongjianxi
Jan 20, 2020 15:59
Where can I download the attached project "PerformanceDrop.zip"? Any link?
PNUMIA-Rob
Jan 13, 2020 17:33
Some of our users have also reported super laggy frame rates and we have confirmed that their devices are in the list, so we are also receiving lashback because of this issue.
@Unity -- Please fix this ASAP and release an updated engine right away.
Thanks in advance.
ReneSchleese
Jan 12, 2020 17:41
Having the same issue. Getting lots of negative reviews in Google Play store.
Why is this marked as "Fixed in 2019.3"? Reading through the 2019.3 patch logs it is listed under "Known issues".
osmanelbeyi
Jan 05, 2020 23:39
+1
having the same issue
Marcos-Elias
Dec 14, 2019 23:17
Still no solution for this very critical bug? We are getting lots of negative reviews on Google Play from people with these devices... Some people asking for refunds after the update and so on...
il2cpp seems to be not stable at all, we cannot rely on it... Mono 32-bit does not have this problem. Unfortunately most people don't like the idea of manually installing a game apk and obb to avoid it, and we cannot reach all the user base to ask for them to use the 32 bit that we provide.
Since Unity is one of the most popular game engines ever, IMHO they should talk more with Google before forcing us to use a "beta-bugged" feature like this :( Google could wait a little bit more for il2cpp to be considered stable before forcing everybody switching to it.
Otherwise we are completely stuck, we just cannot update or launch our games for Android.
Cenkakdag
Dec 06, 2019 18:23
Same problem here as well.
bryanunity
Dec 01, 2019 18:09
same problem, can not upload to Google.