Search Issue Tracker
Fixed
Fixed in 2020.3.47f1, 2021.3.23f1, 2022.2.14f1, 2023.1.0b11, 2023.2.0a8
Votes
0
Found in
2020.3.42f1
2021.3.15f1
2022.1.24f1
2022.2.1f1
2023.1.0a22
2023.2.0a1
Issue ID
UUM-20754
Regression
No
[Android] Input.acceleration doesn't get the acceleration of some devices when disabling Input.gyro
How to reproduce:
1. Open the attached “IN-22916_1392784_gyro_accelerometer“ project
2. Build and Run for Android
3. In the Scene click the “gyro“ button to disable Input.gyro
4. Observe the top acceleration measurements
Expected result: Measurements of the linear acceleration of the device are being updated
Actual result: Measurements of the linear acceleration of the device aren’t updated
Reproducible with: 2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a22
Reproducible with these devices:
Samsung Galaxy S22 (SM-S901B), Android 12, CPU: Exynos 2200, GPU: Ltd.
Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: Exynos 9820 , GPU: Mali-G76
Samsung Galaxy S20+ 5G, Android 10, CPU: Exynos 990, GPU: Mali-G77
Not reproducible with these devices:
Samsung Galaxy Z Flip3 5G (SM-F711B), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Huawei - (ELS-NX9), Android 10, CPU: HiSilicon Kirin 990 5G, GPU: Mali-G76
Samsung Galaxy Note10+ 5G (SM-N976V), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Samsung Galaxy A52 (SM-A525F), Android 12, CPU: Snapdragon 720G (SM7125), GPU: Adreno (TM) 618
Samsung Galaxy Z Fold3 5G (SM-F926B), Android 11, CPU: Snapdragon 888, GPU: Adreno (TM) 660
VLNQA00494 - iPhone 14 Pro Max, 16.0.3 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Note: The customer reported that the issue is not reproducible with a new Input System
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2023.2.0a8):
Basically, this is a third-party issue.
On a few Samsung devices, ASENSOR_TYPE_LINEAR_ACCELERATION sensor is disabled, ASENSOR_TYPE_ACCELEROMETER callback is also unregistered. As a result, users cannot get any updated ASENSOR_TYPE_ACCELEROMETER values.
We solved the problem by adding defense code, but fundamentally Samsung should fix it.