When deploying apps which use Qt for Android Automotive modules, the permissions required are automatically added to the Android manifest file by the deployment tool. Some of the Qt for Android Automotive APIs are geared towards use cases that by their nature require more restricted permissions, such as implementing a launcher app or accessing vehicle properties.

In most cases, you do not need all the permissions that come with the module. If you only want to use the QAndroidNotificationListener from Qt Android Automotive Base Module without using the permissions that come from other APIs in the module, you can do so.

This page lists what permissions each Qt for Android Automotive module uses and adds to the manifest automatically and shows how to override the default deployment tool behavior to manually control the permissions added.

Permissions by module

Permissions in Qt Android Automotive Base Module

The following table outlines the permissions used by the Qt Android Automotive Base Module.

Permissions in Qt Android Automotive Media Module

The following table outlines the permissions used by the Qt Android Automotive Media Module.

Permissions in Qt Android Automotive Vehicle Module

The Vehicle C++ and Quick libraries do not require any permissions. However, the Qt Android Automotive Vehicle Module inherits all its required permissions from its Vehicle Properties Library. This generated library gives access to all properties of a vehicle available through the Android Car API, so all permissions for these properties are required.

The following table outlines the permissions used by the Qt Android Automotive Vehicle Module.

Permissions in Qt Android Activity View Module

The Qt Android Activity View Module uses the following permissions to be able to launch external Activities embedded into a QActivityView.

Note that removing any of these permissions can lead to undefined behavior, as the implementation uses different system components based on the specific Android version being used. This is also the reason why some permissions here are internal to Android itself. All of them are used for allowing full interaction with the embedded content.

Handling permissions manually

If you need more control over what permissions end up in the Android manifest, you can easily add a custom manifest file to your project. The steps to create such a manifest file template are described in the Qt Creator manual.

Once you have added the template Android manifest file, open it. You will find the placeholder for the permissions in it:

<!-- %%INSERT_PERMISSIONS -->

Remove that line to prevent the deployment from automatically adding all the permissions the modules list as their requirements. After this, you can manually add the permissions you would like to use there. For example, if you would like to state that your app uses the QUERY_ALL_PACKAGES permission, you would add an entry such as below:

<uses-permission android:name="android.permission.QUERY_ALL_PACKAGES" />