For Google Maps, we saw Google Maps.
We saw that unique ID when we are
looking at some of the dumpsys in Section 2 at the beginning.
Now, we actually want to see what is stored on the device.
Google Maps is a giant mess.
And I apologize.
If you're an Apple user, Apple Maps is an equal mess.
It changes with every OS version.
It is drastically different.
So what I strongly recommend is that you
go to com.google.android.apps.maps,
and you look at every single database in that directory--
every single one.
Gmm_storage.db is one of the most prevalent.
What's awesome is you can use this database
and say that searches were conducted.
Now, notice what I just said-- searches.
You can search for something and never go there.
I could, right now, search for locations on Maui
and dream of taking a flight tonight and landing in Maui,
where am I going to eat?
It does not mean I went there.
So you're going to use this as a clue of interest.
And then, you would have to dig deeper
to put the person at that location.
But there's nothing that is going to magically just make
searches appear in gmm_storage.db if the user
or someone on that device is not searching for it.
So that's very important that you know that.
We are going to see that we're looking at this in hex.
Now, what's interesting, your tool, at best,
will parse just this.
So we can see it looks like The Ale House Columbia, Maryland.
And we can see that there's a link for it.
You may find Yelp reviews, all kinds of weird stuff.
You may find coordinates on how to get there.
We are going to take it a step further, though.