WEBVTT

00:00:01.857 --> 00:00:03.987 align:middle line:90%
The fun of usagestats--

00:00:03.987 --> 00:00:06.147 align:middle line:84%
Alexis Brignoni wrote
a fantastic script

00:00:06.147 --> 00:00:07.147 align:middle line:90%
that we're going to use.

00:00:07.147 --> 00:00:09.957 align:middle line:84%
You can also run ALEAPP
against this entire lab

00:00:09.957 --> 00:00:13.767 align:middle line:84%
if you prefer that versus
command line usagestats.

00:00:13.767 --> 00:00:20.187 align:middle line:84%
Android 9 and below use XML
files for the usagestats.

00:00:20.187 --> 00:00:23.876 align:middle line:84%
Protobufs are used for
Android 10 and later.

00:00:23.876 --> 00:00:25.837 align:middle line:90%
ALEAPP will support both.

00:00:25.837 --> 00:00:27.597 align:middle line:84%
But what you have
to do is, you're

00:00:27.597 --> 00:00:31.046 align:middle line:84%
going to have to take this
date/time right here--

00:00:31.046 --> 00:00:33.777 align:middle line:84%
and doesn't it look
just slightly strange?

00:00:33.777 --> 00:00:37.497 align:middle line:84%
This is actually not encoded
the way we need it to be.

00:00:37.497 --> 00:00:39.567 align:middle line:90%
This is the date.

00:00:39.567 --> 00:00:42.907 align:middle line:84%
You have to add it to
the last active time.

00:00:42.907 --> 00:00:45.716 align:middle line:84%
So you have to take the date,
which is the file name, add

00:00:45.716 --> 00:00:50.216 align:middle line:84%
the active time for the app
of interest, divide by 1,000,

00:00:50.216 --> 00:00:53.546 align:middle line:84%
and then you have the Unix Epoch
date/time stamp that will work.

00:00:53.546 --> 00:00:56.636 align:middle line:84%
And some people may say, what
the heck did Heather just say?

00:00:56.636 --> 00:00:59.397 align:middle line:84%
It's a lot of work, and that's
why Alexis's script does it

00:00:59.397 --> 00:00:59.966 align:middle line:90%
for you.
