Zendrive SDK v8.0 Release Notes
Updates Made to Android SDK 8.0
1. Background Location Permission
Important Notes:
In Android 12, when the Zendrive SDK app has been permitted coarse location accuracy even when it has background location permission, the SDK app is known to crash. We have fixed this issue in SDK version 8.0.
If drivers are using Android 12 while running a Zendrive SDK version below version 8.0, then the SDK users must not navigate to App Info -> Permissions -> Location and toggle location accuracy from Fine to Coarse.
Alternatively, drivers must upgrade the Zendrive SDK version to 8.0.
Explanation
The Zendrive SDK requires “High” accuracy location and background location permission for trip detection. Therefore, the application will request for the following permissions:
Location Access: This permission determines whether the application has foreground (or background) location permissions.
Location Accuracy: This permission determines whether the application has Coarse or Fine accuracy.
In order to be able to detect trips accurately, the Zendrive SDK requires Background permissions and Fine accuracy. In versions prior to Android 12, granting the background location permission ensured access to Fine Accuracy location. Android did not allow users the flexibility to change Fine Accuracy setting to Coarse, which is why trip detection worked flawlessly.
However, from Android 12, a newly enhanced privacy feature allows users the flexibility to change location accuracy from “Fine” to “Coarse” location any time after granting background permissions.
2. Screen Overlay Feature Disabled
The tap detection feature in Android devices uses screen overlay, which causes the device screen to freeze while using Zendrive SDK-built apps. Zendrive SDK 8.0 takes care of this issue by automatically disabling the screen overlay feature in Android 12 devices.
Note: We recommend users on Android 12 to upgrade their SDK version to 8.0, in order to avoid usability issues.
Benefit: Smooth running of your app, minus incidents of the device screen freezing.
3. Trip Start Extrapolation
The Trip Start Extrapolation feature determines the start location of the next trip by using the end location of the previous trip. This feature extrapolates the distance between both locations and captures this ‘missing mileage’ under a new field called Extrapolated Distance.
Trip Start Extrapolation is useful for calculating mileage accurately. For example, if the user has subscribed to pay-per-mile programs, this feature can help get the most out of the Zendrive SDK. For more information, See our Trip Detection and Tracking product guide.
Improvements and Updates
1. Android Tap Detector
The tap detection feature in Android devices uses screen overlay, which causes the device screen to freeze while using Zendrive SDK-built apps. Zendrive SDK 8.0 takes care of this issue by automatically disabling the screen overlay feature in Android 12 devices.
Note: We recommend users on Android 12 to upgrade their SDK version to 8.0, in order to avoid usability issues.
Benefit: Smooth running of your app, minus incidents of the device screen freezing.
2. Android Collision Detection
The improvements help reduce missed collisions due to phone fall detection, which results in 10% additional collision detections.
Benefit: Improved collision detection is a major factor while computing a user’s road worthiness.
3. Trip Classifier Improvements
The motorcycle classification feature identifies patterns based on the vehicle’s acceleration, braking and turning to spot differences in vehicle dynamics. The model uses this data to determine whether the user is driving a car or a motorbike.
Note: The improvements made to this feature in Zendrive SDK 8.0 are applicable mostly to the motorcycle riders in the state of Colombia. Owing to the fact that there are differences in the types of roads and motorcycle models, our detector requires data from each region.
Benefit: Currently, for the State of Colombia, Zendrive SDK delivers 85%+ efficiency for both precision and recall.
Bug Fixes
1. Crash Fix of Bluetooth Permission
A workaround is in place to prevent Zendrive SDK 8.0 from crashing when the Bluetooth permission is removed from the Manifest. Customers who wish to remove the Bluetooth permission from their Manifest experienced a crash of Zendrive. This issue has been fixed in Zendrive SDK 8.0.
Android Permission Guide
There is a new guide for Android permissions and errors to help you integrate the Zendrive SDK correctly. See Android Permissions.
Zendrive SDK 8.0 for iOS 15
Zendrive SDK 8.0 has been updated to support iOS 15. Support for iOS 15 ensures that Zendrive SDK can gather user and trip data from users who carry iPhone version 6 or above. The following tables detail product improvements and bug fixes made to the Zendrive SDK for iOS 15:
1. Trip Classifier
The motorcycle classification model now operates with better recall and precision. This feature identifies patterns based on the vehicle’s acceleration, braking and turning to spot differences in vehicle dynamics. The model uses this data to determine whether the user is driving a car or a motorbike.
Note: The improvements made to this feature in Zendrive SDK 8.0 are applicable mostly to the motorcycle riders in the state of Colombia. Owing to the fact that there are differences in the types of roads and motorcycle models, our detector requires data from each region.
Benefit: Currently, for the State of Colombia, Zendrive SDK delivers 85%+ efficiency for both precision and recall.
2. Bug Fixes
Zendrive SDK 8.0 has been improved to handle sensor data variations for event detectors. Improved Robustness for handling sensor data variations for event detectors.
Documentation References
See Android SDK Javadoc.
Was this helpful?