WEBVTT

00:00:01.661 --> 00:00:05.081 align:middle line:84%
When we now look at data and
how it lives on the handset,

00:00:05.081 --> 00:00:08.441 align:middle line:84%
it's very important that you
understand solid state flash

00:00:08.441 --> 00:00:09.526 align:middle line:90%
memory properties.

00:00:09.526 --> 00:00:10.901 align:middle line:84%
Now, you're going
to see here, we

00:00:10.901 --> 00:00:16.271 align:middle line:84%
have this first 4-kilobyte
chunk that is in blue.

00:00:16.271 --> 00:00:18.611 align:middle line:84%
Data is going to be
written in these chunks.

00:00:18.611 --> 00:00:20.651 align:middle line:84%
And these are
referred to as pages.

00:00:20.651 --> 00:00:22.721 align:middle line:84%
Now, as data comes
into the device

00:00:22.721 --> 00:00:25.181 align:middle line:84%
or goes out of the
device, that page

00:00:25.181 --> 00:00:27.071 align:middle line:84%
has to be moved all
around the phone.

00:00:27.071 --> 00:00:29.961 align:middle line:84%
Otherwise, your device
would wear out and die.

00:00:29.961 --> 00:00:32.261 align:middle line:84%
If you think about this,
if data is constantly

00:00:32.261 --> 00:00:35.171 align:middle line:84%
being written to the
same place, your phone

00:00:35.171 --> 00:00:36.671 align:middle line:90%
is going to wear out.

00:00:36.671 --> 00:00:39.371 align:middle line:84%
To prevent that,
we have data that's

00:00:39.371 --> 00:00:41.891 align:middle line:84%
going to be moved
around the phone.

00:00:41.891 --> 00:00:43.281 align:middle line:90%
Let's think about this.

00:00:43.281 --> 00:00:45.581 align:middle line:84%
If you send me a
text message, there

00:00:45.581 --> 00:00:48.251 align:middle line:84%
is a database that exists
on that Android or iPhone.

00:00:48.251 --> 00:00:51.881 align:middle line:84%
And that could be in that first
blue chunk of information.

00:00:51.881 --> 00:00:54.791 align:middle line:84%
As it moves, if
I respond to you,

00:00:54.791 --> 00:00:57.221 align:middle line:84%
it's going to move to
a different location.

00:00:57.221 --> 00:00:59.411 align:middle line:84%
If you respond back
to me, it's going

00:00:59.411 --> 00:01:00.874 align:middle line:90%
to move to a different location.

00:01:00.874 --> 00:01:02.291 align:middle line:84%
But what I want
you to think about

00:01:02.291 --> 00:01:04.841 align:middle line:84%
is, you send me that
one text message,

00:01:04.841 --> 00:01:06.521 align:middle line:90%
and I never respond to you.

00:01:06.521 --> 00:01:07.961 align:middle line:90%
Not only do I not respond--

00:01:07.961 --> 00:01:09.191 align:middle line:90%
I ignore it.

00:01:09.191 --> 00:01:11.561 align:middle line:90%
But then I start texting my dad.

00:01:11.561 --> 00:01:14.321 align:middle line:84%
I text my brother
and my friends.

00:01:14.321 --> 00:01:16.991 align:middle line:84%
Every time I'm
accessing that database,

00:01:16.991 --> 00:01:18.424 align:middle line:90%
that data moves around.

00:01:18.424 --> 00:01:19.841 align:middle line:84%
Now, what's really
important is, I

00:01:19.841 --> 00:01:21.466 align:middle line:84%
realize you should
have never texted me

00:01:21.466 --> 00:01:24.981 align:middle line:84%
and I delete it to
cover our tracks.

00:01:24.981 --> 00:01:27.381 align:middle line:84%
Every time that
database moved around,

00:01:27.381 --> 00:01:33.231 align:middle line:84%
it could exist in another
chunk on this data set.

00:01:33.231 --> 00:01:36.321 align:middle line:84%
On that device, all of these
chunks that are moved around

00:01:36.321 --> 00:01:40.461 align:middle line:84%
are not erased until the
entire block is ready,

00:01:40.461 --> 00:01:44.421 align:middle line:84%
meaning each of these pages
are marked as no longer needed,

00:01:44.421 --> 00:01:46.161 align:middle line:90%
please delete me.

00:01:46.161 --> 00:01:49.401 align:middle line:84%
That entire data will
be erased in blocks.

00:01:49.401 --> 00:01:53.391 align:middle line:84%
This is what we are going to
talk about with wear leveling.

00:01:53.391 --> 00:01:56.511 align:middle line:84%
Wear leveling is not going
to exist on all devices.

00:01:56.511 --> 00:02:00.801 align:middle line:84%
But understanding how the data
exists on the actual device

00:02:00.801 --> 00:02:03.503 align:middle line:84%
is important with understanding
why you may uncover things

00:02:03.503 --> 00:02:05.586 align:middle line:84%
that the user thought they
had previously deleted.
