I believe that you are just looking in the wrong place, clicking the Browse Data Tab and then selecting the Messages table will show if there is any data.

The reasoning is that you are looking at the Database Structure, this shows you the tables and the SQL that will/was used to create them and additionally the columns and the SQL for the column definitions.

Having the table named android_metadata very likely shows that the database has come from and Android device rather than from another source i.e. you only find it on Android devices.

Your screenshot shows that there is a table called Messages, this isn't auto-generated nor is it created by SQLite. It has at least two columns according to the screenshot. One is named type and has a defined column-type of INTEGER along with a NOT NULL constraint the other column is named entry and has a column_type of BLOB.

Here's a similar DB that's been copied from an emulator showing how this (populated with 1 row) appears when you look at the Database Structure (Friends is the table and the columns have been expanded).

Note that the Browse Data table has been highlighted and has an arrow pointing to it. Clicking this will show something like :-

This is browsing the data for the android_metadata table (just 1 row with 1 column). To the right of the highlighted table there is a dropdown click this and select the Messages table. You data will be shown e.g (obviously this is for the Friends table):-

• The table has 1 row with 6 columns
  • Column _id has a value of 1
  • Column _name has a value of Test name
  • and so on

Edit regards debugging information.

It is clear that the table you intend to copy/export from your emulator is not the database that you are looking at in DB Browser for SQLite. The database you have provided information for via the utilities provided is :-

/data/data/com.rss.feedster.rss_feedster/databases/rssFeeds

As such it is that file that you want to export copy and then open in DB Browser for SQLite.

It is not google_app_measurement_local.db

I think the issue is basically that you assumed that a database must have a .db file extension. The .db (file extension) does not affect the data it's used purely to indicate the type that the file may be.

I have little doubt that if you open the file indicated above then you will see that the data and structure are as you would expect. Note to see the file select All Files to the right of the File Name input.

As an example the following shows a file exported/copied as db1.rumplestiltskin and then opened in DB Browser for SQLite :-

The Fix

In the Device Monitor Export/Copy/Save the file /data/data/com.rss.feedster.rss_feedster/databases/rssFeeds and then open that in DB Browser for SQLite; noting that if it does not have a .db or .sqlite file extension then you will have to select All Files from the File Type selector to the right of the File Name input in order to be able to select the file from the file browser.

Perhaps have a read of Filename extension, which explains file extenstions in greater detail.