Zendrive SDK v8.2 Release Notes
Important: Upgrading User Devices to Android 12
Please note that Zendrive SDK supports only Android 12 on user mobile devices. Zendrive SDK does not support customer applications targeting Android 12 (which corresponds to Android API level 31).
Zendrive intends to provide support for customer applications targeting Android 12 in Q2, 2022. Please note that upgrading applications before Zendrive’s Android 12 support is released will cause applications to crash.
Zendrive SDK 8.2: New SDK Features for Android 12 and iOS 15
Product Name
Zendrive SDK
Product Version
Version 8.2
OS Support
This version supports Android 12 and iOS 15.
Product Release Date
December 13, 2021
1. SDK Pause Auto Tracking
Description: The Pause Auto Tracking feature allows users the flexibility of pausing SDK’s trip detection feature whenever they want some personal time.
Explanation: Users can now pause SDK's automatic trip tracking whenever they choose, to take a few hours or a few days off. During this time, SDK completely pauses trip tracking and monitoring.
Once the user-specified Pause Auto Tracking duration is complete, SDK automatically resumes tracking the user's trip. However, users can override the pause state and resume the SDK manually if they so choose.
The SDK remains active during pause auto tracking activity, and continues to look for geofence breaches and bluetooth devices for trip monitoring.
Trip data is collected during pause auto tracking, and is analyzed locally within the SDK, but not recorded in the backend.
The locally stored data is purged periodically. The Fleet Manager can monitor users’ pause auto tracking period information from their web dashboard.
Benefit: Users can use pause trip detection for a set period, whenever they want, to suit their personal needs. This feature is especially useful for Commercial Lines.
2. Vehicle Type in Collision Callback
Description: We have introduced a new parameter called ‘vehicle type’ within the Vehicle Type accident info object in the SDK collision callback. This parameter helps to identify the type of the vehicle involved in the collision.
Explanation: In previous versions of the Zendrive SDK, the accident info object would identify the vehicle type involved in an accident as a car. As of SDK v8.2, the 'Vehicle Type' parameter correctly identifies it as a motorcycle.
Benefit: This feature will be useful to customers interested in offering specialized emergency services for motorcycles.
3. Map Matching
Description: We can now use GPS data to map the routes taken by transport vehicles using the new Map Matching API.
Explanation: This API works with the Trip Classifier API to deliver a very accurate performance in matching on-road and off-road transport routes.
Benefits: Zendrive SDK’s server-based map matching technology offers the ability to map trips taken via rail networks, boats, ferries, joy boats, yachts, cruise ships, snowboarding vehicles, skis and so on.
Zendrive SDK 8.2 (For Android Only)
1. Beacon Based Trip Start
Description: When the BLE Beacon associated with the vehicle senses the user’s device, it wakes up the app, and puts it in ‘‘May Be in Drive’ state.
Explanation: If the user starts the vehicle after the BLE Beacon wakes up the app, then SDK starts the trip. However, the trip could be delayed if the user does not start the vehicle immediately, or if the user is currently in a basement location.
Benefit: This feature will help detect trip starts faster and improve mileage accuracy.
Zendrive SDK 8.2: Enhancements (Android 12 and iOS)
The following improvements have been made to the Zendrive SDK for v8.2:
1. Low Accuracy Trip Detection
Description: Previous versions of SDK used Google’s Location Accuracy for trip detection while indoors. However, it was noted trips weren’t being recorded while indoors when Location Accuracy was enabled. We have removed the dependency on Location Accuracy from this release. From SDK 8.2 onwards, SDK will track trips even if Location Accuracy is not enabled, by using other GPS-based sensors.
2. Core Sensor Fusion Upgrades
Description: Improvements have been made to the core Sensor Fusion technology, resulting in greater precision in driving detection.
Explanation: The SDK’s core Sensor Fusion technology processes raw sensor data and provides inputs to all driving event detectors.
Benefit: The SDK can now detect hard bakes, hard turns, aggressive acceleration and over-speeding with better precision and recall.
3. Collision Severity
Description: The Zendrive SDK’s collision detection feature can now sense the severity of the collision. We're able to categorize collision severity as High or Low.
Explanation: High collision severity indicates that there’s been major vehicular damage and therefore potential physical injuries. Low collision severity indicates that the collision detected is likely a minor one, with potentially no injuries.
Benefit: Obtaining a collision severity notice in advance enables quick emergency response and action for the driver (and passengers).
4. Android Tap Detector
Description: Zendrive’s Tap detector feature was deactivated due to issues with the Screen overlay permission in Android 12. In SDK 8.2, customers can opt to use one of the following two options are available to customers who still want to use the tap detector event:
Android Tap Detector V2: This version uses a new flavor of the screen overlay permission, suitable for applications that are willing to fetch screen overlay permission from users.
Android Tap Detector V3: This version is a sensor-based event detector that has lower accuracy than Tap Detector V2. However, it does not require any additional permissions from the user.
Benefit: This fix will help users to continue to use a familiar Android feature.
Known Issue: iOS 15 Trip Detection Loss
On iOS 15, when the app is killed and not launched for a certain period of time, SDK does not detect the next trip unless the app is launched again in the foreground. This issue can lead to loss of trip detection for apps running on iOS 15.
The loss of trip detection is due to an issue with Geofencing errors on iOS 15. SDK versions 8.0, 8.1 and 8.2 will be impacted by this issue.
Fix: We expect this issue to be fixed automatically when Apple Inc., updates their iOS15 software.
Was this helpful?