Fairmatic Broadcast Receiver
A receiver to receive callbacks from the Fairmatic SDK when interesting events occur or are detected in the SDK. To receive these callbacks - the application should subclass this class and implement the abstract handlers for SDK callbacks. The subclass should then be registered with the Fairmatic SDK via the SDK setup call.
The application broadcast receiver subclass is not allowed to directly handle intents by overriding the onReceive method of the BroadcastReceiver. The raw SDK intents are not guaranteed to be backward compatible across versions. The application should implement the abstract handler methods in this class to receive the callbacks.
Functions
Called when Fairmatic SDK detects an accident.
Called when the Fairmatic SDK has analyzed a drive. This will only be called for drives where FairmaticDriveType is not FairmaticDriveType.INVALID.
Called when the Fairmatic SDK ends a drive. The drive may have been manually started and ended by the application or auto detected by the SDK.
Called when the Fairmatic SDK resumes a drive after a gap. The gap in drive recording may occur due to an application restart by the OS, application kill and restart by a user, an application crash or other reasons.
Called when the Fairmatic SDK starts a drive. The drive may have been manually started by the application or auto detected by the SDK.
This method is called when the Fairmatic SDK detects a change in device settings that affects trip detection or the normal functioning of the SDK. The user should call com.fairmatic.sdk.Fairmatic.getFairmaticSettings to get detailed error information.
This is an experimental feature, disabled by default. An early notification of a possible collision. This collision is confirmed or invalidated by onAccident callback. Contact support@Fairmatic.com to enable the feature.