Call logs-- now, do not get confused.
This is not a typo.
We have com.android.prov iders.contacts/databases,
contacts2.db again.
So contacts2.db is busy.
It's storing your contacts in those four different databases.
But it's also storing calls in a table of interest called calls.
Starting with Android 7, but not used until Android 8,
which is strange, calllog.db was introduced.
Now, what's strange is, on my Android 8 device
when I was doing testing, I had calls in both contacts2
and in calllog.
If the user upgrades, let's say, they upgrade from 7, 8, to 9,
to 10, you may find call logs in both locations.
So just quickly scan it to make sure your tool is not
missing something.
In calllog.db, your table of interest is going to be calls.
And we can see here, we have number.
This is me just writing a quick query.
So we have the number.
You'll also notice, under ID, do you see all the gaps?
I would sort by that to make sure you
can see which ones are deleted.
We have Timestamp, the name, Duration_in_Seconds,
the type of call it is--
all of the information across the top.
There is a query in your notebook for this file.
Most of the tools are parsing it.