Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.4f1
Issue ID
1129379
Regression
No
[Android] Incorrect Input.compass.trueHeading direction
Steps to reproduce:
1. Open user attached project
2. Build & Run to an Android device
3. Rotate the phone from lying down position to a vertical one
4. Vertically the true heading flips out
Expected result: Input.compass.trueHeading should output a more accurate direction on Android devices
Reproduced in: 2019.2.0a6, 2018.3.7f1, 2017.4.21f1
Devices under test:
Reproduced:
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880
VLNQA00117, Google Pixel 2 (Pixel 2), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00173, Xiaomi Redmi 6 Pro (Redmi 6 Pro), Android 8.1.0, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
No repro:
VLNQA00232 iPhone 8 Plus (iOS 12.1.2)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2019.3.X):
We are closing this due to lack of priority and urgency. Might consider in the future.