does insertOrThrow() of class SQLiteDataBase autocommit the data?

My insert code looks like this

public void insertInTable(float x, float y, float z, int timestamp){

    try {
        ContentValues values = new ContentValues();
        values.put("x_val", x);
        values.put("y_val", y);
        values.put("z_val", z);
        values.put("timestamp", timestamp);

        db.insertOrThrow(DBHelper.tableName, null, values);
        Log.d(Constants.CUSTOM_LOG_TYPE, "Inserted successfully");

    catch (SQLiteException e) {
        Log.d(Constants.CUSTOM_LOG_TYPE, e.getMessage());

And its called from the following piece of code:

public void onSensorChanged(SensorEvent event) {

     ...values retrieved from event ....
     ...the inserted into db

    if (conditions met) {
        //****here the data is inserted****
        dbHelper.insertInTable(x, y, z, (int) timeInMillis);

This code inserts the data fine in the database, and when the db file is exported, the data inserted is present.

My question is how is the data being exported present without the committing the transaction ?

I tried looking into the documentation of [insertOrThrow](, java.lang.String, android.content.ContentValues)), but it doesn’t mention anything with regards to auto-commit.

autocommit is set to false , which I know because when I try inserting using execSQL(), the data is not exported without explicitly committing the transaction.

There is no use of transaction, commit or even setAutocommit(true).
How is the code working ? Am I missing something here ?