本文介绍了SensorEvent.timestamp绝对(UTC)时间戳?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我问自己什么在SensorEvent.timestamp时间戳手段。像3548712982000号出现。这是不确切的东西:自1970年以来等毫微秒/毫秒这或许有些溢出的错误?看来,因为它是在同一时间不同的设备不同!!!

I question myself what the timestamp in SensorEvent.timestamp means. Numbers like 3548712982000 occur. It is not plausible for anything: nanoseconds/milliseconds since 1970 etc. Is this maybe some overflow error? It seems as it is different on different devices at the same time!!!

推荐答案

刚上所以这个问题后,我找到了答案了几秒钟:见<一href="http://$c$c.google.com/p/android/issues/detail?id=7981">http://$c$c.google.com/p/android/issues/detail?id=7981在这里说,这些都是因为运行时间纳秒。

Just a few seconds after this question on SO I found the answer: See http://code.google.com/p/android/issues/detail?id=7981 where is said that these are nanoseconds since uptime.

Android的文件明确是否需要更新。

The android documentation definitively needs an update.

这篇关于SensorEvent.timestamp绝对(UTC)时间戳?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-04 23:09