Permission Overview

The library requires at least the following permissions to access MOVE SDK services.

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

Depending on the used services, different permissions are required. The following table gives an overview what's required:

Mode of Transport	Driving	ACCESS_FINE_LOCATION	ACTIVITY_RECOGNITION [2]
		ACCESS_BACKGROUND_LOCATION [5]	POST_NOTIFICATIONS [4]
			BLUETOOTH_CONNECT
			GooglePlayLocationAccuracy [1]
	Cycling	ACCESS_FINE_LOCATION	GooglePlayLocationAccuracy [1]
		ACCESS_BACKGROUND_LOCATION [5]
		ACTIVITY_RECOGNITION	POST_NOTIFICATIONS [4]
	Walking	ACTIVITY_RECOGNITION	POST_NOTIFICATIONS [4]
		ACCESS_BACKGROUND_LOCATION [5]
Driving Services	Distraction-Free-Driving (DFD)	ACCESS_FINE_LOCATION
		READ_PHONE_STATE
		SYSTEM_ALERT_WINDOW [6]
	Driving behaviour events (DBE)	ACCESS_FINE_LOCATION
Other services	Points of Interest	ACCESS_FINE_LOCATION
		GooglePlayLocationAccuracy [1]
	Public Transport	ACCESS_FINE_LOCATION
		ACTIVITY_RECOGNITION
		GooglePlayLocationAccuracy [1]
	Automatic Impact Detection	ACCESS_FINE_LOCATION	GooglePlayLocationAccuracy [1]
	Assistance Call		ACCESS_FINE_LOCATION [3]
		FOREGROUND_SERVICE_LOCATION	Allows a regular application to use Service.startForeground with the type "location".
		REQUEST_IGNORE_BATTERY_OPTIMIZATIONS	Permission an application must hold in order to use Settings.ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS.
		BLUETOOTH	Phone call/speaker switch recognition.
		BLUETOOTH_CONNECT	Needed only for communicates with already-paired Bluetooth devices. Android 12
		BLUETOOTH_SCAN	Needed to scan devices such as BLE.
		BLUETOOTH_ADMIN	Needed to scan devices on Android 11 and lower.
		CHANGE_NETWORK_STATE	To check internet connection in background.
	Health	READ_STEPS	Health Connect
		READ_HEALTH_DATA_IN_BACKGROUND	Health Connect

[1] GooglePlayLocationAccuracy = isNetworkLocationPresent + isNetworkLocationUsable

[2] improves trip recognition and classification considerably

[3] required permission deprecated with v2.4.0+

[4] see POST_NOTIFICATION Runtime Permission

[5] Since SDK 2.6: if backgroundLocationPermissionMandatory in MoveOptions is true the permission ACCESS_BACKGROUND_LOCATION is mandatory else this permission is optional.

[6] Since SDK 2.6.9: if overlayPermissionMandatory in MoveOptions is false the permission SYSTEM_ALERT_WINDOW is NOT mandatory anymore. Attention: in this case the device must be equipped with a gyroscope!

Grant the Background Location permission is strongly recommended. Similarly for the optional Activity Recognition permission (Driving) - make sure to request this from the user, otherwise it will degrade the quality of the service.

More Information regarding the Android system permissions can be found here: https://developer.android.com/reference/android/Manifest.permission

The required permissions must be granted before the MOVE SDK service can be used. If any single required permission is missing, the entire MOVE SDK stops working. In case of missing permissions this will be presented by MoveServiceFailure and/or by MoveServiceWarning.

For more information about "dangerous permissions" visit the official developer page.

In fact the MOVE SDK is not aware of permission changes, the developer can tell the MOVE SDK that the error is resolved.

MoveSdk moveSdk = MoveSdk.get();
if (moveSdk != null) {
    List<MoveServiceFailure> errors = moveSdk.getServiceErrors();
    if (!errors.isEmpty()) {
        moveSdk.resolveError();
    }
}