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
Comments (2)
-
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
- GfxDevice::UpdateBufferRanges when running UIBuilder tests
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a3
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.26f1