Constant stream of error messages in console log: "Invalid timestamps detected. Time step between successive gyroscope sensor samples is very small or not monotonic"

[ngokevin]

Issue by cemkod Wednesday Jan 13, 2016 at 00:55 GMT Originally opened as https://github.com/aframevr/aframe-core/issues/793

---

Device: Nexus 7 II Browser: Firefox 43.0

When running the examples, there is a constant stream of the following error message in console log: Invalid timestamps detected. Time step between successive gyroscope sensor samples is very small or not monotonic

Gyro controls seem to be responsive with no lag.

[eskalera]

Same issue here.

• Device: Epson Moverio BT-200
• Browser: Firefox 45

[dmarcos]

@eskalera Is this still an issue on master?

[eswara1997]

@dmarcos still having this error. I'm using a samsung s7 edge with firefox.

Edit: I was able to almost get rid of the error by going intoaframe.js and changing util.max_timestep and 'util.min_timestep' Is this bad. What should be done to solve this error.

[anthonybarsotti]

I'm having this error occur too using an iPhone 6 Plus. I'm not currently using Aframe but I'm using the WebVR polyfill so I feel like it's potentially related to that.

[perqa]

It is clearly related to WebVR polyfill. See webvr-polyfill.js:5706:

                if (deltaS <= Util.MIN_TIMESTEP || deltaS > Util.MAX_TIMESTEP) {
                    console.warn('Invalid timestamps detected. Time step between successive ' +
                    'gyroscope sensor samples is very small or not monotonic');
                    this.previousTimestampS = timestampS;
                    return;
                }```

[jsantell]

This appears to be still an issue: https://github.com/googlevr/webvr-polyfill/issues/201

If anyone can follow up there with more info (what are the timestamps? are they not updated or too small/large?), I'll check it out

[jsantell]

Closed via https://github.com/googlevr/cardboard-vr-display/pull/9 -- will be in the next polyfill release. To clarify, this just silences the messages and only displays once. In testing, was getting messages for this in iOS and Firefox for Android, but the pose estimation was still working just fine, so this clears out the console a bit. If anyone has issues with this warning AND poses are not working, would love to learn more!

[dmarcos]

@jsantell sweet! thanks.