Permissions
Welcome to our guide on how smartphone permissions impact the functionality and performance of our Mobile Telematics SDK. Permissions are crucial for determining the extent to which our SDK can access and utilize smartphone features. This page explains the key permissions required and how each one contributes to the SDK's operation.
Below, you will find a comprehensive table that outlines each permission, detailing its specific impact on the SDK's performance and functionality. Additionally, the table presents different scenarios, illustrating how varying permission settings can affect the accuracy and completeness of the telematics data collected.
By understanding the role of each permission, you can ensure that your application is configured optimally, providing users with the best possible experience while maintaining the necessary levels of privacy and security.
Please refer to the table below for a detailed breakdown of smartphone permissions and their implications for our Mobile Telematics SDK.
iOS
iOS Permissions and the Telematics SDK
| Permissions | Why required | How no Permission affects tracking | How granted Permission affects tracking |
|---|---|---|---|
| Location - Don't Allow | |||
| Location - While in use | |||
| Location - 'Always allow' | It allows us to record tracking data continuously, even when the OS kills background processes or the app is not actively being used. | SDK and Tracking won't work | SDK will work as expected and record trip data (GPS data) |
| Bluetooth Enabled | Not required if you do not use a BLE device, which is not your case | No effect | No effect |
| Motion & Fitness Enabled | It provides access to smartphone sensors like Accelerometer and Gyroscope | 1. No incident detection (Braking, Acceleration, Cornering, Phone usage) 2. Affects automatic trip detection | 1. SDK will work as expected and detect incidents (Braking, Acceleration, Cornering, Phone usage) 2. improves automatic trip detection |
Android
| Permissions | Why required | How no Permission affects tracking | How granted Permission affects tracking |
|---|---|---|---|
| Location - Deny | |||
| Location - While in use | |||
| Location - Allow all the time | It allows us to record tracking data continuously, even when the OS kills background processes or the app is not actively being used. | SDK and Tracking won't work | SDK will work for up to 5 min if the app is opened |
| Physical Activity | It provides assess to smartphone sensors like Accelerometer and Gyroscope | 1. No incident detection (Braking, Acceleration, Cornering, Phone usage) 2. Affects automatic trip detection | 1. SDK will work as expected and detect incidents (Braking, Acceleration, Cornering, Phone usage) 2. improves automatic trip detection |
| Battery Optimization | It enables SDK to works in the background | if OS kills tracking, the SDK won't be able to re-launch it. Inconsistent Data collection (rare data points), Trips won't be automatically uploaded to Damoov server | OS allows the app to work in the background |
Updated 3 months ago