summaryrefslogtreecommitdiff
path: root/tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
diff options
context:
space:
mode:
authorChristopher Tate <ctate@google.com>2018-12-11 14:55:19 -0800
committerChristopher Tate <ctate@google.com>2018-12-11 14:55:19 -0800
commit3d65d4d59533d6a789b5c9e901ee89cbff665a23 (patch)
tree1adf3b6f1c7637dc94239704bb2d2394fe68833a /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
parentb5555f6929640e0c114b103feda72d170a0ad632 (diff)
Be more comprehensive about boot time RTC check
If we detect that the RTC is uninitialized at boot time, we advance to the nearest safe estimated time that we can determine. We can't necessarily touch read/write filesystems at this point, so we have been using the timestamp of the root filesystem. Unfortunately, on retail devices that timestamp is often artificial, and quite far in the past by today's standards (e.g. some time in 2009). We now consult a variety of milestones to get a better estimate for the latest possible "the current date cannot be earlier than this" reference point: the root filesystem timestamp, the Build.TIME system variable, and the [ro.build.date.utc] system property if available. The latter two, in particular, are typically within at most two years of the current real time/date, rather than the eight or nine years of offset that we see with the root filesystem timestamp. Test: manually boot with system time forced to the 0 epoch Test: CTS Bug: 65354678 Bug: 63711349 Change-Id: I36bbe6dfebba79ad83ce536917d6893427a026dd
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions