Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.2.X, 2017.3.X, 2018.1.X
Votes
53
Found in
5.6.1f1
Issue ID
912848
Regression
No
[Android] Input.gyro is extremely laggy on specific device with Android 7.0
Steps to reproduce:
1) Download attached project 'AndroidAttitudeBug.zip' and open in Unity
2) Build and Run 'Main' scene on a device
3) Rotate device
You will see that Input.gyro.attitude and Input.gyro.userAcceleration appear to be lagging
Expected result: Input.gyro.attitude and Input.gyro.userAcceleration should not be lagging (check attached video 'expected.mp4')
Actual result: Input.gyro.attitude and Input.gyro.userAcceleration appear to be lagging (check attached video 'bug.mp4')
Reproduced with:
5.5.3p4, 5.6.1p1, 2017.1.0b6
Device under test:
Reproduced with:
Samsung SM G925F (Galaxy S6 Edge)*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760, Build:samsung/zeroltexx/zerolte:6.0.1/MMB29K/G925FXXU5DQA7:user/release-keys
Pixel 2
Not reproduced with:
Samsung SM G928F*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760, Build:samsung/zenltexx/zenlte:6.0.1/MMB29K/G928FXXS3BPIA:user/release-keys
Xiaomi Mi 4i*, OS:5.0.2, CPU:arm64-v8a, GPU:Adreno (TM) 405, Build:Xiaomi/ferrari/ferrari:5.0.2/LRX22G/V8.1.5.0.LXIMIDI:user/release-keys
Samsung SM G935F*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T880, Build:samsung/hero2ltexx/hero2lte:6.0.1/MMB29K/G935FXXU1BPLB:user/release-keys
iPad Air (iOS8.1.1)
Not reproduced when Galaxy S6 Edge was with Android 6.0.1
This issue has been reported to google: https://issuetracker.google.com/u/1/issues/69360770
------------------------------------
Fixed in:2017.2.2p2, 2018.1.0b10, 2018.2.0a1
Comments (20)
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Hobodi
Sep 12, 2018 14:12
2018.2.5f - gyro.input still drifting
Neogene
Apr 21, 2018 07:44
Reported on 2017.4.1f1 on Samsung S6 and A8, created issue# 1028669
Hiverlab
Jan 24, 2018 09:23
Report this issue:
Unity 2017.3
Pixel 2 XL
Samsung S6 Edge
Retinad
Dec 19, 2017 23:20
Problem still exists in Unity 2017.3.0f3 on Android Samsung Galaxy S6. Any workaround? @JAMES-DECARLO : Do you have a solution? I tried with Input.gyro.rotationRate, it is faster but it drift really fast...
arocha55
Nov 16, 2017 16:33
Also seen with Pixel 2 and Pixel 2 XL devices running Android 8.0 on Unity 2017.2.0f3.
Any updates on when can we expect a fix for this? It is affecting flag ship Android phones.
Thanks!
Hallihax
Nov 03, 2017 17:20
Also affects 2017.2.0f3 on (at least) Samsung S6
infuseMed
Oct 30, 2017 19:26
This issue occurs with 2017.1.1f1 with a Pixel 2 (but does not occur with Pixel 1 XL)
spacefrog
Oct 24, 2017 09:14
This heavily hurts my current development for the Galaxy S6/S7 series
Input.gyro.updateInterval does'nt work at all, always reporting 2E+10, even right after setting the value . Please Unity FIX THIS !
pezvolador
Oct 18, 2017 16:42
Not sure if it's strictly related to the issues described here, but I have experienced the same lag with a Huawei p8 lite 2017.
I ran sensor box and noticed that the gyro works extremely slow as is, so it may be malfunctioning. But anyway, is there any alternative method to avoid using the gyroscope when developing VR apps in unity?
The fact that some VR apps work just fine makes me think there must be some kind of workaround.
roppi2
Oct 16, 2017 11:15
Note @NODRAP's comment: despite the slow updating, I also had wrong (super tiny) gyroscope values on my Galaxy S6 Edge. I did a reboot as described by NODRAP and after that the gyroscope values were correct, even though the slow updating persisted.