Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On some devices, the rotation rates exhibit a low-level drift on one or more rotation axes. The symptom expressions are not identical, but they appear to be related to low component quality (iPhone 5c versus higher end devices) and/or rough usage (drops, etc).
Test devices Kilo and Juliet (both iPhones 5c) are affected. Lay them flat on a table or hold them absolutely still in your hand, and you'll see the camera drift up or down to the min/max y values, and in an infinite rotation in the x direction.
In an ideal scenario, we could ask users to calibrate their gyroscopes and apply a corrective factor to all inputs. Barring that, the next best thing we can try is to add a low-pass filter which ignores input less than a given threshold. In my non-scientific testing with the only affected devices at my disposal, I found that a noise threshold between 0.10 and 0.15 filtered out the noise with a minimal loss in sensitivity. Less than 0.10 and the 360 camera position starts to drift. I'm using 0.12 for now.
See also: https://forums.developer.apple.com/thread/12049