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.

This is a cherrypick of a later change back to Android P.

Test: manually boot with system time forced to the 0 epoch
Test: CTS
Bug: 65354678
Bug: 63711349
Bug: 122883482
Merged-In: I36bbe6dfebba79ad83ce536917d6893427a026dd
Change-Id: I36bbe6dfebba79ad83ce536917d6893427a026dd
(cherry picked from commit bfbd98868e56064f1c4813dcdbaedf87ced526ea)

0 files changed, 0 insertions, 0 deletions