Android: SmartDrive 1.6.6 / Consolidated SDK 1.1.6 — initialize(), vehicleSelected(), compileSdk 36
Hub, Simplified integration, TripWrapper SDK, Migration guide, Lifecycle, Diagnostics,
Demo overview and the framework page move to 1.6.6 / 1.1.6 (BLE 1.5.6, shared classes
1.1.7): five lifecycle calls with initialize() restoring the last accepted configuration
at process start, vehicleSelected() with the unit type for apps without PortalAPI in
place of the host's vehicleUnitType(), configurations comparing by value, and the
compileSdk 36 requirement the AGP 9 builds introduce. The Lifecycle page's restart
story now rests on initialize rather than start. Release notes gain the v1.6.6 entry.
Android: re-apply start when a setting is chosen after launch
The SmartDriveDemo field log of 2026-10-07 showed the SDK started in
SMART mode before the first-run screen set BLE, so it gated recording
on a permission the app never requested. The demo now calls
ScopeSDK.start again from AppTypeActivity; the integration page gets a
pitfall for settings chosen after launch and the demo overview shows the
extra call in the lifecycle and the sequence.
Android: SmartDrive 1.6.7 / Consolidated SDK 1.1.7 — tripCounts stays current; demo Local trips
Release notes entry for 1.6.7, the 1.1.7 row in the Consolidated SDK versions
table, dependency snippets and "last updated" lines on every Android page, the
tripCounts row on the TripWrapper page with when the flow refreshes, and the
demo overview's new Local trips block.
Android: confirmProcessingTrips (SmartDrive 1.6.8) in the API reference, the integration guarantees and the demo overview
Android: SmartDrive 1.6.8 / Consolidated SDK 1.1.8 release rows
Release notes v1.6.8 with the latest-version banner, the 1.1.8 row and
paragraph in the hub page's version table, dependency snippets and
last-updated lines on the integration, diagnostics, TripWrapper, migration,
SmartDrive and demo pages, and the migration guide's processing-check rows
pointing at confirmProcessingTrips.
Android: retryFailedTrips as a manual send (SmartDrive 1.6.9); the demo's Auto-resend failed trips switch
Android: SmartDrive 1.6.9 / Consolidated SDK 1.1.9 release rows
Android: SmartDrive 1.6.5 / Consolidated SDK 1.1.5 — the facade release (tripRetentionDays, ghost-rule fix); 1.6.4 folded into it
Android: document the consolidated SDK and the TripWrapper facade
Six new pages, mirroring the iOS set: the Consolidated SDK hub, Simplified SDK
Integration, the TripWrapper SDK reference with the direct-manager mapping
table, the TripWrapper migration guide, the SmartDriveDemo Android app
overview, and Diagnostics and Health Snapshot. Home and the sidebar gain a
Consolidated SDK block listing them.
The SmartDrive framework page keeps the direct-manager API and the permission
and battery guidance, headed 1.6.4 with a banner pointing new integrations to
the facade, current dependency versions, a note mapping section 2 onto typed
fields, the retired extreme-battery-saver setting marked as such, and the
facade's retry path noted in 4.8. Release notes gain 1.6.0 through 1.6.4.
Demo links point at SmartDriveDemo-Android's feature/new_facade branch, where
the consolidated integration lives.
SmartDrive: Battery saver (Power saving mode) guidance in Requirements
Battery saver is separate from the battery-optimisation exemption and has a
much stronger effect: with it on, location, activity recognition and
background work are throttled for every app and the phone drops back into
deep sleep far more aggressively, even while driving - trips get missed or
start many kilometres late on a phone that is correctly exempted. Adds a row
to "Permissions at a glance" and a block in 1.2.4 with the recommendation to
keep Battery saver off (no per-app exemption exists) and a Kotlin sample for
detecting it (PowerManager.isPowerSaveMode) and opening the settings screen.
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework: Vehicle selection documentation
This update clarifies the process for setting the recording vehicle, explaining the importance of the unit serial number for backend trip processing. It details the two-step configuration when using PortalBaseApi and explicitly notes that trips cannot be sent to the backend without a selected vehicle ID.
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Added documentation for the `sendAllUnsentTrips()` method to support Mode of Transport (MOT) configurations and handle incomplete MOT reports.
Updated Android SmartDrive framework (markdown)
Added a new section on retrying failed trips and updated existing sections to clarify the limitations of the built-in auto-resend feature and the behavior of trip processing.
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Added section about selection of recording vehicle
updated latest SDK versions
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Updated documentation to support SmartDrive v1.4.2
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework (markdown)
Updated Android SmartDrive framework 1.2.1 (markdown)