DriveMotionMonitorClient
TNDriveMotionMonitorClient mainly provides some monitor functions for trip upload status. developers must obtain DriveMotionMonitorClient after initializing DriveMotion.
Get TNDriveMotionMonitorClient
1 2 3 4 5 | |
1 2 3 4 5 | |
Use TNDriveMotionMonitorClient
TNDriveMotionMonitorClient provides some monitor functions for trip upload status.
Get Upload Progress Request
the TNGetUploadProgressRequest will get the trip upload progress.
Build Request
1 | |
1 | |
Create a Call and execute it
Callback is a closure accepting response and error parameters.
1 2 3 4 5 6 7 8 9 | |
1 2 3 4 5 6 7 8 9 | |
Get Upload Success Timestamp
the TNGetUploadSuccessTimestampRequest will get trip upload success timestamp.
Build Request
1 | |
1 | |
Create a Call and execute it
Callback is a closure accepting response and error parameters.
1 2 3 4 5 6 7 8 9 | |
1 2 3 4 5 6 7 8 9 | |
Bluetooth unavailable during trip (since 3.18.0)
When edge matching is enabled, the SDK can notify your app if phone Bluetooth is off, app BT permission is not granted, or both, while a trip is already recording and no qualifying peripheral has been seen for a configurable period. The trip is not stopped; this is for in-trip diagnostics only.
Set an object that conforms to TNDriveMotionMonitorDelegate on DriveMotionSettings when you configure the DriveMotion service (see Initialize the SDK and monitor delegate wiring). An optional callback is used:
1 2 3 4 | |
Threshold configuration
The minimum time after trip start (and on trip interval checks) before this may fire is controlled with btUnavailableTripThresholdSec in remote dm_common_model, mapped to CommonConfig. The default in the SDK is 120 seconds if unset.