1

I'm developing an app that need to know the moment when the system startup, periodically.
I use System.currentTimeMillis(); to get the current "date" in millis.
I get the system elapsed real tine with SystemClock.elapsedRealTime().
I subtract the total time with the elapsed time, and I retrieve the system bootup time.

I would understand if the value change of milliseconds over time(different times in executing instructions). But for me it changes of seconds!!! Is very strange.
Someone have an idea of why?

Yohanes Khosiawan 许先汉
  • 2,453
  • 4
  • 24
  • 28
user2543740
  • 172
  • 1
  • 10
  • you mean "seconds" as for seconds from execution consecutive to (VERY VERY) consecutive execution? – eduyayo Nov 19 '14 at 08:24

1 Answers1

3

Differences of seconds (or even tens of seconds) should not be surprising. "Current Time" corresponds to what the user perceives from the clock displayed. If you watch the displayed clock, it will not always change immediately. Read the docs:

http://developer.android.com/reference/android/os/SystemClock.html

It's pretty clear that you can't depend on currentTimeMillis for much of anything where you need millisecond accuracy. However, in most applications you really don't need that level of accuracy...

If you are trying to determine "exact boot time" from a specific moment in time later, a few seconds probably is the best you will do. Besides, what qualifies as "booted"?? When the kernel is loaded? When the user can interact with the device? When the device screen lights up? When the device can actually be unlocked?

You should probably just listen for RECEIVE_BOOT_COMPLETED (Android - Start service on boot).

Here is the Android doc: http://developer.android.com/reference/android/Manifest.permission.html#RECEIVE_BOOT_COMPLETED

Community
  • 1
  • 1
Jim
  • 10,172
  • 1
  • 27
  • 36