Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
1
Found in
2018.4
2019.4
2019.4.17f1
2020.2
2021.1
2021.2
Issue ID
1304067
Regression
No
[Android] Input.Compass.headingAccuracy is always set to 0
Reproduction steps:
1. Download and open the user-submitted project "UnityCompass.zip"
2. Build and run for Android
3. Inspect the "HeadingAccuracy unity" log in the built project
Expected result: A varying value is logged
Actual result: 0 is logged
Reproducible with: 2018.4.30f1, 2019.4.18f1, 2020.2.2f1, 2021.1.0b3, 2021.2.0a2
Reproduced on:
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: NOT FOUND, GPU: Mali-G72
VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno (TM) 308
VLNQA00321, Xiaomi MI 9 (MI 9), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
-
nghianv7
Dec 26, 2022 06:54
Reproduced on:
Unity 2020.3.9f1Device: XiaoMi Redmi Note10S / Android 12
-
yosun
Feb 07, 2021 03:26
Wow. can't believe this hasn't been fixed yet since 2014
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a3
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.26f1