The “wake-up” feature is used to wake up or start you application when important trip events occur (e.g. if a trip is started). With this mechanism you don’t need to worry about connection persistence. Note: Once a wake-up event is fired and the trip status changes the wake-up feature must be registered again.
A service wake-up is much more reliable in terms of killing an application (when an app is force closed or killed). The service wake-up will start even when the application was force closed by a user. More on this can be understood from the API documentation provided once logged in.
You can decide. The connection can be persistent but if there is no need to stay connected, we recommend you use the wake-up feature to wake up your application when a user’s trip status changes. Using the wake-up feature will help reduce battery usage.
Not exactly. In Android, the connection itself does not require many resources. However, it is possible that your application does. Therefore if you do not need to start your application because a trip is not in progress then you should use the wake-up feature.
Maintaining connections to Cellematics Service is in your hands. You will be notified with a proper callback if your connection with Cellematics Service was lost. It is up to you to decide if you would like to re-register or remain disconnected. Please see “Sample Project” for best practices.
Cellematics Service does not reconnect automatically. Either register for the wake-up feature or try to reconnect to Cellematics Service using Android’s BOOT_COMPLETED action.
Cellematics Service doesn’t require Internet connection most of the time. If it should require connection and is unsuccessful at the time you will be notified with a setup error code: NO_INTERNET_CONNECTION. Reference the documentation.
Upon initial installation, Cellematics Service requires some time and an Internet connection to configure itself in order to provide the highest quality of services. If you experience this malfunction simply re-establish Internet connection and after a short wait it should work fine. Reference the documentation.
There is no guarantee which event will come first – the wake-up call or tripClassChanged callback – But, you are guaranteed that when tripClassChanged callback will be called you can safely reregister for a wake-up call.
Yes. Cellematics Service works in heavy-traffic situations but like any software solution solving a complex problem there may be inaccuracies at times.
It allows for the reduction of battery usage by sharing the same resources among multiple applications.
Yes. Cellematics Service is one instance running on a device as a remote service. However, approval for each client is required.
No. Your Cellematics Service application key is only valid for an individual application. You may apply for additional application keys for each additional client.
If you would like to download a sample project that you can build on and run on your device please click here.
You will need a License Key to access the Cellematics Service itself.
Apply for a license key below.