Search Issue Tracker
Won't Fix
Votes
21
Found in
5.4.0f3
Issue ID
871864
Regression
No
[Android]Input.gyro.attitude returns zero values when tested with Moto G 4th generation device
How to reproduce:
1. Download the attached project
2. Build and run on Motorola Moto G4
3. Move device and check logcat for returned values
Result: it gives zero values for Input.gyro.attitude
Reproducible: 5.3.7p3, 5.4.4p1, 5.5.1p1, 5.6.0b5
Note: I have also used Sensor Kinetics application to check if gyroscope works (User showed it in video)
DUT(reproduced):
Motorola Moto G (4) , Qualcomm Snapdragon 617, Adreno 405, OS 6.0.1
DUT(didn't reproduce):
Samsung Galaxy S7 [SM-G930V],Qualcomm Snapdragon 820, Adreno 530, OS 6.0.1
LG G5 [LG-H850], Qualcomm Snapdragon 820, Adreno 530, OS 6.0.1
Xiaomi Mi 4i , Qualcomm Snapdragon 615, Adreno 405, OS 5.0.2
Won't Fix: We cannot measure the attitude of this device because COMPASS and ROTATION_VECTOR sensors are missing.
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
- Select Preset "None" icon changes after switching tabs
- [Android] Crash when using xxHash3 and targeting the ARMv7 Architecture with IL2CPP Scripting Backend
- GameObject reference in a Script Component becomes missing when unpacking a variant of another Prefab variant
- Project Settings vertical separator position is not synchronized with the mouse position when dragging it horizontally
- Crash on PhysicsDebugDraw::SelectFiltering::Update when entering play mode with Physics Debug window docked and unfocused
zharramadar
Aug 16, 2017 19:16
I can confirm this bug in Unity 2017.1.0f3 with Moto G5.
saurabhk
Aug 14, 2017 08:10
I affirm this bug in Unity 5.6.0f3 with a Moto G4, Moto G4 Plus and MotoG2.
AdhikS
Aug 04, 2017 07:55
I can confirm this bug in Unity 5.6.0f3 with a Moto G4, Moto G4 Plus and MotoG2.
RJproz
Apr 14, 2017 15:16
This bug is coming in Unity 5.6.0 f3 too. Gyro.attitude not working in Moto G4 plus
EdgarTaor
Apr 08, 2017 23:57
I can confirm this bug in Unity 5.6.0f3 with a Moto G4 and Moto G4 Plus.