WEBVTT

00:00:01.700 --> 00:00:04.580 align:middle line:84%
The most important part that
we are going to cover right

00:00:04.580 --> 00:00:05.930 align:middle line:90%
before you start your lab--

00:00:05.930 --> 00:00:08.900 align:middle line:84%
keyword searching in Physical
Analyzer can be buggy.

00:00:08.900 --> 00:00:12.410 align:middle line:84%
If you find a bug, please
report it to tech support.

00:00:12.410 --> 00:00:14.910 align:middle line:84%
If you're not confident
doing that, you can email me.

00:00:14.910 --> 00:00:17.420 align:middle line:84%
My Cellebrite email is
heather@cellebrite.com.

00:00:17.420 --> 00:00:18.512 align:middle line:90%
It's pretty easy.

00:00:18.512 --> 00:00:19.970 align:middle line:84%
There are different
ways to search,

00:00:19.970 --> 00:00:21.810 align:middle line:84%
and you have to
know what it means.

00:00:21.810 --> 00:00:24.890 align:middle line:90%
So we look at this first one.

00:00:24.890 --> 00:00:27.880 align:middle line:84%
Any of these terms versus
All of these terms.

00:00:27.880 --> 00:00:33.160 align:middle line:90%
Any means marsha or mallow.

00:00:33.160 --> 00:00:35.742 align:middle line:84%
So it's not-- if it
has a hit with marsha,

00:00:35.742 --> 00:00:36.700 align:middle line:90%
it's going to show you.

00:00:36.700 --> 00:00:38.440 align:middle line:84%
If it has a hit with mallow,
it's going to show you.

00:00:38.440 --> 00:00:39.898 align:middle line:84%
If it has a hit
with marsha,mallow,

00:00:39.898 --> 00:00:41.006 align:middle line:90%
it's going to show you.

00:00:41.006 --> 00:00:43.580 align:middle line:90%
You put a comma in between.

00:00:43.580 --> 00:00:47.540 align:middle line:84%
All of these terms will
be marsha and mallow.

00:00:47.540 --> 00:00:50.860 align:middle line:84%
None of these terms is
exactly what it says.

00:00:50.860 --> 00:00:53.800 align:middle line:84%
This checkbox right here,
Search in file contents--

00:00:53.800 --> 00:00:57.773 align:middle line:84%
this could add not only several
minutes but several hours,

00:00:57.773 --> 00:01:00.190 align:middle line:84%
depending on how complex you're
trying to make the search.

00:01:00.190 --> 00:01:01.978 align:middle line:90%
So be very careful with that.

00:01:01.978 --> 00:01:04.270 align:middle line:84%
In this next lab, I want you
to try all these searches.

00:01:04.270 --> 00:01:07.720 align:middle line:84%
It's a very tiny data set
on an older Android device

00:01:07.720 --> 00:01:09.830 align:middle line:84%
that if it crashes, it's
not the end of the world.

00:01:09.830 --> 00:01:11.290 align:middle line:90%
It's very quick to parse.

00:01:11.290 --> 00:01:13.632 align:middle line:84%
When you get your
search hits, you

00:01:13.632 --> 00:01:16.090 align:middle line:84%
will see that it's going to
tell you how many hits you have

00:01:16.090 --> 00:01:18.340 align:middle line:84%
and then you can start sorting
and looking through it.

00:01:18.340 --> 00:01:22.090 align:middle line:84%
You should find both
parsed information--

00:01:22.090 --> 00:01:25.900 align:middle line:84%
I should say more than just
both-- parsed information,

00:01:25.900 --> 00:01:28.390 align:middle line:84%
files that store
that information,

00:01:28.390 --> 00:01:30.880 align:middle line:84%
and potentially
unparsed data if you

00:01:30.880 --> 00:01:33.310 align:middle line:90%
choose Search in file contents.

00:01:33.310 --> 00:01:35.320 align:middle line:84%
Search in file
contents is supposed

00:01:35.320 --> 00:01:38.770 align:middle line:84%
to go through and look at every
single file in that file system

00:01:38.770 --> 00:01:40.180 align:middle line:84%
and find those
artifacts for you.
