Search Issue Tracker
By Design
Votes
0
Found in
2019.3.14f1
2019.4
2020.1
2020.2
Issue ID
1264491
Regression
No
[Android] Android.JNI.CallVoidMethod 15-20ms stalls on OnePlus devices when using the haptic motor through a 3rd party plugin
Repro steps:
1. Open attached project
2. Make sure "Development Build" and "Autoconnect Profiler" are checked
3. Build and Run on Android
4. Press and hold the button at the bottom of the display
5. Observe the spikes in the profiler
Actual: Android.JNI.CallVoidMethod spikes appear in the profiler
Reproducible with: 2019.4.6f1, 2020.1.0b16, 2020.2.0a19
Tested and reproduced on these devices:
----------, Oneplus OnePlus 6 (ONEPLUS A6003), Android 10, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Did not reproduce on:
VLNQA00128, Samsung Galaxy Note8 (SM-N950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00225, Qualcomm (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00294, Oppo Reno Z 中国版 (PCDM10), Android 9, CPU: Mediatek MT6779 Helio P90, GPU: PowerVR Rogue GM9446
Notes:
- Reproduces on Mono and IL2CPP
- Could not test 2018.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
Add comment