Android SmartDrive framework ‐ Release Notes - scopetech/Mobile-Public GitHub Wiki
Android SmartDrive SDK Release Notes
Release notes for each SmartDrive framework - what was changed, fixed, improved or added.
Versions
v1.6.9 - 12 October, 2026
[!IMPORTANT] LATEST VERSION — bundled by Consolidated SDK
com.scopetechnology:sdk:1.1.9. Covers the whole 1.6 line; 1.6.5 to 1.6.8 were interim builds.
- New TripWrapper facade, the recommended way to integrate. One host class that answers whether a user is logged in, one typed configuration, and five calls:
initialize,start,authenticated,permissionsChanged,logout. Recording starts on its own once a session, a vehicle and the permissions fromrequiredPermissions()are in place, and resumes after a reboot. Through the Consolidated SDK the same API isScopeSDK. The directSCPSmartDriveManagerAPI keeps working. See Android Simplified SDK Integration. - Trip events and counts come through callbacks for trip started, updated, ended and sent, and through the
tripStateandtripCountsflows, which stay current without polling. - Sending:
retryFailedTrips()sends every unsent trip on demand, quarantined ones included;confirmProcessingTrips { fetchTrips() }keeps the processing count in step with the Portal;tripRetentionDays(default 30) runs the retention sweep for you. - Diagnostics:
getDiagnostics()andisHealthy()for a status screen, and aTRIPWRAPPER HEALTH SNAPSHOTin the log at start, trip start and trip end. See Android Diagnostics and Health Snapshot. - Recording quality: a parked phone's drifting position no longer prolongs or splits a trip, a trip start from an idle phone needs a real departure, and MHub vehicles can record distraction events only.
- Requirements and updating:
compileSdk 36or later (built with Android Gradle Plugin 9). Pairs withshared-classes1.1.7,portal-api-base1.2.9 andble1.5.6. From an interim 1.6 build, bump the version and callinitializebeforestartif you do not yet. Moving an existing app to the facade: Android TripWrapper Migration Guide.
v1.5.5 - 7 September, 2026
- Reliable trip sending. A background worker sends unsent trips with retries: at trip end, when a network is available and every 8 hours. Uploaded trips stay on the phone until the backend confirms them, and a trip the backend keeps rejecting is set aside for manual sending instead of being retried forever.
- Automatic resending is one switch,
resendFailedTrips(true)onSCPSmartDriveManager(default off), and trips held by the manual-sending window upload on their own when the window expires. See 2.1.5. - Recording under Doze and Battery saver: budgeted wakelocks around trip start, a GPS keep-alive when the fused provider is throttled, and tolerance to GPS gaps during a trip, so trips start and continue on an idle phone. The guidance in 1.2.4 still applies.
- Fixes: trip data is no longer lost or mixed between trips at trip end, nothing records without a login, and mode-of-transport analysis is corrected. Pairs with
shared-classes1.1.6 andportal-api-base1.2.9.
v1.5.2 - 22 July, 2026
- Improved trip start detection — trips start sooner when movement is detected, reducing delayed or missed trip starts.
- Improved ghost-trip detection — better filtering of false trips caused by GPS drift while parked, reducing the likelihood of phantom trips.
- Simplified SDK integration — the SDK now bundles the ProGuard/R8 keep rules it needs, so apps using code minification integrate without adding manual configuration
v1.4.13 - 3 Jun, 2026
- Migrated Protobuf library from full version to lite
- Should be used together with SharedClasses v1.1.5
v1.4.12 - 16 Dec, 2025
- All Locations gets validated for impossible acceleration
- Fix for too long exception duration when GPS signal is weak
v1.4.11 - 27 Oct, 2025
- Simplified Real-time event sending configuration
- Removed redundant(unit provisioning related) config items.
- Added extra logging to help developers to diagnose issues related to incorrect MProfiler configuration
- Combine MProfiler config and Real-time event sending feature enablement into single config item.
v1.4.5 - 27 Jun, 2025
- Optimised trip end detection logic if Real-time event sending is used.
v1.4.4 - 25 Apr, 2025
- Off-Road MOT detection implemented
- Railway MOT detection logic improvements
- Event re-sending fixes
- Gradle upgrade to v8.9
v1.4.2 - 8 Oct, 2024
- MOT detection fixes
- Distraction detection fixes
- Bug fixes for Android 14
v1.4.1 - 14 Jun, 2024
This version has refactored SmartDrive codebase for easier maintenance and improved performance.
v1.3.7 - 15 Mar, 2024
This version focuses on trip sending algorithm improvements.
- Improving trip sending flow when using "Portal" approach.
- Unfinished trips marked with correct state in case of no network.
- Clearing resources correctly and avoiding incorrect states in manager that is responsible for trip sending.
- Predictable approach using coroutines for async work
v1.3.6 - 25 Feb, 2024
Introducing new feature Realtime trip events sending.
v1.3.2 - 30 Jan, 2024
Bugfix version for v1.2.1 for distracted driving.
- Previous version had a bug where even defined "minimumSpeed" was not taken into account in reality. This version makes sure speed validation is done correctly. Developers need to update version number and that is it - no other changes in code are needed.
v1.2.1 - 10 Jan, 2024
Introducing new configuration for Distracted Driving.
- "minimumSpeed" value is now taken into account when event validation happens. If you set minimum speed as
5.0fvalue, which means that minimum speed is5km/h, any event that is detected with lower speed will be ignored.
v1.2.0 - 07 Dec, 2023
- Major code refactoring